IBM Detailed ALM/ELM for Aerospace & Defence overview

IBM ELM for Aerospace and Defense Industry
Speed the delivery of smart air vehicles and systems
Imran Hashmi
SALES LEADER- AI APPLICATIONS
+1-416-788-9101
Imran.Hashmi@ca.ibm.com
HTTPS://HASHMI.CA
IBM Engineering Solutions

• Challenges & Trends in Aerospace/Defense industry
• IBM Engineering platform for Aerospace/Defense
• The A&D demonstrator
• Engineering Lifecycle Management Solution for A&D capabilities
• Deeper Dive: Accelerating Industry Compliance for Aerospace:
• ARP4754 and DO178C
• Summary and additional resources
Outline
2

Today’s A&D Engineering Challenges
Watson / Presentation Title / Date
Technology of smart products is evolving fast and somewhat unpredictable way...
This imposes multiple challenges for the manufacturers
• Dealing with increasing complexity with unpredictable technological disruptions
• Responding quickly to new competitive and defense threat
• Meeting growing industry regulatory demands in areas like safety and security
• More effective supplier/integrator collaboration and complex ecosystems
• Business environment requires effective support of multi-variants programs
Complexity is rising!
Lines of code:
Mars Curiosity rover:
F22 Raptor
F-35 fighter jet:
0.5m
1.7m
24.7m
product engineering has to transform…

Todays engineering practices are challenged to keep up…
Today’s Document centric engineering – Practices based combination of siloed tools and
documents…
4IBM Watson IoT / © 2018 IBM Corporation
‒ Expensive rework due to late discovery of issues
‒ Slow response to bids and change requests
‒ Inefficient supplier collaboration
‒ Non-optimal designs due to early design lock
‒ High costs of regulatory compliance activities
The Science of engineering has evolved
to empower innovation, have you?
Lack traceability, version variance management,
governance and testability results in:
Require
ments
Traceability
Reports
Designs

5
Standards often initially increase project costs
Example: Transition to DO-178B compliance
Typical
DO-178B
Project
Successful
DO-178B
Project
Technical
Project without
DO-178B
• Added 60% -
100% Cost
• Added 25% - 40%
Cost for Initial
Development
• Solid processes
• Experienced
Team
+25-
40%
+60 –
100%
Source: Avionics Certification – Vance Hilderman and Tony Baghai ISBN-10: 1885544332
(avionics publications)
Common transition issues
• Inadequate formal plans or not following them
• Inadequate level of detail and process for Requirements
• Inadequate or high manual effort for Requirements Mgmt
and Traceability Mgmt
• Improper Tool Qualification (too much or too little)
• Weak process and checklist management
Extraexpenseto
achievecompliance

Companies already face
the challenges of increasing
complexity……
IBM Engineering / © 2019 IBM Corporation
News reports:
F-35 Fighters will cost $22B more than
expected – 24 million lines of code proving
difficult
189 People Killed in Lion Air Flight 610
Reuters sources claim a software issue is
suspected in Airbus A220 engine blowouts
Computer code in a typical plane
has grown 40% in past decade
6

Industry vision: Digital Engineering initiative by
US Department of Defense
“conduct engineering in more integrated virtual environments
to increase customer and vendor engagement, improve threat
response timelines, [..], reduce cost of documentation and impact
sustainment affordability.
Such engineering environments will allow DoD and industry
partners to evolve designs at conceptual phase, reducing the
need for expensive mockups, premature design lock, and
physical testing.” 1
1. DoD Digital Engineering Initiative:
https://www.acq.osd.mil/se/initiatives/init_de.html
7

IBM ELM for A&D
End to end engineering lifecycle management optimized with
AI
ELM enables a digital process for product
engineering
 Higher velocity and agility with high quality –
digital transformation of engineering
 Support industry practices and regulations -
Compliance
 Effective supplier management
 Foster consistency and constant improvement -
agility
ELM for A&D specializes ELM with
 Reference implantation demonstrating 15288
lifecycle processes (“Aviary”)
 Industry templates for standards compliance
 DO178, ERP 4754a*

