Startup Schedule Activity Descriptions

IPMS 2000
START-UP
SCHEDULE
General Activities
Pre Start-Up Activities:
GE1000: Contract Award
GE1007: Review Lessons Learned
GE1008: Initial Start-Up Meeting
GE1010: Establish Labor System
GE1015: Acquire Financial & Accounting Number
GE1020: Establish Physical Facilities (Office, Tel, Etc.)
GE1025: Review Staff Req. & Assign Initial Personnel
GE1030: Identify Project Contractual Requirements
GE1035: Project Team Review IPMS Package Relationship
GE1040: Identify Personnel & Computer Requirements
GE1050: Identify Project Personnel/IPMS Access & Roles
GE1055: Define & Approve WBS, OBS, CBS Strategy
GE1110: Establish WBS/CBS
Start-Up Activities:
GE1005: Arrange/Conduct Project Kick-Off Meeting
GE1045 Define Project Execution Strategy
GE1065: Provide Functional & Systems Software Training
GE1070: Project Team Review Global Default Codes
GE1075: Project Team Approve WBS, OBS & CBS
GE1078: Shared Data Overview Meeting
GE1080: Discuss Process Systems & Services
GE1090: Identify & Input WBS/CBS Codes in IPMS
Planning Activities:
GE1060: Establish/Update Project Implementation/Execution Plan
GE1120: Review WPIDs, Quality Plan, Project Start-Up
GE1125: Develop Project Quality Plan
GE1130: Prepare Project Procedures
GE9999: IPMS Start-Up Complete
IPMS GENERAL START-UP ACTIVITIES

ACTIVITY ID
GE1000
DESCRIPTION
Contract Award
The responsibility to identify contract award and initiate set up of IPMS rests with
Project Management. The IPMS instance will be set up by the start-up team. The
instance will be loaded with a copy of all the Corporate data, as defined and
agreed upon by the project during Start-Up activity review.
Project Code (4 characters) and Sub-Project Code (4 characters) are required. This
combination must be unique. At least one sub-project is required. The Project
Code is generally descriptive (client, project name). Project Code and Sub-Project
Codes are set up in PMRR1212.
GE1005
Arrange/Conduct Project Kick-Off Meeting

The use of IPMS is defined in the Project Kick-Off Meeting.
GE1007
Review Lessons Learned

Lessons learned are reviewed to educate project staff so that known pitfalls may
be avoided.
GE1008
Initial Start-Up Meeting

All global support and project staff using IPMS attends the initial start-up
meeting. This begins the IPMS start-up process.
GE1010
Establish Labor System

The project must decide which labor system to use. The Business Unit typically
defines the labor system. The cost module must be set up specifically for the
chosen labor system.
GE1015
Acquire Financial & Accounting Number

The financial and accounting number is set up in IPMS for the procurement
module and accounting interface.
GE1020
Establish Physical Facilities (Office, Tel, Etc.)

This is a project responsibility.
GE1025
Review Staff Req. & Assign Initial Personnel

This is a project responsibility to define for the start-up.
GE1030
Identify Project Contractual Requirements

The project and start-up team is to identify all contractual requirements that relate
to all IPMS functions and ensure that IPMS setup for all modules complies with
the contract. This is done to assure that contract requirements are addressed
during set-up.

ACTIVITY ID
GE1035
DESCRIPTION
Project Team Review IPMS Package Relationship

Engineering progress measurement is defined by Workpackages in IPMS.
Standard Workpackages are loaded from Corporate. Workpackages are loaded
into Tracking. The Project Team requires training to develop understanding of the
Workpackage concept and options.
GE1040
Identify Personnel & Computer Requirements

The project must identify all personnel and their hardware requirements. The
project should coordinate with IT to ensure that these needs are met.
GE1045
Define Project Execution Strategy

The Global IPMS team will define the next steps to execute IPMS Start-Up.
Responsibilities for all other activities in the start-up schedule will be defined.
GE1050
Identify Project Personnel/IPMS Access & Roles

The project must identify all IPMS users and their roles. The IPMS System
Administrators will set up the users in the project database.
GE1055
Define & Approve WBS and CBS Strategy

Project must define and approve the WBS and CBS. The WBS/CBS is used by all
modules in IPMS.
GE1060
Establish/Update Project Implementation/Execution Plan

The project is to establish a Project Implementation/Execution Plan. The project
and start-up team should review the plan to ensure that IPMS setup for all
modules complies with the plan.
GE1065
Provide Functional & Systems Software Training

Project to identify needs and Global IPMS team will train project staff.
GE1070
Project Team Review Global Default Codes

The Global IPMS team will review all standard codes.
GE1075
Project Team Approve WBS, OBS & CBS

Full project team approval of the coding structures of the Work Breakdown
Structure (WBS), Organizational Breakdown Structure (OBS) & the Cost
Breakdown Structure (CBS) as available in IPMS.

ACTIVITY ID
GE1078
DESCRIPTION
Shared Data Overview Meeting

This is a presentation given by Mike Chidalek to the project to explain how
modules interact.
GE1080
Discuss Process Systems & Services

This is a set-up activity by MRP to put data in a table that provides a list of values
(LOV) for Systems and Services used on the project.
GE1090
Identify & Input WBS/CBS Codes in IPMS

WBS definitions are entered in PMRR1214 and used by all modules. The CBS is
used by the cost module.
GE1110
Establish WBS/CBS
It is the Project Team responsibility to define WBS & CBS.
GE1120
Review WPIDs for Project Start-Up

Project to review standards and ensure that IPMS Start-Up complies with WPIDs
for Project Start-Up.
GE1125
Develop Project Quality Plan

It is the Project Team responsibility to define Project Quality Plan.
GE1130
Prepare Project Procedures

Project to develop all Project Procedures including Procurement & Materials
Management procedures, Procurement procedures and Document procedures will
all be produced for the project and will incorporate agreed IPMS work processes.
GE9999
IPMS Start-Up Complete
Information Technology
IT1000: Establish Instance on Appropriate Server
IT1005: Analyze/Consolidate Hardware/Software
IT1010: Requisition Equipment/Software (TCP/PC210 Etc)
IT1025: Install, Load and Set up Local Equipment
IT9999: IT Complete with IPMS Set-Up
IPMS Startup Schedule Activity Descriptions
05/09/00
IPMS INFORMATION TECHNOLOGY START-UP ACTIVITIES

ACTIVITY ID
IT1000
DESCRIPTION
Establish Instance on Appropriate Server

