Workshop Overview and Introduction

1
Workshop Overview and Introduction

• Hans-Peter.de.Koning_at_esa.int
• (ESA D/TOS-MCV)
• 9 April 2002

2
Topics

• Relevant open standards
• Managing user expectation
• Technology Readiness Levels
• Understandability of standards
• Importance of implementations, test suites and
  toolkits
• Overview of workshop programme
• Questions for round-table
• Organisational issues

3
Relevant open standards (1)

• Data oriented
• Process oriented
• Discipline oriented
• Industrial domain specific
• Generic ICT

4
Relevant open standards (2)

• Basic ISO standards
• ISO 31 1000 Quantities and units, SI
• ISO 8879 SGML Standard Generalized Markup
  Language

• ISO 10303 / STEP
• EXPRESS and Resources
• AP203 PDM 3D explicit shapes
• AP209 FE analysis
• AP210 Electronic assys (avionics, )
• AP212 Electro-technical (harnesses, )
• AP214 Automotive (AP203 CSG, kinematics, )
• AP221 Process plant (registries, STEPLib,
  multi-language)
• AP232 Technical data packages
• AP233 Systems engineering
• AP237 CFD data
• EACM Part 5x Mathematical basis engineering
  analysis
• PDM schema

• ISO 13584 / PLIB
• STEP-compatible parts libraries

• STEP-based standards
• STEP-TAS Thermal Analysis for Space
• STEP-NRF Network-model Results Format

5
Relevant open standards (3)

• IETF
• LDAP Lightweight Directory Access Protocol

• W3C standards
• HTTP and URI/URL
• HTML XHTML
• XML eXtensible Markup Language
• MathML Mathematical Markup Language
• XSL XSLT XPath eXtensible Stylesheet
  Language and XSL Transformations Path
• XML-Schema
• RDF Resource Description FrameworkSemantic
  Web
• DOM Domain Object Model
• SOAP Simple Object Access ProtocolWeb
  Services based on HTTP and XML
• PNG Portable Network Graphics
• SVG Scalable Vector Graphics

• OMG standards
• UML Information System Modelling
• CORBA OO Distributed Processing
• MDA Model Driven Architecture
• XMI XML Metadata Interchange
• MDTF Manufacturing Domain Task Force

• Web 3D Consortium
• VRML Virtual Reality Modeling LanguageISO/IEC
  14772

• Public domain standards
• HDF Hierarchical Data Format (NCSA)
• NetCDF Network Common Data Form (UCAR)

6
PDE standardisation support in Aerospace Industry

• Aeronautics
• IAQG, SAE, AECMA, SJAC, NATO, ASTM, ISO TC20
• Space
• NASA-STD-2817 Computer-Aided Engineering, Design
  and Manufacturing Data Interchange Standards
  (Issued 1998)
• ECSS-E-10-07 Exchange of Product Data (European
  Cooperation for Space Standardization, WG Draft)
• ISO TC20/SC13 Space data and information
  transfer systems CCSDS Consultative Committee
  for Space Data Systems
• ISO TC20/SC14 Space systems and operations
• General (with large aerospace contribution)
• PDES Inc.

7
Managing user expectation (1)

• Why does it take so long to get working
  solutions?
• Inherently complex must achieve international
  consensus
• Many standards long development lead times
  scarce resources
• Need standards developers with very wide field of
  expertise
• Need software engineers with good feel for
  application domain
• Significant learning curve to use converter /
  data access development kits
• Large (tedious!) validation efforts are essential
• But these are almost always under-estimated

8
Managing user expectation (2)

• Quality exchange solutions require intensive
  validation
• Initial workplans regularly underestimate effort
  needed
• Regularly ambition to do too large a chunk in one
  go
• Where incremental, modular approach would be
  better
• But standardisation procedures are not well
  adapted
• And who keeps the overview across all modules?
• Usually quite a heavy process for standard
  preparation and balloting

9
Managing user expectation (3)

• Too much promised too early want to show
  results
• Need for a clear roadmap
• Need to clearly indicate maturity of standard
  implementation
