Beruflich Dokumente
Kultur Dokumente
1 Version control
Version Date Status Author Comments
0.1 14.06.2016 Draft Daniela Simon Initial Version
Content
1 Version control ................................................................................................................................. 1
2 General Information ......................................................................................................................... 2
3 Verification Criteria .......................................................................................................................... 2
4 Candidate for Change Description .................................................................................................. 5
5 Current Situation .............................................................................................................................. 6
6 Embedded Documents .................................................................................................................... 6
7 Impacts and reasons for change ..................................................................................................... 6
8 Evaluation & Response ................................................................................................................... 6
9 Change Request Description ........................................................................................................... 7
10 Official Offer ..................................................................................................................................... 8
11 Authorized signatures ...................................................................................................................... 9
1
Candidate for change | Change request form
2 General Information
Title: IntegrateStandardBasic_eTracking.doc
EMMA ID: eTCR-616918
Reference to: eTracking
iCAP Project / Stream(s): Handling / Quality Management Service
Requestor: LCAG
(LCAG, IBS, .) Daniela Simon F/IM-AH
First-/Last Name: Alex Mathai Varghese
Vendor: IBS
LCAG:
Date issued: 14.06.2016
Related to other change no.
Impact On Costs in T€: To be filled when the final agreement and sign-off is done
Impact On Project Plan: To be filled when the final agreement and sign-off is done
(high, medium, low, no)
3 Verification Criteria
Please specify and comment the demand for the CfC/CR in respect to the following
categories. The comment is essential to gain approval.
2
Candidate for change | Change request form
3. 3. CfC/CR cannot be shifted to a later point in time and/or release to reduce running cost
iCAP will not fund the CfC/CR!
YES Estimate the one time and recurring NO
The CfC/CR Owner has to clarify with business
cost for implementing the CfC/CR side to agree on a funding outside iCAP. Any
later in time (in a later release). funding by iCAP must be decided in an appropriate
Review Board (i.e. Domain RB or iCAP RB).
3. 4. CfC/CR has been thoroughly checked and discussed with vendor to identify all functions that are
part of the provider obligations (and thus not to be paid again).
iCAP will not fund the CfC/CR!
YES VM to approve explicitly. NO
The CfC/CR Owner has to clarify with business
side to agree on a funding outside iCAP. Any
funding by iCAP must be decided in an appropriate
Review Board (i.e. Domain RB or iCAP RB).
3. 5. CfC/CR has been thoroughly checked and discussed with vendor to reduce it to its absolute
minimum (to eliminate all not essential requirements).
iCAP will not fund the CfC/CR!
YES NO
The CfC/CR Owner has to clarify with business
side to agree on a funding outside iCAP. Any
funding by iCAP must be decided in an appropriate
Review Board (i.e. Domain RB or iCAP RB).
3
Candidate for change | Change request form
3. 9. CfC/CR is evaluated by vendor to be incorporated into the Standard Product. Thus, no recurring
costs (AMC) are claimed by vendor.
Involve iCAP Vendor Manager for negotiations.
Vendor has to explain, why the CR requested
YES VM to approve explicitly NO cannot be part of the Standard Product.
4
Candidate for change | Change request form
[X] Scope MP 6
[X] Formal iCAP Rel. 2016/5
[X] Time
[] Miscellaneous CfC616918_Integrat
eStandardBasic_eTracking.doc
5
Candidate for change | Change request form
5 Current Situation
Description of the current situation (as-is).
S No./Ref ID are from Requirement Matrix serial number and reference IDs to clarify the
activity changing further.
PSP-Code is from the Microsoft Project Plan for the master project plan for releases, MPs and
increments.
6 Embedded Documents
Additional supporting documents to be provided by the requestor, if any.
Could be requirement matrix, change log or project plan etc.
6
Candidate for change | Change request form
“Formal” is anything formally agreed between the parties before. S No. / Ref ID are from
Requirement Matrix serial number and reference IDs to clarify the activity changing further.
PSP-Code is from the Project Plan.
S No./Ref ID/
Description CC/
PSP-Code/
(especially describe product alignment (X, C, R) and CR/
Activity Name/ impact on maintenance) R
….
[] Scope There will be a new category of shipments
[] Formal based on the service code attached to the
[] Time shipments. Whenever a shipment is booked
with service code Z, these shipments are called
the standard basic shipments, then for such
shipments there will be a desired TOA and
desired LAT for such shipments. These desired
TOA and desired LAT will not get changed after
the initial booking. For such shipments with
service code Z, Order steering will pass on the
additional values <DESIREDTOA> and
<DESIREDLAT> through transportation plan.
7
Candidate for change | Change request form
S No./Ref ID/
Description CC/
PSP-Code/
(especially describe product alignment (X, C, R) and CR/
Activity Name/ impact on maintenance) R
….
be displayed based on the <DESIREDLAT>
value from the event trigger message.
2. The LAT / Latest Acceptance Time tab of the
shipment in the “Booking at Goods acceptance”
tab shall be displayed based on the
<DESIREDLAT> value from the event trigger
message.
3. If the shipment is not a standard basic
shipment, then the LAT/latest acceptance time
shall be displayed based on the updated LAT in
iCargo.
10 Official Offer
(LCAG will not fill this section, only vendors will fill this section)
8
Candidate for change | Change request form
Annual Maintenance per Effort / Costs Comment (i.e. refer to S No./Ref ID/
Item / ID PSP-Code/ Activity Name/ ….)
PD CC Requirement
PD
PD
Total effort (sum) 0 PD NA
Total Maintenance 0 T€
MP MP MP
Implementation effort CC [PD] 0 0 0
Implementation effort CR [PD] 0 0 0
Annual Maintenance CR-items [PD] 0 0 0
Dropped effort [PD] 0 0 0
< description whether the change has any impact on Milestones of Project Plan or any other
relevant activities >
11 Authorized signatures
___________________ __________________________________
Date Signature Initiator
(<Initiating Party>)
___________________ __________________________________
9
Candidate for change | Change request form
10