Systemization.

The first step in preparation of a model for a work process is to separate the total
assets in
smaller pieces to simplify the definition of the individual pieces of work. This
process is called
systemisation; resulting in system definitions.
A system is defined as a functional-identifiable section of the plant that shall be
commissioned and brought to ready for start-up (RFSU) to a significant extent
isolated from
the adjacent systems. Subsequently systems are combined and started to realise
production.
On basis of the above, a system can be defined, as a complete assembly of
piping, vessels,
equipment, instruments, and electrical supplies etc. that can be defined as
having a singular
purpose within a unit. This definition will afford the ability to conduct meaningful
and
complete tests within the system.
Systems are normally started in a specific sequence, as required, by the process
operations.
It is suggested that operations personnel, with support of the commissioning
manager and
system engineer, use flow schemes issued in the feed package (including
updates) to start
identifying the systems and the sequence in which they will be started. The
system that is
placed in service first under the accepted start-up logic that provides a service to
other
systems is considered the provider system; the system receiving the service is
designated
the receiver system.
Defined systems will be indicated on Process Engineering Flow Schemes
(PEFS) or other
discipline drawing as applicable and assigned a unique number. However, for
process
systems it is recommended that the first pass of systemisation be completed at
PFS level,
taking into account circulation possibilities for dynamic testing and simulation
runs.
The systemisation approach should also be applied to all projects civil and
building works as
well as all supporting power and instrument facilities.
4.1 System Definition Guidelines
When defining systems (identifying system breaks) a number of considerations
need to be
taken into account. These considerations may be related to the hardware, but
also to the
work process and/or organisation.
Five categories of system breaks can be distinguished:
1. Functional breaks: Definition must meet requirements for all work processes
planned on
that system, including any testing required as part of the Flawless Initiative e.g.
novelty
or prototype testing.
2. Commodity breaks: Utilities, feed/product systems, process systems,
electrical. DCS,
civil.
3. Scope breaks: IC contract to IC contract, IC contract to EPCM and IC/EPCM
to nonproject
scope. However, certain utility units/start-up blocks may be spread across IC &
EPCM scope breaks, in this case the system will still be bound by the scope
breaks as
far as possible while maintaining a logical and practical system break point.
Guidance
and governance on the location of system breaks where contract scope
boundaries are
involved will be provided by PMC Commissioning. It is important for these cross
contract start-up blocks & systems, that a close working relationship is
maintained
between all system engineers with systems in that start-up block. For each of
these
cross contract units, start-up blocks and systems, there shall be a single system
engineer who will also have responsibility for coordinating all contractors within
that
unit, start-up block or system and ensuring continuity and completeness
throughout all
the applicable scopes. In most cases this responsibility will fall to a system
engineer
within the EPCM utilities as they will have the major parts. However this will not
always
be the case as some other utilities such as chilled water have their mayor parts in
the
IC scope. This lead role will be agreed with the PMC during systemisation.
4. Plot breaks: Where possible systems should be wholly contained within a
start-up block
and start-up blocks contained within a geographical commissioning area to
promote
safe control of work during commissioning; the logical grouping of start-up blocks
within
a commissioning area will become apparent during the development of the
WEFS.
5. Time breaks: various project or operational phases.
Points of isolation between the systems will normally be at the open breakers for
electrical
systems and at manual isolation valves for mechanical systems, system breaks
at butt welds
shall be avoided. The isolation points are included in the provider system.
4.1.1 System size
There is no simple guideline for the right size of a system. If relative small
systems are
defined the result will be a significant increase of relationships between systems
and
therefore it will be difficult to separate activities on system level. This means that
a (large)
number of systems will be needed to carry out a single activity, resulting in
inefficiency. If on
the other hand too large systems are defined, parallel groups of activities can be
defined.
This will often lead to definition of sub system to reduce the overall schedule time
needed to
complete all activities of a system.