1. Howard Mason BAE Systems
Product Life Cycle Support (PLCS) The Information Backbone to transform the Logistics Enterprise
Howard Mason
BAE Systems
Standard Title may be replaced by audience specific title – examples:
“PLCS: Another STEP towards delivering Business Benefit“
“PLCS: A STEP in the right direction”
“ Business Improvement – STEP by STEP”
“ PLCS: One small STEP for man…”
Or whatever…
Include Name, Organisation, Venue and Date as required

2. Exploiting the benefits Future plans
The PLCS Initiative
The Business Context
Overview of PLCS
Vision
Capabilities
Deliverables
Status
Exploiting the benefits
Future plans
Replace this slide with your own related to the content of the actual presentation
Slide title should be Agenda or Content or Presentation Route Map
PLCS Inc. (c) 2002

3. Setting the Business Context Business Drivers
Reduced Cost of Ownership
Users of products are seeking improved availability, reliability, maintainability and lower cost of ownership.
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
Protect investment in product data
Users of information systems want more open platforms to reduce IT costs and ensure longevity in use of information
3 main business drivers
Reduced cost of ownership – owners faced with reducing budget and ageing equipment
Making use of legacy data – reduction in cost of interface development and maintenance
Providing a means of sustainable business growth through use of information to secure support contracts
PLCS Inc. (c) 2002

4. Setting the Business Context Digital Product Data has become a valuable business asset
New Business Opportunities
Leading manufacturers are ‘going downstream’ to generate additional revenue from supply of lifecycle support services
Product Lifecycle Management
Increased focus on managing information throughout the product lifecycle – Concept to Disposal
Businesses are focusing on total cost of ownership, as product life cycles increase and products become more expensive to maintain
Extended Enterprise
Increasingly complex business networks
Knowledge workers need to share information in real time
Not practical to adopt common system mandate
Internet technology has changed the way of working
Following on from the previous slide – last point on Sustainable Business Growth
Digital Data as a business asset
Product information has moved from Engineering asset to Enterprise asset
New Business opportunities through use of product data in support
Business are focussing on providing life cycle support services and through life cost management
The use of Internet technology opens up communication across the ‘virtual enterprise’
The last bullet is a lead into the next slide which shows collaboration in the supply chain
PLCS will play an important part in facilitating the supply of timely and accurate information.
PLCS Inc. (c) 2002

5. Setting the Business Context Requirements of the Extended Enterprise
Extended enterprises are formed to meet project specific requirements
Partners may differ from project to project
Different partners are likely use different systems
Companies want a common way to exchange digital product data
Configuration Management becomes a key enabler for information exchange
Suppliers want a unified approach from Prime Contractors and OEMs
International collaboration demands product data exchange and sharing across many organizations
Worldwide operation demands a worldwide standard
Program Manager
Sales
Marketing
Engineering
Support
Mfg.
Project Z
Product Team 2
Product Team 1
Project Y
Project X
Supplier A
Supplier B
Supplier C
Partner
FIREWALL
Having introduced the extended enterprise, this slide defines some of the requirements
This is important in a PLCS context because it reinforces the need for a neutral standard for data exchange
Project composition can vary from project to project – so dictating a common system to ensure integration is not a practical option – it becomes prohibitively expensive to keep developing and maintaining point to point interfaces every time you move to a new project
Configuration Management is a key requirement – if the product information is not representative an accurate representation of the actual product it becomes meaningless – feedback is an essential element in maintaining accurate product configuration information in all phases of the lifecycle.
Equally Tier1/Tier2 suppliers want to be able to collaborate on projects, without the need for investing in project specific interfaces. Applications complying with a neutral standard will help reduce this cost and allow greater opportunity to compete.
Many A&D projects have an international collaboration element and therefore adoption of an ISO standard will facilitate collaboration across national boundaries – PLCS is the only ISO standard to address the complete product life cycle.
PLCS Inc. (c) 2002

6. Setting the Business Context Configuration Management is a major challenge
Multiple product views
Major problems keeping information to operate and maintain a product aligned to actual product configuration through life
Major problems linking support information to product information
Software applications use proprietary data standards and are often difficult to integrate
Inconsistent data definitions
Customer
Requirements
Concept
and
Assessment
Demonstration
Manufacture
In Service
Disposal
Feedback
As Manufactured
Configuration
As Planned
As Designed
As Maintained
This slides draws attention to the importance of Configuration Management and the problems associated with keeping product information aligned to the physical instance of the product throughout its life.
Different people require different views of the Product information, as-designed, as-planned, as manufactured, as-maintained etc. All are valid, but maintaining the links is a complex configuration management task which is not done well today.
Once in the field, it is difficult to maintain an accurate configuration record of the product because of limitations in feedback processes and systems.
Individual software applications only address part of the information systems requirement. To put together an overall information systems architecture requires dedicated interfaces to be developed
Some application architectures are proprietary and difficult to integrated using standard tools.
When software vendors provide an information exchange capability for import/export through a vendor independent neutral standard, the issues and costs of application integration will be significantly reduced.
The other key point to make on this slide is that PLCS is an extension to the PDM schema capability under ISO 10303, STEP
PLCS Inc. (c) 2002