Set up the IPMS project and copy standard database to project.
IT1005
Analyze/Consolidate Hardware/Software
This is a Project/IT function intended to get the project to determine who needs
hardware and access to IPMS.
IT1010
Requisition Equipment/Software (TCP/PC210 Etc)

This includes acquiring all equipment/software (data lines) necessary to run IPMS
from the project location.
IT1025
Install, Load and Set up Local Equipment

Set up IPMS and AppWorx access on local machines for project staff.
IT9999
IT Complete with IPMS Set-Up
05/09/00
Reference
RE1000: Request IPMS Project/Sub-Project Number from Corporate
RE1010: Review Security Roles
RE1015: Review Discipline Codes
RE1020: Review Project Position Codes
RE1035: Obtain/Populate Financial Related Info (CO/AC/RC)
RE1040: Populate Number & Related Data in Instance
RE1045: Populate Sub-Project & Related Data in Instance
RE1065: Populate Security
RE1070: Populate Project Organization
RE1075: Define Project Process Systems from LOV
RE1080: Link Project Organization to Disciplines/Personnel
RE1085: Extract Project Suppliers from Corporate List
RE1090: Attach Suppliers List to Project
PMRR1215: Review Global & Default Reference Codes
PMRR1410B: Review Standard Narratives & Narrative Models
PMRR1238A: Populate Personnel in Personnel Table
PMRR1240B: Populate Addresses in IPMS
PMRR1240C: Populate Sub-Project Addresses
RE9999: IPMS Reference Tables Set-Up Complete
05/09/00
IPMS REFERENCE START UP ACTIVITIES

ACTIVITY ID
RE1000
DESCRIPTION
Request IPMS Project / Sub-Project Number from Corporate

Upon receiving the IPMS Instance Request, the Project Code (4 Characters) and
the Sub-Project Code (4 Characters) will be populated in IPMS. The Project
Codes is project descriptive and the Sub-Project Code is generally numeric.
RE1010
Review Security Roles

Project activity to review roles available and acknowledge whether or not a
project has needs for special roles which do not exist (special client access, etc.).
RE1015
Review Discipline Codes

Discipline codes are populated in PMRR1230 and is required by all IPMS
modules.
RE1020
Review Project Position Codes

Review the project positions defined for individuals receiving transmittals on the
project. In the transmittal process of Document Management, documents may be
transmitted either to individuals or to project positions.
RE1025
Define Legacy Financial No & Related Data (CO/AC/RC/Job No/BT)

The legacy financial number drives much of the processing in Cost. All financial
information (company, accounting center, responsibility center, job number, and
billing type) must be defined. On the set-up screen, there is the ability to choose
which (CO/AC/RC/Job No/BT) is defaulted to each Award Sub Line Item. Cost
uses this for the commitment process.
RE1035
Obtain/Populate Number & Related Data in Instance

This step is to populate the legacy financial number and the related data Award
sub line item default, different billing types valid on the project, etc.
RE1040
Populate Project Number to Project in IPMS Instance

This step is to populate the approved Project Number in IPMS.
RE1045
Populate Sub-Project & Related Data in Instance

The Project Contract requirement may be addressed by having the option to
choose to have separate sub-projects. Each Sub-Project is managed separately.
This option must be fully understood by the project management before being
deployed. Normal practice is to set the project up as a single sub-project.
05/09/00

ACTIVITY ID
RE1050
DESCRIPTION
Populate Project Addresses - PMRR1240

The project address code must be populated. The address code is used to set the
sub project addresses.
RE1065
Populate Security
Define user roles for tables, forms and views. Users can be connected to a single
or multiple roles in the security table.
RE1070
Populate Project Organization - PMRR1230

The Organization Code for the project must be populated, then linked with the
Discipline Code. Organization Discipline is required when registering any type of
documents to identify the owner and originator of the document.
RE1075
Define Project Process Systems for LOV

This is a set-up activity by MRP to put data in a table that provides an LOV for
Systems used on the project.
RE1080
Link Project Organization to Disciplines/Persons

Link Disciplines to the Organization codes and to Personnel.
RE1085
Extract Suppliers from Corporate List to Populate IPMS

This is a set up activity by the start-up team.
RE1090
Attach Suppliers list to Project

This is a set-up activity by Procurement after the project determines which
Suppliers to populate in IPMS.
PMRR1215
Review Global & Default Reference Codes

This includes a review of all codes for completeness and accuracy.
PMRR1238A Populate Project Personnel

The project personnel name and their Network Access # must be registered and a
title or position must be identified. This is only required for any personnel that
will receive documents.
PMRR1240B Populate Addresses in IPMS
This is required for any physical locations that will submit or receive documents
or materials: the project office(s), the jobsite, client office(s), suppliers, vendors,
fabricators, etc.
10
05/09/00

ACTIVITY ID
DESCRIPTION
PMRR1240C: Populate Sub-Project Addresses

No action is required if a single sub-project is used.
PMRR1410B Review Standard Narratives & Narrative Models
Procurement and Engineering responsibility to review the standard narratives.
Ensure the Document Type field is populated. Tape Clauses can be defined as
needed for project for RFQs or Purchase Awards.
RE9999
IPMS Reference Tables Set-Up Complete
11
05/09/00
MATERIAL REQUIREMENTS PLANNING

PMRR1238: Identify MRP Personnel Codes & Roles
MC1070: Identify RFQW/RFQ/PO Numbering Scheme
MC1005: Identify Coding Structure for Project Tag No EDMS/IPMS
MC1010: Identify & Populate MTO Levels for Project Use
MC1030: Audit/Review Application Utilization
MC1033: Identify Document Numbering Scheme for Engineering MTO Interface
MC1040: Set-Up Bulk Tag Alert Message
MC1050: Identify Spec Automation Responsibilities
MC1075: Confirm Database Link for EDMS/IPMS
MC1085: Review Completeness of IPMS Project Instance
MC1090: Identify & Execute Design & Supplier Interfaces for IPMS
MC1125: Identify MTO Process (System/Manual)
PMDD1140: Populate Tags (Manually)
PMRR1213: Set MTO Sum Start Position & Length
PMRR1240: Define Address Rules & Populate Addresses
MC9999: MRP IPMS Start-Up Complete
Before the database administration group makes a copy of the corporate database, it is requested
that those individuals maintaining the corporate database be notified. This will insure that any
unfinished work that may be active can be committed, and the complete activities will be
reflected in the new instance
MRP has a table identified as BLD_ITEM that has a column name including proj_no. This
particular table must not be updated to the new project number and remain 0000. The script
written to change proj-no has been written as such.
12
05/09/00
IPMS MATERIAL START-UP ACTIVITIES