Engineering Lifecycle Management Solution Platform
Capability
Analysis
System
V & V
System
Test
Operationa
l test
System
Specification
Operations
and
Maintenance
Deploy
Component
test
Electrical /
Electronics
Design
Mechanical
Design
Lean Software
Engineering
Traceability and Impact Analysis
Across the and through the V
IBM
Engineering
Lifecycle
Management
Systems of
Systems
Operational
Analysis
System
Design
Component
Design
(HW/SW/Mech)
Implementation
Requirements
management
System Analysis
& Design
Component
Test Management
System
Test Management
DOD/OEMs
Mil
Defense Suppliers
Software Development CI/CD
Mission Analysis
ERM
DOORS Next Generation
RQA
Requirements Quality
Assistant Rhapsody
& Model Manager
Systems edition
Rhapsody
& Model Manager
Systems edition
Rhapsody
Test conductor
Engineering Test
Management
(ETM)
Engineering Test
Management
(ETM)
Engineering
Insights
ENI
Reporting Service
Publishing Engine
Engineering
Workflow
Management
(Build+SCM)
Rhapsody
& Model Manager
SW edition
Engineering Test
Management
(ETM)
Engineering
Workflow
Management (SCM)
Planning, Tracking, Change

ELM for Aerospace/Defense Supported Practices
Technical processes
 Mission Analysis
 Managing Requirements
 System Analysis & Architecture
definition
 Verification and validation
 Operation & maintenance
INCOSE 15288 SE processes
Tech. Management processes
 Configuration & data management
 Variant Management and PLE
 Change management - Analyzing the Impact of
Change
 Planning and tracking – Scaled agile support
 Quality assurance – digital reviews

IBM Engineering Lifecycle Management: transforming smart products engineering
11
Digital continuity
Enable cross discipline digital threads to
streamline impact of change analysis and
standards compliance
Early design verification
Verify at all stages of the product lifecycle
with model based engineering and digital
twins
Scaled agility
Effective agile engineering with digital
governance, real-time feedback, team
collaboration, and continuous delivery
Data and configuration
management
product line engineering
Reuse engineering data in parallel
development and product variants
Engineering insights with AI
Use AI and advanced analytics to improve
quality and support engineering decision
making
Efficiency
Correctness

A&D reference implementation: The Aviary surveillance
System
Bird Control
Bird Watcher
Hummingbird
Script+Videos:
https://ibm.box.com/s/tsw6olp32aiipbl4w5565l6lrzdh
rvln
Cloud instance:
https://ukiot.clm.oncloudone.com/rm/web?expandProje
ct=https://ukiot.clm.oncloudone.com/rm/rm-
projects/_QhSGcCMJEem4vZIQTRKFzA
User: Aviaryvisitor
Pass: Aviary01
 Designing the UAV system – Systems Engineering
 Specifying the requirements
 Planning (SAFe for complex solutions)
 Requirements analysis (MBSE)
 Architecture and allocation (MBSE)
 IV&V: test planning
 4754 alignment/safety analysis**
• Developing of the software (Avionics)
 Handoff from SE to software
 SW planning and delivery (SAFe/agile)
 DO178 work products**
• Integration with HW design for the UAV (via PLM)**
• Change process
 assess impact of change
 Delivering the change
• Managing variants
 Creating a new variant
 Updating changes across

Digital Continuity: realizing digital threads
• Understanding all relationships
across lifecycle disciplines and
artifacts
• End to end traceability and data
consistency
• Impact analysis
• Traceability management is a
foundation to most standard
engineering industry practices
Digital continuity
Enable cross discipline digital threads to
streamline impact of change analysis
and standards compliance
COLLABORATIVE ENVIRONMENT
LINKED
DATA
ARCHITECTURE
MBE T&E Manufacturing Training O&S
Model-Based
Systems Engineering
Model-Based
Manufacturing
Model-Based
Supply Chain
Model-Based
Design (Hardware)
Sustainment and IoTModel-Based
Software Engineering
S T O R A G E
LINKED TOOLS
AND
PROCESSES
Blended Virtual and
Physical Continuous I&T
ENDOF
LIFE
SUSTAINMENT
MBM
MDSD
MBD
MBSE
CONCEPT
MBSE = Model-Based Systems Engineering
MBD = Model-Based Definition
MDSD = Model-Driven SW Development
MBM = Model-Based Manufacturing