7. Setting the Business Context Limitations with current standards (as at November 1999)
Current standards are specialized and focus on either:
a piece of a business transaction or process, e.g. Order,Part or
presentation of specific content, I.e. Aircraft maintenance manual
Example: Transaction oriented
Defence: AECMA 2000M
Commercial: ATA Spec 2000, EDIFACT, ANSI X.12
Example: Content oriented
Manufacturing and process centric:
ISO 9000, STEP
Operations and maintenance centric:
Defence: MIL-STD-1388, Def-Stan 00-60, AECMA S1000D
Commercial: ATA Spec 2000, 2100
This slide attempts to explain the limitations of existing standards and by implication, why PLCS is required.
Existing standards only deal with part of the problem – they are either transaction based and deal with part of the process or
They deal with specific information exchanges related to content – I.e.technical publications
No standards deal with the complete life cycle process – concept to disposal.
No standards deal with process and content/context
Hence PLCS fills a gap in the market.
PLCS Inc. (c) 2002

8. Setting the Business Context Available capabilities - ISO STEP
STEP is an established international standard for the exchange, integration and sharing of product data
Geometry
Product structure
Manufacturing interfaces
Drawings
STEP Release 2 covers new functions:
Finite Element Analysis
Printed Circuit Assemblies
Wiring looms
Mechanical Design
Construction industry
XML for the Web
PLCS Inc. (c) 2002

9. Setting the Business Context STEP in service
Product Data Management exchange for Eurofighter
Supplier interface for Lockheed Martin
Configuration Management and Digital Pre-Assembly exchange at Boeing - RR, GE and P&W
Interface between A380 and its engines
IBM's global e-procurement design data exchange
Solid model exchange for Electric Boat
US and UK Navy RAMP programmes
Japanese SCADEC programme for the construction industry
Ford CAD/PDM data integration
NASA Engineering information
PLCS Inc. (c) 2002

10. Overview Imagine the opportunities if …
Configuration management information was always accurate, up to date and immediately accessible
Maintenance information was precisely tailored to the work to be done
Spares and inventory costs were minimized through vendor involvement in an integrated supply chain
In-service feedback was accurate, meaningful and readily available to product designers and support managers
Change was easy to manage
Moving now into a summary of issues and challenges
This slide encourages the reader to consider how much easier life would be if we could be sure about the accuracy, timeliness and relevance of the information we have to deal with in our day-to-day business.
The intention is that the audience sympathize with this view and we encourage them to think that PLCS can provide the capability for this dream to become a reality.
Adopting PLCS implies cutting out waste and improved efficiency in the use of resources.
PLCS Inc. (c) 2002

11. Overview The Key Business Problem
How to keep the information needed to operate and maintain a product aligned with the changing product over its life cycle?
Product
in Focus
Product Definition
Information
Maintenance
Schedules
Consumables
Software
Transportation
Feedback
Tools
Test
Equipment
Support
Facilities
Spares
Storage
Requirements
Training
Following on from the previous slide
This slide gives some examples of the type of information that must be maintained in line with the actual product configuration – it places the issue in the form of a business problem to be solved
It also stresses the importance of feedback from field operations.
PLCS Inc. (c) 2002

12. Product Life Cycle Support (PLCS) Membership
Finnish
Defence
Forces
This slide shows the current membership – it could come at the beginning of the presentation if considered appropriate.
I have it at the end to reinforce that these companies are committed and, having heard the business case, the opportunity is open for others to participate in the widespread implementation of the standard through associate membership ( to be defined)
PLCS Inc. (c) 2002

13. 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 STEP - the STandard for Exchange of Product model data
This is the standard introduction slide
Bullet 1: Emphasize joint industry government initiative – focussed on product support
Bullet 2: International project – Now years to ensure successful Transition to Implementation – on time/on programme
Bullet 3: Keeping support information aligned with product as it changes over its life
Bullet 4: Extension of ISO STEP – to be published as an Application Protocol AP 239
Draw attention to web site
Talk about the four corners of the logo
Support Engineering – Defining the support solution, facilities and operating environment
Resource Management – Material and Manpower Planning and Scheduling – Links to transaction studies
Configuration Management – Maintaining information in line with product – multiple product views
Maintenance and Feedback – Undertaking work in accordance with schedule and providing timely and accurate feedback
PLCS Inc. (c) 2002