ACTIVITY ID
MC1005
DESCRIPTION
Identify Coding Structure for Project Tag Nos. for EDMS/IPMS Validation
Define the coding structure for the Project tag number and confirm that data
transfer through EDMS/IPMS Interface satisfies conditions of tag numbers. (WBS
code in correct format, Org-Disc. etc.)
MC1010
Identify & Populate MTO Levels for Project use

Identify and populate the various levels in which the project requirements will be
maintained in material takeoff and material summary. Including valve,
preliminary, intermediate and final material take-offs (MTO).
MC1030
Audit/Review Application Utilization

Ongoing audit/review of how personnel have utilized the MRP application.
MC1033
Identify Document Numbering Scheme for Engineering MTO Interface

The project will determine the document numbering scheme. This is necessary to
begin down loading data into IPMS.
MC1040
Set-Up Bulk Tag Alert Message

The Bulk Tag Alert feature notifies the project MRP via e-mail that MERLIN has
duplicated project valves in the catalog and piping material class.
MC1050
Identify Specification Automation Utilization

Define or confirm who will perform spec automation (MERLIN OR MRP)
MC1070
Identify RFQW/RFQ/REQN/P.O. Numbering System Strategy

Define the numbering scheme for the documents such as RFQW and Requisition.
BUSINESS UNIT has a Standard numbering scheme for Requisitions and POs.
13
05/09/00
IPMS MATERIAL START-UP ACTIVITIES

ACTIVITY ID
MC1075
DESCRIPTION
Confirm Database Link for EDMS/IPMS

Contact Database Administrator to confirm that the interface capability is created
for project implementation.
MC1085
Review Completeness of IPMS Project Instance

MRP responsibility to review MRP maintenance tables for assurance that
Corporate Default Codes are loaded properly.
MC1090
Identify & Execute Design & Supplier Interfaces for IPMS

Define the files that will be utilized for the IPMS interface. These files can be:
Tagged Items; Line Lists; MERLIN (spec. auto) and CAD.
MC1125
Identify MTO Process (System/Manual)

Define the roles for the MTO process. Definition needed if MTO's will be
populated manually by MRP or by electronic transfer?
PMDD1140
Populate Tags (Manually)

Identify whether the tagged items are to be loaded into the system manually.
PMRR1213
Set MTO Sum Start Position & Length

The value used in these fields determines the level of detail that Cost uses to
report project requirements by WBS.
PMRR1238
Identify MRP Personnel Codes & Roles

Confirm assignment of ID. & Corp Code for MRP personnel and identify all roles
that MRP personnel may require for Project (Ex. BBRH065 = H065)
PMRR1240
Define Address Rules and Populate Addresses PMRR1240

Define the association of a material reference number to a specific address to
facilitate the identification during the MTO Process or RFQW/REQN (ex.
destination; origin or admin. address) and populate addresses.
MC9999
MRP IPMS Start-up COMPLETE

Application is ready for the Material Control personnel to begin project activities
14
05/09/00
PROCUREMENT
PO0100: Identify Procurement / Purchasing Responsibilities
PO0220: Identify Procurement WP Numbering Scheme
PO0300: Review Global / Project Variable Reference Codes
PO0700: Develop Project Procurement Plan / Project Procedures
PO0705: Identify Procurement Distribution Requirements
PO0710: Identify Project Suppliers Requirements List
PO0712: Develop Client / Project Approved Suppliers List
PO0725: Identify Procurement Reporting Requirements & Data Dates
PO0730: Identify Procurement Chains with Durations
PMMP1100: Assign Commodity Types/Assign to Material Reference Number
PMRR1232: Review Suppliers by Commodities
PMRR1240A: Identify Procurement Address
PMRR1410: Review, Modify Standard Narratives
PMRR1410A: Modify & Populate Standard Narratives
PO1000: Procurement Set-Up Complete Issue First P.O.
Note: Make sure that the default corporate coding structure to be used for P.O.'s is set on form
PMRR1215. This is part of the IPMS Administration instructions.
15
05/09/00
IPMS PROCUREMENT START-UP ACTIVITIES

ACTIVITY ID
PO0100
DESCRIPTION
Identify Procurement Purchasing Responsibilities

Determine from the project what is to be bought and by whom (Client, 3rd Party,
or Business Unit). In addition, determine what commodities the Business Unit
will buy and where (home office or field). [Non-IPMS activity - part of project
start-up process!]
PO0220
Identify Procurement Work Package Numbering Schemes

Establish the work package numbering schemes to be used on the project
following corporate & Business Unit recommendations whenever possible. The
work package number is intended to be the same as the requisition and PO
number.
PO0300
Review Global Reference Codes PMRR1132/7019

Familiarize project personnel with these codes and determine if there are any that
need to be adjusted for the particular project.
PO0700
Develop Project Procurement Plan / Procedures

This is a standard project implementation task that establishes the ground rules for
how the Procurement effort will be executed on the project.
PO0705
Identify Project Distribution Requirements

Determine what the distribution requirements are for Procurement documents and
reports and provide these to Documentation for input into the project distribution
matrix. [No IPMS forms associated with this activity]
PO0710
Identify Project Suppliers Requirements List

Procurement needs to define and review the project supplier list. Upload of
Business Unit standard can be done and then adjusted for project needs.
PO0712
Develop Client / Project Approved Bidders List PMMP3322

Prepare lists of all bidders for each commodity from the supplier table. Develop
lists of client/project approved bidders for each commodity from these lists.
PO0725
Identify Procurement Reporting Requirements & Data Dates

The data dates are defined by the project and input by Tracking. The project is to
determine which Procurement reports are required regularly by the project and
what the issue frequency is. Provide this information to Document Management.
PO0730
Identify Procurement Chains with Durations

Each Business Unit has defined procurement chains for the projects to use. The
project procurement group can define the activity durations.
16
05/09/00
IPMS PROCUREMENT START-UP ACTIVITIES

ACTIVITY ID
DESCRIPTION
PMMP1100 Assign Commodity Types/Assign to Material Reference Number

Project and procurement to define commodity types for supplier selection.
Product Commodity Code (PCA) assignment can be selected from the glossary.
The project can review RFQ suppliers linked to the PCC product code.
PMRR1232: Review Suppliers by Commodities
Only the project list is transferred to IPMS. This is intended to be a one time
transfer. Additional suppliers identified later will be manually loaded.
PMRR1240A Identify Procurement Address PMRR1240/1241
Determine whether purchases are to be agency 3rd party, etc. and create addresses
with the proper purchasing entity title and liability code.
PMRR1410
Review & Modify Project Standard Narrative Models

