{"id":327407,"date":"2024-10-19T22:44:41","date_gmt":"2024-10-19T22:44:41","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-9223-1022018\/"},"modified":"2024-10-25T21:27:44","modified_gmt":"2024-10-25T21:27:44","slug":"bs-en-9223-1022018","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-9223-1022018\/","title":{"rendered":"BS EN 9223-102:2018"},"content":{"rendered":"
The present document:<\/p>\n
is based on internationally-recognised concepts;<\/p>\n<\/li>\n
proposes organisational principles and implementation processes for Configuration Management from both viewpoints: \u201cprogramme\u201d and \u201ccompany\u201d, with emphasis on the \u201cprogramme\u201d viewpoint;<\/p>\n<\/li>\n
deals with capture, safekeeping and release of configuration information. It details the principles described in EN 9223\u2011100.<\/p>\n<\/li>\n<\/ul>\n
It is up to each programme responsible person to define the necessary details of application and tailoring in the Configuration Management plan.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
6<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | 1 Scope 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | 4 The configuration status accounting process and its place in the overall programme Configuration Management 4.1 Configuration status accounting process overview <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 4.2 Nature of the configuration status accounting process <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 4.3 Recording initialisation <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 4.4 Configuration status accounting and lifecycle 5 Records associated with the configuration identification process <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 6 Records associated with the configuration control process <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 7 Records associated with the configuration verification, review and audit process <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 8 Relationship with other processes 8.1 Scope 8.2 Relationship with need specification process <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 8.3 Relationship with preliminary design process 8.4 Relationship with the detailed design process <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 8.5 Relationship with qualification process 8.6 Relationship with industrialisation and production processes <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 8.7 Relationship with operational in use process <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 8.8 Relationship with the disposal process 9 Requirements for exchanging and\/or sharing data <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 10 Implementation of traceability requirements in the configuration status accounting process <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | Annex A (informative)Information system prerequisite needed for configuration status accounting <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | Annex B (informative)Non exhaustive examples of attributes that allow to assure traceability <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Programme Management. Configuration Management – Configuration status accounting<\/b><\/p>\n |