Você está na página 1de 199

BP.

080 FUTURE BUSINESS PROCESS &


MAPPING
Urbacon Trading & Contracting LLC
Projects
Oracle e-Business Suite Implementation Release 12

Author : Chandra Reddy


Creation Date : 02-Oct-16
Last Updated : 19-Dec-16
Control Number : UCC_PA_BP080_FINAL
Version : FINAL

Approvals:

Name of the Approver Designation Signature

Mr. Manoj Yogi M.M Sr. Cost Control Engineer

Mr. Zaid Hindi Sr. Project Planning Analyst

Mr. Gary Crossman Commercial Manager

Mr. Biju Vadassery Jose Senior Maintenance Manager

Mr. Amjad Jabali – PIH Project Manager - UCC

Mr. U.V.V. Ramana Project Manager - Nalsoft

______________________________________________________________________________________
Date of Submission : 19-Dec-2016
Expected Date of Feedback : 20-Dec-2016
Review Feedback Received Date :
_______________________________________________________________________________________
BP.080-Future Business Process

Document Control

Change Record

Date Author Version Change Reference

21-Nov-16 Chandra Reddy 1.0 No Previous Document


24-Nov-16 Chandra Reddy 2.0 1.0
30-Nov-16 Chandra Reddy 3.0 2.0
16-Dec-16 Chandra Reddy Final 3.0
19-Dec-16 Chandra Reddy Final Final

Reviewers

Name Position

Mr. Mousab Haddad Project Control Director


Mr. Manoj Yogi M.M Sr. Cost Control Engineer
Mr. Zaid Hindi Sr. Project Planning Analyst
Mr. Gary Crossman Commercial Manager
Mr. Amjad Jabali Project Manager – UCC
Mr. Chandra Reddy Project Manager – Nalsoft
Mr. U.V.V. Ramana Project Director - Nalsoft

Distribution

Copy No. Name Location

1 Project Library Urbacon


2 Project Library Nalsoft

Note to Holders:
If you receive an electronic copy of this document and print it out, please write your name on the equivalent of
the cover page, for document control purposes.
If you receive a hard copy of this document, please write your name on the front cover, for document control
purposes.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential ii


BP.080-Future Business Process

Contents

Document Control ....................................................................................................................ii


Introduction .............................................................................................................................. 1
Purpose............................................................................................................................... 1
Sources................................................................................................................................ 1
Document Structure........................................................................................................... 1
Overview of Urbacon Trading & Contracting ........................................................................ 3
Key Terminologies used in Project Costing ............................................................................ 6
Requirements by Area .............................................................................................................. 8
Projects ............................................................................................................................... 8
Organization Structure ...................................................................................................... 8
Project Organization .......................................................................................................... 9
Project Types ...................................................................................................................... 9
Contract Types Contract Scope Industry & Subindustries ........................................... 10
Units ................................................................................................................................. 11
Project Templates ............................................................................................................. 11
Activity Master ................................................................................................................ 11
Resource Types ................................................................................................................ 14
Expenditure Category – Cost Category.......................................................................... 14
Expenditure Types – Cost Codes (CSI Codes) ............................................................... 16
Cost Code Master............................................................................................................. 18
Expenditure Item to Inventory Item Mapping .............................................................. 20
Project Number ................................................................................................................ 21
Project Creation with Project Initiation Document (PID).............................................. 22
Capital Expenditure Project (In House) ......................................................................... 25
BOQ Details & Project Tasks (Work Breakdown Structure) ......................................... 26
Cost Budget by Tasks and Cost Codes ........................................................................... 31
Budget Revision (Internal Budget Change) ................................................................... 35
IBC Assessment................................................................................................................ 38
Project Budget Workflow ............................................................................................... 40
Project Budget Integration with GL ................................................................................ 41
Budgetary Control ........................................................................................................... 42
Project Contract Agreements .......................................................................................... 44
Contract Agreement -Variations ..................................................................................... 46
Defect Liability Period ..................................................................................................... 47
DLP Check List ................................................................................................................ 49
Inventory Item Structure ................................................................................................. 50
Budgetary Control – Custom Requests .......................................................................... 53
Budgetary Process ........................................................................................................... 54
Project Purchase Requisition and Purchase Order ........................................................ 54
Actuals: Account Payables/Site General Expenses (Petty Cash, Telephone
Charges, Site Expenses Etc.,). Transactions – Purchasing & Payables (Project
General Expenses)............................................................................................................ 56
Purchasing & Payables Account Generator ................................................................... 58
Journal Voucher View Access ......................................................................................... 59
Depreciation Cost ............................................................................................................ 60
Site Material Requisition (SMR-With in the same sites) ................................................ 61
Material Issue to Project Site from Store ........................................................................ 62
Material Return from Project Site to Store...................................................................... 63
Equipment Vehicle requisition Form ............................................................................. 65
Purchase Requisitions (Projects) ..................................................................................... 66
Purchase Requisitions for Services ................................................................................. 68
Purchase Requisitions for Subcontract works................................................................ 69

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential iii


BP.080-Future Business Process

Fuel Request ..................................................................................................................... 70


Manpower Request Form (MPRF) .................................................................................. 71
Staff Requisition: .............................................................................................................. 72
Staff Requisition Form (SRF) ........................................................................................... 72
Actuals: Manpower Utilization Cost .............................................................................. 72
Staff Timesheet Cost ........................................................................................................ 74
Actuals: Equipment Utilization Cost .............................................................................. 75
Item Expenditure Inquiry................................................................................................ 76
Work Done Evaluation .................................................................................................... 78
Invoice Evaluation/Payment Application Quantities................................................... 79
Certified Evaluation......................................................................................................... 80
Project Invoicing .............................................................................................................. 81
Payment Certificate (Advance) ....................................................................................... 84
Payment Certificate (Invoice).......................................................................................... 86
Accruals ............................................................................................................................ 88
Project - Revenue Recognition ........................................................................................ 90
Payment Certificate (Final Retention Recovery) ............................................................ 92
Subcontract Process ......................................................................................................... 93
Subcontract Agreement ................................................................................................... 94
Subcontract Liability Statement ...................................................................................... 95
Subcontract Billing: Subcontract Advance Payment Certificate ................................... 98
Subcontract Billing: Payment Certificate (Monthly Invoice) ........................................ 99
Subcontract Billing Retention Recovery ....................................................................... 100
Subcontract Billing Final Retention Recovery.............................................................. 100
Department Budgets ...................................................................................................... 101
Department Budgets - Reporting.................................................................................. 102
Cost to Company Labor ................................................................................................ 104
Cost to Company Staff................................................................................................... 104
Forecasting ..................................................................................................................... 105
Actual Cost Reallocation ............................................................................................... 107
Stock Check .................................................................................................................... 110
MJCR (Monthly Job Cost).............................................................................................. 110
Commitment Cost Reallocation .................................................................................... 116
MCCR of WSD & FSD ................................................................................................... 116
Monthly Company Costing (MCCR)............................................................................ 116
Cost Variance ................................................................................................................. 118
Primavera Activities ...................................................................................................... 119
Primavera to EBS (2 Way Integration) ........................................................................ 120
Scope of Work Liability ................................................................................................. 121
Database ......................................................................................................................... 124
Cashflow Project & Company ....................................................................................... 126
Auto-Accounting ........................................................................................................... 137
Data Requirements ........................................................................................................ 139
Personalization’s ................................................................................................................... 141
DFF’s...................................................................................................................................... 142
Interfaces and Workflows .................................................................................................... 143
Reports .................................................................................................................................. 145
Projects Integration with other Modules............................................................................. 149
Flow Chart: Item Creation ................................................................................................... 150
Flow Chart: PO Receipt ........................................................................................................ 151
Flow Chart: Material Return to Supplier (PO Returns)...................................................... 152
Expense Purchase Flow ........................................................................................................ 153
Future Process Flow: Material Request ............................................................................... 154

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential iv


BP.080-Future Business Process

SMR Complete Process Flow ............................................................................................... 155


Future Process Flow: Subcontract Process Flow................................................................. 156
Future Process Flow: Fuel Flow........................................................................................... 157
EVRF (ADS) Process Flow ................................................................................................... 158
Projects Process Flow ........................................................................................................... 159
Annexure –A1: Organization – Sub-inventory (Pictorial Representation) ....................... 160
Annexure - A: Location - Organization – Sub-inventory ................................................... 162
Annexure – B: Customer Type & Contract Types & Contract Scope & Industries .......... 166
Annexure – C: Industry, Sector and Sub Sector Standard ................................................. 167
Expenditure Category – Annexure - D................................................................................ 169
Expenditure Types – Annexure - E...................................................................................... 173
Unit of Measures – ANNEXURE F ...................................................................................... 190
G&A Details – ANNEXURE G ............................................................................................ 191
Open and Closed Issues for this Deliverable ...................................................................... 194
Open Issues .................................................................................................................... 194
Closed Issues .................................................................................................................. 194

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential v


BP.080-Future Business Process

Introduction

Purpose
The purpose of this document is to:
 Capture UCC key requirements in areas of Projects
 Map the requirements to available functions and processes within Oracle Applications
 Where applicable, highlight the gap and analyze it in terms of suggestions
 Workarounds, customization, interfaces etc.
The identification and mapping of Business Requirements is a critical milestone in the development of the future
solution and should help to give the widest possible project audience a picture of the architecture of the future
information system.

Sources
This Conceptual Architecture document was prepared with inputs from the following sources:
 Handover Sessions, where the UCC Project Team spelled their requirements in each area and handed
over associated documents etc.

Document Structure
This document is composed of four sections:
1) Overview of UCC requirements.
2) Detailed description of requirements in each of the functional areas.
3) The issues within UCC as they currently stand and finally.
4) The functional process flows of Projects.

Section 2- Requirements by Area- uses a tabular format to analyze and map UCC requirements. The various
column headings are defined below:

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 1


BP.080-Future Business Process

Control Number A reference number to identify each requirement and


area with reference to BPS

Functional Requirement A statement of Urbacon Trading & Contracting


requirement.

Description A description and definition of the functional


requirement and the process involved within Urbacon
Trading & Contracting.

Map Does the Oracle system meet the Urbacon Trading &
Contracting requirement? If it does then a ‘’ is placed
in the column. If not then it is highlighted as a GAP. If an
Interface is required this will be indicated as I/F.

PR Refers to the priority of the gap in terms of


WA - Workaround Acceptable
NA - Not applicable
CH - High Priority Customization
CL - Low Priority Customization

Functional This column briefly describes how Oracle maps the


Map/Recommended Urbacon Trading & Contracting requirements or what
Solution solution NALSOFT propose to any gaps identified :
 A description of how Oracle meets the requirement
 What workarounds can be used to meet some of the
gaps
 What Customizations are required to meet the
requirement or a description on why there is a gap
 What interface development is required

Responsibility Which section, within Urbacon Trading & Contracting


will have the responsibility for this business requirement

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 2


BP.080-Future Business Process

Overview of Urbacon Trading & Contracting


UrbaCon Trading & Contracting Company LLC, also known as UCC, is a Qatari based international construction
Services Company and a leading grade one licensed builder. Our impressive construction footprint in Qatar is led
by our ever growing pool of trained professionals. With over 4,718 experts and 33,812 tradesmen coupled with
more than 2,143 plants and machines, we mobilize ample resources on the spot and meet demanding schedules.

The success of our company is not only due to our highly capable team and vast resources; it is also a result of
UCC’s unique, fast-track strategies that streamline design and construction milestones, unlike any other
traditional building construction undertaking. At UCC, we engage in parallel activities for design, procurement,
and construction. As a result, we deliver projects with innovative solutions, in shorter time periods, and exceed
our clients’ expectations. This strategy is both fundamental and paramount to our business model as it builds
trust, which is at the cornerstone of our core values.

Our reputation for delivering robust turn-key services and high-quality developments is driven by our
commitment to building neighborhoods and enhancing the community at large. We are dedicated to Qatar's
National Vision of 2030 and aim to fulfill our contribution through UCC’s continued relationships with our
clients, customers, and the community.
Specialization:

 Residential, Hospitality & Entertainment

 Stadiums, Landscaping & Agriculture

 Retail, Offices & Governmental Buildings

 Marine

 Heavy Construction, Infrastructure & Tunneling

 Health & Education

Services

 General Contracting.

 Project Construction Management.

 Engineering, Procurement and Construction (EPC).

 Design and Build.

 Lump Sum and Turn Key Contracting.

 Industrial, Mechanical and Engineering Projects.

 Logistics.

 Operation and Maintenance (O&M).

 Real Estate Development.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 3


BP.080-Future Business Process

 Concept and Master Planning.

 Heavy Marine Works.

The key features/processes that the Project costing implementation should support are:

Organizations A Project organization will be defined in UCC Company. This organization


is used in Auto-accounting to derive company segment value.
Ex:- HCN – Hotel and Complex of Al-Najadh Souq
Project Templates Project templates enable you to quickly create projects that share common
features and have a number of predefined attributes and options. After you
create a new project using a project template, you can customize it to make it
unique, if necessary. The Quick Entry feature makes it easy for you to define
specific project attributes (such as the project name, project description, key
members etc.) whenever you create a project based on a project template.

Project & Task A project is a primary unit of work that you can break down into one or
more tasks. You charge the transactions you enter in Oracle Projects to a
project and a task.
You organize your project work into smaller, more easily manageable units
called tasks. A project structure can contain an unlimited number of tasks,
and as many task levels as you want. You can number and name the tasks as
you wish.

Budget A budget is an estimate of the financial performance of a project. You can


create budgets to plan and manage the financial performance of projects
throughout the project life cycle. You can also utilize budgets to track
ongoing project performance and project status by comparing budget
amounts to actual amounts using reporting tools.
Budget will be entered for each Task by resource (Expenditure type) and
time is from date & to date of task.

Expenditure Types An expenditure type is a classification of cost that you assign to each
expenditure item. Expenditure types are used to enter the Project related
expenses.
Ex:- Excavation, Mobilization, Manpower.etc

Transactions  Material Transactions will be transferred from Inventory to Projects


 Manpower usage transactions will be interfaced from Time and
attendance custom Module
 Supplier Invoices will be transferred from Payables to Project costing
 Expense purchase accruals will be transferred from Purchasing to
Project costing

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 4


BP.080-Future Business Process

Auto accounting Each expenditure item's accounting transactions are held as cost distribution
lines. Cost distribution lines are debit amounts. Oracle Projects creates lines
for costs. Auto accounting determines the General Ledger accounts based on
auto accounting rules to which Oracle Projects charges transactions. Oracle
Projects uses the accounting from Auto accounting when it generates
accounting events for the cost distribution lines. Create accounting process
creates final accounting for the accounting events and transfers to General
Ledger.

Integration Project Costing is Integrated with Payables, Purchasing, Inventory,


Receivables, General ledger, Time & attendance (custom) and Human
resources

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 5


BP.080-Future Business Process

Key Terminologies used in Project Costing

Project/Task owning Organization – This Organization can own and manage Projects and task.

Project Expenditure Organizations – These Organizations can incur expenditures, and hold budgets for projects
in the processing operating unit.

PA Period: – Project accounting periods (PA Period) track Project data on a periodic basis. PA periods can be
used for budgeting and for accounting for cost. PA period would be monthly for UCC which will be shared with
Monthly GL period.

GL Period – These are GL periods with in Oracle Projects. This is the accounting calendar attached to the ledger

Project Currency – The currency in which project amounts are summarized for Project summary reporting.

Transaction Currency - Currency in which the transactions are performed.

Expenditure Item date - The date on which work is performed and is charged to a project and task.

Expenditure Category -This is group of all expenditure types. UCC Refers Expenditure Category as Cost Code
Category.

Expenditure Type - Group of the expenditure items. It is the head under which expenditure is incurred. UCC
refers Expenditure Types as Cost Codes

Raw Cost -The Direct Cost is called Raw Cost. The raw cost is the actual cost of the work performed

Bill Through Date – The date through which you want to invoice a project. When Oracle Projects generates an
invoice, it picks up revenue distributed expenditure items that have an expenditure item date on or before this
date and events that have a completion date on or before this date.

Draft Invoice: – A potential project invoice that is created and stored in Oracle Projects. Draft invoices require
approval before they are officially accounted in receivables

Draft Revenue – A project revenue transaction that is created and stored in Oracle Projects.

Revenue: - In Oracle Projects, the amounts recognized as income or expected billing to be received for work on a
project.

Revenue Budget - The estimated revenue amounts at completion of a project. Revenue budget amounts can be
summary or detail.

Un Billed Receivable: - The amount of open receivables that have not yet been billed for a project. Oracle Projects
calculates unbilled receivables using the following formula: (Unbilled Receivables = Revenue Accrued - Amount
Invoice)

Work Breakdown Structure – The Hierarchy of tasks is called as work breakdown Structure. Oracle Projects
processes tasks based on their position in the WBS. The distinct positions are:

 Top Task: A task whose parent is the project


 Lowest Task: A task that is at the bottom of the WBS, without any child tasks

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 6


BP.080-Future Business Process

Key Members – Key members are employees who belong to a project and can Enter and maintain project data

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 7


BP.080-Future Business Process

Requirements by Area

Projects
Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility
Number Requirement

PA.BP.1.0 Currently Project wise Stores are maintained in  In Future, Each project store will be defined as an Organization. SETUP
Organization
UCC.
Structure
Project Name will be taken as Organization Name and project
Each Project Store is defined as an Organization location will be defined as Organization Location.

Project Name is taken as Organization Name and In future Cost Control Department want to follow Alphanumeric
project location is defined as Organization sequence numbers as Organization Code.
Location.
Example:
Organization Code is continues 5 Digit Serial
Number. Project Number: U0295HCNS

Example: Project Name: Hotel & Complex of Al-Najadah Souq

Project Number: U-295-295-14-HCNS Project Location: Hotel & Complex of Al-Najadah Souq

Project Name: Hotel & Complex of Al-Najadah Organization Code: A01


Souq
Organization Name: Hotel & Complex of Al-Najadah Souq
Project Location: Hotel & Complex of Al-Najadah
Souq Organization Location : Hotel & Complex of Al-Najadah Souq

Organization Code:10301 Note: Central Store will be defined as a separate Organization.

Organization Name: Hotel & Complex of Al- Please refer Annexure- A for Future Organizations Details.
Najadah Souq

Organization Location : Hotel & Complex of Al- Please refer Annexure- A1 for Inventory Organization structure in
Diagram.
Najadah Souq

Depending on different Scenarios/criteria like

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 8


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

1. Size of the projects


2. Small projects at same location (Near to
each other) etc.
One store is maintained for multiple projects.

Currently UCC is having a Central warehouse in


Umm Al Hawaya.

PA.BP.2.0 A project organization is required to define  In UCC, a separate inventory organization will be defined for SETUP
Project
projects in project module and all commitment Projects and this organization is enabled with following
Organization
and actual costs will be tracked against the Project classifications to take care of project requirements.
Organization and projects.
Project/Task owning Organization:

Project/Task Owning Organizations can own projects and/or tasks


in the operating unit. To own projects and tasks in an operating
unit, an organization must have Project/task owning organization
classification must be enabled.

Project Expenditure/Event Organization:

Project Expenditure/Event Organizations can own project events,


incur expenditures, and hold budgets for projects in the processing
operating unit. To have these capabilities in the operating unit, an
organization must have the Project expenditure/event classification
must be enabled.

PA.BP.3.0 A Project type is used for grouping a project based  A Project type is used for grouping a project based on the type class. SETUP
Project Types
on the type class. The project type determines The project type determines how Oracle Projects processes costs and
how Oracle Projects processes costs and revenue revenue for a project and provides defaults and controls for project
for a project and provides defaults and controls entry and processing. It is a primary classification for all the
for project entry and processing. projects. At least one project type has to be set up to create projects
in Oracle Projects.
At higher level these project types have been
categorized by UCC.
The class attached to the Project type is Contract
Reports and Dashboards can be developed based
on project types. Project type will be assigned to project Template and sub-

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 9


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

sequentially, it will be assigned to projects.

While defining a new Project user needs to make sure that he select
correct option based on the type of project.

The following project Types will be defined

 General

Project Type Field Size: 20 Char

PA.BP.4.0 UCC Would like to capture the following details GAP CL Following fields should be provided in the PID document SETUP & Project
Contract Types
in the system and would like to generate reports Key User
Contract Scope
on the same.  Customer Type
Industry &
Subindustries  Contract Types
 Contract Types  Contract Scope
 Contract Scope  Industry
 Sector  Sector
 Subsector  Sub Sector

For Full Details of Customer Types, Contract Types, Contract Scope


and Industry, Please refer Annexure-B

For Full Details of Sector and Sub Sector, Please refer Annexure-C

A Look up “Customer Type” should be created to maintain the


Customer Type Master.

A custom form needs to be developed to maintain the Master for


Contract Types, Contract Scope, Industry, Sector and Subsector.

Whenever a PID is created in the system, cost control department


should select the Predefined Types from the list of value.

Note: Complete Final List provided by UCC is attached in Annexure


B and C.

Please refer MD050 for more details.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 10


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

PA.BP.5.0 Unit of Measurements  Units are nothing but unit of measures which specifies quantities or SETUP
Units
amounts of an expenditure item. These units are attached to
expenditure types. This Unit of Measures can be used for physical
quantity of work done at site.

Ex:
Effective Dates
Code Meaning Description
From To
KG Kilogram Kilogram 01-JAN-1951
$ Currency Dollars 01-JAN-1951

For Full Details of Units, Please refer Annexure-F

PA.BP.6.0  Project template will be used to define project information that does SETUP
Project Templates
not typically change for each new project created from the Template.

We can define typical work breakdown structures and task


durations for common projects. Once templates are created it can
be used to create a project by copying a project template and then
changing specific values.

A project template includes the following elements:

 Basic project information


 Work breakdown structure (WBS)
 Project and task options, including key members
 Budgets (optional)
 Quick Entry fields which specify fields to enter for the new
project when creating it from a template

Based on the project types following template will be defined:

 UCC TEMPLATE

PA.BP.7.0 High Level Summary Master GAP CH A custom form should be developed to maintain High Level SETUP
Activity Master
Summary Codes in the System.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 11


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

The form should contain 8 Levels of Activity Codes.

Header Level:
 Operating Unit
Line Level:
 High Level Code
 High Leve Code Description
 L1 Code
 L1 Description
 L2 Code
 L2 Description
 L3 Code
 L3 Description
 L4 Code
 L4 Description
 L5 Code
 L5 Description
 L6 Code
 L6 Description
 L7 Code
 L7 Description
 L8 Code
 L8 Description

Note:
1. Length of Each Level of Code should be 8 Digits.
2. UCC should be able to use any no of Digits out of
8 Digits.
3. Least Level code will be used for Actuals Cost
Capturing.

The control of the master should be with Cost Control Department.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 12


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

For Budgets and Actuals capturing, any level can be used apart
from highest Level Codes.

In a project multiple levels of Activity Codes should not be used.


Please refer below example

Example:
S NO DESCRIPTION UOM

A Civil Works
A01 Earthwork CUM
A011 Dewatering System GPA
A012 Earthwork (excavation & backfilling) CUM
A013 Termites Control SQM
A03 Shoring & Guniting System LM
A031 Shoring System, -----m deep LM
A032 Guniting Work SQM
A05 Concrete Works CUM
A07 Formwork SQM

From the above table, the following validation needs to be


incorporated in BOQ Details screen.

4. A011 and A01 should not be used in same project


for Budgeting purpose or Actuals Capturing.
System should validate and stop BOQ upload and show error in
BOQ Upload Screen.

Error: “Different Levels of Activates Exists”

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 13


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

5. A032 and A01 can be used in same project.

6. Highest Level (A: Civil Works) should not be


allowed to be used in Budgeting or actuals.

Nalsoft will check the feasibility in the Build Phase.

Note: UCC Needs to Provide the final Activity/High Level


Summary Code Master.

Please refer MD050 for more details

PA.BP.8.0 UCC is using CSI Codes are Expenditure Types GAP CH UCC is not going to use Resource Types directly in any of the SETUP
Resource Types
and categorized CSI Codes to different Resource processes, UCC Would like to maintain the Resource Types in the
Types. system for reporting. Different Reports like Monthly Job Costing,
Cost Variance and Etc will be generated based on resource Types.
UCC would like to track all the resources types in
the system.
A Lookup set will be created for defining Resource types.
First Digit of the Cost Code is Resource Type.
Look Up Details will be as follows
Example:
 Lookup Name: UCC_RESOURCE_TYPES
Cost Code Description  Description: UCC Resource Types
L2011030 Civil Helper The Resource Types which are going to be defined in the Lookup
E1032130 Drilling Machine are
G3021160 Temporary Car Park Shed Type Description
M2031100 Concrete Forming- Plywood L Labor
M Material
G General Requirements (Prelims)
E Equipment & Vehicles
S Subcontractors
D Design & Supervision
C Contingencies & Provisions
PA.BP.9.0 UCC has categorized Cost Codes at higher level  Expenditure Category: SETUP
Expenditure
and would like to track the same in the system for
Category – Cost
reporting purpose. Expenditure category describes the source of UCC organization's

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 14


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Category costs. For example, an expenditure category with a name such as


Example: Labor refers to the cost of labor. An expenditure category with a
name such as Supplier refers to the cost incurred on supplier
CSI Category Description invoices.
M1030000 Concrete
M1040000 Masonry & Plastering Expenditure categories (Cost Categories) can be used in Auto
M1050000 Metals Accounting rules and in reporting. Expenditure categories are used
G3010000 Office Facilities for grouping expenditure types (Cost Codes) for costing.
G3030000 Utilities Connection
E1020000 Heavy equipment Ex: - M1030000 - Concrete.
E1030000 Light equipment
Lower Cost Category of UCC will be defined as Expenditure
S1040000 Masonry
Category in Projects Module and Lower Cost Category description
S1080000 Openings
will be defined as Expenditure Category Description.

Expenditure Category at Projects will be as follows


Effective Dates
Name Description
From To
M103 Concrete 01-JAN-1951
M105 Metals 01-JAN-1951
M122 Plumbing 01-JAN-1951
E102 Heavy Equipment 01-JAN-1951
E103 Light Equipment 01-JAN-1951
S104 Masonry 01-JAN-1951
S103 Finishes 01-JAN-1951
L201 Labor Charges 01-JAN-1951
G409 Electricity Charges 01-JAN-1951

The following Cost Category Creation process is agreed to be


followed in future.

Whenever a new Cost Category is required to be created at


PMV/WSD/UCC/FSD, the Cost Category details (In Agreed

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 15


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Format) will be shared with Cost Control Department (User should


be nominated).

Nominated user will check Cost Category Details and Create an


Category in the system.

If user want to stop using a Category, the same can be end dated.
Inactive Categories cannot be used for any further transactions,
however existing costed records will not have any affect.

Note: Before End dating the Category, user need to make sure that
all cost related to that Category is transferred to Projects Module.

Please refer Annexure- D for Cost Category (Expenditure Category)


Details

PA.BP.10.0 UCC Would like to Maintain CSI Codes as  Expenditure Type SETUP
Expenditure
Types – Cost Expenditure Types. An expenditure type is a classification of cost that you assign to each
Codes (CSI UCC would like to maintain Cost Codes at UCC expenditure item you enter in Oracle Projects and is made up of the
Codes) Level. following elements:

Cost Code Structure:  An expenditure category (Cost Category) (used to group


expenditure types for costing)
E 4 01 0000  A revenue category (used to group expenditure types for
revenue and billing)
(Cost Group, Higher Cost Category, Lower Cost  A unit of measure
Category, Descriptive Cost Category)  One or more expenditure type classes

UCC Would like to follow the below Cost Code Cost Codes will be defined as Expenditure Types in Projects
Structure Module.
T Gro Su D Description Expen
y up b C diture Ex:-
p C Type
e
L 2 01 10 Civil Helper L2011 Expenditure Type/Cost Code Description
30 030
L2011030 Civil Helper
L 2 01 10 Carpenter L2011
L2011060 Carpenter
60 060

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 16


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

M 1 03 31 Ready Mix M1033 M1053000 Metal Decking


00 Concrete 100 G3021130 Temporary Shelter
M 1 05 30 Metal M1053 E1031160 Compactor
00 Decking 000 S2031100 Concrete Forming
G 3 02 11 Temporary G3021
30 Shelter 130
Expenditure Type is codified as follows
E 1 03 11 Compactor E1031
60 160
Ty Group Sub DCC Description Expendit
S 2 03 11 Concrete S20311
pe ure Type
00 Forming 00
L 2 01 1030 Civil Helper L2011030
L 2 01 1060 Carpenter L2011060
The length of the cost code structure that is
M 1 03 3100 Ready Mix M1033100
maintained by UCC is 8 characters.
Concrete
UCC would like to maintain the same in the M 1 05 3000 Metal Decking M1053000
future. G 3 02 1130 Temporary Shelter G3021130
E 1 03 1160 Compactor E1031160
UCC, PMV and WSD/FSD should maintain one S 2 03 1100 Concrete Forming S2031100
cost code master only and the master will be
maintained by Cost Control Department (UCC).
Expenditure Types in Projects Module
Whenever a new cost code is required to be
created, the cost Code Details will be shared with Name Exp Revenue UOM Description
UCC Cost Control Department (In Agreed Category Category
Format) and UCC Cost Control Department
L2010000 L2011030 Other HRS Civil Helper
Validates and Creates the code in System.
L2010000 L2011060 Other HRS Carpenter
M1030000 M1033100 Other ITEM Ready Mix
Concrete
M1050000 M1053000 Other ITEM Metal Decking
E1030000 E1031160 Other HRS Compactor
S2030000 S2031100 Other ITEM Concrete
Forming

The following Cost Code Creation process is agreed to be followed


in future.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 17


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Whenever a new Cost Code is required to be created at


PMV/WSD/UCC/FSD, the Cost Code details (In Agreed Format)
will be shared with Cost Control Department (User should be
nominated).

Nominated user will check Cost Code Details and Create an Cost
Code in the system.

If user want to stop using a Cost Code, the same can be end dated.
Inactive Cost Codes cannot be used for any further transactions,
however existing costed records will not have any affect.

Note: Before End dating the Cost Code, user need to make sure that
all cost related to that Cost Code is transferred to Projects Module.

Please refer Annexure- E for Cost Code (Expenditure Type) Details


PA.BP.11.0 Cost Control Master cannot be maintained in Standard Projects Project Cost
Cost Code Master UCC would like to track all the following details GAP CH
of Cost Codes in the system. Module. Control
Department User
 Cost Group
 Higher Cost Category A Custom form should be developed to maintain all the below
 Lower Cost Category category levels.

 Detailed Cost Category


A custom form should be developed in such a way that all the Cost
Groups can be mapped in a hierarchy.

Example:
A Detailed Cost Category Should be linked to Lower Category,
Lower Category should be linked with Higher Cost Category and
Higher Cost Category should be linked to Cost Group.

Expenditure Categories:
Custom Interface should be developed in such a way that the
combination of Cost Group, Higher Cost Category, Lower Category
should be interfaced to Standard projects module as Expenditure
Categories. Lower Category Description should be interfaced to
projects module as Expenditure Category Description.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 18


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Example:

Type HHC LCC LCC Description Expenditure


Category
M 1 03 Concrete M103
M 1 05 Metals M105
M 1 22 Plumbing M122
E 1 02 Heavy Equipment E102
E 1 03 Light Equipment E103
S 1 04 Masonry S104
S 1 03 Finishes S103
L 2 01 Labor Charges L201
G 4 09 Electricity Charges G409

Expenditure Types:
Custom Interface should be developed in such a way that the
combination of Cost Group, Higher Cost Category, Lower Category
and Detailed Cost Category should be interfaced to Standard
projects module as Expenditure Types. Detailed Category
Description should be interfaced to projects module as Expenditure
Type Description.

Example:
Ty Group Sub DCC Description Expendit
pe ure Type
T 4 03 1190 Investigations & T4031190
Testing
T 4 06 1230 Built Form Design T4061230
L 2 01 1030 Civil Helper L2011030
L 2 01 1060 Carpenter L2011060
M 1 03 3100 Ready Mix M1033100
Concrete
M 1 05 3000 Metal Decking M1053000

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 19


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

G 3 02 1130 Temporary Shelter G3021130


E 1 03 1160 Compactor E1031160
S 2 03 1100 Concrete Forming S2031100

Note: 2 Custom Interface Custom Programs needs to be developed


to Interface Expenditure Types and Expenditure Categories to
standard projects module.
 Create Expenditure Categories
 Create Expenditure Types

Whenever a new Cost Codes are defined, user need to run the
“Create Expenditure Category” first and then “Create Expenditure
Types”.

System should automatically identify the new cost codes created in


the Cost Code Master Custom Form and should interface new
Values to Standard Screens.

Note: High Level Summary Codes should be linked with Cost


Codes in this custom form. One Code will be linked to one High
Level Summary Code only. One High Level Summary Code can be
captured to Multiple Cost Codes.