Review the corporate standard narratives and modify as needed to make them
project specific. Determine which clauses will be used regularly for which
documents and establish narrative models to group them.
PMRR1410A Modify & Populate Project Standard Narrative Models

Modify and input the models and assign the clauses. Edit all clauses coded with
an ~. to fill in the blanks with project information. Create and input as many
additions/ standard clauses as desired for the particular project.
PO1000
Procurement Setup Complete
17
05/09/00
DOCUMENT MANAGEMENT
DM1025: Review and Update Global and Default Codes
DM1000: Establish Document Management Execution/Responsibility Plan
DM1005: Identify Project Reporting Requirements
DM1010: Identify Job Book/Handover Requirements
DM1015: Review Project SDRL Requirements
DM1020: Identify Project Transmittal Recipients
DM1030: Identify Bar Coding Requirements and Schedule Interface
DM1040: Populate Transmittal Cover Letter
DM1045: Set up Bar Coding
DM1050: Identify Document Numbering Scheme
DM1055: Identify Construction Document Revision Requirements
DM1090: Review DM Access and Roles
DM1095: Populate Hand-Over Work Package Subtype
DM2000: Establish Document Management Project Staff Training
PMDC1102: Populate Document Revision
PMDC1103: Populate Transmittal Distribution Matrix
PMDC1104: Review Recipients Addresses
PMDC1701: Produce tray labels
PMDC170304: Review and Update Global & Default Codes
PMTR1640: Establish Transmittal/Doc Mapping Associations
PMTR1660: Review Document Default Chains
PMTR1660A: Review Transmittal Default Chains
DM2050: Document Management Set-Up Complete (Issue Data)
18
05/09/00
IPMS DOCUMENT MANAGEMENT START-UP ACTIVITIES

ACTIVITY ID
DM1000
DESCRIPTION
Establish Doc Management Execution/Responsibility Plan

The project is responsible to developing the Doc Management Responsibility
Plan.
DM1005
Identify Project Reporting Requirements

The start-up team will review the standard reports in IPMS with the project
document personnel.
DM1010
Identify Job Book / Handover Requirements

The project may or may not have the information for job books in the beginning
of the project, however, the project should follow up to ensure this information is
available as soon as possible.
DM1015
Review Project SDRL Requirements

The default SDRL Code details must be reviewed and updated based on the
project requirements. Each SDRL Code must be set up with review cycles
required, duration of each review cycles, the required copies and media. The
duration of the approval code must also be updated by review cycles of the
document.
DM1020
Identify Project Transmittal Recipients

The project is to identify the project personnel and their positions so they can be
attached in IPMS to transmittals. The start-up team will assist the project
counterpart in loading this information.
DM1025
Review/Update Other Default Document Management Reference Tables

Other Document Management default reference tables must be reviewed and
updated as necessary such as:
DM1030
Transmittal Cover Letter

Document Approval Status
Project Alpha File
Project Subject File
SDRL Review Codes
Qualification Reason
Review Action Type
Identify Bar Coding Requirements

The bar coding requirements will be defined in the start up meetings.
19
05/09/00

ACTIVITY ID
DM1040
DESCRIPTION
Populate Transmittal Cover Letter

The project will define the cover letters to be used for a specific project.
DM1045
Set up Bar-coding
If the project will use the bar-coding functions, then the bar-code hardware must
be installed to the PC system that will be used to do the bar-coding facility. The
network must be set up to facilitate the bar-coding.
DM1050
Identify Document Numbering Scheme

The document numbering scheme for any types of document, Engineering,
Supplier, and General must be identified by the project. Once the document has
been attached to other applications such as Tracking, e.g. Chain, WP, etc. the
document number can not be changed, or deleted.
DM1055
Identify Document Revision

The document revision scheme for engineering, supplier, and general documents
must be identified by the project. Once the document revision numbers are used
by any documents, the revision number can not be changed.
DM1090
Review DM Access and Roles

The project/start up counterpart will determine the access and roles needed for
document management.
DM2000
Establish Doc Management Project Staff Training

The training will be done by the IPMS start-up team as the project requires.
PMDC1102
Populate Document Revision (Engineering/Supplier/General) - PMDC1102

The document revisions for engineering, supplier and general documents must be
populated for both the Business Unit and Client if necessary.
PMDC1103
Populate Transmittal Matrices

The distribution matrix must be populated before creating any types of
Transmittals. The grouping of the matrix must be thought out before starting to
create matrices for all the purposes of transmittals. The grouping e.g. document
types, sub types, organization discipline and etc. The matrix recipients details
such as review actions, required copies and media must be specified. The
distribution matrix is used by the transmittal.
20
05/09/00

ACTIVITY ID
PMDC1104
DESCRIPTION
Review/Update Recipients Addresses - PMRR1238

The personnel address must be reviewed and updated. The address is used when
sending or mailing documents to the recipients.
PMDC1701
Produce Tray Labels

The document recipients bar-code tray labels must be created before using the barcoding functions.
PMDC170304Review & Update Global & Default codes

The document recipients bar-code tray labels must be created before using the barcoding functions.
PMTR1640
Establish Transmittal/Doc Mapping Associations

The default transmittal mapping association must be reviewed and updated for the
project with the scheduler and document management.
PMTR1660
Review/Update Document Default Chains - PMTR1660

The default document (item) chains must be reviewed and updated for the project
with the scheduler on the project. Default chains that will not be use by the project
should be VOIDED.
PMTR1660A Review Transmittal Default Chains

The default transmittal mapping association must be reviewed and updated for the
project with the scheduler. The transmittal mapping will populate the document
milestone dates, using the transmittal issue date and transmittal actual completion
dates.
DM2050
Document Management Set-Up Complete Issue Data
21
05/09/00
TRACKING
PMTRXXXA: Review Corporate Tables From Glossary
PMTRXXXB: Review Default Tables in Project Instance
PMRR1132X: Define & Set-Up Project Calendars
PMTR1085: IPMS Work Package Training with Project Team
PMTR1095: Identify Work Package Numbering Scheme
PMTR1100: Identify Work Package Progress Options
PMTR1105: Engineers/Construction to Identify Work Packages
PMTR1115: Identify Work Package Type and Sub-Types
PMTR1120A: Populate Work Package Type & Sub-Types
PMTR1410A: Identify & Update Work Package Milestones and Chains
PMTR1524A: Review CPM definition tables
PMTR1604B: Review mapping
PMTR1630A: Define & Populate Project Data Dates
PMTR1640A: Review Transmittal Associations with Docs
PMTR1660B: Review default chains {Items)
PMTR9999: Tracking Start Up complete
Tracking needs sub-directories created in the temp directory for each project's subproject. E.g.: if
GPAC was a new project, we would need two sub-directories under the temp directory, one
would be 1990 and the other would be 0638. This is necessary to allow one project that has
multiple projects to run the Tracking Freeze. If we only have one subproject, then the directory
still must be created. Also if we add a new subproject to an existing project, a new sub-directory
must be created for the subproject.
This action item is one of the bullet items listed in the IPMS Database Administration section.
22
05/09/00
IPMS TRACKING START-UP ACTIVITIES

