the story of the plcs standard. - pdt europe

2018 © Eurostep Group

Why PLCS is a good fit for the MBE and the MBEE (Model Based Extended Enterprise) and Systems Lifecycle Management and where it is in use

The story of the PLCS standard.

Nigel Shaw


Introduction

• Nigel Shaw• Managing Director for Eurostep Limited since 1995

• Chair of ISO TC184 SC4 Editing committee for STEP (ISO 10303) first release

• Lead modeller for the NATO CALS Data Model

• Technical Lead for PLCS, Inc.

• And more…


What is PLCS?


Boeing’s Standards Radar Chart

PLCS


Product Life Cycle Support (PLCS) ISO 10303-239

• 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, Inc. closed down late 2004

• Standard published by ISO in 2005

• Edition 2 published in 2012

• 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


Before PLCS there was the AECMA standards and …

The STEP standard

Started 1984

First release of

12 parts late 1994

The NATO effort

to combine scopes

of S1000D, S2000M

and 1388/00-60


FinnishDefence Forces

Product Life Cycle Support (PLCS)Membership – Nov 2002

Supported by: and

Each member

provided both

funding and

expert effort


The Key Business ProblemHow to keep the information needed to operate and maintain a

product aligned with the changing product over its life cycle in a heterogeneous organization, process and system environment?

Tools

Test

Equipment

Support

Facilities

Consumables

Software

Transportation

Spares

Storage

Requirements

Training

Product Definition

Information

Maintenance

Schedules

Product

Feedback


Product Life Cycle Support (PLCS)Inputs to the Initiative

NATO

PilotProject #1

PLCS

ISO 10303

AP239

ISO

15288OMG

STEP

Mil Spec

CM2549

ATA

Effectivity

AP208

POSC/

Caesar

FMV

CTG2

AP214

ISO

TC184/SC4

WG3/T8

PWI

PDM

Schema

AP 233

PLIB

Def Stan

00-60

+ Others

NCDM

Mil Spec

1388

AECMA

1000D

2000M

AP203

Commentary:

This slide was created

early in the

development of PLCS.

The set of input

standards goes

beyond ILS


• ISO 10303-239 edition 1 containing:

• Data Model

• Activity Model

• DEXlib containing:

• Example DEX

• Reference data

• Autogenerated XML schemas (per ISO 10303-28)

PLCS deliverables


What has happened since 2005?

A potted history of PLCS


AP239e3 activity

PLCS key developments

2005 2010 2015

ISO 10303-239: 2005

DEXlib

ISO 10303-239: 2012 ISO 10303-239: 2019

PLCS V 1.0Committee Specification 01

PLCSlibConcerns over file size,

xml schema

complexity, EXPRESS

as a language

Systems

EngineeringISO 10303-233: 2012

STEP future architecturePLCS

Concept Model

Uses SysML

to define mappings

Into DEXs

PLCS Technical Committee

ASD DEXsPLCS

Platform Specific

Model (PSM)

In SysML

+ XML Schema


PLCS key developments plus some related standards

AP239e3 activity

2005 2010 2015

ISO 10303-239: 2005

DEXlib

ISO 10303-239: 2012 ISO 10303-239: 2019

PLCS V 1.0Committee Specification 01

PLCSlibConcerns over file size,

xml schema

complexity, EXPRESS

as a language

Systems

EngineeringISO 10303-233: 2012

STEP future architecturePLCS

Concept Model

Uses SysML

to define mappings

Into DEXs

PLCS Technical Committee

ASD DEXsPLCS

Platform Specific

Model (PSM)

In SysML

+ XML Schema

GEIA 0007 GEIA 0007b

ASD S5000FASD S3000L 1.0 ASD S3000L 1.11388

00-60 00-600

SX000i 1.0


• Like DEXlib but driven from SysML models

• Starting point was translation into SysML from Express

• Some model revision to make implementation easier

• Initial harmonization with AP242 performed

• Support for DEX definition using SysML with computer sensible mappings described via parametric diagrams