14. Product Life Cycle Support (PLCS) Goals
PLCS Standard:
Improve product availability
Reduce operating, support and maintenance costs
Improve quality and accessibility of Product Life Cycle Support information
PLCS, Inc:
Accelerate technical development of the ISO standards
Encourage early implementation commercial software vendors
Encourage early industry participation in the development and testing of the standard
Having defined the opportunities and issues, this slide summarizes the three main business goals of PLCS
Improved availability
Reduced cost
Improved Quality
It also describes some of the goals of PLCS Inc, aimed at bringing the standard to market in relatively short time
The success of PLCS will depend upon its widespread implementation.
Before proceeding it may be worth checking for understanding with the audience and seeking their confirmation that the opportunities and issues identified are recognised in their business context.
PLCS Inc. (c) 2002

15. Product Life Cycle Support (PLCS) The Vision
Change Directives
Standard Commercial Transactions
Feed and
Extract
Scope of STEP Today
Shared Data
Product Representations
Product Performance
Product Structure
Life Cycle Data
Maintain/Dispose
Query
Support Performance
Task Resource Data
Failure Analysis
Maintenance Analysis
Support Environment
Support and Operational Feedback
Derived Disposable Data
Use
Respond
This slide deals with the scope of PLCS
The first build starts by defining the scope of the STEP PDM Schema today
To be of greater relevance to the Maintainer, some additional information is required - this turns the source of product data into a source of product data across the lifecycle – I.e. not just in the design/manufacture phase. This data is then potentially the subject of change through life and the next build shows how support and operational feedback also impact on the source of life cycle data in order to maintain an accurate configuration.
The next build addresses the fact that some of this data is extracted for use and then discarded – I.e. not used under configuration control – no feedback
The final build refers to the need of commercial systems like ERP systems to extract and feed information too and from the single data source.
PLCS Inc. (c) 2002

16. Extended Enterprise of OEM’s, Customer, Partners
Product Life Cycle Support (PLCS) Extended Enterprise enabled by Internet technology
Internet-based architecture and federated data models make possible implementations involving thousands of users across many sites
Extended Enterprise of
OEM’s, Customer, Partners
and Suppliers
PLCS
Domain
Define and implement the support solution, maintain the product configuration
Suppliers
Tier 2
Tier 1 Suppliers
Product Lifecycle Management (PLM)
Enterprise Integration
through dedicated networks
Extended Enterprise Integration
Customers
Partners
Domain specific
information systems
(e.g. CAD, MRPII, Planning)
Enterprise
Opportunity provided by Internet technology in supporting the ‘Extended Enterprise’
Start by referring to the axis
On the X axis - the product life cycle from concept to disposal
On the Y axis – the extended enterprise from local department through Company to customers and partners and the Tier1/Tier2 supply chain
The initial build shows the extent of influence of traditional information systems, I.e. mainly design and manufacture, localized to functional departments and possibly some visibility within the company
The second build (green) refers to enterprise integration through dedicated networks- possible involving major partners and the customer – the scope again mainly confined to design and manufacture phases – This is typically the domain supported by traditional client-server architectures
The next build introduces the impact of the Internet – allowing the realistic prospect of large scale supplier integration and collaboration. This has long been the aim of concurrent engineering/collaborative engineering but until now the technology was not there to allow it to make it practical.
The Internet opens up the opportunities for managing the product information through life – latest three letter acronym is PLM(Product Lifecycle Management) with the emphasis on Lifecycle
PLCS scope is shown in purple, mainly in the support phase, but also extending back into design and manufacturing for the design for supportability and design of the support solution. Make reference to the fact that the x-axis scale distorts the impact of PLCS – In-service phase is typically 5-10 times longer than the design/manufacture phase. Example: B52 bomber will have a total lifecycle of 100 yrs when it is eventually withdrawn from service.
The final build shows the importance of operational feedback – providing the ability to update the as-maintained configuration and provide valuable operating experience to influence new designs.
Dept
Concept
Assessment
Demonstration
Manufacture
In-Service
Disposal
Operational Feedback
Product Life Cycle
PLCS Inc. (c) 2002

