40
Product Life Cycle Support (PLCS) Managing Product Support Information from Concept to Disposal What is ISO 10303 AP 239 PLCS? FINSE 23.10.2003, Helsinki Lt.Col Jukka Ponsi Defence Staff
Product Life Cycle Support (PLCS)Managing Product Support Information from Concept to Disposal
What is ISO 10303 AP 239 PLCS?
FINSE 23.10.2003, Helsinki
Lt.Col Jukka PonsiDefence Staff
2PLCS Inc. (c) 2002
Content of the Presentation
Setting the business contextPLCS initiativePLCS standardQuestions?
3PLCS Inc. (c) 2002
Setting the Business ContextBusiness Drivers
Reduced Cost of OwnershipUsers of products are seeking improved availability, reliability, maintainability and lower cost of ownership.
Protect investment in product dataUsers of information systems want more open platforms to reduce IT costs and ensure longevity in use of information
Sustainable Business GrowthCompanies are seeking to make money through the life cycle support of their products to improve profits, improve quality and be more competitive
4PLCS Inc. (c) 2002
Setting the Business ContextDigital Product Data has become a valuable business assetNew Business Opportunities
Leading manufacturers are ‘going downstream’ to generate additional revenue from supply of lifecycle support services
Product Lifecycle ManagementIncreased focus on managing information throughout the product lifecycle – Concept to DisposalBusinesses are focusing on total cost of ownership, as product life cycles increase and products become more expensive to maintain
Extended EnterpriseIncreasingly complex business networksKnowledge workers need to share information in real timeNot practical to adopt common system mandateInternet technology changes everything
5PLCS Inc. (c) 2002
Setting the Business ContextConfiguration Management is a major challenge
Multiple product viewsMajor problems keeping information to operate and maintain a product aligned to actual product configuration through lifeMajor problems linking support information to product informationSoftware applications use proprietary data standards and are often difficult to integrateInconsistent data definitions
CustomerRequirements
CustomerRequirements
Conceptand
Assessment
Conceptand
Assessment Demonstrationand
Manufacture
Demonstrationand
ManufactureIn Service
and Disposal
In Serviceand
Disposal
Feedback
As ManufacturedConfiguration
As PlannedConfiguration
As DesignedConfiguration
Feedback
As MaintainedConfiguration
6PLCS Inc. (c) 2002
Setting the Business ContextLimitations with current standards (1998)
Transaction CentricDefence: AECMA 2000MCommercial: ATA Spec 2000, Edifact, ANSIx.12
Content CentricCAD Models/PDM: ISO 10303 (STEP)Configuration Management (EIA 649+)Logistic Support Analysis: MIL-STD-1388, Def-Stan 00-60
Presentation Centric AECMA Spec 1000DATA Spec 100
Current (1998) standards for product support information:Address individual processes, not life cycle managementUse different technologiesHave gaps, conflicts and overlaps. Predate the internet age
7PLCS Inc. (c) 2002
Setting the Business ContextAvailable capabilities - ISO STEP
STEP is an established international standard for the exchange, integration and sharing of product data
GeometryProduct structureManufacturing interfacesDrawings
STEP Release 2 covers new functions:Finite Element AnalysisPrinted Circuit AssembliesWiring loomsMechanical DesignConstruction industry
XML for the Web
8PLCS Inc. (c) 2002
Eurofighter TyphoonSTEP in service
Structural build work share
37.5% BAE SYSTEMS
19.5% ALENIA
30% EADS-Germany
13% EADS-CASA
Nat
iona
l and
exp
ort c
usto
mer
s
Concurrent product development
Supp
liers
Commonsupplier
base
Four assembly
lines
9PLCS Inc. (c) 2002
Eurofighter PDM Data ExchangeSTEP in service
BAE SYSTEMS
Alenia
EADS-D
EADS-CASA
Partners use different PDM systems
ProductManager (BAE SYSTEMS, Alenia), MetaPhase (EADS-Germany)Optegra (EADS-CASA)
Exchange required to supportConfiguration managementProduct Structure release
10PLCS Inc. (c) 2002
OverviewThe Key Business Problem
How to keep the information needed to operate and maintain a product aligned with the changing product over its life cycle?
Tools
TestEquipment
SupportFacilities
Consumables
Software
Transportation
Spares
StorageRequirements
Training
Product DefinitionInformation
MaintenanceSchedules
Productin FocusProductin Focus
FeedbackFeedback
11PLCS Inc. (c) 2002
Product Life Cycle Support (PLCS)The Initiative
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 4 years; 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
12PLCS Inc. (c) 2002
Product Life Cycle Support (PLCS)Membership
FinnishDefence Forces
13PLCS Inc. (c) 2002
IndustryIndustryDefenceDefence
IT Vendors
IT Vendors ResearchResearch
The Finnish Defence Forces (FDF) believe that the development of Product Life Cycle Support
(PLCS) will enable the FDF to exchange vital product information between parties.
The FDF see PLCS as an enabler to keep the defence systems performance
on required level at affordable costs.
14PLCS Inc. (c) 2002
Product Life Cycle Support (PLCS)The Vision
Scope of STEP Today
Shared Data
Product Representations
Product Performance
Product Structure
Support Performance
Change Directives
Support Environment
Failure Analysis
Maintenance Analysis
Task Resource Data
Life Life Cycle Cycle DataData Maintain/DisposeMaintain/DisposeQueryQuery
Derived Derived Disposable DataDisposable Data
UseUseRespond
Respond
Support and Operational Feedback
Standard Standard Commercial Commercial TransactionsTransactionsFeed and
Feed and
ExtractExtract
15PLCS Inc. (c) 2002
Product Life Cycle Support (PLCS)Typically complex systems environment – point to point integration
7.FMECA
6.LSAR
2.Maintainers
ViewingTool
3.StockMgmt
8.CAD
4.MaintenanceManagement
10IETM
11Parts
Supplier Database
12 Depot Maint
Mgmt
13.Distribution,
Transportation
14 Defects & FailureReporting
9.Product
Data
Functional Requirements
LSA Data
LSA Data
5.RequirementsManagement
LSA Data
Support Data
CM Data
Support Data
Part Data
CM Data
CM DataCM Data
Defects and
Failures Maintenance
Mgt Data
DesignData
Support Data
DistributionData
Tech Pubs Data
1.Support
Data
CM DataOperational Objectives
FMECAResults
16PLCS Inc. (c) 2002
Product Life Cycle Support (PLCS)PLCS will enable cost effective information exchanges
1.Support
Data
7.FMECA
6.LSAR
5.RequirementsManagement
2.Maintainers
ViewingTool
3.StockMgmt
4.MaintenanceManagement
LSA Data FMECAResults
Support data
8.CAD
9.Product
Data
10IETM
11Parts
Supplier Database
12 Depot Maint
Mgmt
13.Distribution,
Transportation
14 Defects & FailureReporting
Functional Req.Part data Maintenance
Mgmt Data
Maintenance
Mgmt Data
PLCS compliant information exchangesPLCS compliant information exchanges
TechPub Data
Defects& Failures
Maintenance
Mgt Data
Design Data Design data Parts Data Distribution
Data
In future, support system integration will be easier to implement
17PLCS Inc. (c) 2002
Product Life Cycle Support (PLCS)Extended Enterprise enabled by Internet technology
Extended Enterprise ofOEM’s, Customer, Partners
and Suppliers
Enterprise Integrationthrough dedicated networks
Domain specific information systems
(e.g. CAD, MRPII, Planning)
Dep
tEn
terp
rise
Cus
tom
ers
Part
ners
Tier
1
Supp
liers
Tier
2Su
pplie
rs
Exte
nded
Ent
erpr
ise
Inte
grat
ion
Product Life Cycle
Internet-based architecture and federated data models make possible implementations involving thousands of users across
many sites
Concept Assessment Demonstration Manufacture In-Service DisposalOperational Feedback
PLCSDomain
Define and implement the support solution, maintain the product configuration
Product Lifecycle Management (PLM)
18PLCS Inc. (c) 2002
Product Life Cycle Support (PLCS)Extended Enterprise – Importance of PLCS
Dep
tEn
terp
rise
Cus
tom
ers
Part
ners
Tier
1
Supp
liers
Tier
2Su
pplie
rs
Exte
nded
Ent
erpr
ise
Inte
grat
ion
Product Life Cycle
When set against a timeline – the picture looks more like this!
C A D M In-Service D
PLCS DomainPLCS Domain
Design forSupportability
Design forSupportability
In Service Support andOperational Feedback
In Service Support andOperational Feedback
Typically 25 – 50 years Operational Life5 – 10 years
19PLCS Inc. (c) 2002
Product Life Cycle Support (PLCS)Example: PLCS for MoD and Defence Contractors
CRISP
MRC
DR4LITS
OASIS Etc …
MoD (PE) Databases for Product Support
SupportContractor
Project specific ‘Point to Point’ interfaces to be developed andmaintainedISO 10303 STEP, AP 239 (PLCS)ISO 10303 STEP, AP 239 (PLCS)
LPD(R)
Eurofighter
Etc …
Astute AstuteTrent 800
RB 199
Etc … Etc …
WAH-64 ApacheEH 101 Merlin
Bowman
Multiple Contracts with UK Defence Contractors
20PLCS Inc. (c) 2002
Product Life Cycle Support (PLCS)Goals
PLCS Standard:Improve product availabilityReduce operating, support and maintenance costsImprove quality and accessibility of Product Life Cycle Support information
PLCS, Inc:Accelerate technical development of the ISO standardsEncourage early implementation commercial software vendorsEncourage early industry participation in the development and testing of the standard
21PLCS Inc. (c) 2002
Product Life Cycle Support (PLCS)Deliverables
A new vision for life cycle supportA terminology dictionaryAn illustrative process model (Application Activity Model)A large data model, standardised through ISO (AP239)An extensible set of data exchange standards (constrained subsets of AP239, with implementation guidance)Improved capability to tailor or extend the data model or exchange sets using “reference data” (with maximum re-use from current standards)A standardised interface to one (or more) transaction standards/systems .. (ebXML, Exostar, 2000M?)
22PLCS Inc. (c) 2002
Product Life Cycle Support (PLCS)Capabilities enabled by PLCS – ISO 10303 AP 239
Product DescriptionCapability to define product requirements and configuration, including relationships between parts and assemblies in multiple product structures (as-designed, as-built, as-maintained)Work ManagementCapability to request, define, justify, approve, schedule and capture feedback on work (activities) and related resources.Property, State and BehaviourCapability that describes and captures feedback on product properties, operating states, behaviour and usageSupport Solution and EnvironmentCapability to define the necessary support for a given set of products in a specified environment and to define support opportunity, facilities, personnel and organizations
AP 239Capabilities
AP 239Capabilities
23PLCS Inc. (c) 2002
Product Life Cycle Support (PLCS)Unique Value Proposition
International Standard for product support information -based on ISO 10303 STEP (AP 239)Complete product lifecycle – from concept to disposalSingle source of assured product and support informationData independence - Processes, Systems, Format Interoperability across enterprises and systems through:
Standardization of semantics for product supportIntegrated suite of data models for data exchange and information sharingUtilization of ISO STEP standards, methods and tools (incl XML/XSLT)
Extensibility and tailoring through the use of Reference data libraries
Customers, Contractors and Software VendorsCustomers, Contractors and Software Vendorsworking together to develop and implementworking together to develop and implement
a neutral data exchange standard for product supporta neutral data exchange standard for product support
24PLCS Inc. (c) 2002
Current situation (September 2003)
Activity Model published (available to all)1750 requirements allocated to ~130 modulesModule development completed (subject to comment):
PDM Modules are now stable as ISO Technical SpecificationsFirst two sets of PLCS modules accepted - remainder under ISO ballotAP239 information model available
Draft International Standard ballot for Application Protocol due to start in November 2003Development of first eight Data Exchange Sets under wayLaunch events in September in Scandinavia, US and UKFuture organisation in place - more later Implementation activities are gaining momentum in Norway, Sweden, Finland, UK and US
25PLCS Inc. (c) 2002
Current status
Standard under ballotSome effort will be required to answer commentsBallot on full AP239 to be completed
DEX infrastructure in placeOver 40 DEX identifiedEight under active development
Vendor tools under development and testEarly implementations under way
Nature of activity is changing from development to exploitationPLCS, inc activity scheduled to end in November 2003
26PLCS Inc. (c) 2002
Standards development and maintenance
ISO TC184/SC4 is responsible for “Industrial data”Working Group 3 is responsible for “Product modelling”Team 8 is responsible for “Product life cycle”
Team 8 will retain responsibility for AP239Resources committed through national standards bodiesAlso provides clear liaison to Systems Engineering development
27PLCS Inc. (c) 2002
DEX Development and publication
Open-source infrastructure developedSeeking more open participation
lower cost entryNeed enhanced links with other information standards development Selected OASIS consortium as parentProposed formation of an OASIS Technical Committee for “Product Life Cycle Support”Open to all OASIS membersOperating under OASIS rules
28PLCS Inc. (c) 2002
Getting involved
Join in an early implementation Join the OASIS Technical Committee to participate in DEX development
First meeting scheduled for 26 September in Manassas, VASign-up required by 11 September - see
www.oasis-open.orgContribute to further developments in ISO through your national standards body
29PLCS Inc. (c) 2002
PLCS: relationship to other standards
“If we reach high,we do so only because
we stand on the shouldersof those who went before”
(Albert Einstein)
30PLCS Inc. (c) 2002
PLCS: Inputs to AP239
ISO15288OMG
STEP
Mil Spec2549
ATAEffectivity
AP208
POSC/Caesar
FMVCTG2
NCDM
AECMA1000D2000M
Mil Spec1388
AP203
TC184/SC4WG3/T8
PWI
PDMSchema
PLCSInitiative
AP 233PLIB
Def Stan00-60
RCMITDef Stan
00-60Logical
SGMLEDIFACT
IDEF1-X
Relational
EXPRESSbased
31PLCS Inc. (c) 2002
AP239 Product Life Cycle Support – Activity Model
An IDEF 0 model with 157 activities (boxes) and 220 information exchanges (arrows)Purpose:
1999/00: to define the scope of PLCS activity2001/2: to expose data requirements2003: (current role) to represent the activities and information flows supported by Application Protocol 239
Future useCommunication the PLCS VisionCharting information exchange boundaries between organizationsIdentifying and illustrating DEXs
Available as .bp1, .idl, html, xml or pdf.
32PLCS Inc. (c) 2002
Example: Support Engineering AAM
NODE: TITLE: NUMBER:Generate a Support SolutionA0 SE-02
A1
Manage Support EngineeringProgramme
A2
Identify & Define Support
Requirements
A3
Design Support Solution
A4
AssessSupportSolution
Support SolutionRequirements
Info from otherSystems
Customer Requirements
Support FeedbackOperator Feedback
Life Cycle Directives
Requests forConcessions
SE Programme
Requests forRequirementClarification
Change Directives
Requirementsto Design
Feedback to CM
APSI and RelatedInformation
AssessmentNeeds & Results
Requestinvestigations
PerformanceExpectations
RequirementsFeedback
Requests to LCO
Support Solution
PerformanceReports
RequirementDirectives
ResourceFeedback
33PLCS Inc. (c) 2002
AP239 – The information model
Main conceptsA LARGE, GENERIC data model Defined in EXPRESS 134 Modules, ~500 Entities, ~1200 attributesCan be extended using classification based on Reference Data, stored in an external Library (RDL)
Main conceptsTop Module structureUsing the model for support engineering
34PLCS Inc. (c) 2002
Ap239 Product Life Cycle SupportKey semantic concepts (Mar 03)
ProductsActivities
ResourcesLocation
StatesProperties
Environment
Lifecycle phases: (Required, Design, Planned, Realized)
Business qualifiers:(Characterization, Conditions, Justification, Risks)
35PLCS Inc. (c) 2002
AP239 Top Modules
36PLCS Inc. (c) 2002
AP239 – Data Exchange Sets
DEXs are:Subsets of the AP239 Information modelSelected to meet a specific data exchange needSupported by Usage Guidance, population rules and Reference data
DEXs may be standardized at any level (work group, company, project, organization, national, international)DEXs enable
Consistent implementation of AP239Data consolidation through time
Same DEXDifferent DEX
37PLCS Inc. (c) 2002
Initial PLCS DEXs (draft only)
DEX 1Product breakdown
for support
DEX 5Maintenance
Plan
DEX 6SupportDrivers
DEX 3TaskSet
DEX 2Product Faults
Part id
Fault idLSI idFunction id
Task id
DEX 4Work schedulewith feedback
DEX 7Fault reporting
Serial product id
REF DATA
DEX 8Manufactured Item
Activity id?
38PLCS Inc. (c) 2002
Reference Data
Reference data is:standardised computer interpretable data,used to extend or tailor a data modelor to hold agreed descriptions of data to be shared between participants
Reference data provides:a capability to tailor and extend a standardised data model in a controlled manner
Examples of reference datatypes of task (e.g. safety critical, level 3 skillstypes of required resource (NSN)Type of product
The scope of Reference data is HUGEReference data is a further opportunity for standardization
39PLCS Inc. (c) 2002
Product Life Cycle Support (PLCS)Contact Details
For further information contact any of the following PLCS team members:
Program [email protected] [email protected] [email protected]
FDF [email protected] [email protected] Finland [email protected]
Or visit the PLCS web site: www.plcsinc.org (esp. the FAQs)
40PLCS Inc. (c) 2002
Thank you for your attention.Any questions?
