Ap239 Product Life Cycle Support Managing Product Support Information from Concept to Disposal

1
Ap239 Product Life Cycle SupportManaging Product
Support Information from Concept to Disposal

• John Dunford
• PLCS, Inc. / Eurostep Ltd
• SC4 Liaison Plenary
• 12 Mar 03, San Diego

2
Ap239 Product Life Cycle SupportIntroduction

• A joint industry and government initiative to
  accelerate development of new standards for
  product support information
• An international project to produce an approved
  ISO standard within 4yrs commenced November 1999
• PLCS will ensure support information is aligned
  to the evolving product definition over the
  entire life cycle
• PLCS extends ISO 10303 STEP - the STandard for
  Exchange of Product model data

www.plcsinc.org
3
Ap239 Product Life Cycle SupportWhy is it
needed?

• Product and Support Information is a major
  business asset
• Value can be added by
• Write once use many times e.g. re-use of the
  Product Model for technical documentation
• Managing product and support information as a
  single assured source
• Automate work planning and resource provision
• Automate capture of feedback, as work proceeds
• However there are risks
• Understanding do I understand the context in
  which information is provided?
• Change Management do I have the right version?
• Can I avoid lock-in to proprietary systems or
  formats?
• Information standards unlock the value and
  help manage the risks

4
Product Life Cycle Support (PLCS)Who will use it?

• Shaded area represents main industry focus for
  PLCS
• Common Attributes
• Complex high value products with long life cycles
  and demanding in-service support requirements

Military Ship Commercial Ship Military
Aircraft Commercial Aircraft Submarine Power
Plant Oil Production Rigs
Business Aircraft Special Ind.Equipment Telecom
Switchgear Aircraft Engine Avionics
Missiles Satellites Ordinance
High
Power Turbine Mining Equipment Trucks Landing
Gear Elevators Process Plant Army Vehicles
Automobiles Transmissions Special M/c
Tools Agricultural Machinery Engines
Computers Leisure Vehicles Radio/Radar
Medium
Product Complexity
Pumps Valves Filters Brakes
Boats Lawn Equipment Rail Cars Transformers
Domestic Appliances Consumer Electronics Bicycles
Exhaust Systems
Low
Medium
High
Low
Support Complexity
5
Ap239 Product Life Cycle SupportApplications of
interest
CM Data
Operational Objectives
CM Data
CM Data
CM Data
4. Maintenance Management
14 Defects Failure Reporting
9. Product Data
12 Depot Maint Mgmt
5. Requirements Management
Functional Requirements
Defects and Failures
CM Data
Maintenance Mgt Data
1. Support Data
Support Data
3. Stock Mgmt
13. Distribution, Transportation
7. FMECA
Design Data
FMECA Results
LSA Data
Support Data
Distribution Data
LSA Data
2. Maintainers Viewing Tool
6. LSAR
8. CAD
10 IETM
11 Parts Supplier Database
Part Data
LSA Data
Tech Pubs Data
Support Data
6
Ap239 Product Life Cycle SupportPLCS will enable
cost effective information exchanges
1. Support Data
5. Requirements Management
2. Maintainers Viewing Tool
3. Stock Mgmt
6. LSAR
4. Maintenance Management
7. FMECA
FMECA Results
LSA Data
Maintenance Mgmt Data
Maintenance Mgmt Data
Support data
Functional Req.
Part data
PLCS compliant information exchanges
Tech Pub Data
Defects Failures
Maintenance Mgt Data
Design Data
Design data
Distribution Data
Parts Data
8. CAD
9. Product Data
10 IETM
11 Parts Supplier Database
13. Distribution, Transportation
12 Depot Maint Mgmt
14 Defects Failure Reporting
In future, support system integration will be
easier to implement
7
Ap239 Product Life Cycle SupportUnique Value
Proposition

• International Standard for product support
  information - based on ISO 10303 STEP (AP 239)
• Complete product lifecycle from concept to
  disposal
• Single source of assured product support
  information
• Data independence - Processes, Systems, Format
• Interoperability across enterprises and systems
  through
• Standardization of semantics for product support
• Integrated suite of data models for data
  exchange and information sharing
• Utilization of ISO STEP standards, methods and
  tools (incl XML/XSTL)
• Extensibility and tailoring through the use of
  Reference data libraries

Customers, Contractors and Software Vendors
working together to develop and implement a
neutral data exchange standard for product support
8
Ap239 Product Life Cycle SupportPLCS, Inc.
Membership
9
PLCS, Inc. Program

• Year 1 - Nov 99 to October 2000
• Develop and document process models, and
  associated process definitions, for life cycle
  support processes
• Year 2 - Nov 2000 to October 2001
• Complete requirement capture (1500)
• Identify data modules (140) and exchange sets (
  30 CC)
• Develop initial technology demonstrators
• Year 3 - Nov 2001 to October 2002
• Develop foundation modules ( 90 in STEP Module
  Repository)
• Integrate to develop UoF and Conformance Classes
  modules