Digital threads essentially implement domain information models
Traceability model required by DO178 DALs
Example: DO 178 required information
model
Required Artifact types
Relationships between artifacts
AKA Traceability

Analysis and Design
Models
Requirements
ManagementTest Management
Workflow
Management
IBM ELM Platform High Level Architecture
• Standards based
Electrical Design PLM
Multi-domain
Simulation
Lifecycle
Graph
(LQE)
Lifecycle
Links
Global
Configuration
Management
Software implementation
• End to End
traceability with Link
• Central analytics
based on knowledge
• Federated
configuration
Analysis
Reporting
Metrics
Systems Engineering
Product Line
Engineering
Work Management
HW Disciplines

Impact analysis based on lifecycle graph
Update from RELM

Hkjhkjh
Integrating engineering disciplines
Systems Engineering
SW
Engineering
Electronics Mechanical
HW Disciplines/PLM
Handoff

ELM vs. PLM approaches for the engineering lifecycle
18
ELM PLM
Req Mgmnt
Change Mgmnt
Conf. Mgmnt
MBSE
Test Mgmnt.
SW development
SCM
Agile management
ECO
BOM
MCAD
ECAD
EDA
Manufacturing
• Originated from ALM
Software practices
• Agile
• Concurrent
• Federated
approach, based
on open and
modern integration
standards
• Originated from
PDM/mechanical
engineering
• Formal/”high ceremony”
• Serial
• Centralized approach,
proprietary APIs
ELM integrates with PLM where it manages HW artifacts and manufacturing

Air Vehicle
Camera
Rotors
Requirements
Test
Air Vehicle
<<B1>>
Control
Unit
UAV Sys
PLM design structure
Integrating HW development - ELM-PLM
Viewer
ELM Specification
R1
R2
Sys ECR HW-ECR
ELM
PLM

Engineering data management: Organize and consistently manage
engineering assets across the lifecycle with global configuration management
Consistently manage engineering data across product levels and
subsystems
How to baseline data across disciplines: requirements, design,
V&V
How to systematically reuse engineering assets across different
variants and programs?
GCs are based OSLC configuration management standard
- An open protocol also to 3rd party products!!!
Cfgm
UAV
stream
A GC
UAV
RM Stream
UAV
AM Stream
UAV
QM stream
Test
Design
Requirements
JTS
UAV
System
Organizing Configurations of Engineering Data based
On Logical Product Breakdown Structure
Air Vehicle
Avionics CoMMS
Ground Stn.
UAV
RM Stream
Model P
AM Stream
Model P
QM stream
AV
Requirements
C Architecture
PT Test
PT Code
Comms
Requirements
Architecture
Test
Code

Product Breakdown Structure
Central engineering data management for
the lifecycle
The systems engineering is organized under
a central structural breakdown using ELM
GCM
Each logical node contains SE artifacts and
sub nodes
Partitioning data by responsibilities
The breakdown structure of the UAV system

• Consistent evolution of data
across engineering disciplines:
common baselining
• Manage platform assets across
variants and programs
• Reuse all engineering assets from
the platform: requirements, design,
implementation, test
• Manage changes across variants
and programs
• Harvest innovation in programs for
reuse across the product lines
Product line engineering and reuse
22
Platform
Assets
Variant 1
Variant 2
Variant 3
Time
Strategic reuse and product
line engineering
Support configurations of
engineering data for reuse across
projects and products for efficient
parallel development and variant
managementTestDesignRequirements Code

24
Components are collections of artifacts - for example – a model
Artifacts have versions
Each configuration determines the version for each artifact
Artifact versions can be shared across configurations
Each Lifecycle tool should support components configurations of its artifacts
Managing variants with configuration branches
24
A5.2
A2.1
A4.1
UAV [platform]
A3.1
A1.1
A5.3
A2.1
A4.2
UAV [Customer A]
A3.1
A1.1
A5.3
A2.1
A4.2
UAV[Customer B]
A3.1
A1.1
A6.1 A7.1
Common element
Modified element
Added element
Models
Code
Test
Requirements