PA.BP.12.0 For material issues, Each Item needs to be mapped with Each SETUP & Project
Expenditure Item Expenditure Type Mapping with Inventory Item. GAP CH
to Inventory Item Expenditure Type. A Separate custom form will be provided where Cost Control
Each Inventory item will be mapped with an Expenditure Type. User
Mapping UCC Want Expenditure Type/Cost Code
population in Inventory and Procurement Process
Automatically based on selected item. UCC needs to provide Inventory Item with Expenditure Item. UCC
has agreed to provide the same.

Control of Item to Expenditure Type mapping will be with Cost


Control Department. UCC need to nominate a user for the same.
Note: If item is not mapped with Expenditure Type, Item cannot be
used for Material Issues Transactions.

2 separate column

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 20


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Unit of measure
 Conversion
Should be provided in the Item Expenditure Type Mapping custom
form. UOM of the Expenditure Types defined in Projects Module
should be populated against each Expenditure Type and
Conversion Factor should be defined against Item UOM and
Expenditure Type UOM.

UCC needs to provide Conversion values of Inventory Item UOM


with Expenditure Item UOM. UCC has agreed to provide the same.

Owner of the form will be Cost Control Department and details


needs to be provided by Cost Control Department.

PA.BP.13.0 Project Number:  When a project is awarded, Finance department will create the SETUP
Project Number
project number in the GL module and forwards PID document to
Currently UCC is following the below Project cost Control Department with Project Number information.
Numbering Structure

U-656-656-16-OSRC Cost Control Department creates project in Project Module.

(Company Name – Sequence of Project Number – In Future UCC will follow below Project Numbering Structure
Sub Sequence of Project Number – Year – Project
Name Short Code)
Project: UXXXXXXXX
All Project, Site & Finance Users are very fond of
the above project number structure. Project Number will be 9 Digits and structure is as follows
The project will be remembered based on U – Company
Sequence Number (656) and Project Name Short XXXX – Project sequence Number
Code (OSRC) and sometimes combination of both XXXX – Project Short Code
(656-ORSC).

While migrating open projects to EBS, UCC For accounting purpose these project numbers needs to be defined
would like to track old project number also. in the auto accounting lookups, an interface shall be done in such a
way that when a project is created in Projects window, the same will
be automatically created in auto accounting lookups.

While Migrating Open Projects, Old Project number can be tracked


in Project Description. Users can query the project in Project Module

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 21


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

with description also.

UCC Projects and Finance Departments has confirmed that the same
structure will be maintained in COA Project Segment also.
PA.BP.14.0 Project Creation with PID GAP CH Project template will be used to define project information that does Project Cost
Project Creation
with Project not typically change for each new project created from the Template. Control User
Project Number Generation: We should define typical work breakdown structures and task
Initiation
Document (PID) durations for common projects. Once templates are created it is used
At Present UCC is following the below Project to create a project by copying a project template and then changing
Numbering Structure specific values.

U-656-656-16-OSRC
Projects can be created in Oracle Projects in the following way
(Company Name – Sequence of Project Number –
Sub Sequence of Project Number – Year – Project 1. Quick Entry in Oracle Projects (Manual)
Name Short Code) a. Copying from an existing Template

All Project, Site & Finance Users are very fond of Quick Entry in Oracle Projects (Manual)
the above project number structure.
To create a new project, an existing template needs to be identified
The project will be remembered based on that best matches to the project. When project is created from a
Sequence Number (656) and Project Name Short template, Oracle Projects copies the project, its work breakdown
Code (OSRC) and sometimes combination of both structure, and all of the project and task options to the new project.
(656-ORSC).
Project Number is Manual and Alphanumeric. At the time of Project
Project Initiation Document (PID) is the base creation, key user enters the following information.
document for UCC to create project. It contains all  Project Number (List of Values)
the necessary (mandatory and optional)
information for the creation of project like  Project Name
 Project Name  Project Description
 Customer  Project Start Date
 Currency
 Project Finish Date
 Duration (Start and Finish Dates) and
other key information.  Project Key member
 Project Customer
Template is provided by Cost Control
Department.
The Initial Project Status is ‘Unapproved’. Before entering the
Once the required information is entered, the transactions, it has to be changed to ‘Active’. Transactions can be
project will be submitted for approval. entered only for Approved Projects.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 22


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Note: Only Approved projects can be used for Note: - When new Project is announced, same Project number needs
Actual Transactions. to be defined in Project Segment of chart of accounts and sub-
sequently it is used in Projects Auto-accounting for generating
Same PID document is used for creation of Project accounting entries. In the absence of same, system will not generate
in Primavera. Sr. Projects Analyst carries out the any accounting entries for this project and gives error.
task.
Project Creation Process:
UCC Would like to Capture all PID Information in
project creation window. Validations on each When a new project is awarded, Cost Control Department creates
fields should be discussed in details. PID Document in the system and sends it for approval.

Approval Hierarchy:

Cost Control  Project Manager/Director  Deputy CEO  CEO


and Publish

PID Maintains the following statuses:

 Draft
 In progress
 Active
 Completed

A button “Create Project” should be provided in PID Custom


Screen. When PID is approved, Project creation user should select
the “Create Project” button to create a project in projects module
automatically.

In Standard Projects Module, a Project should be created with


following information

 Project Number
 Project Name
 Project Start Date
 Project Finish Date
 Customer

Note: Create Project button should be available only when the PID
Status is “Active”.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 23


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Initial Status of the project will be Design. Based on requirement,


Cost Control Department changes the project status from Design to
Active to use the project for Actual Transactions.

Following Project Statuses will be maintained by system

 Cancelled
 Completed
 Design
 Running Construction
 Pre Contract
 On Hold
 Maintenance (DLP)

Based on phase of the project, different statuses will be selected for


the project.

Some of the major fields which will be provided in PID document


are

 Project Number
 Project Name
 Customer
 Project Start Date
 Project End Date
 Contract Type
 Contract Scope
 Industry
 Sub Industries
 Old Project Numbers (Different fields for different systems
like Dynamics Project Number, Old Project Number, Old
Primavera Project Number Etc.)
 Contract Start Date
 Contract End Date
 Insurance Details (Different Fields) Etc.,

Note:

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 24


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Old Project number and No of fields details should be provided by


Cost Control department

When project is created in projects module, the same project number


should be linked automatically with COA Project number in Auto
Accounting Lookup Sets to make sure accounting accuracy.

For more details, please refer PID MD.050 Document.

PA.BP.15.0  Using capital projects, UCC will define capital assets and capture Project Key User
Capital
Expenditure construction-in-process (CIP) and expense costs for assets which are
Project (In House) creating. When assets are ready to place in service, UCC can
generate asset lines from the CIP costs and send the lines to Oracle
Assets for posting as fixed assets.

UCC would use the CAPITAL Project type for their internal
projects. The costs will be accumulated against the project like other
normal projects.
When Project type is capital project, entire project amount is
available for transfer to fixed assets module.

When Projects is completed, finance department changes the Project


status from “Approved” to “Pending Close” for verification. When
verification is completed, finance user enters the asset book and date
place-in service for asset amount. When entry is completed, user
clicks on “Generate Asset Lines” in capital project window. Then
system generates asset lines for entire project amount.

When asset lines are generated, same will be transferred to fixed


assets module by running PRC: Interface Asset lines to Fixed Assets.
Then Asset lines will be transferred to fixed assets and it is available
in mass additions window as a new asset. Then Asset user can add
these lines to existing asset or create a new asset from Mass
additions work bench.

After transferring the project value to fixed assets, Project status will

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 25


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

be changed from “Pending Close” to “Closed”.

When depreciation is run, CIP asset clearing account which was


transferred from projects will be credited and asset cost account will
be debited
PA.BP.16.0 When a project is awarded to UCC, Project will be GAP CH In Standard Application BOQ Details cannot be captured. Project Cost
BOQ Details &
created in Candy by referring PID Document. Control User
Project Tasks
Custom Process needs to be developed to maintain BOQ Details in
(Work
Cost Control Department Loads the Client BOQ the system.
Breakdown
Structure) and perform Budget against the BOQ using
Project Resources in Candy. Custom Process:

Users would like to load the same (With Details The following process should be followed
Resource Breakdown Structure) in Oracle EBS.
When a project is awarded to UCC, Cost Control Department will
At present only one type of Budget is maintained create project in Candy with information available in PID
by UCC which is Control Budget. UCC Would Document.
like to Maintain Master Budget and revised
budget in EBS. Cost Control Department Loads the Client BOQ and perform
Budget against the BOQ using Project Resources in Candy.
All revised budget needs to be requested through
Internal Budget Change (IBC) and approved Note: EBS will not maintain any resource master as Resources
request will be connected to IBC statement and change from project to project and a standard resource master is not
the same will be considered as Revised Budget. maintained by UCC.

Approval Hierarchy: Initiator  Commercial All the BOQ’s with Resources will be exported to Excel (In EBS
Manager  Project Manager  Project Director  format).
Sr. Cost Control Engineer  Cost Control
Manager  Sr. Estimator  Cost Control Director A custom screen should be developed where all the BOQ’s with
Resources can be loaded for validation “BOQ Details Validation
Status of Budgets: Approve, Reject, Change Form. The following information should be available for loading
Request and Delegate.
Header Details:
Assessment Hierarchy:
Sr. Cost Control Engineer  Cost Control  Operating Unit
Manager  Cost Control Director  CEO.  Project Number
 Project Name
Once budget change is approved, UCC want to
send notification to all approvers. Line Details:

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 26


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 BOQ Code – Price Code


 BOQ Description
 Bill Quantity
 Final Quantity – Budget Quantity
 Unit
 Net Rate – Budget Rate
 Selling Rate
 Net Final Amount – Budget Amount
 Selling Amount
 Trade Code
 Trade Code Description
 Cost Code
 Cost Code Description
 Resource Code
 Resource Code Description
 Resource Unit
 Resource Quantity
 Resource Final Rate
 error

The custom form will validate all lines and show the error messages
against the BOQ Lines

Validations:

Following conditions needs to be checked while uploading BOQ


details in the system

 Unit of Measures used in Candy should be same as EBS


 Cost Codes used in Candy BOQ should be same as EBS
Cost Codes/Expenditure Types
 BOQ Quantity Should not be Less than Zero
 BOQ Value Should not be Less than Zero
 Resource Quantities Should not be Less than Zero
 Trade Codes should in candy should be same as EBS
 BOQ Description should not be null
 If Final Quantity is Zero, it is not required to calculate
Resource Rate

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 27


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 If Resource has a final Amount, System should validate


weather BOQ is mapped with Cost code. If cost code not
mapped, System should show error.

EBS should following values in interface form and show the % of


deviation.

 Selling Amount (Selling Rate * BOQ Quantity)


 Resource Values (Resource Rate * Resource Quantity)
 Cost Code Rate (Sum of all resource Rates)
 Net Rate (Sum of all cost Code Rates)
 Net Final Amount (Selling Rate * Final Quantity)

Candy will push the data to EBS with 6 Digits in Rate columns, EBS
should recalculate all the above mentioned values and show
difference of Percentage (Absolute Error) in value each BOQ wise.
(Difference between EBS Calculation and Candy interfaced
calculation)

The Absolute error should be shown at header level for whole


project as well. If the Percentage difference is more than agreed
percentage, cost control department will not load the BOQ to EBS.

If any errors are found against the BOQ lines, user can update the
same in Candy and upload the information to custom form again for
validation.

Once the details are validated and errors doesn’t exist, user can click
on create button which will load all the BOQ’s to BOQ Details
Custom Window

Once the BOQ’s are uploaded to BOQ Details Custom Forms, the
same should be submitted for approval.

BOQ Details screen consists of following information

Header Details:

 Operating Unit
 Project Number

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 28


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Project Name
 Created By
 Status
 Version No
 Budget Type (Master Budget and Revision Budget).

Note: First uploaded budget will be considered as Master Budget


and the revised budgets will be considered as Revision Budgets. The
same will be identified with Budget Type at Form Header Level

Line Details:

 BOQ Code – Price Code


 BOQ Description
 Bill Quantity
 Final Quantity – Budget Quantity
 Unit
 Net Rate – Budget Rate
 Selling Rate
 Net Final Amount – Budget Amount
 Selling Amount
 Trade Code
 Trade Code Description
 Cost Code
 Cost Code Description
 Resource Code
 Resource Code Description
 Resource Unit
 Resource Quantity
 Resource Final Rate

Approval Hierarchy: Initiator  Commercial Manager  Project


Manager  Project Director  Sr. Cost Control Engineer  Sr. Cost
Control Manager  Sr. Estimator  Cost Control Director

Following statuses will be maintained in BOQ Details Form

 Draft

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 29


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Inprocess
 Approved

Note: Only Approved BOQ Details will be considered in reporting


and interfaces

Once the BOQ are loaded in Custom form, Activities should be


created automatically in the Task window.
Work breakdown structure (WBS)
Normal Projects:
When a new project is awarded, the same will be created using a
project template. Project template will be used to define project
information that does not typically change for each new project
created from the Template.

The Tasks can be created in the templates and the same will be
copied to Projects when a project is created by copying a Template.

The work breakdown structure for any project shall be defined at


the initial stage of the project and additions to the task structure
shall be done as the need arises. Care should be taken as to defining
sub-tasks for a task which has expenses accumulated under it.

As Oracle Projects does not allow defining of additional sub tasks


for a particular task for which costs have been already been
accumulated nevertheless peer tasks can be defined and added to
the Work Breakdown structure.

BOQ Projects:

UCC is going to use High Level Summary Codes as Tasks in EBS.

Actual Cost of the Project will be captured at High Level Summary


Codes & Cost Code Level and Budget is also going to be performed
at the same level.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 30


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

High Level Summary Codes are linked with BOQ which are
prepared in Candy. The same shall be imported to EBS.

Based on BOQ Upload, Cost Codes should be identified and Cost


Code Related High Level Summary Codes should be interfaced to
Projects Module as Tasks.

Note: A custom Form needs to be developed to create link between


Cost Code and High Level Summary Codes. In high level summary
master custom form, a field will be provided to link Cost Codes
with Activities. Based on the link established, the activities in actual
transactions will be defaulted based on selected/defaulted cost
code.

Please refer BP.PA.7.0 for more details on High Level Summary


Master.

Note: Personalization should be done in Standard Tasks screen in


such a way that user cannot update any Tasks values in Standard
Budgets Screen.

Project Start and End Dates will be taken as Task Start and Ends
Dates.

Please refer MD.050 for more details and field level validations.

PA.BP.17.0 Cost Budget Integration to GL GAP CH Normal Projects: Project Key User
Cost Budget by
Tasks and Cost
A budget is an estimate of the financial performance of a project.
Codes
UCC will create budgets to plan and manage the financial
performance of projects throughout the project life cycle. UCC can
also utilize budgets to track ongoing project performance and
project status by comparing budget amounts to actual amounts
using reporting tools.

When new Project is awarded, same is created in Project costing

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 31


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

with Tasks. Task wise, Project Level planning will be done for the
project in Budgets window.

Project cost budget contains the following information


 Task Information
 Raw cost
 Unit of measure
 Expenditure types (Manpower, Material, Machine, Sub-
Contracts and General Expenses)
 Exp. Type Qty

UCC would use the Approved Cost Budget type (Pre-defined) for
entering all the project related budget amounts.

Approve the submitted budget by performing Base lining action.


Only a Base lined budget is available for budget Vs actual
comparison and also for Budgetary Control.

A version control maintained for all the changes made to a budget


and tracked as history.

Verification with regard to the budgetary limits availability will take


place against the Base lined budget defined for a project.

In standard application BOQ wise budget details cannot be


captured.

In Standard Application, Budgets can be entered against a task and


Cost Code.

Budgetary Control cannot be performed in the system without


Standard Approved Cost Budget. However to perform Budget
check in the system, Standard Budgets needs to be created.

Once the BOQ’s are uploaded and approved by the authority, the
same should be interfaced to Standard Project Budgets screen by
selecting Interface Budget Button.

Custom Process:

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 32


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Customization needs to be performed to Interface the budget value


to standard Project Budgets and subsequently to GL for enabling
Budgetary Control.

Before Interfacing Budgets to Standard Screen, Tasks needs to be


created in the system as Task and Cost Code wise budget is created
in standard Budgets screen.

Please refer BP.PA.17 for information on Task/High Level


Summary Code Creation Process.

UCC is going to use High Level Summary Codes as Tasks in EBS.


The High Level Summary Codes can be called as “High Level
Activities”

Actual Cost of the Project will be captured at High Level Summary


Codes & Cost Code Level and Budget is also going to be performed
at the same level.

High Level Summary Codes are linked with Cost Codes which are
prepared in Candy. The same shall be imported to EBS as Tasks.

Note: Until High Level Summary Codes are interfaced as Tasks in


Standard Application, user should not be able to Interface Standard
Cost Budget.

Once the tasks are interfaced, User should select Create Cost Budget
button to create cost Budget in Standard application.

Following information should be interfaced to standard Cost


Budgets

 Task Name
 Cost Code
 Cost Code Description
 Unit of Measure
 Quantity
 Amount

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 33


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Note: Unit of measures are maintained against each code in EBS.

Each Cost Code has multiple resource planned under it with


different resources UOM. If the Cost Code UOM is LS (Lumpsum),
Sum of all the resource Quantities will should be shown as Cost
Code Quantities.

If a Resource has a different UOM measure than LS, System should


calculate the quantity based on UOM Conversion maintained in the
system.

The converted Quantity should be interfaced to Standard Budgets


screen.

Note: If a cost code is used in candy for which Account mapping is


not performed, System should show an error message with Cost
Code details that “Account Mapping does not exist for following
cost code/s”

Once the Budget is interfaced to Standard Budgets screen, Following


program needs to be run “Interface Project budgets to GL” to
transfer Budget amounts to GL.

First Version of Budget is considered as “Master Budget” and


changes cannot be made to master budget. Whenever changes
occurred in budget, changes will be tracked with version number
and treated as running budget.

Cost Code and Account mapping will be maintained in Projects


Module.

Note: Personalization should be done in Standard Budgets screen in


such a way that user cannot update any budget values in Standard
Budgets Screen.

Note: UCC Need to nominate a key user who should perform


account mapping task whenever a new cost code is created.

Whenever a new Account with 5 Series is created, the same needs to

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 34


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

intimate to Cost Control Department (Email) so that Cost Control


department can map Cost Code for the Account.

Please refer PMV BP and WSD Projects BP080 documents for details
on WSD, FSD and PMV Budgets.

PA.BP.18.0 Internal Budget Change GAP CH The following custom screens and Workflows needs to be Project Key User
Budget Revision
developed to track IBC activities
(Internal Budget
Currently UCC is maintaining IBC system to track
Change)
or perform Budget Changes for a project. Custom Screens:

Whenever a Budget needs to updated, users  IBC Change Reason Setup


creates a Request in IBC System by selecting any  IBC Requisition
one of the Reasons.  IBC Summary Details
Predefined Reasons are available with UCC. Each  IBC Requisition Approval Setup
Reason has different purpose to serve.  IBC Assessment Approval Setup

Example: Workflows
 Approved Variation: In this user can
change the rate in the cost budget but  IBC Requisition Approval Workflow
not the quantity.  IBC Assessment Approval Workflow
 Unapproved Variation: In this user can Interfaces
only change quantity in the cost budget  IBC Requisition to Budgets
but not the rate.
Please refer MD.050 for more details and field level validations.
Cost Control Department controls the reasons
matrix master. Process:

User will not be able to create a change request Whenever a Budget needs to updated, users creates a Request in
until following fields are entered IBC Custom Requisition Screen by selecting any one of the Reasons.
Project ID
Description of IBC Reasons List of Value will be populated from IBC Change Reason
Reason Setup Form.

The request is sent to hierarchy for approval. Predefined Reasons are available with UCC. Each Reason has
Once the Budget change request is approved, the different purpose to serve.
details are sent to Cost Control Department for
revising Budget and same is imported in EBS as Reasons used by UCC are as follows
Revised Budget.
 Reason A – Item requested by Client/Consultant (No VO)
UCC is expecting complete IBC Process in

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 35


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Projects.  Reason B – Item requested by Client/Consultant (With VO)


 Reason C – Changes based on management decisions
UCC is expecting Two-way hyperlink to see the  Reason D – Estimating Error in the Budget
request from Assessment, Revised budget and  Reason E – Change in Method of Construction
vice a versa.  Reason F – Revision of drawing in design and build
projects
Budget Approval Hierarchy details needs to be  Reason G - Value Engineering
shared by UCC Cost Control Department.  Reason H - Release of concept budget
 Reason I - Changing of Cost Code

Reason A: Item Request by Client/Consultant:


In a case where the Client/Consultant requests changes to the scope
without approving a Variation order and management agrees to
execute this change as such.

Reason B – Item requested by Client/Consultant (With VO)


In a case where the Client/Consultant requests a change with a
Variation order/Instructions.

Reason C – Changes based on management decisions


In a case where management decides to execute a change to the
project scope that will enhance the overall image of the company,
given that these instructions will not have an impact on the sale
value of the project.

Reason D – Estimating Error in the Budget


Any items missed completely during the preparation of the estimate
or the budget of the project. Mistake in the quantity take-off during
the preparation of the estimate or the budget of the project and
Wrong Rate Build-up (This can be anything that affects the rate of
the activity such as: Wrong resource rates, wastage factors, usage,
productivity, utilization …etc.).

Reason E – Change in Method of Construction


In case the operation team decides to change the method of
construction from that specified item in the budget.

Reason F - Revision of drawing in design and build projects


This only applies to design and build projects, where the design is
changed and results in a new set of drawings.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 36


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Reason G - Value Engineering


In cases where UCC suggest alternate materials, products or
methods to meet the requirements of the original scope. This is only
if it is approved by the consultant / client without affecting the
project value.
Reason H - Release of Concept Budget
During the preparation of the initial budget, some items will be
estimated in a rough way with available detailed information such
as drawings, specifications, or subcontractors …etc. This concept
budget which is reserved from that specific scope can be released to
a detailed one when the scope/Information is available. This reason
will also be used for the adjustment of PS and PC rate items in the
contract or if UCC need to reallocate the budgeted management
contingency.

Reason I - Changing of cost codes and task codes


In a case where the original cost codes / task codes have to change
in the budget due to reallocation of cost codes / task codes in the
initial phase in the same resource category.

Reasons which CANNOT be consider for IBC

 Future rate changes or price escalations.


 Negotiations which subcontractors/suppliers which
change the unit rate.
 Changes to project organization and/or personnel during
Project execution.
 Changes to the project duration (Acceleration or Delay) if
not approved with the cost implication by the
client/consultant.
 In a situation where additional contingencies are required

Each Reasons will have their own fields level validation and the
same will be detailed in MD050

Cost Control Department controls the reasons matrix master.

User will not be able to create a change request until following fields
are entered

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 37


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Project Number/Project Name


 Description of IBC (Manual Entry)
 Reason
 Proposed Items
 Attachments

The request is sent to hierarchy for approval. Once the Budget


change request is approved, the details are sent to Cost Control
Department for revising Budget (Candy) and same is imported in
EBS as Revised Budget.

Approval Hierarchy: Initiator  Commercial Manager  Project


Manager  Project Director  Sr. Cost Control Engineer  Sr. Cost
Control Manager  Sr. Estimator  Cost Control Director

Please refer MD.050 for more details and field level validations.

PA.BP.19.0 GAP CH Once the IBC request is approved, Cost Control will make the Project User
IBC Assessment
required changes in Candy and upload the BOQ Details to EBS as
revised Budget.

Process of BOQ upload with all the validations will be applied on


revised BOQ as well.

Please refer PA.BP.17 for details of BOQ upload.

Along with above validations the following validations will be


applied when revised BOQ’s are uploaded.

1. If any activity was removed from uploaded BOQ, System


should check whether any actual transactions exists for the
Activity. If any actual transactions exists, system should
show an error message.
Assessment Hierarchy:
Sr. Cost Control Engineer  Sr. Cost Control Manager  Cost
Control Director  CEO.

Status of Budgets: Approve, Reject, Inprocess, Draft.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 38


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Customization needs to be performed to Interface the budget value


to standard Project Budgets and subsequently to GL for enabling
Budgetary Control.

While uploading the Revised Budget Change, the following are


mandatory

1. Project Number
2. Project Name
3. Revision Date
4. IBC Number.

If an IBC number is used once, the same number should not be


available for uploading another revision of BOQ’s.

Tasks Revision

Whenever changes happen in BOQ, the changes will be made in the


Candy Application and same will be loaded to BOQ Detail Custom
Screen.

When the loading is performed, the system should check the


following

 New High Level Summary Code (Tasks) added


 Existing Activity Codes deleted

If any new High Level Summary codes(Tasks) are identified, the


same should be interfaced to Tasks window when BOQ is uploaded
and users selects Create Tasks option in BOQ Custom Screen

If any existing Tasks are removed, system should check whether the
tasks are used for any actual cost capturing.

If Not: When Create Tasks button is selected, Task will be removed


from Tasks Window.

If Yes: System should stop uploading of BOQ with the error


message as follows

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 39


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

“Following Tasks have been used for Actual Cost Capturing”

Budget Revision:

Based on revised BOQ, Budget needs to be recalculated and


interfaced to standard projects budgets with following information

 Project Number
 Revision Number
 Revision Date
 Task
 Cost Code
 Quantity
 Value
Once Budget is interfaced to standard projects module, following
program needs to run automatically and interface the Budgets
information to GL (Accounting Combination based on cost codes).

“Interface Budget to GL”.

Please refer PA.BP.17 and PA.BP.20 for more details on Budget


Interface to GL

Please refer MD.050 for more details and field level validations.

PA.BP.20.0 Project Budget GAP CH After cost budget amounts are entered for a Project, accounting SETUP
Workflow entries should be generated based on budget amounts & resources
(expenditure types) entered for a Project. These accounting entries
will be generated based on expenditure types if Budget workflow is
customized. Otherwise, user needs to enter the Budget accounting
combination for each expenditure type manually. After accounting
entries are generated, it will be transferred to General Ledger.

Note: Cost Control Department needs to map the expenditures

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 40


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

types to Budget accounts to create a budget in GL module.

PA.BP.21.0 Project Budget  Projects budget integration feature enables to integrate project SETUP
Integration with budgets with non-project budgets. A non-project budget is a budget
GL defined outside Oracle Projects (General Ledger).

To use budget integration, UCC needs to do the following:


 Define organization-level budget in Oracle General Ledger.
 Define budget integration for projects.
 Enter project budget amounts and generate accounts for each
project budget line.

The budget baseline process validates the submitted budget version,


creates a baseline version, generates accounting events, creates
budget journal entries in final mode and validates the
Budget amounts against a GL budget.

 Import budget journal entries in General Ledger.


 Review and post the budget journal entries to add the project
budget amounts to the GL budget balances.

Note: It is agreed that Budgetary control at GL would be advisory


only. Whenever requisition is created, if budget exceeds, system
shows Warning message and proceeding with requisition approval.

Accounting definition for Budget interface to GL

Account From
Company Company from Project Organization
Division Division from Project Type
Department Constant
Account Account from Expenditure Type
Sub-Account Subaccount from Expenditure Type
Project Project from Project Number
Employee Constant
Inter Co Constant
Future Constant

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 41


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Please refer PA.BP080.21.0 for more details on Budgetary Control

PA.BP.22.0 UCC would like to have Budgetary Control at  In Oracle Projects, there are two options to control Budgets. Project Key User
Budgetary
Purchase, Subcontract, services Requisition and
(PA.BPS.14.0) Control
Purchase Order Level for Inventory and Expense Advisory and Absolute. Based on the requirement of the project, the
Items. Value based Budgetary Control is expected control can be enabled by the finance user.
by UCC. Budget will be checked Cost Code wise.
Absolute Control: User cannot raise a Purchase Request or Purchase
Last Purchase Price should be shown in the PR. Order if Budget is not available (Budget Check Fails)

UCC Would like to see the following details in PR Advisory Control: when Budget check is failed, System will show a
while budgetary check is done. message to user that he is exceeding the Budget. User can click on
OK and proceed with his transaction.
 Balance Budget
 Available Stock, Commodity Wise Control is project wise control. In same Project Organization, One
(Quantity, Cost and Total Value) project can have Absolute control and One can have Advisory
 Balance Committed Control. It is mandatory to have either one of the controls (Either
 Total Budget Advisory or Absolute).
 Hyperlink to All window is required to
substantiate the same. UCC has agreed to go with Advisory control for all the projects.

Budget also need to be linked with comparison Standard Budgetary Control Processes:
statement while finalizing the subcontract
package.  Purchase Requisition
 Purchase Order
 Payable Invoice

Example Of Budgetary Control:

When budget is created for a cost code, account wise budget will be
created in Leger Module.

Account and Cost Code mapping will be performed in Project


Costing Module. The control will be available with Cost Control
Department. Project Budget will be automatically created and
interfaced to GL based on BOQ uploaded.

Please refer PA.BP.17 for more details on Project Budget interface to

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 42


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

GL.

If Budget of 10000 was performed for a cost code, the details will be
shown as follows

Budget Encumbrance Actual Balance


Amount Amount Amount Available
10000 0 0 0

Once a request or purchase order of 4000 is raised against the cost,


the details will be updated as follows

Budget Encumbrance Actual Balance


Amount Amount Amount Available
10000 4000 0 6000

When actual transaction performed (Cost Booked for the project),


the transaction will be shown as follows. Assume Actual was
performed for 3000

Budget Encumbrance Actual Balance


Amount Amount Amount Available
10000 1000 3000 6000

When a new request for 3000 is raised against the same cost code,
the details will be shown as follows

Budget Encumbrance Actual Balance


Amount Amount Amount Available
10000 4000 3000 3000

At any point of item user can see the above values each cost code
/Account wise.

The same is applicable for all Budgetary control processes

Note: Reconfirmation required on Budgetary Control

Value Based Budgetary control will be maintained in all above

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 43


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

processes.

PA.BP.23.0 Currently After Creation of project, Agreement is GAP CH Agreement & Funding: Project
Project Contract
created by Commercial department to track Commercial User
Agreements An agreement represents any form of contract, written or verbal
Contract related information.
between contractor & customer. An agreement provides a funding
to project & tasks. Each and every project should have an
Following Details are required to be captured in
agreement with customer name & contract value.
the Contract Agreement.
All revenue & invoices in project billing are recorded against an
1. Employer agreement.
2. Date of Contract
3. Form of Contract
Whenever new project is awarded, an agreement needs to be
4. Contract Documents
defined with the following options
5. Contract Commencement Date
6. Date of Position of Site  Customer Name (Client Name)
7. Currency  Number (Project Number)
8. Contract Reference number
9. Customer Order number  Type (Agreement Type)
10. Payment terms  Currency (QAR)
11. Project Manager
 Amount ( Contract Value)
Agreement has revisions.  Terms (Payment Terms)
 Description (Contract Description)
 Administrator (Default Employee who is creating
agreement)
 Creation Date
An agreement definition is mandatory before generating any
revenue or invoice for a project. Whenever Project value is changed,
contract value needs to be changed in this window.

Project Funding:
Funding a Project before accrue revenue and invoice is a mandatory
step in Project Billing. Funding is a step that allocates an amount
associated with customer agreement value to Project. The total
amount of allocated project funding value should be equal to Project
revenue budget amount in order to successfully baseline the project.

After agreement is entered, same form is used to allocate the

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 44


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

amount to project

In funding window, user will specify the following information


 Project Number
 Task (Optional)
 Date Allocated
 Funding amount
 Funding classification (Original/Additional) – Initially the
classification value is “Original”. When amount needs to be
added, then value is “Addition”

When amount is entered against a Project, it is shown as allocated,


not base lined in funding summary window. Then it needs to be
base lined in funding inquiry window.

Project should have a start and end date to perform Baseline action.

A version control maintained for all the changes made to a budget


and tracked as history.

Based on Contract Value in Agreement, customization should be


done in such a way that agreement is automatically created in
project module.

Agreement Custom Form:

A Custom form needs to be developed to track all the contract


Agreement details against a project.

Custom form should consists of following details.

1. Employer
2. Date of Contract
3. Form of Contract
4. Contract Documents
5. Contract Commencement Date

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 45


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

6. Date of Possession of Site


7. Currency
8. Contract Reference number
9. Customer Order number
10. Payment terms
11. Project Manager
12. Contractor All Risk
13. Insurance Details
14. DLP Period Etc

Whenever a new project is awarded, after creation of project in


projects module, Commercial Department user should navigate to
Projects Agreement Custom form and enter all the mandatory
information in the Agreement custom Form.

Once all the required information is entered, the agreement will be


submitted for approval. Initial status of the document will be Draft
and the document status will be changed to Inprocess when the
document is submitted for approval.

Once the document is approved by Hierarchy, the status of the


document will be changed to Approved.

If the document is rejected by any of the approver, the agreement


