Table 1.

CR Tracker
Customer Planned
YTD Program
S. No. Customer Name Programme Programme CR Project ID
EBITDA
Name EBITDA

# text text % % num

1 XYZ E2E 25% <to be created>

2 ABC OMD -83% <to be created>

3
4

<contains sample data>

A “Customer Programme” represents an SOW which has been signed with the customer, e.g. CRM Transformation,
This field is available at contract level in PACE.

Where there are multiple customers and/or program managers associated with a single programme, please still keep
Please ensure to reference the same Programme Name in all the related entries
 Program area in
CR Planned Mapped project Identified On
SBU which CR is
EBITDA ID Date
identified

% num text dd-mm-yy text

16578,
EMEA (Enterprise) +
C0400000001657 4/10/2018 Application MS
Europe Comms
8
16579,
EMEA (Enterprise) +
C0400000001657 4/9/2018 Application MS
Europe Comms
9

he customer, e.g. CRM Transformation, End to End Application Maintenance,ERP Transformation, End to End IT Outsourcing, etc.

th a single programme, please still keep a single CR project id mapped to the programme. However, pls include details of respective progra
 Scope of the CR Future Looking / Work Already Done

(description) dropdown

Additional tickets, to by invoiced to client Work Already Done

Additional tickets, to by invoiced to client Work Already Done

n, End to End IT Outsourcing, etc.

ver, pls include details of respective program managers and their programs in separate entries.
 Efforts PO Currency Amount of Client identified Amount of TechM
CR Activity Type
required Number of PO CR Identified CR

dropdown man days (in currency of PO) (in currency of PO)

Application MS 12345678 Euro 2,623,215 0

Application MS 45678901 Euro 394,820 0

Project Manager Project Manager Program Manager Program Manager

(Employee ID) (name) (Employee ID) (name)

97728 xxx 97728 Prasad,Tumul

97728 yyy 97728 Prasad,Tumul

 Approval attached from IBU
CDM CDM Any other contributor
Head

(Employee ID) (name) (Employee ID) (Y/N)

328633 vvv ?

328633 www ?
 MS

Approval attached from Approval attached from

Count of tickets Count of Apps
SBU Delivery Head Client

(Y/N) (Y/N) Contracted Value Actual Value Contracted Value

17247 25797 73

27039 35997 58
 MS L1/L2

Count of Apps Effort (PDs) Onsite/ offshore ratio Count of enhancements

Actual Value Contracted Value Actual Value Contracted Value Actual Value Contracted Value

64

50
 MS L3/L4 Dev/ Transform

Count of enhancements Effort for enhancements (PDs) Onsite/ offshore ratio Onsite/ offshore ratio

Actual Value Contracted Value Actual Value Contracted Value Actual Value Contracted Value
 Dev/ Transformation/ Implementation Testing

Onsite/ offshore ratio Count of Requirements / User Stories Count of TCs Onsite/ offshore ratio

Actual Value Contracted Value Actual Value Contracted Value Actual Value Contracted Value
Onsite/ offshore ratio

Actual Value
# Approving Party Attachment

1 IBU Head Approval

2 SBU Delivery Head Approval

3 Client SPOC Approval *

* Client approver to be CCGB final approver from client

 Approval Needed on

Details of CR with split of customer identified CRs and TechM identified CRs

Details of CR with split of customer identified CRs and TechM identified CRs

Details of CR with split of customer identified CRs and TechM identified CRs.
This includes:
- Signed CR document
- Email approval of split of TechM and Client identified portion of CR