ISO 23234:2021
(Main)Buildings and civil engineering works — Security — Planning of security measures in the built environment
Buildings and civil engineering works — Security — Planning of security measures in the built environment
This document provides requirements and recommendations for effective planning and design of security measures in the built environment. The purpose of the document is to achieve optimal protection of assets against all kinds of malicious acts, while ensuring functional, financial, and aesthetic aspects. The document describes which methods and routines need to be implemented in various stages of a building or civil engineering works project, as well as the competencies needed to achieve a good result. This document is applicable to new builds, refurbishments and development projects by government and private entities, for various environments, buildings and infrastructure.
Bâtiments et ouvrages de génie civil — Sûreté — Planification des mesures de sûreté dans l'environnement bâti
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 23234
First edition
2021-02
Corrected version
2021-05
Buildings and civil engineering
works — Security — Planning of
security measures in the built
environment
Bâtiments et ouvrages de génie civil — Sûreté — Planification des
mesures de sûreté dans l'environnement bâti
Reference number
©
ISO 2021
© ISO 2021
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2021 – All rights reserved
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Planning of security measures for the built environment . 5
4.1 General . 5
4.2 Security planning as part of risk management . 6
4.3 Size of projects . 6
4.4 Division of the building process into stages . 6
4.4.1 General. 6
4.4.2 Strategic definition . 7
4.4.3 Preparation and brief . . 8
4.4.4 Concept design . 8
4.4.5 Developed and technical design . 8
4.4.6 Construction . 8
4.4.7 Testing and handover . 9
4.4.8 In use . 9
4.4.9 Decommissioning . 9
4.5 Organization and principal . 9
4.6 Special advisers in security projects .10
4.6.1 General.10
4.6.2 Security planner .10
4.6.3 Security risk adviser .10
4.6.4 Technical security adviser .11
4.6.5 Operational security adviser .12
4.6.6 Project information security adviser .12
5 Security deliverables in stages.13
5.1 Strategic definition .13
5.1.1 Asset inventory.13
5.1.2 Protective security objectives .13
5.1.3 Requirements for protective security planning .14
5.1.4 Threat assessment, scenario selection and design-basis threats .14
5.1.5 Information security for the project .15
5.1.6 Security risk analysis (strategic) .15
5.1.7 Clarification of conditions .15
5.2 Preparation and brief .16
5.2.1 Input to the dependency map .16
5.2.2 Security risk analysis (preparation and brief) .16
5.2.3 External requirements report .16
5.2.4 Security strategy .17
5.2.5 Input to zoning .17
5.2.6 Input to the spatial and functional programming .17
5.2.7 Identification and assessment of security measures.17
5.2.8 Cost survey .17
5.2.9 Contributions to preliminary design report .18
5.3 Concept design .18
5.3.1 Reassessment of security objectives.18
5.3.2 Security risk analysis (concept) .18
5.3.3 Reassessment of security strategy .18
5.3.4 Description of security measures .18
5.3.5 Integration of security measures .19
5.3.6 Selection of security measures .19
5.3.7 Input to operational requirements .19
5.3.8 Cost survey for concept .19
5.4 Developed and technical design .19
5.4.1 Input to tender drawings .19
5.4.2 Input to delivery and job descriptions .20
5.4.3 Contributions in tender evaluation.20
5.4.4 Assessment of final design .20
5.5 Construction .20
5.5.1 Implementation control .20
5.5.2 Participation in functional tests and commissioning .21
5.5.3 Input to the operations and maintenance manuals .21
5.5.4 Input to operational requirements .21
5.5.5 Requirements for alterations in security measures .21
5.5.6 Assessment of as-built design .22
5.6 Testing and handover .22
5.6.1 Participation in handover .22
5.6.2 Completeness check .22
5.6.3 Quality and functionality check .22
5.7 In use .22
5.7.1 Contribution to trial use .22
5.7.2 Security training .23
5.7.3 Security verification .23
5.8 Decommissioning .23
5.8.1 Overview of sensitive installations .23
5.8.2 Security risk assessment (decommissioning) .23
Bibliography .24
iv © ISO 2021 – All rights reserved
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www .iso .org/ patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www .iso .org/
iso/ foreword .html.
This document was prepared by Technical Committee ISO/TC 59, Buildings and civil engineering works.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/ members .html.
This corrected version of ISO 23234:2021 incorporates the following corrections:
— Table 1 has been corrected to be consistent with the rest of the text.
Introduction
0.1 General
The objective of this document is to provide requirements and recommendations for organizations to
effectively plan security measures in order to protect their built environment (e.g. buildings, plants,
infrastructure, and property) against undesirable intentional actions.
This document describes an approach to planning security measures in the built environment based
on generic stages and corresponding security deliverables in each stage. This document also defines a
number of roles that should be assigned in the project organization to ensure that the security input to
the design and construction process has been founded on professional assessment.
For practical use, the individual organization can adapt this document to its own project model and
other organization-specific factors. This can also require that individual tasks be moved or allocated to
other stages than those specified in this document.
This document is applicable independent from the chosen risk assessment methods, standards and
guidelines for the project. Risk assessment methods are not described in this document and neither is
the design of mitigation measures.
Figure 1 shows a checklist for when this document becomes applicable.
Figure 1 — Checklist as guidance for possible use of ISO 23234 in built environment projects
vi © ISO 2021 – All rights reserved
0.2 National security regulations
In addition to the requirements ensuing from the organization's own risk acceptance, organizations
that are subject to national security regulations (where they exist) can be obliged by law to protect
critical assets (material and functional).
For organizations not subject to such regulations, it is natural to base their approach on the insurance
companies' requirements for their basic security. This document is general in nature and for general
use, both within and outside of the scope of application of national security regulations.
0.3 Safety and security
This document is targeted primarily at the domain referred to as protective security. In this document
the common word "safety" and the term "protective security" are used to distinguish between methods
of combating undesirable unintentional incidents or accidents (safety) and combating undesirable
intentional actions (protective security).
In the context of protective security, risk is usually understood as "an expression of the relationship
between the threat against a specific asset and this asset's vulnerability to that specific threat". The
threat derives from a threat actor and has a differing degree of severity depending on the actor's
capability (knowledge and experience, access to weapons, tools and means of assistance), intent,
previous and presumed future choice of target (targeting).
Planning of a building and civil engineering works involves two aspects related to protection
– protective security and safety (the latter including for example protection against fire, flood,
earthquake, and technical installations failure in the building and civil engineering works). The two
aspects can, under some circumstances, generate contradictory requirements, and resolving them in
a satisfactory manner is a very important task at the planning and design stage. A typical example of
such contradictory requirements is the necessity of safeguarding effective evacuation of persons from
a building in an emergency situation versus the necessity of preventing unauthorized persons from
1)
entering the building. Universal design, i.e. accessibility and egressibility , is also an important aspect
that needs a high degree of attention.
1) Ability to leave the building or any other delimited area.
INTERNATIONAL STANDARD ISO 23234:2021(E)
Buildings and civil engineering works — Security —
Planning of security measures in the built environment
1 Scope
This document provides requirements and recommendations for effective planning and design of
security measures in the built environment.
The purpose of the document is to achieve optimal protection of assets against all kinds of malicious
acts, while ensuring functional, financial, and aesthetic aspects.
The document describes which methods and routines need to be implemented in various stages of a
building or civil engineering works project, as well as the competencies needed to achieve a good result.
This document is applicable to new builds, refurbishments and development projects by government
and private entities, for various environments, buildings and infrastructure.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO 6707-1, Buildings and civil engineering works — Vocabulary — Part 1: General terms
ISO 19650-5, Organization and digitization of information about buildings and civil engineering works,
including building information modelling (BIM) — Information management using building information
modelling — Part 5: Security-minded approach to information management
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 6707-1 and the following
apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
3.1
security
state of relative freedom from threat (3.18) or harm caused by deliberate, unwanted, hostile or
malicious acts
[SOURCE: ISO 19650-5:2020, 3.7]
3.2
protective security
use of measures when managing risk (3.20) linked to undesirable intentional actions
3.3
preventive security
planning, preparation, implementation and overseeing of protective security (3.2) measures which seek
to eliminate or reduce risk (3.20) resulting from a threat (3.18)
3.4
actor
organization or individual that fulfils a role
3.5
project stage
delimited stage within a project
Note 1 to entry: A project stage can in turn be divided into sub-processes. The division is often justified on
the basis of identifying deliverables, decisions, and changes of actors (3.4). It can be adapted to the individual
organization or situation.
3.6
strategic definition
project stage (3.5) during which the justification, overarching aim, and framework of the project are
identified
3.7
preparation and brief
project stage (3.5) during which it is ascertained whether the project is feasible, and determined which
conceptual solution is most appropriate
3.8
concept design
project stage (3.5) during which principles are developed for a technical solution with realistic strategies
and plans for the project, so that a final decision on implementation can be made on a correct basis
3.9
developed design
project stage (3.5) that includes coordinated and updated proposals for structural design, building
services systems, outline specifications, cost information and project strategies in accordance with the
design programme
3.10
technical design
project stage (3.5) that occurs after the developed design (3.9) has been completed and in which the
residual technical work of the core design team is completed
3.11
construction
project stage (3.5) during which deliverables are completed in accordance with plans and intentions
3.12
testing and handover
project stage (3.5) during which a fault-free technical delivery is handed over and it is ensured that all
systems are correctly adjusted to their intended use
3.13
user
organization or person which uses or is intended to use, a building or other construction works
Note 1 to entry: A user can also be the owner of the building or construction works.
[SOURCE: ISO/TR 15686-11:2014, 3.1.131, modified — "animal or object" has been deleted; Note 1 to
entry has been deleted and replaced with a new Note 1 to entry; cross-references to terminological
entries in ISO 6707-1 have been removed.]
3.14
in use
project stage (3.5) during which technically sound and economic operation is ensured that satisfies the
user's requirements for the project and that provides the intended effect
2 © ISO 2021 – All rights reserved
3.15
decommissioning
project stage (3.5) during which a viable and prudent conclusion to ownership or period of use is
ensured
3.16
asset
item, thing or entity that has potential or actual value to an organization
Note 1 to entry: Value can be tangible or intangible, financial, or non-financial, and includes consideration of risks
(3.20) and liabilities. It can be positive or negative at different stages of the asset life.
Note 2 to entry: Physical assets usually refer to equipment, inventory and properties owned by the organization.
Physical assets are the opposite of intangible assets, which are non-physical assets such as leases, brands, digital
assets, use rights, licences, intellectual property rights, reputation, or agreements.
Note 3 to entry: A grouping of assets referred to as an asset system could also be considered as an asset.
Note 4 to entry: Life, health and welfare of humans and other living beings can also be an asset.
Note 5 to entry: In the context of this document, organization can be understood as both owner and user of the
physical asset in question.
[SOURCE: ISO 55000:2014, 3.2.1, modified — Notes 4 and 5 to entry have been added.]
3.17
vulnerability
lack of resilience against an undesirable intentional action or inability to recover a new stable condition
of an asset (3.16)
3.18
threat
potential, deliberate action that can cause harm to an asset (3.16)
Note 1 to entry: A threat is always related to a threat actor (3.4), which can be an individual or an organization.
3.19
design-basis threat
threat (3.18) used as a basis for preparing security measures
3.20
risk
effect of uncertainty on objectives
Note 1 to entry: An effect is a deviation from the expected. It can be positive, negative or both, and can address,
create or result in opportunities and threats (3.18).
Note 2 to entry: Objectives can have different aspects and categories, and can be applied at different levels.
Note 3 to entry: Risk is usually expressed in terms of risk sources, potential events, their consequences, and their
likelihood.
Note 4 to entry: In the context of protective security (3.2) against threats, risk is usually expressed in terms of
threat, impact, and vulnerability (3.17).
Note 5 to entry: In the context of this document, risk is used as a negative deviation.
[SOURCE: ISO 31000:2018, 3.1, modified — Notes 4 and 5 to entry have been added.]
3.21
residual risk
risk (3.20) remaining after risk treatment
Note 1 to entry: Residual risk can contain unidentified risk.
Note 2 to entry: Residual risk can also be known as “retained risk”.
Note 3 to entry: “Risk treatment” in this document means carrying out mitigating measures to reduce the risk.
[SOURCE: ISO Guide 73:2009, 3.8.1.6, modified — Note 3 to entry has been added.]
3.22
risk assessment
overall process of risk (3.20) identification, risk analysis (3.23) and risk evaluation
[SOURCE: ISO Guide 73:2009, 3.4.1]
3.23
risk analysis
process to comprehend the nature of risk (3.20) and to determine the level of risk
Note 1 to entry: Risk analysis provides the basis for risk evaluation and decisions about risk treatment.
Note 2 to entry: Risk analysis includes risk estimation.
[SOURCE: ISO Guide 73:2009, 3.6.1]
3.24
stakeholder
person or organization that can affect, be affected by, or perceive themselves to be affected by a decision
or activity
Note 1 to entry: A decision maker (3.25) can be a stakeholder.
[SOURCE: ISO Guide 73:2009, 3.2.1.1]
3.25
decision maker
top management or a person designated by the top management, and given delegated authority to make
decisions
3.26
principal
person or organization that has initiated the project
Note 1 to entry: Principal can correspond to "developer" or "client".
3.27
project manager
person with the responsibility for planning, executing, and closing off a project
3.28
supplier
person or organization supplying materials or products
Note 1 to entry: In this document, supplier can also mean person or organization supplying services.
[SOURCE: ISO 6707-2:2017, 3.8.30, modified— Note 1 to entry has been added.]
3.29
security deliverable
security-specific written report, memorandum, drawing, digital information model, product solution
or other documentable work based on specialist professional input
Note 1 to entry: The security deliverable is normally a sub-element of or input to the project to be executed.
4 © ISO 2021 – All rights reserved
3.30
external policy maker
external actor (3.4) that sets guidelines for the project and whom the project has little opportunity to
influence
Note 1 to entry: External policy makers can include the police, planning and building authorities, heritage
authorities, other public authorities, standards-setting bodies, etc.
3.31
security planner
adviser with knowledge and experience in managing the planning of the security works in construction
projects with special security requirements
3.32
security risk adviser
adviser with knowledge and experience in undertaking risk assessments (3.22)
3.33
technical security adviser
adviser within a technical subject with special knowledge and experience in security (3.1) during the
operational phase of the process
Note 1 to entry: This can include engineers with specialist knowledge and experience in the vulnerability (3.17)
and security of structures, electro-technical installations, or other systems. This can also include architects or
landscape architects with specialist knowledge and experience in security.
3.34
operational security adviser
adviser within the domain of human and organizational security measures during the operational
phase of the project
Note 1 to entry: This role is often filled by the user's own security organization.
4 Planning of security measures for the built environment
4.1 General
Where there is an identified need for protective security in relation to an asset in the built environment,
protective security measures shall be considered and, where implemented, managed in all project
stages.
This document sets out a suggested model for project stages (see Table 1) that can be applied whether a
project relates to a new or existing asset. Some projects might follow alternative project models for the
execution of work. Depending on the nature of the project, the complete model can be followed, or parts
can be adapted and applied.
The actors in a construction process have defined tasks and roles in the different stages and sub-
processes. The principal is responsible for defining the construction programme and detailed
requirements, while the project manager and project planning manager are responsible for
ensuring that the decision support documentation for security is prepared in line with the accepted
recommendations of the project security adviser and to the right quality. The project planners shall
jointly develop the project from a list of needs and functions that result in suggestions for detailed
interdisciplinary solutions. The project executors shall deliver and implement the selected solutions,
and document that their execution complies with the defined requirements.
All actors involved in the project security works shall familiarise themselves with the requirements
and instructions defined by the principal in the project and understand how the security requirements
also affect the individual's specialism and choice of solutions. This document describes the tasks,
functions, and responsibilities of the protective security roles during the individual stages. This
should be viewed in relation to other security deliverables in the construction project. Requirements
for protective security measures shall be developed in the project in the same way as other functions
and requirements. Security requirements should be defined through processes for security risk
management in the principal's organization before the project is established.
4.2 Security planning as part of risk management
In a construction project where protective security measures are to be implemented in accordance
with this document, there can often be a number of activities in parallel with, or in advance of, what is
defined as the construction project itself. During the planning processes, public stakeholders should be
asked whether their needs are sufficiently taken into account.
The principal shall decide which security measures to implement. The basis for such recognition often
emerges from the organization performing security risk assessments as an on-going activity in the
organization's security risk management.
The organization is expected to have ongoing processes for mapping, analysing, and assessing its threat
profile in relation to assets and known threats. Changes in the asset inventory or the threat picture can
result in the need to alter security measures. The same can be true after incidents that have affected
the organization.
Which security deliverables are included at each stage within a specific construction project depends on
the nature of the project and how it is being organized. Sometimes, a security risk analysis has already
been conducted by the principal before the construction project begins. The project organization can
then use the security risk analysis as supporting documentation for its work.
The principal can choose to include the introductory security deliverables in the strategic definition
project stage, as part of its ongoing operations, as a concept for the construction project, or as the first
stage of the construction project. A construction project organised in accordance with this document
shall always use design-basis threats and security risk analyses in the project planning and execution
of the security works.
4.3 Size of projects
Organizations with a need for security measures against undesirable intentional actions shall
perform mapping, assessments, and analyses as a basis for their choice of final security measures. The
organization and scope of the work should be modified according to the type and size of the project.
For smaller projects, it can be appropriate to use this document for parts of the process only, and the
security deliverables can have a lesser scope. This gives the organization the opportunity to adapt the
usage of this document to its own needs.
4.4 Division of the building process into stages
4.4.1 General
The deliverables in the stage descriptions show which information and documentation is necessary to
complete the project tasks during that individual stage.
Table 1 shows where the individual security deliverables belong in different stages of the construction
project.
6 © ISO 2021 – All rights reserved
Table 1 — Project stages and security deliverables
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8
Strategic Prepara- Concept Developed Construc- Testing and In use Decommi-
definition tion and design and techni- tion handover ssioning
brief cal design
Asset inven- Input to the Reassess- Input to Implemen- Partici- Contribution Overview
tory dependency ment of tender tation pation in to trial use of sensitive
map security drawings control handover installations
objectives
Protective Security Security Input to Partici- Complete- Security Security risk
security risk analysis risk analysis delivery and pation in ness check training assessment
objectives (preparation (concept) job descrip- functional (decommis-
and brief) tions tests and sioning)
commission-
ing
Require- External re- Reassess- Contribu- Input to the Quality and Security
ments for quirements ment of tions in operations functionali- verification
protective report security tender eval- and mainte- ty check
security strategy uation nance man-
planning uals
Threat Security Description Assessment Input to
assessment, strategy of security of final de- operational
scenario se- measures sign require-
lection and ments
design-basis
threats
Information Input to Integration Require-
security for zoning of security ments for
the project measures alterations
in security
measures
Security Input to the Selection Assessment
risk analysis spatial and of security of as-built
(strategic) functional measures design
program-
ming
Clarification Identifica- Input to
of conditions tion and operational
assessment require-
of security ments
measures
Cost survey Cost survey
for concept
Contribu-
tions to
preliminary
design re-
port
4.4.2 Strategic definition
Within the strategic definition stage, the purpose and framework of the construction project, to meet
the user needs and requirements (where known), are identified and a business plan prepared.
The degree of protection required to mitigate the risks posed by identified potential threats to the
completed building or infrastructure, the services delivered from or by it, or specific sensitive assets
contained within or on it, shall also be defined.
The principal then assesses if the construction project is commercially viable and whether to continue
the planning or not.
4.4.3 Preparation and brief
During the preparation and brief stage, conceptual solutions are developed to establish whether the
construction project as set out in the strategic definition stage is feasible. By the end of this stage,
the most appropriate conceptual solution is determined based on the organization’s general business
plan, provisional business plan for the construction project (justification and strategic objective) and a
requirements analysis linked to the construction project.
Opportunities and preconditions for the project are investigated and the objectives, framework, and
success criteria for the project are specified. The stage also involves the definition of the functional and
spatial requirements.
At the end of this stage a conclusion is reached as to whether to proceed with the project or not.
4.4.4 Concept design
The concept design develops the principles for a technical solution and the strategies and plans for the
construction project so that a final decision on implementation can be made.
During this stage, the following shall be produced:
— a verified specification of the user's needs and requirements;
— a study of functions and solutions;
— the expected impact assessment of the protective measures; and
— a confirmed business plan for the project.
These shall allow a final project scope, a specific execution plan and a cost estimate to be produced and
enable the organization to reach a final decision on the financing and execution the project.
4.4.5 Developed and technical design
During the developed and technical design stage, detailed and quality-assured design documents are
produced, as well as the final project scope and execution strategy with associated costs (including
estimates of uncertainty margins), schedule, and quality requirements. The suppliers shall also submit
detailed information on systems and products.
In this stage, the principal shall decide where any specialist personnel, materials and systems are
required during the project and for the completed building or infrastructure, based on the information
set out in the user requirements.
The purpose of documentation produced in this stage is to ensure that the construction project can be
completed to the right quality at the right time.
4.4.6 Construction
During the construction stage, work should be undertaken according to the design documentation and
other associated requirements.
In this stage, the principal shall ensure that qualified persons take necessary decisions in compliance
with the business plan and user’s needs.
A plan should be developed for testing of relevant components and systems and a quality assurance
review of the completed works shall be undertaken. By the end of the construction stage, “as built”,
operation and maintenance documentation shall be submitted to the principal.
8 © ISO 2021 – All rights reserved
4.4.7 Testing and handover
By the conclusion of the testing and handover stage, the completed works should be fault-free and all
systems should be correctly adjusted for their intended use before the construction works is handed
over to the principal, together with any testing and certification documentation.
During the trial use period, operating personnel and users should also be trained in the use of any
specialist systems.
At the end of the trial use period, the principal assesses whether the completed project complies with
the business plan and accepts (or rejects) the results of tests and reports from the trial.
As a result of the work during this stage, finished construction works, quality-assured with functional
tests, trial use and inspections, emerges. The user monitors the functions of the product and assesses
the performance.
4.4.8 In use
During the in-use stage, the construction works should be operated according to the needs of the user;
and its performance, as well as the performance of specific systems, should be monitored and recorded.
4.4.9 Decommissioning
Decommissioning occurs when the current use or ownership of a construction works comes to an end.
During this stage, it can be necessary for current assets to be removed, especially where the owner or
user considers that the assets are of a sensitive nature. The assets can also be replaced by other assets
belonging to new users.
During this stage, the principal keeps final accounts and performs analyses, while the user’s
participation ceases.
If the construction works, or in the case of demolition, the site, is sold, all relevant documentation shall
be transferred to a new owner.
4.5 Organization and principal
The organization becomes a principal (buyer, client) when it decides to carry out a construction project.
The principal can sometimes be the intended user of the final outcome of the project.
The principal can choose to:
— sell the finished construction works to a buyer unknown at the planning stage;
— sell the finished construction works to a buyer known at the planning stage;
— continue to own the construction w
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...