• Tools ensure conformance to the underlying model

• More help and background information

• Snap shot of PLCSlib published as the OASIS PLCS TC Committee specification

• PLCS PSM

• Decided to create a single XML schema

• Contrast with one per DEX

• Works with current XML tools

• Much smaller file sizes

• Greater use of encapsulation

PLCSlib - see http://www.plcs.org/plcslib/plcslib/


Why use PLCS now?

Business cases


There are many potential business cases for using PLCS

• Standard information interfaces for contracting

• Maintaining an Assured Product and Support Information set

• Information integration/linking across disciplines/areas/tools

• Digital Thread (including Digital Twins)

• Collaboration Hub core model (Eurostep)


• The problem scenario:

• Defence systems come with their own IT

• Data needed for operations is locked into that IT

• And may never be available for Defence organization use

• Each system supplier has their own approach

• Each supplier contract is unique and there is little or no commonality between suppliers

• The objective

• Suppliers use an information delivery mechanism defined on the basis of a standard

• All suppliers of equivalent systems are treated the same and subject to the same contracted requirements

• Data delivered from suppliers can be imported via a single mechanism

• No system specific IT is needed

• The same mechanisms can be used to supply data from the Defence Organization to its suppliers

Standard information interfaces for contracting

This is the approach being taken by Sweden’s FMV and France’s DGA, using PLCS DEXs to contract.

It has also been used between Norway’s NDLO and BAE Systems Hagglunds.

MINISTÈRE DE LA DÉFENSE

SIMMT - DTE Focal point Slide N°23 / 32PDT Europe 2014 - 15 October 2014

Généralisation de PENCIL & intégration dans SIM@T

LECLERC

VHM

CAESARVBCI

PPT

Commandes

CR IT, Commandes

Relevé de potentiels

Assistance technique

CR IT, Commandes


Assistance technique.dat

.docCR IT, Commandes


.xls

.doc

SACRAL

SOPRANO

Logiciels

pilotage

CHEOPS

CREDO

SILCENT

SAGEE

CONCERTODRHAT

STOCKEURS

SICS

CIMD

EMA

SIOC

CFT

EMAT

CHORUS MINEFINSPA COMMIT

NNO

Disponibilité

Consommation de

potentiels

Données

de référence

Ordres de

magasinage

Pièces

disponibles

Localisation

Optimisation des parcs

Référentiel des

personnels

Dispositif

organique

Finances

Patrimoine

PEN CILPEN CIL


• This is exactly in line with the original problem statement:

How to keep the information needed to operate and maintain a product aligned with the changing product over its life cycle in a heterogeneous organization, process and system environment?

• Assured Product and Support Information (APSI) is a term defined in the PLCS Activity Model

Maintaining an Assured Product and Support Information set

Eurostep have an active project concerning Naval

Ships

BAE Systems have also implemented PLCS (by

autogeneration) for their Titanium system


Information integration/linking across disciplines/areas/toolsRequire Make Support

Use

rS

yst

em

Su

pp

lier

Main

ten

ean

ce

Su

pp

lier

Relationships that

cross over between

data sets of systems

are shown as

By holding data within

the PLCS model we can

instantiate and use such

relationships for tracing

and change management


• The digital thread refers to the communication framework that allows a connected data flow and integrated view of the asset’s data throughout its lifecycle across traditionally siloed functional perspectives.

• The digital twin refers to a digital model of a particular asset that includes design specifications and engineering models describing its geometry, materials, components and behavior. More important, it also includes the as-built and operational data unique to the specific physical asset that it represents. • For example, for an aircraft, the digital twin would be identified to the physical product unit

identifier which is referred to as the tail number. The data in the digital twin of an aircraft includes things like specific geometry extracted from aircraft 3D models, aerodynamic models, engineering changes cut in during the production cycle, material properties, inspection, operation and maintenance data, aerodynamic models, and any deviations from the original design specifications approved due to issues and work-arounds on the specific product unit.

What is the Digital Thread

