OASIS Product Life Cycle Support (PLCS) TC
Completed:The Technical Committee was closed by TC Administration on 17 April 2017 and is no longer active. Archives of its work remain publicly accessible and are linked from this page. OASIS appreciates the efforts of all those who participated in this TC.
Collaborating on the deployment of an international standard for product data exchange (ISO 10303) to support complex engineered assets from concept to disposal
Table of Contents
- Technical Work Produced by the Committee
- External Resources
- Mailing Lists and Comments
- Additional Information
Boeing and Eurostep release joint report - A new approach to PLCS Web Services Boeing and Eurostep have investigated a new approach to developing standardized PLCS Web Services. The basic concept is that PLCS DEXs should be developed using mainstream technology. Resulting in cheaper, simpler and faster development and automatic generation of DEX based PLCS Web Services. The reduced complexity will allow more people to contribute to the success of PLCS. Download the report Please join the LinkedIn group PLCS Solutions where there will be more about PLCS. -- Dr Rob Bodington
View the Gartner presentation on PLCS given at PDT Europe 2009. Gartner Presentation
View other PDT Europe 2009 presentations PDT Europe 2009 Presentations
View PDT Europe 2010 presentations PDT Europe 2010 Presentations
View the Official PLCS Presentation
The purpose of the OASIS Product Life Cycle Support (PLCS) TC is to establish structured data exchange and sharing to support complex engineered assets throughout their total life cycle.
These Data Exchange Specifications (DEX's) are based upon ISO 10303 (STEP) Application Protocol 239 (Product Life Cycle Support). The OASIS PLCS TC is responsible for defining, developing, testing and publishing of OASIS PLCS DEX's, and for liaison with ISO TC 184/SC4.
PLCS Video Jotne EPM Technology has created a video explaining the PLCS Data Exchange Specifications (DEXs). Click here to view.
STEP/PLCS Use CasesMicrosoft has recently published a case study with Share-A-space success at BAE Systems - "BAE Systems Creates New Revenue Stream with Customer Service Portal with Share-A-space". Click here A previous Microsoft case from June 2008 is also available - "Defence Manufacturer Cuts Collaboration Costs with Innovative Supply Chain Solution" Click Here
PLCS Related White Papers
The CIMdata Commentary on Jotne EPM’s EDMmodelServer™(plcs)—Using PLCS to Harmonize Product Development and Support Environments Click here for a copy.
The Aerospace Industries Association (AIA) recommends adopting PLCS. "Engineering Data Interoperability - A Standards Based Approach" was published with the recommendation on 7 March 2008. Click here for a copy. "Re-engineering the Aftermarket with PLCS" - new white paper on business benefits In co-operation with John Stark, the leading independent management and technology consultant in PLM, Eurostep has written a white paper on the business benefits of implementing PLCS. Recent changes in the business environment have opened new opportunities in the aftermarket. Successfully exploiting these trends presents many challenges, including both new commercial relationships and management of huge volumes of product data. The new approaches to meeting the challenges that are discussed in this paper will enable OEMs to provide effective low-cost global support for long-life complex engineered products such as airplanes, power plant, heavy vehicles, industrial machinery and equipment, elevators, trains, and weapon systems; as well as less complex systems. A coherent information environment in which the necessary data are available to all participating actors is a prerequisite for efficient product support. PLCS can be thought of as a new “world map” for product support. Like any new map, PLCS contains much that is familiar – a maintenance task is still a maintenance task – and many new discoveries. Just like a map, PLCS can be used in different ways. One is to solve business problems by automating data exchange between existing systems. PLCS can also be used to support a major update of processes across an entire organization. This white paper written by John Stark in co-operation with Eurostep describes the standard itself and explains how an organization can implement PLCS to achieve tangible business benefits. Examples are provided of PLCS projects in some well known organizations. Download the white papers, "Standards-based PLM: Re-engineering the Aftermarket with PLCS, Part 1 Business Benefits" and "Re-engineering the Aftermarket with PLCS: Part 2 Technologies and Deployments". Click on John Stark White Papers in the left frame.
NIST Releases Lifecycle Management Standards Report The National Institute for Standards (NIST) has just released a study NISTIR 7339, "Analysis of Standards for Lifecycle Management of Systems for US Army --- a preliminary investigation". The study highlights the importance of ISO 10303, the Standard for Exchange of Product Model Data (STEP). The PLCS TC is working closely with ISO 10303 to develop Data Exchange Specifications. Download the NISTIR 7339 report.
Note for Developers of ISO 10303-239 (PLCS) Data Exchange Specifications The OASIS Product Life Cycle Support Technical Committee develops Data Exchange Specifications [DEXs], and their supporting infrastructure using the International Standard ISO 10303-239:2005(E) Industrial automation systems and integration — Product data representation and exchange Part 239: Application protocol: Product life cycle support.
The OASIS PLCS Technical Committee will consider any Data Exchange Specifications, Capabilities, and Reference Data developed by outside projects for adoption by OASIS. All material submitted should comply with the OASIS TC established process. Material will be reviewed by the OASIS PLCS TC Technical Oversight Group (TOG) prior to submission for acceptance by the PLCS TC members. If material successfully passes the OASIS TC ballot, it will be submitted to the OASIS membership for ballot and publishing as an OASIS standard.
To minimize the risk of non-compliance and consequent rework, projects or organizations developing Data Exchange Specifications based on ISO 10303-239 are advised to contact one or more of the following PLCS TC development experts:
Tor Arne Irgens (Norwegian Defense)
Rob Bodington (Eurostep)
Leif Gyllström (AerotechTelub AB)
Chris Kreiler (ManTech (e-IC)) PLCS TC Secretariat
Tim Turner (LSC Group)
- ISO TC184/SC4 (Tim King)
- ASD (formerly AECMA) (Carl-Johan Wilen)
- POSC/Caesar (Nils Sandsmark)
- GEIA (Jim Colson)
Teams have been formed to complete the work offered to OASIS by the PLCS consortium, and DEX development is well underway. Significant progress is being made on the first eight DEX. However, there is still much to be done to finalise the Data Exchange Specifications based on the ISO PLCS standard, and additional resources would be welcomed by the DEX Teams, to support the development, documentation and testing of the final specifications.
PLCS uses an open source development environment based on XML and XSL scripts to facilitate the creation of compatible and interoperable specifications. There are opportunities for technical support with XSL expertise to support Infrastructure Maintenance.
PLCS Portal and DEX Library Website Link
Members of the PLCS TC may download complete DEX and STEP files from the PLCS resources web site developed by Eurostep. You will need a user name and password. Please contact the Secretariat if you have forgotten how to log in. The URL for the PLCS Portal is: http://www.plcs-resources.org/
Reference Data Instructions
Members of the PLCS TC may download Reference Data Instructions. These were taken from the "Help" section in DEXLib. Please contact the Secretariat if you have any questions. The document is posted under Documents. The document may be downloaded directly from here PLCS Guide for Reference Data .
For technical assistance regarding this OASIS TC web page, contact email@example.com.
Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.