ACTIVITY ID
DESCRIPTION
PMRR1132X Define / Setup Project Calendar

The project is to define the project calendars and dates. The Tracking startup
person will populate in IPMS. Dates must be input to define working days and
times. Calendars need to be set up for engineering, procurement and construction.
PMTR1085
IPMS Work Package Training with the Project Team

The work package training is a presentation done by the Tracking startup team. It
is scheduled by the project just prior to beginning work package development.
Attendees should include the project management, all engineering discipline leads
and project controls.
PMTR1095
Identify Work Package Numbering Scheme

The project will create a work package numbering scheme. This should consist of
a common coding structure that has been defined by the Business Unit. The
maximum length of this number is 13 digits.
PMTR1100
Identify Work Package Progress Options

Each work package must have a progress option selected. The options are P, C, I
and U. This determines how progress is earned. This engineer will determine
which type of progress is to be used when the work packages is defined. Project
controls may assist with this assignment.
PMTR1105
Engineers/Construction to Identify Work Packages

The work group lead engineer will define the work packages for his/her discipline.
The construction work packages may be input from the estimate by the project
scheduler.
PMTR1115
Identify Work Package Type and Subtype

The work package type and subtype table should be reviewed. The Business Unit
has established standards for each discipline. A project has the option to add
project specific codes as needed. A start up person will need to add any project
coding. This must be coordinated with document management to maintain
alignment between items and work packages.
PMTR1120A Populate Work Package Type & Subtypes

The Business Unit standards will be loaded into IPMS once the instance is
established.
23
05/09/00

ACTIVITY ID
DESCRIPTION
PMTR1410A Identify & Update Work Package Milestones & Chains

The Business Unit has established standard chains for each discipline. The
project should review the chains and milestone. The project may make
adjustments for project specific scope and requirements. Adjustment may require
process owner approval. Process owner review is required for all changes to the
chains.
PMTR1524A Review CPM Definition Tables
The Business Unit standard chains contain the CPM definition. The project
should review the CPM definition table. The CPM activities can be adjusted to the
needs of the project. Changes to this table require process owner approval.
PMTR1604B Review Mapping
The mapping table must be reviewed by IPMS startup personnel and adjusted by
the Tracking startup person as required for project procedure and any Milestone
changes.
PMTR1630A Define & Populate Project Data Dates
The project is to define the project data dates or reporting dates. (Mid-Month,
End of Month, Etc.) The Tracking start-up contact will input into IPMS.
PMTR1640A Review Transmittal Associations with Docs
Startup and project personnel for documents, scheduling and tracking must review
the transmittal associations. This table must be adjusted to accommodate chain
defaults and any chain milestone changes.
PMTR1660B Review Default Chains
Default chains must be reviewed by procurement, document, scheduling project
and startup personnel. Item types selected by project personnel must be reviewed
and chain defaults must be adjusted as necessary to assure proper automatic chain
assignment upon item creation.
PMTRXXXA Review Corporate Tables From Glossary
Tracking responsibility to review Tracking maintenance tables for assurance that
Corporate Default Codes are loaded properly.
PMTRXXXB Review Default Tables in Project Instance
Review of standard chain models.

24
05/09/00
ACTIVITY ID
PMTR9999
DESCRIPTION
Tracking Module Functional

Notification of Tracking module functionality is the responsibility of the Tracking
startup representative. Project management and process owners should be
notified.
25
05/09/00
SCHEDULING
PS1000: Develop/Update Level 1 Schedule
PS1005: Issue Standard 120-day Front End Detail Schedule
PS1010: Issue Project Specific 120-day Schedule
PS1020: Develop and Issue Level 2 schedule (Control Package)
PS1030: Project Team to Define Schedule Planning Areas
PS1040: Determine Logic & Durations in CPM & IPMS
PS1045: Define Engineering & Construction Interfaces
PS1050: Review Logic and Durations with PSS Department
PS1055: Review and Adjust Level 3 Early Schedule Dates
PS1060: Approve Level 3 Early Schedule
PS1065: Resource Level the Level 3 Schedule
PS1070: Adjust and Approve Level 3 Schedule
PS1075: Issue Level 3 Baseline
PS1085: Establish Level III Activity Structure
PS1095: Pass Level 4 Activities to ACLS/IPMS
PMTR1210A: Input Work Packages in IPMS
PMTR1210B: Input Work Package Budgets in IPMS
PMTR1555A: Download IPMS Work Package Data to CPM
PMTR1557A: Pass Baseline Dates into IPMS Tracking
Execution Activities:
PS1105: Train Construction Controls on Last Planner Work Plan
PS1115: Train Piping Last Planner on Work Plan Interface
PS1125: Establish Project Work Plan Interface
PS9999: Scheduling Start Up complete
26
05/09/00
IPMS SCHEDULE START-UP ACTIVITIES

ACTIVITY ID
PS1000
DESCRIPTION
Develope/Update Level 1 Schedule

If a Level 1 Schedule was loaded in the proposal, the Project Team should update
this schedule with current information within one week after contract award or
notice to proceed. If a Level 1 Schedule was not included in the proposal the
Project Team will complete one that meets all current contract requirements.
PS1005
Issue Standard 120 Day Front End Detail Schedule

Engineering management has developed a "Standard 120 Day Front-End Detail
Schedule. An electronic file can be downloaded from the Intranet. The project
scheduler will load this file and generate the reports contained in the file.
The Link for this file is:
http://halworld.halnet.com/ss/sspc/sspc_content/plan_scheduling/sspc_pands_pri
mproj.asp
PS1010
Issue Project Specific 120 Day Front-End Schedule

This schedule will contain project specific activities in sufficient detail to control
the project until the Level 3 Baseline Schedule is developed and issued.
PS1020
Develop & Issue Level 2 Schedule

After the Work Breakdown Structure (WBS) is approved, a Level 2 Schedule will
be developed and issued. This schedule will contain at least one activity for each
cost area/discipline combination. Additionally, activities depicting the path of
critical long-lead items should be included. The Level 2 Schedule should meet the
milestones established in the previously issued Level 1 Schedule.
PS1030:
Project Team to Define Schedule Areas