status will be changed to Rejected and the user will be able to
update all the information the document and resubmit for approval
again.

Approval Hierarchy: Initiator  Commercial Manager  Project


Manager  Project Director

Once the agreement is approved, User should select ”Create


Standard Agreement” and “Create Revenue Budget” buttons to
create agreement and revenue Budget for the project.

Please refer MD.050 for design of Project Agreement Custom form.

PA.BP.24.0 Currently whenever variation comes in contract, GAP CH Whenever Variation Occurs in the contract, Commercial department Project
Contract
Agreement is revised and sent for approval based navigates to Contract Agreement Custom form and Create revision Commercial
Agreement -
on hierarchy. for the Contract Value in the Agreement Custom Form. User
Variations

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 46


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

UCC Commercial Department need to provide Revision will be tracked in separate Field with Revision Number (1,
the hierarchy details. 2, 3 etc.). Revision “0” will be considered as the base version.

In future, UCC would like to maintain the Commercial department updates the revised contract value in the
variation details in the system. UCC want to send agreement and submit the document for approval.
notifications to concerned users when agreement
is updated(Variation Order) Initial status of the revised document will be Revision Draft and the
document status will be changed to Inprocess when the document is
submitted for approval.

Once the document is approved by Hierarchy, the status of the


document will be changed to Approved.

If the document is rejected by any of the approver, the agreement


status will be changed to Rejected and the user will be able to
update all the information the document and resubmit for approval
again.

Users can see all the versions of agreement by querying Agreement


with Version Number. Version History will be maintained.

Approval Hierarchy: Initiator  Commercial Manager  Project


Manager  Project Director

Once the agreement is approved, User should select ”Create


Standard Agreement” and “Create Revenue Budget” buttons to
create agreement and revenue Budget for the project.

PA.BP.25.0 Defect Liability Period GAP CH Defect Liability Period: DLP Key User
Defect Liability
Period
Currently when project is completed and moved
to Defect Liability period, the Project is handed The status of a project will change from Execution to DLP once the
over to DLP Department. DLP Department is Project Handover takes place. Execution Team will submit the
creating a new project and tracking the DLP Cost. handover forms along with supporting documents to DLP Team,
and with mutual confirmation (from both teams) of a successful
Currently DLP budget is created in main project handover, the project status will be changed to DLP.
itself and the same budget is getting transferred to
the DLP Project while handing over the Project to Note: DLP budget is planned in the main contract by cost control
DLP Department. department; same budget will be handed over to DLP Department
for budget planning.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 47


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

DLP Budget will not be revised at any


circumstances. DLP budget shall only be affected by Purchases or sub-contracts
initiated by DLP Team.
A separated cost code is maintained for DLP
Projects. This cost code will be activated only Note: All transactions initiated by Execution Team shall be
when the project moves to DLP. considered as (Main Contract) cost; even the release of the final 5%
retention (despite that it is performed by DLP team).
Handover Process: Once Project is completed by
operations department, Commercial department Note: Main Contract activities should not affect DLP budget neither
checks for all the documents like if they are cost nor revenue.
 Take over certificate (It will be issued
from the date DLP Starts)
All the Key Members of DLP should be added as key members and
 Operations and Maintenance Manual
Role restriction should be provided based on Assignment of Key
 As build drawing etc. Members to the project.

While Handing over the project to DLP


Department, Pending retention Percentage Note: DLP Budget is planned in the main contract by cost control
collection is also handed over. DLP Team is department, Same budget will be handed over to DLP Department
responsible only for performance certificate and for Budget Planning.
submittal of request for final payment (If any)
Budget: Budget Created by UCC Main Contract/DLP Department
should be used for Budget Check.

Cost: Costs incurred by DLP Team can be booked totally as UCC


cost, or partially / completely back-charged to other sub-contractors
(plus overheads & profits as necessary). When a cost is back-
charged to others, the same value is reimbursed to DLP budget.

Revenue: DLP Projects will not have any billing process. Saving of
the Budget amount after calculating all costs which are incurred will
be considered as profit. The same profit will be used to calculate the
performance of DLP Department.

Project will change from DLP to Completed – Yet to be Closed when


client Performance Certificate is received, and to Completed when
client performance certificate is received as well as the project has
been fully invoiced and there are no outstanding receivables
(including full retention), and bonds / guarantees have been
returned back to UCC.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 48


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Note: Revisions of Budgets should not be allowed for DLP Activities


unless there is any variation in Main Contract.

PA.BP.26.0 DLP Department would like to track the flowing GAP CH Whenever a contract is handed over to DLP, the following check list DLP Key User &
DLP Check List
check list in the system. is maintained by DLP department to track the details of documents Project User
handed over to DLP department. (Responsibility)

Note: The close out of project should be possible only after these
documents are cleared to DLP and approved by management.

Management needs to confirm the list of applicable document and


not applicable document.

In standard, such feature is not available. A Custom form needs to


be developed to capture the following check list in the system.

Check List:

 Contract Agreement including BOQ, Specifications, etc.


 Contract Close-out Minutes of Meeting
 Client Receiving Acknowledgement on Project Documents
Handing Over
 Contract Close-out Checklist
 Substantial Completion Certificate
 COC, TOC and Others
 Snag List
 Technical Submittals
 a. As Built Drawings Submittals
 b. Material Submittals and Schedules
 c. Method Statement
 Operation & Maintenance Manuals
 Spare Parts Hand over List
 Tools Hand over List
 Keys Hand over List
 Inspection, Testing, & Commissioning Reports
 Training Reports
 Warranties
 Bonds and Guarantees
 Final Account Statement ( FAS )

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 49


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Details of Claims/Variations/EOT
 Details of Deductions / Penalties / Back-Charges
 Certificates:
 a. MMUP
 b. CIVIL
 c. Others

A check box with “YES/NO” should be provided in the custom


form to identify the status of the documents.
PA.BP.27.0 At present UCC is maintaining Item structure  The maximum length for an Item code in the system is 40 characters. Inventory Key
Inventory Item
based on CSI code as shown below. The description field for an Item Code is of 240 characters length. User
Structure
051223.13.1003
Any specifications or other details which are longer than 240
characters can be recorded in the Long Description of the item
(051223.13 – CSI Code, 1003-Sequence number )
which is 3000 characters long.
(Structural Steel European Flat Bar, Size: 18mm x
18.37kg/m x 6M) The description of the item will default while performing
Purchasing Transactions which will be freeze during the time of
The length of the item structure is 14 characters transaction.
including decimals. Item Maintenance in Oracle EBS:-
Objectives are
UCC would like maintain the same in the future.
 Eliminate Duplication
UCC, PMV and WSD/FSD should maintain one  Proper Identification
Item master only and the master will be  Easy search
maintained by Procurement Department (UCC).
Before creating the item code, the following parameters need to be
Whenever a new Item is required to be created at
identified.
PMV/WSD/UCC/FSD, the item details (In
Agreed Format) will be shared with  Item code
PMV/WSD/UCC/FSD Nominated user.  Description
Respective user will check the information and  UOM
forward the same to UCC Procurement  Item Category
Department (User should be nominated).
 Inventory Organization (Stock and Non-Stock)
Nominated user will check Cost Code Details
with Cost Control Department and Create an item  Locator Information (If Required)
in the system.  Min-Max Values

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 50


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

New item can be created by copying from Item Template or existing


item. Once item is created and saved, UOM (Unit of measure)
cannot be changed.
Item Category needs to be assigned to every Item manually. By
default, system will assign a default category for all Items. User
needs to update the defaulted Category to respective category based
on Item code manually.

Item description can be changed as and when required. When New


Item is created, the status of the Item Code will be Active.

When the defined item is incorrect or gets obsolete, it has to be


made Inactive

No transaction can be performed on the items to which Inactive


status is assigned. Inactive Items will not be displayed in the list of
Items.

Items will be created in Item Master and assigned to respective


Inventory organizations. Item attributes in the Inventory
organizations may vary with Organizations.

A fourteen digit Item code is maintained for all Items.

The Item codification is as follows:


XXYYYY.YY.ZZZZ
Where
XXYYYY.YY – It is a combination of Item Main Group and Sub
group. The first two digits ‘XX’ is Item Main group and sub group
will be linked with item main group.
ZZZZ – Item sequence number

Example - 019516.03.1001 (Tarpaulin, PVC, Size: 35' x 35')

The length of the item structure is 14 characters including decimals.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 51


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Segment Name Length Type Validatio


(Max) n
1 Item Code 40 Character None
The following Item Creation procedure will be followed by UCC

Whenever a new Item is required to be created at


PMV/WSD/UCC/FSD, the item details (In Agreed Format) will be
shared with PMV/WSD/UCC/FSD Nominated user. Respective
user will check the information and forward the same to UCC
Procurement Department (User should be nominated).

Nominated user will check Cost Code Details with Cost Control
Department and Create an item in the system.
The Main Groups for the Items are as follows:-
01 - General Requirements
03 - Concrete
04 - Masonry
05 - Metals
06 - Wood, Plastics And Composites
07 - Thermal And Moisture Protection
08 - Openings
09 - Finishes
10 - Specialties
11 - Equipment’s
12 - Furnishings
14 - Scaffolding
22 - Plumbing
26 - Electrical
27 - Communications
28 - Electronic Safety and Security
41 - Plant, Machinery and Equipment’s
80 - Stationery

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 52


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

81 - Clothes And Safety Gear


82 - Tools & Hardware
83 - Food Items And Miscellaneous Medicines
84 - Formwork & Scaffolding
85 - Cleaning And Hygienic Items
86 - Miscellaneous

Note: Cost Code Assignment to Item will be performed by Item


Creator. Item Creator should be nominated by UCC.

All the rate agreement details of UCC with WSD and PMV should
be available to UCC.
PA.BP.28.0 GAP CH Custom Requests: Project Key User
Budgetary
Control – Custom
Budgetary Control should be enabled for following custom requests
Requests
 SMR (Site Material Request)
 EVRF (Equipment Vehicle Request Form)
 FRF (Fuel Request Form)
 MPRF (Manpower Request Form)
 Staff Request Form
 SRF (Service Request Form)
 Comparison if Bid Summary (CBS)

Note: A custom form needs to be developed to decide the Control


Type (Advisory/Absolute) for all the above mentioned Custom
Forms.

Please refer PA.BP.21 for more details on Budgetary Control.

Please refer Inventory and Purchasing BP documents of UCC for


more details.

Please refer MD for detailed design of EVRF etc.,

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 53


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

PA.BP.29.0 UCC would like to have the absolute budgetary  Such feature is not available in standard process. Project Cost
Budgetary
control in following process Control User
Process
Customization will be analyzed in detailed during build phase.

When end user is raising any Standard Workaround:


Requisition or Custom Requests, IF the system
budget check is failed, system should popup a Advisory Control should be maintained in the system and First
window which will ask user to enter the Level approver for all the Requests should be cost control
reason/justification for getting the over budget department. A reason/justification column will be provided in all
items/equipment’s/manpower. requests and the same can be seen in Approval Notification.

User should be able to enter the Cost Control should make sure that the request is rejected if the
Reason/justification in the popup and send it for justification is not reasonable or not mentioned.
approval to nominated user, if the nominated user
is satisfied with the reason, he should be able to If the cost control engineer approvers, the request will go ahead
click on submit and the request should be with the remaining approvers.
submitted for approval.

Note: Budget amendment is not required to be


made for such kind of approvals.

If approver rejects, system should not allow to


submit the document for approval.

Note: If the requested value is below budgeted


value, approval hierarchy should bypass Cost
Control department.

PA.BP.30.0 Currently UCC is maintaining following types of  Requisition will be raised by Units/Projects for Purchase of Project Procurement Key
Project Purchase
purchase orders items. User
Requisition and
1.Purchase Order (Material, Assets, Consumables)
Purchase Order
– Project/Department The following details will be entered in the Purchase Requisition:
2. Service Order
3. International Order
 Items
4. Subcontract Order
 Quantity
Project Purchase Order amount is getting charged  Need by Date
to project based on selected project. Currently  Price
 Project Number

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 54


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Activity details are not selected at PO Level.  Task


 Project Organization
Currently in UCC, Encumbrance or Budgetary  Date
control is not performed through system. Cost  Expenditure Item
Control department is maintaining the Budget
Control manually. Once the requisition is submitted for approval, budget check will
take place and on passing will be sent through the approval
hierarchy for approvals. Based on Requisition Amount, document
Based on the request from the project sites, the
will pass through the approval process and will get approved.
procurement department purchases the material
(Expense PO). The material is purchased in such a
way that, the purchase cost is directly booked to Once approved the requisition is forwarded to the Purchasing Dept.
projects. The material is also directly delivered in
the projects site instead of receiving in to Store. Using Auto create option, Purchase request will be copied and a
purchase order will be raised against that. All the details entered in
Purchase request will be copied to purchase order also.

After entering/checking all the details, the buyer submits the PO for
approval. The Purchase order will be approved based on the
approval hierarchy.

Once the PO is approved, material will be directly received at


project site and based on the received details a receipt will be made
the project user.

Account will be constructed in PO as follows

Account From
Company Company from Project Organization
Division Division from Project Type
Department Constant
Account Account from Expenditure Type
Sub-Account Subaccount from Expenditure Type
Project Project from Project Number
Employee Constant
Inter Co Constant
Future Constant

Please refer PA.BP.21 for more details on Budgetary Control.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 55


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Please refer PA.BP.58 for more details on Subcontract Process.


PA.BP.31.0 Petty Cash  Project costing is fully integrated with Purchasing and Payables and Finance Key User
Actuals: Account
(PA.BPS.17.0) allows entering project-related requisitions, purchase orders, and
Payables/Site
Petty Cash will be provided to nominated users in supplier invoices.
General Expenses
the site. While giving petty cash, a prepayment
(Petty Cash,
invoice will be created by finance. UCC will enter the supplier advances as pre-payments, expenses
Telephone
Charges, Site related to Mobilization and other general expenses in Payables
Expenses Etc.,). Based on requirement (Emergency), Site users module.
Transactions – procure the material directly with the petty Cash.
Purchasing & UCC would enter project information at the distribution line level
Payables (Project At month End, a PR will be created by the user. for project-related requisitions and purchase orders in Oracle
General Procurement Department creates PO against the Purchasing, and for project-related supplier invoices in Oracle
Expenses) PR and user makes a GRN. Payables.

GRN, PR and Bills will be submitted for Finance When user enters requisitions, purchase orders, and supplier
for clearing the Prepayment balances. invoices in Purchasing or Payables, specify the following project-
related information:
Other Expenses
 Project Number
The transaction like Telephone Charges, Site
Expenses, etc., will be directly booked in payables  Task Number
module by selecting project information (Project  Expenditure Type
Number, Cost Code, and Activity).  Expenditure organization
 Expenditure Date
Requirements:
UCC Want the invoice with details. Lump sum  Project Quantity (quantity of goods or services for which
value without details should be restricted. you are charged. You can enter data in this field only in
Payables, as this field is applicable for invoice lines and
Reconciliation should be done every distributions only.
month/quarterly between project cost ledger and
finance ledger. Recording Receipts and Delivery:
For Expense Purchase Orders, When a purchase order shipment is
PO, SVO (Service Order) & SCO (Subcontract flagged to accrue at receipt and when user enter a receiving
Order) payment has to be posted in project ledger transaction for the purchase order in Oracle Purchasing, system
from the corresponding accounts. generates accounting entry upon receipt is created in Purchasing
Module. These Receipt accruals will be interfaced to Projects as an
Actual. This feature enables to recognize the cost to project in the
period in which it is incurred rather than in the period in which it is
invoiced.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 56


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

The following table specifies the project information that you enter
for each document in Purchasing & Payables

Document Location Fields


Requisition Distribution Line  Project
Level  Task
 Expenditure Type
 Expenditure Org
 Expenditure Date
Purchase Distribution Line  Project
Order Level  Task
 Expenditure Type
 Expenditure Org
 Expenditure Date
Invoice Invoice Line Level  Project
Invoice  Task
Distribution level  Expenditure Type
 Expenditure Org
 Expenditure Date
 Project Qty

Accounting Transactions Created by the Account Generator:


Purchasing and Payables use the Account Generator to determine
the default GL account for each project-related distribution line
based on the project information entered. Account generator needs
to be customized to default the accounting combinations based on
the Project information selected at distribution lines.

Account will be constructed in PO and AP Invoice as follows

Account From
Company Company from Project Organization
Division Division from Project Type
Department Constant
Account Account from Expenditure Type
Sub-Account Subaccount from Expenditure Type
Project Project from Project Number
Employee Constant

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 57


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Inter Co Constant
Future Constant

Interfacing Supplier Costs:


Interface Supplier Costs Program needs to be scheduled to transfer
project-related supplier costs from Purchasing and Payables to
Project costing. This process interfaces receipt accruals from
Purchasing and supplier invoice-related costs and discounts from
Payables to Project costing as actual costs. You must validate
invoices and create accounting for them before interface the costs to
Projects.

Commitment Reporting:
The total cost of a project includes both committed costs and actual
costs. Committed costs are the un-invoiced, outstanding requisitions
and purchase orders charged to a project.

Total Cost-ITD(Inception to Date) = (Committed Costs + ITD-


Actual Costs)

The committed costs can include

 Open Requisitions (Approved & Un-Approved)


 Open Purchase Orders (Approved & Un-Approved)
 Pre-Payment Invoices that are not yet matched to invoices
Unmatched pending invoices (Supplier invoices not yet interfaced
to projects)
Please refer PA.BP.21 for more details on Budgetary Control.
PA.BP.32.0 GAP CH Purchasing & Payables account generator needs to be customized to SETUP
Purchasing &
Payables Account generate accounting combination from Projects information entered
Generator at distribution level.

In the absence of same, user needs to select the PO charge account


and Payables distribution account manually. It may lead to data
entry errors as user has to select same project number (Project
segment) and expenditure type account which was entered at line
level.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 58


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Accounting Combination should be generated based on following


details

Account From
Company Company from Project Organization
Division Division from Project Type
Department Constant
Account Account from Expenditure Type
Sub-Account Subaccount from Expenditure Type
Project Project from Project Number
Employee Constant
Inter Co Constant
Future Constant
PA.BP.33.0 Journal voucher view access is required to know if  Projects Cost Control Department would like to have Journal Project Key User
Journal Voucher
any manual Journals for projects are posted. Vouchers View Access to See the Manual Journals which are entered
View Access
against Projects.

Manual Journal Entries against projects should not be allowed to be


created in GL.

The same can be restricted through GL CVR Rules.

User can see detailed Project Transactions performed in Subledger


modules in Projects Module “Expenditure Inquiry Window”.

Project wise journal details can be see through the Journal Entry
Detailed report. The report access can be provided to Cost Control
Department.

Note: CVR (Cross Validation Rules) will be configured by Finance.


Finance will provide the final Cross Validation Rules while

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 59


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

providing data.

PA.BP.34.0 Depreciation cost of fixed asset need to be posted GAP CH Whenever an asset is required at Project site, a request form called Finance User
Depreciation Cost
on monthly basis to the ledger. Material Request Form will be raised by Project stores subject to
approval.

Normally assets like Porta cabins, power tools, IT assets etc., are
being requested. Central Stores will transfer the asset using Material
Transfer Form.

For Example:
Porta cabin transferred from Central Warehouse to Project A on 01st
Nov 2016 and returned on 10th Nov 2016, then the depreciation for
10 days to be charged to Project A.

The depreciation will be charged to projects based on Internal Hire


Rate.

Internal Hire Rate:

The Internal Hire Rate for an asset will be calculated by taking the
asset depreciation in the earlier month as a basis loaded with some
margin.

There will be two custom forms, one for the Internal Hire Rate for
the asset items and the other is Charge form.

At the end of every month, based on Utilization user have to update


the Custom Charge Form to charge to project based on Internal Hire
Rate of the asset transferred and number of days utilized. No asset
will be transferred through assignments in FA module.

When the task and expenditure type are given in the Charge Form,
the Project Cost will be debited to the respective projects for the
period which the asset is used and Depreciation Control Account
will be credited.

Actual depreciation will be debited to Central Stores as usual when


we run the depreciation for the month. The actual depreciation and
the depreciation charged to projects will be compared and

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 60


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

reconciled.

Please refer FA BP080 for more details.

PA.BP.35.0 Site Material Requisition (SMR-With in the same GAP CH A separate custom form will be developed for material request and Project User
Site Material
(PA.BPS.18.0) Requisition sites) a request will be created from site location to site store keeper for
(SMR-With in the the materials.
same sites) Whenever material is required in the project Site,
SMR (Site Material Request) should be created
At the time of request for the material to projects, site person needs
and sent to Project Manager/Supervisor for
Approval. Approved SMR should be sent to to specify the following values along with Item details:
storekeeper for material Issuance. If stock  Project Number
available in the project store, material will be  Task Number
issued to the project site against the SMR.
 Issue Quantity
At Present this process is performed manually
(Out of the System). UCC Would like to Make the  Sub inventory (Optional)
SMR through EBS.
Each and every Item code is attached with Expenditure type at Item
“Expenditure Type Item Mapping Custom Form”. Expenditure type
is attached with natural account in custom setup form which will be
debited when material is issued.

After giving all the above details the store keeper needs to click on
save and submit for approval.
Once the project manager approvers the material Request, the same
will be submitted to store keeper for Material Issuance.

Value wise Budgetary Control should be checked when user click


on Submit Button. Advisory control should be enabled for this
custom form. If the Request exceeds the budget, system should
show an error message and proceed for approval hierarchy. Cost
Control department will validate the reason for exceeding the
budget and takes a decision on approval.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 61


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Document Sequence for Material Request form


Below document sequence will be followed for all types of material
request in UCC.
Material request document numbering sequence will be – MR-
PROJECT CODE- 00001
MR– Type( MR)
PROJ CODE– UCC Project code like (A01, A02 etc.)
00001 – Running Sequence number
Note - A notification will be send to site store keeper for material
request.
Note:
1. Cost Control Department should be included in approval
hierarchy as the first approver and he should be able to
change the Cost Code.
2. Reallocation of Cost Code possibility should be there
(Feasibility)
3. User should not be able to update the cost code.
Please refer PA.BP.21 for more details on Budgetary Control.

PA.BP.36.0 Site Material Issue GAP CH Material Issue Inventory Key


Material Issue to
User
Project Site from A separate custom form is developed for Material Issue. With
Store reference of request the store keeper will select the MIR (Material
issue request) number and click on populate lines. Once the store
keeper click on populate lines all the material request details like
quantity, task number, issue quantity, sub inventory, locator, lot or
serial if any will be defaulted.
Now the store keeper needs to enter the following details:
 MIR reference number
 Sub inventory
 Locator
 Issue quantity

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 62


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Lot & Serial (If any)

Document Sequence for Material Issue form


Below document sequence will be followed for all types of material
issues.
Material request document numbering sequence will be – MI-
PROJECT CODE- 00001
MI– Type( MI)
PROJ CODE– UCC Project code like (A01, A02 etc.)
00001 – Running Sequence number
The following accounting entries will be generated for material
issues.
INVNETORY
PROJECT COST MATERIAL
ACCOUNT
COMPANY Y Y
DIVISION N N
DEPARTMENT N N
ACCOUNT Y Y
SUB-ACCOUNT Y Y
PROJECT Y N
N N
EMPLOYEE
INTER N N
COMPANY
FUTURE N N
DEBIT XXX
XXX
CREDIT

PA.BP.37.0 GAP CH Project Issues/Returns custom form is used to Process the Inventory Key
Material Return
transaction. When Material is returned from project site, system User
from Project Site

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 63


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

to Store performs the transaction based on the current item cost at Inventory
Organization.

Whenever material is needs to be returned from project site, store


keeper receives the material from 'PROJECT MATERIAL
ISSUES/RETURNS' custom form by selecting ‘PROJECT RETURNS’
type.

At the time of receiving the material from Projects, store keeper


needs to specify the following values along with Item details
 Project Number
 Task Number
 Issue Quantity
 Sub inventory
 Locator/Lot (If Any)

When entry is completed, custom script transfers the completed


transactions to Inventory. When transaction is costed, accounting
entry will be generated in Inventory module and sub-sequently will
be transferred to General Ledger.

To transfer the Project related Inventory transactions, “Cost


Collection Manager” Program will be scheduled on daily/specified
interval in inventory module. This Program transfers the Project
related inventory transactions to Oracle projects Interface tables.

Note: Material will be returned with Material Average cost available


in the system.

Accounting Entry

INVNETORY
MATERIAL PROJECT COST
ACCOUNT
COMPANY Y Y

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 64


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

DIVISION N N
DEPARTMENT N N
ACCOUNT Y Y
SUB-ACCOUNT Y Y
PROJECT Y N
N N
EMPLOYEE
INTER N N
COMPANY
FUTURE N N
DEBIT XXX
XXX
CREDIT

PA.BP.38.0 Currently UCC is not have own Equipment and is GAP CH Equipment Vehicle Requisition form is not available in standard Project User
Equipment
Vehicle hired from PMV Department. ERP Module.
requisition Form
Currently UCC Site User is capturing the A custom form needs Tobe developed for the same.
Equipment utilization details and sending it to
PMV.PMV is generating billing to UCC, based on Whenever any Equipment or Vehicle is required for UCC, EVRF
received Utilization Timesheet details. will be created by Projects users. The following information will be
entered in the EVRF Custom Form
PMV is sending the Equipment Utilization
Timesheet details along with manual Bill copy to  Item Number (Equipment)
UCC. Currently this task is performed manually  Quantity Required
 Unit of Measure (Will be defaulted from Selected Item)
 Cost Code (Defaulted based on selected Item)

Based on agreed rates between UCC and PMV, Value will be


calculated and while submitting the equipment request system will
check for Availability of Budget.

In failure of Budget, system will warn the user.

Whenever a request is raised, the budget amount will be moved to

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 65


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Encumbrance amount in accounting. The details of Budget and


available budget can be seen from Financial module and reports.

UCC Needs to provide a report format if they would like to see


these details in a particular reporting structure.

Note: PMV would like to restrict the Quantity (Absolute Control)


based on forecast quantity submitted by UCC. Cross Functional
discussion is required to finalize the same.

Based on Requested Quantity, PMV deploys the


vehicles/Equipment to UCC using Deployment Custom form.

Please refer ADS BP080 for more details.

Note: Only Equipment Related category items should come in Item


LOV of EVRF. Based on PMV list of Asset Categories, Items will be
created in Inventory Module. List of items will be provided by Cost
Control Department.

Inventory Item to Cost Code Mapping will be maintained in Item


Expenditure Mapping. Cost Code to Assets Mapping will be
maintained in Asset Master.

Note: Please refer Final ADS BP080.

PA.BP.39.0 Purchase Requisitions for Projects  Purchase Requisitions(PR): Project User


Purchase
Requisitions
(Projects) Whenever Material is required at Site, Project Site user creates a
SMR, The store keeper will check for availability of material at store
and Central store. If material is not available at site, Store Keeper
Converts the SMR to PR.

Any request created as direct consumption to the project is


considered as an Expense Project requisition. The destination type
field must be maintained as “Expense” for these requisition lines.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 66


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

If the material is required to be stored at project store and then issue


to project at later point of time, Destination type of Requisition
should be inventory.

Different types of requisition for which the Project site store keeper
is going to create is
 Consumables
 Services
 ADMIN & IT
 Subcontract Works

For all consumables the destination type of the requisition lines will
be Inventory.

All the other types of requisitions will be directly charge to the


Project. So, the destination type will be expense and it is required to
provide the details of Project in the requisition.

Project details to be entered in the Requisition lines are


 Project
 Task
 Expenditure type
 Expenditure Organization
 Expenditure Item Date

Purchase Requisition creation process involves below steps.


1. Store Selection
2. Items selection
3. Adding Items to the Shopping cart
4. Checkout
5. Submit for Approval

When the purchase requisition is submitted for approval, budget


check will take place with reference to the project code and cost

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 67


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

code. If the Purchase requisition amount is within the budgetary


control then system submit the same for approval. If the PR amount
is more than the budget allocated then a warning message will be
shown as ‘budgetary control exceeded’.

Note:
 Average Purchase Order price for last 5 Purchase Orders
will be defaulted in Price field of requisition lines.
 UOM and unit price of the Item can’t be updated in
purchase requisition lines.

Please refer flow chart for more details and Please refer PA.BP.21 for
more details on Budgetary Control.

PA.BP.40.0 Purchase Requisition for Services  Purchase Requisitions for Services Project User
Purchase
Requisitions for
Services Purchase requisition for services will be created by warehouse
storekeeper or project site storekeeper when there is a requirement
for services from project site or central warehouse

For all the services a separate Item code with description as service
will be linked to services category and respective account code.
When the user prepares the requisition the account code linked to
the Item will be defaulted onto requisition.

Purchase Requisition creation process involves below steps.


1) Store Selection
2) Items selection
3) Adding Items to the Shopping cart
4) Checkout
5) Submit for Approval

When the purchase requisition is submitted for approval, budget


check will take place with reference to the project code and cost
code. If the Purchase requisition amount is within the budgetary

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 68


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

control then system submit the same for approval. If the PR amount
is more than the budget allocated then a warning message will be
shown as ‘budgetary control exceeded’

Note:
 The UOM for service Item will default as HRS. In case of
special services the UOM for the Item will default as LUM.
 Average Purchase Order price for last 5 Purchase Orders
will be defaulted in Price field of requisition lines.
 UOM and unit price of the Item can’t be updated in
purchase requisition lines.

Examples for Services are

 Refilling of Fire Extinguishers


 Maintenance of Printing Machine etc.
Please refer PA.BP.21 for more details on Budgetary Control.

PA.BP.41.0 Purchase Requisition for Sub contract works  Purchase requisitions: Project User
Purchase
Requisitions for
Subcontract A custom form needs to be developed for sub contract request
works where it is required to capture the details like cost code, BOQ
(Package) and checklist as an attachment provided with the request.
Quotation creation date can be used as acceptance date for the
subcontract request as this will be prepared by Procurement
department.

Every project has few tasks which need to be allotted to


outside/internal contractor for the work to be done.
For the entire Subcontract works a separate single Item code with
description as subcontract work will be linked to subcontract
category and respective account code.

Select the Destination Organization and location details in the


requisition.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 69


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Under Requisition distributions, Projects tab provide the necessary


details as given below
 Project Number
 Task
 Expenditure type
 Expenditure Organization
 Date

When the purchase requisition is submitted for approval, budget


check will take place with reference to the project code and cost
code. If the Purchase requisition amount is within the budgetary
control then system submit the same for approval. If the PR amount
is more than the budget allocated then a warning message will be
shown as ‘budgetary control exceeded’

Please refer PA.BP.21 for more details on Budgetary Control.

Please refer UCC Procurement BP080 for more details.

PA.BP.42.0 GAP CH Whenever fuel is required at project site, fuel request will be created Project User
Fuel Request
by projects user. A custom form needs to be developed to achieve
the requirement.

In the custom form, Project user needs to select following


information and submit the requisition for approval

 Item
 Quantity
 UOM
 Project
 Cost Code

While submitting the form for approval, system should check the
budget available for fuel. If budget is not available, system will
restrict the user to proceed ahead on request based on Control Type
defined for the project.

Once the fuel request is approved, PMV creates an Purchase order

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 70


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

against the request in PMV Unit with Waqod as Supplier. The fuel
will be directly received at Project site.

An Receipt will be made in PMV unit against the fuel order and the
fuel will be transferred to Projects site through Intercompany fuel
transfer (Customization). Fuel receipt will be made by the project
store against the issue made by PMV Unit.

For Detailed process of Fuel Issues to Project, Please refer PMV ADS
BP080. Please refer PA.BP.21 for more details on Budgetary Control.
PA.BP.43.0 Business Rule: GAP CH Process: UCC Project User
Manpower
 Manpower is maintained by WSD and
Request Form
PMV and supplies to UCC projects for For Manpower Supply Projects, Manpower Request form needs to
(MPRF)
manpower supply works. be developed where UCC project team requests the manpower to
PMV or WSD.
Manpower Supply Projects:
 Project in charge/Project Manager of Once the request is approved in UCC, WSD or PMV nominated
UCC requests manpower for Manpower person (HR person from LRD) will have to approve the request in
Supply Projects (to WSD/PMV) through order to acknowledge the same.
Manpower Request.
 In Manpower request, number of Based on the action taken by WSD/PMV, an FYI notification needs
required employees by Category (Job) is be sent to UCC.
requested.
 The request form is approved by Project Important fields to enter in the form.
Manager, Project Director and Cost
Controller of UCC.  Project Number*
 Once the request is approved from UCC,  Project Location*
WSD person acknowledges the request  To Operating Unit*
and for PMV, an HR person from LRD  Category (Job)*
will acknowledge and coordinate with  Quantity Available*
PMV internally for transfers.  Quantity Required*
 From Date*
Unit Rate Projects:  To Date*

 Section Managers of WSD requests Note: Budget Control by value should be controlled at Requisition