17. Product Life Cycle Support (PLCS) Extended Enterprise – Importance of PLCS
When set against a timeline – the picture looks more like this!
PLCS Domain
Design for
Supportability
In Service Support and
Operational Feedback
Suppliers
Tier 2
5 – 10 years
Typically 25 – 50 years Operational Life
Tier 1 Suppliers
Extended Enterprise Integration
Customers
Partners
Enterprise
Opportunity provided by Internet technology in supporting the ‘Extended Enterprise’
Start by referring to the axis
On the X axis - the product life cycle from concept to disposal
On the Y axis – the extended enterprise from local department through Company to customers and partners and the Tier1/Tier2 supply chain
The initial build shows the extent of influence of traditional information systems, I.e. mainly design and manufacture, localized to functional departments and possibly some visibility within the company
The second build (green) refers to enterprise integration through dedicated networks- possible involving major partners and the customer – the scope again mainly confined to design and manufacture phases – This is typically the domain supported by traditional client-server architectures
The next build introduces the impact of the Internet – allowing the realistic prospect of large scale supplier integration and collaboration. This has long been the aim of concurrent engineering/collaborative engineering but until now the technology was not there to allow it to make it practical.
The Internet opens up the opportunities for managing the product information through life – latest three letter acronym is PLM(Product Lifecycle Management) with the emphasis on Lifecycle
PLCS scope is shown in purple, mainly in the support phase, but also extending back into design and manufacturing for the design for supportability and design of the support solution. Make reference to the fact that the x-axis scale distorts the impact of PLCS – In-service phase is typically 5-10 times longer than the design/manufacture phase. Example: B52 bomber will have a total lifecycle of 100 yrs when it is eventually withdrawn from service.
The final build shows the importance of operational feedback – providing the ability to update the as-maintained configuration and provide valuable operating experience to influence new designs.
This slide provides a greater impression of the time and opportunity to impact through life aspects.
Dept C A D M
In-Service D
Product Life Cycle
PLCS Inc. (c) 2002

18. Product Life Cycle Support (PLCS) Typically complex systems environment – point to point integration
Operational
Objectives
CM Data
CM Data
CM Data
CM Data 5.
Requirements
Management 9.
Product
Data 12
Depot Maint
Mgmt
14 Defects
& Failure
Reporting 4.
Maintenance
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
LSA Data
FMECA
Results
Support Data
Distribution
Data
The main point of this slide is to highlight that there are potentially many sources of information related to the support of a product.
It reinforces the message about complexity of system integration
The complexity also explains why few if any organisations have a fully integrated solution in place.
The slide implies the support information can potentially resides in over a dozen databases – without considering the additional databases for financial and commercial transaction systems typically found in ERP applications.
Understanding every line on the diagram is not important – it is sufficient for the audience to appreciate that the situation is complex and by implication expensive to develop and maintain.
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
PLCS Inc. (c) 2002

19. PLCS compliant information exchanges
Product Life Cycle Support (PLCS) PLCS will enable cost effective information exchanges 1.
Support
Data 2.
Maintainers
Viewing
Tool 3.
Stock
Mgmt 4.
Maintenance
Management 5.
Requirements
Management 6.
LSAR 7.
FMECA
Support data
Maintenance
Mgmt Data
Part data
Maintenance
Mgmt Data
Functional Req.
LSA Data
FMECA
Results
PLCS compliant information exchanges
Tech
Pub Data
Design Data
Design data
Maintenance
Mgt Data
Parts Data
Distribution
Data
Defects & Failures
This slide is aimed as a contrast to the previous slide and simplifies the exchange scenario by introducing a standard mechanism for importing and exporting product information.
Use as anecdotal evidence the data sharing between the two PLCS technology demonstrators.
It proved possible for a data set from one demonstrator (PTC/AEI/Boeing/DoD) to be read by the other (LSC/RR/MoD) despite there having been no collusion between the two teams prior to the AEFI show in Phoenix, AZ last September.
Reduced cost, faster integration, data independence are some of the benefits anticipated from the application of PLCS. 8.
CAD 9.
Product
Data 10
IETM 11
Parts Supplier
Database 12
Depot Maint
Mgmt
13.
Distribution,
Transportation
14 Defects
& Failure
Reporting
In future, support system integration will be easier to implement
PLCS Inc. (c) 2002

20. Product Life Cycle Support (PLCS) Example: PLCS for MoD and Defence Contractors
Multiple Contracts with UK Defence Contractors
LPD(R)
Eurofighter
Etc …
Astute
Trent 800
RB 199
WAH-64 Apache
EH 101 Merlin
Bowman
Project specific ‘Point to Point’ interfaces to be developed and maintained
Support
Contractor
ISO STEP, AP 239 (PLCS)
CRISP
MRC
DR4
LITS
OASIS
Etc …
MoD (PE) Databases for Product Support
This is a slide that was put in for MoD, it can be used however to illustrate the fact that multiple contractors typically each working on multiple contracts need access to both their own information and those of their customer.
The customer’s information is typically in a variety of formats.
For a support contractor to gain access to both sets of information is both time-consuming and expensive – it required purpose built integration
Management and use of Legacy data is one of the biggest issues for Departments of Defence
With a neutral information exchange standard (PLCS) life will be a lot easier.
PLCS Inc. (c) 2002