Taken from: http://www.industryweek.com/systems-integration/demystifying-digital-thread-and-digital-twin-concepts


PLCS Objective – Digital thread through the life cycle

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?

, manufacture

V

, simulate

Product Definition

Information

Tools

Test

Equipment

Support

Facilities

Consumables

Software

Transportation

Spares

Storage

Requirements

Training

Product Definition

Information

Maintenance

Schedules

Product

in Focus

Feedback

ISO 10303-239Product Definition

Information

Feedback

including modelsfor MB(S)E


Needed for a Digital Thread

• Distinguish between designs and actuals (individuals).

• Different BOM views (such as as-designed, as-manufactured and as-maintained) of a product, including the actuals, and link/trace between them.

• Different breakdown views (such as physical and functional breakdowns) of a product and link between them and to different BOM views.

• Different properties and record their values over time or against different views.

• Requirements, their allocation, tracing, Verification and Validation.

• Recording of processes and other actions applied to the product (or done by the product).

• Handling subsidiary products such as tools and equipment and their use and properties.

• Associated documents and other information, such as CAD and simulation models, related to the product and any subsidiary products.


Already included in the PLCS model

✓Distinguish between designs and actuals (individuals).

✓Different BOM views (such as as-designed, as-manufactured and as-maintained) of a product, including the actuals, and link/trace between them.

✓Different breakdown views (such as physical and functional breakdowns) of a product and link between them and to different BOM views.

✓Different properties and record their values over time or against different views.

✓Requirements, their allocation, tracing, Verification and Validation.

✓Recording of processes and other actions applied to the product (or done by the product).

✓Handling subsidiary products such as tools and equipment and their use and properties.

✓Associated documents and other information, such as CAD and simulation models, related to the product and any subsidiary products.

PLCS DEX CASE STUDY

Business Benefits and Promises applying a Model Based Engineering environment with data and information in focus

Mats E NilssonHead of Technical InformationBusiness Area Saab Kockums 2018-02-19

Internal & External Information Management

- an operational view

EXTENDED DIGITAL THREAD AND DIGITAL SHIP

- BASED ON PLCS, DEX AND S1000D

Common standard and supporting database through the product life cycle

CustomerSupplier

DEX:es:

• FaultDefinition

• FunctionalStructure

• ItemDefinition

• ItemOfSupplyIndividual

• MaintenanceReport

• OperationalData

• PhysicalStructure

• Requirement

• TaskMethod

• TechnicalPublication

Pilot test scenarios

S01-S04

PLM

Aveva ERM


Where else is there a life cycle element?

Other domains


Energy

Slides as presented PI Congress 2014


Road and Rail in Sweden (Acando & Eurostep for Trafikverket)

Managing asset data for road and rail networks in Sweden

Not what PLCS was aimed at but still complex products with long life cycles and on-going maintenance


KiraDigi “Lifecycle API for BIM” pilot project:

RES

T A

PI

RES

T A

PI

IFC

BIM models

Cloud deployment

Design, implementationAsset

Management

x

Owner

Goal


Työn sisältö


and then questions!

Conclusions


The bigger picture

Internet

Of Things

Big

Data

Machine

Learning

Changing

Product

Model Based

Systems

Engineering

Digital

ThreadSimulation

History

Logistic

Support

Analysis

Use History

+ Feedback

Digital

Twins


The bigger picture

Internet

Of Things

Big

Data

Machine

Learning

Changing

Product

Model Based

Systems

Engineering

Digital

ThreadSimulation

History

Logistic

Support

Analysis

Use & Maintenance

History + Feedback

Digital

Twins


Conclusions

• The core data model within PLCS has stood the test of time and been successfully applied beyond its original domain

• The need for a standard like PLCS is becoming clearer as the push for the digital thread grows

• To maintain a Digital Thread through life will need a standards basis

• PLCS provides the life-cycle view that many existing standards lack

• And can be used with alongside those standards to add history capabilities

the story of the plcs standard. - pdt europe

Documents