Systems engineering artifact reuse across programs and variants
• Federated configuration management
enables baselining and reuse of
configuration items across all lifecycle
disciplines
• Configuration items are organized in
hierarchical configurations
• Configuration items can have variants to
realize variability across programs and
products
• Configuration items can be reused across
programs and products
Aviary Base
Aviary
w
Payloa
d
1 2 3 40
10
Aviry Base
Hummingbird B
avionics 1.1Rotorsv3.1
B Watcher 1
Variant
Hummingbird b
1 2 30
10
Hummingbird P
Avionics v1
Avionics v2
1 2 30
10
Aviary Payload
Hummingbird P
Avionics 2.1Rotors v3.1
B watcher 1
Common
Example: component reuse across a UAV
system (Aviary) variants
Aviary
stream
Aviary
RM Stream
Aviary
AM Stream
Aviary
QM stream
test
architecture
requirements
GC
repository

IBM
Example: multiple product configurations and evolution
of components
Components can be managed like
smaller products
– Having their own baselines
– Developed by different teams and
schedules
Component teams and product
teams
Model X
Model Y
1 2 3 40
10
Model x.1
Engine v1.1
Pump 1.1Spark v3.1
Gear v2.1
Engine v1
Engine v2
1 2 30
10
Pump v1
Pump v2
1 2 30
10
Model Y.1
Engine v2.0
Pump 2.1Spark v3.1
Gear v2.1
Components are also products that are used by
larger products

Early design validation with Model Based
Engineering
• How to verify the system
specification before actual
implementation?
• How to assess system architecture
before committing to
implementation?
27
Early design verification
Verify requirements and
design at all stages of the
product lifecycle with model
based engineering and digital
twins
Cost of correcting an error found in
integration may be two orders of
magnitude (100x) more expensive than
identifying it during specification!
System
Requirements &
Architecture
Subsystem
Requirements &
Design
Implementation
SW & HW
Module and
Subsystem Integration
& Test
System Integration
and Acceptance Test
?
?
Early verification
Early verification

Apply MBSE across the lifecycle in the Aerospace and
Defense domain
Capability
Analysis
System
V & V
System
Test
Operationa
l test
System
Specification
Operations
and
Maintenance
Deploy
Component
test
Electrical /
Electronics
Design
Mechanical
Design
Lean Software
Engineering
Traceability and Impact Analysis
Across the and through the V
IBM
Engineering
Lifecycle
Management
Systems of
Systems
Operational
Analysis
System
Design
Component
Design
(HW/SW/Mech)
Implementation

IBM MBSE solution core capabilities
that deliver the value…
Create
Trace
Analyze
Validate
Automate
Deliver
Model
Execution
&Simulation
Team &
Stakeholder
Collaboration
Model Based
Testing
Standards based
Modeling
And DSL
Software
Automation
Traceability
with lifecycle
disciplines
Early validation and
agility
Engineering integrity
Effective
Collaboration
Automation
IBM Watson IoT / © 2018 IBM Corporation 29

Model Management and Collaboration
Rhapsody Model Manager
Model configurations
 Model web services
OSLC REST APIs
Web Client
Web Client
Rhapsody Client Rhapsody Client
Design
Collaborate
Manage
Link
Collaborate
Link
Collaborate
Link
Design
Collaborate
Manage
Link
Change
Management
Requirements
Management
Test
Management
OSLC
‒ Model management and
lifecycle integration and
traceability to other disciplines
 OSLC service
‒ Collaborative working on a
model by multiple stakeholders
‒ Parallel development with
multiple streams
‒ Model baselining and version
control
‒ Baselining models together with
all other lifecycle artifacts
‒ Distributed model development
across teams and geographies!
30
Traceability
with lifecycle
disciplines

Integrated requirements traceability

