ISO/TS 15926-11:2023 産業オートメーション システムと統合 — 石油およびガス生産施設を含むプロセス プラントのライフサイクル データの統合 — Part 11: RDFS 手法に基づく参照データの産業利用の簡素化 | ページ 6

3.1.1

asset

any item, thing or entity that has potential or actual value to an organization

[SOURCE:ISO 55000:2014, 3.2.1, modified — Notes 1 to 3 to entry were deleted.]

3.1.2

attribute

quality or feature of something

3.1.3

blank node

bn

node in a resource description framework (RDF) graph representing a resource for which a literal is not given

Note 1 to entry: The resource represented by a blank node is also called an anonymous resource. According to the RDF standard W3C RDF-1.1,^[16] a blank node can only be used as subject or object of an RDF triple.

3.1.4

constraint

thing that limits something, or limits one’s freedom to do something

3.1.5

data

representation of information in a formal manner suitable for communication, interpretation, or processing by human beings or computers

[SOURCE:ISO 10303‑1:2021, 3.1.29]

3.1.6

designing

activity of developing by creating, planning, calculation, or laying out for a predetermined purpose

3.1.7

domain

set of all possible independent values the relationship can take

Note 1 to entry: It is the collection of all possible inputs (the “left-hand” of a relationship).

3.1.8

engineering

activity of designing or producing by methods of technical sciences

Note 1 to entry: During the activity, the properties of matter and the sources of energy in nature are made useful for human beings in structures, machines, and products.

3.1.9

engineered item

type of equipment created by specific and unique engineering and specifications, developed with a supplier or manufacturer

Note 1 to entry: An engineered item has a unique identifier (UID).

3.1.10

engineering data

data that represents the design and or engineering of a system or a system element

Note 1 to entry: The scope can be limited to a specific discipline (electrical, mechanical, civil), however after integrating all engineering data obtained from engineering tools, the result should represent the integrated design in a consistent way, which implies appropriate quality and harmonization of the data, obtained from the various tools.

3.1.11

enterprise

any private or public business or company

3.1.12

entity

something that exists separately from other things and has its own identity

3.1.13

enumeration

complete, ordered listing of all the items in a collection

Note 1 to entry: The term is commonly used in mathematics and computer science to refer to a listing of all of the elements of a set.

3.1.14

facility

permanent, semi-permanent, or temporary commercial or industrial property built, established, or installed for the performance of one or more specific activities or functions

3.1.15

functional requirement

requirement defining either the functional capabilities or behaviour, or both, that a product shall have

3.1.16

interoperability

ability of effective interaction between systems based on the exchange of information

Note 1 to entry: Systems can be computerized systems or enterprises.

3.1.17

information

facts, concepts, or instructions

[SOURCE:ISO 10303‑1:2021, 3.1.41]

3.1.18

formal syntax

specification of the valid sentences of a formal language using a formal grammar

Note 1 to entry: A formal language is computer-interpretable.

[SOURCE:ISO 8000-2:2022, 3.9.1, modified — Notes 2 and 3 to entry were deleted. EXAMPLES 2 and 3 were deleted.]

3.1.19

model

simplified description, especially a mathematical one, of a system or process, to assist calculations and predictions

3.1.20

model based systems engineering

MBSE

formalized application of modelling systems engineering information

Note 1 to entry: The application of modelling supports system requirements, design, analysis, verification and validation (V&V) activities with their mutual relationships, beginning in the conceptual design phase and continuing throughout development and later life-cycle phases.

3.1.21

resource description framework graph

RDF graph

3.1.22

resource description framework triple

RDF triple

atomic data entity in the resource description framework (RDF) data model

Note 1 to entry: An RDF-triple represents a relationship between the objects or data that it links.

[SOURCE: W3C Recommendation 2014]^[16]

3.1.23

resource description framework statement

RDF statement

statement stating facts, relationships and data by linking resources of different kinds

3.1.24

reference data

facility life-cycle data that represent information about classes or individual things which are common to many facilities or of interest to many users

