1. System Engineering Approach
Prepared by : Aws S. Noaman
Assigned to : Dr. Angham E. Alsaffar

2. Contents Introduction What is system approach? Historical view
System concept
Features of system approach
Elements of system approach
System approach phases
System Engineering (SE)
Concept
Principles
Advantages
Process
System Engineering Management Plan (SEMP)
Outline
Example
References

3. Introduction
This assignment will provide you with the meaning of the system engineering approach and its techniques and applications in project management, as well as the importance of the approach and the parts of the organization that makes it a system.
In general, a system is an organized, purposeful structure that consists of interrelated and interdependent elements. These elements continually influence one another directly or indirectly to maintain the activity and existence of the system, in order to attain the goal of the system.
Systems approach to management therefore means the visualization of an organization as composed of different elements that work together to form a unitary whole. For example a firm as a whole could have sub systems such as production, marketing, accounting and human resource management.[1]

4. What is a system approach ?
1- Historical view
In the 1960, an approach to management appeared which try to unify the prior schools of thought. This approach is commonly known as ‘Systems Approach’. Its early contributors include Ludwing Von Bertalanfty, Lawrence J. Henderson, W.G. Scott, Deniel Katz, Robert L. Kahn, W. Buckley and J.D. Thompson.
They viewed organization as an organic and open system, which is composed of interacting and interdependent parts, called subsystems. The system approach is top took upon management as a system or as “an organized whole” made up of sub- systems integrated into a unity or orderly totality.[2]

5. 2- system concept
System approach is based on the generalization that every thing is inter-related and inter dependent. A system is composed of related and dependent elements which when interaction, forms a unitary whole. A system is simply a combination of parts forming a complex whole.
One of it’s most important characteristics is that it is composed of hierarchy of subsystems, that is the parts forming the major systems.
For example, the world can be considered to be a system in which various national economies are sub-systems, and in turn each national economy is composed of its various industries, each industry is composed of firms and of course a firm can be considered a system composed of sub-systems such as production, marketing, finance, accounting and so on.[2]

6. 3- Features of systems approach
A system consists of interacting elements. It is set of inter-related and inter-dependent parts arranged in a manner that produces a unified whole.
The various sub-systems should be studied in their inter-relationships rather than in isolation from each other.
An organizational system has a boundary that determines which parts are internal and which are external.
A system does not exist in a vacuum. It receives information, material and energy from other systems as inputs. These inputs undergo a transformation process within a system and leave the system as output to other systems.
An organization is a dynamic system as it is responsive to its environment. It is vulnerable to change in its environment.[2]

7. 3- Classification of systems[7]
Open system
An open system actively interacts with its environment. By interacting with other systems, it tries to establish exchange relationships
Closed system
A closed system is self contained and isolated from the environment. It is a non-adaptive system. It does not receive inputs often from other systems and does not trade with the outside world. Example: An automatic wrist watch

8. 4- Elements of system approach
A system is made of
subsystems: internal and external.
The system boundary : The limits the internal subsystems
function, are determined by
Note: The external subsystems are those which lie outside
the boundary limits, but still influence the system.
As shown in the figure below.

10. 5- system approach phases
Translation : problem objective, criteria and constraints are defined and accepted by all participants.
Analysis : All possible alternatives to the solution of the problem are stated
Trade-off : Selection criteria and constraints are applied to the alternatives to meet the objective
Synthesis :The best solution in reaching the objective of the system

11. System Engineering (SE)
1- concept
SE : Is a set of activities which control the overall design, implementation and integration of a complex set of interacting components ( systems ) to meet the need of all users.[5]
SE : Is an interdisciplinary approach and means to enable the realization of successful systems.
It focuses on defining customer needs and required functionality early in the development cycle, documenting requirements, then proceeding with design synthesis and system validation while considering the complete problem. [3]

12. 2- principles[3] A- Start with your eye on finish line
Reach consensus at the beginning of the project on
what will constitute the success at the end.
B- Stakeholder involvement is key
The system engineering process includes
stakeholders through all stages of the project

13. Why we should use system engineering (SE) ?
3- Advantages
Why we should use system engineering (SE) ?
An adoption of an improved SE process is able to optimized the three main factors of any project:
Cost factor
Time factor
Performance factor

14. 4- process
Many different process models have been developed over the years that specify a series of steps that make up the system engineering approach.
Among these models is “ V “ model It’s first developed in the 1980s, Wings have been recently added to the “ V “ to show how project development fits with project life cycle
The left wing – initial identification and scope.
The central core – definition, implementation and verification
The right wing – Operation, maintenance changes , and replacement of the system

16. Step 1 : Regional architectures
Identifies the integration opportunities that should be considered and provides a head start for the systems engineering analysis
Step 2 : Feasibility study
INPUT
- Project goals, objectives, purpose and need
PROCESS
- Define evaluation criteria
- Perform initial risk analysis
- Identify alternative concepts
- Evaluate alternatives
- Document results
OUTPUT
Feasibility study that identifies alternative concepts and makes the business case for the project and the selected concept

