An ontology for Systems Engineering based on ISO Semantic encoding of Systems Engineering information

Size: px

Start display at page:

Download "An ontology for Systems Engineering based on ISO Semantic encoding of Systems Engineering information"

Noel Newman
5 years ago
Views:

1 An ontology for Systems Engineering based on ISO Semantic encoding of Systems Engineering information EPC contractor in the Netherlands in the area of shipbuilding, infrastructure, building- and process industry. Leo van Ruijven Principal Systems Engineer Chairman Dutch standards committee Automation systems and integration (mirror TC184/SC4) Member ISO TC 184/SC4 Industrial data (ISO STEP, ISO 15926) Boardmember USPI (Uitgebreid Samenwerkingsverband Proces Industrie Nederland)

2 Agenda Interoperability issue in Systems Engineering projects. Principles of semantic encoding of information according to ISO Creating an ontology for SE applying the principle of semantic encoding enabling MBSE. A sample of a resulting taxonomy and set of relationships.

Actual issue concerning interoperability in projects delivering complex systems: How to create and exchange information so that each role can effectively do

3 Actual issue concerning interoperability in projects delivering complex systems: How to create and exchange information so that each role can effectively do its job Architect SE process Installation contractor Roles in a project Engineering company SE process SE process Client Sub contractor SE process Main contractor

4 Distinguishing layers with respect to information exchange (based on ISO 15926) Company a mapping portal Exchange of information portal mapping Company b Enterprise role ISO (Activity model) Organisations, roles, processes Scope presentation Scope/Domain Content Semantics ISO (Systems Engineering) ISO (Reference data) ISO (RDF statements) To be specified in a Information Delivery Manual Syntax N-quad, RDF/XML, Json (IDM) Storage Triple store or Graph database

Data-exchange of engineering data based on ISO

Neutral data exchange ISO 15926 mapping ICT / PLM SE

based statements SE process Company b Reference Data

5 Data-exchange of engineering data based on ISO Internet portal portal ICT / PLM mapping Neutral data exchange ISO mapping ICT / PLM SE process Company a Core model ISO Triple based statements SE process Company b Reference Data Library (RDL) Reference Model SE Ontology for Systems Engineering

6 Principle of semantic encoding of engineering information within ISO Deck crane B7 is classified as RDL:Pedestal Crane 2 Deck crane B7 has property Total weight deck crane B7 3 Total weight deck crane B7 is classified as RDL:Total Weight 4 Total weight deck crane B7 has magnitude Total weight deck crane B7 is quantified in RDL:Tonnes Statement-ID Lefthand object Relationship Righthand object Origins from ISO AP221 and STEPlib Subject: RDL item or instance of RDL item Examples of standardized relationships within ISO is a part of is quantified in is described by has property is initiated by is involved in is location of has magnitude is objective of. etc. Object: RDL item, instance of a RDL item or a value

7 Use of industrial Reference Data on class level based on RDF "A 'lifting device' that is a tower or derrick equipped with cables and pulleys that can lift or lower and move loads in multiple directions." RDL:Crane "The weight of a body in a specific reference system is the force which, when applied to the body, would give it an acceleration equal to free fall in that reference system" RDL:Weight "A weight that is a sum of the weights of identified parts of an assembly." RDL:PedestalCrane RDL:hasProperty RDL:TotalWeight RDL:isQuantifiedIn RDL:Tonnes "A crane that is mounted on top of a stationary, raised foundation (base, column, pillar)." subject - predicate - object Triple based statements using the Resource Description Framework (RDF) from the W3C consortium (arc node structure)

8 Sample of a concrete project data referring to Reference Data RDL:PedestalCrane RDL:TotalWeight myproject:deckcrane B7 400 myproject:total WeightDeckCrane B7 RDL:Tonnes

9 Applying the semantic encoding principle on process descriptions taken from ISO 15288; System Life Cycle Process (1) Source: ISO Stakeholder Requirements Definition Process: Stakeholder requirements are expressed in terms of a model that may be textual or formal, that concentrates on system purpose and behavior (in the context of the operational environment and conditions). Include in the context analysis the activities that users perform to achieve system objectives Define a representative set of activity sequences to identify all required services that correspond to anticipated operational and support scenarios and environments

10 Semantic encoding of ISO Stakeholder requirement definition process Purpose Why? Is base for What? Objective Is defined by Is realized by Validation Stakeholder requirement Process Scenario (activity sequence) How? Service requires Scenario activity Function Human activity

11 Applying the semantic encoding principle on process descriptions taken from ISO 15288; System Life Cycle Process (2) Source: ISO Requirements Analysis Process: Transform the stakeholder requirement-driven view of desired services into a technical view of a required product that could deliver those services Build a representation of a future system that will meet stakeholder requirements and that does not imply any specific implementation. It results in measurable system requirements. Define the required interactions between the system and its operational environment in terms of interface constraints Define each function that the system is required to perform. The required characteristics, attributes, and functional and performance requirements for a product solution are specified

