ISO 15926-13:2018 産業オートメーションシステムと統合—石油およびガス生産施設を含むプロセスプラントのライフサイクルデータの統合—パート13：統合された資産計画ライフサイクル | ページ 6

3.1.1

activity

individual that is something happening or changing

Note 1 to entry: The ISO/IEC/IEEE 15288:2015 definition of “activity” as “set of cohesive tasks of a process” implies a hierarchy in which processes contain activities, and activities contain tasks. Within this document, all are activities.

Note 2 to entry: The definition in the PMI Lexicon of Project Management Terms states that “activity” is an element of work performed during the course of a project. An activity normally has an expected duration, an expected cost, and expected resource requirements. Activities can be subdivided in tasks.

[SOURCE:ISO/TS 15926-12:2018, 3.1.1, modified — Notes to entry have been added.]

3.1.2

asset planning

planning that is for the construction, commissioning, refurbishment, maintenance, decommissioning, and disposal of assets, including the running down and starting up of production by assets

3.1.3

baseline schedule

schedule that is used by a planning activity as a reference basis for comparison to monitor and control progress on the planned activity

Note 1 to entry: The PMI Lexicon of Project Management Terms defines baseline schedule as “the approved version of a schedule model that can be changed using formal change control procedures and is used as the basis for comparison to actual results”.

Note 2 to entry: A baseline schedule is a specialization of the ISO/IEC/IEEE 15288:2015 definition of “baseline” as “formally approved version of a configuration item, regardless of media, formally designated and fixed at a specific time during the configuration item's life-cycle”.

[SOURCE:ISO 21500:2012, 2.3, modified]

3.1.4

calendar

pattern of working days and shifts that are available for scheduled activities

3.1.5

current schedule

schedule of the planned activity that is currently specified as the agreed working schedule by a planning activity to the performer of the planned activity

Note 1 to entry: ISO 21500:2012 specifies that the role of a current schedule is to avoid adverse schedule impact.

3.1.6

decision gate

activity that approves continuation

Note 1 to entry: Continuation of work beyond a decision gate is contingent on the agreement of the decision-makers.

Note 2 to entry: Criteria for continuation of abandonment are established for each decision gate.

3.1.7

early finish

earliest possible point in time when the uncompleted portions of the activity can finish based on the schedule

[SOURCE:PMI Lexicon of Project Management Terms]

3.1.8

early start

earliest possible point in time when the uncompleted portions of the activity can start based on the schedule

[SOURCE:PMI Lexicon of Project Management Terms]

3.1.9

finish to finish

successor relationship in a plan that is from the finish of one activity to the finish of the next

3.1.10

finish to start

successor relationship in a plan that is from the finish of one activity to the start of the next

3.1.11

free float

period of time into which an activity in a plan can overrun without causing a delay to subsequent activities in the plan

3.1.12

frontline date

date on which the achieved progress on an activity was scheduled

3.1.13

lag

period in time that is specified for a plan succession link

Note 1 to entry: This corresponds to the attributes “lead” and “lag” which are defined in ISO 21500:2012.

3.1.14

late finish

latest point in time that an activity can finish based on the schedule

3.1.15

late start

latest point in time that an activity can start based on the schedule

3.1.16

live schedule

schedule that has been revised from the current schedule to mitigate any delays

3.1.17

managed programme of work

activity that contains management and planning for the whole

3.1.18

milestone

event that is significant in a project, programme of work, or portfolio

[SOURCE:PMI Lexicon of Project Management Terms]

3.1.19

ontology

formal statement of an understanding of the world

Note 1 to entry: An ontology can be represented in any language. It need not be represented in a language specifically designed for ontologies, such as OWL. An ontology can have different representations.

Note 2 to entry: An ontology does not specify what data need to be recorded about the world.

Note 3 to entry: The ontology defined by this document is principally concerned with the world outside a computer system.

[SOURCE:ISO/TS 15926-12:2018, 3.1.3]

3.1.20

plan

specification of how an activity will be done

Note 2 to entry: An unscheduled plan does not contain start and end dates for component activities. A schedule does contain start and end dates for component activities.

Note 3 to entry: Plan corresponds to the term design (noun) defined in ISO/IEC/IEEE 15288:2015 ここで, the design is for an activity rather than for a system or system element.

Note 4 to entry: A plan can be more or less detailed.

Note 5 to entry: The PMI Lexicon of Project Management Terms defines “project management plan” as “the document that describes how the project will be executed, monitored and controlled, and closed.”

3.1.21

plan succession link

succession relationship between one activity or milestone and the next in a plan

Note 1 to entry: A plan succession link has the attributes “lead” and “lag” which are defined in ISO 21500:2012.

3.1.22

planning

activity that is creating a plan

Note 1 to entry: Planning corresponds to the term design (verb) defined in ISO/IEC/IEEE 15288:2015 ここで, a plan for an activity, rather than a design for a system or system element, is created.

3.1.23

project

activity with defined start and finish criteria undertaken to create a product or service in accordance with specified resources and requirements

Note 1 to entry: A continuing operational activity is not a project.

Note 2 to entry: A project has a beginning and end, and can be constrained by available time, funding and resources.

Note 3 to entry: In many cases an activity that is planned consists of parts of different projects with different objectives. Therefore the activity is not a project.

Note 4 to entry: Product here is a result of the project activity, not directly related to Product Breakdown Structure.

[SOURCE:ISO/IEC/IEEE 15288:2015, 4.1.33, modified — The word “endeavour” has been replaced with “activity” at the start of the definition and the Notes to entry have been modified.]

3.1.24

resource

individual that is used to perform an activity

Note 1 to entry: A resource can be material or staff time or equipment.

3.1.25

revised schedule

schedule that has been revised from the current schedule

3.1.26

revision shutdown

shutdown that is in order to make a change to a production activity

3.1.27

schedule

specification of an activity that contains all that is required as a basis for execution, and that specifies start and end dates for component activities

Note 1 to entry: A schedule is the end product of a planning activity at a point in time. A schedule can be revised as a project progresses.

Note 2 to entry: A schedule includes calendars, succession relationships, and all other constraints.

3.1.28

standard class

class whose specification for membership is owned or controlled by a standardization body and is publicly available

[SOURCE:ISO 15926-1:2004, 3.1.2, modified — The Note to entry and examples have been deleted.]

3.1.29

start to finish

successor relationship in which a successor activity cannot finish until a predecessor activity has started

3.1.30

start to start

successor relationship in which a successor activity cannot start until a predecessor activity has started

3.1.31

subject of work

physical object that an activity is carried out upon

3.1.32

total float

period of time into which an activity in a plan can overrun without causing a delay to the completion of the plan as a whole

3.1.33

work order

managed programme of work that contains a request from one party to another for one or more activities to be performed