17. Step 3 : Concept of operation
INPUT
Stakeholder information( list, roles and responsibilities)
Recommended concept and feasibility study
PROCESS
- Identify the stakeholders associated with the project
Define the core group responsible for creating the
concept
- Define stakeholders needs
- Create a system validation plan
OUTPUT
Concept of operations
System validation plan

18. Step 4 : System requirements
INPUT
Concept of operation ( Stakeholders needs )
Functional requirements ( applicable standards, regulations and polices.
PROCESS
Elicit requirement
Analyze requirement
Document requirement
Validate requirement
Manage requirement
Create a system verification plan
Create a system acceptance plan
OUTPUT
System requirement document
System verification plan
System acceptance plan

19. Step 5 : System Design INPUT Concept of operation
System requirement document
Existing system design documentation
Off-the-shelf products
PROCESS
- Evaluate off-the-shelf components
Analyze requirements
Evaluate and develop alternatives
- Documents interfaces and Identify standards
- Create integration plan ( subsystem VP , subsystem AP)
- Develop detailed component
OUTPUT
- Off-the-shelf evaluation and alternative summary report
- High level Design
- Detailed design specifications
- Integration plan (subsystem VP , AP and unit/device test plan)

20. Step 6 : Development and testing
INPUT
System and subsystems requirements
System Design
Industry standards
Off-the-shelf products
Unit/device test plans
PROCESS
- Plan software/hardware development
- Procure off-the-shelf products
- Perform unit/device testing
OUTPUT
software/hardware development Plan
Software and hardware components( tested and ready)
Supporting documentation ( e.g. user manual, maintenance manual, installation)

21. Step 7 : Integration and verification
INPUT
System requirements documents
High level design specification
Hardware and software components
Integration plan
System and subsystem VP
Subsystem AP
PROCESS
- Add details to integration and verification plans
- Perform integration
- Perform verification
OUTPUT
Integration Plan (Updated)
Verification plan (Updated)
Integration test and analysis result
Verification results (including corrective actions taken)

22. Step 8 : Initial development
INPUT
Integrated and verified system ( ready for use )
System acceptance plan
PROCESS
- Plan for system installation and transition
- Deliver the system
Prepare the facility
Install the system
Perform acceptance test
Transition to operation
OUTPUT
Hardware and software inventory
Final documentation and training materials
Delivery and installation plan
Transition plan with checklist
Operations and maintenance plan and procedures

23. Step 9 : System validation
INPUT
Concept of operations
Verified, installed and operational system
System validation plan
PROCESS
- Update VP as necessary and develop procedures
- Validate system
Document validation results, including any corrective
actions or recommendations
OUTPUT
System validation plan (update) and procedures

24. Step 10 : Operations and maintenance
INPUT
System requirements ( operations/maintenance )
Operations and maintenance plan and procedures
Performance data
Evolving stakeholder needs
PROCESS
Conduct operations and maintenance plan reveiws
Provide user support
Collect system operational data
Change or upgrade the system
Provide maintenance activity support
OUTPUT
System performance report
Updated operations and maintenance procedure
Recommended enhancements

25. Step 11 : Retirement/Replacement
INPUT
System requirements ( retirement/disposal requirements)
Service life of the system and components
System performance measures and maintenance records
PROCESS
Plan system retirement
Deactivate system
Remove system
Dispose of system
OUTPUT
System retirement plan
Documented lessons learned
Disposed of the retired system properly

26. System Engineering Management Plan (SEMP)[6]
The SEMP will guide all activities through the life cycle of project through :
Capture what activity must be done and how
Define the way that the effort must be managed ( roles, responsibilities, decision making, risk management and etc. )
Define how people, process and product integrate to manage a system and reach the objective.

27. SEMP outline Technical project planning and control
Include details about the project and how it will be managed ( Scope, roles and responsibilities, scheduling, etc. )
System engineering process
Include details about the process used to guide the activities during each phase of the project life cycle
Engineering specialty integration
Include details of how the efforts of engineering specialties will be used and integrated with overall activities.

28. Example to SEMP
SEMP developed to equipment life cycle management from the design to the disposal of equipment ( in center 2700 in Mexico )
The goal is to create and implement a process that will use to manage, maintain and dispose of equipment
The benefits should be
Better planning for new technology
Improved decision making, management and standardization
Result in cost saving and efficiencies

29. Process used for creating this SEMP
SE lead was assigned
SE lead identified the core team to initiate and scope the effort
Basic requirements were collected
Core team state the SEMP outline
SEMP was written and reviewed
SEMP was placed in configuration control ( maintain configuration control through the permissions and editing feature )
SEMP established guidelines and procedures for project management, risk management, assessments and etc. that must be followed by every equipment project in the center

32. References
[1] Application of systems approach to management in organizations by managers, By Dr. John Yabs UN. Of Nairobi 2014
[2] System Approach to Management: Definition, Features and Evaluation!, research BY Smirti Chand, Indiana state UN. 2011
[3] Overview of the system engineering process by Ed Ryen, PE maintenance – ITS 2008
[4] Construction management principles and practices by Alan Griffith and Paul Watson 2004
[5] system approach to engineering design peter H Sydenham 2004
[6] System engineering management plans by Tamara S. Rodriguez 2009
[7] Introduction to the Systems Approach, By H. William Dettmer