overview on system engineering: applications

Basics of system engineering

1. System engineering Raju Gogoi ( 214216024 , M.tech , IE&M ) Industrial Engineering & Productivity Management

2. Need for System Engineering 1. Air bags , safety device appearing in automobiles in the early 1990’s, became the cause of death for a noticeable number of individuals . Cause : Flaws in the design. Testing and. Deployment conditions used.

3. 2. ARIANE 5 Flight 501 Failure, Ariane 5, the launch vehicle developed by European Space agency, was first launched on June 4 1996, with four satellites. At 37 seconds into flight, Ariane5 veered off course and disintegrated shortly thereafter. Cause: Major flaw in the communication interface.

4. When do you require system engineering ? The system consists of diverse components that have intricate relationships with one another and hence is multi-disciplinary and relatively complex. The system uses advanced technologies that are central to the performance of its primary functions Examples: Satellites, aircraft, auto assembly plant, railway reservation system etc.

5. 3. The First ICBM Project: ATLAS D esigned by the Air Force Ballistic Missile Division B uilt by the Convair Division of General Dynamics. Atlas was the foundation for a family of successful space launch vehicles now built by United Launch Alliance. The Atlas rocket family is today used as a launch platform for commercial and military satellites, and other space vehicles . Involvement of People- 18000 Scientists and E ngineers 17 contractors 200 subcontractors 200,000 suppliers

6. System Engineering Systems Engineering is a top-down, life-cycle approach to the design, development, and deployment of large-scale systems, processes, or operations to meet the effective needs of users and stakeholders in a cost-effective , high-quality way. An organized and systematic way of design Considers all the factors involved in the design Integrates all the disciplines and specialty groups into a team effort Ensures the business and customer needs of all stakeholders and ensures a system that meets the user need C onsiders both the business and the technical needs of all customers with the goal of providing a quality product that meets the user needs.

7. Systems Engineering Mech Engrg Elec Engrg Chem Engrg SW Engrg Civil Engrg Systems Engineering Safety Reliability Maintainability Environment Producibility Systems Engineering Avionics Computers Communications Structures Processes Role of Systems Engineering in Product Development Integrates Technical Effort Across the Development Project Functional Disciplines Technology Domains Specialty Concerns

8. Now, What is a System? A group of interacting, interrelated, or interdependent elements/Components forming a complex whole.(A functionally related group of elements) The human body regarded as a functional physiological unit. Planets, moons and the sun make the Solar system A group of physiologically or anatomically complementary organs or parts: the nervous system ; the skeletal system. A group of interacting mechanical or electrical components. A network of related computer software, hardware , and data transmission devices . Natural Systems Artificial Systems “A system is commonly defined to be a collection of hardware, software, people, facilities, and procedures organized to accomplish some common objectives”

9. System Classification - Complex Behavior Simple structure Simple Behavior Complex structure Complex Behavior Complex structure Complex Technical Simple Human Simple x Technical Complex Human Complex Technical Complex Human

10. System Examples - Spacecraft as a System - A spacecraft can be considered as a system composed of a variety of subsystems . Spacecraft architecture (the division into subsystems) is fairly well defined. The subsystem are in turn composed of smaller subsystems. Spacecraft Bus (SUB- SYSTEM 2) Attitude determination and control Payload processing Power Structures Thermal Payload (SUB- SYSTEM 1) Antenna Filters Multiplexers Spacecraft ( SYSTEM )

11. System Dimension 6 levels 6 levels

12. System Design Hierarchy - Technical levels

13. Define Requirements Investigate Alternatives Full-Scale Design Implementation Integration & Test Operation, Maintenance & Evaluation Retirement, Disposal & Replacement SYSTEM LIFE CYCLE STAGES

14. Identification of Need Concept Definition System Integration Preliminary System Design Detailed Configuration Design Deploymen t Production/ Manufacturing Retirement Operation Refinement Maintenance Development/ Design phase Manufacturing phase Deployment phase Training phase Operation/maintenance phase Refinement Phase Retirement phase

15. Cost and Influence of Each Phase of the Life Cycle for a Municipal Transportation System - Define Requirements Concept Exploration Full Scale Design Manufacturing Operation & Maintenance Retirement & Replacement The size of each object is propotional to its cost. The length of each object’s hadow ’ is proportional to its influence. Define Requirements Concept Exploration Full Scale Design Manufacturing Operation & Maintenance Retirement & Replacement The size of each object is propotional to its cost. Concept Exploration Full Scale Design Manufacturing Operation & Maintenance Retirement & Replacement to its cost.

16. DESIGN PHASE