• Need to manage standards development step by step
• Going through the complete cycle incrementally
• Use feedback from early (limited) implementation
  and validation

10
Incremental development approach
Define / Refine / Extend StandardProtocol
Develop / Upgrade Software Development Toolkit
Develop / Upgrade Converters Test Suites
Validate Converters with Test Suites
11
Technology Readiness Levels (1)

• NASA and ESA use Technology Readiness Level (TRL)
• To define / manage space RD programmes
• Levels 1 9, ranging from initial idea to fully
  robust, validated solution
• Originally for space hardware RD
• Propose adapted version for PDE standards
  software
• Successfully introduced and used in FENET
  programmeFENET a European Commision Thematic
  Network on Engineering Analysis (led by NAFEMS,
  members are 100 companies / institutions)
• Original TRL definitions (for space hardware)
  onhttp//technologyplan.nasa.gov/default.cfm?idA
  ppB

12
Technology Readiness Levels (2) (adapted from
FENET)

• Level Definition for standard / method / tool
• TRL 1 Basic principles observed and reported
• TRL 2 Scope, concept and application domain of
  standard / method / algorithm(s) formulated
• TRL 3 Proof of concept for critical parts of
  standard / method / algorithm(s)
• TRL 4 Standard / prototype tool validated in
  simple representative test cases
• TRL 5 Standard / prototype tool validated in
  comprehensive representative test case suite
• TRL 6 Standard / prototype tool demonstrated on
  representative real world problems
  implemented functionality is complete
  performance / interfacing is solved in principle
• TRL 7 Standard / beta release tool validated on
  representative real world problems
  implemented functionality, performance and
  interfacing are complete
• TRL 8 Robust standard / tool routinely used in
  industrial product development environment
• TRL 9 TRL 8, plus standard / tool fully
  integrated in the industrial product development
  processes

13
Understandability of standards

• Data exchange/archival software developers must
  be able to understand within reasonable time
  what to implement
• How to map standards data structures to those of
  native tools?
• Standards should be designed for implementation
  validation
• As much as possible computer interpretable
  definitions should be used from which the basic
  programming interfaces can be generatede.g. STEP
  EXPRESS (ISO 10303-11), XML/DTDs/XML-Schema, UML
• Must be accompanied by well documented test
  suites
• In STEP the mechanism is in place in principle
  Abstract Test Suite, but not given sufficient
  attention and ease of use
• Test suites should be available through version
  controlled web servers
• Clear, unambiguous pass/fail criteria are needed.

14
Importance of implementations, test suites and
toolkits

• Almost impossible to develop good standard
  without checks from implementation feedback and
  testing
• preferably with different tools in the domain
• In order to make this process feasible low
  threshold access to good quality toolkits is
  essential
• Open source development for (basic) toolkits
  seems very attractive
• Abundant availability of free XML(-related) SDKs
  plays very important role in XMLs successful
  take-up
• STEP is relatively behind in this area

15
Overview of workshop programme

• www.estec.esa.int/conferences/aerospace-pde-2002/p
  rogramme.htm

16
Friday April 12th Birds of a Feather

• Two sessions identified
• Engineering Frameworks Interest Group
  (EFWIG)proposed by Russell Peak and Mike
  Dickerson
• STEP-TAS Thermal Analysis for Spacestatus and
  planning for next half year(chaired by Georg
  Siebes and HP de Koning)
• Any ideas welcome rooms can be made available
• At 1330 tour of ESTEC test facilities

17
Questions for round-table

• Successes with PDE? Failures?
• Most important gaps in currently available
  exchnage
• How make best use of XML / STEP combination
• Format next years workshop?
• Same length? Similar single session programme?
• Candidate cooperation projects?

18
Organisational issues

• Lunch in restaurant next to Newton conference
  room self service, pay with ticket
• Foyer next to Newton reserved for participants
• Some PCs with Internet connection available for
  e-mail checking etc.
• End today Ice Breaker Drinks in Foyer
• Tomorrow evening small excursion to Keukenhof
  and workshop dinner (transport by bus)
• CD-ROM from workshop website including all
  presentations
• All presenters leave copy of presentation with
  me!!
• Will be mailed in May