Why do Systems Engineering? Manage Complexity. Reduce your Risk INCOSEUK Systems Engineering does: The International Council on Systems Engineering Z1 Issue 3.0 Cope with complexity. The benefits of Systems (INCOSE) defines Systems Engineering as “an March 2009 Engineering include not being caught out by interdisciplinary approach and means to enable the omissions and invalid assumptions, managing real realisation of successful systems.” world changing issues, and producing the most What is Systems Engineering? efficient, economic and robust solutions to the need UK members were asked what this definition means Creating Successful Systems being addressed. to them. This leaflet collates the best of these answers into an explanation of the what and why of Systems Systems Engineering is: By using the Systems Engineering approach, project Engineering. "Big Picture thinking, and the application of Common costs and timescales are managed and controlled Sense to projects:” more effectively by having greater control and Systems Engineering IntegratesTechnical Effort awareness of the project requirements, interfaces and Across the Development Project: “a structured and auditable approach to identifying issues and the consequences of any changes. ■ Functional Disciplines requirements, managing interfaces and controlling ■ Technology Domains risks throughout the project lifecycle.” Systems engineers work with programme managers ■ Specialty Concerns to achieve system and project success. Research indicates that effective use of Systems “Build the right system; build the system right.” Engineering can save 10-20% of the project budget. This leaflet is intended to help the “intelligent Systems Engineering considers the whole problem, layperson” to understand what Systems Engineering the whole system, and the whole system lifecycle is and how it could help them and their business. from concept to disposal, “from lust to dust.” It is not hard to know when System Engineering fails, For further information, advice and links to helpful because when something important goes wrong it websites, go to: The V lifecycle model shows the logical relationship usually makes the news fast. People get killed, www.incoseonline.org.uk. between the different Systems Engineering activities buildings fall down, companies go bust, the law or ‘processes’. becomes involved. Download copies of this leaflet and other Systems Engineering resources online at: But when System Engineering goes right, no-one understanding the assess system www.incoseonline.org.uk notices, which is just how it should be. The computer problem space value works when you switch it on, trains run on time, your need validate operate decomission For more information about the worldwide Systems flight lands on time and no one gets mad. Engineering professional community, go to: requirements verify www.incose.org design integrate support dispose

constraints specify accept INCOSEUK @incoseuk detail design/ understanding the assess system manufacture/ Z1 Issue 3.0 March 2009 solution space cost and risk INCOSEUK product code INCOSE© 2015 INCOSEUK UK ltd. 6 Steps to Success Half of all project failures could be prevented 6 Steps to Success by more effective Systems Engineering.

Understanding the Problem Agree and manage the requirements Understand and write down the benefit to be Requirements form the basis for contracts and achieved by the system, and how the system will be acceptance. Starting from the desired effect of the used. Manage Complexity new system, balance requirements with budget and technical feasibility. Identify and consult relevant Identify the key measures of operational effectiveness Reduce your Risk stakeholders. Identify and manage assumptions. (MOEs), and work out how much improvement you Assess impact of proposed changes and trade-offs. expect from the new system. Identify the stakeholders And test the system against its requirements. and agree the system boundary. More than one in three of all projects will fail. Think! How will the environment change between More than two-thirds will not achieve all their aims. Agree and manage the interfaces now and when the system is ready? And how will the Failure is usually obvious only when the project is Manage interfaces to make sure the parts of the environment and end users respond to the new overdue and the budget has been spent. solution combine with each other and the operational system? But decisions and plans made earlier in the project environment to create an effective whole – and to can alter your risk, sometimes dramatically. allow teams to work in parallel confident that all the pieces they are developing will fit together and work Investigate alternative solutions together. Identify who is responsible for and involved Consider, model and evaluate both novel solutions in each interface. and improvements to existing ones. Work out how you will choose between the alternatives; and record Don’t rely on luck; your decision process and rationale in case things use Systems Engineering Track progress against a plan change later and you need to backtrack. Define a As well as the traditional Project Management system architecture that encompasses all elements of measures of cost, schedule and resources, it is the solution. important to track skills, decisions and technical Leaflet prepared and published by the UK Chapter of the performance. Adapt to changes and be prepared to International Council on Systems Engineering. backtrack on decisions. Failure to agree requirements

Prepare the test and support systems With contributions from: or interfaces may be symptoms of deeper problems. Prepare the test, training and support capabilities in Timothy Cusk - Network Rail, parallel with the “operational system”. Make sure Mark Lewis - Scott Wilson, they are all compatible and ready when they are Steve Fielding - Metronet Rail SSL Ltd, needed to test, commission, deploy and use the Jim Brunton - Managed - Complexity, system. Colin Brain - SE Validation, ...and the “Z1 project team”, Ayman El-Fatatry, Ken Astley (SEIC) Samantha Brown (BAE SYSTEMS), Les Oliver (EADS Astrium), Paul Davies and Hillary Sillitto, (Thales), Hazel First look out from your system Woodcock, (Telelogic), and review comments from other UK Chapter members. © 2009 UK Chapter, International Council INCOSEUK All queries should be addressed to the series editor on Systems Engineering INCOSEHazel WoodcockUK email: [email protected]