21. Product Life Cycle Support (PLCS) Capabilities enabled by PLCS – ISO 10303 AP 239
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)
Work Management
Capability to request, define, justify, approve, schedule and capture feedback on work (activities) and related resources.
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
AP 239
Capabilities
This slide deals with the capabilities enabled by PLCS
It describes in simple terms what business transactions will be supported by PLCS – these are the highest level of DEX’s and reflect the way in which the task of producing the Standard has been logically broken down.
It is recommended that the significance of each bullet is explained otherwise the value of the slide may be lost.
PLCS Inc. (c) 2002

22. A new vision for life cycle support A terminology dictionary
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)??
PLCS Inc. (c) 2002

23. PLCS: relationship to other standards
“If we reach high,
we do so only because
we stand on the shoulders
of those who went before”
(Albert Einstein)
PLCS Inc. (c) 2002

24. PLCS: Inputs to AP239 POSC/ Caesar RCM EXPRESS IT based Mil Spec
IDEF1-X
Relational
EXPRESS
based
RCM IT
Mil Spec
2549
Def Stan
00-60
Def Stan
00-60
Logical
AP208
TC184/SC4
WG3/T8
PWI
PLCS
Initiative
Mil Spec
1388
FMV
CTG2
STEP
NCDM
AP203
ATA
Effectivity
AP 233
PDM
Schema
PLIB
ISO
15288
AECMA
1000D
2000M
OMG
SGML
EDIFACT
PLCS Inc. (c) 2002

25. 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 reference data libraries
Build on existing standards:
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
Product Structure, State, Activity
Aim: to enable optimisation of support through life
PLCS Inc. (c) 2002

26. Product Life Cycle Support (PLCS) Main activity areas
Business
Fixed boundaries
Limited scope
Hard to Change
Poor cost awareness
Life cycle business
Open and Flexible
Agile
Lean and focused
NATO CALS PP1 and TLBM
ISO Prelim Work Item
Launch
PLCS
Automate Current Processes
New Integrated Processes
Better , Cheaper Information
Usage Guides
Industry Testing
Published standards
Submit to ISO
Process
Duplicated
Fragmented
Organization Specific
Locked by IT
Coherent
Simplified
Open
IT independent
Information Requirements
“As is” Scenarios
Exchange
Requirements
Develop Activity Models
Test and
Integrate
This is a further expansion of the previous slide with reference to the PLCS activities at each phase of the Systems Engineering Waterfall diagram.
We are currently moving into the blue zone with testing and integration, prior to industry testing and implementation leading to the forecast business benefits in red
Data
Inconsistent Terminology
Format dependent
Massive duplication
Islands of IT
Common language
Format “ as required”
Reduced data set
Portable data
Develop Single Integrated Data Model based on Express
PLCS Inc. (c) 2002

27. 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 activity
2001/2: to expose data requirements
2003: (current role) to represent the activities and information flows supported by Application Protocol 239
Future use
Communication the PLCS Vision
Charting information exchange boundaries between organizations
Identifying and illustrating DEXs
Available as .bp1, .idl, html, xml or pdf.
This slide can be used as a summary of the previous slides on business drivers, enterprise requirements, opportunities and risks/issues (Slides 3-14)
Having access to digital product information provides all kinds of new opportunities for data re-use – based on the old CALS adage “ Input once- use many times” . In many ways CALS was ahead of its time – the CALS vision remains as true today as it was years ago – unfortunately it got a bad name because it failed to deliver, mainly because of two things:
The technology was not there to support it and
It involved significant changes to process, behaviours and other ‘people’ related issues that in practice are very difficult to achieve.
Internet technology and e-business standards make it more likely to happen – however the people/process issues still remain
Assuming people be encouraged to share knowledge and information – the risks than come from ensuring the information is accurate and timely and the context in which the information is provided is understood. For example Q. Is a ‘tank’ a vessel holding fluid or a tracked fighting vehicle – A. both depending upon the context of the question.
PLCS will help standardise product support information through a common terminology dictionary and the use of reference data
PLCS Inc. (c) 2002

