The document discusses data interoperability challenges in the aerospace and defense industry. It finds that:
- Data exchange takes place less than 50% of the time seamlessly between suppliers and customers due to different tools and formats used.
- Manual interpretation is still the dominant method for "translating" data between systems.
- Improved interoperability through standards like STEP and PLCS could provide significant benefits, according to respondents, but investment in interoperability is currently minimal.
10. Existing Solution
What Solution ASD/AIA found
What is Gap
How is ASD/AIA are working
What is Opportunity
www.beanalytic.com
11. The following information exchange scenarios where identified by the
respondents for future standards development:
Ability to establish Aerospace Conversion Standard
Mechanical and electrical definition throughout product life-cycle (should include
3D
solids, boundary representations, annotations, views)
System definition and simulation models, focusing on bandwidth limitations.
Identity and access management, digital rights and intellectual property
protection.
Extraction techniques that allow abstracted exchange of analytical modeling and
www.beanalytic.com
12. Responsibility for engineering
data interoperability standards
identification, management, and
governance is proactively
managed within their
organization.
Respondents indicate that a
validation means exists within their
company to validate the
translation/conversion of data to
assure integrity of data.
Respondents indicate that they believe that improved
Interoperability of computing systems between their
company and their suppliers and customers would provide
their business substantial benefits.
A majority of the respondents believe that to develop and
maintain the Interoperability of computing systems between their
company and their suppliers and customers, we are currently
investing minimal resources.
www.beanalytic.com
13. Tools and Applications “To Facilitate the
Exchange of Data”
Suppliers and their customers are on the
exact
same page (i.e., using same computing
tools)
less than half the time
Translation tools and formats are applied
very
unevenly
Not in the survey, but probably a reflection
of
their cost and lack of fidelity and
compatibility
with legacy systems
Manual interpretation is still the dominant
data
www.beanalytic.com
14. Data Utilization
Suppliers parse technical data into their own software systems about half of the time—2.95
on 1-5
scale
38% report “most of the time/almost always;” 41% report “sometimes/about half of the time”
Suppliers only sometimes convert/translate data prior to re-use internally—2.17 on 1-5 scale
74% report “almost never/sometimes”
Conclusion: these responses appear to be somewhat contradictory; however, if
“convert/translate” is
interpreted to be electronic versus manual, it supports preponderance of “manual”
conversion
Benefits
Strong agreement that improved data interoperability will provide benefits
83% of respondents characterize potential benefits as “substantial/major”
Conclusion
Overall survey highlights need for improvement; respondents overwhelmingly agree that
such
improvement will provide significant benefits
www.beanalytic.com
15. Summary
Clear recognition that data interoperability is essential
“Seamless” data flow/exchange takes place less than 50% of the time
Suppliers must work with multiple customer exchange systems and
formats
Manual interpretation is the predominant form of data “translation”
Broad agreement that improved data interoperability will provide
significant
benefits to suppliers
www.beanalytic.com
17. Mid 1980s: IGES/PDES Organization (IPO) initiated the
development of a second generation of PDE standard called
Product Data Exchange Specification (PDES).
1988: IPO submitted this standard to the International
Organization for Standardization (ISO), which adopted it as the
basis for STEP (Standard for the Exchange of Product Model
Data).
March 1994: Initial release of the International Standard with
MCAD emphasis.
2001: Second major release with rich features
Today: Other advances in-process
www.beanalytic.com
18. What is STEP
ISO: The overall objective of STEP is to
provide a mechanism that describes a
complete and unambiguous product
definition throughout the life cycle of a
product, independent of any computer
system.
It provides information on the use of
STEP too exchange and archive product
data as well as the ISO standardization
process.
The development and implementation of
STandard for the Exchange of Product
model data (STEP) is dynamic and on-
going. "STEP" is actually a series of
standards, developed by experts
worldwide, under the auspices of ISO
10303, Technical Committee (TC) 184,
Sub-Committee (SC) 4. www.beanalytic.com
27. “If we reach high,
we do so only
because
we stand on the
shoulders
of those who went
before”
(Albert Einstein)
www.beanalytic.com
28. Jotne EPM Technology delivers database technology for implementation of ISO
TC184/SC4 methodology and standards – the Open Data Paradigm.
We need a contractual data interchange specification mandated by client/regulatory
authorities to achieve plug-and-play interfaces with application software.
◦ Involved in STEP since 1986, established our « STEP database DEX Architecture »
around 2000.
◦ Working with PLCS/DEX evolvement since 2001 (NDLO, DNV)
◦ Delivering NDLO PLCS Frigate solution in 2006, Involved in NASAMS II, JSF (NDLO,
DNV)
◦ Delivered PLCS/DEX extended solutions for Simbase (WEAG,LSC), MIMER (NMOD,
EADS), VIVACE (EC FP6, Airbus), Open Concurrent Design Server (ESA, DNV),
Inteligrid (EC FP6, Obermeyer), (US Army)
◦ Joined OASIS PLCS TC October 2006
◦ Working with IAI and buildingSMART initiative to develop and implement Information
Delivery Manual (IDM) as part of ISO 16739 (IFC).
◦ Delivered IFC/IDM solutions to NO, SG e-Government solutions, data warehouse
projects (GSA, Statsbygg, US Navy,
◦ Discussions PLCS DEX implementation with ISO 15926 RDS (NMOD, OLF, DNV)
Background
www.beanalytic.com
30. Interoperability Triangle
ISO 10303-203, 209, 212, 214, 239,
ASD 9300-110
Aeronautics & Space
IFC (ISO 16739),
GML (ISO 19100)
Built Environment
PLCS (ISO 10303-239),
ASD/AIA S1000D,
ADL SCORM
Defense
Object Model specification
ISO 15926-2
Oil & Gas
www.beanalytic.com
32. Aeronautics
Pylon attachment
VIVACE (FP6) led by Airbus
•WP 3.4 Engineering
Data Management
•UC from Snecma – Whole Engine Model
A Fan Blade off analysis, shows critical loads
on the pylon attachment part (“mount”)
Blade off
Whole Engine Model workflow
Application of DEX
Whole Engine Model UC
www.beanalytic.com
33. Space
AO/1-4801
Grid based Distributed
Concurrent Design
AO5062 Space Instrument Design
Modelling in a CE Approach
MULTIMEDIA WALL
WHITE BOARD WHITE BOARD
AMT/
Configuration
Mission
& Op.
CDF
leader
Elec.
Archi.
CAO
BARCO
Customers, internal
board,…
PRINTER
Additional
attendant
:
Experts,
Customers
….
System Gestion
Bord
Mechanisms
Propulsion
AOCS
Operations
Instrument
Splitter
working
desktop
TTC
Thermal
Spare
working
station
MULTIMEDIA WALL
WHITE BOARD WHITE BOARD
AMT/
Configuration
Mission
& Op.
CDF
leader
Elec.
Archi.
CAO
BARCO
Customers, internal
board,…
PRINTER
Additional
attendant
:
Experts,
Customers
….
System Gestion
Bord
Mechanisms
Propulsion
AOCS
Operations
Instrument
Splitter
working
desktop
TTC
Thermal
Spare
working
station
AO/1-4063/03/NL/JA ESA STEP-SPE,
Thermal and Space Environment
Analysis Software Tools and Interfaces
3-11624/06/NL/GLC Open Concurrent
Design Server
• XML and Web services
• PDM (PLCS), CAD and SE Domains
• Reference Data Libraries
• Open and Publicly available
Object definitions by ISO/STEP
• Database
• Input sheet
• Output sheet
• Calculation sheet
• Result sheet
www.beanalytic.com
35. Slide 35
SIMBASE server - a legacy/PLCS portal Simulation-based Acquisition for
IT/NO/UK MOD
Workflow Engine
SIMBASE server
Report layer
feedback
User access control, system administration
Data
Browser
Queries
EXPRESS based
Workflow Manager
(import definition, set up instances)
Rules
Convert
to PLCS
Validate
PLCS/DEX
Mapping
4 5
PLCS/DEX
DB
Populated
PLCS
DB
Merge
model
Validate
result
Rules
Mapping
6 7
Rules
Import
Validate
import
3
2
legacy
EXPRESS
DB
Export
Convert
to legacy
Mapping
3’
Rules
Validate
PLCS/DEX
2’ Extract
model
Query
1’
4’
legacy
specific
Export
3’’
= EXPRESS generic
= legacy specific
= EDM/PDTF function
= Express code
Workflow Participant
(review and perform activities)
data
export/
import
legacy
P21/P28 file
Translator
legacy
DB
company xyz
PLCS/DEX
P21/P28 file
www.beanalytic.com