• Test modules by mapping real data sets
• Ballot as Technical Specifications
• Year 4 - Transition to Implementation
• Compile AP239 as Draft International Standard
• Publish test results, usage guides and reference
  data
• Industrial testing, vendor test rallies and 1st
  phase implementations
• Promote widespread use of standard and establish
  user group

12,000 man days International Travel 10M
10
PLCS, Inc deliverables

• A new vision for life cycle support
• A terminology dictionary
• An illustrative process model (AAM)
• A large data model, standardised through ISO
  (Ap239)
• A set of data exchange standards (constrained
  subsets of Ap239)
• Improved capability to tailor or extend the data
  model or exchange sets using external reference
  data (e.g. existing standards)
• A standardised interface to one (or more)
  transaction standards/systems .. (ebXML, Exostar,
  Covisint, 2000M)??

11
Product Life Cycle Support (PLCS)The Vision
Life Cycle Data
12

• Ap239 the evolution of modular AP

13
PLCS development principles

• Create a durable data model standard that can be
  extended/adapted over time without re-modelling
  or re-ballot
• Identify key generic concepts and relationships
• Extend/adapt by classification and ref data
  libraries
• Build on the PDM Schema and the STEP Modular
  Architecture
• Accommodate values that change over time
• Support multiple values for the same property
• Support back-tracking audit
• Maintain unambiguous histories
• Activity, State, Product Structure
• Enable a move towards a single digital source
  of Assured Product and Support Information (APSI)
• Improved accuracy
• Reduce duplication
• Improved Configuration Change Management
• Cheaper to create and sustain?
• Aim to enable optimisation of support through
  life

14
AP239 Product Life Cycle SupportFrom business
process to data model teams

Business view 1999/2001
15
Ap239 Product Life Cycle Support Data Model
Teams (Jun 02 Dec 02)

• Work Management
• Capability to request, define, justify, approve,
  schedule and capture feedback on work
  (activities) and related resources.
• Product Description
• Capability to define product requirements and
  configuration, including relationships between
  parts and assemblies in multiple product
  structures (as-designed, as-built, as-maintained)
• Property, State and Behaviour
• Capability that describes and captures feedback
  on product properties, operating states,
  behaviour and usage
• Support Solution and Environment
• Capability to define the necessary support for a
  given set of products in a specified environment
  and to define support opportunity, facilities,
  personnel and organizations

16
Ap239 Product Life Cycle SupportKey semantic
concepts (Mar 03)

States
Properties
Products Activities Resources
Location
Environment
17
PLCS is a Modular STEP AP

• ISO 10303-239 (Ap239)
• All modules feature two levels of model (ARM, MIM
  and mapping)
• LOTS more work eased by XML environment for
  modules development (stepmod.sourceforge.net)
• Significant IR extensions needed
• Harmonization is achieved by using common modules
• With CAD/PDM via PDM Modules and AP236 (214
  based)
• With requirement modules via AP233
• Classification modules allow reference to class
  definitions in external libraries (e.g. ISO
  15926, PLib)

18
Size of the data model
Modules correct other values approx only
19
AP239 Level 2 Modules
risk justification environment probability
Ap239_product_life_cycle_support
Ap239_product_status_recording
Ap239_activity_recording
Ap239_activity_and_resource_management
Ap239_configuration management
Ap239_product_definintion_information
Ap239_work_definition
Ap239_part_definition_information
Ap239_task_specification_resourced
20
Ap239 Product Life Cycle SupportLife Cycle
Configuration Management is a major challenge

• Product definition for design and build
• Need to know permitted, required and actual
  configuration of every individual product
• Multiple (and different) views at each stage
• Effectivity control of the support solution
  definition
• Historic record for managing feedback
• Requirement management
• Navigation to other data

Customer Requirements
Concept and Assessment
Demonstration and Manufacture
In Service and Disposal
System Requirement Configuration
As Designed Configuration
As Manufactured Configuration
As Maintained Configuration
As Planned Configuration
Feedback
Feedback
CM of product design gt IM of Assured Product and
Support Information
21
Introduction

• Legend