32
Models execution verify the functional and logical specifications
‒ Low fidelity execution verify the
logical correctness of the
specification
‒ Finding design errors during
physical system integration is
costly and inflicts significant delays
‒ Facilitate agility throughout
iterative elaboration and
verification
‒ High fidelity simulation involves
models of physical plant and
performance for quantitative
assessment using technologiesIBM Watson IoT / © 2019 IBM Corporation

MBSE – Small “V” vs Big “V”
33
Product Development Process
Systems Engineering
Virtual Multi-Disciplined Engineering
Requirements
Capture & Analysis
implementation
Implementation
& Unit Testing
Deliver and Deploy
System Validation
and Acceptance
Deploy and Monitor
Physical Multi-Disciplined Engineering
System
Acceptance
Systems
Analysis & Design
Detail
Design
Virtual Module
Integration & Test
Virtual System
Integration Testing
Continuous Feedback Loop
Simulation
Optimization
Module
Integration & Test
(Sub-)System
Integration Testing
verification
verification

Model Validation – model
based testing
• The system architecture is
verified against the
requirements
• Requirements are
elaborated as use case
scenarios
• Rhapsody Test Conductor
automates execution of test
scenarios against a test
architecture
IBM Watson IoT / © 2018 IBM Corporation
Use case scenarios
Execution of a scenario

Scaled Agile Project Management & Governance
Applying lean/agile principles for large
multi-disciplinary projects
• Effective management of team of
teams
• Leveraging MBSE
• Supply chain coordination
• Continuous visibility into project
status and KPIs
• Implementing the Scaled Agile
Framework (SAFe) for large
solutions
Scaled Agility
Enable effective agile
engineering with digital
governance, real-time feedback,
team collaboration, and
continuous delivery
Several A&D enterprises have
already deployed SAFe!

Advanced agile planning support… for smarter decision making
Team of teams planning

Example: Aviary top solution epics

Optimize engineering with AI
Inject automation and intelligence across the engineering
lifecycle
z
Engineering Insights with
AI
Use AI and advanced
analytics to improve quality
and support engineering
decision making
• Supporting decision making
• What is the impact of change
• Harnessing AI to analyze and
provide insights
• Producing all necessary evidence
for engineering regulatory
compliance
Requirement quality and
structuring
Defects Classification
Model Construction
Testplanning
Advisor
Automted
escallation
Reuse assistance
Assess risk of change
Engineering Process
Advisor
Intelligent
impact analysis
Test creation
Market
Analysis
System
V & V
System
Test
System
Requirements
System
Design
Deploy or
Release to Mfg
Customer
Requirements
Operations and
Maintenance
Implementation
Component
test
Component
Design
Electrical /
Electronics
Design
Mechanical
Design
Lean Software
Engineering
IBM Engineering
Lifecycle
Management

IBM Requirements Quality Assistant
• Removes risk and ambiguity in the requirements authoring
phase out-of-the-box by using AI (Watson Natural
Language Understanding)
• Pre-trained to detect key quality indicators designed to be
consistent with the INCOSE Guidelines for Writing Good
Requirements
• Authors receive coaching from Watson to improve the
quality of the requirement as it is being written
Enterprise benefits (400 engineers example)
• Reduce the cost of defects by 60% to save $3.9M
• Reduce cost of manual reviews by 25%
• Retain engineering expertise for junior engineers
New Watson capability embedded inside DOORS Next Generation (DNG)

Best Practice Guidelines
INCOSE Guide for Writing Requirements
Written by a worldwide cross-industry team
GE, Madrid Technology University, Harris
Corporation, Systems Engineering
Global, Airbus, Continental AG, Motorola,
NASA, Loughborough University and more
Rules reflected in the Systems Engineering
Handbook and ISO 15288
40

IBM Requirements Quality Assistant
• Grades requirements against a criteria that was designed to
be consistent with the INCOSE Guidelines for Writing Good
Requirements
• Pre-trained to detect 10 quality issues
– Unclear actor or user
– Compound requirement
– Negative requirements
– Escape clause
– Missing units
– Missing tolerances
– Ambiguity
– Passive
– Incomplete requirements
– Unspecific quantities
• Add to the list of quality issues or do deeper training through a
3 week services engagement with IBM services team
41