Once the plot plan has been confirmed, the project team will define schedule areas
using the Business Unit Standard. At KBR, First Planner helps to set the duration
of the project activities for each discipline with in a schedule area. The Level III
Schedule will be generated from the First Planner meetings.
PS1040
Determine Logic and Durations in CPM & IPMS

The scheduler will input inter-work package logic and refine the durations to
finalize the CPM network and produce an Early Date schedule. The durations
may need to be adjusted in IPMS to match the CPM dates.
27
05/09/00

ACTIVITY ID
PS1045
DESCRIPTION
Determine Engineering/Construction Interfaces

The scheduler, working with engineering and construction management, will
insert an interface activity between corresponding chains of logic in the
engineering and construction schedules. This interface activity will be used to set
target data for engineering deliverables, and allow sufficient backlog of work for
construction.
PS1050
Review Logic & Durations with PSS Department

When a preliminary CPM schedules is complete, it will be reviewed with Project
Support Services representatives.
PS1055
Review & Adjust Level III Early Schedule Dates

After PSS Department review of the preliminary Level III Schedule, the scheduler
will review the early dates with engineering, construction, and project general
management for approval of the logic, durations and resulting milestone dates.
PS1060
Approve Level III Early Schedule

After review of the early dates, engineering, construction and general project
management should sign the approved block on the schedule.
PS1065
Resource Level the Level III Schedule

Using the appropriate type (time limited or resource limited), the scheduler will
resource level the approved early schedule to optimize resource utilization.
PS1070
Adjust & Approve Level III Schedule (Baseline)

After Resource Leveled Dates are established, the scheduler will review these
dates with the appropriate supervisor and adjust specific activity dates.
PS1075
Issue Level III Schedule

The scheduler will officially issue, by cover letter under the Project Managers
signature, the approved Level III Schedule.
PS1085
Establish Level III Activity Structure

The project will determine the numbering structure for the level 3 schedule IDs.
PS1095
Pass Level 4 Activities to ACLS/IPMS

The pass of level 4 activity information is performed for the Last Planner Work
Plan for construction. This information is passed to ACLS to set pipe priorities.
A file is created by ACLS and passed to the site material control group.
28
05/09/00

ACTIVITY ID
PS1105
DESCRIPTION
Train Construction Controls on Last Planner Work Plan

Training for the Last Planner is required for the controls personnel. This is to
assure the interface is set up properly and the correct information is being passed
from scheduling to ACLS and on to material control.
PS1115
Train Piping Last Planner on Work Plan Interface

The Last Planner Work Plan for pipe determines what should be worked on at any
given time during the project. The material control group can give piping detailed
information about any MTO. This determines if the material is on site and can be
installed by the field.
PS1125
Establish Project Work Plan Interface Procedure

The project will determine the timing of the interface between scheduling, ACLS,
material control and the pipe department.
PMTR1210A Identify & Input Work Packages Into IPMS

Using the approved WBS and working with Engineering Management, the
discipline leads will quantify the scope of work and group the work into work
packages. This includes the estimated work hours. A work package input sheet
will be completed by the work group lead. From this input sheet the scheduler
will enter the work package in IPMS.
PMTR1210B Input Work Package Budgets
During the input step describe above the scheduler will input the work package
work hour budgets defined on the input sheet filled out by the discipline leads.
PMTR1557A Pass Baseline Dates into IPMS Tracking
Depending on how the work packages are mapped to the CPM, certain milestone
baseline dates may not be populated by this process. These dates can be calculated
and added manually (as determined by project requirements).
PMTR1555A Download IPMS Work Packages to CPM
Using the IPMS to CPM Interface Program, the scheduler will download work
package information to the CPM System. The initial download will create
activities with appropriate durations, start and finish data, work hour budgets, and
relationships between activities of the same work package.
PS9999
Scheduling Setup Complete

This is a Finish Milestone indicating that all scheduling startup activities are
complete.
29
05/09/00
COST CONTROL
CC1005: Review Cost Reporting Requirements VS Standards
CC1010: Identity Level of Control for Project Budget
CC1000: Review Global & Default Codes
CC1015: Establish CDT/CDST Budget Defaults
CC1020: Review/Revise GL to Cost Category Codes
CC1025: Populate Currency Default by Month
CC1030: Establish/Populate WBS Codes
CC1035: Populate PCOA/Subproject PCOA
CC1040: Populate Cost Categories for PCOA Table
CC1045: Identify/Populate Control Package Numbering Schemes
CC1046: Establish Extraction Parameters
CC1050: Identify/Populate Bulk Material Allocation
CC1055: Populate PCOA Rules/Material Reference Codes for Tag Items and Non-standards
CC1056: Populate PCOA Rules for Bulk Materials
CC1065: Populate Project Hierarchies for Reporting
CC1085: Load Progress
CC9000: IPMS Cost Module Set-Up Complete
CC1060: Load Estimates
CC1075: Connect WBS/PCOA's to Work Packages
CC1080: Balance Estimate and Populate Control Estimate
CC1047: Create Freeze
CC1048: Post Actual Costs
CC1070: Identify IPMS Variance Matrix Approach
CC1090: Run Cost Summary Report
30
05/09/00
IPMS COST CONTROL START-UP ACTIVITIES

ACTIVITY ID
CC1000
DESCRIPTION
Review all Global and Default Codes - PMRR1132/PMCC1020.

Review and revise Cost Control Code Spec Tables in Reference (PMRR1132).
There are twelve Code Spec Types in Cost: Job Number Billing Type; Cost
Category Type; Cost Freeze Type; Commitment Header Type; Control Type;
Code of Account Type; Curve Type; General Ledger Code; Project Deviation
Notice Type; Problem Group; Allocation Method Type, and Variance Group.
Review Corporate Code of Account Table (PMCC1020).
CC1005
Review Cost Reporting Requirements vs. Standard

Cost reporting requirements, defined in the RFP/Contract, further identification of
client reporting/capitalization guidelines, and B&R Management needs, will
influence coding structure, level of control, variance matrices, labor interface
requirements (i.e. billed vs. actual) and other downstream activities.
CC1010
Identify Level of Control for Project Budget

Identifying control level for the original budget and variances is essential in that
this decision drives activities tied to MRP and Tracking. If the level of control is
at the Tag Item level, the tag member must exist in MRP catalog and the PCOA
must reside in the Tag Item Maintenance table before loading the estimate. If the
level of control is at the work package level, workpackages must exist in the work
package header form prior to bringing the estimate into IPMS.
CC1015
Establish CDT/CDST Defaults for Budgets - PMCC1110

