Project - Contract linking

POC Exercise
(20/04/2009)

© Tech Mahindra Limited 2008 Tech Mahindra Limited confidential

Overview.
 Project Contract Business Unit Structure.
 Solution for the points raised in earlier P1-C1
demo.
 Resource’s Billability Capturing.
 Project Contract Attributes.

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 2

Project-Contract BU Structure.
 Contract Business Units will be created based on the
segments of business., Eg: BT1CA, BT2CA, APCCA etc.
 Project Business Units will be in line with the contract
business units. E.g.: BT1PC, BT2PC, APCPC

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 3

Open Points Of earlier P1-C1 DEMO.
 How to map resources & the rates at the contract line level.

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 4

Proposed Solution.
 Resource Based Contract Lines:
 There will be activities defined in every project.
 Resources will be assigned to these activities, along with their
customer project roles.
 For every customer project role, the cost rate as well as billing
rate can be defined in the system.
 In addition to this, the rate sets will be defined in the system
which determine the source criteria for incoming data
(Spectrum data), and for each of these source criteria there can
be rates defined.
 Once the timesheet data is entered in the spectrum it will be
pulled in project costing module and for each resource, the
source criteria from rates sets will be matched and accordingly
cost & bill rates will be calculated.
 For these, there would be billing and cost transactions created
in PC which in turn will flow to billing module.

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 5

Proposed Solution (Contd…)
 Example:
 Suppose there is one activity called ‘Offshore’ defined for
project P1.
 The project & activity are linked to a contract line called
‘Offshore charges’.
 A resource R1 is working for the above activity in project P1
with a customer role as ‘Designer’.
 Assume he has filled the timesheet for the current month by
specifying details of regular work, OT and Weekend work.
 There is a cost rate & billing rate already defined for the role
‘Designer’. Also the rate set for offshore is also defined which
talks about the rates of the role ‘Designer’ for different
categories of work: Regular, Overtime and weekend. For each
of these category there will be different rates. Which means for
the category ‘Regular’ the rate will be Quantity * Billing rate of
a role ‘Designer’. And for others it can be 800 INR/MHR.

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 6

Proposed Solution (Contd…)

 Once this structure is established, and data is pulled from

spectrum to PC module, the system will calculate the actual
values based on these rate sets and create cost & billing
transactions in Project costing module.
 And this data will be further moved to Billing.
 Thus instead of mapping resources at the contract line level,
they will be mapped to project activities and project activities in
turn will be mapped to contract lines.
 Using this solution, we can get Project activity wise revenue as
well cost.

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 7

Proposed Solution (Contd…)
 Non-Resource Based Contract Lines:

 In case of non-resource based contract lines, there can be

activities defined in the project for each of them.
 Eg: There can be activities for non-resource based costs like
Hardware, Travel, Training, shift allowances.
 And these activities will be mapped to contract lines.
 In the system, through “Add Transactions” option the cost and
bill amounts can be captured and further moved to billing.

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 8

Proposed Solution (Contd…)
 Validations:

 For FP as well as T&M contracts there can be only one & unique
project-activity combination attached to every contract line.

 While creating a project, an attribute called ‘IDU’ is captured

and based on that the corresponding IDU head can be derived.
In the system, we are not explicitly capturing IDU head of a
project. It can be derived based on the IDU selected for the
project.

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 9

Capturing Resource’s Billability.

 Resource’s billability can be captured at the project activity

level.
 Authorized users can add the billability values for a certain
date range of resource’s current assignment.
 Major Validations:
 After the billing is completed for the particular billable
employee for a particular period, the billability record can’t be
changed/deleted.
 All the billability records of all the team members will not be
editable once the project closure is approved by finance.

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 10

Capturing Resource’s Billability.

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 11

Capturing Resource’s Billability.

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 12

Project & Contract Attributes.
 Project Attributes:
 Project Domain
 Project Sub-domain
 Functional Area
 COTS of the project
 Project Technology
 Percentage Applicability of a particular technology to a project.
 Primary Flag.

 Each Of these values will have valid lookup values.

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 13

Project & Contract Attributes.

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 14

Project & Contract Attributes.

 Contract Attributes:
 Customer PM
 Opportunity Name
 Owning IDU
 Pre Quote Reference
 LOB (Lin Of Business)
 OUC
 Customer Platform
 Customer Program
 Pipeline Ref. No.
 PR Number
 FP Contract Type
 PO Start & End Date
 Customer Ref. No
 CRGN

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 15

Project & Contract Attributes.

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 16

Thank You

08/25/24 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 17