28. AP239 Product Life Cycle Support – Activity Model Concepts
The PIF – Product in focus: “what products do you want me to support?”
A PIF will be supported by one or more support solution definitions: how to support these products
Each support solution definition is based on
A deployment environment
A support solution requirement
The deployment environment defines:
A product group – a sub-set of the PIF needing tailored support
A usage pattern
A definition of the expected support organizations, locations, facilities and resources
A support requirement is a structured requirement statement including performance metrics and targets for support performance
Support metrics are required to enable:
Continuous optimization of support solution definition through life, based on feedback from use
Specification of an assessment strategy (what data to collect and how)
A PIF scope may include many deployment environments and hence many support solution definitions
These will be derived from a common set of task and resources descriptions
This slide can be used as a summary of the previous slides on business drivers, enterprise requirements, opportunities and risks/issues (Slides 3-14)
Having access to digital product information provides all kinds of new opportunities for data re-use – based on the old CALS adage “ Input once- use many times” . In many ways CALS was ahead of its time – the CALS vision remains as true today as it was years ago – unfortunately it got a bad name because it failed to deliver, mainly because of two things:
The technology was not there to support it and
It involved significant changes to process, behaviours and other ‘people’ related issues that in practice are very difficult to achieve.
Internet technology and e-business standards make it more likely to happen – however the people/process issues still remain
Assuming people be encouraged to share knowledge and information – the risks than come from ensuring the information is accurate and timely and the context in which the information is provided is understood. For example Q. Is a ‘tank’ a vessel holding fluid or a tracked fighting vehicle – A. both depending upon the context of the question.
PLCS will help standardise product support information through a common terminology dictionary and the use of reference data
PLCS Inc. (c) 2002

29. AP239 Product Life Cycle Support – Activity Model Concepts
(Each) Support solution definition includes:
Tasks specifications and task logic (e.g. diagnostic procedures)
Relationship of tasks to the product configuration (including “effectivity” /“applicability” to all product versions)
Specification of task trigger conditions based on:
State of individual product (as identified by UID)
Usage of individual product
Prior task or other events
Identification and quantification of resources needed for each task, including a resource consumption model
Task specifications may:
point to an existing document
point to an SGML document (e.g. an AECMA 1000 Module)
be fully “machine readable”
Task specifications may be linked to resources
Required resources
Resource items (products, people, facilities etc)
PLCS Inc. (c) 2002

30. APSI and Related Information
Assured Product Support Information comprises
PIF scope
Description of relevant deployment environments
Support Solution requirements
Product Definition Information (at least that needed for support)
Support Solution Definitions
This full data set is subject to configuration change management (CM = IM?)
Related Information may comprise
Test results
Manufacturing records
History of collected feedback on:
Individual product configuration over time
Product state and properties over time
Activities, including:
Product use
Work done
Resource use
PLCS Inc. (c) 2002

31. AP239 – The information model
Main concepts
A large, generic data model
Defined in EXPRESS
144 Modules, ~500 Entities, ~1200 attributes
Can be extended using classification based on Reference Data, stored in an external Library (RDL)
PLCS Inc. (c) 2002

32. PLCS is a Modular STEP AP
Modules allow common definitions of product data to be reused
Extensive re-use of PDM modules
To bring compatibility with design/PDM tools
Basic work order/work request process common to change in design
Extended to provide
Life cycle CM
Full work management capability
Condition based task triggers
All modules feature two levels of model, with mapping
User view of information
Link to common concepts across all of STEP
Full harmonization achieved where needed by common modules
With CAD/PDM via PDM Modules
With Requirement Tools
PLCS Inc. (c) 2002

33. PLCS enables requirement management through life
AP239 will share common modules with AP233 – Systems Engineering:
Text-based Requirements
Multiple, related breakdowns, including “System” concept
Interfaces
Aim is to support requirements trace from pre-design through to maintenance and disposal
UK MOD has funded demonstration project for this capability with BAE Systems
PLCS Inc. (c) 2002

34. In the PLCS models it is assumed that any value supplied
PLCS provides full history to support optimization and change over time
In the PLCS models it is assumed that any value supplied
E.g. a property such as mean time to perform a task
may have multiple values over time
where each value could have been:
supplied at different times
by different people
subject to approval
subject to security classification
Have an associated justification/probability/risk
This requirement has been recognised from the start of modelling
Improve CM of support information by use of “single source” Assured Product and Support Information (APSI)
PLCS Inc. (c) 2002

35. Product Life Cycle Support (PLCS) Life Cycle Configuration Management is a major challenge
Need to distinguish and compare data from different life cycle phases
“Class” & Individual
Need multiple (and different) views at each stage
Product structures provide “Life cycle core”
Used to navigate and control applicability of support solution and of feedback data
Core used to manage configuration change
Customer
Requirements
Concept
and
Assessment
Demonstration
and
Manufacture
In Service
and
Disposal
System
Requirement
Configuration
As Designed
Configuration
As Manufactured
Configuration
As Maintained
Configuration
This slides draws attention to the importance of Configuration Management and the problems associated with keeping product information aligned to the physical instance of the product throughout its life.
Different people require different views of the Product information, as-designed, as-planned, as manufactured, as-maintained etc. All are valid, but maintaining the links is a complex configuration management task which is not done well today.
Once in the field, it is difficult to maintain an accurate configuration record of the product because of limitations in feedback processes and systems.
Individual software applications only address part of the information systems requirement. To put together an overall information systems architecture requires dedicated interfaces to be developed
Some application architectures are proprietary and difficult to integrated using standard tools.
When software vendors provide an information exchange capability for import/export through a vendor independent neutral standard, the issues and costs of application integration will be significantly reduced.
The other key point to make on this slide is that PLCS is an extension to the PDM schema capability under ISO 10303, STEP
As Planned
Configuration
Feedback
Feedback
PLCS Inc. (c) 2002