CDT/CDST standards have been established for budget, commitment and actual
expenditure transactions. These need to be reviewed and populated in the project
database. The department process owner must approve any deviations.
CC1020
Review/Revise GL to Cost Category Codes - PMCC1050

IPMS budgets and records expenditures at a more summary level than the GL
Code by grouping like GL Codes and tying them to Cost Categories. The Cost
Category level is the summary level that is used in Cost. Departmental standards
have been established for this activity. They must be reviewed and revised as
required.
CC1025
Populate Currency Default by Month - PMCC1120

This table must be populated prior to any transactions occurring, i.e. loading
budgets and posting actuals. This table is based on the subprojects default
currency and is used for establishing the monthly conversions used by Halliburton
Corp. A conversion, even if it is the same as the subproject default, must be
established for each month of the project duration.
31
05/09/00

ACTIVITY ID
CC1030
DESCRIPTION
Establish/Populate WBS Code Tables - PMRR1214/1216

Upon determination of the WBS Codes to be used on the project, the WBS Code
Type and WBS Codes most be populated right away. The WBS Code table is one
of the most commonly used table by other applications and is required early on in
many start-up activities. Once WBS Codes are established, they should not be
changed.
CC1035
Populate PCOA/Subproject PCOA PMCC1020

Project specific code of accounts for engineering, project management, material
and construction directs/indirects must be populated in the Project Code of
Account Maintenance table. The subproject code of account must also be
populated.
CC1040
Populate Cost Categories for PCOA Table - PMCC1020/1050