manpower through e-mails/phones. level.

Note: UCC creates the budget of manpower against single cost code.
Staff Requisitions of UCC are also performed Budget check of manpower should be checked with that cost code.
where request for staff comes from a

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 71


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

department/project.
Once the Requisition is raised, the value of the Budget will be taken
Require Quantity Budget control in Requisitions. as committed. Users can raise Request for remaining amount only.

Please refer PA.BP.21 for more details on Budgetary Control.

Please refer Time and Attendance BP080 for more details.


PA.BP.44.0 Staff Requisition Form (SRF) GAP CH In Standard application, staff requisition process is not available. Project User
Staff Requisition:
Staff Requisition Whenever the staff is required by UCC at project A custom form needs to be developed to request staff. A custom
Form (SRF) site, project team is raising a request through SRF form with following fields should be developed.
(Staff Requisition Form) and sending it for
approval. Once the request is approved, UCC is  Project/Department
checking for the Manpower Availability and  Staff Job
performing following activities  Quantity Available
 Quantity Required
 If the staff is available, it is issued to the  Cost Code
project site.
 If the staff is not available, it is Once all the information is entered, the user should be able to
transferring from another project site. submit the request for approval.

Approval hierarchy need to be shared by the Cost Approval Hierarchy details should be provided by UCC.
Control Department.
While submitting for approval, the System should check for value
Budget check. Based on the Control Type (Advisory/Absoulte),
system should restrict the user based on budget.

Once the Requisition is raised, the value of the Budget will be taken
as committed. Users can raise Request for remaining amount only.

UCC creates the budget of staff against single cost code. Budget
check of manpower staff should be checked with that cost code.

Please refer PA.BP.21 for more details on Budgetary Control.

Please refer T&A BP for more details.