36. 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 document) 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)
Eurofighter Typhoon PDM partners
.. A powerful and proven capability for Configuration Management of a complex product design
PLCS Inc. (c) 2002

37. PLCS Core: Life Cycle PDM Capability (2)
AP239 has added:
Classification, supported by Reference data libraries
Product_as_individual (planned and realized)
Product breakdowns (system, physical, functional, zonal and hybrid)
Text based requirements (from AP233)
Extended property capability
Interfaces
Attachment_slot
Message, Envelope (similar to ENGDAT)
Information Rights
… A powerful capability for Life Cycle Configuration Management of Assured Product and Support Information
PLCS Inc. (c) 2002

38. Work Management modules
Work_record
Work_order +
Work_request
Product State
&
Usage
Product
Definition
Information
Work_
Definition
Activity
Activity Method
Work
Order
Work Request
Product_
as_realized
Activity_ as_realized
Resourced_
Activity
Resource_
Management
Support_
Provider
Resource_
as_realized
Resourced
Task Spec
Task_
Specification
Scheme
Required_
Resource
Resource_
Item
PLCS Inc. (c) 2002

39. PLCS uses Reference data
What is it?
Values for attributes that are agreed and defined in advance of use
E.g types of task, grades of people, types of products, types of document
E.g. Nato Stock Number – classifications
Why use it?
Because it improves reliability and effectiveness of exchange
Because it can be extended:
To add to the scope of the standard
To provide project specific capabilities
Because it supports re-use of values from existing standards
Idea proven in Oil and Gas industry
PLCS Inc. (c) 2002

40. AP239 – Data Exchange Sets DEXs are:
Subsets of the AP239 Information model
Selected to meet a specific data exchange need
Relevant modules
Supported 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 AP239
Data consolidation through time
Same DEX
Different DEX
PLCS Inc. (c) 2002

41. Current DEX developments
Product as individual
Product breakdown for support
Maintenance plan
Task set
Operational feedback
Fault states
Work Package Definition
Work Package Reporting
PLCS Inc. (c) 2002

42. Current situation (December 2004)
Activity Model published (available to all)
1750 requirements allocated to ~130 modules
Module development completed:
PDM Modules under publication as ISO Technical Specifications
PLCS modules under publication as ISO Technical Specifications
AP239 information model accepted as ISO Technical Specification
Draft International Standard ballot for Application Protocol successfully completed 13 September, with unanimous acceptance
Publication by ISO January hyperlinked CD-ROM product to follow
Development of first eight Data Exchange Sets nearing completion
Implementation activities are gaining momentum in Norway, Sweden, Finland, UK and US
PLCS Inc. (c) 2002

43. Product Life Cycle Support (PLCS) Unique Value Proposition
International Standard for product support information - based on the ISO standard for product data (STEP)
Complete product lifecycle – from concept to disposal
Single source of assured product and 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
Extensibility and tailoring through the use of Reference data libraries
This slide defines the unique aspects of PLCS - as opposed to the more general ‘goodness’ business benefits claimed by all software vendors about their products and services. These are specific to the PLCS Standard
PLCS is the only International standard for product support
PLCS is the only standard to address the complete product lifecycle
PLCS is the only standard to address the full range of product support requirements (content and transaction) - Integration of support related applications and databases using the PLCS standard will provide a single manageable source of assured product information.
PLCS standard provides independence of processes, applications, and proprietary data formats making integration a much simpler task
PLCS standards supports bi-directional information exchange and interoperability across multiple companies/departments/suppliers within an extended enterprise.
The use of Reference data provides the ability to quickly tailor the instantiation of PLCS to the unique requirements of the project
And finally, it is the first time that Governments, Contractors and Vendors have got together to develop a common standard
Customers, Contractors and Software Vendors
working together to develop and implement
a neutral data exchange standard for product support
PLCS Inc. (c) 2002

44. PLCS: relationship to other standards
Looking back
AP239 acknowledges a debt to all listed inputs
Current position
AP239 can use the data generated by current ILS standards
AP239 implementations will need resource to cleanse and enhance data generated by current standards (it’s not very good!)
AP239 enables, but does not force, much higher levels of data integration
The future
AP239, and other factors, will drive change in most current ILS standards (e.g. DEF STAN 00-60)
The pace and direction of this change depends on market factors
PLCS Inc. (c) 2002