Accelerating Aerospace and Defense regulatory
compliance with IBM ELM
Aircraft Safety: ARP 4754
Airborne SW development : DO-178C

A&D safety: a stack of
guidelines

Testing
Requirements
Design
Workflow
MEC
ELM Automates A&D compliance through a set of domain
templates, reports, and guidance
Engineering
Lifecycle
Management
with AI
Organization Concept (SAFe)
…built on one cross domain Data & Link Model
ETM Assets
Reports (JRS, PUB, ENI)
Process & User Guidance
DOORS Next Template
Rhapsody Profile
EWM Work Item Types System
Requirement
+ Risk
+ Feasibility
+ Impact
+ …
Integration
Test
System
Architecture
+
+ …
Review
+ Approver
+ Finding
+ …
1
2
3
4
5
6MEC

IBM ELM for SAE ARP-4754A (Sys. Dev. & Req.)
Aerospace Recommended Practice 4754a - development processes which support certification of Aircraft systems.
TableObjective text Outputs IBM Solutions
2.1
Aircraft-level functions,
functional requirement,
functional interfaces and
assumptions are refined
*List of Aircraft level
functions
*Aircraft-level
Requirements
Requirements Management,
Model Based Systems
Engineering, Traceability
(DOORS/NG, Rhapsody,
Rhapsody Model Manager,
Rational Publishing Engine)
2.2
Aircraft functions are allocated to
systems System Requirements
2.3
System requirements, including
assumptions and
system interfaces are defined. System Requirements
2.4
System derived requirements
(including derived safety-related
requirements) are defined and
rationale explained. System Requirements
2.5System architecture is defined. System Design Description
2.6
System requirements are
allocated to the items. Item Requirements
2.7
Appropriate item, system and
aircraft integrations are
performed. Verification Summary
Aircraft and System Development Process and Requirements Capture- Air worthiness certification is a major
challenge and cost factor for A/C
manufacturers
- ARP 4754 ensures product quality and
safety
- acknowledged by the certification
authorities as an acceptable means of
compliance
- Recommends use of MBSE techniques
aligned with D0-178 C and DO-331

DO-178 B/C Considerations for Airborne SW development
• All SW design items need to be classified with
assurance levels (DAL)
• Higher DALs require increasingly increasing number
guidance compliance
Traceability model required by DO178 DALs
DO178 Design assurance levels

Impact of MBSE on ARP 4754A and DO-178 C
• ARP 4754A advocates use of DO-178 C and MBSE development for Systems and SW test
• DO-331 is supplement to DO-178 C defines how to do Model Based test and verification
• Mapping to lifecycle processes
Process that generates
lifecycle data
Model-Based Design
Example 1
Model-Based Design
Example 4
Model-Based Design
Example 5
System Requirement
and System Design
Processes
Requirements allocated
to software
Requirements from which
the model is developed
Software Requirement
and Software Design
Processes
Design Model Design Model
Design Model
Software Coding
Process
Source Code Source Code Source Code

ELM Tools Mapping to DO-178 B/C and DO-331
• Configuration Management Overarching Process
• Engineering Workflow Manager
• Reporting
• Jazz Reporting Services
• Reporting Engine
• Engineering Insights (RELM)
DNG
ETM
Rhapsody/RMM/TC
EWM

IBM Engineering Method Composer Practice Library for
DO-178
• Practices for DO-178 B and C, supplemented by
• DO 331 MDD
• DO 332 OOT
• Practice contains
• DO178 Objectives
• Software development process with mappings to objectives
• Tool mentors
• Published Website
• ISDP 178 mapped to DO-178 B/C objectives
• Checklists to capture compliance
• Microsoft Word templates for process documentation, for
example PSAC
• Process Templates in EWM
• Work item templates mapped to DO 178 B/C objectives
• Tracking compliance with the objectives

IBM Rhapsody Kit for DO-178B/C
5
• Overview: describes the content of the Rhapsody workflow qualification package
• Rhapsody Reference workflow : provides an exemplary workflow for modelling,
code generation and verification in safety critical
• TestConductor Workflow: describes testing activities and objectives
• TestConductor Safety Manual: provides additional information for using TC in
safety related development
• PSAC for SMXF
• SXF/SMXF frameworks
• SXF/SMXF validation suites
• TestConductor Validation Suite (optional)