[SOURCE:ISO 15926‑1:2004, 3.1.18, modified —"process plants" replaced by"facilities".]

3.1.25

range of relationship

set of all possible dependent values the relationship can produce from the domain values

Note 1 to entry: The domain values are in the “right-hand” of a relationship.

3.1.26

semantics

study of meaning, concerned with the relationship between signifiers that people use when interacting with the world, and the things in that world that these signifiers denote

Note 1 to entry: The goal of semantics is the creation of a common understanding of the meaning of things, helping people understand each other despite different experiences or points of view.

3.1.27

semantic encoding

concept encoding

technique of replacing natural language terms in a message with identifiers that reference data dictionary entries

Note 1 to entry: By applying semantic encoding to data, an organization creates a basis for portable data by ensuring the semantics of the data are explicit.

Note 2 to entry: Semantic encoding is necessary to create characteristic data ここで, the replaced natural language terms are properties (for each of which the data set includes a corresponding value).

[SOURCE:ISO 8000-2:2022, 3.9.2]

3.1.28

semantic data modelling

development of descriptions and representations of data in such a way that the latter’s meaning is explicit, accurate, and commonly understood by both humans and computer systems

Note 1 to entry: In semantic data modelling, all concepts used to model a system are explicitly defined by ontologies, capturing the “meaning” of data with all its inherent relationships in a single graph.

3.1.29

statement

information that is regarded as indivisible and which is the case, independent of natural language

Note 1 to entry: Adapted from ISO/TS 15926-6:2013.

Note 2 to entry: A statement can be recorded as an instance of the entity relationship in ISO 15926-2. A set of one or more statements can be recorded in shorthand form as a single item as an instance of a template, as defined in ISO/TS 15926-7.

3.1.30

signature statement

statement that states that the performer of an activity applied including the sign-off date on an individual named graph

3.1.31

stakeholder

person or company that is involved in a particular organization, project or system

Note 1 to entry: The stakeholder's involvement is especially because they have invested money in it or have a functional responsibility.

3.1.32

stakeholder requirement

requirement defining how a stakeholder wants to interact with an intended solution for a requirement

3.1.33

system element

part of a system which can be inanimate physical objects (not alive) and animate physical objects (alive)

Note 1 to entry: A system often is called a “set of elements”.

3.1.34

systems engineering

interdisciplinary approach governing the total technical and managerial effort required to transform a set of stakeholder needs, expectations, and constraints into a solution

Note 1 to entry: The approach supports a solution throughout its life.

3.1.35

system requirement

result of the transformation of the stakeholder, user-oriented view of desired capabilities into a technical view of a solution that meets the operational needs of the user

3.1.36

tagged item

equipment and major electrical and instrumentation item that has a specific tag number and which is treated individually for tracking and tracing purposes

Note 1 to entry: Bulk materials are excluded from this definition which normally are identified batches.

3.1.37

technical solution

solution to a problem that is dealt with so that the difficulty is removed by applying an appropriate technology or design principle

3.1.38

payload data

actual data in a data packet or data container minus all headers attached for transport and minus all descriptive meta-data

Note 1 to entry: In a network packet, headers are appended to the payload for transport and then discarded at their destination.

3.1.39

V-model

graphical representation of a system's development life cycle

Note 1 to entry: It is used to produce rigorous development life cycle models and project management models.

3.1.40

validation

proof that the system accomplishes or, toned down, can accomplish its purpose

Note 1 to entry: It is usually much more difficult and much more important to validate a system than to verify it, and give an answer to the question: ‘Have we made the correct product?'

3.1.41

verification

proof of compliance with the specification

Note 1 to entry: Compliance may be determined by an objective test, analysis, demonstration, inspection, etc. for each requirement or set of requirements. It answers the question: ‘Have we made the product correctly?’

Note 2 to entry: In general, verification is seen as the process of checking the compliance with a requirement.

3.1.42

3D model

representation of a physical body using a collection of interconnected points in a three-dimensional space

Note 1 to entry: Interconnected points can form triangles, lines, curved surfaces.