PDM module
Foundation module
UoF level module
Implementation module
AP Module
22
UoF module product_management_data
product_management_data
part and version identification part view
definition product categorization product
identification product identification
assignment product version product version
relationship product view definition
23
UoF module document_management
document_management_data
document_and_version_identification document_assig
nment document_definition document_properties docu
ment_structure external_item_identification_assign
ment file_identification
24
UoF module management_resource_information
management_resource_information
alias identification approval certification contra
ct date_time date_time_assignment identification_a
ssignment multi_linguism_arm person
organization person_organization_assignment projec
t security_classification
Enable characterisation of foundation modules
25
UoF module ap239_management_resource_information
ap239_management_resource_information
management_resource_information
alias identification approval certification contra
ct date_time date_time_assignment identification_a
ssignment multi_linguism_arm person
organization person_organization_assignment projec
t security_classification
class
external_class
classification_assignment
attributre_classification
Enables characterisation classification via
Ref Data
26
UoF module ap239_properties
ap239_properties
property_assignment product_view_definition_proper
ties independent_property independent_property_rep
resentation value_with_unit measure_representatio
n
Extended_property_representation
class
external_class
classification_assignment
attribute_classification
27
UoF module ap239_document_management
ap239_document_management
document_management_data
ap239_management_resource_information
ap239_properties
Envelope
Message
Information-rights
28
UoF module requirement_management
requirement_management
management_resource_information
Requirement_identifcation_and version
Requirement_view definition
Requirement_view definition_relationship
Requirement_assignment
29
Implementation module ap239_part_definition_infor
mation
ap239_part_definition_information
ap239_management_resource_information
interface
management_resource_information
interface_lifecycle
product_management_data
product_as_individual
ap239_document_management
document_management_data
State_definition
ap239_properties
State_observed
requirement_management
30
Implementation module ap239_product_definition_in
formation
ap239_product_definition_information
product_breakdown
system_breakdown
assembly_structure
zonal_breakdown
part_definition_relationship
hybrid_breakdwon
product_replacement
functional_breakdown
product_view_definition_relationship
physical_breakdown
product_relationship
attachment_slot
ap239_part_definition_information
31
Work in progress to complete Configuration
Management capability

• Variant/Specification management
• Investigate Ap236 Modules from Ap214
• Enable Configuration Change Management via a link
  to Ap239_activity_and_resource management
• Work request
• Work order
• Scheme (plans and schedules)
• Tasks specification and resources
• Feedback on task completion

32
PLCS Core Life Cycle PDM Capability (1)

• PDM Schema already supports automated exchange of
• Part id and properties
• Associated documents and files (incl. CAx)
• Product structure
• Product (and doc) approval status
• This is already in production use by
• US Aerospace and Defence prime contractors (via
  AP203)
• German/Swedish/French Automotive sector (via
  AP214 cc6)
• EF2000 PDM partners
• .. A powerful and proven capability for
  Configuration Management of a complex product
  design

33
PLCS Core Life Cycle PDM Capability (2)

• AP239 has added
• Product_as_individual (planned and realized)
• Product breakdowns (system, physical, functional,
  zonal and hybrid)
• Attachment_slot
• Interfaces
• Extended property capability
• Text based requirements (from AP233)
• Message, Envelope (similar to Ap232 and to
  ENGDAT)
• Information Rights
• Classification, supported by Reference data
  libraries
• A powerful capability (yet to be proven) for
  Life Cycle Configuration Management of Assured
  Product and Support Information

34
So what else have you done?

• Seven other Level 2 Modules
• New Integrated Resources
• 3 new parts
• Part 56 (State)
• Part 57 (Expression Extension)
• Part 58 (Risk)
• A revision of Part 41
• People/Organisation/ (add type, experience and
  qualifications)
• Position in organisation
• Location
• Extensible select for property_assignment
• Completion of the AP Document
• AP document content
• Definition of Conformance Classes

35
Conclusions

• PLCS, Inc has invested heavily in STEP, including
  many contributions to the common good of SC4
• Completion of PDM modules
• Major input to development of Modular
  architecture
• Provided the supporting tools and training well
  beyond the funding by NIST
• Updated the related qc check list (after
  automating many checks!)
• Encouraged the adoption of ISO 10303 as the
  standard of choice for 4 national Ministries of
  Defence.
• ..it has yet to receive much return!

36
The road to delivery

• With your help we can deliver a major extension
  to STEP by publishing AP239 for DIS ballot by
  October 03 when PLCS. Inc. funding will end.
• Why should you help?
• We are producing high quality models
• We have investigated harmonisation with most of
  SC4
• Modules
• Traditional AP projects
• IS0 15926, Plib and MANDATE
• We have achieved harmonization in many areas
• Common modules
• Common approach to classification
• Re-use of Part 20
• There are still a few open issues but we need
  agreement NOW to put our material out to ballot

37
What help do we need?

• In San Diego
• Final agreement on the structure and content of a
  Modular AP
• WG3 and WG12 approval to release ballots for
• PLCS ballot package 2 (CD/TS)
• Parts 56 and 57 (CD)
• Agreement (subject to ballot) to use EXPRESS 2 to
  open up property_assignment in Part 41
• Agreement (subject to ballot) to other Part 41
  changes needed to support PLCS ballot package 3
  and 4
• Completion of EXPRESS 2
• Before Stuttgart
• Your comment and support on PLCS module ballots
• Your comments and support on the IR extensions
• At Stuttgart
• Rapid resolution of ballot issues for IRs and
  Modules
• Approval to publish Ap239 for DIS ballot

38
Meetings to achieve this

• Weds
• Wg 12 Plenary 10-30
• Part 56 State
• P41 including Property_assignment extension
• Wg 12 Plenary 1-5
• Part 57 Expression Extension
• Part 58 Risk
• 1730 Change Management Plenary
• Thurs
• 1300 PLCS technical briefing (Room 283)
• 1530 WG3 Plenary

39
Product Life Cycle Support (PLCS)Contact Details