Mapping of tools to ARP 4754A
DOORS/DNG & RHAPSODY RHAPSODY
QUALITY MANAGER, TEST CONDUCTOR
AND RHAPSODY

ARP4754 Integral Process
5.1 Safety Assessment
5.2 Development Assurance Level
Assignments
5.3 Requirements Capture
5.4 Requirements Validation
5.5 Implementation Verification
5. 6 Configuration Management
5.7 Process Assurance
5.8 Certification & Regulation
Authority Coordination
- Core process for the
development at
- Aircraft
- System
- Subsystem
- HW/SW levels
Safety Analysis
Rhapsody (Dependability profile)
Medini Analyze
Systems Engineering
Requirements Management
Rhapsody, Test Conductor
Quality Management
Process
Management
CCM, Methods
Workflow
Management
Method Composer

Safety analysis profile based on 4761 (for ARP 4754 DO178)

SafranEngineimplementsDigital“V”Lifecycle withIBMELM
Change
Management
Configuration
Management
Documentation
Management
Operational
Analysis
Functional
Architecture
Define System
requirements
Subsystem &
Component
Specification
Physical
Architecture
Manufacture - Buy - Reuse
Imperatives:
• Achieve ARP 4754 compliance
• Quicker time to market

Axel Mauritz
Head of Domain Virtual
Product Engineering,
Airbus Group Innovations
Genius of Things event
Munich, Feb 2017
Multisystem,
multidisciplinary navigation
Understand impact of changes
Consistency between viewpoints
“If a problem is discovered with a plane, we need the digital thread that links throughout the
product lifecycle so we can explore whether the problem is due to improper service, a poor
manufacturing process, or a design flaw. Our engineers need to understand how the plane will be

MBDA, a European defense company, provides its transnational staff
with a common platform for modeling, testing and sharing highly
complex designs and design protocols.
60+ months
Reduced typical system
design time from
18 months
to
Business problem: Needed to improve complex engineering design collaboration and cycle time across geographical borders
Solution: A model-based systems engineering platform across widely distributed design and engineering teams to analyze and
communicate software, mechanical and electrical requirements
“We’re now able to define and model all the requirements of a complex missile system very early in the development process.
This differentiates our delivery capabilities in a highly competitive global marketplace.”
— MBDA executive
while enabling design team
collaboration across geographies
59

Naval Group – engineering lifecycle framework
based on ELM and OSLC

F-35 mission systems development is driven by Rhapsody models
The F-35 requirements are specified using DOORS, and
the Mission Systems software is designed and generated
from Rhapsody
https://www.reuters.com/video/2018/02/06/f-35-rules-the-skies-at-uk-
airshow?videoId=391328378&videoChannel=118264
61

Summary: IBM Engineering for A&D
 Implement “digital engineering” for effective complex systems engineering
 Applying MBE, AI, and analytics
 Streamline Stakeholder/Supplier collaboration with Advanced requirements
management and support for defense architecture frameworks such as
DoDaf/MoDaf/NAF
 Accelerate Industry standards compliance through tool features, best practices and
templates
 ARP 4754
 DO-178C
 Foster Variant management and concurrent workflows with Global configuration
support across the engineering platform
 Extend to feature based PLE-at-scale with partner solutions Pure Systems and Big-
Lever
 Automate certifiable Embedded SW implementations compatible with industry
guidelines
 DO-178B/C

Questions?
Imran Hashmi
SALES LEADER AI APPLICATIONS
+1-416-788-9101
https://hashmi.ca
Imran.Hashmi@ca.ibm.com

IBM Detailed ALM/ELM for Aerospace & Defence overview

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a IBM Detailed ALM/ELM for Aerospace & Defence overview

Similar a IBM Detailed ALM/ELM for Aerospace & Defence overview (20)

Último

Último (20)

IBM Detailed ALM/ELM for Aerospace & Defence overview