Once activity CC1020 has completed, all relative cost cats must be tied to the
project code of accounts (PCOA's) before any budget, commitment or actual
transactions can occur.
CC1045
Identify/Populate Control Packages - PMCC1090

Based on reviews in activity CC1005, relative WBS Code/PCOA combinations
can be established and linked to Control Packages, which are used for reporting
purposes.
CC1046
Establish Extraction Parameters - PMCC1360/1365/1330/1440

The extraction parameters for the labor, accounting, and commitment interfaces
must be established prior to receiving any transactions of these types.
CC1047
Create Freezes
Before actuals are posted in the system, PMCC1700, Freeze Indicator, should be
established.
CC1048
Post Actual Expenditures

Labor and accounting costs can post to the system.
CC1050
Identify/Populate Bulk Material Allocation Method - PMCC1510

If bulk material will be allocated, then bulk PCOA's must have the allocation
method for distribution assigned.
32
05/09/00

ACTIVITY ID
CC1055
DESCRIPTION
Populate PCOA Rules for Tag Items and Non-Standards

Tag items must have a PCOA assigned to them in the Tag Item Maintenance
table. This is accomplished by creating a relationship between the tag number and
a PCOA in the PCOA Rules Table (PMCC1910). All non-standard material
references items must have a PCOA assigned via PCOA Rules Table.
CC1056
Populate PCOA Rules for Bulk Materials - PMCC1910

Like tag item maintenance, PCOA's must exist for each bulk material reference in
the MRP Catalog. To accomplish this, the PCOA Rules Table must be populated
for all bulk material. When all the material references have been populated with
PCOAs, commitments can be brought into the Cost Module.
CC1060
Load Estimate(s) - PMCC1310

The estimate Interface between Program Estimate and IPMS results in this form
being populated. If an estimate is to be loaded from a source other than B&R's
estimate program, a review for record layout must be discussed with Cost support
personnel so that an interface may be provided which will facilitate this activity.
After the loading the estimate, make the Control Type Assignment and release the
estimate to the control level.
CC1065
Populate Project Hierarchies for Reporting - PMRR1610

Certain reports within Cost Module require a hierarchy to be established prior to
executing. These are primarily Cost Comparison type report and Cost/Scheduling
analysis type. They are typically run at a Control Package or Workpackage level.
Obviously, these elements of data must be established before this activity can be
accomplished. Logs, listings, commitment reports and variance reports do not
require a hierarchy
CC1070
Identify IPMS Variance Matrix Approach - PMCC1170

Based on CDT/CDSts and variance types, a matrix must be established in order
for an approved variance to update the required budgets. PDNs, variances and
change orders can be tracked in IPMS.
CC1075
Connect WBS/PCOA's to Workpackage (if required) - PMTR1210

If the control level budget does not include a workpackage number, the
WBS/PCOA tie must be made in the budget pop-up of the Workpackage Header
PMCC1210.
33
05/09/00

ACTIVITY ID
CC1080
DESCRIPTION
Balance Estimate & Populate Control Estimate PMCC1320

The control estimate can be manually entered, released from the detail estimate
(PMCC1310), or loaded from workpackages. The control estimate must validate
against a series of tables within IPMS before it can be released to the Cost
Summary as the original budget.
CC1085
Load Progress PMCC1350

If progress will be reported in the cost module, use PMCC1350 for that purpose.
CC1090
Run Cost Summary Report PMCC1710/1720

All the cost data can be viewed in the cost summary forms PMCC1710/1720 and
printed using the various cost reports.
CC9000
Cost Module Functional
34
05/09/00
SITE MATERIAL CONTROL

PMRR1505: Create Priorities and Priority Dates PMRR1502
PMSC1105: Create Warehouse & Location Bins
PMSC1115: Attach Material Reference Numbers to Bin Locations - PMSC1115
PMSC1140: Establish Max / Max Inventory Levels PMSC1140
PMSC1205: Identify Items for Preventive Maintenance PMCS1205
PMSC1306: Set Parameters for Painted Pipe Extract PMCS1306
PMSC1415: Select Address and Warehouse For Work Planning PMCS1415
Create a warehouse of '001'_DEFAULT and bin location of 'DEFAULT' for each destination
address. IPMS Site Form PMSC1105 is used to do this.
35
05/09/00
IPMS SITE CONTROL & CONSTRUCTION SUPPORT STARTUP ACTIVITIES

ACTIVITY ID
PMRR1505
DESCRIPTION
Create Priorities and Priority Dates

Use this form to maintain the priority codes used by projects/subprojects. The
priority code information is used by MRP and Site Control for Last Planner work
plan.
PMSC1105
Create Warehouse & Bin Locations

Warehouse Locator Maintenance. Use this form to maintain inventory location(s)
for items identified by material reference numbers and stored in a given
warehouse. You can identify one primary location and multiple secondary
locations for each material reference number.
PMSC1115
Attach Material Reference Numbers to Bin Locations

Attach the material reference number to the actual bins in the warehouse.
PMSC1140
Set-Up Max/Min Inventory Levels

Max / Min Maintenance. Use this form to maintain an inventory of items that are
controlled on a reorder-point basis (max/min). Use the max/min feature for items
that are not generally considered as part of the material takeoff process (such as
small-bore pipe).
PMSC1205
Identify Items for Preventive Maintenance

Identify items requiring periodic Preventive Maintenance. Use this form to record
periodic maintenance performed on a tagged item. This form shows the complete
history of maintenance work performed on the tagged item and the next projected
date to perform the maintenance.
PMSC1306
Set Parameters for Painted Pipe Extract

Painted Pipe Selection Parameters. Use this form to identify the parameters and
rules used to extract requirements from the bills of material in the Material
Requirements Planning application. The extracted requirements are copied into
the Painted Pipe module in the Construction Support application.
PMSC1415
Select Address and Warehouse for Work Planning

Work Plan Address Selection for Available Material. Use this form to select
addresses and warehouses that will be used in the work plan available material
extract.
36
05/09/00
QUANTITY SURVEYING
QS1000: Confirm Set-Up of Network ACLS, Access to System
QS1005: Receive Estimate ACSII File
QS1010: Establish ACLS Coding & Sub-coding Structure
QS1015: Load Estimate to ACLS
QS1020: Develop/Load Project ACLS Milestones
QS1025: Set-Up Unit Rate Labor Sub-system
QS1030: Review IPMS Interface, Roles of ACLS Personnel
QS1035: Set-Up Work Plan Interface
QS1040: Perform ACLS Interface
QS1045: Balance Estimate Cost, Tracking & Scheduling
37
05/09/00
IPMS QUANTITY SURVEYING START-UP ACTIVITIES

ACTIVITY ID
QS1000
DESCRIPTION
Confirm Set-Up of Network ACLS, Access to System

Confirm Oracle Network Client Server ACLS Set-Up and access in coordination
with Business Unit IT Representatives. Run ACLS99 Winstall script on ACLS
PCs.
QS1005
Receive Estimate ACSII File

Receive Estimate Control File (ASCII) and review project scope pending WBS
Development.
QS1010
Establish ACLS Coding & Sub-coding Structure

Develop Detailed Sub-code to Control Estimate: Balance Estimate.
QS1015
Load Estimate to ACLS

Load Detailed Control Estimate to various ACLS tables.
QS1020
Develop/Load Project ACLS Milestones

Development/Acceptance of ACLS Project Milestones using the Standard
Milestone Guide list or adjusting to fit the project needs.
QS1025
Set-Up Unit Rate Labor Sub-system

Set-up and attach main stem, area stem and control package to ACLS detailed
codes for rollup and interface with Cost and Scheduling.
QS1030
Review IPMS Interface, Role of ACLS Personnel

Review IPMS interfaces with ACLS, Cost, and Scheduling personnel on IPMS
projects only. Verify work flow process for the Controls Group.
QS1035
Set-Up Work Plan Interface

Review level 4 Id's with Scheduling and Material Control. Verify work flow
process for Last Planner.
QS1040
Perform ACLS Interface

Perform IPMS interfaces according to Controls Group work flow process.
PMAI5010-Work Package download to ACLS
PMAI5040-Control Package Activity download to ACLS
PMAI500X-ACLS Progress back to IPMS
PMAI505X-Work Planner pass to IMPS
38
05/09/00
IPMS QUANTITY SURVEYING START-UP ACTIVITIES

ACTIVITY ID
QS1045
DESCRIPTION
Balance Estimate Cost, Tracking & Scheduling

The project needs to balance the budgets between the controls groups. This
should be done monthly at the very least.
39
05/09/00
40
05/09/00

Startup Schedule Activity Descriptions

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Startup Schedule Activity Descriptions

Uploaded by

Copyright:

Available Formats

IPMS 2000

IPMS GENERAL START-UP ACTIVITIES

Arrange/Conduct Project Kick-Off Meeting

Review Lessons Learned

Initial Start-Up Meeting

Establish Labor System

Acquire Financial & Accounting Number

Establish Physical Facilities (Office, Tel, Etc.)

Review Staff Req. & Assign Initial Personnel

Identify Project Contractual Requirements

IPMS GENERAL START-UP ACTIVITIES

Project Team Review IPMS Package Relationship

Identify Personnel & Computer Requirements

Define Project Execution Strategy

Identify Project Personnel/IPMS Access & Roles

Define & Approve WBS and CBS Strategy

Establish/Update Project Implementation/Execution Plan

Provide Functional & Systems Software Training

Project Team Review Global Default Codes

Project Team Approve WBS, OBS & CBS

IPMS GENERAL START-UP ACTIVITIES

Shared Data Overview Meeting

Discuss Process Systems & Services

Identify & Input WBS/CBS Codes in IPMS

Review WPIDs for Project Start-Up

Develop Project Quality Plan

Prepare Project Procedures

IPMS Start-Up Complete

IPMS Startup Schedule Activity Descriptions

IPMS INFORMATION TECHNOLOGY START-UP ACTIVITIES

Establish Instance on Appropriate Server

Requisition Equipment/Software (TCP/PC210 Etc)

Install, Load and Set up Local Equipment

IT Complete with IPMS Set-Up

IPMS Startup Schedule Activity Descriptions

IPMS Startup Schedule Activity Descriptions

IPMS REFERENCE START UP ACTIVITIES

Request IPMS Project / Sub-Project Number from Corporate

Review Security Roles

Review Discipline Codes

Review Project Position Codes

Define Legacy Financial No & Related Data (CO/AC/RC/Job No/BT)

Obtain/Populate Number & Related Data in Instance

Populate Project Number to Project in IPMS Instance

Populate Sub-Project & Related Data in Instance

IPMS Startup Schedule Activity Descriptions

IPMS REFERENCE START UP ACTIVITIES

Populate Project Addresses - PMRR1240

Populate Project Organization - PMRR1230

Define Project Process Systems for LOV

Link Project Organization to Disciplines/Persons

Extract Suppliers from Corporate List to Populate IPMS

Attach Suppliers list to Project

Review Global & Default Reference Codes

PMRR1238A Populate Project Personnel

IPMS Startup Schedule Activity Descriptions

IPMS REFERENCE START UP ACTIVITIES

PMRR1240C: Populate Sub-Project Addresses

IPMS Reference Tables Set-Up Complete

IPMS Startup Schedule Activity Descriptions

MATERIAL REQUIREMENTS PLANNING

IPMS Startup Schedule Activity Descriptions

IPMS MATERIAL START-UP ACTIVITIES

Identify & Populate MTO Levels for Project use