17. SIX FUNCTIONS (STAGES) OF DESIGN PROCESS Define system level design problem : Originating requirements development Develop the system functional architecture : Analyze function allocation 3 . Develop the system physical architecture : W hich component require 4 . Develop the system operational architecture : How system will be operated 5. Develop the interface architecture : Interface between sub subsystems 6. Define the qualification system for the system : To meet stakeholder requirements

18. DEVELOPMENT PHASE MANUFACTURING PHASE DEPLOYMENT PHASE TRAINING PHASE OPERATION OR MAINTENANCE PHASE REFINEMENT RETIREMENT PHASE Define Requirements Investigate Alternatives Full-Scale Design Implementation Integration & Test Operation, Maintenance & Evaluation Retirement, Disposal & Replacement The system life cycle All the six functions of design process are applicable throughout all the life cycle phases

19. Major Input : Stake holders’ needs/inputs Major output : Originating requirements, Operational concept FUNCTION (STAGES) Operational Concept ( Basic idea of system ) External Systems ( Boundary/Sub system ) Originating Requirements ( Requirements from stakeholders/customers ) Objectives hierarchy ( Prioritize requirements ) Documentation Requirement management 1. Define system level design problem

20. 1.a Originating Requirements REQUIREMENT ANALYSIS Requirements analysis is bridging the gap between system requirement engineering and system design. Requirements analysis determine the requirements for system functions .

21. Originating Requirements Derived from operational needs, operational requirements are those top-level statements defined in language that is understandable to stakeholders, leaving substantial room for design flexibility . Derived requirements Defined by system engineering team in engineering terms during the design process. Supplement Originating requirements Implied Requirements Requirements not specifically identified in the OR but can be inferred based upon the available information. It is anticipated. Emergent Requirements Requirements that are not even hinted at in the OR but whose presence is made known by stakeholders later in the system engineering process.

22. Hierarchy Conclusion : Requirements analysis provides the designer with a model of: S ystem information Function Behavior

23. Documentation of Originating Requirements Clearly Written and unambiguously Should include : Input/output Requirements System wide technology requirements Document is called ORIGINATING REQUIREMENTS DOCUMENT (ORD)

24. 2. Develop the system functional architecture S ystematic process of identifying, describing, and relating the functions, a system must perform, in order to be successful D oes not address how these functions will be performed. (*done by component engineer) Deals with: The top-level functions that need to be performed by the system proceeds to lower levels of the system decomposition to define the system functional design and interfaces Where and how often these functions need to be performed; under what conditions Functional Analysis

25. Why Functional Analysis ? To draw out all the functions, the system must perform to meet its requirements. Decompose functions: determine support functions needed to higher level functions Required for subsequent requirements allocation. To identify profitable trade studies. In describing what must be done and not how to do it, we decouple requirements from implementation. This leaves the implementation trade spaces unbiased.

26. Functional Analysis Tools Functional Architecture : Top-down definition of system functions. Dictionary describing each function. Functional flow block diagrams(FFBDs): Used to show the sequence of all functions to be accomplished by a system. N-squared Diagrams: Used to develop data, function or hardware interfaces. Timelines : Adds consideration of functional durations . Used to support the development of requirements for operations, test and maintenance functions.

27. Example : Functional Decomposition of a NASA Space Science Mission

28. Example : Functional Architecture of a Planetary Defence Program

29. Functional Flow Block Diagrams (FFBD). A primary functional analysis technique is the Functional Flow Block Diagram (FFBD). Purpose : To show the sequential relationship of all functions that must be accomplished by a system. Each function (represented by a block) is identified and described in terms of inputs, outputs, and interfaces from top down so that sub-functions are recognized as part of larger functional areas. Some functions may be performed in parallel, or alternate paths may be taken. Functions are arranged in a logical sequence so that any specified operational use of the system can be traced in an end-to-end path. The FFBD network shows the logical sequence of “ what” must happen.

30. Example: Planetary Defence Level 1 Functional Flow Block Diagram For Threat Detection

31. Example : Planetary Defence Level 1 Functional Flow Block Diagram For Threat Elimination

32. Example : Planetary Defence Level 1 Functional Flow Block Diagram For Threat Re-evaluation

33. Time Line Analysis Although the FFBD network shows the logical sequence of “what” must happen, it does not describe a time duration to functions or between functions. A TLA can be applied to such diverse operational functions as spacecraft command sequencing and launch vehicle processing. TLA defines concurrency, overlapping, and sequential relationships of functions. TLA is used to identify specific time-related design requirements.

34. Time Line Analysis Example for Sub-Function of Launch Readiness

35. THANK YOU !