PLCS Tutorial in 30 minutes! NASA ESA PDE 2009 Nigel Shaw, Eurostep Limited C O P Y R I G H T E U R O S T E P G R O U P
What is PLCS ? ISO 10303-239 Published 2005 Part of STEP Product Life Cycle Support Effectively an ISO standard for PLM content C O P Y R I G H T E U R O S T E P G R O U P
Presentation menu - PLCS Why? Who? Activity Data Information DEXs C O P Y R I G H T E U R O S T E P G R O U P
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 Product Definition Transportation in Focus Information Consumables Maintenance Schedules Feedback Software Tools Spares Test Training Equipment Support Storage Facilities Requirements C O P Y R I G H T E U R O S T E P G R O U P
Usage Maintenance Plan Maintenance Maintenance Schedule Requirements Maintenance Maintenance Task Task perfomance Maintenance Analysis Maintenance Fault state Actual Task Planning definitions Fault states Extended Enterprise Types Individuals LSAR Change Management As-maintained Spare Parts Configuration Design As-built Design Configuration Location Requirements Management Manufacturing Individual BOM Configuration Design Analysis Domain Definition Definitions (CAD, etc) C O P Y R I G H T E U R O S T E P G R O U P
Product Life Cycle Support (PLCS) Membership – Nov 2002 Finnish Defence Forces Supported by: and C O P Y R I G H T E U R O S T E P G R O U P
OASIS PLCS Technical Committee PLCS, Inc. disbanded and handed over to the relevant ISO committee and to the OASIS PLCS Technical Committee Key priorities identified in the OASIS PLCS TC » DEX publication − Aviation maintenance and Task set » Further DEX development − Support for business DEXs » ISO 10303-239 second edition » Implementers Forum » Web services standardization C O P Y R I G H T E U R O S T E P G R O U P
THE PLCS ACTIVITY MODEL C O P Y R I G H T E U R O S T E P G R O U P
PLCS Activity Model USED AT: AUTHOR: PLCS, Inc DATE: 07/11/2002 WORKING READER DATE CONTEXT: PROJECT: ISO 10303-239 Annex F REV: 15/10/2003 DRAFT TOP RECOMMENDED NOTES: 1 2 3 4 5 6 7 8 9 10 PUBLICATION operating life cycle VIEWPOINT: The life-cycle owner who PURPOSE: To represent the activities and schedule directive * acquires the product-in-focus and strives to information flows supported by Application Protocol 239 maximise value over the complete life cycle Product Life Cycle Support (PLCS). of the product, by taking whatever actions The set of products to be supported is known as are necessary to deliver the required the "product in focus" or PIF. operational capability at minimum life cycle cost. product needing support supported product support element disposed element allocated support requirements APSI and related information rejected issue or change transaction replies Provide through life support for product transaction request feedback information to system operator * product & support element information operator feedback * request to life cycle owner change directive information from other systems £0 0 NOTE 2: All tunnelled arrows in this model NOTE 1: Dashed ( - - - - ) arrows apply to all decompositions of the applicable represent physical items (blue box. where diagrams are reproduced in colour). All other NOTE 3: APSI = assured product & arrows represent information. support information standard support information technology service or commercial infrastructure infrastructure transaction set NODE: TITLE: Provide through life support for product NUMBER: A-0 C O P Y R I G H T E U R O S T E P G R O U P
C O P Y R I G H T E U R O S T E P G R O U P
C O P Y R I G H T E U R O S T E P G R O U P
Short path - Short path C O P Y R I G H T E U R O S T E P G R O U P
Long path - Long path - C O P Y R I G H T E U R O S T E P G R O U P
THE PLCS DATA MODEL C O P Y R I G H T E U R O S T E P G R O U P
PLCS Data model C O P Y R I G H T E U R O S T E P G R O U P
The PLCS Data model » What follows is a very high level view! C O P Y R I G H T E U R O S T E P G R O U P
Product Product structures Part Assignments Product _relation View_relation Version_relation related related related relating relating relating Product Product _version Product _view_definition view_of of_ product in_context Context Person_or_ Property Representation Classification ID_alias Date_time Effectivity Organization C O P Y R I G H T E U R O S T E P G R O U P
Types of Products System Functional Requirement Part Interface Slot Document Breakdown Breakdown Product _relation View_relation Version_relation related related related relating relating relating Product Product _version Product _view_definition view_of of_ product in_context Context Person_or_ Property Representation Classification ID_alias Date_time Effectivity Organization C O P Y R I G H T E U R O S T E P G R O U P
Product individual System Functional Requirement Part Interface Slot Document State Breakdown Breakdown Product _relation View_relation Version_relation related related related relating relating relating Product Product _version Product _view_definition view_of of_ product in_context Context Product_individual observed_ product Observation observed_state actual_state Product _individual_ State version expected_state Planned_ Product Realized_ Product Person_or_ Property Representation Classification ID_alias Date_time Effectivity Organization C O P Y R I G H T E U R O S T E P G R O U P
Maintenance Plans, System Functional Schedules, Job Cards, Requirement Part Interface Slot Document Breakdown Breakdown Work Request/Order Task Product _relation View_relation Version_relation structure related related related relating relating relating required_ product Activity_method Product Product _version Product _view_definition view_of utilizes of_ product in_context Context Product_individual method_used Scheme observed_ product Observation structure schedule observed_state actual_state operates_on Product _individual_ Activity State version utilizes expected_state directive start Planned_ Product Realized_ Product Date_time finish start_state end_state in_response_to observation_consequence Work_order Work_request Person_or_ Property Representation Classification ID_alias Date_time Effectivity Organization Justification Condition Skill C O P Y R I G H T E U R O S T E P G R O U P
Further details System Functional - Projects / Contracts Requirement Part Interface Slot Document Breakdown Breakdown - Location - Messages handles Project Task Product _relation View_relation Version_relation has structure related related related specifies relating relating Contract relating required_ product Activity_method Product Product _version Product _view_definition view_of utilizes of_ product in_context Context Product_individual method_used Scheme observed_ product Observation structure storage schedule Location observed_state actual_state operates_on Product _individual_ Activity State version utilizes expected_state directive start Planned_ Product Realized_ Product Date_time finish start_state end_state in_response_to observation_consequence Work_order Work_request Person_or_ Property Representation Classification ID_alias Date_time Effectivity Organization Message Justification Condition Skill Envelope C O P Y R I G H T E U R O S T E P G R O U P
DATA EXCHANGE SPECIFICATIONS C O P Y R I G H T E U R O S T E P G R O U P
DEXs (Data Exchange Specifications) » PLCS has a large scope » Need to be able to contract for smaller scopes − With more detailed descriptions and guidance » Need to (perhaps) be able to claim conformance to a scope − Most systems do not cover all the scope » Hence Data Exchange Specifications: − Some generic e.g. Aviation Maintenance, Task Set − Some specific for business LOGSA developed DEXs Norwegian Defence UK MOD » All found in DEXlib − (see www.plcs-resources.org) C O P Y R I G H T E U R O S T E P G R O U P
Summary » PLCS is an ISO standard designed to handle a rich data set concerned with complex products through life − Enable exchange of data between systems and organizations − Enable better data (change) management » It is not defense specific but was established to meet defense needs » It has been designed to be extensible and flexible C O P Y R I G H T E U R O S T E P G R O U P
More information » PLCS: − ISO committee: ISO TC184/SC4 − OASIS committee » http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=plcs − Community » www.plcs-resources.org − Includes links to DEXlib » Eurostep − www.eurostep.com » The presenter − Nigel Shaw + 44 1745 582008 − nigel.shaw@eurostep.com C O P Y R I G H T E U R O S T E P G R O U P
Recommend
More recommend