PA.BP.45.0 Currently UCC is not have own manpower and GAP CH Based on Manpower Request, Manpower will be deployed to UCC WSD User and
Actuals:
(PA.BPS.21.0) manpower is hired from WSD Department. projects and deployment details of Manpower will be entered Project User
Manpower

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 72


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Utilization Cost UCC has 2 types of agreement with WSD. against WSD Project.
1. Unit Rate Basis
2. Contract Basis
A custom form needs to be developed to enter Manpower
Utilization Time sheets of WSD. Manpower Utilization time sheets
Unit Rate Basis: Whenever manpower is required
will be entered against the WSD projects and at month end based on
for UCC, UCC is sending a request to WSD with
the rate of the Manpower, Manpower Invoice (UCC Project
Manpower Forecast Details. WSD Supplies
Manpower Cost) details will sent to Projects Team for approval with
manpower on hourly rate basis. Time keeper is
following information.
maintaining the time sheets of the Manpower and
submit the details to WSD. WSD is generating
billing to UCC, based on Timesheet details  Project Number
received from timekeepers.  Expenditure organization
WSD is sending the timesheet details along with  Expenditure type (Cost Code)
manual Bill copy to UCC. UCC is allocating the  Expenditure date (transaction date)
total cost of Manpower to different Cost Codes in  Amount (Time * Rate (Picked from Time & Attendance).
Cost Details report. Currently this task is
performed manually by Cost Control Department.  Transaction Source (Time & Attendance System)

Contract Basis: UCC is Subcontracting Formworks A custom form should be developed to interface the manpower cost
etc. related activities to WSD. In such cases, UCC to UCC. The form will contain following details
is considering that as subcontract order and
treating WSD as subcontractor. Commercial and
Contracts department is tracking the work done Header:
details of Subcontracted Activity and Processes
the Payment to WSD. UCC is not concerned on Project Number
Manpower Utilization/Count of manpower for
Project Name
such contracts.
Month
Operating Unit

Detail Level:

 Cost Code (Default Cost Code should be defaulted from


Request)
 Bill Amount (Bill Amount from WSD should be populated
here)
 Date (30 Records, Day wise record)

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 73


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Task (Should be defaulted based on Cost Code)

Day wise records should be populated in this custom form (Total 30


or 31 records).

User can view the details and update the cost code and task
information (If Required) and click on Transfer Button.

The Cost should be interfaced to Project module based on Cost Code


and Activity Code of custom form.

Note: Reports is expected by UCC to view all detailed cost code


wise rates and Calculations. WSD need to provide the report format.

Please Refer WSD BP080 for report details.

Please refer PA.BP.47.1 for details on Actual Cost details in Projects


module
Please refer T&A BP document for more details of Timesheets.
PA.BP.46.0 GAP CH A Custom form needs to be developed to enter the Staff Time sheets. Project User
Staff Timesheet
Cost
Based on request for Staff, Staff will be deployed to UCC and
deployment details of Staff will be entered against UCC Project.

On daily basis, UCC site need to enter the Staff time sheets with
following information

 Employee
 Hours
 Activity
 Cost Code (Mapped with Employee)
 Project No
 Project Organization (Populated based on Project)
 Time sheet Date

The time sheet should be submitted for approval to UCC.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 74


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Timesheet Approval Hierarchy should be provided by UCC.

Once the time sheet is approved, the cost of the Staff will be
transferred to Project Module and Accounting entries will be
generated in GL.

STAFF COST
STAFF COST
ABSORPTION
COMPANY Y Y
DIVISION N N
DEPARTMENT N N
ACCOUNT Y Y
SUB-ACCOUNT Y Y
PROJECT Y N
EMPLOYEE N N
INTER N N
COMPANY
FUTURE N N
DEBIT XXX
CREDIT XXX

Please refer PA.BP.47.1 for details on Actual Cost details in Projects


module
PA.BP.47.0 Currently UCC is not have own Equipment and is GAP CH A custom form needs to be developed to capture the equipment Project User
Actuals:
(PA.BPS.22.0) hired from PMV Department. utilization details. PMV will be maintaining all the equipment
Equipment
utilization cost details and transfer the equipment utilization bill to
Utilization Cost
Currently different types of contract requests are UCC on monthly basis.
maintained between UCC and PMV. These
Contracts can be categorized into 2 Major types PMV will enter the Utilization Cost of Equipment against UCC
(Higher Level). Projects.
1. Hourly Rate Basis
2. Contract Basis Equipment Utilization entry form consists of following details

Unit Rate Basis: Whenever Equipment is required  Project Number (from Project access setup)
for UCC, UCC is sending a request (EVRF) to
 Expenditure organization (Defaulted from Project)
PMV with Equipment Forecast Details. PMV
Supplies equipment to UCC on hourly rate basis.  Expenditure type (Cost Code defaulted based on selected

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 75


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

equipment)
Currently UCC Site User is capturing the  Expenditure date (transaction date)
Equipment utilization details and sending it to
 Cost Code (Defaulted)
PMV. PMV is generating billing to UCC, based on
received Utilization Timesheet details.  Amount (Time * Rate (Picked from Agreement).
 Activity (Higher Level Activity)
PMV is sending the Equipment Utilization
Timesheet details along with manual Bill copy to
UCC. UCC is allocating the total cost of Once the time sheet is entered, the same will be submitted for
Equipment to different Cost Codes in Cost Details approval.
report. Currently this task is performed manually
by Cost Control Department. PMV needs to provide the approval hierarchy details.

Contract Basis: UCC is Subcontracting Excavation


Works, Earth Works etc. related activities to PMV. Once the Utilization time sheet is approved, 2 interfaces should be
In such cases, UCC is considering that as customized to transfer Cost to UCC
subcontract order and treating PMV as  Actuals with Task and Cost Code to Projects
subcontractor. Commercial and Contracts
 Accounting entry to GL
department is tracking the work done details of
Subcontracted Activity and Processes the
Payment to PMV. UCC is not concerned on
Equipment Utilization or Number of Equipment’s Please refer MD.050 for more details and field level validations.
utilized to complete the task/activity.
Please refer PA.BP.47.1 for details on Actual Cost details in Projects
module
PA.BP.47.1 Actual Cost Inquiry Window  All the Actual Cost Transactions performed in different modules Project Key User
Item Expenditure
will be interfaced to Project module using Project transactions
Inquiry
Import based on different sources.

Example of Sources:

 Inventory Misc
 Time and Attendance
 Equipment Utilization
 Usage
 Supplier Invoices Etc.,

All the details interfaced to projects will be available in Item


Expenditure Inquiry Screen.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 76


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

User can rearrange the columns available in Item Expenditure


Inquiry screen and export it to excel for further analysis.

Details in Expenditure Inquiry can be queried each project wise or at


UCC Level also with different parameters/options.

For Example:

 Project Number
 Project Name
 Activity Number
 Activity Name
 Transaction from Date
 Transaction to Date
 Cost Code
 Cost Category
 Transaction Sources
 GL Date
 Supplier Number
 Supplier Name
 Invoice Number etc.

For many transactions, User can select a transaction line and directly
navigate to Transaction level to see more details.

For Example:

 Supplier Invoice
 PO Receipts
 Purchase Orders

Details which will be available in the Item Expenditure Inquiry


window are as follows

 Transaction ID
 Project Number
 Project Name
 Task Number
 Task Name

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 77


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Cost Code
 Item Transaction Date
 GL Date
 Supplier
 Quantity
 Unit of Measure
 Value
 Invoice Number
 Inventory Item
 PO Number
 PO Receipt Number
 Currency
 Project Type Etc.,

User can see the accounting entries of transactions from Expenditure


Inquiry by navigating to tools  View Accounting.

Following reports requested can be generated from details in Item


Expenditure Inquiry Form.

 Monthly Running Cost for Project


 Actual Cost Sheet
PA.BP.48.0 QS Department tracks Work done Quantities GAP CH Work Done window is going to be there in Projects custom module Commercial &
Work Done
(PA.BPS.25.0) against each BOQ. The work done quantity details (BOQ). Project Key User
Evaluation
are used to generate invoices to Customer.
This window is used to enter the work done (Cumulative). This
UCC Would like to capture Work done details in window consists of the BOQ details, where with reference to the
the system. BOQ Details, work done quantity is entered. The BOQ details are
picked form the BOQ Detail Form.
QS Will enter the Work done details in the system
directly. In some cases it can be performed in Following fields will be available in Work Done Evaluation Form
excel and UCC would like to upload the same in
to System. Work done Entry for the Period
Entry Date:
UCC would like to have following BOQ No:
fields/Columns in Work done Evaluation Description: Complete anti termite treatment all as specified
Unit: SQM
 Unit of Measure Cumulative Work Done Quantity
 Remaining Quantity Cumulative Final Work Done Quantity

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 78


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Work Done Quantity BOQ Quantity


 Actual Work Done Quantity (Monthly, Rate
cumulative) will be used for MJCR Contract Type
 Previous Work done Quantity
Document number and document date options will be provided in
the system to track the changes made in the work done quantity in a
month.

Once all the Work Done Quantities are entered, the same will be
submitted for approval to Sr. QS.

Revision Control should be provided in the custom form.

To calculate BCWP, 3 options are available.

Option: 1: Based on Actual Workdone Quantities entered by QS in


the Workdone evaluation custom form.

Option2: A custom form needs to be provided to Cost Control


department in which each cost code wise % completion can be
imported with reference to the bill code.

Option3: Interface the Percentage completion from Primavera.

Option 4: Interface each Cost Wise from Candy

The Percentage completion calculated at this form should be used in


MJCR process.

PA.BP.49.0 QS Department Tracks Payment Application GAP CH Invoiced Quantity window is going to be there in Projects custom Commercial Key
Invoice
(PA.BPS.26.0) Quantities against each BOQ. module. User
Evaluation/Payme
nt Application
UCC Would like to capture Payment Application This window is used to enter the Invoiced Quantity (Cumulative).
Quantities
Quantities details in the system. This window consists of the BOQ details, where with reference to
the BOQ Details, Invoiced Quantity is entered. The BOQ details are
UCC would like to have following picked form the Costing Form.
fields/Columns in Payment Application Ex:
Quantities form
Cumulative Invoiced Quantity Entry for the Period

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 79


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Unit of Measure Entry Date: 13/Sep/2011


 Remaining Quantity BOQ No:
 PA Quantity Description: Complete anti termite treatment all as specified
 Previous PA Quantity Unit: SQM
Work done Quantity:
Invoiced Quantity
Final Invoiced Quantity
BOQ Quantity:
Rate:
Contract Type: Remeasurable

Document number and document date options will be provided in


the system to track the changes made in the work done quantity in a
month.

Once all the Invoiced Quantities are entered, the same will be
submitted for approval to Sr. QS.

Revision Control should be provided in the custom form.

PA.BP.50.0 QS Department tracks Certified Quantities against GAP CH Certified Quantity window is going to be there in Projects custom Commercial Key
Certified
each BOQ. module. User
(PA.BPS.27.0) Evaluation
UCC Would like to capture Certified Quantities This window is used to enter the certified quantity (Cumulative).
details in the system. This window consists of the BOQ details, where with reference to
the BOQ Details and work done quantity, certified quantity is
UCC would like to have following entered. The BOQ details are picked form the Costing Form.
fields/Columns in Certified Quantities form Ex:
 Unit of Measure
 Remaining Quantity Certified Quantity Entry for the Period
 PC Quantity Entry Date: 13/Sep/2011
 Previous PC Quantity BOQ No
Description: Complete anti termite treatment all as specified
Unit: SQM
Work Done Quantity: 10
Certified Quantity: 9
Final Certified Quantity
BOQ Quantity: 24
Rate: 0.22
Contract Type: Remeasurable

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 80


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Document number and document date options will be provided in


the system to track the changes made in the work done quantity in a
month.

Once all the certified Quantities are entered, the same will be
submitted for approval to Sr. QS.

Revision Control should be provided in the custom form.


PA.BP.51.0 Project Invoicing GAP CH Payment Certificate process which UCC is expecting is not available Commercial Key
Project Invoicing
in Standard Project Billing. User

Customization needs to be performed to achieve the same.

A Custom component for billing (Payment Certificate) should be


provided to UCC

PC (Payment Certificate) is of 5 types


1. Advance
2. Progress Billing
3. Final Progress Billing
4. Retention Release
5. Final Retention Release

Custom Process:

When a project is awarded to UCC. Before starting the project some


of the amount in total contract will be taken as an advance.

For entry of advance Invoice, the document type will be selected as


“Advance”

The following details needs to be entered in the header level

 Operating Unit
 Project Number
 PC Type (Advance)
 Document Type
 Document Date
 PC No

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 81


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Period
 Comments (if any)

Once the advance document type is selected, at line level the


advance amount will be entered in Accounting Value Column
against the Advance Row. Once the transaction has been entered,
user will Click on transfer which will automatically create an
Advance Invoice in AR Module. When the advance amount is
received from the customer, Receipt will be taken against the
Advance Invoice.

When next milestone is due, UCC needs to raise an invoice against


the same. For raising the invoice for Value of work done, UCC will
select the Document Type as Payment Certification in PC Custom
Form and Enter the Value of Work done amount in work done Row
and advance Recovery, Retention and other deductions amount in
respective rows in Accounting Value Column.

When the transaction entry is completed user will select Transfer


button which will pass the total amount (work done-Advance
Recovery) Receivables and Un-Billed Receivables entries in AR and
the advance Recovery accounting transaction will be passed to GL
Directly.

When the total project is completed (Final Invoice). UCC user will
enter the Work done, Advance Recovery, Retention and other
deduction amounts in PC custom form by selecting PC Type as
Final Progress Billing.

When the transaction entry is completed user will select Transfer


button which will pass the total amount (VOWD-Advance
Recovery) Receivables and Revenue entries in AR and the advance
Recovery accounting transaction will be passed to GL Directly.

Note: Value of work done amount will be calculated from Certified


Quantities form.

Accounting Entry:

Advance:

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 82


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Account Receivables Advance

COMPANY Y Y
DIVISION N N
DEPARTMENT N N
ACCOUNT Y Y
SUB-ACCOUNT N N
PROJECT Y Y
INTER N N
COMPANY
FUTURE N N
DEBIT XXX
XXX
CREDIT

Advance Recovery:

Unbilled
Advance
Receivables
COMPANY Y Y
DIVISION N N
DEPARTMENT N N
ACCOUNT Y Y
SUB-ACCOUNT N N
PROJECT Y Y
INTER N N
COMPANY
FUTURE N N
DEBIT XXX
XXX
CREDIT

Invoice:

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 83


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Unbilled
Account Receivables
Receivables
COMPANY Y Y
DIVISION N N
DEPARTMENT N N
ACCOUNT Y Y
SUB-ACCOUNT N N
PROJECT Y Y
INTER N N
COMPANY
FUTURE N N
DEBIT XXX
XXX
CREDIT

Following are the Types of Details maintained in PC

 Advance
 Additional Advance
 Retention
 Final Retention
 Additional Retention

Note: Finance has confirmed that the following accounts are


maintained in GL

 One account for Advance and Additional Advance


 One account for Retention and Additional Retention
Note: Detail discussion is going on with finance on accounts.
PA.BP.52.0 After the contract is awarded to UCC, Advance, GAP CH When a project is awarded to UCC. Before starting the project some Commercial Key
Payment
Recovery and retention terms are getting agreed of the amount in total contract will be taken as an advance. User
Certificate
with the customer. All these information is
(Advance)
captured in PID Document. A Custom component for billing (Payment Certificate) will be
provided to UCC.
Based on contract Terms, Currently Commercial
Department is preparing Advance invoice to For entry of Advance, the Payment Certificate Type will be selected
client/Customer based on agreement details. as “Advance” for advance invoice.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 84


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Currently UCC is capturing Advance Invoice The following details needs to be entered in the header level
details manually. After creating the Advance
Invoice, the same is sent to Approval manually.  Operating Unit
 Project Number
Approval Hierarchy details needs to be provided  PC Type
by UCC Commercial Department.  Document Type
Currently this process is maintained manually  Document Date
and UCC would like to have complete process in  PC No
system.  Period
 Comments (if any)

Once the advance document type is selected, at line level the


advance amount will be entered in Accounting Value Column
against the Advance Row. Once the transaction has been entered,
user will Click on transfer which will automatically create an
Advance Invoice in AR Module. When the advance amount is
received from the customer, Receipt will be taken against the
Advance Invoice.

When advance recovery needs to be done, user will enter the details
of the advance recovery in advance recovery field when next invoice
has been raised against the project. Once the entry is completed, the
user will select the transact button which will directly pass the
Advance Recovery entries in GL.

Note: Value of work done amount will be calculated in work done


evaluation custom form and the same will be entered in PC custom
form.
Accounting Entry:

Advance:

Account Receivables Advance

COMPANY Y Y
DIVISION N N
DEPARTMENT N N
ACCOUNT Y Y

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 85


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

SUB-ACCOUNT N N
PROJECT Y Y
INTER N N
COMPANY
FUTURE N N
DEBIT XXX
XXX
CREDIT

Advance Recovery:

Unbilled
Advance
Receivables
COMPANY Y Y
DIVISION N N
DEPARTMENT N N
ACCOUNT Y Y
SUB-ACCOUNT N N
PROJECT Y Y
INTER N N
COMPANY
FUTURE N N
DEBIT XXX
XXX
CREDIT

PA.BP.53.0 Currently QS is capturing the Work done details GAP CH When a project is awarded to UCC, based on the agreement with Commercial Key
Payment
against a project and sharing the details to customer some amount will be deducted in the Invoice as Retention. User
Certificate
Commercial Department. Based on contract Presently Retention is appealable for all types of projects.
(Invoice)
Terms and Work done details received from QS
Department, Commercial Department is A Custom component for billing (Payment Certificate) will be
preparing invoices to client/Customer and provided to UCC.
submitting it for internal Approval. While
preparing the invoice, following deductions are For entry of invoice the Type will be selected as Payment certificate.
applied by UCC

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 86


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

The following details needs to be entered in the header level


1. Retention
2. Advance Recovery  Operating Unit
 Project Number
UCC Commercial Department need to provide  PC Type
Final list of Deductions maintained by UCC.  Document Type
 Document Date
UCC would like to populate Advance and  PC No
Recovery Percentage in Payment certificate  Period
automatically based on Contract Agreement.  Comments (if any)

UCC Would like to have Document Type "Final At line level while entering the Invoice amount in PC, Against the
Bill Type" in the Payment Certificate. same Retention amount will be entered. The entry will be done in
Cumulative Value Column.
UCC would like to populate Value of work done
(VOWD) Value automatically based on Work Once the entry is completed, the user will select Transfer button.
done Quantities entered at Work done Evaluation Then, the retention accounting entry will be passed in GL directly.
by Quantity Surveyor.
Types of Retention Releases are maintained by UCC. Retention
Approval Hierarchy details needs to be provided Release is done when project is completed and Final Retention
by UCC Commercial Department. release is done by DLP Department when the project or DLP period
is completed.
Currently all this process is maintained manually
and UCC would like to have complete process in When project is completed and retention release invoice needs to be
system. sent to customer, user will select the Document Type as Retention
Release and enter the Retention release amount in Cumulative
Column against Retention release field and click on transfer. Once
the user has selected the transfer button, system will automatically
raise retention Release invoice in receivables module.

Accounting Entry:

Retention:

Unbilled
Retention
Receivables
COMPANY Y Y
DIVISION N N

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 87


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

DEPARTMENT N N
ACCOUNT Y Y
SUB-ACCOUNT N N
PROJECT Y Y
INTER N N
COMPANY
FUTURE N N
DEBIT XXX
XXX
CREDIT

Retention Release:

Receivables Retention

COMPANY Y Y
DIVISION N N
DEPARTMENT N N
ACCOUNT Y Y
SUB-ACCOUNT N N
PROJECT Y Y
INTER N N
COMPANY
FUTURE N N
DEBIT XXX
XXX
CREDIT

PA.BP.54.0 GAP CH Projects Module doesn’t have a provision to capture the Accruals. Project Key User
Accruals
UCC want to enter the accruals and affect the project on monthly
basis to calculate percentage of completion.

Following accruals should be captured in the system

Accruals for material

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 88


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Accruals for subcontractors


Accruals for staff and labour service
Accruals from WSD
Accruals from PMV
Accruals from FSD
Depreciation of Asset

Accruals for Material: Material Accrual referred as the Material


Consumed to perform the activity for the current month but the cost
may be missed out in system due to non-entry of records in the
system. Based on the Monthly check performed by UCC, the
difference in stock of Physical check and System check will be taken
as Accruals.

Accruals for Subcontractors: Actual Work done Quantities and


Value will be taken as accruals for Subcontractor. If Actual Work
done was not entered by Q.S, Cost Control department will
manually enter the accrual value (In Accrual Custom Form) against
the subcontract agreement.

Accruals from WSD: These Accruals are referred as the manpower


engaged from the WSD to perform Direct and Indirect Works and
delay in posting or invoicing to UCC.

Accruals from FSD: These Accruals are referred as the Formwork


and Scaffolding Assets engaged from the FSD to perform the Works
and delay in posting or invoicing to UCC.

Accruals from PMV: These Accruals are referred as the Equipment


Cost engaged from the WSD to perform Works and delay in posting
or invoicing to UCC.

Depreciation of Asset: These Accruals are reffered as the assets


utilized by UCC and delay in posting the Depreciation cost to
projects.

A custom form needs to be developed to capture the accruals in the


system.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 89


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

A project number should be selected at the header level of the form


and click on generate, based on details in Subcontract and other
processes, the accruals details should be populated in the custom
form. Some of the values like petty cash and etc are not maintained
in the system, so a provision to enter accruals manually also should
be allowed in the custom form.

Approval Hierarchy of Accruals Custom Form: Cost Control


Engineer – Sr. Cost Control

When the accruals are approved by the cost control department,


Cost Control User should click on Transfer button to transfer
Accruals to Project module and GL Module.

When the actual cost is affected in the month end, Cost Control User
navigates to Accruals form and select respective line which he want
to reverse. Once all the lines are selected, user can click on Transfer
button which creates negative entries in projects module and
reverse accounting entries in GL Module.

A check box should be provided in header level, show all and hide
cleared Accruals. When the check box is selected, all the accruals
which are settled should be hidden.

These Accrual values are used in MJCR Process. Please refer


PA.BP.70 for more details on MJCR.

Please refer MD050 for details of form and field wise validations.

PA.BP.55.0 GAP CH To Recognize Revenue UCC is going to use percent Complete Projects Key User
Project - Revenue
process.
Recognition
Before Recognition of Revenue, user needs to check whether all the
actual transactions have been done for the project and accruals are
booked for the project.

Once user confirms that all the actual transactions and accruals have
been entered (Up to Date), User will navigate to Revenue
Recognition Custom Form.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 90


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

User should to select Operating Unit and Period at header level and
click on Get lines. System should populate Actual Cost, Revenue
Budget and Cost Budget details each project wise. Based on the
formula provided by UCC, Percentage Completed will be calculated
by the system and should be show in custom form.

User can select the lines for which he want to recognize the revenue
and post. Remaining lines can be posted at later point of time.

User will click on submit to get approval on Percentage completion


and revenue recognition value.

Hierarchy details needs to be provided by UCC. Final approver for


the % Completion will be finance user.

Once the document is approved, user need to click on generate


Revenue.

An interface needs to be developed in system in such a way that an


revenue entry will be created in GL automatically

The following programs will be run to transfer the values to GL and


create Revenue Accountings.

“PRC: Create Accounting”

Percentage Completion Formula:


Revenue = ((Cost Incurred/Cost Budget) *(Revenue Budget))-
Booked Revenue
Accounting Generation will be as follows

Unbilled
Revenue
Receivables
COMPANY Y Y
DIVISION N N
DEPARTMENT N N
ACCOUNT Y Y

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 91


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

SUB-ACCOUNT N N
PROJECT Y Y
INTER N N
COMPANY
FUTURE N N
DEBIT XXX
XXX
CREDIT

PA.BP.56.0 Currently when project is completed and GAP CH When project is completed closed (DLP Completed), user will Commercial Key
Payment
Takeover certificate is received, Partial Amount of navigate to Payment Certificate and select Type as Final Retention User
Certificate (Final
Retention is getting recovered from Client based Recovery
Retention
on Contract Agreement Terms.
Recovery)
 Operating Unit
After creating the Retention Release Invoice, the  Project Number
same is sent to Approval manually.  PC Type
 Document Type
Remaining Retention Amount is released by  Document Date
Client after DLP Period. DLP Department is  PC No
recovering remaining Retention Amounts.  Period
 Comments (if any)
Approval Hierarchy details needs to be provided
by UCC Commercial Department.
Accounting Entry:
Currently all this process is maintained manually
and UCC would like to have complete process in Retention Release:
system.

Receivables Retention

COMPANY Y Y
DIVISION N N
DEPARTMENT N N
ACCOUNT Y Y
SUB-ACCOUNT N N
PROJECT Y Y
INTER N N
COMPANY

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 92


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

FUTURE N N
DEBIT XXX
XXX
CREDIT

PA.BP.57.0 At present UCC subcontract process is handled by GAP CH Subcontract Request Project &
Subcontract
Procurement department and Subcontract Procurement
Process
department. A Subcontract Request will be raised by Site and budgetary control User
will be checked at the time of requisition. Once the Request is
 The procurement department take care of approved the same will be sent to Procurement department for
finalizing subcontractor based on further process.
qualification, comparisons and other
specifications. Request for Quotation & Quotation

 The subcontractors are invited to Based on the Subcontract Request the Procurement department
participate in the bid through RFQ by the creates Requests for Quotation and Quotations. Bid analysis will be
performed by Procurement department and Procurement will
procurement team.
compare/rate and check budget in Bid Analysis report and submits
it for approval to hierarchy.

 Once the subcontractor is finalized based Selected Supplier details will be forwarded to Commercial
on the comparisons and qualification the Department for agreement Creation.
contract is awarded to the subcontractor.
Subcontract Agreement:

 Once the subcontractor is finalized the Subcontract Agreement will be created against the Subcontractor.
Requisition reference number will be entered in Subcontract
Subcontract Department creates a
agreement for reference purpose. Subcontract Management Custom
Subcontract Agreement.
process should be followed for Work Order and Service Order
processes.
UCC wants to continue with the same procedure
in future. Subcontract Liability Statement:

Subcontract Liability statement (Work done) will be captured on


monthly basis. Subcontractor Payment Application quantities will
be tracked in Subcontract Liability Statement.

Actual Work done quantities will be captured in SC liability


statement for Accruals purpose.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 93


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Subcontract Liability Statement will be submitted for approval.

Payment Certificate:

Approved Subcontract Liability Statement will be referred in


Payment Certificate and Work done/certified values will be
populated in Payment Application. Advance Recovery, Retention
and other deductions will be entered/calculated based on
percentages provided in agreement.

Payment Certificate will be submitted for approval, once Payment


certificate is approved, Payables invoice will be created in payables
module (Auto Interface) with Payment certificate Values.

Please refer PA.BP.58, PA.BP.59, PA.BP.60, PA.BP.61, PA.BP.62 and


PA.BP.63 for details of subcontract process.

Please refer PA.BP.54 for Accruals details.

Please refer MD for more details.


PA.BP.58.0 In the contract agreement of Subcontract process GAP CH Once the Subcontractor is finalized, the details will be sent to Commercial User
Subcontract
the key users want to have two way approvals Commercial department for processing Subcontract Agreement.
Agreement
 Within Internal Project Department. In standard application, subcontract agreement feature is not
 Final approval with other management available. A custom form needs to be developed to capture the
team. subcontractor agreement details.
 The key users want to have an Advance
recovery option for Advance Payment The custom form contains following details
and for Down Payment option there
should be no recovery option.  Subcontractor Name
 Subcontractor Number
At present users have Scope of Work field in the  Subcontract Order No (Created by Procurement)
agreement they want this field to be kept in place  Subcontract Type (Service Order, Work Order, Light
of Task number in the agreement. Order)
 BOQ Details
Milestone payments, monthly assessment  DLP Details
payment terms are used in the present system and  Payment Terms
same need to be followed in the future as well.  Subcontract Value
 Bond Details
Users want to have Place of Payment as optional.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 94


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

There should be some fields in the agreement like Commercial Department should enter all the required mandatory
types of insurance, eligibility document & etc. information in agreement form.

Apart from existing Bond Types in Subcontract Some of the mandatory fields are as follows
Agreement, Few Other Bond Types are required.
The list is to be provided by Finance Department.  Project Number
 Subcontract Number/Name
Letter of Guarantee’s created for the supplier  Subcontract Type (Lumpsum/Remeasurable)
should be shown in list of value of Guarantee’s in  Currency
Subcontract Agreement.  Advance %
 Retention%
Replace Contract Name field to Subcontract  Advance Recovery %
Name.  Contract Award Date
 Agreement Validity Dates
 Defect Liability Days
 Insurance Details

Once all the information is entered, the document should be


submitted for approval.

Approval Hierarchy details should be provided by Commercial


Department.

Revision control should be provided for Subcontract agreement to


capture the variations.

PA.BP.59.0 If the subcontractor is not registered in Qatar than GAP CH A custom form needs to be developed to capture the Subcontract Commercial User
Subcontract
withholding tax of 5% on work done will be Work done details.
Liability
applied.
Statement
The subcontract work done details form consists of following
information

 Subcontract Quantity
 SC Value
 SC Application Quantity
 SC Application Amount
 Actual Workdone Quantity
 Actual Workdone Value

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 95


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Workdone Value
 Workdone Quantity
 Material at Site
 Variation Values

At month end QS will check the details of Subcontract Work done


and enter the same in the liability statement for generation of
invoices.

Accruals: Accruals should be calculated based on Actual Workdone


Value. If QS doesn’t enter Actual Workdone values, a provision
should be provided to Cost Control department to enter the accruals
value directly in Accruals Custom Form.

Subcontract Material Issue:

A customization needs to be developed to track the Material issued


to subcontractor. Whenever material is issued to subcontractor from
Project Store, The material details needs to captured for deductions.

A custom form should be developed in inventory Module.


Whenever material is required to be issued to Subcontractor, the
material will be issued against a SMR. Store Keeper should select
the subcontractor name at header level and issue the material.

The details of Material issued to subcontractor should be populated


in a custom form in Subcontract module where QS can enter the
margin percentage.

Based on the Margin entered in the custom form, Value of Billing


should be calculated (Based on Item Weighted Average cost and
Margin).

Purchases for Subcontractor:

UCC Procures material for subcontractors. Material Purchases made


to the subcontractor should be captured.

The details of Material procured to subcontractor should be


populated in a custom form in Subcontract module where QS can

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 96


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

enter the margin percentage.

Based on the Margin entered in the custom form, Value of Billing


should be calculated (Based on Purchase Price and Margin). Partial
Material Billing can be performed.

Material on Site

A custom form needs to be developed to track material on site with


following details

 Item Code
 Item Description
 Quantity
 Bill Quantity
 Rate
 Amount
 Remarks

Material off Site

A custom form needs to be developed to track material off site with


following details

 Item Code
 Item Description
 Quantity
 Bill Quantity
 Rate
 Amount
 Remarks

Once all the details are entered by Q.S, the Liability Statement
should be submitted for approval.

Note: Approval Hierarchy should be provided by Commercial


Department (Project Wise Hierarchy).

Liability Statement Customization will have Version Control.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 97


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Please refer PA.BP.54 for Accruals details.


PA.BP.60.0 Subcontract Advance Payment Certificate GAP CH When a subcontract order is awarded. Before starting the work Commercial User
Subcontract
some of the amount in total contract will be provided as an advance.
Billing:
Currently based on Subcontract Order, Contracts
Subcontract
department is preparing Advance Payment A Custom component for billing (Payment Certificate) will be
Advance Payment
Certificate Certificate Outside the system. provided to UCC.

Print Advance PC is sent for internal approval for For entry of Advance, the Payment Certificate Type will be selected
processing payment. Approved copy is getting as “Advance” for advance subcontractor invoice.
submitted to Finance for Processing of Payment to
supplier. The following details needs to be entered in the header level

Finance is directly processing Payable  Operating Unit


Prepayment invoice in the Fusion system.  Project Number
 Subcontract Agreement No
UCC would like to maintain Payment Certificate  Document Type
details in System.  Document Date
 PC No (Auto Generation)
Approval Hierarchy details needs to be provided  Period
by UCC Contracts Department.  Comments (if any)

Once the advance document type is selected, at line level the


advance amount will be entered in Accounting Value Column
against the Advance Row. Once the transaction has been entered,
user will Click on transfer which will automatically create an
Prepayment Invoice in AP Module.

When advance recovery needs to be done, user will enter the details
of the advance recovery in advance recovery field when next invoice
has been raised against the Subcontract Agreement. Once the entry
is completed, the user will select the transact button which will
directly pass the Advance Recovery details to AP.

Note: Value of work done amount will be calculated in Subcontract


Liability Statement custom form and the same will be Populated in
PC custom form.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 98


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

PA.BP.61.0 Payment Certificate (Monthly Invoice) GAP CH QS Will track the Subcontract work done and capture all the Commercial User
Subcontract
information in Liability Statement.
Billing: Payment
Currently based on Subcontract Order work done
Certificate
details captured by QS department, QS At every month end, QS needs to navigate to PC Custom form and
(Monthly Invoice)
department is preparing Payment Certificate create a Payment Certificate for Subcontract Agreement.
(Outside the system).

Print PC is sent for internal approval for The following details needs to be entered in the header level
processing payment. Approved copy is getting
submitted to Finance for Processing of Payment to  Operating Unit
supplier.  Project Number
 Subcontract Agreement No
Finance is directly processing Payable invoice in  Document Type
the Fusion system and applying Retention and  Document Date
Advance Recovery amounts.  PC No (Auto Generation)
 Period
UCC would like to maintain Payment Certificate  Comments (if any)
details in System.
Once the details are entered, QS should click on Get Lines button
UCC want to populate Advance and Recovery which will generate VOWD value along with Advance Recovery
Percentage in Payment certificate automatically and Retention Values (Based on Percentages captured at
based on Agreement. Agreement)

Approval Hierarchy details needs to be provided QS Can enter the other deduction values in PC and Submit it for
by UCC Contracts Department. approval to hierarchy.

Note: Hierarchy details needs to be provided by UCC Commercial


Department (Project Wise).

Once the PC is approved, a notification will be sent to finance user


for information.

QS Needs to click on Create Invoice button which will create a draft


invoice with all the deduction amounts.

Note: QS needs to select Prepayment invoice number in PC while


submitting a Progress Invoice with advance recovery.

Note: Value of work done amount will be calculated in Subcontract


Liability Statement custom form and the same will be Populated in

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 99


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

PC custom form.

Following are the Types of PC are maintained

 Advance
 Additional Advance
 Progress Invoice
 Retention
 Final Retention
 Additional Retention
PA.BP.62.0 Retention Recovery GAP CH When the subcontract work is completed, QS will enter the
Subcontract
Retention Recovery Invoice.
Billing Retention
Currently QS Department verifies the contractual
Recovery
terms and releases Retention amounts to A Custom component for billing (Payment Certificate) will be
Subcontractor. Retention Release Payment provided to UCC.
certificate is prepared by QS and is getting
submitted for approval (Manual Approval). For entry of Retention Recovery, the Payment Certificate Type will
be selected as “Retention Recovery”.
QS is sending the Signed copy to Finance for
Payment release. The following details needs to be entered in the header level
UCC would like to maintain Retention Release
Payment Certificate details in System.  Operating Unit
 Project Number
Approval Hierarchy details needs to be provided  Subcontract Agreement No
by UCC Contracts Department.  Document Type
 Document Date
 PC No (Auto Generation)
 Period
 Comments (if any)

Once the retention recovery amount is entered, the document can be


submitted for approval.

Once the transaction has been entered, user will Click on transfer
which will automatically create a Prepayment Invoice in AP
Module.

PA.BP.63.0 GAP CH Final Retention Recovery will be performed by DLP Department


Subcontract
after completion of DLP Period.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 100


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Billing Final
Retention When the DLP Period is completed, DLP Department will enter the
Recovery Final Retention recovery Invoice.

A Custom component for billing (Payment Certificate) will be


provided to UCC.

For entry of Final Retention Recovery, the Payment Certificate Type


will be selected as “ Final Retention Recovery”.

The following details needs to be entered in the header level

 Operating Unit
 Project Number
 Subcontract Agreement No
 Document Type
 Document Date
 PC No (Auto Generation)
 Period
 Comments (if any)

Once the retention recovery amount is entered, the document can be


submitted for approval.

Once the transaction has been entered, user will Click on transfer
which will automatically create a Prepayment Invoice in AP
Module.

PA.BP.64.0  Department Budgets are created in General Ledger Module. Project Key User
Department
Budgets
Complete Control of Department budgets will be lying with Cost
Control Department.

Each account combination wise budgets should be defined GL


Module.

The following information needs to be entered in Budgets Window

 Currency

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 101


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Budget
 Period
 Account Code Combination
 Value
The budgets can be uploaded through Excel Sheets.

UCC would like to have following type of control in department


budgets
When end user is raising any Requisition, IF the system budget
check is failed, system should popup a window which will ask user
to enter the reason/justification for getting the over budget.

User should be able to enter the Reason/justification in the popup


and send it for approval to nominated user, if the nominated user is
satisfied with the reason, he should be able to click on submit and
the request should be submitted for approval.

If approver rejects, system should not allow to submit the document


for approval.

Please refer Budgetary control point for more details on Budget


Control.
Note:
Excel Upload Option is available to create department Budgets.
Department Budget amendments are not Made.
Finance should have view only access to department budgets.
Elements received from Projects Cost Control Department should be
validated with COA.

Please find Annexure-G for detailed elements used in Preparing


G&A Budget

PA.BP.64.1 GAP CH Reporting: UCC Cost Control Department Generates following Project Key User
Department
Budgets - reports on monthly basis

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 102


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Reporting  Departments Monthly Summary


 Department Periodic Report
 Actual Cost

Actual Cost:
To Generate Actual Cost Report a Custom form needs to be
developed to track Accruals Cost details.

The custom form should contain following details

Header Level:
 Department/G&A Code
 Department/G&A Name

Line Level:
 G&A/Department Details
 Each Detail wise/Month wise Accrual Cost Entry Column

Department Periodic Report:

Department periodic Report consists of each Detailed wise Budget


Vs Actual Comparison (Monthly).

Department Monthly Summary:

The report contains following details each department wise

 G&A/Department Details
 Budget
 BCWP (Earned Value)
 ACWP
 Trend Input (should be provided as parameter in report)

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 103


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 CTC
 CAC
 CVAC

Different valued Reports can be generated based on Trend Selected


at Parameters while generating Report.

Please refer MD050 for more details and field level validations.
PA.BP.65.0 UCC would like to get the Cost to company GAP CH Cost to Company Calculation will be performed by HR Department. HR User
Cost to Company
(Labor) details from EBS. CTC rates of Labor are Please refer T&A Document for More Details.
Labor
calculated in HCM module.
However the details provided by Cost Control department are as
follows

Please find attached CTC Calculation Formula Sheet with Elements


which needs to be considered

Labor CTC.xlsx

Note: Currently HR Department doesn’t have CTC Calculation for


Labor. It is an open point in T&A
PA.BP.66.0 UCC would like to get the Cost to company GAP CH Cost to Company Calculation will be performed by HR Department. HR User
Cost to Company
(Labor) details from EBS. CTC rates of Labor are Please refer T&A Document for More Details
Staff
calculated in HCM module.
Note: Currently HR Department doesn’t have CTC Calculation for
UCC was calculating CTC rate with following Staff. It is an open point in T&A
information
1. Basic
2. Transport
3. Housing
4. Medical Insurance
5. Air Tickets
6. Mobile Charges
7. Recruitment Expenses
8. Visa Charges

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 104


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

9. Indemnities and etc.

UCC would like to charge staff cost to projects


based on the CTC rates and time frames.

PA.BP.68.0 GAP CH Project User


Forecasting UCC Want to Forecast the following in the system
 Manpower Forecast
 Staff Forecast
 Equipment Forecast
Forecasting feature is not available in projects module. Forecasting
customization needs to be developed.
Planning Department is going to perform the forecasting.
Following forms needs to be developed for forecasting
customization
 Manpower Forecast Project Level
 Staff Forecast Project Level
 Equipment Forecast Project Level
 Manpower Forecast Company Level Custom
 Staff Forecast Company Level
 Equipment Forecast Company Level

Following fields should be available in Forecast form


Manpower Forecasting Form
 Project Number
 Project Name
 Current Holding Quantities (Total Manpower defined in
Manpower Pool) (Inhouse and Hired)
 Calendar months based on project start and end date. If
project is more than 7 Years then 7 Years of Calendar from

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 105


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Project Start Date.


 Labor Jobs Defined in HR
Staff Forecasting Form
 Project Number
 Project Name
 Current Holding Quantities (Total Staff defined in HR)
 Calendar months based on project start and end date. If
project is more than 7 Years then 7 Years of Calendar from
Project Start Date.
 Staff Jobs defined in HR

Equipment Forecasting Form


 Project Number
 Project Name
 Current Holding Quantities (Total Equipment Inhouse and
Hired)
 Calendar months based on project start and end date. If
project is more than 7 Years then 7 Years of Calendar from
Project Start Date.
 Equipment Categories Defined in Asset Management (Eam
Module)
Planner for projects need to enter forecasting data in the custom
form.
Approval Hierarchy is required for all the Project Level Forecasting
Custom Forms.
Hierarchy: Planner  Project Manager  Project Director 
Planning Headoffice
In each project level custom forms, Forecasting will be performed by
Planning department by splitting total quantities to period.
Once all the project level forecasting is completed. User should

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 106


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

navigate to company level custom from and click on Generate.

All the Project level Month Values will summed up and shown in
Company Level.
Following information will be shown at company level forecasting
forms
Header:
 Operating Unit
Lines:
 Project Number
 Project Name
 Totals
 Detailed Split upto 7Years

Revisions: Revision control should be available for all project


forecasting forms. Monthly revisions are made by Planning
Department.

Deployment of Manpower/Staff/Equipment should not be


restricted on Forecasting Quantities.
The forecast is used in MJCR Process.

PA.BP.69.0 GAP CH
Actual Cost On Need Basis Cost Control Department would like to allocate Cost Project Key User
Reallocation from

 Activity to Activity
 Cost Code to Cost Code
 Project to Project
A custom Process needs to be developed in EBS for Cost

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 107


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Reallocation.
The custom form should contain following details
 Cost Booked Activity
 Cost Booked Cost Code
 Project No
 Project Name
 Cost Booked Date
 Cost Value
Cost Control Department will reallocate the cost by entering the
following details in the custom form against the above mentioned
fields by selecting the line (Check Box)
 Reallocated Activity (Defaults Cost Booked Activity) User
will change (If Required)
 Reallocated Cost Booked Cost Code (Defaults Cost Booked
Cost Code) User will change (If Required)
 Reallocated Project No (Defaults Cost Booked Project No)
User will change (If Required)
 Reallocated Project Name (Defaults Cost Booked Project
Name)
 Reallocated Cost Date (Defaults Current Date)
 Reallocated Cost Value (Defaults Cost Value Activity) User
will change (If Required)
Validations:
 Cost Reallocation Value should not be more than Original
Cost Value
Activity Reallocation with in the projects:
When Activity Reallocation is performed, there will not be any
financial Impact. The transactions will be posted in projects module
only.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 108


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Cost Code Reallocation with in the projects:


When Cost Code is reallocated is performed, Accounting entries
should be posted to General Ledger Module in Unposted Status.
Accounting Department will post the Journal Manually by verifying
the details.
Accounting entry should be generated automatically based on
Selected Cost Codes and mapping of Cost to Accounts.
Debit: Reallocated Cost Code
Credit: Original Cost Code
Cost Reallocation between projects:
When Project to Project cost reallocation is performed, Accounting
entries should be posted to General Ledger Module in Unposted
Status.
Accounting Department will post the Journal Manually by verifying
the details.
Accounting entry should be generated automatically based on
Selected projects and Cost Codes and mapping of Cost to Accounts.
Debit: Reallocated Cost Code & Project
Credit: Original Cost Code & Project
Before Reallocation, Cost Control user should send the reallocation
approval notification to Projects Department and For Your
information notification to Finance User.
Hierarchy details needs to be provided by Cost Control Department.
Please refer Reallocation MD050 for more details.

Note: Budget needs to release when Cost Code Reallocation


transaction process is performed.
Please refer PA.BP.21 for more details on budgetary affects.
Please refer MD.050 for more details and field level validations.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 109


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

PA.BP.69.1 
Stock Check On Monthly Basis, Projects department visits site and performs Project User
Physical Inventory Check to identify Stock discrepancies.
Physical Inventory Check Process available in System can be used to
perform the stock check
Oracle Inventory provides a fully automated physical inventory
feature that you can use to calculate system-maintained item on-
hand balances with actual counts of inventory.

Based on the counting date, system freezes the on-hand qty. When
actual quantities are entered, system shows the difference between
system & actual qty.

If quantity check department identifies that entry of the quantities


has been missed, they can intimate the store keeper to perform the
transaction in the system before count update.

The following things to do for Physical inventory counting are:


 Physical Inventory (Name)
 Tag Generation (generating tags for the items)
 Tag counts ( Physical counting)
 Approve Adjustments Approving or rejecting variation

The report requested by Projects Department for Stock check


process can be generated based on the above process.
PA.BP.70.0 GAP CH
MJCR (Monthly The following Custom Form needs to be developed in MJCR Process Project Key User
Job Cost) to generate MJCR Reports.

The following reports will be printed from MJCR Process


 Executive Summary
 Abstract
 Breakdown
 Billing Analysis

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 110


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 RB & BCWP
 Master Budget
 IBC Log
 Cost Booked in ERP
 Accrual Cost
 Stock
 VO Log

MJCR is a resource Based Costing Report which is submitted on


monthly basis.
Executive Summary Report will be used as Cover Page for MJCR
Reports.
The following information will be used to create the above
mentioned reports

Master Budget: Base Budget of the Project will be considered as


Master Budget (rev 0). Approved Master budget cannot be changed
at any point of time.

Revised Budget: Whenever changes occur in the Budget due to


scope variations, design changes or any reason, the revision of
budget will be performed, the latest revised budget value should be
considered in the reports

% of Master Budget: Based on total Budget value and value of Each


Cost Group, Cost Group wise percentage should be calculated.

% of Revised Budget: Based on total Revised Budget Value of Each


Cost Group, each Cost Group wise percentage should be calculated.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 111


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Earned Value (BCWP):


Taking percentage completion from BOQ (Valuation) entered by QS
Or Taking Percentage Completion from Primavera

Cost Booked in ERP: Total Actual Cost from ERP should be


generated.

Accruals: Total Accruals booked for the project should be generated.


Please refer BP.PA for details of accruals.

Actual Cost Work performed (ACWP): Cost Booked in ERP +


Accruals

Cost variance to Date: Earned Value – ACWP

CPI (Cost Performance Index): BCWP/ACWP

CTC (Cost to Complete): Calculated based on Trend Input

Total Balance Liability Cost: Stock at site + Balance Commitment


Cost + Uncommited Cost

CAC (Cost at Completion): ACWP + CTC

CVAC (Cost Variance at Completion): Revised Budget - CAC

Following forms and processes needs to be developed to generate

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 112


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

MJCR reports

 Trend Input (Breakdown Form)


 Accruals
 Stock at Site
 Billing Analysis (Based on Details from Primavera)
 Actual Cost Reallocation
 IBC
 Commitment Cost Reallocation

Trend Input Custom Form:


Custom Form should consist of following details
 Cost Code
 Cost Code Description
 Master Budget
 Revised Budget
 Earned Value
 % of BCWP against budget
 Cost in ERP (Accruals should be booked in ERP)
 ACWP (Cost in ERP)
 Cost Variance
 CPI
 Stock at Project Site(Store)
 Balance Commitment (Manual Entry)
 Uncommited Cost (Manual Entry)
 Total Balance Liability Cost

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 113


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 CTC
 Trend Input (Manual Selection)
 CAC
 CVAC

Executive Summary:
Executive Summary report consists of following main details.
 Contractual Data
 Cost Data
 Preliminary Information
 Contract Status
 Budget Status
 Progress Status
 Billing Status
 Risks & Opportunities
 Performance Indices
Executive Summary Details are generated based on detailed reports
which are mentioned above.
Billing Analysis:
Custom form should to be developed to interface the Billing analysis
performed in Primavera based on Billing Value provided from ERP.

Billing Value (Actual) should be interfaced to primavera, Primavera


should forecast the Billing value and interface the same to Project
Module to “Billing Analysis Custom Form”

Billing Analysis Rep consists of following details

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 114


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Original Billing Plan - Monthly


Original Billing Plan - Cumulative
Submitted Billing - Monthly
Submitted Billing - Cumulative
Certified Billing - Monthly
Certified Billing - Cumulative
Revised Billing Plan - Monthly
Revised Billing Plan - Cumulative
Deviation From Original Billing Plan
Percentage Deviation From Original Billing Plan

Detail Report process will be available in MD050 with field level


details.
Please refer PA.BP.54 for Accrual Details
Please refer PA.BP.69 for Actual Cost Reallocation Details
Please refer PA.BP.69.1 for Stock at Site Details
Please refer PA.BP.18 and PA.BP.19 for IBC Details
Please refer PA.BP.76 for Primavera Details

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 115


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

PA.BP.71.0 UCC Would like to reallocate Commitment Cost GAP CH Commitment cost cannot be reallocated in the system. Project Key User
Commitment
Cost Reallocation
UCC would like to reallocate Commitment cost Detailed analysis should be performed in Build Phase.
from one Cost to another cost code.

The commitment reallocation process is required


to generate MJCR Process related reports.
PA.BP.72.0 MCCR of WSD & FSD Project GAP CH Details of MCCR of WSD & FSD was provided by UCC Cost WSD Key User
MCCR of WSD &
Control Department, they would like to generate the same from
FSD
System.

MCCR of WSD & FSD will be explained in WSD Projects BP080


Document.

Please refer WSD Projects BP080 Document.


PA.BP.73.0 GAP CH Project Key User
Monthly The following reports are generated in MCCR Process
Company Costing
(MCCR)  Job Information
 Job Information 2
 Billing Analysis
 Revenue
 Cost Analysis
 Quarter Comparison
 Gross Margin
 Quarter Performance

Job Information:

Job Information Report Consists of following information:


 Project Number
 Project Name

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 116


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Contract Type (Maintained in PID)


 Status (Status of the project)
 Build Up Area (Should be maintained in PID/Project
Definition Window)
 Contractual Start (Project Start Date)
 Contractual Finish (Project Finish Date)
 Expected Finish (Value should be picked based on Latest
Expected Finish Date interfaced from Primavera)
 Running Cost Per Day (Preliminary Cost of the Project
(Excluding Mobilization, Demobilization and
Maintenance)divided by Original Contractual Duration of
the project)
 Contractual LD/Penalties per LD per Day (Total Sum of
Liquidity Damages/Penalties or any cost which main
contractor would be liable to pay to the client incase of
project is delay)
 Original contract Sum
 Original Estimation Cost Budget (Rev 0 or Master Budget)
 Original Estimation Margin (Should be calculated based on
Rev0 or Master Budget)

Please refer PA.BP.70 for details on Billing Analysis

Please refer PA.BP.18 and PA.BP.19 for IBC Details which is used for
Cost Analysis Report Generation.

Please refer PA.BP.76 for Primavera Details

Detailed Specs will be provided in MD Document. Field Wise


Calculations will be explained.

Please refer PA.BP.70 Details of Executive summary.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 117


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

PA.BP.74.0 GAP CH UCC Generates Project Key User


Cost Variance
 Monthly Cost Variance
 Cumulative Cost Variance reports

Cost Variance Report is dependent on MJCR Process.

Following forms and processes needs to be developed to generate


Cost Variance reports

 Trend Input (Breakdown Form)


 Accruals
 Stock at Site
 Actual Cost Reallocation
 IBC
 Commitment Cost Reallocation

Cumulative Cost Variance Report consists of following details

Section wise
 Latest Revised Budget
 Cost at Completion
 Cost Variance
 Cost Performance Index

Monthly Cost Variance Report consists of following details

Section Wise

 IBC Period
 Change in Cost at Completion
 Change in CVAC
 Change in Cost Performance Index

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 118


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Please refer PA.BP.54 for Accrual Details


Please refer PA.BP.69 for Actual Cost Reallocation Details
Please refer PA.BP.69.1 for Stock at Site Details
Please refer PA.BP.18 and PA.BP.19 for IBC Details

Please refer MD050 for detail field wise description.


PA.BP.75.0 UCC Would like to have seamless integration GAP CH For a project detail level activities are planned in primavera with Project Key User
Primavera
with the following details following details
Activities
 All the planning activities of the project  Late Start Date
to EBS.  Late Finish Date
 Early Start Date
 BOQ selling/ Budget rates to primavera.  Early Finish Date
 Activity ID
 Actuals to reflect back to primavera.
 Activity Code (Map with EBS)
 Budgeted resources in details.  Project Number

 CTC from cost control reports. Once all the information is planned in primavera, the same needs to
be interfaced to EBS.
 Actuals, budget and price to Primavera.
A custom form needs to be developed in EBS to capture all the
 Scheduled Workdone to ERP. Activities with Dates.

 Scheduled Budget work to ERP. Whenever activities are planned in primavera, all the activities with
dates should be interfaced to Activities Staging Table in EBS. System
 Scheduled Resource histogram to ERP.
should pick the activities from Staging table and shown in Projects
 Remaining Activities. Activities Custom Form with following details

 Consolidated histogram for Staff, labor  Project Number


and equipment.  Project Name
 Activity ID
 Percentage of completion on BOQ level,  Activity Code (Map with EBS)
activity level.  Late Start Date
 Late Finish Date
Forecast cost/work done to ERP.  Early Start Date
 Early Finish Date

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 119


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

For More information please refer PA.BP.76.0


PA.BP.76.0 UCC would like to interface the following GAP CH Following custom staging Tables and forms needs to be developed Project User
Primavera to EBS
information from ERP to Primavera to have Integration between Primavera and EBS (2 Way)
(2 Way
Integration)
 BOQ selling rates.  Activity Table
 BOQ Budget Rates.  Forecasting Details Table
 Budgeted resources in all details. (Like  Revenue Forecasting Details Table
manpower, equipment, materials,  Cost Forecast Table
subcontractors, and prelims with  Cost to Complete Table
different measurements like hours, m3,  Activity Details
m2 &etc.)  Revenue Forecast
 CTC from Cost control reports.  Cost to Complete Details
 Actual cost to date.
 Actual billing to date. The following details should to be interfaced from EBS to Primavera

From Primavera to ERP  BOQ Details


 BOQ Quantities
 Scheduled work done (planned work  Net Rate
done )  Selling Rate
 Scheduled Budgeted work (BCWS)  Net Amount
 Scheduled resource histograms  Selling Amount
 Remaining activities  Trade Codes
 Cost Codes with Quantity and Costs
 Percentage of completion on BOQ level,  Resources with Quantities and Rates
Activity level &etc.  Actuals
 Based on Actual Work done Quantity entered by Q.S
 Forecasted remaining cost. against each BOQ
 Billing Value
 Forecasted remaining work.  Cost to Complete (Total Value)

The following details should be interfaced from Primavera to EBS

 Percentage of Completion by Activity & BOQ


 Completion Based on Dates
 Activity start & finish dates (early & late & target)
 Early Start date
 Early Finish date
 Late Start date
 Late Finish date

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 120


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Activity Start date


 Activity Finish date
 Forecasted dates of activity
 Updated Dates of Activity (Latest Dates)
 Critical path (Separate Field)
 Check Box(Yes/No)
 Total expected finish date for project/milestone
 Project Finish Date
 Target drawing dates against BOQ.
 Drawings are maintained as Activities (Activity Start
and Finish Date)
 Revenue Forecast Against BOQ (Monthly Basis)
 Cost Code Forecast (Quantity Only)
 Monthly Distribution of Cost to Complete
 Package BOQ Target Procurement Dates

All the Values from Primavera should be sent to staging Tables in


EBS and Based on Staging Tables, Validations should be performed
to data and populated in Custom forms.

All the Data sent to Primavera should be generated in Staging


Tables and Primavera should pick the values from Staging Tables.

PA.BP.77.0 GAP CH
Scope of Work Scope of Work wise reports will be generated in Scope of Work Project User
Liability Liability Reports

Each scope of work is defined as a cost code in the system.


Example of Scope of works:
 Earthworks
 MEP Lighting Works
 Lift Installations
 Fire Stopping Works
 Stainless Steel Works

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 121


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Painting Works
Please refer PA.BP.11.0 for details of Cost Codes and Subcontract
Cost Codes.
Scope of work liability reports are printed in 2 levels
 High Level Summary Report (All Projects and All Scope of
Works)
 Each Scope of Work wise Reports
Scope of work High Level Summary Report consists of following
details
 Project Name
 Cost Code
 Cost Code Description (Scope of Work)
 Total Budget (Budget for the Cost Code)
 Subcontract Name (can be picked from SC Agreement)
 Subcontract Code
 Original Contracts Value (Original Agreement Value)
 Approved Liabilities (Based on Value of Work done from
Liability Statement)
 Approved Liability Variance (Total Budget – Approved
Liabilities)
 Forecasted Liabilities
 Forecasted Liabilities Variance (Total Budget-Forecasted
Liabilities)
 Recoverable Amounts
Scope of Work Liability Assessment Form:
A custom form needs to be developed to generate Scope of Work
Liability wise report.
The form should contain following details

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 122


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Header Level:
 Operating Unit
 Project Number
 Project Name
 Cost Code
 Description (Scope of Work)
 Date
 Total Revised Budget Value (Latest/Revised total Budget
of the cost code)
 Approved Liabilities (From Subcontract Liability
Statement)
 Forecast Final Cost
 Variance from Budget (Total Revised Budget Value –
Forecast Final Cost)
Line Level:
 Descriptions
 Original Contract Value
 Contractual claims
 Contra Charges

Details like Contract Charges, Adjustments etc .,should be generated


under each Description
Following columsn should be generated against each Description of
Detailed Descriptions
 Initiated By
 Contract & Variations Claimed/Approved
 Claimed Value by Subcontractor (Claims should be
tracked in Subcontract Liability Statement)

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 123


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Approved Amount by UCC (Approval of Claims


should be tracked in Liability Statement)
 Status (Status from Liability Statement)
 Contract & Variation Liability Assessment
 Unapproved Amount (Claimed Value by Subcontractor
– Approved Amount by UCC)
 Estimated Liability for Unapproved Amount (A field
needs to be provided for manual entry)
 Estimated Total Liability (Unapproved Amount –
Estimated Liability for Unapproved Amount)
 Recovery Assessment
 Recoverable (Manual)
 Non Recoverable (Estimated Total Liability -
Recoverable)
 Recoverable Details
 Remarks (Manual)

Detail report can be analyzed in MD050 Document.

PA.BP.78.0 GAP CH
Database UCC would like to generate 2 excel reports for generating different Project User
reports/graphs manually
 Header Details report
 Line Details report
Header Detail report consists of following details
 Project Name
 Project Number
 Project to Date (report Parameter)
 Northing (From Project PID)

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 124


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Easting (From Project PID)


 Original Contract Value (Base version of Contract Value)
 Revised Contract Value (Latest Approved Revised
Contract Value)
 Contract Type (From PID)
 Project Type (From Project Definition Window)
 Contractual Start Date (From PID)
 Contractual Finish Date (From PID)
 Expected Finish Date (From Latest Date which is generated
from Primavera)
 Project Director (From Key Members of Project)
 Project Manager (From Key Members of Project)
 Cost Control Manager (From Key Members of Project)
 Sr. Cost Control Engineer (From Key Members of Project)
 Cost Control Engineer
 Status (Project Status)
 Original Cost Budget (Master Budget)
 Revised Cost budget (Latest Approved Revised Budget)
 Budgeted Cost Work performed
 ACWP
 CTC
 CAC
 Cost Variance to Date
 Estimated Margin
 Margin
Please refer PA.BP.70.0 for details on BCWP, ACWP and etc values.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 125


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Line Details report consists of following details

 Project Number
 Project Name
 Actual Cost
 ACWP
 BCWP
 CAC
 Commitment Cost
 Cost Code
 Cost to Complete
 Original Budget
 Revised Budget
 Stock at Site
 Uncommitted Cost
 Accruals
 % Revised Budget

Please refer PA.BP.54 for Accrual Details


Please refer PA.BP.69 for Actual Cost Reallocation Details
Please refer PA.BP.69.1 for Stock at Site Details
Please refer PA.BP.70

PA.BP.79.0 GAP CH
Cashflow Project Project Wise Forecasting Cash flow reports are generated by UCC Project Key User
& Company Planning department. & Finance Key
User

Cash Inflow Report


Cash Inflow Report consists of following details
Header Details
 Project Value
 Advance %
 Advance Value

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 126


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Project Start Date


 Project End Date
 Retention Execution
 Retention Completion (Based on Final Retention Release
%)
 Payment Terms - Certified (Days) (From PID Document)
 Defect Liability Period (Days) (From PID Document)
 Advance Payment Guarantee
 Performance Guarantee
Line Details:
Monthly Forecasting of following details should be generated in the
report
 Gross Invoice
 Gross Cumulative
 Advance Cumulative
 Advance
 Retention Cumulative
 Retention
 Net Invoice (Gross Invoice - Advance - Retention)
 Net Cumulative (Net Invoice + Previous Month Net
Cumulative)
 Net Receipt
 Retained Cash in Bank
 Cumulative Value (Net Receipt + Retained Cash in Bank +
Previous Month Cumulative Value)
All the Actual values should be generated from Payment Certificate
and the forecasting details should be picked from Primavera details.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 127


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Cash Outflow Report:


Cash Outflow Report consists of following details
Header Details
 Project Value
 Advance %
 Advance Value
 Project Start Date
 Project End Date
 Retention Execution
 Retention Completion (Based on Final Retention Release
%)
 Payment Terms - Certified (Days) (From PID Document)
 Defect Liability Period (Days) (From PID Document)
 Advance Payment Guarantee
 Performance Guarantee
Detail Levels are divided into 2 major categories
 Direct Overheads
 Subcontractor
Direct Overheads
 Mobilization
 Design Fees
 Staff Cost
Following details are required to be generated on monthly basis
 Gross Invoice
 Gross Cumulative

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 128


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Advance Cumulative
 Advance
 Retention Cumulative
 Retention
 Net Invoice
 Net Cumulative
 Net Receipt
 Retained Cash in Bank
 Cumulative
Each Subcontractor description wise following details should be
generated in the report
 Subcontract Description
 Advance Payment
 Advance Payment Date Paid
 Retention Execution
 Retention Completion
 Payment Terms - Certified (Days)
 Defect Liability Period (Days)
All the above details should be picked from Subcontract Agreement
details and when multiple Subcontractors are provided with one
Subcontract Description, Payment Terms should be averaged and
calculated and shown in the reports.
Final Cash flow reports formats needs to be provided by UCC

PA.BP.80.0 Initial Over Run Process GAP CL UCC would like to track the Overrun details and send it to approval Projects Key User
Initial Overrun
Process to GCEO and CEO.

A custom form needs to be developed to track the Overrun details


and send it for approval.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 129


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Whenever Overrun rises while budget check performs, the overrun


details should be populated in the Overrun Custom Form. Custom
form should contain following details

 Project ID
 Initial Overrun Request
 Cost Code
 Cost Code Description
 Item Code
 Item Description
 Unit of Measure
 Quantity
 Unit Rate
 Amount
 Initial Overrun Type (Quantity or Value)
 Status of Approval
 Date of Issue
 Date of Approval
 Initial Overrun Reason(Select from the LOV)

Reasons master should be maintained in system. A lookup needs to


be defined in the system to maintain Reason Master of Overrun.

Reasons Master for Over run:


 Price escalation
 Require urgent delivery
 Exceeding wastage percentage
 Damage/loss from site
 Poor quality
 Management decision
 Change in construction method

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 130


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Change in Specification
 Rejected variation
 Self-Acceleration

Each project wise details will be generated in the Overrun Custom


form and send it for approval.

Approval Hierarchy should be provided by UCC (GCEO/CEO).

The Log for the Over runs has to be maintained in the system and
user should be able to print in Overrun report format.

Please refer MD document for more details.

PA.BP.81.0 Rate Analysis Report GAP CL Rate analysis Report is generated each project wise or multiple Project Key User
Rate Analysis
Report project wise with date range.

Report consists of following details

 Project Number
 Project Name
 Cost Code
 Cost Code Description
 Item Code
 Item Description
 Unit of Measure
 Budget
 Maximum Rate
 Maximum Rate Date
 Minimum Rate
 Minimum Rate Date
 Latest Rate

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 131


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Latest Rate Date


 Average Rate
 Market Latest Rate
 Market Latest Rate Date
 Market Average Rate

Report Details are as follows

Budget: The revised budget rate in a job (if the report is for a specific
job), or the average of the revised budget rate during the selected
duration (if the report is for all jobs), for rough budget job no budget
rate will be shown.

Project Rates: The data for a job (if the report is for a specific job), or
from multiple jobs (if the report is for all jobs)

 Max Actual Rate/Date: The maximum actual rate used in


the purchase of the product during the selected duration
and measured in the default unit in a job, or in multiple
jobs data, based on the report filters, and the date of this
purchase.
 Min Actual Rate/Date: The minimum actual rate used in
the purchase of the product during the selected duration
and measured in the default unit in a job, or in multiple
jobs data, based on the report filters, and the date of this
purchase.
 Latest Actual Rate/Date: The up-to date actual rate used in
the purchase of the product during the selected duration
and measured in the default unit in a job, or in multiple
jobs data, based on the report filters, and the date of this
purchase.
 Average Actual Rate: The average rate used in the
purchase of the product during the selected duration and
measured in the default unit in a job, or in multiple jobs
data, based on the report filters.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 132


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

The formula used for the computation of the average actual rate as
follows:

 Average rate for one job, or for all jobs in details formula =
Total cost amount of all product’s purchases during the
selected duration per job / Total quantity of all relevant
purchases measured in the same default unit.
 Average rate for all jobs in summary formula = Total cost
amount of all product’s purchases during the selected
duration for all jobs / Total quantity of all relevant
purchases measured in the same default unit

Market Rates: Shown only if the report is generated for 1 job only or
for all jobs in details.

 Latest Actual Rate/Date: The up-to date actual rate used in


the purchase of the product during the selected duration
in all jobs (excluding the selected job) and measured in the
default unit based on the date of this purchase.
 Average Actual Rate: The average rate used in the
purchase of the product during the selected duration in all
jobs and measured in the default unit based on the date of
this purchase.

The formula used for the computation of the average actual rate as
follows:
 Average rate of the market formula = Total cost amount of
all product’s purchases during the selected duration in all
jobs including the selected job / Total quantity of all
relevant purchases measured in the same default unit

PA.BP.82.0 GAP CH Project Key User


ZVC Calculations ZVC Calculations ZVC Report Consists of following details

 Price Code
 Description

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 133


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Resource Code
 Item Number
 Quantity
 Unit of Measure
 Cost Price
 Cost Amount
 Activity

Based on BOQ Details loaded in the system, the details should be


generated in the report.

PA.BP.83.0 Concerns and Recommendation Report GAP CH A custom from needs to be developed to maintain Corrective Action Project Key User
Concerns and
Recommendation Plan. Custom form should have the following details
s Report
 Project Number
 Project Name
 Report Date
 Cost Code
 Cost Code Description
 Issue Description
 Reason
 Recommendation and Strategic Action
 Date of Recommendation
 Cost Impact
 Statues of the Recommendation (Actioned or Not)
 Action Effective Date

This Report will be generated every month for each Cost report.

PA.BP.84.0 Planning Database GAP CH UCC would like to generate following reports to generate Planning Key
Planning
Dashboards User
Database

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 134


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Exposure Database
 Revenue Forecast Database
 Dashboard Database
 Weekly Dashboard Checklist
 Staff Forecast Dashboard
 Labor Forecast Dashboard
 Equipment Forecast
 Baseline Checklist

Detail reports will be analysis.

Baseline Checklist: This report consists of following details


 Project Number
 Project Name
 Project Status
 Planning Manager
 Sr. Planning Engineer
 Planning Engineer
 Assistant Planning Engineer
 Baseline Revision Number
 Baseline Revision Date
 Baseline Revision Approval Date

All the above details needs to be picked from Projects Window and
Project Key user details.

Equipment Forecast report consists of following details


 Date
 Project Number
 Project Name
 Project Commencement Date

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 135


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Revised/Contractual Completion Date


 Forecast Completion Date
 Project Location
 Equipment Description
 Equipment Capacity
 Total Owned Equipment
 Month Wise Current Holding Details
 Monthly Staff Forecasting
Labor Forecasting

 Date
 Project Number
 Project Name
 Project Commencement Date
 Revised/Contractual Completion Date
 Forecast Completion Date
 Project Location
 Designation
 Month Wise Current Holding Details
 Monthly Staff Forecasting

Staff Forecasting

 Date
 Project Number
 Project Name
 Project Commencement Date
 Revised/Contractual Completion Date
 Forecast Completion Date
 Project Location
 Designation

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 136


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

 Month Wise Current Holding Details


 Monthly Staff Forecasting

Please refer Report Spec for more details on reports fields.

PA.BP.85.0 
Auto-Accounting Revenue & Invoice accounts will be generated based on the auto SETUP
accounting setup. Auto Accounting determines the General Ledger
accounts based on auto accounting rules to which Oracle Projects
charges transactions.
Oracle Projects uses the accounting from Auto Accounting when it
generates accounting events for revenue & invoice distribution lines.
Accounting process creates final accounting for the accounting
events and transfers to General Ledger & Receivables.
UCC would use auto-accounting based on event types. Natural
accounts are attached to Event types.
To generate Revenue & Invoice account entries, the following
accounting rules will be defined.

Function:- EVENT REVENUE

Segment Value Description


Company Company from Value Derived from
Project Organization
Organization
Division Division from Value derived based
Project Type on Project Type
Department Constant 00
Account From Event Type Value Derived from
Event Type
Sub-Account Constant 00000
Project Project from Value Derived from
Project No. Project No.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 137


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Employee Constant 00000


Inter Co Constant 000
Future Constant 00

Function:- REVENUE & INVOICE ACCOUNTS (Receivable


Account)

Segment Value Description


Company Company from Value Derived from
Project Organization
Organization
Division Constant 00
Department Constant 00
Account Account- Account-Receivable-
Receivable- Constant
Constant
Sub-Account Constant 00000
Project Project from 0000000
Project No.
Employee Constant 00000
Inter Co Constant 000000
Future Constant 000

Function:- REVENUE & INVOICE ACCOUNTS (Unbilled


Receivable Account)

Segment Value Description


Company Company from Value Derived from
Project

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 138


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

Organization Organization
Division Constant 00
Department Constant 00
Account Account-Un Account-Receivable-
Billed Constant
Receivable-
Constant
Sub-Account Constant 00000
Project Project from 0000000
Project No.
Employee Constant 00000
Inter Co Constant 000000
Future Constant 0000

PA.BP.86.0  The following data needs to be provided


Data
Requirements
 Expenditure and types
 Activity Master
 As of cut-off date, Project-wise BOQ and cost budget needs
to be prepared with Budget Values
 As of cut-off date, all Open Projects with Task details needs
to be uploaded
 Projects in DLP Period
 Revenue budget
 Contract Agreement Details
 Cost incurred details as per live date by expenditure type

Activity Responsibility
Data Accuracy Check UCC
(Duplicate records)
Format Specification NALSOFT

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 139


BP.080-Future Business Process

Control Functional Description Map PR Functional Map/ Recommended Solution Responsibility


Number Requirement

(Required Columns)
Manual entry into system/ UCC/NALSOFT
Developing Interface Script
and Uploading the Data into
Interface Tables
Post Entry Scrutiny UCC

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 140


BP.080-Future Business Process

Personalization’s

Projects

S. No Personalization Resolution Remarks

1 Project Status Inquiry – Invoiced Amount, Received In project status inquiry the details of AR Invoice needs to
Account show in the project status inquiry window. The following
fields needs to be inserted
 Invoiced Amount
 Received amount
 Advance Amount
 Retention Amount

2 Projects Tasks Freeze for BOQ Projects Activities will be created as tasks in Main Projects Tasks
window. A Personalization will be done in such a way that the
Tasks cannot be changed for BOQ Projects (Tasks which are
created from Costing Window).

3 Budgets window Freeze Approved Cost Budget and Approved Revenue Budget will be
created from Projects custom form, an personalization will be
done in such a way that no changes can be made in Budgets
window for BOQ projects in order to avoid mismatch between
values of Projects Custom form and Standard Budget window.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 141


BP.080-Future Business Process

DFF’s

Projects

Sr. No DFF Description

1 Main Contract Number A zoom form needs to be developed to track Main Contract Number against DLP Project.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 142


BP.080-Future Business Process

Interfaces and Workflows

Projects

SR. No Workflow Description

1 Project Purchase Requisition/Purchase Order Charge Account Project PO/PR auto charge account generation. When an PR/PO has been raised against a
project, based on the auto accounting setup the system will automatically generate charge
account, which cannot be changed manually.

2 AP Invoice (Project Invoice) AP Project Invoice Charge Account Generation workflow has been developed. When an AP
invoice has been raised and project details are entered in the invoice, the system will
generate charge account based on the selected Project type, Expenditure Type and auto
accounting setup.

3 Project Approved Cost Budget Account Generation (Budget GL Interface) In Projects Budgets window, Budget Accounting Generation workflow has been developed.
when the baseline option is selected in cost budget window, the system will generate
Accounts against each resource which has been utilized to arrive cost budget and interface
the same to GL.

4 BOQ Details Cost Budget Interface to Standard Project Budgets

5 Agreement When Custom Agreement is entered, Standard Agreement should be created automatically

6 Approved Revenue Budget When Custom Agreement is entered, Standard Revenue Budget should be created
automatically

7 Tasks In Costing window, Based on BOQ details uploaded An Interface should be developed in
such a way that the Trade Codes will be created in Projects Tasks window automatically
when the user selects the Create/Update tasks button in BOQ window.

8 Approvals Required for following forms


 PID
 Agreement
 Workdone
 Invoiced
 Certified

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 143


BP.080-Future Business Process

 Percentage Completion
 Payment Certificate
 Subcontract Agreement
 Subcontract Liability Statement
 Subcontract Payment Certificate
 Accruals
 Cost Reallocation

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 144


BP.080-Future Business Process

Reports

Projects

Sr. No Module Report Type Report Name Report Description Location Printer Type Mode Paper Output

1 Projects Analysis Internal Budget Change (IBC) Internal Budget Change (IBC)
Log Log

2 Projects Analysis Subcontract and Consultancy Subcontract and Consultancy


Agreement Log Agreement Log

3 Projects Analysis Payment Log Payment Log

4 Projects Analysis Payment Certificate Payment Certificate

5 Projects Analysis Interim Application for Interim Application for


Payment Payment

6 Projects Analysis Executive Summary Report General Summary-MJCR

7 Projects Analysis Abstract-MJCR Abstract-MJCR

8 Projects Analysis Break Down-MJCR Break Down-MJCR

9 Projects Analysis Billing Analysis-MJCR Billing Analysis-MJCR

10 Projects Analysis RB & BCWP-MJCR RB & BCWP-MJCR

11 Projects Analysis Master Budgets-MJCR Master Budgets-MJCR

12 Projects Analysis Cost Booked in ERP-MJCR Cost Booked in ERP-MJCR

13 Projects Analysis Accrual Cost-MJCR Accrual Cost-MJCR

14 Projects Analysis Stock-MJCR Stock-MJCR

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 145


BP.080-Future Business Process

15 Projects Analysis VO log-MJCR VO log-MJCR

16 Projects Analysis Periodic Cost Variance Report Periodic Cost Variance Report

17 Projects Analysis Cumulative Cost Variance Cumulative Cost Variance


Report Report

18 Projects Analysis Job Information-MCCR Job Information-MCCR

19 Projects Analysis Revenue-MCCR Revenue-MCCR

20 Projects Analysis Cost Analysis-MCCR Cost Analysis-MCCR

21 Projects Analysis Quarter Comparison-MCCR Quarter Comparison-MCCR

22 Projects Analysis Gross Margin-MCCR Gross Margin-MCCR

23 Projects Analysis Quarter Performance-MCCR Quarter Performance-MCCR

24 Projects Analysis Scope of Work Liabilities Scope of Work Liabilities


Assessment Schedule Assessment Schedule

25 Projects Analysis Scope of Work Liability Scope of Work Liability


Assessment Form Assessment Form

26 Projects Analysis Cash In Flow Cash In Flow

27 Projects Analysis Cash Out Flow Cash Out Flow

28 Projects Analysis Extension of Time Claim Extension of Time Claim

29 Projects Analysis Current Progress vs Exposure Current Progress vs Exposure

30 Projects Analysis Ongoing Projects Billing Ongoing Projects Billing


Forecast Forecast

31 Projects Analysis Rate Analysis with budget Rate Analysis with budget
comparison comparison

32 Projects Analysis High Level Summary Report High Level Summary Report

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 146


BP.080-Future Business Process

33 Projects Analysis Cost Code Analysis Cost Code Analysis

34 Projects Analysis Data Base Detailed/Lines Data Base Detailed/Lines


Report Report

35 Projects Analysis Data Base Header Report Data Base Header Report

36 Projects Analysis Monthly Running Cost for Monthly Running Cost for
Projects Projects

37 Projects Analysis Actual Cost Sheet Actual Cost Sheet

38 Projects Analysis Departments Monthly Departments Monthly


Summary Report Summary Report

39 Projects Analysis Department Periodic Report Department Periodic Report

40 Projects Analysis Department Actual Cost Report Department Actual Cost


Report

41 Projects Analysis Initial Overrun Report Initial Overrun Report

42 Projects Analysis Manpower Forecast – Project Manpower Forecast – Project


Level Level

43 Projects Analysis Staff Forecast – Project Level Staff Forecast – Project Level

44 Projects Analysis Equipment Forecast – Project Equipment Forecast – Project


Level Level

45 Projects Analysis Manpower Forecast – Company Manpower Forecast –


Level Company Level

46 Projects Analysis Staff Forecast – Company Level Staff Forecast – Company


Level

47 Projects Analysis Equipment Forecast – Company Equipment Forecast –


Level Company Level

48 Projects Analysis Rate Analysis Report Rate Analysis Report

49 Projects Analysis ZVC Calculations ZVC Calculations

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 147


BP.080-Future Business Process

50 Projects Analysis Exposure Database Exposure Database

51 Projects Analysis Revenue Forecast Database Revenue Forecast Database

52 Projects Analysis Dashboard Database Dashboard Database

53 Projects Analysis Weekly Dashboard Checklist Weekly Dashboard Checklist

54 Projects Analysis Staff Forecast Dashboard Staff Forecast Dashboard

55 Projects Analysis Equipment Forecast Dashboard Equipment Forecast


Dashboard

56 Projects Analysis Labor Forecast Dashboard Labor Forecast Dashboard

57 Projects Analysis Baseline Check List Baseline Check List

58 Projects Analysis Concerns and Recommendation Concerns and


Report Recommendation Report

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 148


BP.080-Future Business Process

Projects Integration with other Modules

PROJECT COSTING INTEGRATION

PURCHASING RE R
PAYABLES GENERAL LEDGER

TS S,
Q EC

UN IE
UI E

SUPPLIER COSTS

CO NTR
SI IP
TI T A

AC E
O

F T
N/ CC

O E
PO R

T DG
, E UA

AR BU
XP LS

CH ST
EN

CO
SE

MAN POWER MACHINE


TIME AND TRANSACTIONS UTILIZATION
FLEET MANAGEMENT
ATTENDANCE PROJECTS
(CUSTOM)
(CUSTOM)
NS

PR
R

ICES
TU

OJ
IO
RE

EC
AT

INVO
D

T
RM
AN

CO
FO
ES

ST
ER
SU

IN

S
TOM
IS

EE
L

OY
IA

CUS
ER

PL
AT

EM
M

INVENTORY HUMAN RESOURCE RECEIVALES ASSETS

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 149


BP.080-Future Business Process

Flow Chart: Item Creation

New Item Creation

Determine Determine
Search for existing
Start the item the Item
Item Category
Code Category Setup > Item >
Categories

Category
No Define New Value
Existis

Key Flexfield
Value

Define New
Category

Category Code
Determine
Template to Yes
be used
Attach Category
Set

Category Set

Create New Item Copy Item Attributes Change UOM


Code in Master Enter Description from existing Item accordingly and
Org Code or template save.
Master Items Master Items Master Items
Master Items

Assign to Child Assign Item


Organizations Category
Master Items Master Items

Item Storing
Yes No
Organization?

Assign to Uncheck Inventory


appropriate Stockable, Transactable,
Subinventory Organization Costing enabled, Inv. Asset
Items value attributes Organization
Items

Assign to
appropriate Stock
Locator Organization
Items
End

End

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 150


BP.080-Future Business Process

Flow Chart: PO Receipt


PO Receipt

Enter Header Info


Goods Check PO in
Waybill No,
Start Received Expected Receipts
additional
at Store Window
Comments etc
Receipts Header

Enter the actual quantity


received Select the PO
Enter the Sub inventory/ Shipment Lines to
Locator/Serial etc to be received
receive the material
Receipts Lines

End

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 151


BP.080-Future Business Process

Flow Chart: Material Return to Supplier (PO Returns)

Material Return to Supplier(PO Returns)

Start

Identify PO
No, Receipt
No. and Item
to return

Enter PO No/SRV
No/Item Code

Find Window

Select Item to be
Returned

Enter Quantity

Select Return to
Field value as
“Supplier”

Enter Return Date/Reason/


Comments/Lot and Serial
No if necessary

Transact the
Quantity

End

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 152


BP.080-Future Business Process

Expense Purchase Flow

Start

Project
Project Expense
Commitment
PR
Cost (PR)

No

Approval

Yes

Project
Project Expense
Commitment
PO
Cost (PO)

No

Approval

Yes

Actual Cost
Receipt Autointerface Interface to
Project

End

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 153


BP.080-Future Business Process

Future Process Flow: Material Request


Site Material Request

1. Source Organization
(Header)
2. Request Type (Header)
Site Material Request 3. Project Details (Header)
4. Item (Consumables)
5. UOM & Quantity
6. Activity

No

Approvals

Yes

Notification to Store Keeper

1. MIR Reference No.


2. Sub Inventory
Material Issues 3. Locator
4. Issue Qty
5. Lot & Serial

Project Interface

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 154


BP.080-Future Business Process

SMR Complete Process Flow

Start

Site Material
Request

Stock Material Issue to


Yes End
Availability Project Site

No

Material Request
from Central Store

Stock Material Transfer


Yes
Availability to Project Store

No

Material Request
to other Project
Store

Material Transfer
Stock
Yes to Project Store
Availability
(Project to Project)

No

Purchase Request

Purchase Order

Receipt Material

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 155


BP.080-Future Business Process

Future Process Flow: Subcontract Process Flow


Subcontract Process Flow

Tender Package Check List


-Drawings
Subcontract Request
-Specifications
-Bill of Quantity

No

Date of
Acceptance

Yes

Request for Quotation

Quotation from Supplier

Technical &
Commercial Evaluation

Subcontract Order

Subcontract Award

Work Order/Service
Subcontract Liability
Order/Subcontract Approval Yes
Statement/Workdone
Agreement

No
No

Approval

Yes

Subcontract Payment
Certificate

No

Approval

Yes

Subcontract Invoice
Interface to Payables

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 156


BP.080-Future Business Process

Future Process Flow: Fuel Flow


Bulk Fuel Transfers Process Flow

Service Agreement
Start with Project /
Customer
PMV

Purchase Blanket
Fuel Request at If fuel supply from Fuel Issue from PMV
Agreement with No
Project Site WOQOD Tankers to Projects
WOQOD
PMV UCC PMV

Yes

Blanket Agreement
Order Release

PMV

PO Receipt

PMV

Fuel Issue to Projects

PMV

Fuel Receipt

UCC

Invoice to WOQOOD/ Invoice Preparation &


End
Monthly Approvals

PMV

Invoice to Project/
Monthly

End

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 157


BP.080-Future Business Process

EVRF (ADS) Process Flow


Asset Deployment Process Flow

External Hiring

Purchase
Quotation Purchase Order
Requisition

Approved

No

Service Agreement with


Start
Projects

Requisition from Available Allocation of Vehicles Creation of Vehicle


Yes Mobilization
PROJECT (EVRF) Internally? from PLANT Deployment Order

Replacement Release Receipt at Release for Deployment Receipt at


Demobilization Yes Breakdown
Required? PLANT for Maintenance Breakdown PROJECT

No No

Yes Redeployment Return to PLANT (Off


Mobilization Receipt at PROJECT Demobilization
Transfer hire)

Replacement
Transfer
Equipment Utilization
Billing to PROJECTS Receipt at PLANT
Time Entry

Monthly

End

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 158


BP.080-Future Business Process

Projects Process Flow


Projects Process Flow

Start

Award Of Project

CCS-Candy Oracle - EBS

Create Project
Create Project Number
in GL

Create BOQ

Assign Cost Code &


Trade Codes
Create Project initiation
Document (PID)

CANDY INTEGRATION NO
Assign Resources
Approve

YES

Create Project

NO
Approve

YES

Assign Key Member/


Roles

Cost Budget
Upload BOQ From CCS-
Candy
Activities

NO

Approve

Standard Agreement

Create Agreement

Revenue Budget

Manpower Actual
Primavera Integration

Equipment Actual

Material Actual

General Expenses
Accruals for material

Subcontract Accruals
Accruals for
subcontractors

Accruals for staff


Workdone

Accruals from WSD

Accruals from FSD


Invoice

Accruals from PMV

Accrual for Services

Retention Release Final Progress Invoice Progress Invoice Additional Advance Payment Certificate Certified

Closure/DLP

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 159


BP.080-Future Business Process

Annexure –A1: Organization – Sub-inventory (Pictorial Representation)

UCC ORGANIZATION STRUCTURE


Global Item
Master

Urbacon Trading
& Contracting
Item
Master(UGI)
Operating Unit

Urbacon Trading
& Contracting
Urbacon Item
Master

Urbacon Item
Organization
Organizations

Central Aspire Park Hotel &


Warehouse Edutainment Complex of Al-
Urbacon Head
Umm Al Complex U-513- Najadah Souq U-
Office
Hawaya Store 513-15-APEC 295-295-14-
HCNS

GEN STORE STR1.000.000 GEN STORE1 MS.000.000


Subinventories &

IT STORE
CARPETS GEN STORE2
PWR TOOLS MS.000.000
Locators

ADM STORE
FURNITURE PPE STR1.000.000
GEN STORE
DEPARTMENT PWR TOOLS STR2.000.000
FUEL R01.A01.000 FUEL STR1.000.000
EMPLOYEE DAMAGED STR2.000.000
DAMAGED DAMAGED TS.000.000
YARD YRD.000.000

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 160


BP.080-Future Business Process

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 161


BP.080-Future Business Process

Annexure - A: Location - Organization – Sub-inventory

Item Master Organization Name Org. Code Subinventory Code Subinventory Description
UIM - UCC Item Organization UIM NA NA
IT STORE IT Store
UHO ADM STORE Admin Store
UHO - UCC Head Office DAMAGED DAMA
CARPETS Return Carpets from project
CHEMICALS Chemical Items
FUEL Fuel
GEN STORE UAH_Store
PRJ FRNT1 Project furniture
CWH - Umm Al Hawaaya Store CWH
OFF FRNT1 Office furniture
PPE Personal productive Equipment
PWR TOOLS Power tools
P.DAMAGED Partial damaged items
F.DAMAGED Fully damaged items
IT ASSET IT Asset
IT – IT Store IT
IT CONS IT Consumables
FUEL Fuel
A01 - Aspire Park Edutainment Complex U-513-513- GEN STORE Gen Store
A01
15-APEC DAMAGED Damaged Sub Inventory
PWR TOOLS Power Tools
FUEL Fuel
UCC Global Item Master PPE PPE Store
A02 - Mokarbia and Reman Café Restaurant at Ezdan
A02 GEN STORE Subinventory @ Mokarabia Reman Cafe
U-292-292-14-MRRE
DAMAGED Damaged Sub Inventory
PWR TOOLS Power Tools
FUEL Fuel
PPE PPE Store
GEN STORE1 Subinventory @ Al-Najadah Souq
A03 - Hotel & Complex of Al-Najadah Souq U-295-
A03 GEN STORE2 Subinventory @ Al-Najadah Souq
295-14-HCNS
PWR TOOLS Power Tools
DAMAGED Damaged Sub Inventory
YARD Subinventory @ Al-Najadah Souq
FUEL Fuel
A04 - Design and Build of Al Khor Farm Villa U-443- GEN STORE Gen Store
A04
443-15-AKFV DAMAGED Damaged Sub Inventory
PWR TOOLS Power Tools
A05 - Lusail Reclaimed Islands-Marine Works U-37- FUEL Fuel
A05
219-13-LRIMW PPE PPE Store
UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 162
BP.080-Future Business Process

Item Master Organization Name Org. Code Subinventory Code Subinventory Description
GEN STORE Subinventory @ Lusail Reclaimed Island
DAMAGED Damaged Sub Inventory
PWR TOOLS Power Tools

FUEL Fuel
PPE PPE Store
A06 - Souq Ahmad Pedestrian Tunnel U-310-310-14-
A06 GEN STORE Subinventory @ Souq Ahmad Pedestrian
SAPT
DAMAGED Damaged Sub Inventory
PWR TOOLS Power Tools
DAMAGED Damaged Sub Inventory
PPE PPE Store
A07 - Lusail Office Tower 1 UC-112-112-12-LOT1 A07
GEN STORE Subinventory @ Souq Ahmad Pedestrian
PWR TOOLS Power Tools
TLC_APPLNC Tlc Appliances Sub Inventory
TLC_CONSUM Tlc Consumables Subinventory
A08 - Facilities Management Department A08 DAMAGED Damaged Sub Inventory
FUEL Fuel
PPE PPE Subinventory
FUEL Fuel
GEN STORE Gen Store
A09 - Coast Guard Base UC -37-217-13-CGB A09
DAMAGED Damaged Sub Inventory
PWR TOOLS Power Tools
FUEL Fuel
A10 - Umm Al Huwaya Central Complex U-506-506- GEN STORE Gen Store
A10
15-UAHCC DAMAGED Damaged Sub Inventory
PWR TOOLS Power Tools
FUEL Fuel
GEN STORE Gen Store
A11 - New Labor Camp Expansion U-314-314-14-
A11 PWR TOOLS Power Tools
NLCE
DAMAGED Damaged Sub Inventory
PPE PPE Store
FUEL Fuel
A12 - CP07-A-1C - Infrastructure Works at Wadi
A12 DAMAGED Damaged Sub Inventory
Crossing - Seef Lusail South & QEC
GEN STORE Store Sub Inventory
FUEL Fuel
PPE Only For PPE Transfer From Central warehouse
GEN STORE1 Subinventory At Al Jassassiya South House
GEN STORE2 Subinventory 2 At Al Jassassiya South House
A13 - Al Jassassiya South House U-74-74-14-AJSH A13
GEN STORE3 Subinventory 3 At Al Jassassiya South House
GEN STORE4 Subinventory 4 At Al Jassassiya South House
GEN STORE5 Subinventory 5 At Al Jassassiya South House
GEN STORE6 Subinventory 6 At Al Jassassiya South House
UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 163
BP.080-Future Business Process

Item Master Organization Name Org. Code Subinventory Code Subinventory Description
PWR TOOLS Power Tools
DAMAGED Damaged Sub Inventory
YARD Sub Inventory Yard At Al Jassassiya South House
FUEL Fuel
GEN STORE Gen Store
A14 - Al Jeryan Private Lounge, White House Spa &
A14 DAMAGED Damaged Sub Inventory
Horse Majlis U-445-445-15-ALSM
PWR TOOLS Power Tools
PPE PPE Subinventory
FUEL Fuel
GEN STORE Gen Store
A15 - Jeryan New Staff Villas and Apartments U-514-
A15 PWR TOOLS Power Tools
514-15-JNSVA
DAMAGED Damaged Sub Inventory
PPE PPE Subinventory
FUEL Fuel
PPE Store For Storing PPE
A16 - Al Rafaa Villa and Majilis U-568-568-15-
A16 GEN STORE Main Stores
ARVMP
DAMAGED Damaged Sub Inventory
PWR TOOLS Subinventory To Store Power Tools
FUEL Fuel
A17 - MOQ Tenant Fit Out U-464-464-15-MOQT A17 GEN STORE Gen Store
PWR TOOLS Power Tools
FUEL Fuel
A18 - Hotan Farm Majlis Renovation, Health Club &
A18 GEN STORE Gen Store
Private Villa U-444-444-15-HMCV
PWR TOOLS Power Tools
FUEL Fuel
GEN STORE Gen Store
A19 - Sheikh Hamad Bin Jassim Al Thani Villa U-203-
A19 PWR TOOLS Power Tools
203-14-SHBJV
DAMAGED Damaged Sub Inventory
PPE PPE Store
FUEL Fuel
GEN STORE Gen Store
A20 - Muraikh Compound U-424-424-15-MC A20 PWR TOOLS Power Tools
DAMAGED Damaged Sub Inventory
PPE PPE Store
FUEL Fuel
GEN STORE Gen Store
A21 - Plot at Al Mazroa Farm U-473-473-15-PAMF A21
DAMAGED Damaged Sub Inventory
PWR TOOLS Power Tools
FUEL Fuel
GEN STORE Gen Store
A22 - North Farm U-238-238-13-NF A22
PWR TOOLS Power Tools
DAMAGED Damaged Sub Inventory
UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 164
BP.080-Future Business Process

Item Master Organization Name Org. Code Subinventory Code Subinventory Description
PPE PPE Store
FUEL Fuel
GEN STORE Gen Store
A23 - Al Khor Residence U-334-334-14-AKR A23 PWR TOOLS Power Tools
DAMAGED Damaged Sub Inventory
PPE PPE Store
FUEL Fuel
GEN STORE Gen Store
A24 - Plot Bu Thelah Farm U-447-447-15-PBTF A24 PWR TOOLS Power Tools
DAMAGED Damaged Sub Inventory
PPE PPE Store
FUEL Fuel
A25 - Ghariya Palace Marine Works U-449-449-15-
A25 DAMAGED Damaged Sub Inventory
GPMW
GEN STORE Main Store
FUEL Fuel
A26 - MOQ Kidzmondo A26 DAMAGED Damaged Sub Inventory
GEN STORE Main Store Of Moq Kidsmondo
FUEL Fuel
A27 - Interior Decoration Works for Amiri Guard GEN STORE Sub Inventory @ Guard Building Msheireb
A27
Building- Msheireb U-471-471-15-IDWAG DAMAGED Damaged Sub Inventory
PWR TOOLS Power Tools
DAMAGED Damaged Sub Inventory
FUEL Fuel
A28 - Souq Waqif to Souq Najada Tunnel U-315-315-
A28 GEN STORE Gen Store
14-SWSNT
PWR TOOLS Power Tools
PPE PPE Store
EPW_CONS Epw Consumables Subinv
FUEL Fuel
A29 - Workshop MEP Store A29
DAMAGED Damaged Sub Inventory
PPE PPE Store

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 165


BP.080-Future Business Process

Annexure – B: Customer Type & Contract Types &


Contract Scope & Industries

Customer Types:

Customer Types Description


Public Private Partnership (PPP) Public Private Partnership (PPP)
Private Private
Public - Government Public - Government

Contract Types:

Contract Types Description


Lumpsum Lumpsum
Cost Plus Cost Plus
Remeasurable Remeasurable

Contract Scope:

Contract Scope Description


Build Only Build Only
Build Operate (BO) Build Operate (BO)
Build Operate Transfer (BOT) Build Operate Transfer (BOT)
Build Own Operate (BOO) Build Own Operate (BOO)
Build Own Operate Transfer (BOOT) Build Own Operate Transfer (BOOT)
Design Build (DB) Design Build (DB)
Design Build Operate (DBO) Design Build Operate (DBO)
Design Build Operate Transfer (DBOT) Design Build Operate Transfer (DBOT)
Engineering Procurement Construction (EPC) Engineering Procurement Construction (EPC)
Engineering Procurement, Construction Engineering Procurement, Construction
Management (EPCM) Management (EPCM)

Industries:

Industries Description
Chemical Chemical
Construction Construction
Oil And Gas Oil And Gas
Industrial Industrial
Power And Water Power And Water
Transport Transport

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 166


BP.080-Future Business Process

Annexure – C: Industry, Sector and Sub Sector


Standard

Industry Standard Sector Standard SubSector Standard


Chemical Production Fertilizer Plant
Chemical Production Petrochemical Plant
Chemical Storage Chemicals Tank
Construction Commercial Convention Centre
Construction Commercial Offices
Construction Commercial Research Centre
Construction Cultural Church, Mosque
Construction Cultural Museum, Library
Construction Cultural Theatre
Construction Earthwork Dredging, Reclamation
Construction Education University, School
Construction Healthcare Hospital, Clinic
Construction Hospitality Hotel, Resort
Construction Leisure Sport Facility, Stadium
Construction Leisure Theme Park
Construction Mixed-Use Mixed-Use
Construction Public Government Facility
Construction Residential Apartments
Construction Residential Houses, Villas
Construction Retail Mall, Market
Construction Telecom Data Centre
Industrial Mining Mine
Industrial Production Aluminium
Industrial Production Cement
Industrial Production Glass
Industrial Production Other
Industrial Production Other Metal
Industrial Production Steel
Oil And Gas Downstream Gas Processing Plant
Oil And Gas Downstream Oil Refinery
Oil And Gas Storage Gas Tank
Oil And Gas Storage Oil Tank
Oil And Gas Transmission Gas Compression Station
Oil And Gas Transmission Gas Pipeline
Oil And Gas Transmission Oil Pipeline
Oil And Gas Transmission Oil Pumping Station
Oil And Gas Upstream Gas Extraction
Oil And Gas Upstream Oil Extraction
Power And Water Cooling District Cooling Plant
Power And Water Cooling Seawater Cooling Plant
Power And Water Desalination Water Desalination Plant
Power And Water Generation Coal Power Plant
Power And Water Generation Nuclear Power Plant
Power And Water Generation Oil/Gas Power Plant
Power And Water Generation Solar Power Farm
Power And Water Generation Waste to Energy Power Plant
Power And Water Generation Wind Power Farm
Power And Water Storage Dam

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 167


BP.080-Future Business Process

Power And Water Storage Reservoir


Power And Water Storage Water Tank
Power And Water Transmission Cable, Overhead Line
Power And Water Transmission Canal
Power And Water Transmission Substation, Control Centre
Power And Water Transmission Tunnel
Power And Water Transmission Water Pipeline
Power And Water Transmission Water Pumping Station
Power And Water Treatment Water Treatment Plant
Transport Infrastructure Apron, Runway
Transport Infrastructure Berth, Quay Wall
Transport Infrastructure Bridge, Causeway
Transport Infrastructure Railway
Transport Infrastructure Road, Interchange
Transport Infrastructure Streets, Utility Networks
Transport Infrastructure Tunnel
Transport Terminal Airport
Transport Terminal Car Park
Transport Terminal Rail Station
Transport Terminal Seaport

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 168


BP.080-Future Business Process

Expenditure Category – Annexure - D

LABOR
Code Description Start Date End Date
L201 Labor Charges
L403 Benefits & Services (LRD)

MATERIAL
Code Description Start Date End Date
M103 Concrete
M104 Masonry & Plastering
M105 Metals
M106 Wood, plastics, and Composites
M107 Thermal & Moisture Protection
M108 Openings
M109 Finishes
M110 Specialties
M111 Equipment (Permanent)
M112 Furnishings
M113 Special Construction
M114 Conveying Equipment
M121 Fire Suppression
M122 Plumbing
M123 Heating, Ventilating, and Airconditioning (HVAC)
M125 Integrated Automation
M126 Electrical
M127 Communications
M128 Electronic Safety and Security
M131 Earthwork
M132 Exterior Improvements
M133 Utilities
M134 Transportation
M135 Waterway and Marine Construction
M140 Process Interconnections (LPG works etc..)
M141 Material processing and handling equipment
M142 Process heating, cooling, and drying equipment
Process gas and liquid handling, purification, and
M143
storage equipment

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 169


BP.080-Future Business Process

M144 Pollution and waste control equipment


M145 Industry specific manufacturing equipment
M146 Water and waste water equipment
M148 Electrical power generation

GENERAL REQUIREMENTS
Code Description Start Date End Date
G301 Office Facilities
G302 Temporary Facilities & Shelter
G303 Utilities Connection
G304 Office Furniture
G305 Office equipment
G306 Project Signage
G407 Telephone, Internet & Fax Charges
G408 Water Charges
G409 Electricity Charges
G410 Sanitary Charges
G411 Consumables
G412 Additional Expenses
G413 Personal Protection Equipment
G414 Safety Net
G415 First Aid
G416 Protection & Care
G417 Quality Requirments
G418 Bonds & guarantees
G419 Insurances
G420 Permits & Fees
G421 Staff Charges
G422 Staff Benefits

EQUIPMENT & VEHICLES


Code Description Start Date End Date

E102 Heavy equipment


E103 Light equipment
E401 Asset purchases
E404 Heavy vehicles
E405 Light vehicles
E406 Surveying Equipment’s

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 170


BP.080-Future Business Process

E107 Scaffolding & Formwork

SUBCONTRACT
Code Description Start Date End Date

S102 Existing Conditions


S103 Concrete
S104 Masonry
S105 Metals
S106 Wood, plastics, and Composites
S107 Thermal & Moisture Protection
S108 Openings
S109 Finishes
S110 Specialties
S111 Equipment (Permanent)
S112 Furnishings
S113 Special Construction
S114 Conveying Equipment
S121 Fire Suppression
S122 Plumbing
S123 Heating, Ventilating, and Airconditioning (HVAC)
S125 Integrated Automation
S126 Electrical
S127 Communications
S128 Electronic Safety and Security
S131 Earthwork
S132 Exterior Improvements
S133 Utilities
S135 Waterway and Marine Construction
S140 Process Interconnections (LPG Works etc..)
S141 Material processing and handling equipment
S142 Process heating, cooling, and drying equipment
Process gas and liquid handling, purification, and
S143 storage equipment
S144 Pollution and waste control equipment
S145 Industry specific manufacturing equipment
S146 Water and wastewater equipment
S148 Electrical power generation

DESIGN & SUPERVISION


Code Description Start Date End Date

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 171


BP.080-Future Business Process

D301 Design
D302 Supervision
D303 Project Management

CONTINGENCIES & PROVISIONS


Code Description Start Date End Date

C001 Contingency & Provisions

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 172


BP.080-Future Business Process

Expenditure Types – Annexure - E

Expenditure Expenditure Unit of


Description Exp Category Start Date
Type Class Measure
L2011030 Civil Helper L2010000 Other Hours 1-Jan-51
L2011060 Carpenter L2010000 Other Hours 1-Jan-51
L2011090 Concrete Mason L2010000 Other Hours 1-Jan-51
L2011130 Block work Mason L2010000 Other Hours 1-Jan-51
L2011160 Plastering work Mason L2010000 Other Hours 1-Jan-51
L2011190 Tiling work Mason L2010000 Other Hours 1-Jan-51
L2011230 Steel Fixer L2010000 Other Hours 1-Jan-51
L2011260 Scaffolder L2010000 Other Hours 1-Jan-51
L2011290 Waterproofing Applicator L2010000 Other Hours 1-Jan-51
L2011560 Painter L2010000 Other Hours 1-Jan-51
L2011660 MEP Helper L2010000 Other Hours 1-Jan-51
L2011690 Plumber L2010000 Other Hours 1-Jan-51
L2011730 HVAC Technician L2010000 Other Hours 1-Jan-51
L2011760 Electrician L2010000 Other Hours 1-Jan-51
L2011790 Ductman L2010000 Other Hours 1-Jan-51
L2011860 Finishing Helper L2010000 Other Hours 1-Jan-51
L2012130 Partitioner L2010000 Other Hours 1-Jan-51
L4011330 Waterproofing Chargehand L2010000 Other Hours 1-Jan-51
L4011360 Concrete Chargehand L2010000 Other Hours 1-Jan-51
L4011390 Block Chargehand L2010000 Other Hours 1-Jan-51
L4011430 Plastering Chargehand L2010000 Other Hours 1-Jan-51
L4011460 Reinforcement Chargehand L2010000 Other Hours 1-Jan-51
L4011490 Scaffolding Chargehand L2010000 Other Hours 1-Jan-51
L4011530 Tiling Chargehand L2010000 Other Hours 1-Jan-51
L4011590 Painting Chargehand L2010000 Other Hours 1-Jan-51
L4011630 Civil Foreman L2010000 Other Hours 1-Jan-51
L4011830 MEP Foreman L2010000 Other Hours 1-Jan-51
L4011890 Plumbing Chargehand L2010000 Other Hours 1-Jan-51
L4011930 Electrical Chargehand L2010000 Other Hours 1-Jan-51
L4011960 HVAC Chargehand L2010000 Other Hours 1-Jan-51
L4011990 Ductman Chargehand L2010000 Other Hours 1-Jan-51
L4012130 Tower Crane Operator L2010000 Other Hours 1-Jan-51
L4012160 Partition Chargehand L2010000 Other Hours 1-Jan-51
L4012190 Finishing Foreman L2010000 Other Hours 1-Jan-51
L4012230 Watchman L2010000 Other Hours 1-Jan-51
L4012260 Rigger L2010000 Other Hours 1-Jan-51
L4012290 Safety Marshal L2010000 Other Hours 1-Jan-51
L4012330 Chainman L2010000 Other Hours 1-Jan-51
L4012360 Assistant Surveyor L2010000 Other Hours 1-Jan-51
L4012390 Assistant Storekeeper L2010000 Other Hours 1-Jan-51
L4012430 Assistant Timekeeper L2010000 Other Hours 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 173


BP.080-Future Business Process

L4012460 Site office boy L2010000 Other Hours 1-Jan-51


L4012490 Site office Assistant L2010000 Other Hours 1-Jan-51
L4012530 Assistant Quality Control L2010000 Other Hours 1-Jan-51
L4012560 Camp Cleaner L2010000 Other Hours 1-Jan-51
L4012590 Assistant Camp Boss L2010000 Other Hours 1-Jan-51
L4012630 Welder L2010000 Other Hours 1-Jan-51
L4012660 Plant Helper L2010000 Other Hours 1-Jan-51
L4012690 Assistant Auto Mechanic L2010000 Other Hours 1-Jan-51
L4012730 Auto Mechanic L2010000 Other Hours 1-Jan-51
L4012760 Assistant Auto Electrician L2010000 Other Hours 1-Jan-51
L4012790 Auto Electrician L2010000 Other Hours 1-Jan-51
L4012830 Light Driver L2010000 Other Hours 1-Jan-51
L4012860 Heavy Driver L2010000 Other Hours 1-Jan-51
L4012890 Light Bus Driver L2010000 Other Hours 1-Jan-51
L4012930 Heavy Bus Driver L2010000 Other Hours 1-Jan-51
L4012960 Light Operator L2010000 Other Hours 1-Jan-51
L4012990 Heavy Operator L2010000 Other Hours 1-Jan-51
L4030010 Accomodation L4030000 Other Hours 1-Jan-51
L4030020 Transportation L4030000 Other Hours 1-Jan-51
L4030030 End of Service Benefits L4030000 Other Hours 1-Jan-51
L4030040 Leave L4030000 Other Hours 1-Jan-51
L4030050 Air Ticket L4030000 Other Hours 1-Jan-51
L4030060 PPE / Safety Expenses L4030000 Other Hours 1-Jan-51
L4030070 Medical L4030000 Other Hours 1-Jan-51
L4030080 Immigration Expense L4030000 Other Hours 1-Jan-51
L4030090 Communication Allowance L4030000 Other Hours 1-Jan-51
L4030110 Food Allowance L4030000 Other Hours 1-Jan-51
L4030120 Bonus / Incentive L4030000 Other Hours 1-Jan-51
L4030130 Training Expenses L4030000 Other Hours 1-Jan-51
L4030140 Tools L4030000 Other Hours 1-Jan-51
M2031100 Concrete Forming- Plywood M1030000 Other Item 1-Jan-51
M2031110 Concrete Forming- White Wood M1030000 Other Item 1-Jan-51
M2031120 Concrete Forming- Form work Accessories M1030000 Other Item 1-Jan-51
M1031130 Concrete Forming- Releasing agent M1030000 Other Item 1-Jan-51
M1031500 Concrete Accessories & Consumables M1030000 Other Item 1-Jan-51
M1031510 Binding Wire M1030000 Other Item 1-Jan-51
M1031520 Water Stops M1030000 Other Item 1-Jan-51
M1031530 Concrete Chemicals M1030000 Other Item 1-Jan-51
M4031550 Small Tools M1030000 Other Item 1-Jan-51
M1032100 Reinforcement Bars M1030000 Other Item 1-Jan-51
M1032200 Fabric and Grid Reinforcing M1030000 Other Item 1-Jan-51
M1033100 Ready Mix Concrete M1030000 Other Item 1-Jan-51
M1033900 Concrete Curing M1030000 Other Item 1-Jan-51
M1034100 Precast Structural Concrete M1030000 Other Item 1-Jan-51
M1035000 Cast Decks and Underlayment M1030000 Other Item 1-Jan-51
M1036000 Grouting M1030000 Other Item 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 174


BP.080-Future Business Process

M1040510 Masonry Mortaring M1040000 Other Item 1-Jan-51


M1040520 Masonry & Plastering Accessories M1040000 Other Item 1-Jan-51
M1042100 Clay Unit Masonry M1040000 Other Item 1-Jan-51
M1042200 Concrete Unit Masonry M1040000 Other Item 1-Jan-51
M1042300 Glass Unit Masonry M1040000 Other Item 1-Jan-51
M1044300 Stone Masonry M1040000 Other Item 1-Jan-51
M1051200 Structural Metal Framing M1050000 Other Item 1-Jan-51
M1053000 Metal Decking M1050000 Other Item 1-Jan-51
M1055100 Metal Stairs M1050000 Other Item 1-Jan-51
M1055200 Metal Railings M1050000 Other Item 1-Jan-51
M1055730 Cladding Material M1050000 Other Item 1-Jan-51
M1064100 Architectural Wood Casework M1060000 Other Item 1-Jan-51
M1064200 Wood Paneling M1060000 Other Item 1-Jan-51
M1064300 Wood Stairs and Railings M1060000 Other Item 1-Jan-51
M1064400 Ornamental Woodwork M1060000 Other Item 1-Jan-51
M1064800 Wood Frames M1060000 Other Item 1-Jan-51
M1070110 Dampproofing M1070000 Other Item 1-Jan-51
M1070120 Polythene Sheets M1070000 Other Item 1-Jan-51
M1070130 Thermal Insulation M1070000 Other Item 1-Jan-51
M1070140 Steep Slope Roofing M1070000 Other Item 1-Jan-51
M1070150 Membrane Roofing M1070000 Other Item 1-Jan-51
M1070160 Flexible Flashing M1070000 Other Item 1-Jan-51
M1070170 Roof and Wall Specialties and Accessories M1070000 Other Item 1-Jan-51
M1070180 Fire and Smoke Protection M1070000 Other Item 1-Jan-51
M1070190 Preformed Joint Seals M1070000 Other Item 1-Jan-51
M1079200 Joint Sealants M1070000 Other Item 1-Jan-51
M1079500 Expansion Control M1070000 Other Item 1-Jan-51
M1081300 Metal Doors M1080000 Other Item 1-Jan-51
M1081400 Wood Doors M1080000 Other Item 1-Jan-51
M1081500 Plastic Doors M1080000 Other Item 1-Jan-51
M1081120 Metal Doors M1080000 Other Item 1-Jan-51
M1083000 Specialty Doors and Frames M1080000 Other Item 1-Jan-51
M1083100 Access Doors and Panels M1080000 Other Item 1-Jan-51
M1083200 Glass Door M1080000 Other Item 1-Jan-51
M1084000 Entrances, Storefronts, and Curtain Walls M1080000 Other Item 1-Jan-51
M1085000 Windows M1080000 Other Item 1-Jan-51
M1086000 Roof Windows and Skylights M1080000 Other Item 1-Jan-51
M1087100 Door Hardware M1080000 Other Item 1-Jan-51
M1088100 Glass Glazing M1080000 Other Item 1-Jan-51
M1088300 Mirrors M1080000 Other Item 1-Jan-51
M1089100 Louvers M1080000 Other Item 1-Jan-51
M1092100 Gypsum Board Assemblies and Supports M1090000 Other Item 1-Jan-51
M1092300 Gypsum Plastering M1090000 Other Item 1-Jan-51
M1093005 Ceramic Tiles M1090000 Other Item 1-Jan-51
M1093010 Mosaic Tiles M1090000 Other Item 1-Jan-51
M1093015 Other Stones M1090000 Other Item 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 175


BP.080-Future Business Process

M1093020 Porcelin Tile M1090000 Other Item 1-Jan-51


M1093025 Clay Tiles M1090000 Other Item 1-Jan-51
M1093030 Interlock Tiles M1090000 Other Item 1-Jan-51
M1093035 Marble M1090000 Other Item 1-Jan-51
M1093040 Marble threshold M1090000 Other Item 1-Jan-51
M1093045 Granite M1090000 Other Item 1-Jan-51
M1093050 Concrete Tiles M1090000 Other Item 1-Jan-51
M1093055 Tiling Accessories M1090000 Other Item 1-Jan-51
M1095000 Ceilings M1090000 Other Item 1-Jan-51
M1095500 Staircase Nosing M1090000 Other Item 1-Jan-51
M1096500 Resilient Flooring M1090000 Other Item 1-Jan-51
M1096600 Terrazzo Flooring M1090000 Other Item 1-Jan-51
M1096700 Raised Flooring M1090000 Other Item 1-Jan-51
M1096800 Carpeting M1090000 Other Item 1-Jan-51
M1097200 Wall Coverings M1090000 Other Item 1-Jan-51
M1098000 Acoustic Treatment M1090000 Other Item 1-Jan-51
M1099100 Painting M1090000 Other Item 1-Jan-51
M1099600 High-Performance Coatings M1090000 Other Item 1-Jan-51
M1101400 Signage M1100000 Other Item 1-Jan-51
M1102100 Compartments and Cubicles M1100000 Other Item 1-Jan-51
M1102600 Wall and Door Protection M1100000 Other Item 1-Jan-51
M1103000 Fireplaces and Stoves M1100000 Other Item 1-Jan-51
Safety Specialties (Emergency Aid, Fire
M1104000 Protection, etc..) M1100000 Other Item 1-Jan-51
Storage Specialties (Lockers, Post boxes, Closets,
M1105000 Shelving, etc..) M1100000 Other Item 1-Jan-51
Exterior Specialties (Sun screens, Canopies, Car
M1107000 shelters, Flagpoles, etc..) M1100000 Other Item 1-Jan-51
Other Specialties (Pest control devices, grilles,
Flags and banners, Gas lighting, Security mirrors,
M1108000 etc..) M1100000 Other Item 1-Jan-51
M1111000 Vehicle and Pedestrian Equipment M1110000 Other Item 1-Jan-51
M1111300 Loading Dock Equipment M1110000 Other Item 1-Jan-51
Commercial Equipment (Retail, Banking,
Hospitality, Office, Postal, Packaging and
M1112000 Shipping Equipment) M1110000 Other Item 1-Jan-51
Residential Equipment (Appliances, Kitchen
M1113000 units etc..) M1110000 Other Item 1-Jan-51
Foodservice Equipment (Storage, Preparation,
Delivery carts, cooking and dispensing
M1114000 equipments) M1110000 Other Item 1-Jan-51
M1115000 Educational and Scientific Equipment M1110000 Other Item 1-Jan-51
M1116600 Athletic Equipment M1110000 Other Item 1-Jan-51
M1117000 Healthcare Equipment M1110000 Other Item 1-Jan-51
M1118200 Facility Solid Waste Handling Equipment M1110000 Other Item 1-Jan-51
Other Equipment (Religious, Agricultural,
M1119000 Horticultural, Arts and crafts equipment etc..) M1110000 Other Item 1-Jan-51
M1121000 Art M1120000 Other Item 1-Jan-51
M1122100 Window Blinds M1120000 Other Item 1-Jan-51
M1123600 Countertops M1120000 Other Item 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 176


BP.080-Future Business Process

Furnishings and Accessories (Bath and bedroom


M1124000 linen & furnishings, rugs and mats etc..) M1120000 Other Item 1-Jan-51
M1125000 Furniture M1120000 Other Item 1-Jan-51
M1126000 Multiple Seating M1120000 Other Item 1-Jan-51
Other Furnishings (Interior planters and public
M1129000 space furnishings etc..) M1120000 Other Item 1-Jan-51
M1131100 Swimming Pools M1130000 Other Item 1-Jan-51
M1131200 Fountains M1130000 Other Item 1-Jan-51
M1132000 Special Purpose Rooms M1130000 Other Item 1-Jan-51
M1133000 Special Structures M1130000 Other Item 1-Jan-51
Integrated Construction (Building modules,
sound, vibration control, radiation protection
M1134000 etc..) M1130000 Other Item 1-Jan-51
Special Instrumentation (Stress, Seismic,
M1135000 Meteorological Instrumentation etc..) M1130000 Other Item 1-Jan-51
M1141000 Dumwaiters M1140000 Other Item 1-Jan-51
M1142000 Elevators M1140000 Other Item 1-Jan-51
M1143000 Escalators and Moving Walks M1140000 Other Item 1-Jan-51
M1144000 Lifts M1140000 Other Item 1-Jan-51
M1147000 Turntables M1140000 Other Item 1-Jan-51
M1148000 Scaffolding M1140000 Other Item 1-Jan-51
Other Conveying Equipment (Facility chutes,
M1149000 Pneumatic Tube, Slide pole systems etc..) M1140000 Other Item 1-Jan-51
M1211300 Sprinkler Systems M1210000 Other Item 1-Jan-51
M1211310 Fire Hose Reel M1210000 Other Item 1-Jan-51
M1211320 Cabinets for fire fighting work M1210000 Other Item 1-Jan-51
M1211330 valves M1210000 Other Item 1-Jan-51
M1211340 Pipes M1210000 Other Item 1-Jan-51
M1211350 Breeching Inlet M1210000 Other Item 1-Jan-51
M1211360 Fire Fighting Consumables M1210000 Other Item 1-Jan-51
M1211370 Smoke Ventilation M1210000 Other Item 1-Jan-51
M1212000 Fire-Extinguishing Systems M1210000 Other Item 1-Jan-51
M1213000 Fire Pumps M1210000 Other Item 1-Jan-51
M1214000 Fire-Suppression Water Storage M1210000 Other Item 1-Jan-51
M1220513 Man Holes/ Covers M1220000 Other Item 1-Jan-51
M1221103 PVC Pipes M1220000 Other Item 1-Jan-51
M1221106 UPVC Pipes M1220000 Other Item 1-Jan-51
M1221109 Slotted Pipe M1220000 Other Item 1-Jan-51
M1221113 PPR Pipe M1220000 Other Item 1-Jan-51
M1221116 Insulated Pipe M1220000 Other Item 1-Jan-51
M1221119 Water Meter M1220000 Other Item 1-Jan-51
M1221123 Water Pumps M1220000 Other Item 1-Jan-51
M1221126 Plumbing fittings M1220000 Other Item 1-Jan-51
M1221129 Gratings M1220000 Other Item 1-Jan-51
M1221133 Concrete Pipe M1220000 Other Item 1-Jan-51
M1221136 GRP Pipe M1220000 Other Item 1-Jan-51
M1221139 Cast Iron Pipe M1220000 Other Item 1-Jan-51
M1221143 Water Tanks M1220000 Other Item 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 177


BP.080-Future Business Process

M1221146 Drains M1220000 Other Item 1-Jan-51


M1221149 Other Sewage pipes M1220000 Other Item 1-Jan-51
M1221210 Septic Tanks M1220000 Other Item 1-Jan-51
M1221410 Rain Water Drainage M1220000 Other Item 1-Jan-51
M1223010 Water Heaters M1220000 Other Item 1-Jan-51
M1224000 Plumbing Fixtures M1220000 Other Item 1-Jan-51
M1224800 Plumbing Accessories M1220000 Other Item 1-Jan-51
M1225000 Pool and Fountain Plumbing Systems M1220000 Other Item 1-Jan-51
Gas and Vacuum Systems for Laboratory and
M1226000 Healthcare Facilities M1220000 Other Item 1-Jan-51
M1232010 HVAC Piping M1230000 Other Item 1-Jan-51
M1232020 HVAC Pumps M1230000 Other Item 1-Jan-51
M1233100 HVAC Duct and Casings M1230000 Other Item 1-Jan-51
M1233300 HVAC Accessories M1230000 Other Item 1-Jan-51
M1233400 HVAC Fans M1230000 Other Item 1-Jan-51
M1234000 HVAC Air Cleaning Devices M1230000 Other Item 1-Jan-51
M1235000 Central Heating Equipment M1230000 Other Item 1-Jan-51
M1236000 Central Cooling Equipment M1230000 Other Item 1-Jan-51
M1238000 Decentralized HVAC Equipment M1230000 Other Item 1-Jan-51
M1238500 Thermostat M1230000 Other Item 1-Jan-51
M1251000 Integrated Automation Network Equipment M1250000 Other Item 1-Jan-51
Integrated Automation Instrumentation and
M1253000 Terminal Devices M1250000 Other Item 1-Jan-51
M1255000 Integrated Automation Facility Controls M1250000 Other Item 1-Jan-51
M1259000 Integrated Automation Control Sequences M1250000 Other Item 1-Jan-51
M1260110 Earthing & Accessories M1260000 Other Item 1-Jan-51
Cable Tray, Trunking, Conduits, Ducts & Cable
M1260500 ladders Accessories M1260000 Other Item 1-Jan-51
M1260510 Multi Core Cables M1260000 Other Item 1-Jan-51
M1260520 Single Core Cables M1260000 Other Item 1-Jan-51
M1260600 Switchboards and Panelboards M1260000 Other Item 1-Jan-51
M1261000 Medium-Voltage Electrical Distribution M1260000 Other Item 1-Jan-51
M1262000 Low-Voltage Electrical Transmission M1260000 Other Item 1-Jan-51
M1262410 Switch & Sockets M1260000 Other Item 1-Jan-51
M1262420 Isolators M1260000 Other Item 1-Jan-51
Facility Electrical Power Generating and Storing
M1263000 Equipment M1260000 Other Item 1-Jan-51
M1264100 Facility Lightning Protection M1260000 Other Item 1-Jan-51
M1265000 Light Fittings & Accessories M1260000 Other Item 1-Jan-51
M1265200 Emergency light M1260000 Other Item 1-Jan-51
M1265300 Exit Signs M1260000 Other Item 1-Jan-51
M1265600 Exterior Lighting M1260000 Other Item 1-Jan-51
M1271000 Structured Cabling M1270000 Other Item 1-Jan-51
M1272000 Data Communications M1270000 Other Item 1-Jan-51
M1273000 Voice Communications M1270000 Other Item 1-Jan-51
M1274100 Audio-Video Systems M1270000 Other Item 1-Jan-51
Distributed Communications and Monitoring
M1275000 Systems M1270000 Other Item 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 178


BP.080-Future Business Process

M1275100 Public Addressing System M1270000 Other Item 1-Jan-51


M1281110 BMS System M1280000 Other Item 1-Jan-51
M1281300 Low Current System M1280000 Other Item 1-Jan-51
M1282300 Video Surveillance M1280000 Other Item 1-Jan-51
M1283100 Fire Detection and Alarm M1280000 Other Item 1-Jan-51
M2311000 Site Clearing M1310000 Other Item 1-Jan-51
M1312300 Fill M1310000 Other Item 1-Jan-51
M1313100 Soil Treatment M1310000 Other Item 1-Jan-51
M1314000 Shoring and Underpinning M1310000 Other Item 1-Jan-51
M1315000 Excavation Support and Protection M1310000 Other Item 1-Jan-51
M1316000 Special Foundations and Load-Bearing Elements M1310000 Other Item 1-Jan-51
M1317000 Tunneling and Mining M1310000 Other Item 1-Jan-51
M1321000 Bases, Ballasts, and Paving M1320000 Other Item 1-Jan-51
M1321100 Base Courses M1320000 Other Item 1-Jan-51
M1321600 Curbs, Gutters, Sidewalks, and Driveways M1320000 Other Item 1-Jan-51
M1321700 Humps M1320000 Other Item 1-Jan-51
M1323000 Site Improvements M1320000 Other Item 1-Jan-51
M1327000 Wetlands M1320000 Other Item 1-Jan-51
M1328000 Irrigation M1320000 Other Item 1-Jan-51
M1329000 Planting M1320000 Other Item 1-Jan-51
M1330000 Utilities M1330000 Other Item 1-Jan-51
M1340000 Transportation M1340000 Other Item 1-Jan-51
M1350000 Waterway and Marine Construction M1350000 Other Item 1-Jan-51
M1401110 Gas Piping and Duct Works M1400000 Other Item 1-Jan-51
M1401120 Control System Equipment Panels and Racks M1400000 Other Item 1-Jan-51
M1401130 Bulk Material s Valves M1400000 Other Item 1-Jan-51
M1410000 Material processing and handling equipment M1410000 Other Item 1-Jan-51
M1420000 Process heating, cooling, and drying equipment M1420000 Other Item 1-Jan-51
Process gas and liquid handling, purification,
M1430000 and storage equipment M1430000 Other Item 1-Jan-51
M1440000 Pollution and waste control equipment M1440000 Other Item 1-Jan-51
M1450000 Industry specific manufacturing equipment M1450000 Other Item 1-Jan-51
M1460000 Water and waste water equipment M1460000 Other Item 1-Jan-51
M1480000 Electrical power generation M1480000 Other Item 1-Jan-51
G3011130 Office Rental Facilities G3010000 Other 1-Jan-51
G3011160 Rent Expenses G3010000 Other 1-Jan-51
G3021130 Temporary Shelter G3020000 Other 1-Jan-51
G3021160 Temporary Car Park Shed G3020000 Other 1-Jan-51
G3021190 Temporary Gates/Barriers G3020000 Other 1-Jan-51
G3021230 Temporary fencing G3020000 Other 1-Jan-51
G3021260 Temporary Access & Stairs G3020000 Other 1-Jan-51
G3021290 Garbage Chute G3020000 Other 1-Jan-51
G3021330 Demobilization G3020000 Other 1-Jan-51
G3031130 Water temporary Connection Network G3030000 Other 1-Jan-51
G3031160 Sewerage temporary Connection Network G3030000 Other 1-Jan-51
G3031190 Electricity temporary Connection Network G3030000 Other 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 179


BP.080-Future Business Process

G3031230 Telephone, Internet & Fax line Networks G3030000 Other 1-Jan-51
G3041130 Furniture G3040000 Other 1-Jan-51
G3051130 Air Conditioners G3050000 Other 1-Jan-51
G3051160 Computer Hardware G3050000 Other 1-Jan-51
G4051190 Computer Software G3050000 Other 1-Jan-51
G3051230 Telephone & Fax machine G3050000 Other 1-Jan-51
G3051260 Mobile Communication Devices G3050000 Other 1-Jan-51
G3051290 Kitchen Equipments & Accessories G3050000 Other 1-Jan-51
G3051330 Water Tank G3050000 Other 1-Jan-51
G3061130 Sign Boards G3060000 Other 1-Jan-51
G3061160 Temporary Project Signage G3060000 Other 1-Jan-51
G4071130 Telephone, Internet & Fax Line Charges G4070000 Other 1-Jan-51
G4071160 Mobile Phone Charges G4070000 Other 1-Jan-51
G4081130 Water Consumption Charges G4080000 Other 1-Jan-51
G4091130 Electricity Consumption Charges G4090000 Other 1-Jan-51
G4101130 Drainage Charges G4100000 Other 1-Jan-51
G4101160 Garbage Disposal G4100000 Other 1-Jan-51
G4111130 IT Spare Parts & Consumables G4110000 Other 1-Jan-51
G4111160 Kitchen & Pantry Consumables G4110000 Other 1-Jan-51
G4111190 House Keeping Consumables G4110000 Other 1-Jan-51
G4121130 Stationery Expenses G4120000 Other 1-Jan-51
G4121160 Emergency Medical Expenses G4120000 Other 1-Jan-51
G4121190 Entertainment Expenses G4120000 Other 1-Jan-51
G4121230 Photograph Expenses G4120000 Other 1-Jan-51
G4121260 Oil G4120000 Other 1-Jan-51
G4121290 Fuel G4120000 Other 1-Jan-51
G4121330 Courier Expenses G4120000 Other 1-Jan-51
G4121360 Gifts G4120000 Other 1-Jan-51
G4121390 Training Expenses G4120000 Other 1-Jan-51
G4121430 Food Expenses G4120000 Other 1-Jan-51
G4131130 Safety Helmet G4130000 Other 1-Jan-51
G4131160 Safety Shoes G4130000 Other 1-Jan-51
G4131190 Goggles G4130000 Other 1-Jan-51
G4131230 Gloves G4130000 Other 1-Jan-51
G4131260 Jacket G4130000 Other 1-Jan-51
G4131290 Coverall G4130000 Other 1-Jan-51
G4131330 Gum Boots G4130000 Other 1-Jan-51
G4131360 Safety Harness G4130000 Other 1-Jan-51
G4131390 Ear Plug G4130000 Other 1-Jan-51
G4131430 Uniform G4130000 Other 1-Jan-51
G4131460 Dust Mask G4130000 Other 1-Jan-51
G4141130 Safety Net G4140000 Other 1-Jan-51
G4151130 First Aid Box G4150000 Other 1-Jan-51
G4151160 First Aid Medicine G4150000 Other 1-Jan-51
G4161130 Traffic Cone G4160000 Other 1-Jan-51
G4161160 Barrication Tape G4160000 Other 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 180


BP.080-Future Business Process

G4161190 Safety Sign & Sticker G4160000 Other 1-Jan-51


G4161230 Safety Light G4160000 Other 1-Jan-51
G4161260 Fire Extinguisher G4160000 Other 1-Jan-51
G4161290 Fire Alarms G4160000 Other 1-Jan-51
G4161330 Razor Wire G4160000 Other 1-Jan-51
G4161360 Warning Lights G4160000 Other 1-Jan-51
G4161390 Temporary Oxygen & acetylene Gas G4160000 Other 1-Jan-51
G4161430 Rubber Strip Traffic Control G4160000 Other 1-Jan-51
G4161460 Fire Blanket G4160000 Other 1-Jan-51
G4161490 Safety Barriers G4160000 Other 1-Jan-51
G4174100 Regulatory Requirments G4170000 Other 1-Jan-51
G4174200 References G4170000 Other 1-Jan-51
Quality Assurance ( Mockups, Field Samples
G4174300 etc..,) G4170000 Other 1-Jan-51
G4174500 Quality Control ( Lab Testing etc.., ) G4170000 Other 1-Jan-51
G4181130 Performance Bond G4180000 Other 1-Jan-51
G4181160 Advance Payment Bond G4180000 Other 1-Jan-51
G4181190 Retention Guarantee Bond G4180000 Other 1-Jan-51
G4191130 Contractors All Risk Insurance G4190000 Other 1-Jan-51
G4191160 Plant & Equipment Insurance G4190000 Other 1-Jan-51
G4191190 Professional Indemnity for Design Insurance G4190000 Other 1-Jan-51
G4191230 Workmanship Compensation Insurance G4190000 Other 1-Jan-51
G4191260 On Road Third Party Liability Insurance G4190000 Other 1-Jan-51
G4201130 Building Permit Fees G4200000 Other 1-Jan-51
G4201160 Utility Connection Fees G4200000 Other 1-Jan-51
G4201190 Temporary Deposits for NOC G4200000 Other 1-Jan-51
G4201230 Temporary Structure Permit G4200000 Other 1-Jan-51
G4201260 Marketing Fees G4200000 Other 1-Jan-51
G4201290 Interest Paid or received G4200000 Other 1-Jan-51
G4201330 Fines G4200000 Other 1-Jan-51
G4201360 Bank & Finance Charges G4200000 Other 1-Jan-51
G4201390 Government Fees G4200000 Other 1-Jan-51
G4201430 Certification Charges G4200000 Other 1-Jan-51
G4211130 Top Management G4210000 Other 1-Jan-51
G4211160 Accounts and Finance Department G4210000 Other 1-Jan-51
G4211190 Contracts and Commercial Department G4210000 Other 1-Jan-51
G4211230 Document Control G4210000 Other 1-Jan-51
G4211260 Formwork and Scaffolding Department G4210000 Other 1-Jan-51
G4211290 Human Resources Department G4210000 Other 1-Jan-51
G4211330 Information Technology Department G4210000 Other 1-Jan-51
G4211360 Internal Auditing Department G4210000 Other 1-Jan-51
G4211390 Labour Resource Department G4210000 Other 1-Jan-51
G4211430 Operations Department G4210000 Other 1-Jan-51
G4211460 Planning Department G4210000 Other 1-Jan-51
G4211490 PMV Department G4210000 Other 1-Jan-51
G4211530 Procurement Department G4210000 Other 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 181


BP.080-Future Business Process

G4211560 SHEQ Department G4210000 Other 1-Jan-51


G4211590 Technical and Engineering Department G4210000 Other 1-Jan-51
G4211630 Cost Control Department G4210000 Other 1-Jan-51
G4211660 Maintenance Department G4210000 Other 1-Jan-51
G4211690 MEP Department G4210000 Other 1-Jan-51
G4221130 Immigration Expense G4220000 Other 1-Jan-51
G4221160 Communocation Allowance G4220000 Other 1-Jan-51
G4221190 Training Expenses G4220000 Other 1-Jan-51
G4221230 Leave Salary G4220000 Other 1-Jan-51
G4221260 End of Service Benefits G4220000 Other 1-Jan-51
G4221290 Air Ticket G4220000 Other 1-Jan-51
G4221330 Transporatation Allowance G4220000 Other 1-Jan-51
G4221360 Medical Insurance Allowance G4220000 Other 1-Jan-51
G4221390 Bonus / Incentive G4220000 Other 1-Jan-51
G4221430 Education Allowance G4220000 Other 1-Jan-51
G4221460 Housing Allowance G4220000 Other 1-Jan-51
E1021130 Dozer E1020000 Other 1-Jan-51
E1021160 Articulate Dump Truck E1020000 Other 1-Jan-51
E1021190 Excavator E1020000 Other 1-Jan-51
E1021230 Shovel E1020000 Other 1-Jan-51
E1021260 Roller E1020000 Other 1-Jan-51
E1021290 Asphalt Spreader E1020000 Other 1-Jan-51
E1021330 Wheel Loader E1020000 Other 1-Jan-51
E1021360 Backhoe Loader E1020000 Other 1-Jan-51
E1021390 Dumper E1020000 Other 1-Jan-51
E1021430 Farm Tractor E1020000 Other 1-Jan-51
E1021460 Skid Loader E1020000 Other 1-Jan-51
E1021830 Rolling Machine E1020000 Other 1-Jan-51
E1031160 Compactor E1030000 Other 1-Jan-51
E1031260 Concrete Mixer/Mortar Mixer E1030000 Other 1-Jan-51
E1031290 Augers & Bores, Vibro hammers E1030000 Other 1-Jan-51
E1031330 Breakers E1030000 Other 1-Jan-51
E1031360 Cutting Machine E1030000 Other 1-Jan-51
E1031390 Dewatering Machine E1030000 Other 1-Jan-51
E1031430 Power Float E1030000 Other 1-Jan-51
E1031490 Coring Machine E1030000 Other 1-Jan-51
E1031530 Chasing Machine E1030000 Other 1-Jan-51
E1031560 Shearing Machine E1030000 Other 1-Jan-51
E1031590 Folding Machine E1030000 Other 1-Jan-51
E1031630 Hydraulic Press E1030000 Other 1-Jan-51
E1031660 Lock Former E1030000 Other 1-Jan-51
E1031690 Concrete Spraying Machine E1030000 Other 1-Jan-51
E1031730 Scabbler E1030000 Other 1-Jan-51
E1031760 Scarifier E1030000 Other 1-Jan-51
E1031790 Scrubber Drier E1030000 Other 1-Jan-51
E1031830 Shotcrete Machine E1030000 Other 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 182


BP.080-Future Business Process

E1031860 Concrete Vibrator E1030000 Other 1-Jan-51


E1031960 Grinding Machine E1030000 Other 1-Jan-51
E1031990 Saw E1030000 Other 1-Jan-51
E1032130 Drilling Machine E1030000 Other 1-Jan-51
E1032160 Angle Grinder E1030000 Other 1-Jan-51
E1032190 Jig Saw Machine E1030000 Other 1-Jan-51
E1032230 Welding Machine E1030000 Other 1-Jan-51
E1032260 Plaster Machine & Accessories E1030000 Other 1-Jan-51
E1032360 Impact Wrench E1030000 Other 1-Jan-51
E1032390 Planers E1030000 Other 1-Jan-51
E1032430 Sanders E1030000 Other 1-Jan-51
E1032460 Router Plunge E1030000 Other 1-Jan-51
E1032490 Air Blower E1030000 Other 1-Jan-51
E1032530 Heat Gun E1030000 Other 1-Jan-51
E1032560 Rush Machine E1030000 Other 1-Jan-51
E4011130 Containers E4010000 Other 1-Jan-51
E4021490 Forklift E4010000 Other 1-Jan-51
E4021530 Man Lift E4010000 Other 1-Jan-51
E4021560 Boom Truck E4010000 Other 1-Jan-51
E4021590 Scissor Lift E4010000 Other 1-Jan-51
E4021630 Telehandler E4010000 Other 1-Jan-51
E4021660 Tower Crane E4010000 Other 1-Jan-51
E4021690 Mobile Crane E4010000 Other 1-Jan-51
E4021730 Crawler Crane E4010000 Other 1-Jan-51
E4021760 Winch Crane E4010000 Other 1-Jan-51
E4021790 Material Hoist E4010000 Other 1-Jan-51
E4021860 Chiller E4010000 Other 1-Jan-51
E4031130 Air Compressor E4010000 Other 1-Jan-51
E4031190 Generators E4010000 Other 1-Jan-51
E4031230 Water Pump E4010000 Other 1-Jan-51
E4031460 Tower Light E4010000 Other 1-Jan-51
E4031890 Bar Bending Machine E4010000 Other 1-Jan-51
E4031930 Bar Cutting Machine E4010000 Other 1-Jan-51
E4032290 Lab Equipments E4010000 Other 1-Jan-51
E4032330 Laboratory Tools E4010000 Other 1-Jan-51
E4032590 Pressure Testing Pump E4010000 Other 1-Jan-51
E4032630 Vices E4010000 Other 1-Jan-51
E4032660 Crane Accessories E4010000 Other 1-Jan-51
E4032690 Chain Pulley E4010000 Other 1-Jan-51
E4032730 Equipment -Spares, Repairs & Maintenance E4010000 Other 1-Jan-51
E4041130 Flat Bed E4040000 Other 1-Jan-51
E4041160 Low Bed E4040000 Other 1-Jan-51
E4041190 Tipper Truck E4040000 Other 1-Jan-51
E4041230 Tractor Head Trailer E4040000 Other 1-Jan-51
E4041260 Bus E4040000 Other 1-Jan-51
E4041290 Sewage Tanker E4040000 Other 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 183


BP.080-Future Business Process

E4041330 Water Tanker E4040000 Other 1-Jan-51


E4041360 Diesel Tanker E4040000 Other 1-Jan-51
E4041390 Recovery Truck E4040000 Other 1-Jan-51
E4051130 Car E4050000 Other 1-Jan-51
E4051160 Van E4050000 Other 1-Jan-51
E4051190 Pickup- Double cabins E4050000 Other 1-Jan-51
E4061130 Total Station E4060000 Other 1-Jan-51
E4061160 Auto Level E4060000 Other 1-Jan-51
E4061190 Theodolite E4060000 Other 1-Jan-51
E4061230 GPS Units E4060000 Other 1-Jan-51
E4061260 Digital Gauges E4060000 Other 1-Jan-51
E4061290 Digital Level E4060000 Other 1-Jan-51
E4061330 Laser Level E4060000 Other 1-Jan-51
E4061360 Surveying Equipment - Sundries E4060000 Other 1-Jan-51
E2071130 Wall System E1070000 Other 1-Jan-51
E2071160 Column System E1070000 Other 1-Jan-51
E2071190 Slab System E1070000 Other 1-Jan-51
E2071230 Wall System - Panel System E1070000 Other 1-Jan-51
E2071260 Core Wall System - ACS H20 + Steel Waler E1070000 Other 1-Jan-51
E2071290 Columns System - Universal Panels E1070000 Other 1-Jan-51
E2071330 Wall System - Waler + H20 E1070000 Other 1-Jan-51
E2071360 Columns System - Waler + H20 E1070000 Other 1-Jan-51
E2071390 Single sided Walls System - H20 + Steel Waler E1070000 Other 1-Jan-51
E2071430 Core Wall System - CCS H20 + Steel Waler E1070000 Other 1-Jan-51
E2071460 Slab System - Shoring System + H20 E1070000 Other 1-Jan-51
Slab System - Table System / FSD Slab System
E2071490 Flex System E1070000 Other 1-Jan-51
Slab System - Table System / FSD Slab System
E2071530 Flex System E1070000 Other 1-Jan-51
E2071560 Slab System - Cuplock + H20 E1070000 Other 1-Jan-51
E2071590 Alum Mobile Tower / Stair Tower E1070000 Other 1-Jan-51
E2071630 Edge Protection (Rapid EPS) E1070000 Other 1-Jan-51
E4071230 Access Scaffolding & Towers E1070000 Other 1-Jan-51
Assessment (Surveys, environmental &
S2022000 hazardous material assessments) S1020000 Other 1-Jan-51
S2023000 Subsurface Investigation S1020000 Other 1-Jan-51
S2024000 Demolition and Structure Moving S1020000 Other 1-Jan-51
S2025000 Site Remediation (Decontamination) S1020000 Other 1-Jan-51
S2026000 Contaminated Site Material Removal S1020000 Other 1-Jan-51
S2027000 Water Remediation S1020000 Other 1-Jan-51
S2028000 Facility Remediation S1020000 Other 1-Jan-51
S2031100 Concrete Forming S1030000 Other 1-Jan-51
S1032100 Concrete Reinforcing S1030000 Other 1-Jan-51
S1032300 Stressed Tendon Reinforcing S1030000 Other 1-Jan-51
S1033100 Cast-in-Place Concrete S1030000 Other 1-Jan-51
S1033500 Concrete finishing S1030000 Other 1-Jan-51
S1033700 Specialty Placed Concrete S1030000 Other 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 184


BP.080-Future Business Process

S1034100 Precast Concrete S1030000 Other 1-Jan-51


S1034900 GRC Work S1030000 Other 1-Jan-51
S1035000 Cast Decks and Underlayment S1030000 Other 1-Jan-51
S1036000 Grouting S1030000 Other 1-Jan-51
S1037000 Mass Concrete S1030000 Other 1-Jan-51
S1038000 Concrete Cutting and Boring S1030000 Other 1-Jan-51
S1042000 Unit Masonry S1040000 Other 1-Jan-51
S1042100 Clay Unit Masonry S1040000 Other 1-Jan-51
S1042200 Concrete Unit Masonry S1040000 Other 1-Jan-51
S1044000 Stone Assemblies S1040000 Other 1-Jan-51
S1045000 Refractory Masonry S1040000 Other 1-Jan-51
S1046000 Corrosion-Resistant Masonry S1040000 Other 1-Jan-51
S1047000 Manufactured Masonry S1040000 Other 1-Jan-51
S1048000 Plastering S1040000 Other 1-Jan-51
S1051200 Structural Steel Framing S1050000 Other 1-Jan-51
S1051600 Structural Cabling S1050000 Other 1-Jan-51
S1052000 Metal Joists S1050000 Other 1-Jan-51
S1053000 Metal Decking S1050000 Other 1-Jan-51
S1054100 Structural Metal Stud Framing S1050000 Other 1-Jan-51
S1055000 Metal Fabrications S1050000 Other 1-Jan-51
S1057000 Decorative Metal S1050000 Other 1-Jan-51
S1061000 Rough Carpentry S1060000 Other 1-Jan-51
S1062000 Finish Carpentry S1060000 Other 1-Jan-51
S1064000 Architectural Woodwork S1060000 Other 1-Jan-51
S1065000 Structural Plastics S1060000 Other 1-Jan-51
S1066000 Plastic Fabrications S1060000 Other 1-Jan-51
S1067000 Structural Composites S1060000 Other 1-Jan-51
S1068000 Composite Fabrications S1060000 Other 1-Jan-51
S1071000 Dampproofing and Waterproofing S1070000 Other 1-Jan-51
S1072000 Thermal Protection S1070000 Other 1-Jan-51
S1073000 Steep Slope Roofing S1070000 Other 1-Jan-51
S1074000 Roofing and Siding Panels S1070000 Other 1-Jan-51
S1075000 Membrane Roofing S1070000 Other 1-Jan-51
S1076000 Flashing and Sheet Metal S1070000 Other 1-Jan-51
S1077000 Roof and Wall Specialties and Accessories S1070000 Other 1-Jan-51
S1078000 Fire and Smoke Protection S1070000 Other 1-Jan-51
S1079000 Joint Protection S1070000 Other 1-Jan-51
S1081100 Doors and Frames S1080000 Other 1-Jan-51
S1083000 Specialty Doors and Frames S1080000 Other 1-Jan-51
S1084000 Entrances, Storefronts, and Curtain Walls S1080000 Other 1-Jan-51
S1085000 Windows S1080000 Other 1-Jan-51
S1086200 Unit Skylights S1080000 Other 1-Jan-51
S1087000 Hardware S1080000 Other 1-Jan-51
S1088000 Glazing S1080000 Other 1-Jan-51
S1089000 Louvers and Vents S1080000 Other 1-Jan-51
S1092100 Gypsum board assemblies S1090000 Other 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 185


BP.080-Future Business Process

S1092700 GRG Works S1090000 Other 1-Jan-51


S1093000 Tiling S1090000 Other 1-Jan-51
S1095000 Ceilings S1090000 Other 1-Jan-51
S1096200 Specialty Flooring S1090000 Other 1-Jan-51
S1096400 Wood Flooring S1090000 Other 1-Jan-51
S1096500 Raised Flooring S1090000 Other 1-Jan-51
S1097000 Wall Finishes S1090000 Other 1-Jan-51
S1098000 Acoustic Treatment S1090000 Other 1-Jan-51
S1099100 Painting S1090000 Other 1-Jan-51
S1099400 Decorative Finishing S1090000 Other 1-Jan-51
S1099600 High Performance Coatings (Epoxy Coating etc..) S1090000 Other 1-Jan-51
S1101400 Signage, Road Marking and Accessories S1100000 Other 1-Jan-51
S1102100 Compartments and Cubicles S1100000 Other 1-Jan-51
S1103000 Fireplaces and Stoves S1100000 Other 1-Jan-51
Safety Specialties (Emergency Aid, Fire
S1104000 Protection, etc..) S1100000 Other 1-Jan-51
Storage Specialties (Lockers, Post boxes, Closets,
S1105000 Shelving, etc..) S1100000 Other 1-Jan-51
Exterior Specialties (Sun screens, Canopies, Car
S1107000 shelters, Flagpoles, etc..) S1100000 Other 1-Jan-51
Other Specialties (Pest control devices, grilles,
Flags and banners, Gas lighting, Security mirrors,
S1108000 etc..) S1100000 Other 1-Jan-51
S1111300 Loading Dock Equipment S1110000 Other 1-Jan-51
S1112100 Service Equipment S1110000 Other 1-Jan-51
S1113200 Unit Kitchens S1110000 Other 1-Jan-51
Foodservice Equipment (Storage, Preparation,
Delivery carts, cooking and dispensing
S1114000 equipments) S1110000 Other 1-Jan-51
S1115000 Educational and Scientific Equipment S1110000 Other 1-Jan-51
S1116100 Theater Equipment S1110000 Other 1-Jan-51
S1116600 Athletic Equipment S1110000 Other 1-Jan-51
S1116800 Play Field Equipment S1110000 Other 1-Jan-51

S1117000 Healthcare Equipment S1110000 Other 1-Jan-51


S1118100 Facility Maintenance Equipment S1110000 Other 1-Jan-51
S1118200 Facility solid waste handling equipment S1110000 Other 1-Jan-51
Other Equipment (Religious, Agricultural,
S1119000 Horticultural, Arts and crafts equipment etc..) S1110000 Other 1-Jan-51
S1121000 Art S1120000 Other 1-Jan-51
S1122100 Window Blinds S1120000 Other 1-Jan-51
S1123000 Casework S1120000 Other 1-Jan-51
Furnishings and Accessories (Bath and bedroom
S1124000 linen & furnishings, rugs and mats etc..) S1120000 Other 1-Jan-51
S1125000 Furniture S1120000 Other 1-Jan-51
S1126000 Multiple Seating S1120000 Other 1-Jan-51
Other Furnishings (Interior planters and public
S1129000 space furnishings etc..) S1120000 Other 1-Jan-51
S1131100 Swimming Pools S1130000 Other 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 186


BP.080-Future Business Process

S1132100 Controlled Environment rooms S1130000 Other 1-Jan-51


S1132400 Special Activity Rooms S1130000 Other 1-Jan-51
S1133000 Special Structures S1130000 Other 1-Jan-51
Integrated Construction (Building modules,
sound, vibration control, radiation protection
S1134000 etc..) S1130000 Other 1-Jan-51
Special Instrumentation (Stress, Seismic,
S1135000 Meteorological Instrumentation etc..) S1130000 Other 1-Jan-51
S1141000 Dumbwaiters S1140000 Other 1-Jan-51
S1142000 Elevators S1140000 Other 1-Jan-51
S1143100 Escalators S1140000 Other 1-Jan-51
S1143200 Moving walks S1140000 Other 1-Jan-51
S1144000 Lifts S1140000 Other 1-Jan-51
S1147000 Turntables S1140000 Other 1-Jan-51
S1148000 Facility Chutes S1140000 Other 1-Jan-51
S1211300 Fire suppression sprinkler systems S1210000 Other 1-Jan-51
S1212000 Fire-Extinguishing Systems S1210000 Other 1-Jan-51
S1213000 Fire Pumps S1210000 Other 1-Jan-51
S1214000 Fire-Suppression Water Storage S1210000 Other 1-Jan-51
S1221000 Plumbing Piping S1220000 Other 1-Jan-51
S1223000 Plumbing Equipment S1220000 Other 1-Jan-51
S1224000 Plumbing Fixtures S1220000 Other 1-Jan-51
S1225000 Pool and Fountain Plumbing Systems S1220000 Other 1-Jan-51
Gas and Vacuum Systems for Laboratory and
S1226000 Healthcare Facilities S1220000 Other 1-Jan-51
S1231000 Facility Fuel Systems S1230000 Other 1-Jan-51
S1232000 HVAC Piping and Pumps S1230000 Other 1-Jan-51
S1233000 HVAC Air Distribution S1230000 Other 1-Jan-51
S1234000 HVAC Air Cleaning Devices S1230000 Other 1-Jan-51
S1235000 Central Heating Equipment S1230000 Other 1-Jan-51
S1236000 Central Cooling Equipment S1230000 Other 1-Jan-51
S1237000 Central HVAC Equipment S1230000 Other 1-Jan-51
S1238000 Decentralized HVAC Equipment S1230000 Other 1-Jan-51
S1251000 Integrated Automation Network Equipment S1250000 Other 1-Jan-51
Integrated Automation Instrumentation and
S1253000 Terminal Devices S1250000 Other 1-Jan-51
S1255000 Integrated Automation Facility Controls S1250000 Other 1-Jan-51
S1259000 Integrated Automation Control Sequences S1250000 Other 1-Jan-51
S1261000 High-Voltage Electrical Distribution S1260000 Other 1-Jan-51
S1262000 Medium-Voltage Electrical Distribution S1260000 Other 1-Jan-51
S1263000 Low-Voltage Electrical Transmission S1260000 Other 1-Jan-51
Facility Electrical Power Generating and Storing
S1264000 Equipment S1260000 Other 1-Jan-51
S1265000 Electrical Protection S1260000 Other 1-Jan-51
S1266000 Lighting S1260000 Other 1-Jan-51
S1271000 Structured Cabling S1270000 Other 1-Jan-51
S1272000 Data Communications S1270000 Other 1-Jan-51
S1273000 Voice Communications S1270000 Other 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 187


BP.080-Future Business Process

S1274000 Audio-Video Communications S1270000 Other 1-Jan-51


S1275100 Public Address System S1270000 Other 1-Jan-51
Electronic Access Control and Intrusion
S1281000 Detection S1280000 Other 1-Jan-51
S1282000 Electronic Surveillance S1280000 Other 1-Jan-51
S1283100 Fire Detection and Alarm S1280000 Other 1-Jan-51
S1284000 Electronic Monitoring and Control S1280000 Other 1-Jan-51
S2311000 Site Clearing S1310000 Other 1-Jan-51
S2312310 Excavation S1310000 Other 1-Jan-51
S1312320 Fill S1310000 Other 1-Jan-51
S2313100 Soil Treatment S1310000 Other 1-Jan-51
S2313200 Soil Stabilization S1310000 Other 1-Jan-51
S1314000 Shoring and Underpinning S1310000 Other 1-Jan-51
S1315000 Excavation Support and Protection S1310000 Other 1-Jan-51
S1316000 Special Foundations and Load-Bearing Elements S1310000 Other 1-Jan-51
S2317000 Tunneling and Mining S1310000 Other 1-Jan-51
S1321000 Bases, Ballasts, and Paving S1320000 Other 1-Jan-51
Paving Specialties (Speed bumps, pavement
S1321700 markings etc..) S1320000 Other 1-Jan-51
S1323100 Fences and Gates S1320000 Other 1-Jan-51
S1327000 Wetlands S1320000 Other 1-Jan-51
S1328000 Irrigation S1320000 Other 1-Jan-51
S1329000 Planting S1320000 Other 1-Jan-51
S1347100 Roadway Construction S1330000 Other 1-Jan-51
S1347300 Protective Covers S1330000 Other 1-Jan-51
S1347700 Transportation Equipment S1330000 Other 1-Jan-51
S1350000 Waterway and Marine Construction S1350000 Other 1-Jan-51
S1400000 Process Interconnections (LPG Works etc..) S1400000 Other 1-Jan-51
S1410000 Material processing and handling equipment S1410000 Other 1-Jan-51
S1420000 Process heating, cooling, and drying equipment S1420000 Other 1-Jan-51
Process gas and liquid handling, purification,
S1430000 and storage equipment S1430000 Other 1-Jan-51
S1440000 Pollution and waste control equipment S1440000 Other 1-Jan-51
S1450000 Industry specific manufacturing equipment S1450000 Other 1-Jan-51
S1460000 Water and wastewater equipment S1460000 Other 1-Jan-51

S1480000 Electrical power generation S1480000 Other 1-Jan-51


D3011130 Architectural Design D3010000 Other 1-Jan-51
D3011160 Structural Design D3010000 Other 1-Jan-51
D3011190 ID - Design D3010000 Other 1-Jan-51
D3011230 Landscaping Design D3010000 Other 1-Jan-51
D3011260 Shop Drawing Services D3010000 Other 1-Jan-51
D3011290 Commercial Services D3010000 Other 1-Jan-51
D3021130 Architectural Supervision D3020000 Other 1-Jan-51
D3021160 Structural Supervision D3020000 Other 1-Jan-51
D3021190 ID - Supervision D3020000 Other 1-Jan-51
D3021230 Landscaping Supervision D3020000 Other 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 188


BP.080-Future Business Process

D3030000 Project Management D3030000 Other 1-Jan-51


C0011130 Contract Provisional Sums C0010000 Other 1-Jan-51
C0011160 High Level Budget & Estimates C0010000 Other 1-Jan-51
C0011190 Project Maintenance C0010000 Other 1-Jan-51
C0011230 Management Contingency C0010000 Other 1-Jan-51
C0011260 Head Office Contingency C0010000 Other 1-Jan-51

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 189


BP.080-Future Business Process

Unit of Measures – ANNEXURE F


Unit of Measures

EFFECTIVE DATES

SR. NO UNIT MEANING DESCRIPION START DATE FINISH DATE

1 SHT SHEET SHEET 01-Jan-1951


2 NOS NUMBERS NUMBERS 01-Jan-1951
3 PKT PACKET PACKET 01-Jan-1951
4 PR PAIR PAIR 01-Jan-1951
5 SET SET SET 01-Jan-1951
6 DRM DRUM DRUM 01-Jan-1951
7 ROL ROLL ROLL 01-Jan-1951
8 MTR METER METER 01-Jan-1951
9 LS LUMPSUM LUMPSUM 01-Jan-1951
10 SQM SQ METER SQ METER 01-Jan-1951
11 CUM CUBIC METER CUBIC METER 01-Jan-1951

Note: Final List will be prepared based on Item Master provided by Inventory Key Users.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 190


BP.080-Future Business Process

G&A Details – ANNEXURE G

Equation
S.N.

A Staff Cost

A.0 Number of Labours

A.1 Number of Staff

A.2 Staff Gross Salaries

A.2.1 Staff Gross Salaries - Basic Sum of Basic per annum

A.2.2 Staff Gross Salaries - Accommodation Sum of HRA per annum

A.2.3 Staff Gross Salaries - Transportation Sum of TRP per annum

A.2.4 Staff Gross Salaries - Other Allowance Sum of OTH per annum

A.3 Staff CTC

A.3.01 Staff CTC - Air Tickets (Reg. Vac 2x) Sum of CTC Airticket per annum

Staff CTC - Air Tickets (EOS@10% 1x)

Staff CTC - Leave Encash @ 20% Est.)

Staff CTC -Annual Leave @ 10% Est.)