12 Semantic encoding of ISO Requirement analysis process (also representative for the architectural design) stakeholder is involved in interaction is involved in environment supports port Functional requirement Is of type f interface f Service Performance requirement System requirement is a specification for Functional object is performed by Technical function results in is realized by Is constrained by Constraint Is bases for Technical Solution has property property Is evidence for Stakeholder requirement

13 Applying the semantic encoding principle on process descriptions taken from ISO 15288; System Life Cycle Process (3) Source: ISO Operation Process and Maintenance Process: Services that meet stakeholder requirements are delivered. Services meeting stakeholder requirements are sustained. Assign personnel to operate the system Operator knowledge, skill and experience requirements guide the personnel selection criteria Monitor the system operation to confirm that service performance is within acceptable parameters Maintenance constraints are provided as inputs to requirements Define the constraints on system requirements that are unavoidable consequences of the maintenance strategy.

14 Semantic encoding of ISO operation and maintenance process Stakeholder requirement Is bases for System requirement is a specification for Service is monitored by Is bases for Strategy Technical function Human activity is defined in Procedure is realized by Role is fulfilled by Party

15 A resulting generic model for MBSE System requirement is a specification for is evidence for is a specification for is base for interaction port interface Functional object results in property supports Technical Solution has property Is involved in Is performed by is realized by is constrained by stakeholder environment Technical function Physical side of the system Stakeholder requirement objective Process Service is realized by Human activity Role party is realized by is fulfilled by is base for requiers is monitored by Purpose Process side of the system Scenario activity Scenario (activity sequence) procedure Is defined in strategy

16 rdfs:subclassof rdfs:subclassof RDL:Status RDL:Characteristic RDL:Material RDL:SpatialLocation RDL:FunctionalPhysicalObject RDL:State RDL:MaterializedPhysicalObject RDL:PhysicalObject RDL:Property RDL:Scale RDL:TemporalWholePart RDL:Stage RDL:FailureMode RDL:Risk RDL:Deviation RDL:LifeCycleStage RDL:Condition RDL:System RDL:Port RDL:Baseline RDL:PropertySpace RDL:PropertyQuantification RDL:Shape RDL:Interface RDL:SystemElement RDL:Feature RDL:SingleDimensionalNumber RDL:MultiDimensionalNumber RDL:UnitOfMeasure RDL:PropertyRange RDL:Objective RDL:Process RDL:Function RDL:Interaction RDL:Activity RDL:Measure RDL:Service RDL:Person RDL:Specification RDL:InformationRepresentation RDL:InformationObject RDL:Organisation RDL:Role RDL:Collection RDL:Discipline RDL:Party RDL:Organism RDL:Document RDL:Identification RDL:Requirement RDL:Event RDL:Milestone RDL:Thing rdfs:subclassof Sample of a RDL for SE

17 Fragment of the initial set of SE relationships derived from the ontology Part 11 relation class name Reverse name Definition Domain Range complies with concerns characteristic defines compliance criteria a specialization where the subject shall be conformant to for the specification of the object. characteristic is concern of A class of relationship with signature where a requirement specification concerns a system characteristic. thing information object property information object concerns stage stage is concern of A class of relationship with signature where a requirement specification concerns a system life cycle stage. information object period in time is part of A relationship that denotes an assembly_of_individual is an arrangement_of_individual that indicates that the part is connected directly or indirectly to other parts of the whole. The parts and wholes are super-molecular objects. contributes to the realization of is partially realized by A relationship where the work package deliverable item contributes to the delivery of a system, functional physical object, or materialized physical object. creates is created by A relationship where a contract requires the delivery of a contract deliverable. defines the delivery of delivery is defined in A relationship where a plan defines one or more workpackages in order to achieve an objective deviates from has deviation A relationship where a contract deviation defines the deviation of a contract follows route is route for A class of relationship where an instance of a type of connection follows a instance of a type of route has acceptance criterion is acceptance criterion for A relationship where a verification activity has acceptance criteria by which the outcome is to be judged. thing thing activity activity state physical object activity thing physical object thing information object activity physical object information object

18 Findings and conclusions The approach of ISO can cope with the richness and dynamics of Systems Engineering information on class level and instance level as well. The developed ontology for SE consist of a set of integrated information models using approx. 300 different entities and 150 different kind of relationships. The presented ontology has been successfully applied in complex infra structure projects covering the full system life cycle, improving interoperability. There is a gap in the availability of software tools that can supports ontology based data integration standards like ISO Implementation of the ISO RDF Named Graph approach by means of a triple store or graph database has shown to lead to effective data-integration solutions, improving interoperability.

19 Questions? What to do How to define ISO ISO System Life Cycle Processes Life Cycle Data Integration Systems Engineering Ontology and data-exchange enabling MBSE

Ontology for Systems Engineering

Ontology for Systems Engineering Model-based Systems Engineering Leo van Ruijven Manager Technology Development Croon TBI Techniek Rotterdam, the Netherlands Leo.vanruijven@croon.nl Abstract This paper