Day 1 Presentation NASA

1
Example of Applied Systems Engineering at BAE
SYSTEMS ALENIA MARCONI SYSTEMS
By Keith Minnican Friday 27th July 2001
11/12/2009/MS115-01
2
Historical Product Development Life-Cycle
Systems View
StructuredSub-SystemSpecifications
SystemSpecifications
System Co-ordination
RequirementsAnalysis
Configuration Change Control
Acceptance Criteria
CustomerRequirements
Sub-System Design Integration by Area/Zone
Procurement Long Lead - Vendor Agreements - Call
Offs
What the Customer Wanted
In-ServiceSupport
Manufacture Assembly by Area/Zone
AcceptanceTrials
Test Commissioningby System
3
Historically Stand-Alone Sequential Processes
Are they finished yet?When will we get the
drawings?Is there anybody listening?Is there
anybody there?
4
The Old Shipyard Way Over the Wall
Inefficiency during transfer of knowledge and
understanding
Understanding whats gone before
Iterations

• Information was not effectively shared, resulting
  in physical rework
• Market pressures forced reduced Design Build
  Timescales

5
Organisation

• Programme Based
• Prime Contract Organisation
• Fixed Price
• Multi-disciplined Design and Build Teams
• Concurrent Engineering
• Shared Data environment across all sites
• Design and Build
• Engineering Directorate
• Design support to programmes
• Development of Processes and Systems
• Resource development and deployment
• External Design related Contracts
• Research and Design Related activities

6
Product Development Life-Cycle BAE SYSTEMS Marine
Ltd
Safety Hazard Logs Connection Details Test
Commissioning Documents Support,Reliability
Maintenance Records Technical Manuals Datum
Pack Trouble Reports etc
Stage 1
Stage 2
Stage 3
Stage 4
Stage 5
Stage 6
Stage 7
Stage 8
Stage 0
Initial Design Concept Feasibility System Design
Sub-system Design Primitive Modelling
Spatial Integration Detail Modelling
Engineering Outputs to Production
Installation Outfit
Test Commission
Parts Manufacture
In-Service Support
Disposal




Procurement Long-Lead Items -- Vendor Agreements
-- Call-Offs -- Spares
KEY
Tollgate
Product Definition
7
Engineering Process Model - LM05/05
ACCEPTANCE
START
Manage Systems Engineering
Provide Specialist Support (ARM, Safety,
Operations, ILS Etc)

ISS
Determine Requirements
DESIGN for SUPPORT MANAGEMENT SERVICE
Secure Acceptance and Certification
Perform Functional Analysis
ELECTRONIC DATUM PACK MANAGEMENT SERVICE

SUB SYSTEM ENGINEERING AND IMPLEMENTATION
Support Higher level Tests (trials)
MAINTENANCE MANAGEMENT SERVICE
Design System And specify/procure Sub
Systems
STOCK MANAGEMENT SERVICE
Integrate and Test System
Create Candidate Solution Concepts
PROVISIONING MANAGEMENT SERVICE
DESIGN CHANGE/UPGRADE MANAGEMENT SERVICE
(Stage 0)
(Stage 1, 2 3)
(Stage 4)
(Stage 5 6)
LIFECYCLE COSTING MANAGEMENT SERVICE
Harmonise Sub System Implementations
(Stage 7)
Perform System Analysis
8
Stage 0 Product Development Life-Cycle Definition
9
Stage 1 Product Development Life-Cycle
10
Stage 1 Sub-System Design Primitive Modelling
11
Stage 2 3 Product Development Life-cycle
FABRICATION/NAS
SHEET METAL/SHOPS
SMITE
DDH
OUTFIT
SLIPWAYS
12
Stage 2 Integration by Area (Space and Level of
Detail)
13
Stage 3 Outputs to Production
14
Stage 3 into Stage 4 Manufacture and Assembly
15
Product Development Life-cycle Dependencies
16
Key Success Factors

• Satisfactory Design Validation of Stage 0
• Build Strategy
• Detailed planning and integration
• Requirements Capture and Management
• Appropriate System Partitioning
• Functional Analysis
• Transverse requirement management
• Controlled Design Reviews
• Successful Tollgate entry and exit between all
  stages
• Facts Based trade-offs

17
Working Towards A Common Approach
Integrated Processes, Measures and Systems
Processes Best Practice
Data Systems Architecture
Measures Norms
18
Internal Customer Perceptions

• Processes
• Global understanding
• Ownership
• Management
• Effectiveness Measures
• Measures
• Not uniformly applied
• Unclear
• Ownership

19
Internal Customer Perceptions

• Data
• Understanding of Product Database
• Data structures Complex
• Data categorisation
• Systems Architecture
• Ability to absorb
• Extensive Support and training
• What to use when

20
Internal Customer Perceptions

• Basics are sound (Stage 0, 1, 2 and 3) need to
  concentrate on making it work and how best to
  apply and operate.
• Education and Awareness
• Ownership
• Compliance Audits
• Review Refresh
• Hierarchy
• Touch Feel

21
Form and Content Touch and Feel

• Written in QA speak - not for Engineers
• Documents seen as an evil- for audit only
• Process content of variable quality

22
Proposed Documentation / Information Structure
23
(No Transcript)
24
Working Towards - A Common Book Approach

• Common set of Processes, Measures Systems
• Ownership of Processes, Measures Systems with
  knowledge and area of expertise
• Check applicability and appropriateness
  refresh
• Monitor compliance usage and content
• Taking the Service Level Agreement that step
  further!

25
Working Towards - Common framework to support
each Project (Taking the Service Level Agreement
that step further)

• Processes Best Practice
• Applications CVmacs
• System Data Architecture
• Measures
• Training
• Compliance Checks
• Change Request, Implementation Management
• Customer Charter
• Common Framework Configuration Control

26
Questions
Any Questions?