Overview of Systems Engineering at BAE SYSTEMS & ALENIA MARCONI SYSTEMS

1. Overview of Systems Engineering at BAE SYSTEMS & ALENIA MARCONI SYSTEMS By Leigh Watton Friday 27th July 2001 12/20/2019/MS115-01

2. The Woolly Bit Customer With Money And Perceived Need Customer With Expectation The Total Engineering Process Currently Includes : WOOLLY BIT Product Project Manager Manufacture Detail Design

3. Complexity Scale Width The total complexity of the system exceeds one person’s ‘Brainful’

4. The Concept of Left Shift

5. Late Changes => Bigger Impact £ Cost of Changes specifications drawings interface specs test specs schedule procurement specs purchase orders packaging test equipment tooling reviewing design proving tests operational trials EMC tests environmental trials cost estimates simulation and modelling component selection reliability assessment safety assessment design certificates pink wire mods configuration management concept design plans/strategies estimates requirements analysis/modelling Time Design Stage Production Stage

6. 3A 3B 4 5,6,7 Customer FCA Acceptance SRR FDR SDR PDR CDR TRR PCA RBD FBD SBD PD DD Imp T&I A&C Systems Engineering Generic Activity Sequence (SEGAS) Typical Phase Review correspondence for a development programme

7. HIGHER LEVEL CONTAINING SYSTEM DELIVER SYSTEM SYSTEM REQUIREMENTS PDR CDR FULL PRELIM FCA TRR TRR PCA SRR FDR SDR PDR CDR INTEG OF SUB- T&I A&C RBD FBD SBD PD DD P SYS Imp M SYSTEM SUB-SYSTEM DELIVER REQUIREMENTS SUB-SYSTEM SUB/ FCA SYST PCA TRR SRR SDR PDR CDR FDR A&C T&I RBD FBD SBD PD DD P Imp M SUB-SYSTEM COMPONENTS System / Sub-System Interaction

8. System Analysis and Control System Analysis & Control (Balance) Process Input - Requirements Requirements Analysis Requirements Loop Functional Analysis and Allocation Design Loop Design Synthesis Verification Process Output - System Architecture - Specs and Baseline The Basic RFS Loop

9. Customer Requirements System Requirements Specification R F System Acceptance Specification System Requirements Specification System Functional Structure Integration and Test Specifications System Response Specification S Sub System Requirements Specifications S = C + D The Core Design Process - 1

10. Cust Req Sys Req Spec R F Sys Req Spec Sys Fun Struc Sys Acc Spec Sys Fun Struc Sys Req Spec Sys Resp Spec C D Chosen Sol Sub Sys Req Specs Int & Test Specs The Core Design Process - 2

11. The Core Design Process - 3 Sys Fun Struc Cust Req Sys Req Spec R F Sys Req Spec Sys Acc Spec Sys Fun Struc Sol Concs Sys Fun Struc Sys Req Spec Sol Concs Sys Resp Spec C D Chosen Sol Concerns Sub Sys Req Specs Int & Test Specs

12. Procure (Customer) Supra System Engineer Procure System(s) Research Risk Mitigation Replace or Upgrade Contract Applied Research Bid Maintain System Engineer/Design Feedback Operate Procure, Manufacture and Test Develop System (Contractor) In Service Use (User) Support Train Accept Deliver The Product Lifecycle • Concurrency reduces the risk all round

13. The ‘V’ Diagram TIME L E V E L Design and Specification Integrate and Test Manufacture Parts

14. TIME Accept L Validated System E and Sub Systems Customer's V Customer Equipment and Development E Operational Environment Activities L Tested and Partially-Proven System The ‘V’ Diagram - cont Customer Equipment and Response Trials Operational Environment Specification Integrate with and Drawings Customer's Equipment System Reqts Spec System Response Engineering Integrate Specification Activities and Test and Drawings System Sub System Reqts Spec

15. TIME Accept L Validated System E and Sub Systems Customer's V Customer Equipment and Development E Operational Environment Activities L Tested and Partially-Proven System Tested and Partially-Proven Sub System The ‘V’ Diagram - cont Customer Equipment and Response Trials Operational Environment Specification Integrate with and Drawings Customer's Equipment System Reqts Spec System Response Engineering Integrate Specification Activities and Test and Drawings System Sub System Reqts Spec Sub System Response Engineering Integrate Specification Activities and Test and Drawings Sub Systems Building Block Reqts Spec

16. TIME Accept L Validated System E and Sub Systems Customer's V Customer Equipment and Development E Operational Environment Activities L Tested and Partially-Proven System Tested and Partially-Proven Sub System Tested and Partially-Proven Building Blocks The ‘V’ Diagram - cont Customer Equipment and Response Trials Operational Environment Specification Integrate with and Drawings Customer's Equipment System Reqts Spec System Response Engineering Integrate Specification Activities and Test and Drawings System Sub System Reqts Spec Sub System Response Engineering Integrate Specification Activities and Test and Drawings Sub Systems Building Block Reqts Spec Design Response Building Specification Test Blocks and Drawings Building Detail Drawings and Plans Blocks

17. TIME Accept L Validated System E and Sub Systems Customer's V Customer Equipment and Development E Operational Environment Activities L Tested and Partially-Proven System Tested and Partially-Proven Sub System Tested and Partially-Proven Building Blocks Building Blocks The ‘V’ Diagram - cont Response Trials Specification Integrate with and Drawings Customer's Equipment System Reqts Spec System Response Engineering Integrate Specification Activities and Test and Drawings System Sub System Reqts Spec Sub System Response Engineering Integrate Specification Activities and Test and Drawings Sub Systems Building Block Reqts Spec Design Response Building Specification Test Blocks and Drawings Building Detail Drawings and Plans Blocks Produce Building Blocks