A.3.02 Staff CTC - Accum. EOS @ 10% Est. Sum of CTC Graduity per annum

A.3.03 Staff CTC - Visa & Immigration Sum of CTC Visa per annum

Sum of CTC Education Allowance per


A.3.04 Staff CTC - Education
annum

A.3.05 Staff CTC - Medical Insurance Sum of CTC Insurance per annum

Sum of CTC Housing Allowance per


A.3.06 Staff CTC - Housing Allowances
annum

Sum of CTC Communication per


A.3.07 Staff CTC - Mobile Allowance
annum

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 191


BP.080-Future Business Process

A.3.08 Staff CTC - WC Insurance 0.08 %

A.3.09 Staff CTC - Recruitment Sum of Recruitment Cost Per Annum

A.3.10 Staff CTC - Provision for Salary Increment 2%

A.4 Bonus

A.5 Training 2,000.00 QAR/Person/Year

A.6 HR Management Charges 51.28 QAR/Person/Month

Total Staff Cost

B Logistics

B.1 Motor Car Expenses

B.1.1 Motor Car Expenses - Fuel (Petrol)

B.1.2 Motor Car Expenses - Driver

B.1.3 Motor Car Expenses - Vehicle Rent

B.2 Office Space

B.2.1 Area

B.2.2 Office Rent 140.00 QR/Sqm/Month

