{"id":410742,"date":"2024-10-20T05:41:49","date_gmt":"2024-10-20T05:41:49","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iso-15926-132018\/"},"modified":"2024-10-26T10:29:46","modified_gmt":"2024-10-26T10:29:46","slug":"bs-iso-15926-132018","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iso-15926-132018\/","title":{"rendered":"BS ISO 15926-13:2018"},"content":{"rendered":"
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 1 Scope <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 2 Normative references 3 Terms, definitions, symbols and abbreviated terms 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 3.2 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 3.3 Symbols <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 4 Layers and extension of integrated asset planning life-cycle data 4.1 Layers for integrated asset planning life-cycle data <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 4.2 The documentation of the layers <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 4.3 Use of the layers 4.4 Extensions for particular engineering applications 4.5 Simplification for a scheduling application view <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 5 Representation of planning data 5.1 Basis of the approach <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 5.2 Fundamental planning objects 5.2.1 Objective of planning <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 5.2.2 Required or proposed activity and specification <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 5.2.3 Alternative specifications <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 5.3 Schedule 5.3.1 Definition of a schedule <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 5.3.2 Level of a schedule <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 5.3.3 Role of a schedule <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 5.4 Planning activity <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 5.5 Actual activity that fulfils a requirement <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 5.6 Decomposition of an activity 5.6.1 Parts of activities and their level <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 5.6.2 Decomposition of a specification <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 5.7 Classifications of an activity 5.7.1 Activity purpose and activity breakdown 5.7.2 Activity management objective <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 5.7.3 Asset life-cycle phase <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 5.7.4 Activity risk 5.7.5 Activity criticality <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 5.7.6 Activity priority 5.7.7 Activity completion status <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 5.7.8 Activity planning status <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 5.8 Resource for an activity 5.8.1 Specification of a resource <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 5.8.2 Resource breakdown 5.8.3 Available physical object for a resource 5.8.4 Quantity-based and time-based resources <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 5.8.5 Consumable material and equipment 5.8.6 Quantity base resource usage <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 5.8.7 Work centre and organizational level <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 5.8.8 Staff time and discipline <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 5.8.9 Consumption profile <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 5.8.10 Material resource availability checking and ordering <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | 5.8.11 Material resource delivery <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 5.9 Participants in an activity 5.9.1 Subject of work <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 5.9.2 Subject of work and physical breakdown <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 5.9.3 Role of a person or organization <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 5.9.4 Planning software 5.10 Shutdown 5.10.1 Shutdown phase 5.10.2 Necessary shutdown for an activity <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 5.10.3 Shutdown scope 5.10.4 Shutdown reason <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 5.11 Dates and times for an activity 5.11.1 Beginning and end events for an activity <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 5.11.2 Required beginnings and ends <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 5.11.3 Required as early or as late as possible <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 5.11.4 Proposed beginnings and ends <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 5.11.5 Actual beginnings and ends 5.12 Duration of an activity <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 5.13 Measure of progress 5.13.1 Frontline date <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 5.13.2 Performance measurement <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 5.14 Event and milestone <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | 5.15 Temporal relationships between activities and events 5.15.1 Succession relationship <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 5.15.2 Specified lag for a succession relationship <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 5.15.3 Specified lag with calendar for a succession relationship <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | 5.15.4 Free float and total float for an activity in plan <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | 5.15.5 Dependency relationship 5.16 Calendar 5.16.1 Working days <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | 5.16.2 A repeating period in time <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | 5.16.3 A repeating point in time 5.17 Identification of objects <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | 5.18 Work order 5.19 Area of facility and site 6 Scheduling application view 6.1 Use of the scheduling application view model <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | 6.2 Simplification of the ISO 15926 ontology <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | 6.3 An actual activity in the scheduling application view model <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | 6.4 Data planning for the scheduling application view <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 6.5 User defined properties in the scheduling application view <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Annex A (normative) Ontology for integrated asset planning life-cycle <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Annex B (normative) XML schema for exchange between scheduling applications <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Annex C (informative) Relationship between the planning ontology and the scheduling application interface <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Annex D (informative) Schedule and activity level <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Annex E (informative) Interface to reference data libraries <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | Annex F (informative) Usage scenarios <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Annex G (informative) Relationship with UN\/CEFACT XML schema for reporting project schedule and cost performance <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Industrial automation systems and integration. Integration of life-cycle data for process plants including oil and gas production facilities – Integrated asset planning life-cycle<\/b><\/p>\n |