18. System Sub Systems Sub Systems Units Building Blocks Components System Hierarchy The smallest System shown is at 'Building Block' level (e.g. a circuit board), made up from 'Components'

19. Concurrency • The steepness of the “V” represents the level of concurrency Highly concurrent Highly serial, very little concurrency

20. TIME Accept L Validated System E Production Acceptance Customer's V Development E Deliver Systems Activities L The ‘W’ Diagram - cont System Specification and Manufacture Customer Equipment and Response Trials Operational Environment Specification Integrate with and Drawings Customer's Equipment System Reqts Spec Refined Drawings and Test Equipment System Response Engineering Integrate Integrate Specification Activities and Test and Test and Drawings System System PRODUCTION Sub System Reqts Spec DEVELOPMENT PROTOTYPES Refined Drawings and Test Equipment Sub System Response Engineering Integrate Integrate Specification Specification Activities and Test and Test and Drawings and Drawings Sub Systems Sub Systems Building Block Reqts Spec Design Response Building Specification Refined Drawings and Test Equipment Test Test Blocks and Drawings Building Building Detail Drawings and Plans Blocks Blocks Produce Produce Building Building Refined Detail Drawings and Plans Blocks Blocks

21. Concept Demonstrator Concept Demonstrator Development Development Production Production The VW Diagram In order to ‘gain hindsight’ early, a concept demonstrator is built before main development, shown as a narrow V

22. The Process Model and the ‘V’ Diagram (process, product, time) System Engineering Process Model Time Product Hierarchy Waterfall ‘V’ Diagram

23. The Process Model is Recursive It Applies at Each Level in the System Hierarchy System Engineering Process Models ‘V’ Diagram

24. System Engineering Context Diagram Notes 1. The diagram is schematic only a few of the inputs and outputs are shown. 2. Sub system suppliers may be internal or external to own company. 3. The interface to sub system suppliers mirrors that with the customer and user when shown in detail. User (Higher Level Tests/Trials) Customer Management Data, Agreed Requirements and acceptance criteria, Plans, System Design, Design Proving Evidence, Design Certificate Stated Requirements, Acceptance Agreement Facilities Test Records Project Plans, System Design Procedures, Support, Management Data Other Engineering Functions (Project Management, Production, Sub Systems etc.) Prototype System and Support Equipment World Perform System Engineering Support Constraints Compliance Evidence Plans Test Equipment Requirements, Plans Records Management Data, Agreed Requirements and acceptance criteria,, Plans, Test and Support Equipment Designs and Material, Design Proving Evidence, Design Certificate Sub System Requirements, Plans Support, Resources Company Infrastructure Management Data, Agreed Requirements and acceptance criteria, Plans, Sub System Designs and Material, Design Proving Evidence, Design Certificate Sub System Suppliers Test and Support Equipment Suppliers

25. SE Process Model (Level 2) ACCEPTANCE START M MANAGE SYSTEM ENGINEERING F M SS SS PROVIDE SPECIALIST DESIGN SUPPORT R AC DETERMINE REQUIREMENTS SECURE ACCEPTANCE AND CERTIFICATION ISS F PERFORM FUNCTIONAL ANALYSIS T SUPPORT HIGHER LEVEL TESTS (TRIALS) SUB SYSTEM ENGINEERING AND IMPLEMENTATION PROVIDE IN SERVICE SUPPORT D DESIGN SYSTEM AND SPECIFY SUB SYSTEMS I INTEGRATE AND TEST SYSTEM C CREATE CANDIDATE SOLUTION CONCEPTS SYSTEM TEST EQUIPMENT HARMONISE SUB SYSTEM IMPLEMENTATIONS H H A E PERFORM SYSTEM ANALYSIS A DESIGN REVIEWS

26. M F Perform Manage Provide Secure Create Integrate and Specialist Acceptance Candidate Functional System Test System Design and Solution Analysis Engineering Support Certification Concepts R A D Support Harmonise Perform Provide Design System Determine and Specify Higher Level Sub Systems System In Service Requirements Sub Systems Tests(Trials) Implementations Analysis Support Perform System Engineering LEVEL 1 C SS I AC H T ISS LEVEL 2 Level 3 Level 4

27. Specify and Specify and Analyse Capture Prepare Agree System Agree System Requirements Requirements for R Acceptance Requirements Criteria 2.1 3.1 4.1 Define Supra System Analyse requirements Determine requirement Determine conditions 1.1 Identify required skills 5.1 and interfaces data for completeness specification format for acceptance and personnel 2.2 3.2 4.2 1.2 Define required functions Analyse functional Produce requirement Identify customer Select methods 5.2 (see F2) requirements specification supplied items and tools to manage (see F2, F3) requirements 2.3 4.3 Determine Demonstrate traceability Produce system 5.3 3.3 required performance Use modeling and from higher level acceptance specification 1.3 Produce plan, work simulation to analyse specifications breakdown, and 2.4 Determine constraints requirements Review and agree programme 5.4 4.4 on the system (see A) Review, agree and system acceptance control requirement specification 1.4 Produce cost 2.5 3.4 Determine support Develop understanding specification estimates requirements of requirements 1.5 Establish points 2.6 3.5 Determine cost, Explore impact of of contact with numbers and timescale non-compliance customer/user organisation 2.7 3.6 Determine customer’s Refine requirements selection criteria 3.7 Highlight risks 2.8 Determine customer’s requirements for Design Proving 2.9 Determine non customer requirements 2.10 Collect and collate requirement data Determine Requirements R R1 R2 R3 R4 R5