B.2.3 Store Rent 15.00 QR/Sqm/Month

B.2.4 Electricity & Water Charges 10.00 QR/Sqm/Month

B.2.5 Portable Drinking Water 26.00 QR/Person/Month

B.2.6 Office Kitchen Exp. 100.00 QR/Person/Month

B.2.7 Main Office Repairing & Maintenance

Total Logistics

C Financial Requirements

C.1 Financing and Interest Charges

C.2 Professional Charges & Legal Charges

C.3 Zakat & Donations

C.4 Trade License Expenses

C.5 Depreciation

Total Financial Requirements

D IT Requirements

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 192


BP.080-Future Business Process

D.1 Software

D.1.1 ERP Users Number

D.1.2 ERP Cost 550.00 QAR/Person/Month

D.1.3 Work Station Charge 137.50 QAR/Person/Month

D.1.4 Special Software Costs Custom

D.2 Telephone, Fax & Internet Charges 100.00 QAR/Person/Month

D.3 Printing, Photocopying & Stationary 110.00 QAR/Person/Month

Depreciation / Amortization

Total IT Requirements

E Other Expenses

E.1 Travelling & Business Trips

E.2 Shipping Expenses

E.3 Entertainment 25.00 QAR/Person/Month

E.4 Tender Expenses

E.5 Marketing and Advertisement


E.6 Miscellaneous Expenses

Total Other Expenses

GRAND TOTAL

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 193


BP.080-Future Business Process

Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

1 Commitment Cost
Reallocation

Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

1 Project Numbering 9Digits UCC Cost Control


Structure
2 UCC BOQ auto import in Yes. UCC and WSD
WSD
3 Same Activity Master for Main Activity Master will be maintained UCC and WSD
UCC and WSD by UCC. WSD will maintain a child master
to maintain a rollup (WSD Specific) of the
Activities from Main Activity Master.
4 Orders below 500,000 are Light Order Process will be followed. Procurement and
not considered as Commercial
Subcontract Order
5 Material Should be returned Leftover material should be returned with Projects Cost Control
to stores with average cost Cost (Average Cost of System)
not with Zero cost
6 Customer billing Commercial &
Deductions Finance
7 Subcontract Billing Commercial &
Deductions Finance
8 PMV Process PMV
9 Finance would like to Cost control has agrred to reverse it every Finance and Cost
reverse all the accrual month Control
entries automatically in the
next month first date. Need
confirmation from UCC
Cost Control Department.

UCC_PA_BP080_FINAL UCC/NALSOFT - Confidential 194

Você também pode gostar