Beruflich Dokumente
Kultur Dokumente
Introduction
IPMS 2000 was developed to consolidate and
integrate multiple, diverse Materials Management,
Procurement, Document Management, Project
Control and Site Control Applications throughout
KBRs worldwide offices. The objective in
developing IPMS 2000 was to globalize and
standardize project execution systems, standards,
and practices by incorporating the best practices
exercised in Houston, London, and Alhambra.
IPMS 2000 has been operational since late-1993. In
1998, a project was undertaken to put a Graphic
User Interface (GUI) front-end on the system to
mimic Windows-type functionality. As a result,
IPMS 2000 is a completely point and click
system.
System Functional Scope
IPMS 2000 fully integrates and automates the
functional areas of Document Management,
Materials Operations / Materials Management
and Project Controls. It is designed to
implement a full Engineering - Procurement Construction project scope, but can be utilized
for any portion of project execution.
System Organization
IPMS 2000 is organized through Oracle's
relational database technology. The underlying
data model is rationalized to permit single point
of entry. The discipline responsible for
performing each function is solely responsible
for creating and maintaining the same
information within IPMS 2000. All other
disciplines use existing data and only enter the
required information to perform their function
and generate their operational documents or
reports. All operational project documents and
reports are generated from IPMS 2000.
IPMS 2000 DETAILS.DOC
Administration/Security
Reference
Document Management
Procurement
Tracking
Cost Control
Administration/Security
Application
Reference Application
The Reference Application within IPMS 2000
controls most of the common codes used
throughout the system. Project, subproject, work
breakdown structures (WBS), organizational
breakdown structures (OBS) and standard code
values are maintained. Corporate standard codes
are populated as part of the project startup
process and some can be edited for project
specific requirements. Codes used for global
data collection may not be edited by the project.
All applications validate or select from these
IPMS 2000 DETAILS.DOC
Document Management
Application
Document Registers
The system organizes document groups
relative to engineering documents, supplier
documents, and general correspondence.
Within each of these groups, documents are
organized by document type and subtype. All
documents are associated with the
appropriate project organization, the
discipline within that organization, in
addition to WBS and OBS coding.
All documents can be controlled through
multiple filing references at multiple
locations as well as lifecycle coding to
provide for archiving and turnover
procedures. Individual document media and
size information can also be maintained.
Engineering Documents
When engineering documents are registered
in the system, tracking chains are
automatically assigned. This, in connection
with the transmittal portion of document
management, assists the tracking and cost
control applications with measuring project
engineering progress. Part of the project setup activity identifies which material takeoff
documents are automatically inserted into the
2
Supplier Documents
Procurement Application
The Procurement Application consists of the
pre-order functions of requisitioning, inquiry
(request of quotation), and award. the after order
functions include expediting, traffic and a
limited inspection capability. For supplier
documents, see the Document Management
Application.
All procurement documents are issued directly
from IPMS 2000. Material operations are
therefore, fully automated. The procurement
operational processes and documents are
associated to the IPMS 2000 workpackage and
Tracking Application, and automatically update
procurement status and projections as a result of
the work performed. Through this mechanism,
all affected disciplines are alerted to the relative
impact as the work progresses. If there are
specific review and approval milestones for any
of the procurement processes, the Tracking
Application can be invoked to track and control
these activities.
Requisitioning
All material is requisitioned through IPMS
2000. The material catalog contains the
reference for all requisitioned material. The
Requisition controls the authorization level for
procurement activity, inquiry or purchase.
IPMS 2000 DETAILS.DOC
Procurement Award
Expediting
Traffic
The IPMS 2000 traffic function may be used for
any material movement from one location to
another. This includes material movement from
a supplier to the final material destination as
well as movement from one warehouse location
to another that requires tracking and a carrier.
Material movement from an award to its final
destination can be performed at a level
determined appropriate by the project. Levels
vary from none to tracking shipments at the
award subline level to a complete packing list
and packing manifesto. Depending on how the
traffic process is used, material can be received
directly by shipment. Further, depending on
how the project elects to use the traffic function,
material movement tickets (MMTs) can be
automated, through a controlled process, based
upon expediting status indicating which material
is ready to ship. Interfaces also exist with
various freight forwarders to automatically feed
the freight forwarders system with purchasing
and expediting information and in turn feed
IPMS 2000 MMTs with the shipment
information from the freight forwarders system.
Special instructions for material handling can be
set up in the Material Requirements Planning
Application. This includes international
export/import coding in accordance with the
Bruxelles International Nomenclature
(Harmonized Commodity Control Number / US
Schedule B Number). These instructions can be
included as part of the procurement documents
to the suppliers.
Shipments can be tracked through each segment
(route segment) of the logistic process,
including various modes of shipment, transfer to
multiple carriers as well as shipment
consolidation. Consolidated shipment schedules
can be maintained in order to coordinate and
plan individual shipments. Segment freight
costs, in multiple currencies, may be tracked for
invoicing and cost control, if required. Traffic
documentation can be monitored and handled as
IPMS 2000 DETAILS.DOC
Site Support
There are a number of important functions
that support overall material management at
the site. These include subcontract
administration, equipment maintenance,
equipment service log, painted pipe control,
and punch list.
Committing labor
Tracking Application
The IPMS 2000 Tracking Application can be
seen as two general utilities, workpackage
and chain milestones, that can be applied to
the managing of all facets of the project. The
Tracking Application also has a CPM
interface process as well as an interface to
constructions labor control system, ACLS the Automated Craft Ledger System.
Project Calendars
As part of the project's set up, a series of
project calendars are established and
provided a code. Normally there is an elapsed
calendar and at least one working calendar.
Each working calendar identifies the working
days and the number of working hours per
day. Each working calendar can be
segmented to show different working
schedules through time. There can be a
separate Working Calendar to reflect the
working practices of each site. These
calendars are used for date validation, date
calculations, and date projections.
10
Chain Milestones
Each project defines the milestones they wish to
track. Corporate default milestones are loaded
initially to facilitate the setup, but can be
modified as required. Each milestone can be
identified to a specific discipline (OBS), its type
(start or finish) and its parent milestone if it is
embedded.
Chain models, or templates, are established by
attaching milestones and assigning each
milestone its order, duration and default earning
rules (percent earned). Any discipline or
function can define milestones and chains for
their use. The user applies the appropriate chain
models when he or she wishes to schedule,
track, and project progress in the specific work
activity.
Milestones can also be "mapped" to virtually
any IPMS 2000 date field, so that the database
can automatically update the tracking function
as work is performed. Default mapping is
provided as part of the IPMS 2000 setup, but
like milestones can be modified to meet the
specific requirements of the project. There are
two specialized forms of mapping: Milestone
mapping is provided for tracking tagged items
from design through installation. Milestones are
also mapped to transmittal purpose to permit
the automated tracking maintenance when
documents are issued through the transmittal
process.
Workpackage
IPMS 2000 permits grouping or organizing any
set of components maintained within IPMS
2000 into workpackages. This permits the
tracking of these workpackage contents as a
package as well as individual items.
Workpackages can also relate to other
workpackages as a parent or linking function.
Examples of the primary workpackages are
engineering, procurement and construction. An
example of another, more specialized
CPM Interface
The IPMS 2000 workpackage portion of the
Tracking Application is designed to interface
with a number of Third-party CPM applications,
notably Primavera, Open Plan, and Artemis.
One or more wrkpackages can be associated to a
single CPM activity; the milestone mapping
permits a more detailed, intermediary tracking
in IPMS 2000 while limiting the activity
breakdown in the CPM to only the necessary,
higher level critical interfaces. An automated
process transfers IPMS 2000 progress at the
workpackage level to the CPM environment.
When CPM critical path analysis has been
performed, the resulting projections can be
transferred back to IPMS 2000 where the CPM
results are compared with the IPMS 2000
projections.
Automated Craft Ledger System (ACLS)
Interface
Kellogg Brown & Root uses an Oracle-based
Construction Craft tracking / progress system,
Automated Craft Ledger System, to plan and
control craft labor at the detailed level. IPMS
2000 provides a download capability to the
ACLS for setup. This includes the latest
document information such as MTO,
workpackage, CPM schedule information, cost
coding information, and budgeting information.
IPMS 2000 provides for a tracking freeze for
reporting and history. This tracking freeze is
IPMS 2000 DETAILS.DOC
Cost Coding
All cost codes are maintained in IPMS 2000.
This includes all codes of accounts as well as
the breakdown of cost data in order to
manage all phases of control.
Project Codes of Accounts hierarchies are
established for the entire project, including
cross-references to client and third-party
codes of accounts, as required. A code of
accounts rules tables automatically codes
MTO's and commitments to the correct
project code of account. This eliminates error
and reduces the effort to code the operational
outputs from IPMS 2000.
Cost category and subcategory hierarchies
permit the tracking of cost breakdowns to
subcategories of costs and permit rollups
based upon reporting and control
requirements. For example, the cost category
of material can be broken down to
equipment, bulk material and consumables.
Some subcategories of these include process
equipment, instruments, welding rods, etc.
Cost type and subtype hierarchies permit the
differentiation between subtypes of budgets,
changes, commitments, and forecasts.
Budgets can be differentiated between a
number of different baselines: changes
administered from approved, trend, budget
12
13
14
15