Getting the best from SC4 John Dunford, David Leal, Nigel Shaw

1
Getting the best from SC4(John Dunford, David
Leal, Nigel Shaw)

• ISO/TC184/SC4
• Fukuoka, Japan
• September 2001

2
Agenda

• Current Issues/Requirements for co-operation
  across SC4
• PLCS Requirements (JD)
• Set Theory Module (DL)
• Modularization Issues from AP221 (DL)
• PLCS Modularization Issues (JD)
• Beyond SC4 (NKS)

3
Product Life Cycle Support (PLCS)Background

• A joint industry and government initiative to
  accelerate development of new standards for
  product support information
• An international project to produce draft ISO
  standards within 3 years.
• PLCS will ensure support information is aligned
  to the evolving product definition over the
  entire life cycle
• PLCS utilizes ISO 10303 STEP - the STandard for
  Exchange of Product model data

4
Setting the Business ContextBusiness Requirements

• Reduced Cost of Ownership
• Users of products are seeking improved
  availability, reliability, maintainability and
  lower cost of ownership.
• Protect investment in product data
• Users of information systems want more open
  platforms to reduce IT costs and ensure longevity
  in use of information
• Sustainable Business Growth
• Companies are seeking to make money through the
  life cycle support of their products to improve
  profits, improve quality and be more competitive

5
Setting the Business ContextBusiness Problem

• How to keep the data needed to operate and
  maintain a product in line with the changing
  product over its in-service life?

Feedback
6
Setting the Business ContextSupport System
integration is complex and bespoke
Defects Failures
Operational Objectives
12 Depot Maint Mgmt
5. Req. Dev. Tool
Functional Req.
4. Maintenance Management
CM Data
3. Stock Mgmt System
9. ECP CM Tool
CM Data
13. Distribution, Transportation
7. FMECA Tool
Maintenance Mgmt Data
CM Data
1. Support Data Model
FMECA Results
Distr. data
2. Maintainers Viewing Tool
Product data
6. LSA Tool
LSA Data
Product data
Functional Req.
10 IETM CSDB?
8. CAD
14 Defects Failure reporting
11 Parts Supplier database
Physical Design
LSA Data
Parts Data
Tech Pub Data
7
Setting the Business ContextPLCS Standard will
enable effective information exchange
1. Support Data Model
5. Req. Dev. Tool
2. Maintainers Viewing Tool
3. Stock Mgmt System
6. LSA Tool
4. Maintenance Management
7. FMECA Tool
FMECA Results
Maintenance Mgmt Data
Maintenance Mgmt Data
LSA Data
Product data
Functional Req.
Product data
PLCS compliant data exchanges
Tech Pub Data
Defects Failures
Maintenance Mgmt Data
CM Data
Physical Design Data
Distr. data
Parts Data
9. ECP CM Tool
8. CAD
10 IETM CSDB?
11 Parts Supplier database
13. Distribution, Transportation
12 Depot Maint Mgmt
14 Defects Failure reporting
In future, support system integration will be
easier to achieve
8
PLCS and SC4 Standards

• PLCS needs interoperability with STEP in some,
  but not all areas
• Interoperability needed
• Product Structure, Tech Data Package and PDM
• Properties
• Requirements (AP233)
• Interoperability not needed
• STEP geometry (PLCS just points to CAD/CAM
  data)
• Engineering Analysis
• PLCS needs to extend STEP substantially
• Instance
• Multiple product breakdown views
• In-service CM/CCM configure to role, change
  implementation
• Extended enterprise with many participants/roles
• Document
• Much wider context,
• Unbounded list of document types
• Document Generation hot linking (XML based)
• Support data Tasks Resources Reasons for
  doing work Anomaly/Fault/Degradation etc.
• Planning and Scheduling (IFC link)

9
So what?

• PLCS will extend STEP beyond current IRs
• New IRs needed
• Some assumptions implicit in current IRs/Modules
  may no longer be valid in full life cycle context
• Support environment is diverse and unbounded
• Data set cannot be fully prescribed in advance
  (need extensibility)
• Not all users need to interoperate - need
  tailoring for
• Different reference data
• Different user terminology
• Different property sets
• Classification and RDLs seem to answer this need
• Implementation options alter what can/should be
  standardized
• As standalone database (data warehouse?)
• As mapping between a (limited) set of current
  systems
• As standardized exchange (CC, DEX, Template)
• One size does NOT fit all
• Need a grow your own option ( registration?)

10
Questions for Open Technical Forum

• How can a STEP AP exploit 15926/13584 concepts?
• Classification (Set theory)
• RDLs as an Extensibility Mechanism
• When should a new AP use classification
  mechanisms RDL in place of explicit modeling
  (e.g. types of product breakdown)?
• What impact would use of RDLs have on approach to
  compliance/conformance testing?
• How can STEP offer users more flexibility?
• Options to implement any useful subset?
• Options to tailor implementation to use local
  language/classes/property sets?
• Should SC4 provide a registration authority?

11
PLCS issue with Modularization

• Use of modules
• How can classification concepts be applied to
  modules?
• Can APs grow over time?
• Will number of APs explode?
• How to achieve integration of a modular AP
• Does the modular approach
• save effort?
• deliver interoperability?
• Is interpret in advance always the best
  approach?
• What role will IRs play in IIDEAS?
• When will IIDEAS option to interpret where and
  when needed be available?
• Whats wrong with an implementable ARM? (Epistle
  Template!)

12
Product Life Cycle Support InitiativeMembership
is growing why not join us!