45. Exploiting the benefits

46. Implementing PLCS
PLCS (a standardized information model) can be implemented in 3 ways:
As an integration architecture for a new product life cycle support management system (c.f. PIPPIN, EPISTLE, ISO 15926, NPDM)
As a mapping between systems (APIs) (LITS to RR CM system)
As a standardized data exchange capability (plus compliant software)
STEP technology supports all three and is language independent (Cobol, Java, C++, XML)
STEP is in production use, with proven benefits, for CAD, CAM and PDM systems
STEP has mainly been used to standardize data exchange
PLCS can also be used to promote further standardization via Reference Data (e.g. fault codes, skill grades)
PLCS Inc. (c) 2002

47. Implementing PLCS on a new program
Use PLCS/STEP formats to capture design information as it is generated in a way that support engineers can re-use
Develop Support Information in PLCS format
Less duplication – single assured source
Easy to present/deliver in any required form (e.g. Spec 1000D, XML, PDF)
Improved management of effectivity/applicability
Deliver a PLCS enabled maintenance management capability
Automatic upload from single assured source
The right data is available for maintainers (can be tailored to serialized item)
Improved feedback collection (report in the language used to specify, auto-complete)
Better in-service metrics
Faster learning
PLCS Inc. (c) 2002

48. Implementing PLCS for an existing program
Identify current information shortfalls or problems
Use the PLCS Activity Model to identify relevant data exchanges (arrows) that cross IT system boundaries, within and beyond your company
Implement appropriate DEXs, where there is a valid business case
Consider adopting PLCS for new data generated (changes, modifications, upgrades etc.)
N.B. Most current formats can readily be delivered from a PLCS integrated source. The latter is cheaper to build and easier to maintain.
What NOT to do – immediately abandon current systems (and standards) that meet business needs
PLCS Inc. (c) 2002

49. Norwegian pilot - New frigate programme
PLCS Inc. (c) 2002

50. PLCS to link five legacy support applications
UK MOD demonstrator
Scenario:
Ship damaged by fire
Compartment containing mixture of equipment due for maintenance, due for upgrade, or no longer available
Consolidation of planned and unplanned maintenance requirements into work programme
PLCS to link five legacy support applications
PLCS Inc. (c) 2002

51. Swedish pilot
The purpose of this pilot is to verify the possibility to use the PLCS data exchange sets to transmit information regarding assembly breakdowns, spares recommendations and maintenance plans for the Gripen Fighter aircraft according to the OASIS PLCS defined Data Exchange Sets (DEX001 and DEX005). The result of the study will be reported back to the OASIS community.
The study is a joint effort by a number of FMV projects and industry, funded by FMV. It will be carried out between mid September 2004 and January 2005.
PLCS Inc. (c) 2002

52. Future Plans

53. 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 AP239
Resources committed through national standards bodies
Also provides clear liaison to Systems Engineering development
Replace this slide with your own related to the content of the actual presentation
Slide title should be Agenda or Content or Presentation Route Map
PLCS Inc. (c) 2002

54. DEX Development and publication
Open-source infrastructure developed
Seeking more open participation
lower cost entry
Need enhanced links with other information standards development
Selected OASIS consortium as parent
Formed OASIS Technical Committee for “Product Life Cycle Support”
Open to all OASIS members
Operating under OASIS rules
Replace this slide with your own related to the content of the actual presentation
Slide title should be Agenda or Content or Presentation Route Map
PLCS Inc. (c) 2002

55. The OASIS Technical Committee
The purpose of the OASIS Product Life Cycle Support TC is to:
establish structured data exchange and sharing capabilities for use by industry to support complex engineered assets throughout their total life cycle
define, develop, test and publish OASIS Product Life Cycle Support DEX’s based upon ISO (STEP) Application Protocol 239 (Product Life Cycle Support).
liaise with ISO TC 184/SC4
coordinate with relevant OASIS Technical Committees
promote the use of OASIS Product Life Cycle Support DEX’s across industries and governments world-wide
PLCS Inc. (c) 2002

56. Join in an early implementation
The Challenge
The PLCS consortium has delivered the basic standard, and an infrastructure for exploiting it, and has closed down
Join in an early implementation
Join the OASIS Technical Committee to participate in DEX development
See and select PLCS
Contribute to further developments in ISO through your national standards body
Replace this slide with your own related to the content of the actual presentation
Slide title should be Agenda or Content or Presentation Route Map
PLCS Inc. (c) 2002

57. Product Life Cycle Support (PLCS) The Information Backbone for the Enterprise
Questions?
Answers!