Finding The EAP Requisition

Business BlueprintBusiness Blueprint CUSTOMER ACCESS PERMITTED
SAPHIR - SAP - Equipment FOR

CMA CGM AND AFFILIATES
Document Version: 0.1.091.0
Date: 3030. SeptemberJune 2014
Status: Sent for CMA CGM Approvedal
Asset ManagementAsset Management

CMA CGM GroupCMA CGM Group
Business Blueprint
SAPHIR - SAP - Equipment
Document History
Version Date Company Author/Editor Status Change Formatted Table
0.1 31. March 2014 SAP Bushra Khan Draft First draft
0.2 16. April 2014 SAP Bushra Khan Draft Second draft
0.3 05. June 2014 SAP Bushra Khan Draft Third draft
0.4 13. June 2014 SAP Bushra Khan Draft Fourth Draft including changes to:
7.5: Cross Process Related
Topics/Integration Points
8.10: Process Seals & Spare Parts
Procurement Management
(5.1.4.3.)
8.8 Maintenance & Recovery
Management
8.7. Lost & Found Management
Incorporated feedback from
Delivery B - various processes
KPIs Updated
No requirement updates Formatted: Indent: Left: 0.04", Hanging: 0.2", No bullets
or numbering
KPIs updated
Formatted: No bullets or numbering
0.5 13. June 2014 SAP Bushra Khan Draft Feedback from Delivery B incorporated.
0.6 20. June 2014 SAP Bushra Khan Draft Feedback from Delivery B incorporated.
0.7 23. June 2014 SAP Bushra Khan Draft Solution Mapping content added
0.8 26. June 2014 SAP Bushra Khan Draft Solution Mapping content added
CMA CGM Feedback incorporated
SAP Internal review
0.9 30. June 2014 SAP Bushra Khan, Sent for Quality check done
Mafy CMA CGM Content finalized
ANDRIANAVAH, Approval
Noelle COLLIAT
Formatted: Normal
Customer Access Permitted for

Asset ManagementAsset ManagementAsset ManagementAsset Management CMA CGM
0.1.091.01.00.9 - 30. September 201430. September 201430. June 2014 - ApprovedApprovedSent for CMA 2014 SAP AG or an SAP affiliate company. All rights reserved. 2014
CGM Approval SAP AG or an SAP affiliate company. All rights reserved. 2014 SAP
Document History AG or an SAP affiliate company. All rights reserved. 2
Business Blueprint
0.10 18. July 2014 SAP Bushra Khan, Sent for Quality check done
Mafy CMA CGM Content finalized based on BBP1 final
ANDRIANAVAH, Approval delivery feedback
Noelle COLLIAT
0.11 01. August 2014 SAP Bushra Khan, Sent for Content finalized based on v0.10
Mafy CMA CGM delivery feedback
Noelle COLLIAT
0.12 28. August 2014 SAP Bushra Khan, Sent for No changes
Mafy CMA CGM
Noelle COLLIAT
1.0 30. September SAP Bushra Khan, Approved Figure 55 updated

Mafy Final Version
ANDRIANAVAH,
Noelle COLLIAT
Formatted: English (United States)

Document History AG or an SAP affiliate company. All rights reserved. 3
Business Blueprint
Reviews/Approvals
Name Title Version Date Company Review / Approval

Status
Bastien REMANT DOLE BPO 0.9 30. June 2014 CMA CGM Approval
OpenApproval open
Bastien REMANT DOLE BPO 0.10 18. July 2014 CMA CGM Approval Open
Bastien REMANT DOLE BPO 0.11 01. August 2014 CMA CGM Approval Open
Bastien REMANT DOLE BPO 0.12 28. August 2014 CMA CGM Approved

Reviews/Approvals AG or an SAP affiliate company. All rights reserved. 4
Business Blueprint
Table of Contents
1 About This Document ........................................................................................................................................................ 97

1.1 Purpose and Scope ................................................................................................................................................. 108
1.2 Management/Executive Summary .......................................................................................................................... 109
1.3 Glossary................................................................................................................................................................. 1210
1.4 Related Documents ............................................................................................................................................... 1210
2 Solution Overview ......................................................................................................................................................... 1413
3 Assumptions and Constraints ......................................................................................................................................... 1918
4 Value Determination ...................................................................................................................................................... 2019

4.1 Major Business Pain Points (To Achieve Business Objective) ..................................................................................2019
4.2 Key Performance Indicators (KPIs) .........................................................................................................................2322
5 SAP Organizational Structure ........................................................................................................................................ 2927
6 Data Management .......................................................................................................................................................... 3028

6.1 Master Data Concept .............................................................................................................................................3028
6.2 Master Data Objects ..............................................................................................................................................3028
6.3 Master Data Requirements .................................................................................................................................... 3129
6.4 Migration Concept ................................................................................................................................................. 3633
7 Business Process Landscape .......................................................................................................................................... 3734

7.1 Business Area ........................................................................................................................................................ 3734
7.2 Business Area/Process Groups ............................................................................................................................... 3935
7.3 Equipment Asset Management Processes ............................................................................................................. 4036
7.4 Interface to Equipment Maintenance & Repair and Recovery Management Legacy Systems ................................. 4439
7.5 Cross Process Related Topics/Integration Points ................................................................................................... 4540
7.6 Event Management ...............................................................................................................................................4641
8 Business Process and Solution Design ........................................................................................................................... 5949

8.1 Process Equipment Master Data Management (5.1.1.1.) ........................................................................................ 5949
8.1.1 Process Description .............................................................................................................................. 5949
8.1.2 Business Process Diagrams................................................................................................................... 6050
8.1.3 Requirement List ................................................................................................................................... 6151
8.1.4 Process Step Detailed Requirements & Solution ................................................................................... 6252
8.2 Process Equipment Fleet Strategy Management (5.1.1.2.) ...................................................................................... 7972
8.2.1 Process Description ............................................................................................................................... 7972
8.2.2 Business Process Diagrams.................................................................................................................... 8073
8.2.4 Process Step Detailed Requirements & Solution .................................................................................... 8174
8.3 Process Owned Equipment Management (5.1.1.3.) .................................................................................................8679
8.3.1 Process Description ...............................................................................................................................8679
8.3.2 Business Process Diagrams....................................................................................................................8780

Table of Contents AG or an SAP affiliate company. All rights reserved. 5
Business Blueprint

8.3.4 Process Step Detailed Requirements & Solution ....................................................................................8881
8.4 Process Leased Equipment Management (5.1.1.4.) ............................................................................................. 128120
8.4.1 Process Description ........................................................................................................................... 128120
8.4.2 Business Process Diagrams................................................................................................................ 129121
8.4.3 Requirement List ............................................................................................................................... 130122
8.4.4 Process Step Detailed Requirements & Solution ................................................................................ 130122
8.5 Process Equipment Sub-Lease-From Management (5.1.1.5.) ...............................................................................161153
8.5.1 Process Description ............................................................................................................................161153
8.6 Process Equipment Sub-Lease-To Management (5.1.1.6.) .................................................................................. 182172
8.6.2 Business Process Diagrams................................................................................................................. 183173
8.6.4 Process Step Detailed Requirements & Solution .................................................................................185175
8.7 Process Lost and Found Equipment Management (5.1.1.7.) ................................................................................ 205197
8.7.2 Business Process Diagrams................................................................................................................206198
8.8 Process Maintenance & Repairs (MnR) Management (5.1.4.1.)............................................................................ 227217
8.9 Process Recovery Management (5.1.4.2.) ...........................................................................................................239229
8.9.1 Process Description ...........................................................................................................................239229
8.10 Process Seals and Spare Parts Procurement Management (5.1.4.3.) ................................................................... 251239
8.10.3 Requirement List ...............................................................................................................................252240
8.10.4 Process Step Detailed Requirements and Solution .............................................................................252240
9 Integrated Solution Management and Technical Solution Management .................................................................... 262250
10 Technical/Development Related Items ...................................................................................................................... 263251

10.1 Gaps .................................................................................................................................................................. 263251
10.2 Custom Development ........................................................................................................................................ 265253
1 About This Document ..........................................................................................................................................................7

1.1 Purpose and Scope ..................................................................................................................................................... 8
1.2 Management/Executive Summary .............................................................................................................................. 9
1.3 Glossary.................................................................................................................................................................... 10
1.4 Related Documents .................................................................................................................................................. 10

Business Blueprint
2 Solution Overview ............................................................................................................................................................. 12
3 Assumptions and Constraints ............................................................................................................................................. 17
4 Value Determination .......................................................................................................................................................... 18

4.1 Major Business Pain Points (To Achieve Business Objective) ..................................................................................... 18
4.2 Key Performance Indicators (KPIs) ............................................................................................................................ 18
5 SAP Organizational Structure ............................................................................................................................................ 23
6 Data Management .............................................................................................................................................................. 24

6.1 Master Data Concept ................................................................................................................................................ 24
6.2 Master Data Objects ................................................................................................................................................. 24
6.3 Master Data Requirements ....................................................................................................................................... 25
6.4 Migration Concept .................................................................................................................................................... 29
7 Business Process Landscape .............................................................................................................................................. 30

7.1 Business Area ........................................................................................................................................................... 30
7.2 Business Area/Process Groups ...................................................................................................................................31
7.3 Equipment Asset Management Processes ................................................................................................................. 32
7.4 Interface to Equipment Maintenance & Repair and Recovery Management Legacy Systems ..................................... 34
7.5 Cross Process Related Topics/Integration Points ....................................................................................................... 36
7.6 Event Management ................................................................................................................................................... 37
8 Business Process and Solution Design ............................................................................................................................... 42

8.1 Process Equipment Master Data Management (5.1.1.1.) ............................................................................................ 42
8.1.1 Process Description .................................................................................................................................. 42
8.1.2 Business Process Diagrams....................................................................................................................... 43
8.1.3 Requirement List ...................................................................................................................................... 44
8.1.4 Process Step Detailed Requirements & Solution ....................................................................................... 45
8.2 Process Equipment Fleet Strategy Management (5.1.1.2.) ......................................................................................... 60
8.3 Process Owned Equipment Management (5.1.1.3.) .................................................................................................... 68
8.4 Process Leased Equipment Management (5.1.1.4.) ................................................................................................... 107
8.4.1 Process Description ................................................................................................................................. 107
8.4.2 Business Process Diagrams..................................................................................................................... 108
8.4.3 Requirement List .................................................................................................................................... 109
8.4.4 Process Step Detailed Requirements & Solution ..................................................................................... 109
8.5 Process Equipment Sub-Lease-From Management (5.1.1.5.) .................................................................................... 141
8.5.3 Requirement List ..................................................................................................................................... 143

Business Blueprint
8.6 Process Equipment Sub-Lease-To Management (5.1.1.6.) ........................................................................................ 161

8.7 Process Lost and Found Equipment Management (5.1.1.7.) ......................................................................................185
8.7.1 Process Description .................................................................................................................................185
8.7.4 Process Step Detailed Requirements & Solution ...................................................................................... 187
8.8 Process Maintenance & Repairs (MnR) Management (5.1.4.1.)................................................................................. 206
8.8.1 Process Description ................................................................................................................................ 206
8.8.2 Business Process Diagrams......................................................................................................................207
8.8.3 Requirement List .....................................................................................................................................207
8.8.4 Process Step Detailed Requirements & Solution ...................................................................................... 213
8.9 Process Recovery Management (5.1.4.2.) ................................................................................................................ 218
8.10 Process Seals and Spare Parts Procurement Management (5.1.4.3.) ........................................................................ 228
8.10.4 Process Step Detailed Requirements and Solution .................................................................................. 230
9 Integrated Solution Management and Technical Solution Management ..........................................................................239
10 Technical/Development Related Items ............................................................................................................................ 240

10.1 Gaps ....................................................................................................................................................................... 240
10.2 Custom Development ............................................................................................................................................. 243

Business Blueprint
1 About This Document
Note
Please note the following color code used in the flowcharts:
o Light Blue: Normal process
Formatted: Font: 8 pt
o Dark Green: Integration points within Equipment Workstream Formatted: Font: 9 pt
o Light Green: Equipment status updates Formatted: Font: 9 pt
o Orange: Integration points across streams Formatted: Font: 9 pt
o Yellow: GAPs Formatted: Font: 9 pt
Formatted: Font: BentonSans Book


About This Document AG or an SAP affiliate company. All rights reserved. 9
Business Blueprint
Formatted: Font: BentonSans Regular Italic

1.1 Purpose and Scope
This document states the conceptual results of the workstream /substream Asset Management of the SAPHIR project. These
workstream results were devised and decided on by the project team and the department experts from customer CMA CGM
during the Business Blueprint project phase. This is the main concept document of the workstream /substream Asset
Management. It is supplemented by separate specifications for custom developments and other external documents (WRICEF,)
The content of this document forms the basis and the guidelines for the subsequent realization phase. Together with all the
related documents (see chapter 1.2) this document aims to describe the future business solution based on SAP software.
Any additional explanations that are only relevant when the project is in progress are given in the various project management
plan documents, which the project management team will provide on request.
Methodological approach has been followed for a comprehensive description of the solution. A systematic requirements and
solution coverage documentation has been established at each process and process step level, providing clear information for
realization choices in the requirement list with the following values.
SAP Standard
Requirement is covered in SAP Standard (e.g. TM, CRM etc.)
Implementation
There are some adjustments needed during implementation/realization (e.g. Interface, Form) to fulfill the requirement
Custom Development
Custom development is needed to fulfill the requirement
Roll-in for FBS
Requirement could be covered in FBS Transportation Resource Planning, however, SAP takes absolutely no commitment that
such requirement is or will be covered in FBS Transportation Resource Planning as its exists on the date of the Business
Blueprint or in the future.
Price to be agreed upon when and if customer purchases corresponding standard SW
Out-of-Scope
Requirement is not in scope
1.2 Management/Executive Summary
This blueprint provides an overview of the to-be business processes in the area of Equipment Asset Management and maps them
to the relevant SAP solutions in order to successfully implement SAP in the CMA-CGM group.
The blueprint describes the processes from the perspective of CMA CGM Logistics department.

Business Blueprint
Flowcharts have been used to facilitate CMA CGM understanding of business processes and to highlight important integration
points across business areas such as equipment logistics, equipment inventory management, procurement, finance and asset
accounting.
Solution descriptions explain how these processes shall be executed in SAP systems, identifying technical GAPs where applicable.
Section 2 of this document provides further details about the integration of Equipment Asset Management into the overall SAP
solution landscape at CMA CGM.
Equipment Asset Management covers the following topics:

Management of fleet strategy
Management of owned equipment procurement and sale
Management of equipment leasing (and sub-leasing)
Management of equipment damage and loss
Management of equipment maintenance and repair
Management of recovery for equipment loss
Management of procurement for seals and spare parts
Management of owned equipment procurement and sale

The process covers the procurement and disposal (sale) of owned equipment. Procurement of owned equipment describes details
about negotiations with supplier, contract creation and execution, equipment delivery and finally, invoicing and payment. Disposal
refers to the sale of containers.
Management of equipment leasing (and sub-leasing)

The process describes procurement and return of leased equipment. Procurement captures details about negotiations with the
lessor, agreement creation and execution, equipment pickup or delivery and finally, invoicing and payment.
Management of equipment damage and loss

This process deals with handling cases of lost, damaged and found equipment
Management of equipment maintenance and repair

The maintenance and repair process deals with the identification and handling of damaged equipment, repairs management and
availability of equipment for operational use after repair completion.
Management of recovery for equipment loss

Recovery Management deals with the recovery of financial loss incurred due to loss or damage of a container by a third-party
Management of procurement for seals and spare parts

This process deals with the procurement of seals and spare parts for reefers (reefer kits).

Business Blueprint
1.3 Glossary
Throughout the document SAP terminology is used unless otherwise noted. Terms and abbreviations relevant for this business
blueprint are part of the central glossary; see [Glossary].
1.4 Related Documents
The following documents are not part of this business blueprint. They are not automatically accepted together with this business
blueprint, but may be subject to separate customer acceptance procedures.
Document Document Title Version/ Filename Author Formatted Table

ID Type Date
[ToBe_EQP] To Be Equipment Fleet 0.6.4 SAP_FGD-To- SAP Field Code Changed

Process Management 04.March.2014 Be_Process_Equip
ment_V0.6.4_files
(2)
[BBP_PRM] BBP Procurement 0.109 SAP-FND- SAP

0830. AugustJune BBP_PRM-v0.9.pdf
2014
[BBP_EQP_IM] BBP Inventory 0.100.9 SAP-FND- SAP

Management 1830. Julyne 2014 BBP_EQP_IM-
v0.9.pdf
[BBP_EQP_LM] BBP Logistics 0.10 SAP-FND- SAP

Management 18. July 20140.9 BBP_EQP_LM-
30. June 2014 v0.9.pdf
[BBP_Q2C_Booking] BBP Documentation 0.99 SAP-FND- SAP

3030. June June BBP_Q2C_Booking Formatted: Default Paragraph Font
2014 s-v0.9.pdf
[BBP_NWK_CAPA_ALLO BBP Network Capacity 0.9 SAP-FND- SAP

] and Allocation 0.9 BBP_NWK_CAPA_
Management 20. June 201420. ALLO-v0.9.pdf
June 2014
[BBP_FIN_Asset] BBP Asset Accounting 0.9 SAP-FND- SAP

30. June 20140.9 BBP_FIN_ASSET-
30. June 2014 v0.9.pdf
[BBP_FIN_AR_AP_BA] BBP AR, AP and 0.9 SAP-FND- SAP

Banking 30. June 20140.9 BBP_FIN_AR_AP_B
30. June 2014 A-v0.9.pdf
[BBP_FIN_INV] BBP Invoicing & 0.9 SAP-FND- SAP

Collection 30. June 20140.9 BBP_INV-v0.9.pdf
30. June 2014

Business Blueprint
Document Document Title Version/ Filename Author Formatted Table

ID Type Date
[EM_Events] Central List EM Master file 2.97 EM_full events CMA Field Code Changed
Events and list_V2.97.xls CGM /
Actions SAP
[C_MD] Concept MDM General To be provided by CMA CGM to CMA

Design CMA CGM complete with the CGM
exact naming of the
document
[C_Migration] Concept Data Migration To be provided by CMA CGM to CMA

General Design CMA CGM complete with the CGM
exact naming of the
document
[C_GRC] Concept GRC Conceptual To be provided by CMA CGM to CMA

exact naming of the
document
[C_TechGen] Concept Technical General To be provided by CMA CGM to CMA

exact naming of the
document
[Glossary] Central Saphir Glossary n/a SharePoint List SAP/ Field Code Changed
Glossary (Official) Saphir Glossary CMA Field Code Changed
Shipping Glossary (Official) CGM
Shipping Glossary
[OrgStruc] BBP Enterprise 0.99 SAP-FND- SAP

Organizational 3030. JuneJune BBP_Organizationa
Structure 2014 l_structures-
v0.9.pdf
[GapList] Central List All Gaps n/a SharePoint List 00 - SAP/ Field Code Changed
All Gaps CMA
CGM
[Integration] Central List Integration n/a Integration List SAP/ Field Code Changed
Subjects CMA
CGM
[EQP_KPI] Central List KPIs n/a SAP_GUI_EQP_KPI CMA

s_V0.4 CGM

Business Blueprint
2 Solution Overview
The figure below provides an overview of the objects that shall be used to model the processes in scope of the SAPHIR stream
Equipment.
Note
The tool for resource planning is assumed to be added to the SAPHIR solution landscape at a later point in time. Details
mentioned here reflect the expectation regarding high-level functionality this tool shall cover. The figure below shall not
imply that any product which may potentially be offered by SAP at future point in time will offer the depicted
functionality.
Figure 111: Solution component overview: Equipment

Solution Overview AG or an SAP affiliate company. All rights reserved. 14
Business Blueprint
The figure below gives an overview of the major solution components, their relationship, and their integration. The text that
follows provides a high-level description about how the objects are related to the most important business processes.
Note
The tool for resource planning is assumed to be added to the SAPHIR solution landscape at a later point in time. Details
mentioned here reflect the expectation regarding high-level functionality this tool shall cover. The figure below shall not
imply that any product which may potentially be offered by SAP at future point in time will offer the depicted
functionality.
Figure 222: Solution Overview
Asset Management
Asset master data shall be modelled as SAP TM resources. Enhancements shall allow maintaining the required information.
Fleet strategy processes consist mainly of senior management decisions and their operation preparation. To-be- developed
reports shall provide system support.

Business Blueprint
The solution for the management of container acquisition is different for owned and leased containers.
Purchasing for owned containers is modeled as a purchasing process within SAP ECC, leveraging the component SAP Materials
Management (MM) Purchasing. Based on framework orders representing contracts with container suppliers, call-offs related to
those contracts shall be modelled as purchase orders. Upon physical receipt of new containers at CMA CGM depots, the creation
of SAP TM resources shall be triggered. Templates of the resource master data shall be maintained in SAP TM. These shall be used
to populate the SAP TM resource attributes for the container identified by its unique number which relates to a series for which
common attributes are defined.
On-hire of leased containers shall be modelled as SAP TM service freight orders in relation to freight agreements. These freight
agreements shall represent contracts with lessors and shall capture the relevant commercial details. Off-hire of containers at the
end of lease shall be similarly modeled as SAP TM service freight orders, also related to the corresponding lease contract. Both
freight orders shall also be the basis for invoice verification of charges invoiced by the lessor, related to on- and off-hire. As per the
standard process, the freight orders shall populate the expected cost per contract through a freight settlement document
transferred to SAP ECC, where invoice verification takes place. Invoice verification shall be supported by additional developments
which are required due to the high volume of items to be checked.
As long as a leased container is part of the CMA CGM fleet, the lessor shall charge the lease cost monthly. A batch program shall
be developed which calculates the lease duration per month for each individual container and creates a monthly service freight
order per lessor, which is linked to the relevant lease contract (freight agreement). This shallThis shall therefore allow the
settlement of lease per diem charges by means of a freight settlement document being transferred to SAP ECC, where a service
purchase order shall be created allowing invoice verification.
Short term sublease-from shall be modelled similarly to long-term lease in terms of the proposed solution.
Sale of owned containers shall be modelled as SAP TM forwarding quotations and shall capture the requests of potential buyers
and, subsequently, create forwarding orders representing the actual sales order. This shall allow consecutive settlement of sales
revenues by means of forwarding settlement documents.
CMA CGM also acts as lessor of containers to third parties. Respective sub-lease-to contracts shall be modelled as SAP TM
forwarding agreements which capture the relevant lease contract details. Actual lease call-offs shall be represented by SAP TM
forwarding orders created in relation to these contracts and shall serve as basis for settlement of the respective revenues by
means of forwarding settlement documents issued towards the lessee. Additional developments shall allow the monthly creation
of those forwarding settlement documents.
A number of enhancements are required to support CMA CGM requirements. It is to be highlighted that SAP TM freight
agreements technically are the same objects as forwarding agreements. Therefore, the required enhancements for modelling the
lease contract shall be implemented only once, and can serve the needs for lease-from as well as lease-to contracts.
In the area of Maintenance and Repair (M&R), requirements are collected which shall be addressed by WRICEF developments
concerning the data integration between SAP solutions and CMA CGMs legacy application IMARS. IMARS shall be used to model
M&R activities in SAPHIR.
For recovery management and reefer kits, including spare parts, the corresponding CMA CGM legacy systems iRecovery and KIRA
shall be integrated by means of interfaces for which requirements are collected and which shall be developed as WRICEF objects.

Business Blueprint
Inventory Management
Events related to container movements shall be captured by SAP Event Management and shall be propagated to SAP TM and
potentially other systems by implementation of event handlers. A required staging area for received events, including manual and
rule-based determination of corrections and refinements of received data, shall be additionally developed.
Master data for organizational and geographical structures shall be captured using SAP TM zones. Those structures shall be made
available to a future tool for planning of resources which is supposed to be added to SAPHIR scope once identified and evaluated.
Depots shall be modelled as SAP TM locations.
Depot contracts shall be modelled as SAP TM freight agreements. In relation to those agreements, service freight orders shall be
created in the case that CMA CGM orders specific services from a depot. These freight orders shall create freight settlement
documents, thereby allowing invoice verification of corresponding depot invoices in SAP ECC.
A batch program shall be developed which creates monthly SAP TM service freight orders that contain the consumed storage
services per depot, while considering specific contractually agreed free storage quota. Freight settlement documents created from
those service freight orders shall serve as basis for respective invoice verification in SAP ECC.
Charges invoiced by depots for gate-in/out moves shall be captured in relation to SAP TM service freight orders that represent
depot release and depot acceptance orders.
For tactical inventory management and repositioning avoidance, requirements have been identified which shall be covered by a
tool for planning of resources which CMA CGM intends to add to the SAPHIR solution landscape scope at a later point in time. This
tool shall provide visibility of forecasted demand and supply of containers per location. What-If scenarios are required in order to
score different repositioning avoidance options, taking into account cost and fleet imbalance effects.
In the areas of management of contractual commitments and repositioning avoidance, the major requirements shall be covered
by a tool for planning of resources which is not part of the solution landscape yet. Corresponding requirements towards this tool
are captured in this document.
For expedition of idle equipment, events tracked in SAP event management shall be evaluated. Numerous gaps are recorded in
terms of requirements that shall be covered by enhancements.
Equipment Logistics
Shippers demands for containers resulting from forwarding orders (bookings) shall be determined from SAP TM transportation
units (TU) linked to empty provisioning items. It shall be possible to assign suitable depots which satisfy such demands, based on a
depot determination offered by a tool for resource planning which CMA CGM intends to add to the SAPHIR solution landscape at a
later point in time. The identified pickup depot shall be stored on the empty provisioning stage of the empty provisioning TU. A
document authorizing the depot to issue containers for the identified demand in the determined depot shall be represented by a
SAP TM service freight order (depot release order). Items in this (depot release) service freight order shall be linked to the empty

Business Blueprint
provisioning TU items as well as to the corresponding depot contract freight agreement item. Subsequently, the freight
settlement documents created based on this service freight order shall allow depot invoice verification in relation to gate-out
handling cost.
After a container has been gated out to the shipper from the depot, the corresponding event recorded in SAP Event Management
shall be processed in order to assign a specific container number (chosen by the depot) to the TU for which it is used.
Similarly to depot release, depot acceptance orders shall also be modelled as separate service freight orders linked to empty
return transportation units. Similarly, the return depot shall be identified by the tool for resource planning and recorded in the TU
stage. Requirements are documented in relation to return depot optimization, which shall consider possible cost savings by
returning empty containers after carrier haulage import completion to another depot than the default depot. This shall happen if it
positively impacts the depot balancing while being a preferable option for achieving this positive impact under cost
considerations.
Depot release and depot acceptance service freight orders shall be used also in relation to leasing on- and off-hire, receipt of newly
acquired owned containers, or in case of inland repositioning.
Inland empty repositioning shall be modelled as transportation units linked to forwarding orders. Transportation of those TUs can
be executed by means of freight orders, which is part of the Intermodal stream processes.
Maritime repositioning shall also be covered by forwarding orders representing empty bookings on vessels. Empty provisioning
and empty return TUs assigned to these forwarding orders shall be used for assigning the pickup and return depot in similarity to
laden cargo bookings, leveraging the expected capabilities of the tool for resource planning.

Business Blueprint
3 Assumptions and Constraints
The assumptions for the solution are especially, but not limited to, the following:
CMA CGM plans to integrate a tool for resource planning into the SAPHIR scope at a later stage. As of now no specific tool has
been selected and therefore the functionality of that tool is not yet known. For this BBP it is assumed that the to-be-tool
should offer the following capabilities on a high level:
o Visibility of stock per location, also visualized map-based
o Capability to implement customer-specific calculations of KPIs which can be visualized
o Capability to identify a suitable location (depot, terminal and so on) for container pickup and return
o Forecasted demand and supply for containers per location and aggregated according to organizational and geographical
hierarchies
o Ability to define rules which determine exceptional situations and provide visibility for these (alerts)
o Decision support capabilities, for example achieved by what-if analyses to decide about various options of container
repositioning or avoidance of repositioning under consideration of location imbalances and cost
Once the tool is identified, it will likely have to be enhanced by CMA CGM to cover all needs.
All relevant container master data shall be stored in SAP Transportation Management in resource objects. Therefore the
resource object will have to be enhanced. The use of SAP ECC equipment master data as source of container master data shall
not be considered. Integration with FI-AA (Financial Asset Accounting) is managed via enhancement which would also be the
case if the container master data was stored in SAP ECC equipment master object.
The usage of the ECC equipment master would require significant enhancements which does not seem justified as long as the
implementation of SAP Enterprise Asset Management (EAM) for management of container maintenance and repair is not
foreseen.
All processes related to owned equipment purchase shall be designed in the SAP ERP system (modules: SAP-MM, FI-AA, FI-
CO, FI-AP)

Assumptions and Constraints AG or an SAP affiliate company. All rights reserved. 19
Business Blueprint
4 Value Determination
4.1 Major Business Pain Points (To Achieve Business Objective)
The following Pain Points (related to the current situation) are the output of the To-Be-Process phase for Asset ManagementAsset
ManagementAsset ManagementAsset Management:
Pain Point Description Text

ID
1 Gap between actual ISO code of a container and information in system - For Business reasons, we create
various container size/types to differentiate two containers with same ISO codes. As every Size/types need to
have referential with ISO codes, we increment amounts of ISO codes used.
2 Technical specificities informed by default; difficulty to segregate container characteristics within same
Size/Type group - Container Technical specificities are linked to container size/type by default
3 Container grade in container passport - Container grade (Food grade, General Cargo) is currently not
updated properly; while information is usually available at depot level
4 Costs missing when calculating standard Imbalance costs - database of costs are fulfilled manually when costs
are missing in the system. For example: empty positioning when no Empty repositioning Reference is created.
5 Follow-up of delivery schedule of Produced containers done by Excel file - No integration between purchase
order and Equipment management tool
6 Multiple entry of same information - no connection between Access file, Tracking and invoicing module (each
module updated manually, leading to additional workload)
7 Control of invoices - done via external Access tool
8 Managing received invoices - No possibility to record a Credit note received from partner when a mistake in
original bill is found out after payment
9 PU & DO visibility - lack of visibility about authorized places of pick/up & delivery
10 Multiple entry of same information - no data sharing between Access tool/Recovery, invoicing module and
Tracking update.
11 Tracking events - Tracking moves are currently managed through events, such as Gates, Loadings, etc No
additional information between 2 generic events (for example: trucker's delay, container en-route localization,
...) ; if available, these are depending on local initiatives (UK, US)
12 MEA move not showing all information available - MEA move can be used as default, whether container is
damaged or not. Statute (damaged or available) is confirmed afterward. Information may already be available
in EDI message
13 Damage condition on board - When we are loading a box empty, the mention "Damaged" is lost
14 Grade of empty discharge unit - If container directly returned at terminal in POL, and discharge at POD without

Value Determination AG or an SAP affiliate company. All rights reserved. 20
Business Blueprint

ID
inspection, no way to find grade of the container. We will need an ad-hoc information from depot to know the
grade
15 Tracking move block & manual update - tracking move blocking in case of bad sequencing, missing mandatory
information or non-consistent information. They must be manually updated. 25% of total moves have no
direct integration, leading to huge workload (full-time staff in big agencies)
16 Depot Contract database - Contracts are supposed to be stored in a common database (BCL) but not used as
not able to provide outputs (such as Invoice control for example).
17 Dummy booking for Release order acceptance - When a FF comes to pick up containers for multiple customers,
or a VIP customer is picking up boxes for 1 month booking without knowing in advance the Booking number, a
dummy booking is created to enable the release, and integration is performed later on.
18 Dummy booking for Release order acceptance - Problem with calculation of D&D: if MOS move, DD start, if
MEA in dummy depot, don't start
19 Positioning of boxes to private yard - Who is paying for this move? Depends on contract. A transfer move is
created, which therefore requests a Transport Move and payment order.
20 Customer depot tracking moves - Information received from customers not always reliable(delayed tracking,
no booking reference)
21 Customer priority - no automatic clue to know priority list of customers. It is done manually within the agency
to determine which bookings are served and which one are not;
22 Absence of provisional stock module and lack of anticipation on stock availability - no standard way to forecast
our stock. Throughout the world, different way to have stock anticipation
23 Lack of visibility on stock availability and condition - even in our stock situation, situation is not clear as
container population is multiple: Available, Unavailable, Dedicated to specific traffic, and so on
24 Export forecast accuracy - Export forecasts received from agencies under different format (LARA, excel,
sheet); and difficulty to assess accuracy: cross-check with historical data (% of shortfall, gap between forecast
& reality, Historical stats
25 Import Forecast accuracy - Import volumes available in system, but time and place of redelivery difficult to
assess
26 Change of port of discharge for empty containers on board - in case of COD, Tracking should be updated based
on bay plan
27 Planning loading of empty containers on vessel - discussion via e mail, phone calls & XLS files. No integrated
follow-up between cargo flow management and Logistics team
28 Reasons for idle containers - Reasons for idle contains can be multiple (customs, non-responding customer, will
of partner, etc), as well as level of criticality (feedback to notification, payment of partial invoices, etc)
29 manual check of stock availability and Imbalance -
30 visibility on time between release and empty return at destination - There is a free-time period for partners to
use CMA CGM boxes, but system is not recording information (if available)if customer is extending use time
31 Stock visibility - Logistics has to send information to customer service (regular reports, phone discussions,
manual process) about stock for Customer service to be able to confirm to customer equipment availability &

Business Blueprint

ID
finally confirm booking
32 Buffer in customer yard - no visibility on the stock at customer yard, only the total volume
33 Depot allocation and stock management - In case of C/H, Release order (and choice of depot) issued by
transport manager to the partner , while Release Order is issued by Log department in case of M/H
34 Booking forecast - Export forecast method not harmonized - different whether we are in Asia, Europe, India,
35 Booking change or cancellation - In case of change or cancellation of booking, Equipment team has to cancel
manually the depot Release order to enable the change at booking level. This is time consuming and slow-
down the whole process
36 Booking cancellation - When booking canceled, manual process to consolidate costs involved (detention,
handling, transport if any, storage if any, Repairs if any) and invoice
37 Container substitution - lot of manual workload to validate the possibility between logistics, booking desk, and
Intermodal in case of Carrier Haulage booking
38 Special Instructions - Lists received by Excel file from HO, with manual management of the off-hires
39 Special Instructions - highly depending on tracking side - not properly done if tracking outdated
40 Depot acceptance order - In case of modification of the place of return, Depot Acceptance Order (DAO) must
be canceled and resent to the right depot --> additional manual workload
41 Choosing the redelivery depot - Returning volumes are managed to depot "per vessel" (= all units from one
vessel to same depot) so it's based on experience. No visibility on ratio of returns between one depot and the
other
42 Off-hire quotas - No visibility on quota per Lease company, for proper management of off-hires
43 Empty positioning information to depots - Depots are not informed in case of empty positioning from/to them
(only manually by local logistics)
44 Booking for empty loading on board CMA CGM vessels - For loading empties on board CMA CGM vessels,
creation of a booking in the Customer Service screen, as if it were a regular booking. BUT system is requesting
the issuance of a Release Order, which is not the case for empty loading
45 Local shunt - empty positioning reference not always performed in case of local shunt because of time-
consuming process
46 Logistics Dashboard - Low possibility to drill down information, need a dashboard for more precise information
47 Multiplicity of reports - Almost everybody has reports on his own desktop. Information should be easily
retrieved from system, for consistency in reporting process.
48 No integration with accounting system - I mars process stops at Self-billing step
49 Definition of grades - CMA CGM has a standard for "A-grade" containers; but there can be some different
requirements depending on country & customer. Grade definition is rather subjective
50 Cost allocation - Some costs are allocated to MnR account while there shouldn't be (based on proper allocation
from agency)

Business Blueprint

ID
51 Follow-up of damages - When container is flagged as damaged in the tracking, this information is lost when
container is positioned or loaded empty on board a vessel. This causes problem within stock forecast tool
(container discharged in a port but unavailable)
Pain Point ID Description Text
AM_1 Gap between actual ISO code of a container and information in system: We create various container
size/types to differentiate two containers with same ISO codes. As every Size/types need to have
referential with ISO codes, we increment amounts of ISO codes used
AM_2 Container Technical specificities are linked to container size/type by default which creates difficulty to
segregate container characteristics within same size/type.
AM_3 Container grade in container passport: Container grade (Food grade, General Cargo) is currently not
updated properly; while information is usually available at depot level
AM_4 Costs missing when calculating standard Imbalance costs. Costs are added manually when missing in
the system
AM_5 Follow-up of delivery schedule of produced containers is done by Excel file as there is no integration
between purchase order and Equipment management tool
AM_6 Multiple entry of same information as there is no connection between Access file, Tracking and
invoicing module (each module updated manually, leading to additional workload)
AM_7 Control of invoices is done via external Access tool
AM_8 Managing received invoices: There is no possibility to record a credit note received from partner when
a mistake in original bill is found after payment
AM_9 Lack of visibility about authorized places of pick/up & delivery
AM_10 Multiple entry of same information as there is no data sharing between Access tool/iRecovery,
invoicing module and Tracking update
AM_11 No integration with accounting system as iMars process stops at self-billing step
AM_12 Definition of grades
AM_13 Cost allocation: some MnR costs are incorrectly allocated to MnR account (while they should be based
on proper allocation from agency)
AM_14 When container is flagged as damaged, this information is lost when container is positioned or loaded
empty on board a vessel. This causes problems within stock forecast tool (container discharged in a
port but unavailable)
4.2 Key Performance Indicators (KPIs)
The following KPIs are the output of the To-Be-Process phase for Asset ManagementAsset ManagementAsset Management: Formatted: Normal

Business Blueprint
Note
The tables will not necessary capture all the KPIs. You can find a Consolidated KPI master file in a central file; see Formatted: SAP_NoteParagraph
[Consolidated KPI].
4.2
The following KPIs are the output of the To-Be-Process phase for Asset Management:
Name Comment Formula Linked Processes Formatted Table
Fleet age pyramid Fleet volume per build date, evolution & 5.1.1.2. Equipment Fleet Strategy
ratio per size/type. Management
KPI updated quarterly based
Fleet renewal Visibility on volumes of containers to be 5.1.1.2. Equipment Fleet Strategy

anticipation replaced (Sales, Off-hire) and estimate Management
of additional needs to cover activity
growth.
KPI updated monthly based
Ratio TEU vs. slot TEUs available as compared to total 5.1.1.2. Equipment Fleet Strategy
available slots / capacity on CMA-CGM Management
vessels.
Utilization ration per Utilization of a particular container size- 5.1.1.2. Equipment Fleet Strategy
container size-type type compared to total TEUs of that Management
size-type available.
Container sales Sales activity in terms of selling price, 5.1.1.3.5. Manage Owned
activity volumes, partners, size/type, location, Equipment Sales
conditions (damage or wear & tear or
old units).
Lease commitments Value of per diem with long-term Ccontract validity x 5.1.1.4. Leased Equipment
commitments per diem x number Management
KPI updated monthly based TC per lease
company
Per diem evolution Leasing per diem per size/type, lessor, 5.1.1.4. Leased Equipment
and lease type. Management
KPI updated quarterly based
Saving through One Saving calculation based on cost 5.1.1.5. Equipment Sub-Lease-
Way utilization assumption for usage of One Way units From Management
One-way / sublease Ratio of volume of off-hire Vs. One way 5.1.1.5. Equipment Sub-Lease-
from off-hire in fleet (gap means that containers are From Management,
misused), evolution per size/type, 5.1.1.6. Equipment Sub-Lease-To
partner, location. Management
KPI updated weekly based

Business Blueprint
One-way / sublease One way and sublease from agreement 5.1.1.5. Equipment Sub-Lease-
from on-hire follow-up & evolution per partner, From Management,
size/type, month, location/hub. 5.1.1.6. Equipment Sub-Lease-To
KPI updated weekly based Management
Saving/revenue Saving calculation based on cost 5.1.1.5. Equipment Sub-Lease-

through container assumption for usage of subleased units From Management; 5.1.1.6.
sublease, one-way (sublease from, sublease to, one-way, Equipment Sub-Lease-To
and cabotage cabotage). Management
Turn Time of Time (in days) of use of containers by 5.1.1.5. Equipment Sub-Lease-
Subleased ('from' or CMA CGM & partners. From Management,
'to'), one-way and KPI updated monthly based 5.1.1.6. Equipment Sub-Lease-To
cabotage units Management
Business volume For 1-way and cabotage, sublease-from 5.1.1.5. Equipment Sub-Lease-
evolution with and sublease-to year per year From Management,
partners comparison. 5.1.1.6. Equipment Sub-Lease-To
Management
Amount of recovered Amount of recovered value from lost 5.1.1.7. Lost and Found
value containers per location, agent, Equipment Management
size/type, condition (long-term
stationary, damaged or recovery).
Volumes of units Volume of lost units per location, agent, 5.1.1.7. Lost and Found
declared in total loss size/type, value, condition (long-term Equipment Management
stationary, damaged or recovery)
Taux de casse' - 1 Percentage of Volume of units gated-in 5.1.1.7. Lost and Found
Damaged vs. total volume gated-in. Equipment Management; 5.1.2.3
Manage Depot
Taux de casse' - 2 Percentage of damaged units in depot 5.1.1.7. Lost and Found
stock. Equipment Management; 5.1.2.3
Manage Depot
EDI direct integration Percentage of direct integration 5.1.2.1 Track Movements
Tracking performance Tracking quality and time gap per 5.1.2.1 Track Movements
partner, location, agency
Tracking quality Percentage of pairing moves reference 5.1.2.1 Track Movements

as valid from both commercial and
operation point of view.
Tracking reliability Time gap (time between physical date 5.1.2.1 Track Movements
and its integration date in system).

Business Blueprint
FIFO indicator Percentage of equipment staying more 5.1.2.3 Manage Depot

than 30 days within a specific depot.
Volume of idle As "First-in First-out" rule is supposed to 5.1.2.3 Manage Depot

(empty) containers be applied, no idle should be existing,
Booking satisfaction Number of booking postponed/canceled 5.1.2.4 Manage Contractual

level at CMA CGM request because of Equipment Commitments
shortage or non-compliance of
equipment.
Turn time Number of days of activity (max flow) 5.1.2.5 Manage Tactical
covered by stock. Equipment Inventory Supply and
Demand
Export forecast Need forecast Vs. actual export. 5.1.2.5 Manage Tactical
quality Equipment Inventory Supply and
Demand
Filling factor Vessel geometrical capacity vVs. total 5.1.2.5 Manage Tactical
TEUs loaded (full and empty). Equipment Inventory Supply and
Demand
Logistics costs ratio Ratio of expenditures of logistics costs 5.1.2.5 Manage Tactical
(storage, empty positioning, and Equipment Inventory Supply and
handling) vs. activity. Demand
Saving/revenue Saving calculation based on cost 5.1.2.6 Manage Repositioning

through assumption. Avoidance
cabotage/domesticati KPI updated monthly based
on/interchange
release
Turn time of units Time (in days) of use of containers by 5.1.2.6 Manage Repositioning
under partners Avoidance
cabotage/domesticati KPI updated monthly based
on/interchange
agreement
Volume of containers Volume evolution per partner, size/type, 5.1.2.6 Manage Repositioning
under location. Avoidance
Cabotage/Domesticat KPI updated weekly based
ion/Interchange
agreement
Volume of idle (full) Evolution of volumes of idle full 5.1.2.7 Expedite Idle Full
containers - 1 container per country, time frame, Equipment
types.
Volume of idle (full) Ratio vs. stock of containers (full / 5.1.2.7 Expedite Idle Full
containers - 2 empty). Equipment

Business Blueprint
Booking ratio per Volumes of container booked per grade 5.1.3.1 Manage Release
grade (food, general cargo, scrap) / total
volume booked
Customer profile (1) Reliability of customers about requested 5.1.3.1 Manage Release
pick up date vs.VS actual pick-up.
Customer profile - 2 Time between the booking date and the 5.1.3.1 Manage Release
requested pick-up date per customer.
Agency release order Time between issuance of release order 5.1.3.1 Manage Release
management and requested pick-up date (per
agency).
Idle empty containers Volume of empty idle containers for 5.1.3.6 Monitor Agency Logistics
more than 30 (or 180) days. Performance
M&R process time Process time between each step of 5.1.4.1. Maintenance & Repairs
Maintenance & Repair process: damage (MnR) Management
identification, estimate submission,
estimate acceptance or modification,
start of repair and repair completion
(start and end steps available in
Tracking; intermediate steps available in
iMars)
Repair capability Volume of repairs performed per depot 5.1.4.1. Maintenance & Repairs
per timeframe (available in iMars). (MnR) Management
Repair frequency Frequency of repair per series/reefer 5.1.4.1. Maintenance & Repairs
brand (available in iMars). (MnR) Management
Type of repair Type of repair (ratio) per depot 5.1.4.1. Maintenance & Repairs
(available in iMars). (MnR) Management
Average cost per Average cost per repair per depot. 5.1.4.1. Maintenance & Repairs
repair and total cost (MnR) Management
per country
MnR cost vs. damage Amount spent in repairs vs. amount 5.1.4.2. Recovery Management
recovery recovered from liable 3rd party
Misuse level per agent Ratio of volume of off-hire Vs. One way 5.1.1.5. Equipment Sub-Lease-
(for missed one-way in fleet (gap means that containers are From Management
off-hires) misused), evolution per size/type,
partner, location.
Customer reliability Container quantity booked vs. quantity 5.1.3.1 Manage Release
released.
Tracking by channel Percentage moves per channel source 5.1.2.1 Track Movements
(EDI, Web, manual, trucker system )

Business Blueprint
Percentage of sales Percentage of sold containers vs. 5.1.1.3.5. Manage owned Formatted: Font: BentonSans Book
eligible fleet for sales. equipment sales;
5.1.1.2. Equipment Fleet Strategy
Management
Number of bookings Total volume of booking vs. container 5.1.1.2. Equipment Fleet Strategy
per year fleet. Management
EDI direct integration Percentage of direct integration. 5.1.2.1 Track Movements
Ratio of volume of off-hire Vs. Volumes

Leased equipment eligible for off-hire, evolution per 5.1.1.4. Leased Equipment
off-hire size/type, partner, location Management

Business Blueprint
5 SAP Organizational Structure
The SAP organization structure is described in a central document. For more information, see [OrgStruc].
There are no specific organizational structure considerations for this business blueprint.

SAP Organizational Structure AG or an SAP affiliate company. All rights reserved. 29
Business Blueprint
6 Data Management
6.1 Master Data Concept
The master data general design is the responsibility of CMA CGM, further details are available in [C_MD]. For further details on the
expected content of a master data concept document refer to [OoS_Sections].
6.2 Master Data Objects
Especially the following master data are the basis for the solution described in this business blueprint and need to be considered in
the master data and migration concept:
Master Data Object Short Description Formatted Table
Supplier The supplier represents goods/services provider.

(SAP Standard)
Material Master Goods / services to be supplied. Formatted Table

(SAP Standard)
Price Condition Price according to specific criteria.

(SAP Standard)
Resource Resource data is relevant to the planning of order dates taking into account working times and the Formatted Table
(SAP Standard available capacities of the resources. In the context of this blueprint, a resource shall refer mainly
Enhancement) to a Containers, Reefers, Gensets, Chassis and Rolling Floors.
Location A logical or a physical place in which products or resources are managed on a quantity basis.
(Customer Specific) Represents point code and depot.
Business Partner A person, organization, group of persons, or group of organizations in which a company has a Formatted Table
(SAP Standard) business interest. In general, business partners are all legal entities or individuals with whom a
company maintains business contacts.
Service Product Service Products are a group of services that are performed for a booking, e.g. fumigation of a
(SAP Standard) container.
Series Template Series refers to a group of containers often belonging to a certain number range, and having some Formatted Table
(Customer Specific) common characteristics like size-type and linked to an object.

Data Management AG or an SAP affiliate company. All rights reserved. 30
Business Blueprint
Master Data Object Short Description Formatted Table
Supplier The supplier represents goods/services provider.

(SAP Standard)
Material Master Goods / services to be supplied.

(SAP Standard)
Price Condition Price according to specific criteria.

(SAP Standard)
Exchange Rate The actual exchanged rate defined for accounting and purchasing processes.
(SAP Standard)
Resource Resource data is relevant to the planning of order dates taking into account working times and the
(SAP Standard available capacities of the resources.
Enhancement)
Location A logical or a physical place in which products or resources are managed on a quantity basis.
(SAP Standard Represents point code and depot.
Enhancement)
Business Partner A person, organization, group of persons, or group of organizations in which a company has a
(SAP Standard) business interest. In general, business partners are all legal entities or individuals with whom a
company maintains business contacts.
Service Product Service Products are a group of services that are performed for a booking, e.g. fumigation of a
(SAP Standard) container.
Series Template Series refers to a group of containers often belonging to a certain number range, and having some
(Customer Specific) common characteristics like size-type and linked to an object.
6.3 Master Data Requirements
ID Title Description Realization Gap Formatted Table
EQP-MD-001 Management of It shall be possible to store container certificates Implementation 42

Container Certificates in an electronic format and maintain the location
Storage Link to link on the container passport.
Container Master Data
EQP-MD-002 Creation and Technical specifications for containers shall be Implementation 42

Maintenance of created and managed at Size/Type level.
Technical Specifications
at Size-Type Level
EQP-MD-003 Creation and Technical specifications for containers shall be Implementation 42

Maintenance of

Business Blueprint
Technical Specifications created and managed at container level.

at Container Level
EQP-MD-004 Mass Update of It shall be possible to update container master Implementation 42, 2655
Container Master Data data in mass through the use of filters (e.g. age,
contract, number range / series, etc.).
EQP-MD-005 Maintenance of Information about the container grade shall be Roll-in for FBS NA
Container Grade included in the container master data. It shall be
possible to update the grade as the condition of
the container changes.
EQP-MD-006 Additional fields for It shall be possible to enter additional Implementation 42

optional attributes characteristics into the container size-type
within container master data, thereby, reducing the number of
size/types size-types maintained in the system (leading with
n:n: n relationship between ST/ISOCode. See
EQP-MD-012)
EQP-MD-007 Authorizations for It shall be defined which Master Data can be Implementation 2564
Container Master Data accessed and / or changed by different roles
within the logistics team - for example, agencies,
regional office, head office, etc.
EQP-MD-008 Authorizations for It shall be possible to restrict access to container Implementation 2564
Container Residual Value depreciation value and residual value through
maintenance of relevant authorizations within
the logistics team - for example, agencies,
regional office, head office, etc.
EQP-MD-009 Integration with KIRA - KIRA is the legacy system used for management Implementation 1284
Master Data of Reefer kits (spare parts for reefers on board
vessels). An interface between KIRA and SAP
shall be established to allow exchange of master
data.
EQP-MD-010 Container Off-Hire It shall be possible to mark a container to be off- Implementation 42

Status hired with specific statuses (To-Be Off Hired /
Eligible for Off-Hire) and maintain the status in
the passport.
EQP-MD-011 Container Size-Type It shall be possible to maintain specific container Implementation 42

Groups Based on size-types for different processes.
Business Processes
EQP-MD-012 ISO Code - Size-Type It shall be possible to maintain a relationship Implementation 2570
Relationship between ISO codes and container size-type
(company specific) using a conversion or
mapping table.
(Relation n:n between ISO Code / size-type (see
Reefer use case)

Business Blueprint
EQP-MD-014 Information About It shall be possible to identify if a container is Implementation 42

Reserved Containers reserved for a particular customer / purpose (e.g.
VIP customer or specific trade), and the relevant
details of the reservation (e.g. customer name).
EQP-MD-016 Visibility on Valid and It shall be possible to have visibility on the Implementation 2573
Overdue Container containers with valid certification including expiry
Certificates dates, and well as the containers with overdue
certification.
EQP-MD-018 Volume of 'In-Fleet' It shall be possible to have visibility on the Implementation 1643
Events volume of containers on-hired with on-hire date (under
and place. BI
(this requirement is under BI scope) scope)
EQP-MD-019 Volume of 'Out-of-Fleet' It shall be possible to have visibility on the Implementation 1643
Events volume of containers taken out of fleet with (under
details on date and place. BI
(this requirement is under BI scope) scope)
EQP-MD-030 Damaged Flag It shall be possible to maintain a flag in the Implementation 42

container passport (to identify it as a damaged
container (until the repair is completed).
EQP-MD-031 Flag for Branded It shall be possible to identify blue containers Implementation 42
Containers with CMA-CGM Logo by management of a
'brand' flag in the container passport.
EQP-MD-032 Container Sales Status It shall be possible to mark a container to be sold Implementation 42
with specific statuses (To-Be Sold / Eligible for
Sale) and maintain the status in the passport.
EQP-MD-033 Master Data for Reefers It shall be possible to maintain specific master Implementation 42
data for Reefers at the container level.
EQP-MD-034 Master data for Gensets, - Ability to maintain master data for Gensets, Implementation 42
Rolling Floors & Chassis Rolling Floors and Chassis
EQP-MD-035 Reefer Data recorder It shall be possible to attach and maintain reefer Implementation 42
History data recorder history file at the container level.
EQP-MD-037 Container Sales It shall be possible to maintain a 'sales reference' Implementation 42

Reference in the container master data (passport) when
there is a corresponding sales process in
progress.
EQP-MD-038 Master Data for Shipper It shall be possible to maintain master data for SAP Standard NA
Owned Containers (SOC) shipper owned containers.
EQP-MD-039 Management of It shall be possible to manage the validity of Implementation 42

Business Blueprint
ACEP/CSC Certification ACEP/CSC Certification at the container level.

Validity Information
EQP-MD-040 Recovery File Reference It shall be possible to maintain the reference of Implementation 42
the recovery file at the container level.
EQP-MD-041 MnR File Reference It shall be possible to maintain the reference of Implementation 42
the MnR file at the container level.
EQP-MD-042 Container Number It shall be possible to maintain container SAP Standard

Format numbers in the master data, following the ISO
6346 identification numbering.
EQP-MD-043 Creation and Technical specifications for a series of containers Implementation 2571
Maintenance of shall be created and managed at series level
Technical Specifications where the series is a number range / group of
at Series Level containers linked to an object (e.g. a contract and
/ or a call off)
EQP-MD-044 Container Master Data It shall be possible to raise an alert when SAP 42
Creation Check based on container number does not match the predefined StandardImpleme
Container Number name format.It shall be possible to raise an alert ntation
StandardsContainer when container number does not match the
Master Data Creation predefined name format, and to block creation of
Block based on master data until this requirement is met.
Container Number
Standards
EQP-MD-045 Update of Container Information about the container grade shall be Implementation 42
Grade included in the container master data. It shall be
possible to update the grade as the condition of
the container changes.
EQP-MD-046 Activation and Ability to create and deactivate master data for Implementation 2572
Deactivation of Master shipper owned containers based on specific
Data for Shipper Owned triggers.
Containers
EQP-MD-049 Total Loss Status It shall be possible to maintain a 'total loss status' Implementation 42
on the container level, and to update this status
based on relevant triggers in the total loss
declaration process.
EQP-MD-050 Equipment Contract It shall be possible to maintain the relevant Implementation 42,
Reference contract reference(s) (purchasing / leasing 2655,
contract) on the container passport (master 3003
data)It shall be possible to maintain the relevant
contract reference (purchasing / leasing contract)
on the container passport.
EQP-MD-051 Activation and It shall be possible to add or remove leased Implementation 2726,
Deactivation of Leased container (master data) from fleet at the time of 2717

Business Blueprint
(and Sub-Leased) container 'on-hire' and 'off-hire' respectively.

Container Master Data
EQP-MD-052 Activation and It shall be possible to add or remove owned Implementation 2811
Deactivation of Owned container (master data) from fleet at the time of
Container Master Data container 'on-hire' and 'off-hire' respectively.
EQP-MD-053 Classification of It shall be possible to classify containers as Implementation 42, 3003

Container Ownership owned, owned with bank loan, owned with
Class financial lease, or leased.
EQP-RECO- Integration with It shall be possible to manage an interface with Implementation 50, 1853
002 iRecovery for Exchange the legacy recovery system to manage container
of Container Status status
Information
EQP-RECO- Integration with It shall be possible to manage an interface with Implementation 56, 607,
003 iRecovery - Master Data the legacy recovery management system to be 1822,
able to exchange master data. 1849,
2104,
1821, 48
EQP-M&R- Integration with iMars It shall be possible to establish an interface with Implementation 54,1138,
001 for Exchange of the legacy Maintenance & Repair system (iMars) 1851,
Container Status to enable exchange of container status 2003
Information information.
EQP-M&R- Integration with iMars - It shall be possible to establish an interface Implementation 54, 45,
003 Master Data between SAP and the legacy Maintenance & 46, 47,
Repair system (iMars) to enable exchange of 48, 49,
master data. 56, 1821
EQP-M&R- Integration with iMars It shall be possible to establish an interface Implementation 54

006 for Exchange of between SAP and the legacy Maintenance & (Outbou
Container Grade Repair system (iMars) to enable exchange of nd ODI
Information information related to container grade. Flow),
52
(Inboun
d)
EQP-M&R- Integration with iMars It shall be possible to check if the damage flag is Implementation 1138,
007 for Damage Flag Check activated in the container passport based on 1852
specific statuses in iMars.
EQP-LEAS- Update of Total Loss It shall be possible to manage container status Implementation 2584
005 Status for Leased during the total loss declaration process with the 2613
Containers relevant status updates triggered at different
points in the process.

Business Blueprint
6.4 Migration Concept
The data migration general design is the responsibility of CMA CGM, further details are available in [C_Migration]. For further
details on the expected content of a master data concept document refer to [OoS_Sections].

Business Blueprint
7 Business Process Landscape
7.1 Business Area

Business Process Landscape AG or an SAP affiliate company. All rights reserved. 37
Business Blueprint

Business Blueprint
Figure 333 : Business Process Landscape Overview
7.2 Business Area/Process Groups
This blueprint document is part of Equipment Fleet Management.

Business Blueprint
Figure 444 : Business Process Groups of Equipment Fleet Management
7.3 Equipment Asset Management Processes
This focus of this blueprint document is on Equipment Asset Management processes.

Business Blueprint
Figure 555 : Equipment Asset Management Processes
ID Process Name Description In Scope SAP Solution
5.1.1.1. Equipment Master data is the core data that is Yes NA

Master Data essential to operations in a specific
Management business or business unit.
Equipment master data consists of
technical specifications of a
container or a group of containers.
Master data may also be
maintained for accessorial
equipment like Gensets, Rolling
floors, or Chassis.
5.1.1.2. Equipment Fleet Determination of Equipment Fleet No NA

Strategy Strategy is a (manual) decision
Management making process at the top
management level of the
company supported closely by the
Logistics head office.
This process focuses on the details

relevant from the Logistics
Department viewpoint.

Business Blueprint
5.1.1.3. Owned The process concerns the end- to- Yes SAP ECC
Equipment end procurement and disposal of SAP TM
Management owned equipment. Procurement
SAP EM
captures details about
negotiations with supplier,
agreement creation and
execution, equipment delivery and
finally, invoicing and payment.
Disposal refers to the sale of
containers.
5.1.1.4. Leased The process concerns the end- to- Yes SAP ECC
Equipment end procurement and return of SAP TM
Management leased equipment. Procurement
SAP EM
captures details about
negotiations with lessor,
execution, equipment pick-up or
delivery and finally, invoicing and
payment.
Leased containers comprise 70 -
80 percent of the overall fleet.
5.1.1.5. Equipment Sub- Sub-Lease-From is the lease of Yes SAP ECC

Lease-From equipment from a third party, This SAP TM
Management process concerns the end- to-end
SAP EM
procurement and return of sub-
leased-from container, capturing
details about negotiations with
sub-lease-from partner,
execution, equipment pick-up and
finally, management of recurring
invoicing and payment.
5.1.1.6. Equipment Sub- Equipment may be sub-leased-to Yes SAP ECC

Lease-To a partner. This process concerns SAP TM
Management the management of this process
SAP EM
including details about agreement
negotiation, equipment release
and finally, invoicing and
collection of payment.
5.1.1.7. Lost and Found This process deals with: Yes SAP ECC
Equipment SAP TM
Management - Handling cases of lost equipment
SAP EM
- Handling cases of damaged

equipment

Business Blueprint

- Handling cases of total loss
equipment, including declaration
of total loss for leased equipment
- Handling found equipment

Formatted: Space Before: 3 pt, After: 3 pt, Line spacing:
Exactly 13 pt

Business Blueprint
7.4 Interface to Equipment Maintenance & Repair and Recovery

Management Legacy Systems
Maintenance and Repairs (MnR) is currently out of scope of SAPHIR except for integration of the following legacy systems:
IiMarsARS, IiRecoveryECOVERY and KitIT ReeferEEFER ApplicationPPLICATION (KIRA). For this reason the below processes
(level 3) are limited to the processes where integration with SAP might be needed.
Figure 666 : Interface to Equipment Maintenance & Repair and Recovery Legacy Systems Management Processes
5.1.4.1. Maintenance & MnR process details with the identification No SAP ECC
Repairs (MnR) and handling of damaged equipment to (only interfaces (Purchase of MnR services)
Management ensure efficient and timely repairs and shall be managed)
further availability of equipment for
operational use after repair completion. It
deals with all aspects of the process
managed in the legacy MnR application,
iMars, that are relevant for management of
required interfaces
5.1.4.2. Recovery Recovery Management deals with the No SAP ECC

recovery of financial loss incurred due to

Business Blueprint

Management loss or damage of a container by a third- (only interfaces (Recovery invoicing)
party. The process begins with shall be managed)
identification of loss or damages that are
caused by a third party, identification of
the liable third-party, and subsequently
managing the invoicing and collection of
the recovery amount. Recovery process is
managed in a legacy application,
iRecovery. This process captures all details
of the process relevant for management of
required interfaces
5.1.4.3. Seals & Spare This process deals with the procurement of Yes SAP ECC
Parts seals and spare parts for Reefers (reefer
Procurement kits), and captures all details of the process
Management relevant for management of required
interfaces
7.5 Cross Process Related Topics/Integration Points
The following integration points are related to Asset ManagementAsset ManagementAsset ManagementAsset Management:
Integration Point Short Description Solution

Included in
BBP
1350, 1485 Owned Equipment: Yes

- Purchasing business partners, contracts and orders
- Payment for owned equipment (including financial lease/bank loan contracts and
monthly payments)
- Asset acquisition, depreciation, and disposal (sale)
1360, 1480 Leased Equipment: Yes

- Leasing business partners, contracts and call-offs
- Monthly payment to suppliers (and reconciliation)
- Declaration of total loss to lessor for lost / wrecked (leased) containers
1370, 740, 490 Sub-Leased Equipment: Yes

- Sub-lease business partners and contracts
- Monthly settlement (creation and issuance of invoice and collection of payment
from sub-lease-to / receipt, payment and reconciliation of invoice for sub-lease-
from)
1470 Equipment Maintenance and Repair (MnR): Yes (interface

- MnR business partners and contracts mgmt. only)
- MnR services procurement

Business Blueprint
Integration Point Short Description Solution

Included in
BBP
- MnR services payment (invoice receipt, reconciliation and payment)
2680 Equipment Recovery Management: Yes (interface

- Issuance of recovery invoices ( intercompany and third-party) mgmt. only)
2690 Seals Procurement Management: Yes

- Purchasing business partners, contracts and orders
- Payment for seals purchased
2700 Spare Parts Procurement Management: Yes

- Purchasing business partners, and other relevant master data
- Management of spare parts purchase and payment (interface)
7.6 Event Management
This chapter includes only the events that are relevant for the Equipment Asset Management BBP.
Caution
Please note that theis table will not necessary capture all the events. You can find an Event Management (EM) master file
(Final Version) under the following Link: EM_full eventsEM_full eventsEM_full eventsEM_full events Field Code Changed
Formatted: Default Paragraph Font
Internal Short Description of Stream Owner Description of the Event Formatted: Indent: Left: 0"
Stream ID the event Formatted Table
EQ Send the
01 release
0 order to the
Depot
Empty
Release
order
Notification
(CH or MH)
(Full or
Empty)
Optional by
Country in

Business Blueprint
MH or CH
EQ EMPTY Equipment The container is reserved to a shipper

01 RESERVE
5 TO SHIPPER
IM Export Gate Equipment Export empty container is gated out empty

01 out empty from depot
0 from Depot - by TSP (Transport Service Provider) to take
EQ (GATE OUT to shipper location in case of Carrier haulage
02 DEPOT ) booking (CH)
0 (GATE OUT - The unit is physically picked up by the
SHIPPER) shipper for stuffing in case of Merchant
haulage booking (MH)
Expected Timing: at R/O limit date planned
and named on each Empty Release Order
EQ Gate in Equipment Gate in terminal full (MH)

04 Export Expected Timing: Before Terminal cut off
0 terminal full
(MH
booking)
GATE IN
FULL (EXP)
EQ END_STUFF Equipment The unit is stuffed at quay

09 ING Expected Timing: Before Terminal cutoff
0 date
EQ TSHIP_DISC Equipment The unit is discharged FULL at PTS to be

10 HARGED_F reloaded on another vessel to final
0 ULL destination
EQ TSHIP_GAT Equipment In transshipment, the discharged unit is

11 E_OUT moved out to be loaded from a different
0 quay (Gate out)
EQ TSHIP_GAT Equipment In transshipment, the unit is received from a

12 E_IN different quay to be reloaded (Gate in)
0
EQ TSHIP_LOA Equipment The unit is loaded on board FULL at PTS(the

13 D_FULL previous move is a TDF)
0

Business Blueprint
EQ START_UN Equipment Start of unloading process at quay

14 STUFFING
0
EQ END_UNST Equipment The unit is going to be unstuffed at quay

15 UFFING
0
EQ START_INS Equipment This event regards the container with status

16 PECTION MEI.
0 The event notification represents the
starting of the complete inspection
Expected Timing: at gate in date
EQ END_INSPE Equipment This event regards the container with status

17 CTION MEI.
conclusion of the complete inspection and in
the message notification will be present the
new status of the container.
Expected Timing: at gate in date
EQ REPAIR_ST Equipment This event regards the container with status

18 ART MED.
beginning of the container repair process
(This event corresponds to the current MIR
LARA movement).
EQ REPAIR_EN Equipment This event regards the container with status

19 D MIR.
0 The event notification represents the end of
the container repair process (This event
corresponds to the current RWM LARA
movement or all other moves not in MEI,
MIR, MED, CLN/CLN/TLN/TLY/WCM/WRF).
EQ WAREHOU Equipment The unit is used for Warehousing (Standard,

20 SE_USING Flat Rack...). It's not a repair move
0
EQ WAITING_D Equipment Awaiting declaration lessor

21 ECLARATIO
0 N
EQ WAITING_C Equipment Waiting for claim empty

22 LAIM_EMPT
0 Y
EQ WAITING_S Equipment Instruction 'to be sold' (empty); the unit is

23 ALE_EMPT unavailable

Business Blueprint
0 Y
EQ WAITING_S Equipment Instruction 'to be sold' (full);

24 ALE_FULL
0
EQ WAITING_S Equipment Instruction 'to be scrapped', the unit is

25 CRAP unavailable
0
EQ WAITING_O Equipment Instruction 'to be off hired', the unit is

26 FF_HIRE_E unavailable
0 MPTY
EQ OWNED_U Equipment Owned units that have been reported lost

27 NIT_LOST
0
EQ LEASED_U Equipment Leased units that have been reported lost to

28 NIT_LOST the lessor
0
EQ OWNED_U Equipment Damaged owned units reported to be no

29 NIT_DAMA longer sound (carcass)
0 GED
EQ LEASED_U Equipment Damaged leased units reported to be no

30 NIT_DAMA longer sound (carcass)
0 GED
EQ OFF_HIRE_ Equipment Off hire status for units that have been
31 UNIT damaged, lost or stolen
0
EQ SOLD_UNIT Equipment The container has been sold but not picked
31 up by the client yet
0
EQ OFF_HIRE_ Equipment The client physically picks up the container

31 SOLD_EMP empty at depot (off hire)
0 TY
EQ OFF_HIRE_ Equipment The client physically picks up the container

31 SOLD_FULL full at depot (off hire)
0
EQ OFF_HIRE_ Equipment Leased containers: the unit is returned to the

31 EMPTY lease company EMPTY
0 SOC containers: the Empty container is
picked up by the client at port or inland
station

Business Blueprint
EQ OFF_HIRE_ Equipment Leased containers: the unit is returned to the

31 FULL lease company FULL
0 SOC containers: the full container is picked
up by the client at port or inland station
EQ ON_HIRED Equipment The unit to be on-hired is:

31 - a FULL/EMPTY carrier owned/leased (LR
0 ref)
- an EMPTY misused unit from a third party
(MF ref)
- an EMPTY unit subleased from a third party
(LR ref)
- a FULL/EMPTY shipper owned
container(SOC)
EQ SUBLEASE Equipment The unit is sub-leased out EMPTY to a third

31 OUT EMPTY party (SL reference) or it has been misused
0 by a third party (MT ref)
EQ REDELIVER Equipment The unit is redelivered EMPTY by the lessee

31 ED EMPTY after a Sublease out
0
EQ SUBLEASE Equipment The unit is subleased out FULL (SL

31 OUT FULL reference)
0
EQ REDELIVER Equipment The unit is redelivered FULL by the lessee

31 ED FULL after a sublease out
0
EQ GATE OUT Equipment The unit is transferred EMPTY from port <>
32 EMPTY (in to depot or from depot <> to another depot
0 transfer) (Gate out) between different points.
EQ LOAD_EMP Equipment Container is empty on rail car ready for

33 TY_INLAND departure.
0
EQ UNLOAD_E Equipment Container is empty and is unloaded from rail

34 MPTY_INLA car.
0 ND
EQ TO_BE_LO Equipment The container is empty billed ready to load

35 ADED_EMP on a train from inland locations to ports.
0 TY_INLAND Next move is MIT.
EQ GATE_IN_E Equipment The unit arrives Empty at terminal ready to

36 MPTY_TER be loaded (Gate in)
0 MINAL
EQ LOAD_EMP Equipment The unit is loaded on board EMPTY at POL

Business Blueprint
37 TY_ON_BO
0 ARD
EQ TSHIP_DISC Equipment The unit is discharged EMPTY at PTS to be

38 HARGED_E reloaded on another vessel to final
0 MPTY destination
EQ TSHIP_LOA Equipment The unit is loaded on board EMPTY at PTS

39 D_EMPTY_
0 ON_BOARD
EQ DISCHARGE Equipment The unit is discharged EMPTY at POD

40 D_EMPTY
0
EQ IDLE letter Equipment Idle letter has been sent, the container stay
41 sent at the terminal
0
EQ CONTAINE Equipment The full container is damaged and needs to

42 R DAMAGE be changed.
0 Unstuffing of a container to transfer the
cargo into another unit (damage or customs
reasons)
CONTAINERS ISSUES could be: Leakage,
damage, reefer down
EQ CUSTOMS_ Equipment The container has been seized FULL by the

43 EXP_FULL local authorities (customs, quarantine,
0 police, court,,,) at export
EQ CUSTOMS_I Equipment The container has been seized FULL by the

44 MP_FULL local authorities (customs, quarantine,
0 police, court,,,) at import
EQ CUSTOMS_ Equipment The container has been seized EMPTY by

45 EMPTY the local authorities (customs, quarantine,
0 police, court,)
EQ Wrong Equipment The container has been returned in a

46 return different location than the expected one
0 location

Business Blueprint
Internal Stream Short Description of the event DESCRIPTION OF THE EVENT Formatted: English (United States)
Stream Owner Formatted: English (United States)
ID Formatted Table
EQ010 Equipment Send the release order to the Depot Release order is sent to the depot to have container Formatted: English (United States)
Empty Release order Notification ready, and to the shipper (or to the Transport Service
(CH or MH) (Full or Empty) Provider in case of CH) in order to named depot place
Optional by Country in MH or CH and appointment to pick the empty.
EQ015 Equipment EMPTY RESERVE TO SHIPPER The container is reserved to a shipper Formatted: English (United States)
IM010 Equipment Export Gate out empty from Depot Export empty container is gated out empty from depot Formatted: English (United States)
EQ020 (GATE OUT DEPOT ) - by TSP (Transport Service Provider) to take to shipper
location in case of Carrier haulage booking (CH)
- The unit is physically picked up by the shipper for
stuffing in case of Merchant haulage booking (MH)
IM020 Equipment Export Arrival Empty at Shipper Export CH Transport Service Provider arrived at shipper Formatted: English (United States)
location with empty container
IM040 Equipment Export Depart Full from Shipper Export CH container full departed from shipper location Formatted: English (United States)
premise
IM060 Equipment Export Gate In Full at Ramp Export CH container full gated in by Transport Service Formatted: English (United States)
EQ030 Provider at ramp - rail or barge
The unit arrives full in the inland station to be
transferred
IM070 Equipment Export Loaded Full on Rail/Barge Export CH full container loaded on train/barge/truck Formatted: English (United States)
/truck
IM090 Equipment SIGHTING (EXP) / (inland track and The container is moving on the rail/barge road at export Formatted: English (United States)
trace) showing each 'location' ( town/city/station.) it passes
through (last seen status)
IM100 Equipment Export Arrived Full at Ramp Export CH full container arrives at ramp on Formatted: English (United States)
train/barge/truck
IM110 Equipment Export Unloaded Full at ramp Export CH full container unloaded from train/barge Formatted: English (United States)
Rail/Barge / Truck /truck
IM120 Equipment Export Gate out Full From Ramp Export CH full Container gated out from ramp via Formatted: English (United States)
Transport service provider
IM130 Equipment Export Gate in Full at Off Dock Export CH full container is gated in at off dock deport Formatted: English (United States)
Depot (optional)

Business Blueprint
Stream Owner Formatted Table
ID Formatted: English (United States)
IM140 Equipment Export Gate out Full from Off Dock Export CH full container is gated out from off dock Formatted: English (United States)
Depot depot headed for terminal (optional)
IM150 Equipment Export Arrival Full Rail at Terminal Export CH full container arrives at on dock rail/barge Formatted: English (United States)
ramp
IM160 Equipment Export Unloaded Full at Terminal Export CH full container unloaded from train/barge Formatted: English (United States)
Train / Barge /truck /truck on terminal
IM170 Equipment Gate in Export Terminal Full Gate in terminal full (CH) Formatted: English (United States)
EQ040 GATE IN FULL (EXP)
EQ040 Equipment Gate in Export terminal full (MH Gate in terminal full (MH) Formatted: English (United States)
booking)
GATE IN FULL (EXP)
EQ050 Equipment Container loaded on board The unit is loaded on board FULL at POL Formatted: English (United States)
LOAD_FULL_ON_BOARD
NaO220 Equipment Container discharged Container have been well discharge Formatted: English (United States)
DISCHARGE_FULL
IM190 Equipment Import Gate out port full (CH) Import CH container moved out of port by TSP - truck. Formatted: English (United States)
Gate out to consignee or to Off Dock Terminal to be
loaded on a train / barge
IM120 Equipment Import Loaded On Dock Rail Full Import CH loaded on rail on dock and ready for transport Formatted: English (United States)
(optional) on the rail
IM130 Equipment Import Depart On Dock Rail Full Import CH departure on rail toward inland Formatted: English (United States)
(optional) destination/ramp
IM140 Equipment Import Gate in Off Dock Full Import CH gate in by trucker at off dock Formatted: English (United States)
(optional) facility/depot/ramp
IM150 Equipment Import Gate out Off Dock Full Import CH gate out from full from off dock facility/depot Formatted: English (United States)
(optional) by truck
IM160 Equipment Import/export Gate in Off Dock Full Custom' choice to put the container in some place in the Formatted: English (United States)
Custom's choice world into an Off dock. after X days spent on terminal in
some place custom' move the box
IM170 Equipment Import Loaded at Ramp Full Import CH loaded on train/barge Formatted: English (United States)
If location is ramp

Business Blueprint
IM190 Equipment Import Arrival at Ramp Full Import CH full container arrival at rail/barge ramp Formatted: English (United States)
(intermediate ramp)
IM200 Equipment SIGHTING (IMP) / (inland track and The container is moving on the rail at import showing Formatted: English (United States)
trace) each town/city it passes through(last seen status)
IM210 Equipment Import Unload at Ramp Full Import CH full container unloaded at inland rail/barge Formatted: English (United States)
ramp
IM220 Equipment Import Gate out Ramp Full Import CH full container gates out from ramp by truck Formatted: English (United States)
IM230 Equipment Import Gate in Ramp Full Import CH full container gates in from ramp by truck Formatted: English (United States)
Container at Inland destination Import MH container arrived at its final destination
IM240 Equipment Import Gate out Full to Consignee Import CH full container is gated out from inland ramp Formatted: English (United States)
Container full to consignee (MH) via truck for last mile
IM250 Equipment Arrival Full at Consignee (Import) Import CH TSP truck arrives with full container at Formatted: English (United States)
consignee location
IM270 Equipment Pick of Empty from consignee or The customer has to be notified when the containers Formatted: English (United States)
customer associated to his bookings are Picked up empty from
Import Depart from Consignee consignee premises
Empty Import CH TSP truck departed with empty container
from consignee location
IM290 Equipment Import Gate in Depot Empty Event notification for GATE IN the deposit represents Formatted: English (United States)
EQ070 GATE_IN_DEPOT EMPTY the conclusion of the first "visual" inspection of the Formatted: English (United States)
container.
Empty container returned after Import clearance Formatted: English (United States)
EQ080 Equipment START_STUFFING Start of loading process at quay Formatted: English (United States)
EQ090 Equipment END_STUFFING The unit is stuffed at quay Formatted: English (United States)
EQ100 Equipment TSHIP_DISCHARGED_FULL The unit is discharged FULL at PTS to be reloaded on Formatted: English (United States)
another vessel to final destination
EQ110 Equipment TSHIP_GATE_OUT In transshipment, the discharged unit is moved out to be Formatted: English (United States)
loaded from a different quay (Gate out) Formatted: English (United States)
EQ120 Equipment TSHIP_GATE_IN In transshipment, the unit is received from a different Formatted: English (United States)
quay to be reloaded (Gate in) Formatted: English (United States)

Business Blueprint
EQ130 Equipment TSHIP_LOAD_FULL The unit is loaded on board FULL at PTS (the previous Formatted: English (United States)
move is a TDF) Formatted: English (United States)
EQ140 Equipment START_UNSTUFFING Start of unstuffing process at quay Formatted: English (United States)
EQ150 Equipment END_UNSTUFFING The unit has been unstuffed at quay Formatted: English (United States)
EQ160 Equipment START_INSPECTION This event regards the container with status MEI. Formatted: English (United States)
The event notification represents the starting of the
complete inspection
EQ170 Equipment END_INSPECTION This event regards the container with status MEI. Formatted: English (United States)
The event notification represents the conclusion of the
complete inspection and in the message notification will
be present the new status of the container.
EQ180 Equipment REPAIR_START This event regards the container with status MED. Formatted: English (United States)
The event notification represents the beginning of the
container repair process (This event corresponds to the
current MIR LARA movement).
EQ190 Equipment REPAIR_END This event regards the container with status MIR. Formatted: English (United States)
The event notification represents the end of the
container repair process (This event corresponds to the
current RWM LARA movement or all other moves not in
MEI,MIR,MED,CLN/CLN/TLN/TLY/WCM/WRF).
EQ200 Equipment WAREHOUSE_USING The unit is used for Warehousing (Standard, Flat Rack...) Formatted: English (United States)
It's not a repair move
EQ210 Equipment WAITING_DECLARATION Awaiting declaration lessor Formatted: English (United States)
EQ220 Equipment WAITING_CLAIM_EMPTY Waiting for claim empty Formatted: English (United States)
EQ230 Equipment WAITING_SALE_EMPTY Instruction 'to be sold' (empty); the unit is unavailable Formatted: English (United States)
EQ240 Equipment WAITING_SALE_FULL Instruction 'to be sold' (full); Formatted: English (United States)
EQ250 Equipment WAITING_SCRAP Instruction 'to be scrapped', the unit is unavailable Formatted: English (United States)
EQ260 Equipment WAITING_OFF_HIRE_EMPTY Instruction 'to be off hired', the unit is unavailable Formatted: English (United States)
EQ270 Equipment OWNED_UNIT_LOST Owned units that have been reported lost Formatted: English (United States)

Business Blueprint
EQ280 Equipment LEASED_UNIT_LOST Leased units that have been reported lost to the lessor Formatted: English (United States)
EQ290 Equipment OWNED_UNIT_DAMAGED Damaged owned units reported to be no longer sound Formatted: English (United States)
(carcass)
EQ300 Equipment LEASED_UNIT_DAMAGED Damaged leased units reported to be no longer sound Formatted: English (United States)
(carcass)
EQ310 Equipment OFF_HIRE_UNIT Off hire status for units that have been damaged, lost or Formatted: English (United States)
stolen
EQ310 Equipment SOLD_UNIT The container has been sold but not picked up by the Formatted: English (United States)
client yet
EQ310 Equipment OFF_HIRE_SOLD_EMPTY The client physically picks up the container empty at Formatted: English (United States)
depot (off hire)
EQ310 Equipment OFF_HIRE_SOLD_FULL The client physically picks up the container full at depot Formatted: English (United States)
(off hire)
EQ310 Equipment OFF_HIRE_EMPTY Leased containers: the unit is returned to the lease Formatted: English (United States)
company EMPTY
SOC containers: the Empty container is picked up by the
client at port or inland station
EQ310 Equipment OFF_HIRE_FULL Leased containers: the unit is returned to the lease Formatted: English (United States)
company FULL
SOC containers: the full container is picked up by the
client at port or inland station
EQ310 Equipment ON_HIRED The unit to be on-hired is: Formatted: English (United States)
- a FULL/EMPTY carrier owned/leased (LR ref)
- an EMPTY misused unit from a third party (MF ref)
- an EMPTY unit subleased from a third party (LR ref)
- a FULL/EMPTY shipper owned container(SOC)
EQ310 Equipment SUBLEASE OUT EMPTY The unit is sub-leased out EMPTY to a third party (SL Formatted: English (United States)
reference) or it has been misused by a third party (MT
ref)
EQ310 Equipment REDELIVERED EMPTY The unit is redelivered EMPTY by the lessee after a Formatted: English (United States)
Sublease out
EQ310 Equipment SUBLEASE OUT FULL The unit is subleased out FULL (SL reference) Formatted: English (United States)

Business Blueprint
Stream Owner Formatted: English (United States)
ID Formatted Table
EQ310 Equipment REDELIVERED FULL The unit is redelivered FULL by the lessee after a Formatted: English (United States)
sublease out
EQ320 Equipment GATE OUT EMPTY (in transfer) The unit is transferred EMPTY from port <> to depot or Formatted: English (United States)
from depot <> to another depot (Gate out) between
different points.
EQ330 Equipment LOAD_EMPTY_INLAND Container is empty on rail car ready for departure. Formatted: English (United States)
EQ340 Equipment UNLOAD_EMPTY_INLAND Container is empty and is unloaded from rail car. Formatted: English (United States)
EQ350 Equipment TO_BE_LOADED_EMPTY_INLAND The container is empty billed ready to load on a train Formatted: English (United States)
from inland locations to ports. Next move is MIT.
EQ360 Equipment GATE_IN_EMPTY_TERMINAL The unit arrives Empty at terminal ready to be loaded Formatted: English (United States)
(Gate in)
EQ370 Equipment LOAD_EMPTY_ON_BOARD The unit is loaded on board EMPTY at POL Formatted: English (United States)
EQ380 Equipment TSHIP_DISCHARGED_EMPTY The unit is discharged EMPTY at PTS to be reloaded on Formatted: English (United States)
another vessel to final destination
EQ390 Equipment TSHIP_LOAD_EMPTY_ON_BOARD The unit is loaded on board EMPTY at PTS Formatted: English (United States)
EQ400 Equipment DISCHARGED_EMPTY The unit is discharged EMPTY at POD Formatted: English (United States)
EQ410 Equipment IDLE letter sent Idle letter has been sent, the container stay at the Formatted: English (United States)
terminal
EQ420 Equipment CONTAINER DAMAGE The full container is damaged and needs to be changed. Formatted: English (United States)
Unstuffing of a container to transfer the cargo into
another unit (damage or customs reasons)
CONTAINERS ISSUES could be: Leakage, damage, Formatted: English (United States)
reefer down...
EQ430 Equipment CUSTOMS_EXP_FULL The container has been seized FULL by the local Formatted: English (United States)
authorities (customs, quarantine, police, court,,,) at
export
EQ440 Equipment CUSTOMS_IMP_FULL The container has been seized FULL by the local Formatted: English (United States)
authorities (customs, quarantine, police, court,,,) at
import
EQ450 Equipment CUSTOMS_EMPTY The container has been seized EMPTY by the local Formatted: English (United States)
authorities (customs, quarantine, police, court,,,).
EQ460 Equipment Wrong return location The container has been returned in a different location Formatted: English (United States)
than the expected one

Business Blueprint

Business Blueprint
8 Business Process and Solution Design
8.1 Process Equipment Master Data Management (5.1.1.1.)
8.1.1 Process Description
Master data is the core data that is essential to operations in a specific business or business unit. Equipment master data consists
of technical specifications of a container or a group of containers. Master data shall also be maintained for accessorial equipment
like Gensets, Rolling floors, or Chassis.
Caution
Master data management is out of scope for SAP in this blueprint document. This section is maintained only to facilitate
CMA CGM understanding of the master data changes that shall be triggered by other processes.

Business Process and Solution Design AG or an SAP affiliate company. All rights reserved. 59
Business Blueprint
8.1.2 Business Process Diagrams
Figure 777 : Equipment Master Data Management

Business Blueprint
8.1.3 Requirement List
The following requirements apply to the overall process:
ID Title Description Acceptance Criteria Realization Gap
EQP- Authorizations for It shall be defined which - Manage master data Implementation 2564
MD- Container Master Master Data can be accessed authorizations for
007 Data and / or changed by different display / change rights
roles within the logistics team - for standard and
for example, agencies, regional 'additional' fields
office, head office, and so on. (created by
enhancements )
EQP- Authorizations for It shall be possible to restrict - Manage Implementation 2564

MD- Container Residual access to container authorizations for
008 Value depreciation value and residual rights to display
value through maintenance of container related
relevant authorizations within financial information
the logistics team - for (e.g. depreciation)
example, agencies, regional
office, head office, etc.
EQP- Integration with KIRA is the legacy system used - Master data (Vessel Implementation 1284
MD- KIRA - Master Data for management of Reefer kits name, container
009 (spare parts for reefers on numbers and
board vessels). An interface geographical location)
between KIRA and SAP shall be
established to allow exchange
of master data.
EQP- Volume of In-Fleet It shall be possible to have - Report of on-hired Implementation 1643 (under BI
MD- Events visibility on the volume of containers per time scope)
018 containers on-hired with on- period with pick-up
hire date and place. date & place
(this requirement is under BI
scope)
EQP- Volume of Out-of- It shall be possible to have - Volume of containers Implementation 1643 (under BI
MD- Fleet Events visibility on the volume of off-hired, sold, or scope)
019 containers taken out of fleet declared in Total Loss
with details on date and place. per time period with
(this requirement is under BI date & place
scope)
Additional process step specific requirements are listed with the related process step.

Business Blueprint
8.1.4 Process Step Detailed Requirements & Solution
ID Process Step Description Solution Solution

Component Object
5.1.1.1.1. Create equipment size- Size-Type is a CMA CGM specific code for a NA NA
type master data group of containers of a particular size and
typology.
5.1.1.1.2. Maintain equipment Master data for container size-type is updated NA NA

size-type master data in case of changes in technical specifications
like weight, and so on.
5.1.1.1.3. Create series master Series is a group or number range of NA NA

data containers. Series refers to a group of
containers belonging to a certain number
range and having some common
characteristics, for example, procurement
contract, size-type, etc.
5.1.1.1.4. Maintain series master Series is a group or number range of NA NA

data containers. Master data for container series is
updated typically when additional or new
information related to the series is available.
5.1.1.1.5. Create equipment Equipment passport is the master data object NA NA

passport master data for an individual container and is created when
the container number is known. Technical
characteristics of the container are copied
from series to container passport at time of its
creation if series exists. If no series then master
data already existing for the size-type are
copied into the container passport at the time
of its creation.
5.1.1.1.6. Maintain equipment Some information maintained for the NA NA

passport master data container in the passport is updated as it
becomes available or changes, for example:
- Information about container grade
- Information about recovery, maintenance &
repair, and so on.
8.1.4.1 Create Equipment Size-Type Master Data
Size-type is a CMA CGM specific code for a group of containers of a particular size and typology, for example, 20ST is used for 20
feet standard dry container. New size-type master data is created each time a new container type enters the fleet. A standard set
of technical specifications are maintained for each size-type for example, volume, weight, TEUs, units of measure, and so on.

Business Blueprint
Requirements
EQP- Creation and Technical specifications for containers - (Manually) Maintain Implementation 42
MD- Maintenance of shall be created and managed at size- size-type master data
002 Technical type level. for containers in the
Specifications at Size- system containing
Type Level details of standard
technical specifications.
EQP- Additional fields for It shall be possible to enter additional - Possibility to store Implementation 42
MD- optional attributes characteristics into the container size- optional attributes into
006 within container type master data, thereby, reducing size-type master (to
size/types the number of size-types maintained avoid more than one
in the system (leading with n:n size-type for the same
relationship between ST/ISOCODE ISO Code)
(See EQP-MD-012)
EQP- Container Size-Type It shall be possible to maintain specific - Families of size/type Implementation 42
MD- Based on Business container size-types for different shall be maintained
011 Processes processes. based on business
processes (Port Call
Operation, Imbalance
Management, Business
controlling)
- When creating a new
size/type in the Master
data, this data shall be
allocated to a family in
each Business Process
grouping
Example: 20' Dry family
contains size-types 20'
ST, 20' SH, 20' HC, etc.
for the process of
Imbalance
management.
- Each group may
contain several levels of
hierarchy (For example:
a 20HC shall be under
group level 1 High
Cubes and under group
level 2 Dries.
EQP- ISO Code - Size-Type It shall be possible to maintain a - A pre-defined Implementation 2570
MD- Relationship relationship between ISO codes and conversion table shall
012 container size-type (company specific) be able to translate ISO
using a conversion or mapping table. codes into parallel size-

Business Blueprint

(Relation n:n between ISOCODE / type as maintained by
size-type (see Reefer use case) CMA-CGM
8.1.4.2 Maintain Equipment Size-Type Master Data
Master data for container size-type shall be updated in case of changes in technical specifications like weight, and so on.
Requirements
EQP- Creation and Technical specifications for containers - (Manually) Maintain Implementation 42
MD- Maintenance of shall be created and managed at size-type master data
002 Technical Size/Type level. for containers in the
Specifications at Size- system containing
Type Level details of standard
technical specifications.
8.1.4.3 Create Series Master Data
Series is a group or number range of containers. Series refers to a group of containers often belonging to a certain number range,
and having some common characteristics like size-type and linked to an object (for example a purchasing contract or call-off).
Series master data shall be created when:

Purchase orders for purchase of owned equipment are created, The series (with its technical specifications per size-type) is
mentioned on the purchase order.
Requirements
EQP- Creation and Technical specifications for - Possibility to create Implementation 2571
MD- Maintenance of containers shall be created and series master data by
043 Technical managed at series level where the copying all technical
Specifications at series is a number range / group of specifications maintained
Series Level containers linked to an object (e.g. in the respective size-
a contract or a call off) type for that series.
- Ability to maintain any
additional technical

Business Blueprint

specifications for the
series.
8.1.4.4 Maintain Series Master Data
Series is a group or number range of containers. Master data for container series is maintained or updated typically when
additional or new information related to the series is available.
Requirements
EQP- Creation and Technical specifications for - Possibility to create Implementation 2571
MD- Maintenance of containers shall be created and series master data by
043 Technical managed at series level where the copying all technical
Specifications at series is a number range / group of specifications maintained
Series Level containers linked to an object (e.g. a in the respective size-
contract or a call off) type for that series.
- Ability to maintain any
additional technical
specifications for the
series.
EQP- Mass Update of It shall be possible to update - Ability to upload a Implementation 42,
MD- Container Master container master data in mass Spreadsheet to update in 2655
004 Data through the use of filters (e.g. age, mass some fields of
contract, number range / series, etc.). passports for a list of
specific containers
8.1.4.5 Create Equipment Passport Master Data
Equipment passport is the master data object for an individual container and is created when the container number is known.
Technical characteristics of the container shall be copied from series to container passport at time of its creation (if series exists). If
no series exists, the master data existing for the size-type shall be copied into the container passport at the time of its creation.
Equipment passport is typically created when a container is added to CMA CGM fleet for the first time. For example;
Adding newly purchased owned equipment to fleet (5.1.1.3.3.3. On-hire owned equipment)
Adding leased or sub-leased containers to fleet (5.1.1.4.3.5. On-hire leased equipment)
Adding found containers to fleet (5.1.1.3.3.3. On-hire owned equipment)
Adding shipper-owned containers (SOC) to fleet

Business Blueprint
Requirements
EQP- Management of It shall be possible to store container - Maintain link of the Implementation 42
MD- Container Certificates certificates in an electronic format storage location of the
001 Storage Link to and maintain the location link on the container certificate (on
Container Master container passport. the legacy document
Data management
systemDMS)) into the
container passport
EQP- Creation and Technical specifications for - Container passport Implementation 42

MD- Maintenance of containers shall be created and shall copy standard
003 Technical managed at container level. technical specifications
Specifications at based on series it
Container Level belongs to as well as the
size-type
- It shall be possible to
maintain additional
/specific specifications
in addition to the
standard size-type
specifications (e.g.
bamboo floor, orange
color, etc.)
EQP- Flag for Branded It shall be possible to identify blue - Ability to maintain a Implementation 42
MD- Containers containers with CMA-CGM Logo by 'brand' flag in the
031 management of a 'brand' flag in the container master data
container passport. to identify containers
with a blue color and
CMA-CGM logo.
- Ability to filter for such
containers based on the
flag.
EQP- Master Data for It shall be possible to maintain - Ability to maintain Implementation 42
MD- Reefers specific master data for Reefers at reefer specific master
033 the container level. data such as:
o O2 level
o CO2 level
o Humidity
o Set point
Temperature
o Supply temperature
o Return temperature
- Ability to link this
information to a
date/hour (as
information is received

Business Blueprint

almost every hour) (in
case of availability of a
tracking device the
tracking data is
transferred to a legacy
system TRACKSENSE
which in the future may
be connected via an
interface to maintain
this information into
the container passport)
EQP- Master data for It shall be possible to maintain - Ability to maintain Implementation 42
MD- Gensets, Rolling master data for different types of master data for
034 Floors & Chassis equipment. e.g. Gensets, Rolling Gensets, Rolling Floors
Floors and Chassis and Chassis
EQP- Shipper Owned It shall be possible to maintain - Ability to maintain SAP Standard
MD- Containers (SOC) master data for shipper owned master data for shipper
038 containers. owned containers with
container number,
size/type and main
characteristics linked to
it for operational
purpose (weight, size,
etc)
EQP- Activation and It shall be possible to add or remove - Create master data for Implementation 2726,
MD- Deactivation of leased container (master data) from leased container when 2717
051 Leased (and Sub- fleet at the time of container 'on-hire' it is added to the fleet
Leased) Container and 'off-hire' respectively. (on-hired)
Master Data - Deactivate master
data for lease container
when it is removed from
the fleet (off-hired)
EQP- Activation and It shall be possible to add or remove - Create master data for Implementation 2811
MD- Deactivation of owned container (master data) from owned container when
052 Owned Container fleet at the time of container 'on-hire' it is added to the fleet
Master Data and 'off-hire' respectively. (on-hired)
- Deactivate master
data for owned
container when it is
removed from the fleet
(off-hired)
EQP- Container Number It shall be possible to maintain - Ability to use SAP Standard
MD- Format container numbers in the master container numbers
042 data, following the ISO 6346 which are based on:
identification numbering. owner prefix of 3

Business Blueprint

digits+1 digit for unit
identification + a serial
number of 6 digits + a
check digit. For
example:
ABCD1234567.
- Ability to raise a
warning (except the
SOC and accessories)
when a container
master data is created
and the container
number does not meet
ISO standards.
- Ability to waive this
format requirement for
Shipper Owned
Containers (SOC) or
accessories.
8.1.4.6 Maintain Equipment Passport Master Data
Some information maintained for the container in the passport shall be updated as it becomes available or changes during the
operational life of the container. For example information about container grade, information about recovery files open for the
container, maintenance & repair files and damage flag, and so on.
The following processes require maintenance of equipment passport master data as per the following details:
Process Maintenance of Equipment Passport Master Data
5.1.1.3.5. Manage owned equipment sales When the status of the sales request is updated to in progress, the
reference number of this request is transferred to equipment passport
(field: Sales Reference) to indicate potential sale of the container
If the sale is canceled, the reference number of the sales request is
removed from equipment passport (field: Sales Reference)
In case of equipment sale, the passport is deactivated after the sold
container is released from the depot (gate-out)
5.1.1.4.1. Manage leased equipment contracts At the time of lease contract expiry, if the purchase option is exercised,
the containers are added to the fleet as owned. All relevant master data
are updated at this point in time (cost center, contract / call-off
reference, fields required to create the asset in the right asset class, and
so on)

Business Blueprint
Process Maintenance of Equipment Passport Master Data

If the decision to return a leased container is made (before, or at the
time of contract expiry) the equipment is returned to the lessor during
the pre-agreed build-down period after contract expiry lessor during the
pre-agreed build down period after contract expiry at which point in
time the equipment master data is deactivated.
5.1.1.5.1. Manage sub-lease-from contracts If the decision to return a leased container is made (before, or at the
time of contract expiry), the equipment is returned to the lessor during
the pre-agreed build down period after contract expiry at which point in
time the equipment master data is deactivated.
5.1.1.7.3. Manage declaration of total loss For owned equipment, after declaration of total loss, the container
passport is deactivated.
For leased equipment, after declaration and payment of total loss
(status total loss paid), the container passport is deactivated.
5.1.1.7.4. Manage found equipment If master data for the found container already exists in the system, it is
reactivated.
5.1.4.1.2. Manage MnR contract execution After opening of an MnR file, the file number is transferred via an
interface from iMars to SAP and stored in a dedicated field in the
container passport
After empty damaged status Damage flag is activated to indicate
damaged container.
After correction of false damage, Damage Flag is removed from
container passport.
Whenever a repair estimate related to a damaged container is approved
in iMars (iMars status: estimate approved), the Damage flag in the
passport is checked for activation
Whenever a repair estimate related to a container is rejected in iMars
(iMars status- rejected to be sold), the Damage flag in the passport is
activated.
Information about preparation work on container to trigger an update of
container grade
5.1.4.2.1. Open recovery file After opening of recovery file, the recovery file number is transferred via
an interface from iRecovery to SAP and stored in a dedicated field in the
container passport
Caution
Please note that the statuses or eventsor events maintained at the container level are not described here.
Requirements

Business Blueprint
EQP- Maintenance of Information about the - Container passport Roll-in for FBS
MD- Container Grade container grade shall be shall include
005 included in the container information about
master data. It shall be the High-Level
possible to update the container grades as
grade as the condition of follows: A: Top
the container changes. Grade, B: Food
Grade, C: General
Cargo, D: Scrap.
- Default grade
assigned at the time
a new container is
added to fleet is Top
Grade A. Depot unit
younger than 4
years, Grade B (Food
Grade), depot units
older than 4 years:
Grade C (General
Cargo). In general,
Grade will be kept
from previous cycle
(full or empty)
- Container passport
shall include a
second tier grade
(subset of high-level
grade) which is
specific to local
customer
requirements e.g. a
Food Grade
container is grade B;
and a Food Grade
prepared for
customer Danone is
B-DA.
EQP- Container Off-Hire It shall be possible to mark - Mark container to Implementation 42

MD- Status a container to be off-hired be off-hired with a
010 with specific statuses (To- specific status (To-
Be Off Hired / Eligible for Be Off Hired /
Off-Hire) and maintain the Eligible for Off-Hire)
status in the passport. in the passport.
- Ability to mass
update off-hire
status at container
level using filters (for

Business Blueprint

example: set all
containers aged 8
years as 'to be off-
hired') (covered by
EQP-MD-004)
EQP- Information About It shall be possible to - Ability to reserve a Implementation 42

MD- Reserved Containers identify if a container is container for a
014 reserved for a particular specific customer
customer / purpose (e.g. - Ability to identify a
VIP customer or specific reserved container
trade), and the relevant (display details of
details of the reservation active reservation in
(e.g. customer name). container passport)
EQP- Manage Valid and It shall be possible to have - Report showing the Implementation 2573
MD- Overdue Container visibility on the containers list of containers
016 Certificates with valid certification with valid ACEP/CSC
including expiry dates, and certification, with
well as the containers with the last certification
overdue certification. date and location
- Report showing the
list of containers
with overdue
ACEP/CSC
certification
(certification was not
performed in the last
30 months).
EQP- Damage Flag It shall be possible to - Activate 'damage' Implementation 42

MD- maintain a flag in the flag in passport
030 container passport (to when the container
identify it as a damaged gates in at depot and
container (until the repair is is assigned any
completed). status from the
'empty damaged'
group of statuses
- Deactivate the
'damage' flag in the
passport when the
repair is completed
EQP- Container Sales It shall be possible to mark - Mark container to Implementation 42

MD- Status a container to be sold with be sold with a
032 specific statuses (To-Be specific status in the
Sold / Eligible for Sale) and passport.
maintain the status in the - Ability to mass
passport. update sale status at
container level using

Business Blueprint

filters
EQP- Reefer Data It shall be possible to attach - Ability to receive Implementation 42

MD- recorder History and maintain reefer data data recorder history
035 recorder history at the via email and
container level. manually attach to
container passport
EQP- Container Sales It shall be possible to - Ability to copy the Implementation 42

MD- Reference maintain a 'sales reference' sales reference into
037 in the container master the dedicated field in
data (passport) when there container master
is a corresponding sales data when the status
process in progress. of the sales request
for that container is
set to 'in progress'
EQP- Management of It shall be possible to - Manage ana Implementation 42

MD- ACEP/CSC manage the validity of validity date for the
039 Certification Validity ACEP/CSC Certification at ACEP/CSC
Information the container level. certification at the
container level
- For a new
container, this
information is
available only after
first gate-in into aan
ACEP/CSC certified
depot which has to
be performed within
30 months.
EQP- Recovery File It shall be possible to - Ability to store Implementation 42

MD- Reference maintain the reference of recovery file
040 the recovery file at the reference on the
container level. container master for
an open recovery file
against the
container number
- Ability to retain the
recovery file number
on the container
master until it is
replaced by another
(new) recovery file
opened for that
container
EQP- MnR File Reference It shall be possible to - Ability to store Implementation 42

MD- maintain the reference of MnR file reference

Business Blueprint

041 the MnR file at the on the container
container level. master for an open
MnR file against the
container number
MnR file number on
the container master
until it is replaced by
another (new) MnR
file opened for that
container
EQP- Creation and Technical specifications for - Container passport Implementation 42

MD- Maintenance of containers shall be created shall copy standard
003 Technical and managed at container technical
Specifications at level. specifications based
Container Level on series it belongs
to as well as the size-
type
- It shall be possible
to maintain
additional /specific
specifications in
addition to the
standard size-type
specifications (e.g.
bamboo floor,
orange color, etc.)
EQP- Container Master It shall be possible to raise - Ability to raise a SAP 42

MD- Data Creation Check an alert when container warning (except the StandardImplementation
044 based on Container number does not match the SOC and
Number predefined name format.It accessories) when a
StandardsContainer shall be possible to raise an container master
Master Data alert when container data is created and
Creation Block number does not match the the container
based on Container predefined name format, number does not
Number Standards and to block creation of meet ISO
master data until this standards.- Ability to
requirement is met. raise a warning
(except the SOC and
accessories) when a
container master
data is created and
the container
number does not
meet ISO standards.
- Ability to block
master data /

Business Blueprint

passport creation if
the container
number does not
meet this criteria.
EQP- Update of Container Information about the - Second tier grade Implementation 42
MD- Grade container grade shall be information is
045 included in the container removed as
master data. It shall be container leaves the
possible to update the area (for which the
grade as the condition of specific grade was
the container changes. assigned)
- Container grade is
updated over the life
of the container
based on its
condition, either via
EDI messages, after
repair completion or
excel uploads (from
depots)
EQP- Flag for Branded It shall be possible to - Ability to maintain Implementation 42

MD- Containers identify blue containers a 'brand' flag in the
031 with CMA-CGM Logo by container master
management of a 'brand' data to identify
flag in the container containers with a
passport. blue color and CMA-
CGM logo.
- Ability to filter for
such containers
based on the flag.
EQP- Equipment Contract It shall be possible to - Ability to maintain Implementation 42, 2655,
MD- Reference maintain the relevant and update primary 3003
050 contract reference(s) contract reference
(purchasing / leasing for the container in a
contract) on the container custom field in the
passport (master data) container master
It shall be possible to data (Primary
maintain the relevant Contract Reference)
contract reference - Ability to maintain
(purchasing / leasing and update
contract) on the container secondary contract
passport reference for the
container in a
customer field in the
container master
data (Secondary
Contract Reference).

Business Blueprint

e.g. the reference of
financial lease
contract for owned
equipment, the
reference for sub-
lease-to contract for
a leased container.
- Ability to retain
history of changes to
the fields
- Ability to mass
update the fields by
a filter (e.g. contract
reference, number
range, etc.)- Ability
to maintain and
update contract data
for the container in a
custom field in the
container master
data
- Ability to retain
the field
EQP- Update of Total It shall be possible to - Ability to update Implementation 2584

LEAS- Loss Status for manage container status the container status 2613
005 Leased Containers during the total loss to 'Total Loss Formatted: SAP_ScreenElement
declaration process with Declared' with the
the relevant status updates date of declaration
triggered at different points and the last known
in the process. location (at approval
of total loss purchase
order for leased
container, at time of
declaration in
iRecovery system for
owned container -
tracking move in as-
is: TLN/TLY for lost
or idle containers,
and CLY/CLN for
constructive total
loss)
- Ability to update
the container status
to 'Total Loss Invoice Formatted: SAP_ScreenElement
Received/ Paid' at

Business Blueprint

the time of lessor
total loss invoice
entry in finance
(tracking move in as-
is: MWI)
EQP- Integration with It shall be possible to - Information about Implementation 54

M&R- iMars for Exchange establish an interface 'preparation' work (Outbound
006 of Container Grade between SAP and the on container to ODI Flow),
Information legacy Maintenance & trigger an update of 52
Repair system (iMars) to container grade in (Inbound)
enable exchange of container master
information related to data (reflected in
container grade. container passport)
(information inflow /
outflow from iMars))
Note: Valid for
future release of
iMars. Details need
to be checked
EQP- Integration with It shall be possible to check - Whenever a repair Implementation 1138, 1852
M&R- iMars for Damage if the damage flag is estimate related to a
007 Flag Check activated in the container damaged container
passport based on specific is approved in iMars
statuses in iMars. (iMars status:
estimate approved),
the damaged flag in
the passport should
be activated (if not
already activated)
(information inflow
from iMars to SAP)
- Whenever a repair
estimate related to a
container is rejected
in iMars (iMars
status- rejected to
be sold), the
damaged flag in the
passport should be
activated (if not
already activated)
(information inflow
from iMars to SAP)
- Correction of false
damage status in
iMars to deactivate

Business Blueprint

the damaged flag in
the container
passport in SAP
(information inflow
from iMars to SAP)
EQP- Default Status for It shall be possible to assign - After on-hire, the SAP Standard
SLEA- Flexible Lease, Sub- a default status to default status of
016 Lease From and One containers under flexible container under
Way lease, sub-lease-from and flexible lease or sub-
one-way contracts right lease-from contracts
after on-hire. to be set to 'eligible
for off-hire'
- After on-hire, the
default status of
one-way container
to be set to 'to be
off-hired'
EQP- Status update at It shall be possible to Ability to identify Implementation 2734, 2735
SLEA- release and identify the release and release of sub-lease-
017 redelivery of sub- redelivery of a container to container from
lease-to containers under sub-lease-to depot (gate-out)
arrangement, and to trigger - Ability to update
the predetermined status the container status
updates to reflect start of
'sub-lease-to' (at
depot gate-out)
- Ability to identify
redelivery of sub-
lease-to container at
depot (gate-in)
- Ability to update
the container status
to reflect end of
'sub-lease-to' (at
depot gate-in)
EQP- Activation and It shall be possible to add or - Create master data Implementation 2726, 2717
MD- Deactivation of remove leased container for leased container
051 Leased (and Sub- (master data) from fleet at when it is added to
Leased) Container the time of container 'on- the fleet (on-hired)
Master Data hire' and 'off-hire' - Deactivate master
respectively. data for lease
removed from the
fleet (off-hired)
EQP- Activation and It shall be possible to add or - Create master data Implementation 2811
MD- Deactivation of remove owned container for owned container

Business Blueprint

052 Owned Container (master data) from fleet at when it is added to
Master Data the time of container 'on- the fleet (on-hired)
hire' and 'off-hire' - Deactivate master
respectively. data for owned
removed from the
fleet (off-hired)
EQP- Equipment Contract It shall be possible to - Ability to maintain Implementation 42, 2655,
MD- Reference maintain the relevant and update primary 3003
050 contract reference(s) contract reference
(purchasing / leasing for the container in a
contract) on the container custom field in the
passport (master data) container master
data (Primary
Contract Reference)
- Ability to maintain
and update
secondary contract
reference for the
container in a
container master
data (Secondary
Contract Reference).
e.g. the reference of
financial lease
contract for owned
equipment, the
reference for sub-
lease-to contract for
a leased container.
- Ability to retain
the fields
- Ability to mass
update the fields by
a filter (e.g. contract
reference, number
range, etc.)
EQP- Classification of It shall be possible to - Ability to maintain Implementation 42, 3003

MD- Container classify containers as a 'class' field for each
053 Ownership Class owned, owned with bank container from a
loan, owned with financial drop down list of
lease, or leased. predefined values
- Ability to mass
update the field
using a filter such as

Business Blueprint

contract number,
container number
range, etc.
8.2 Process Equipment Fleet Strategy Management (5.1.1.2.)
Determination of equipment fleet strategy is a (manual) decision making process at the top management level of the company
supported closely by the Logistics head office.
Strategy determination relies on information in the form of reports and KPIs that facilitate management decision making.
Logistics relevant information and KPIs are collected and complied from multiple sources in the Logistics department, while
departments like Operations, Controlling and Finance may also provide valuable data as input.
This process focuses on the details relevant from the Logistics department viewpoint.

Business Blueprint
Figure 888 : Equipment Fleet Strategy Management
No requirements apply to the overall process. Process step specific requirements are listed with the related process step.

Business Blueprint

Component Object
5.1.1.2.1. Analyze commercial Commercial capacity refers to total available TEUs N/A N/A
capacity across all services and lines operated by CMA CGM,
as well as the capacity allocated on partner vessels
as per the VSA agreements. It is typically smaller
than the theoretical capacity available.
5.1.1.2.2. Analyze commercial Commercial budget provides information about the N/A N/A
budget expected growth in business in the mid-term, based
on the overall business strategy and services plan.
5.1.1.2.3. Analyze logistics Logistics performance data provide insight into the N/A N/A
performance performance of fleet, particularly equipment
utilization, and help identify opportunities for
optimization of fleet use.
5.1.1.2.4. Calculate target fleet Demand for containers is calculated based on the N/A N/A
size analysis of existing commercial capacity,
commercial budget estimates, and logistics
performance indicators.
5.1.1.2.5. Determine fleet strategy Determination of fleet strategy entails not only the N/A N/A
volumes per size-type, but also financing of the
equipment.
8.2.4.1 Analyze Commercial Capacity
Commercial capacity refers to total available TEUs across all services and lines operated by CMA CGM, as well as capacity
allocation available on partner vessels as per VSA agreements. It is typically smaller than the theoretical capacity available.
Note
Commercial capacity data shall be available from Network and Operations. Additional details described in
[BBP_NWK_CAPA_ALLO].
Capacity data shall be available at different levels of aggregation, for example:

Global capacity is managed independently by each carrier (CMA CGM, McAndrews, ANL, and CNC).
Capacity per service as well as a group of services within a trade is maintained with the option to display certain lines within a
trade (capacity per line is available). Vessel fleet size (nominal capacity of smallest vessel nominal capacity of biggest vessel
that operates on that service) is also maintained per service.
Volumes are 'proforma' for the year, but data are updated quarterly.

Business Blueprint
8.2.4.2 Analyze Commercial Budget
Commercial budget provides information about the expected growth in business in the mid-term, based on the overall business
strategy and services plan. This information is available in terms of TEUs.
Annual budget from all commercial lines shall be available from Finance & Controlling department (either directly, or from the
system).
Example
Following is an example of the Commercial Budget Report.
Figure 999 : (Sample) Commercial Budget Report
Formatted: Font: BentonSans Bold

8.2.4.3 Analyze Logistics Performance
Logistics performance data provide insight into the performance of fleet, particularly equipment utilization, and help identify
opportunities for optimization of fleet use. The performance data shall be available across a range of logistics reports and
performance dashboards.
Indicators used may include:

Business Blueprint
Number of bookings per year

Equipment utilization ratio (per size-type)
TEU to vessel slot ratio (utilization target)
Container turn time
Container cycle time
Requirements
EQP- Container It shall be possible to provide - BI report on dwell time for Implementation 564, 1650
FS- Utilization visibility on dwell time, cycle containers per point (under BI
002 Management time (including for Gensets) (region/country/city).The scope)
and import export cycle data dwell time is the average
so as to enable analysis of number of days of stock on
fleet utilization. ground per location relative
(this requirement is under BI to the commercial activity.
scope) Dwell time calculation:
(average daily stock in TEU
* number of days on the
period) / max flow in TEU
- BI report on cycle time

(maritime, terrestre,
commercial): A cycle is a
group of legs for equipment.
Terrestre cycle is the cycle
on road/ground. A
commercial cycle is Export -
Transit (Maritime part of
journey) - Import, and
maritime cycle is the cycle at
sea.
- BI report for import/export

moves: Import moves
(empty returns) per week,
month with details per
point, size, type and
grouped type.
EQP- Container Fleet It shall be possible to provide - Report providing: Implementation 572 (under
FS- Activity overview of container fleet Graphical overview and BI scope)
004 status and activity. details of fleet activity ratio
(this requirement is under BI (fleet/activity) and turnover
scope) (loadings per year) by size-
type/period and by
TEUs/period, and fleet
history by size-type or
container status (full import)

Business Blueprint

or lease type.
8.2.4.4 Calculate Target Fleet Size
Demand for containers is calculated based on the analysis of existing commercial capacity, commercial budget estimates, and
logistics performance indicators.
To calculate the target fleet size, total demand is adjusted for the planned decrease in fleet size due to the containers that are to
be removed from the fleet during the planning horizon (based on age, equipment sales, off-hire performance, and so on). Once
the target fleet size is known in TEU terms, further analysis is carried out to determine a split between different size-types. Reefer
demand is calculated independently by a dedicated business unit and is provided as input during this process of demand
classification.
Example
Following is an example of the fleet size calculation sheet.

Business Blueprint
Figure 101010 : (Sample) Target Fleet Size Calculation
Requirements
EQP- Fleet Age Pyramid It shall be possible to have visibility on - Report providing Implementation 612
FS- the age and evolution of container visibility on age pyramid (under
001 fleet. for containers in fleet BI
(this requirement is under BI scope) with details on volumes scope)
per size-type, relevant
purchasing contract,
supplier, and so on, per
time period
EQP- Container Fleet It shall be possible to provide visibility - Report providing view Implementation 601
FS- Overview & Evolution on the container fleet (including of container fleet and its (under
003 Gensets and reefers) and its evolution evolution (including BI
with various details like size-type, Gensets and reefers) scope)
contract / lease type, region, amount with details on size-
of idles, full versus empty, and so on. type, status, lease type,
(this requirement is under BI scope) region, view on idles,
full and empty, and so
on in the form of a
graphical dashboard

Business Blueprint
8.2.4.5 Determine Fleet Strategy
Determination of fleet strategy entails not only the volumes per size-type, but also financing of the equipment. This process
covers the management of fleet financing decision, preparation of a fleet strategy proposal and seeking management approval.
8.3 Process Owned Equipment Management (5.1.1.3.)
The process concerns the end- to-end procurement and disposal (sale) of owned equipment. Owned equipment refers to 100
percent self-financed containers, containers purchased with a bank loan or those purchased under a financial lease.
Procurement of owned equipment describes details about negotiations with supplier, contract creation and execution, equipment
delivery and finally, invoicing and payment. Disposal refers to the sale of containers.

Business Blueprint
Figure 111111 : Owned Equipment Management

Business Blueprint
EQP- Procurement of New End-to-end procurement process related - Managing purchase SAP Standard
PUR- Equipment to acquisition of new equipment shall be contracts in system
001 managed and controlled in the system. - Managing creation
and issuance of
purchase orders
- Managing financial /
logistical goods
receipt
- Managing invoice
verification and
payment against
purchase orders

Component Object
5.1.1.3.1. Prepare owned The process covers negotiation and contract SAP MM Contract
equipment purchase preparation for purchase of owned equipment.
contracts
5.1.1.3.2. Manage owned Execution of owned equipment contracts refers to SAP MM Purchase
equipment contract the process of issuing call-offs against existing Order,
execution contracts. The process also captures details of Goods
parallel activities that are to be managed during Receipt,
the process. Master Data
5.1.1.3.3. Manage owned This process covers the details of managing SAP MM, Goods
equipment pickup / equipment delivery by/ pickup from the supplier. SAP TM - Order Receipt,
delivery Management , Freight
Order,
SAP FI AA,
Forwarding
SAP EM - Event
Order
Handler
Asset ,
Event,
Master Data
5.1.1.3.4. Manage owned This process deals with the handling of invoicing SAP FI-AP Invoice
equipment invoicing & and subsequent payment for the procurement of
payment owned containers, as well as any associated
payments to suppliers for provision of quality
control or certification services.
5.1.1.3.5. Manage owned This process deals with the sale of owned SAP TM Order Forwarding

Business Blueprint

Component Object
equipment sales equipment, including identification of equipment Management, Quotation,
to be sold, managing the actual sales process SAP FI-CA, SAP Forwarding
followed by billing and collection of payment, and FI-AA Order,
finally the release of the sold equipment to the Forwarding
buyer. Settlement
Document,
Invoice,
Asset,
Master Data
Formatted: Space Before: 3 pt, After: 3 pt, Line spacing:
Exactly 13 pt

Business Blueprint
8.3.4.1 Prepare Owned Equipment Purchase Contracts
The process covers negotiation and contract preparation for purchase of owned equipment.
Figure 121212 : Prepare Owned Equipment Purchase Contracts
The fleet strategy process provides input regarding the expected volumes of containers that are to be purchased as owned
equipment. Based on this information, the negotiations with the suppliers shall be initiated.
Several suppliers are relevant for this process. These include suppliers:
Manufacturing the containers,
Manufacturing the Reefer machines,
Providing quality control services,, and
Providing certification services.
Negotiations result in a general agreement on volumes and prices. This forms the basis for creating procurement contracts for
each of the above mentioned materials and services.
All equipment to be purchased shall be recorded as a material master in the system.
A dedicated contract type shall be created to manage the owned equipment purchasing process. The contract will be managed by
target quantity. When the total agreed quantity in the contract has been reached on the basis of individual call-offs issued against

Business Blueprint
this contract, the system shall block issuance of additional call-offs (against this contract). Customizing shall allow, depending on
the contract type, to block creation of purchase orders against the contract once the target quantity is reached.
Contracts shall also be defined for:

Purchase of Reefer machines
Purchase of equipment certification services, and
Purchase of equipment quality control services.
The standard field in the contract item acceptance of origin shall be activated to allow the invoice recording and payment after the
Financial Goods Receipt (before the Logistical Good Receipt). This field shall be copied from the contract to all purchase orders
created against the contract.
Note
Acceptance of origin is a standard field in the contract that needs to be set to allow the two-step goods receipt to be
executed.
The "Bamboo Floor" information shall be managed at contract header item level as a specific flag and shall be relevant for price
calculation (GAP 20561495). Each item of the owned equipment contract shall also be linked to equipment Size-Type master data
(maintained in SAP TM) in order to handle all technical specifications (GAP 1485).
If the contract is bank loan or financial lease relevant, a flag shall be maintained at the header level of the contract. (GAP 2056). It
shall not be possible to define a dedicated contract type to handle this information as the decision for bank loan can be made after
contract creation in which case it may not be possible to switch to another contract. It shall also be possible to record the reference
number for the financial lease in a custom field if relevant (GAP 2056).
Maintenance of the information about bank loan or financial lease shall automatically trigger updates to resource master data in
SAP TM to update the contract reference and ownership fields (GAP 3003). Formatted: SAP_ScreenElement
Formatted: SAP_ScreenElement
Maintenance of this flag in the contract shall indicate that the containers under this contract shall not be sold.
Finally, the Finance department shall be informed whenever a contract for purchase of owned equipment is created.
This process covers solution for management of contracts for purchase of owned equipment which are part of integration points
1350 and 1485 as listed in section 7.5 of this document. Further details related to procurement processes can be found in
[BBP_PRM].
Requirements

Business Blueprint
EQP- Purchase Contract A contract (for procurement of - Manage SAP Standard

PUR- Data Authorization owned/ leased containers) includes authorizations for rights
003 confidential information. It shall be to display financial
possible to authorize or restrict information maintained
access to certain information in purchase contracts.
maintained in the contract based on
user role and organization.
EQP- Commitment for It shall be possible to generate a -Create a commitment SAP Standard
PUR- Purchase of commitment at the time of creating in controlling at the
004 Equipment a contract / purchase order for time of purchase
equipment for controlling purpose. contract / purchase
order creation
-Generate a report of
commitments against
purchase contract /
purchase order
aggregated per time
period.
PRM- Inform financial Finance has to be informed when SAP Standard

CTR- department of new contract is created.
044 contracts
PRM- Create contract for A dedicated contract is created by SAP Standard

CTR- container certification Head Office Logistic for container
047 services certification services. This one will
include the service to be provided
and the price condition.
PRM- Create contract for A dedicated contract is created by SAP Standard

CTR- container quality Head Office Logistic for container
048 control quality control services. This one will
include the service to be provided
and the price condition.
PRM- Search Contract by [Equipment] The possibility to search Implementation 2594

CTR- technical specification contract by technical specification
080 (color, CMA CGM logo) will be
provided.
PRM- Maintain owned [Equipment] For owned containers, a Implementation 329

PO- containers number range of serial number is keyed in
117 range in call-off the call-off and provided to
manufacturer.
The container number will be known
only during the On Hire Process. No
automatic generation of container
number is required.
PRM- Prevent contract [Equipment] Owned contracts shall Implementation 2056

Business Blueprint

CTR- extension for owned not be extended.
043 equipment Either another contract or a new
version of the same contract shall be
created (for instance, all information
is the same, only the amortization
per diem is different).
PRM- Manage material [Equipment] It shall be possible to SAP Standard

MD- master data for manage material master (size-type)
015 owned equipment for owned equipment purchasing
purchasing process process
PRM- SAP Standard

Manage suppliers for [Equipment] It shall be possible to
MD-
owned equipment manage suppliers for owned
014
purchasing process equipment purchasing process
EQP- Equipment Contracts It shall be possible to maintain a per One field for 'leasing Implementation 419, Formatted Table
PUR- Per Diem Calculation diem value for (all) equipment per diem' charges (paid 2056
006 related contracts. to the lessor)
- One field for 'financial
per diem' charges (for
financial lease and bank
loans)
- One field for
'amortization per diem'
(based on asset
accounting rules)
- One field for 'total per
diem' charges
- The fields shall be
filled manually by
Logistics department
except 'total per diem'
charges which shall be
automatically
calculated
- For each contract,
only the relevant fields
shall be filled
depending on the
contract type (For
example: for Owned
equipment, only
Amortization field
shall be used while for
Operational Lease, only
Leasing field shall be
used)

Business Blueprint
PRM- Keep traceability of The system shall keep traceability of SAP Standard
CTR- contract versions contract versions
035
EQP- Equipment Contract It shall be possible to maintain the - Ability to maintain and Implementation 42,
MD- Reference Fields relevant contract reference(s) update primary 2655,
050 (purchasing / leasing contract) on the contract reference for 3003
container passport (master data) the container in a
custom field in the
container master data
(Primary Contract
Reference)
- Ability to maintain and
update secondary
contract reference for
the container in a
container master data
(Secondary Contract
Reference). e.g. the
reference of financial
lease contract for
owned equipment, the
reference for sub-lease-
to contract for a leased
container.
- Ability to retain
the fields
- Ability to mass update
the fields by a filter (e.g.
contract reference,
number range, etc.)
PRM- Maintain asset [Equipment] Rules linked to the Implementation 2056

CTR- depreciation rule and asset depreciation are managed in
049 contract sub-types for the owned contract.
owned equipment Contract sub-types for owned
equipment need to reflect if the
contract is an owned contract, an
owned contract with bank loan, or an
owned contract with financial lease.
For the last two sub-types, the
system shall provide fields to record
the type, as well as the related
contracts and business partners.

Business Blueprint
8.3.4.2 Manage Owned Equipment Contract Execution
Execution of owned equipment contracts refers to the process of issuing call-offs against existing contracts, based on business
need and equipment demand in different locations. The process also captures details of parallel activities that are to be managed
during the procurement of owned equipment - for instance, issuance of purchase orders to suppliers providing quality control
services, generation of a container numbers, creation of fixed assets, and so on.
Figure 131313 : Manage Owned Equipment Contract Execution
Owned Equipment contract execution begins with the determination of an equipment phase-in plan. Business seasonality shall be
analyzed to determine peak periods of equipment demand. Supplier production capacities shall also be considered. The phase-in
plan indicates how the total equipment quantity to be purchased during the next year is to be phased-in (how many containers at
which time).
Once equipment phase-in has been planned, the purchasing process begins. Purchasing supports all the operational steps to
request goods or services from the external parties / suppliers.
For purchase of owned equipment, four types of call-offs shall be created:

For the purchase of owned equipment,

Business Blueprint
For the purchase of Reefer machines (if any)

For the purchase of certification services, and
For the purchase of quality control services.
The call off for owned equipment shall be represented in the system by a purchase order which includes details of the agreed price
and volumes, pre-determined specifications, and a meaningful series / number range for each equipment size-type.
Series refers to a group of containers belonging to a certain number range and having some common characteristics. Series /
number range for a group of containers shall be generated by the M&R department. At this time, master data at the series level
shall also be created in the system (GAP 2571).
For purchase of owned equipment, a dedicated purchase order type shall be used, allowing the recording of invoice and payment
at the time of receipt of equipment (batch) certificate. Dedicated fields shall also to be created in the purchase order item to allow
incorporation of equipment series, and to be able to add location / point (in five digits) on the purchase order item to capture the
manufacturing or delivery location (GAP 2056).
The "Bamboo Floor" information shall be managed in the purchase order at the item level as a specific flag. (GAP 1495).
In case of Financial Lease, the call-off shall be free of charge. Since the financial lease may be initiated at any time during or after
the owned equipment purchase process, in the case that the decision for a financial lease agreement is made after the creation of
a purchase order of owned equipment, the purchase order shall be updated to be free of charge and shall not be relevant for
invoice recording.
The purchase order for owned equipment purchase shall be subject to approval via Workflow (GAP 1931). An approved purchase
order shall be sent to the supplier. Purchase order output shall be customized to allow printing or emailing to suppliers.
For each purchase order / call off of owned equipment, purchase orders for equipment certification and for quality control shall be Formatted: Font: BentonSans Book
created against the respective supplier contracts. In case of Reefer purchase, purchase order for the purchase of machinery is also
created.
Note
For reefer purchase orders, the delivery address shall be the container manufacturer's premises as the assembly of the
machines into the boxes is performed by the container manufacturer.
After production for the first batch begins, the quality control supplier shall send daily production acceptance reports to for the Formatted: Font: BentonSans Book
quantities produced. This report shall be received at both the head office and agency level.

Business Blueprint
Figure 141414 : Receive Daily Production Acceptance Report
Example
Following is a sample Production Progress report received from the Quality Control service provider.

Business Blueprint
Figure 151515 : (Sample) Daily Production Acceptance Report
Certification and quality control takes places parallel to production at the manufacturer's premises. Upon completion of each
production batch, proof of production completion shall be received in the form of a Certificate (per batch) from the certification
supplier. This document shall be scanned and stored on a document management system.
The Certificate shall provide details of all containers (including numbers) that have been certified, and is a confirmation that
production confirms to technical specifications and quality requested in the purchase orders.
If additional information for a series /batch of equipment is available in these documents, the already existing series master data
shall be updated accordingly. The link of the storage location for the (batch) container certificate shall also be maintained in the
series master data object.
Note
The certificate is the same for an entire batch of containers.
Receipt of the Certificate for a batch of equipment is a confirmation that the requested materials / services have been produced /
executed. This shall be recorded against the respective purchase order as a financial goods receipt (for owned equipment
purchase, goods receipt will be done in two steps, financial goods receipts and logistics goods receipt).

Business Blueprint
Financial Goods Receipt serves as the basis for payment to the respective suppliers. It shall post an accounting document with the
amount of the purchase order and allow the invoice recording and payment according to the payment terms and methods
maintained in the purchasing contracts. At financial goods receipt, the value of the asset shall also be posted to a general ledger
account (to be used later in the process for fixed asset creation).
The goods / service receipt against the purchase orders created for certification services and quality control shall be manual and
performed in a single step. The one-step goods receipts for certification services shall be performed per batch, at the time of
receipt of (batch) container certificate. For quality control services however, a monthly goods receipt shall be performed for all
containers inspected during the month (as known from daily Production Acceptance reports sent by the supplier).
Goods receipt for Reefer machines shall be manually performed in one-step. This goods receipt shall not trigger any inventory
management goods movements, but shall only be statistical in nature since this allows invoice verification with reference to the
purchase order.
In the case of a financial lease, if the decision for a financial lease agreement is made after financial goods receipt, the goods
receipt shall to be reversed (to clear the account posting document) and the call off shall be updated to be free of charge and thus,
not relevant for invoice recording. The goods receipt shall then be processed in one step.
Example
Following is a sample of the Container Batch Certificate.

Business Blueprint
Figure 161616 : (Sample) Certificate of Inspection Received from Certification Supplier
This process covers solution for management of purchase orders, and creation of fixed assets for owned equipment which are part
of integration points 1350 and 1485 as listed in section 7.5 of this document. Further details related to procurement and asset
accounting processes can be found in BPM_PRM and BPM_FIN (Asset Accounting) respectively.

Business Blueprint
Requirements
EQP- Expected Delivery It shall be possible to use '- Extract purchased Roll-in for FBS
TINV- Schedule for New information regarding container quantity for new
013 Owned Containers delivery schedule, as reflected in containers from
and Provisional the purchase orders of new owned purchase orders
Stock ToolExpected equipment as an input for the new - Transfer quantity as
Delivery Schedule provisional stock tool.It shall be potentially available to
for New Containers possible to use information provisional stock tool
and Provisional regarding container delivery to enhance forecast
Stock Tool schedule, as reflected in the per location- Extract
purchase orders of new equipment purchased quantity for
as an input for the new provisional owned containers
stock tool. from purchase orders
- Transfer quantity as
potentially available to
provisional stock tool
to enhance forecast
per location
EQP- Commitment for It shall be possible to generate a -Create a commitment SAP Standard
PUR- Purchase of commitment at the time of in controlling at the
004 Equipment creating a contract / purchase time of purchase
order for equipment for contract / purchase
controlling purpose. order creation
-Generate a report of
commitments against
purchase contract /
purchase order
aggregated per time
period.
PRM- Scan equipment [Equipment] The certificate issued SAP Standard

GSR- certificates to enable by certification supplier will be
017 invoice verification used as a proof of service delivery
in order to run the invoice
verification. The equipment
certificates will be scanned and
attached to the reception.
PRM- Define equipment [Equipment] The equipment Implementation 326

PO- delivery location destination recorded in the call-off
048 can be the production location or
delivery location (city) according
to Incoterm in order to organize
the pick-up.
PRM- Link equipment [Equipment] Equipment technical Implementation 1873

PO- technical specifications are attached to
041 specification to call- owned equipment purchase order

Business Blueprint

off (call-off) item (i.e. at series level).
PRM- Record Manual [Equipment] The financial receipt SAP Standard

GSR- Financial receipt for allows the invoice payment. This
019 owned container will be done when certificates are
received. Because the container
may be picked up later,
PRM- Update equipment [Equipment] The additional details Implementation 2571

GSR- technical of the equipment technical
015 specification during specification will be updated
goods receipt during the goods receipt of the
equipment.
PRM- Trigger invoice [Equipment] For certification, SAP Standard

LIV- verification for invoices verification is done
020 certification at against the certificate delivery and
certificate delivery the certificate purchase order.
PRM- Trigger invoice [Equipment] For container quality SAP Standard

LIV- verification for control, invoices are received
021 container quality monthly and will be matched to
control the quality control purchase order.
PRM- Enable invoice [Equipment] For owned SAP Standard

LIV- payment prior to equipment, a first step of goods
022 physical receipt receipt will allow the invoice
payment.
PRM- Approve owned [Equipment] The owned Implementation 1931

PO- equipment call-off equipment call-off shall be
044 approved by the Head Office.
8.3.4.3 Manage Owned Equipment Pickup/Delivery
This process covers the details of managing the pick-up or delivery of purchased owned equipment. In this case, equipment may
be:
Delivered by the supplier to an agreed location at an agreed time, or
Picked-up from supplier at an agreed location at an agreed time.

Business Blueprint
Figure 171717 : Manage Owned Equipment Pickup/Delivery

Business Blueprint
As the proof of (batch) production completion is received, the containers are available for pick-up / delivery. The responsible party
is agreed in the relevant purchase order.
If CMA CGM is responsible to pick-up equipment from supplier's premises, the transfer of empty containers shall be organized.
Details of this process are described under 5.1.3.3.2. Manage Inland Empty Repositioning in [BBP_EQP_LM].
If the supplier is responsible for delivery of equipment, a forwarding order shall be created for the transport with restricted
processing meaning it shall not be planning-relevant. This forwarding order shall maintain a reference to the respective purchase
order. All subsequent documents such as a (depot acceptance) service freight order shall maintain a reference to this forwarding
order via the transportation unit, TU.
In addition, a delivery depot shall be determined, and a (depot acceptance) service freight order shall be issued to the depot to
inform about the expected container delivery from manufacturer. Details of these processes have been described in 5.1.3.2.
Returns Management, in [BBP_EQP_LM].
The manufacturer shall be informed about the details of the delivery location (depot) by issuing a delivery confirmation. This
information shall essentially be the same as that contained in the (depot acceptance) service freight order issued to the depot in
reference to the forwarding order mentioned above.
The data from the (depot acceptance) service freight order shall be copied into a new output template and sent to the
manufacturer using output management functions (GAP 2810).
Upon arrival of shipment at CMA CGM depot, the containers shall be gated-in. When the containers gate in with the reference of a
(depot acceptance) service freight order linked to the a forwarding order mentioned above (via the transportation unit, TU),
resource master data shall be created for each TU by copying the series master data (referred to in the purchase order) and adding
the container number received during gate-in (GAP 2811). In case the forwarding order number shall not be available at the time of
gate-in, the process shall be managed manually.
At the same time, a logistics goods receipt against the purchase order shall be triggered (GAP 1870).
This process of creation of resource master data for owned equipment is referred to as on-hiring, after which the equipment is
considered as added to the CMA CGM fleet.
Logistics goods receipt / creation of resource master data shall trigger creation of fixed assets (called as external asset acquisition,
i.e. asset acquisition from an external partner). Activation of the asset shall take place by posting the acquisition value (from the
general ledger account used at the time of financial goods receipt) to the asset. This automatic clearing of the general ledger
account is managed with an enhancement in FI-AA.
If a financial lease agreement exists, the fixed assets shall be created under asset class 'Financial Lease'.
Further details about fixed asset creation have been described in [BBP_FIN_Asset].

Business Blueprint
Figure 181818: On-Hire Owned Equipment

Business Blueprint
This process includes a high level description of asset acquisition with and without financial lease for owned equipment which is
part of integration points 1350 and 1485 as listed in section 7.5 of this document. Further details related to asset accounting
processes can be found in [BBP_FIN_Asset].
Requirements
PRM- Record Logistical [Equipment] The gate-in tracking Implementation 1870

GSR- receipt for owned move will trigger the logistical
020 container equipment receipt in the equipment
fleet.
EQP- Delivery Confirmation It shall be possible to send a delivery - Delivery confirmation Implementation 2810
PUR- to Supplier confirmation to the supplier, with (Form) with reference
005 required depot details and reference to the respective
number needed for the delivery of purchase order, depot
containers to CMA CGM depot details and depot
(Scenario: delivery of newly purchased delivery reference
owned containers by supplier) number.
EQP- Activation and It shall be possible to add or remove - Create master data for Implementation 2811
MD- Deactivation of owned container (master data) from owned container when
052 Owned Container fleet at the time of container 'on-hire' it is added to the fleet
Master Data and 'off-hire' respectively. (on-hired)
- Deactivate master
data for owned
removed from the fleet
(off-hired)
8.3.4.4 Manage Owned Equipment Invoicing & Payment
This process deals with the handling of invoicing and subsequent payment for the procurement of owned containers, as well as
any associated payments to suppliers for reefer machines, and quality control or certification services.

Business Blueprint
Figure 191919 : Manage Owned Equipment Invoicing & Payment
Invoice from the supplier of equipment and supplier of certification services accompanies the Certificate and Acceptance Report,
which serve as proof of (batch) production completion. Invoice from quality control supplier is received monthly.

Business Blueprint
Upon receipt, the paper invoice shall be scanned and electronically stored in the system.
In case of invoice with purchase order reference, all the items in a purchase order can be settled together, regardless of whether an
item has been received in several partial deliveries.
The invoice shall then be recorded in the system with reference to the purchase orders created.
When the purchase order number is keyed in for an invoice, relevant data shall automatically be retrieved from the purchase order,
automatically populating the following information: invoicing party (vendor), payment terms, item data (amount, quantity, service
code, tax code, account assignment, G/L account, etc.) coming from each purchase order line item.
The system shall propose value and quantity coming from purchase order items as a default value into invoice items. This can be
however, overwritten with inputs coming from the vendor invoice. A comparison is then made between total invoice line items
and header amounts of the invoice. Based on this comparison the invoice balance shall be calculated. The quantities and values
that are entered in SAP invoice line items are also compared against the purchase order line items sent to the vendor.
An invoice can be booked in reference to multiple purchase orders. In such case, all relevant purchase order numbers shall be
entered in the invoice screen. All item data coming from purchase orders shall automatically be proposed by the system and be
treated in a similar way as described above.
Invoices may be recorded for a supplier or for another third-party who is able to collect payments for the supplier.
Invoice verification process checks the accuracy of invoices received from vendors with respect to contents, prices, and arithmetic,
matching invoices with purchase orders goods receipts. It uses the data scanned and or entered previously in the Purchasing and
Goods Receipt application areas and passes on documents created when an invoice is posted to Financial Accounting, Asset
Accounting and Cost Accounting.
Invoice verification for invoice against purchase orders are subject to the following workflow approvals:
- Approval to remove the blocking code from the Accounts Payable invoice and release it for payment.
- Approval for "OK to pay" based on the invoice amount (subject to the authority matrix)
In summary, invoice entry, verification and payment process shall include some or all of the following steps:
1. Entry of an electronic document to a repository (scanning & archiving using OpenText)
2. Parking the system document
3. Connecting the system document with an electronic copy from a repository (viewing document)
4. Completing the document (manually or with Kofax Capture OCR Optical Character Recognition)
5. Releasing the document that meets the required criteria, e.g. amount limits
6. Posting the document in SAP Financial Accounting Accounts Payable (FI-AP)
7. Blocking the document for payment if there are differences in quantities and/or value
8. Processing the differences in quantity and/or value, if applicable
9. Releasing the document for payment, if it was blocked due to differences
In the case of a financial lease, if the financial lease decision is made after invoice recording, the invoice shall be cancelled (and Formatted: Font: BentonSans Book
goods receipt shall be reversed as described above). If the financial lease decision is made after the payment to supplier

Business Blueprint
(manufacturer) however, the process shall be to be managed as a sale and lease back of owned equipment. Details of this process
have been documented in [BBP_FIN_Asset].
This process covers solution for recording and payment of invoices for purchase of owned equipment which are part of integration
points 1350 and 1485 as listed in section 7.5 of this document. Further details related to these processes can be found in
[BBP_FIN_AR_AP_BA]. It also highlights high level details about the payment process in the case of a financial lease, listed under
integration points 1350 and 1485, additional details of which can be found in [BBP_FIN_Asset].
Requirements
EQP- Invoicing and Payment It shall be possible to link the creation of - Invoice verification and SAP
PUR- for Purchase of Owned purchase orders for procurement of new payment against Standard
002 Equipment equipment (managed by Logistics purchase orders
department) to the associated invoice
verification and payment process.

Business Blueprint
8.3.4.5 Manage Owned Equipment Sales
Equipment may be sold if it has reached the end of its useful life or is damaged (wrecked), or if an opportunity for sale has been
identified. This process deals with the sale of equipment, including identification of equipment to be sold, managing the actual
sales process followed by invoicing and collection of payment, and finally the release of the sold equipment to the buyer.

Business Blueprint

Business Blueprint
Figure 202020 : Manage Owned Equipment Sales
The sale of owned equipment process covers three scenarios:

Sale to local agency (by head office)
Sale to third party (by head office or local agency)
Sale to third party (by local agency)
The same equipment may be sold by the head office to the agent, and further sold by the agent to a third party.

Business Blueprint
The process begins with the receipt of a request for equipment sale. The request is recorded with details of the equipment volume
demanded, location of potential sale and buyer details. Each request for sale has a validity date.
Depending on the scenario of sale, this request may either be recorded by the HO Equipment Sales Manager or the Local
Equipment Sales Manager, as shown in the graphic below.
Note
The executing role for each step of the container sales process may similarly change depending on the scenario. A
summary of these roles is provided at the end of this process in tabular format.
Figure 212121 : 5.1.1.3.5.1. Record Request for Container Sale
A list of equipment available for sale, compiled on the basis of the equipment status (eligible for sale or to be sold), shall be
available to check if a request for sale can be serviced. In the case of intercompany sale to agent, the agent shall be able to review
this list and record the details of equipment in the sales request.

Business Blueprint
After equipment for sale has been identified to service a certain request, it shall be ascertained that it is available in depot. In case
of availability, the equipment shall be blocked.
The sales price for the equipment shall be determined. This is estimated based on the residual value of the equipment. Margin
may be added in the sales price; however, this is based on individual judgment of the responsible equipment sales manager in the
head office or agency.
An equipment sales quotation is created. This shall allow updating the status of the equipment sales request to indicate that it is
in progress. The reference number of the sales request shall be copied to the equipment master data in a dedicated field to
indicate that a sales process for this equipment runs in parallel.
In the negotiation process that follows, the quotation with the equipment details and price shall either be accepted by the
potential buyer, or a counter offer shall be made. In the case of third party sale, the quotation shall be sent to the potential buyer
and a response shall be received based on which the sales request may be updated. In case of sale to a local agency, quotation
shall be sent to the agent and he can also provide a counter offer.
At the end of the negotiation process, the price for equipment sale shall be finalized between both parties. Based on that, the
sales document shall be created. The history of the originally quoted sales price shall also be retained.
Once the sales price is confirmed, the sales document shall be created from the information available and issued to the buyer.
The status of the equipment sales request shall be updated to indicate that it is now confirmed. This shall also triggers an
automatic update of the equipment status to sold.
The next step is to issue an invoice to the buyer for the sale of equipment. The invoice number shall be updated in the sales
document, and a payment status shall be maintained (paid or not paid). In case of sale to agency, invoice issuance triggers the
deactivation of fixed asset (but not the equipment master data). The sales request status shall be updated to reflect that it is now
complete. Intercompany equipment sale invoice shall be settled via netting. For more information, see [BBP_FIN_AR_AP_BA].
There is no process for release of equipment to the agent.
Equipment sales to third parties are subject to immediate payment. Upon receipt of payment, a notification shall be received
from the collections department with confirmation of payment against an invoice. In this scenario, the sales request status shall
be updated at this point to reflect completion. Instructions to release the equipment to the third-party buyer shall be issued (via
e-mail). Following release of sold equipment, the fixed asset and equipment master shall be deactivated.
The specifics of equipment sale may change or be canceled. This shall be handled by an amendment or cancelation of the
container sales document and issuance of credit notes. In case of cancelation, the status of the equipment sales request shall be
updated to canceled, and a reason for cancelation shall be recorded from a list of predetermined reasons, as explained below:
Container released erroneously by depot (and is not available for release to buyer)
Container used or to-be used for export
Cancelation requested by customer or buyer
Other

Formatted ...
Formatted ...
Business Blueprint Formatted ...
Formatted ...
Formatted ...
Formatted ...
Formatted ...
The following table provides details of the role that executes the process steps in case of the three scenarios:
Formatted ...
Formatted ...
Scenario Sale to Agency by Head Sale to Third-Party by Sale to Third-Party by Formatted ...
Office Head Office Agency
Formatted ...
5.1.1.3.5.1. Record request for HO / Local Equipment HO Equipment Sales Local Equipment Sales Formatted ...
container sale Sales Manager Manager Manager Formatted ...
5.1.1.3.5.2. Review list of containers HO / Local Equipment HO Equipment Sales Local Equipment Sales Formatted ...
available for sale Sales Manager Manager Manager Formatted ...
Formatted ...
5.1.1.3.5.3. Check container availability Local Equipment Sales Local Equipment Sales Local Equipment Sales
in depot Manager Manager Manager Formatted ...
Formatted ...
5.1.1.3.5.4. Block container in depot Local Equipment Sales Local Equipment Sales Local Equipment Sales
Formatted ...
Manager Manager Manager
Formatted ...
5.1.1.3.5.5. Determine sales price HO Equipment Sales HO Equipment Sales Local Equipment Sales Formatted ...
Formatted ...
5.1.1.3.5.6. Create container sales HO Equipment Sales HO Equipment Sales Local Equipment Sales Formatted ...
quotation Manager Manager Manager Formatted ...
5.1.1.3.5.7. Update status of container HO Equipment Sales HO Equipment Sales Local Equipment Sales Formatted ...
sale request to 'in progress' Manager Manager Manager Formatted ...
Formatted ...
5.1.1.3.5.8. Issue container sales Sales quotation is not HO Equipment Sales Local Equipment Sales
quotation issued but is accessible by Manager Manager Formatted ...
the agency in the system Formatted ...
Formatted ...
5.1.1.3.5.9. Confirm quoted price or Local Equipment Sales HO Equipment Sales Local Equipment Sales
provide counter offer Manager Manager Manager Formatted ...
Formatted ...
5.1.1.3.5.10. Receive counter offer / HO Equipment Sales HO Equipment Sales Local Equipment Sales
Formatted ...
confirmation of quoted price Manager Manager Manager
Formatted ...
5.1.1.3.5.11. Confirm final sales price HO Equipment Sales HO Equipment Sales Local Equipment Sales Formatted ...
Formatted ...
5.1.1.3.5.12. Issue container sales HO Equipment Sales HO Equipment Sales Local Equipment Sales Formatted ...
document Manager Manager Manager Formatted ...
5.1.1.3.5.13. Update container status to Automatic Automatic Automatic Formatted ...
sold / sales document issued (SAL) Formatted ...
sales request to confirmed Manager Manager Manager Formatted ...
Formatted ...
5.1.1.3.5.15. Issue container sales HO Equipment Sales HO Equipment Sales Local Equipment Sales
Formatted ...
amendment or cancellation Manager Manager Manager
Formatted ...
5.1.1.3.5.16. Update status of container HO Equipment Sales HO Equipment Sales Local Equipment Sales
Formatted ...
sale request to cancelled Manager Manager Manager
Formatted ...
sales request to 'complete' Manager Manager Manager
Formatted ...
Formatted ...
Business Blueprint
Scenario Sale to Agency by Head Sale to Third-Party by Sale to Third-Party by Formatted: Font: BentonSans Book, Font color: Auto
Office Head Office Agency Formatted: Font: BentonSans Book, Font color: Auto
5.1.1.3.5.18. Issue instructions for HO Equipment Sales HO Equipment Sales Local Equipment Sales Formatted: Font: Bold
release of container Manager Manager Manager Formatted: Font: BentonSans Book, Font color: Auto
Formatted: Font: BentonSans Book, Font color: Auto
Cross-Stream Shortcut: Issue invoice HO Equipment Sales HO Equipment Sales Local Equipment Sales
for container sale Manager Manager Manager Formatted: Font: BentonSans Book, Font color: Auto
Solution:
A forwarding agreement (FWA) dedicated to container sales process shall be maintained in SAP TM. This shall include relevant
data for the sales process such as sales organization, terms of payment, and so on.
The items screen area contains the details of the agreement items. At least one item for the agreement has to be defined (relevant
for charge calculation). Items in the container sales forwarding agreement shall be a container equipment type (represented by a
size-type).
A calculation sheet shall be assigned to each agreement item and shall contain a charge type representing the sales price.
The process begins with the receipt of a request for equipment sale.
The forwarding quotation (FWQ) shall be used to record container sales requests from a buyer (ordering party), and to respond to
these requests by sending an offer of sale. The forwarding quotation shall be created manually to record the sales request received
from the ordering party (via e-mail).
A template for a forwarding quotation document type specific to the container sales process shall be defined in the Customizing
settings. Using a document type allows to determine certain default settings for the forwarding quotation, for example, sales
organization may be predefined; it may be defined how many forwarding orders (to be used in this process as container sales
document) are allowed to be created based on a forwarding quotation of this type, and so on.
The forwarding quotation shall have a validity period determined by the start and end date. Details regarding partner (buying
party) details, location (of sale), and volume of containers demanded for sale, selling organization, and so on shall also be
maintained.
It shall be possible to define source and target locations, pick-up and delivery dates, as well as business partners in the forwarding
quotation. There shall also be a possibility to record one-time locations and one-time addresses that differ from those in the
header data in a forwarding quotation.
On the business partner tab, it shall be possible to maintain the ordering party (buyer) and any further business partner roles if
required (for example notify party).
The size-type shall be an equipment type in SAP TM.
In the items screen area of the forwarding quotation, equipment types (for example, freezer containers and 20-foot
containers) shall be added under item category Container to record the sales demand per size-type.

Business Blueprint
As the details of exact containers to be sold are available from the report for containers flagged for sale (GAP 1654), additional line
items shall be added (manually) to record one item per container available for sale. Eventually, if the full demand can be met, the
number of items shall be the same as the quantity of containers demanded for sale, and each item shall have a container number
assigned.
In the case of intercompany sale to agent, the respective agent shall be allowed (using authorization rules) to edit the forwarding
quotation (sales request) to add the individual containers from the report of containers available for sale.
Instructions for blocking containers in depot after they have been assigned to a potential sale offer (FWQ) shall be managed
manually (out of the system).
The quotation price can be determined for a sales request as a whole, or per container.
The forwarding quotation based on the forwarding agreement with its specific charge types shall allow calculating an individual
price. This manual charge type resulting from the calculation sheet linked to the forwarding agreement item shall allow
maintenance of an individual sales price for the container on forwarding quotation item level (one item per container).
The standard life cycle status functionality of the forwarding quotation shall be used to manage the status of the sales request. Formatted: Font: BentonSans Book
The following standard statuses are available:
Status Description
New The forwarding quotation is newly created and not yet sent.
Transferred The forwarding quotation is sent to the ordering party.
Not Transferred The forwarding quotation that was already sent to the ordering party is now
changed and the changes are not yet sent.
Canceled The forwarding quotation is canceled.
Formatted: Font: BentonSans Regular

Caution
The maintenance of the end to end life cycle status of a sales request (forwarding quotation) shall not be possible. After
the generation of a subsequent document (forwarding order), the status of the previous document shall not be changed.
Only the status of the new document shall be managed.
It shall be possible to simply record the sales request in the form of a quotation and save it (without sending it to the buyer as an
offer of sale).
When the forwarding quotation (sales request) is saved, the system shall assign an ID to the document from the number range
defined for this document type. In addition, the system shall check the data for completeness and consistency. The results of these
checks shall be displayed in the form of error messages and as a completeness status. The initial document status shall be New.

Business Blueprint
The forwarding quotation may be sent to the ordering party as an offer using standard output capabilities. and a specifically
implemented form in case of sale to a third party (GAP 1777). The history of sending and printing documents is displayed on the
Output Management tab.
Standard output management features include the following:

Choose the output method such as print, fax, and e-mail
Preview a document
Enter an attachment
Enter a note
Enter a recipient
Execute the action, such as printing and faxing a forwarding quotation
It shall also be possible to regenerate and execute an action that has already been executed, for example, reprint a business
document. When an action is regenerated, the attributes can be changed, for example, entering a new recipient. The system shall
also display the status of an action after execution. If a particular action is not processed successfully, the system shall display the
cause of the error.
Sending the sales request (FWQ status is set to Transferred) shall trigger the update of the SAP TM resource master (container
master data) to fill the (enhanced) field, Sales Reference with the forwarding quotation (sales request) number. Both the field
(GAP 42) and its population based on the status of the forwarding quotation shall be managed via enhancement (GAP 2654).
Depending on whether the ordering party (buyer) agrees with the quotation or not, it can be accepted or rejected.
Recommendation
In order to keep the process simple and meet requirements for retention of initially quoted and final sales price (using
standard objects available), it is proposed to accept a forwarding quotation and to retain the initial quoted price in this
document in case the sale is proceeded with. If however, the sale is canceled at this stage and shall not result in the
generation of a subsequent sales document, the quotation may be rejected or canceled.
When a forwarding quotation is accepted, a sales document may be created directly from the quotation.
This sales document shall be modeled in SAP TM solution as a forwarding order.
The forwarding order shall be created with reference to an existing forwarding quotation, based on the data in the quotation
(hence the original sales request link shall be maintained). The system shall check whether the quotation is still valid before the
creation of the forwarding order. Outside of its validity period, the quotation (sales request) shall not valid anymore and it shall not
be possible to create a sales document (forwarding order) based on this.
If a forwarding order is created based on the forwarding quotation, the item types (containers being sold) that have been defined
shall be copied to the forwarding order. The charges (selling price) of the items entered in the forwarding quotation shall also be
copied automatically to the forwarding order.

Business Blueprint
The forwarding order type for a container sale shall be configured as restricted processing. A transportation unit shall be created
which represents the actual container documents for the containers to be sold. The (depot release) service freight order shall be
linked to these container documents later in the process.
In the scenario where the final selling price agreed between the two parties is different than the initially quoted price, this shall be
maintained in the forwarding order (and does not propagate backwards to change the forwarding quotation).
Saving the forwarding order shall generate an ID from the range of numbers defined in the Customizing settings for this document
type. However, it shall continue to appear in the document flow as a subsequent document of the original forwarding quotation
(sales request).
After the forwarding order has been created, the data shall be confirmed to the ordering party. It shall be possible to define a
default confirmation type in Customizing for the document type, for example the definition of data the confirmation to the
customer is to be based upon. It shall also be possible to define that the confirmation occurs automatically upon saving. If this
option is not used, the order shall be confirmed manually by the user.
Standard output management shall be used to send the confirmation to the ordering party. The sending type (for example fax and
e-mail) shall be customized. It shall also be possible to print the forwarding order confirmation as a document. In the output
history, it shall be possible to display which confirmation documents were already printed or sent.
A form shall be used as a forwarding order confirmation (sales document) that is sent to the intercompany or external buyer (GAP
1779).
The status of the forwarding order shall be set to confirmed once the confirmation has been created.
An enhancement shall be used to automatically update the resource status to sold at the time of issuance of the forwarding order
(status confirmed) and block the resource with a reason code Sold (This enhancement shall also remove the Eligible for sale/to be
sold flag on the container with the setting of the sold status (GAP 2574).
At the end of the selling process, an invoice shall be issued to the buyer. A forwarding order needs to be settled to be able to
create an invoice. A forwarding settlement shall therefore be performed to trigger the invoice creation process.
Forwarding settlement creates a document (FWSD) that shall be sent to SAP FI-CA to request the creation of an accounting-
relevant invoice which can be sent to a customer. A forwarding settlement document has its own ID and is linked to the forwarding
order in the document flow as a subsequent document. The system shall allow the possibility to track the invoicing status on a
forwarding settlement document (invoiced or not invoiced).
A form shall be used to send the invoice to intercompany or third party buyers (GAP 507).
Following successful invoicing, the status of the forwarding order shall be set as complete.

Business Blueprint
Note
Details of the integration between SAP TM and FI-CA to create invoices from settlement documents are covered in
[BBP_FIN_AR_AP_BA] and [BBP_FIN_INV].
Details of the initial and final sales price (GAP under BI scope) shall be read from the following business objects:
Initial sales price forwarding quotation (assuming all subsequent changes in prices are maintained on the forwarding order)
Final sales price forwarding settlement document or invoice
The (standard) lifecycle status of a forwarding order shall be set to complete once invoicing (in FI-CA) has taken place. It shall be
possible to track the invoice number in relation to the number of the forwarding settlement document in SAP TM.
In case of an intercompany sale (HO to agency), the issuance of the invoice against a forwarding settlement document for
container sale shall trigger the deactivation of the fixed asset in FI-AA. This is to be managed with an enhancement (GAP 2654).
Resource master data shall remain active (as the container is blocked in the depot under reason code sold). There shall be no
container release process for intercompany sale.
In case of HO sale to third party, a workflow notification shall be received by the HO Equipment Sales Manager (GAP 1978) as
confirmation of collection of payment from the third party. At this time, the block on the resource shall be removed (but the sold
status shall remain) and a (depot release) service freight order shall be (manually) created in relation to the container documents
(TUs) linked to the forwarding order and issued (via e-mail) to manage the release of the sold container to the third party.
Note
Details of (depot release) service freight orders have been described in [BBP_EQP_LM].
When a resource (status sold) gates out of the depot with reference to a (depot release) freight order number that is linked to a
(container sales) forwarding order, the resource shall be deactivated by changing its validity date to the date of gate out. It shall
also be checked that the asset is deactivated (if it still exists, as in the case of HO to third party sale). This shall be an enhancement
(GAP 2654).
If however, a container with status sold is released by the depot erroneously (without a release reference linked to the container
sales document), an alert shall be generated and the relevant local and HO Equipment Sales Managers shall be notified (GAP
2654).
The specifics of equipment sale may change. This shall be handled by an amendment or cancelation of the forwarding order
(container sales document).
A forwarding order allows the possibility to make changes even if the confirmation has already been sent to the ordering party.
When changes are made to a forwarding order in confirmed status, the existing confirmation shall be reset and the status of the
order shall change back to not confirmed. The order shall then be confirmed once again.

Business Blueprint
A forwarding order may also be canceled and a new one created from the original forwarding quotation. It can be specified in
Customizing for the document type, how many forwarding orders are allowed to be created from a particular forwarding
quotation, and this check shall be performed by the system at the time of creation of the forwarding order.
A forwarding settlement document related to a forwarding order (sales document) and the corresponding invoice may also be
canceled. There shall be a possibility to use credit memos in relation to forwarding settlement documents if needed.
A sales request may also be canceled by the ordering party.
In this case, the forwarding order and the original forwarding quotation (original sales request) shall be canceled, which shall
change the status of both documents to canceled.
To record a reason for cancelation on the original sales request (forwarding quotation), a reason code for cancelation can be
maintained based on Customizing settings. This shall be visible in the general data area of the forwarding quotation.
Cancelation of documents shall be irreversible.
Note
Summary of objects used:
Container Sales Request Forwarding Quotation Formatted: Font: BentonSans Book, Font color: Auto
Container Sales Quotation Forwarding Quotation
Container Sales Document Forwarding Order Confirmation
Container Sales Invoice Forwarding Settlement Document Invoice in FI-CA
This process covers a solution for issuance and collection of sundry invoices for container sales which is part of integration points
1350 and 1485 as listed in section 7.5 of this document. Further details related to these processes can be found in
[BBP_FIN_AR_AP_BA] and [BBP_FIN_INV].
Requirements

Business Blueprint
EQP- Management of It shall be possible to - Ability to identify of Implementation 2654

CSAL- Container Sales manage the end-to-end containers marked as
001 Process container sales process in the 'Eligible for Sale
system. (Opportunity Sale)' or
'To be Sold (Wreck)'
with relevant details
- Ability to record
request / demand for
container sale with a
validity
- Ability to manage
status of container
sales request (Open/
Closed / Expired, etc.)
- Availability of a
report to check the
status of container
sale requests per time
period
- Ability to issue a
sales quotation with
container numbers,
proposed price and
additional relevant
details
- Ability to create a
sales document with
the container number,
final price, and
additional relevant
details
- Ability to retain
record of initial and
final sales price
- Ability to issue
invoice for sale
- Ability to issue
cancellation of sales
document
- Ability to manage
release of sold
containers
EQP- Agency Support It shall be possible to provide - Ability to record Implementation 2654
CSAL- for Container Sales system support for request / demand for
002 Process managing container sales to container sale with a
the agent in the scenario validity
when the initial sale is made - Ability to manage

Business Blueprint

by the Logistics Head Office status of container
to the Agent, and sales request (Open/
subsequently by the Agent Closed / Expired, etc.)
to a third party. - Availability of a
report to check the
status of container
sale requests per time
period
sales quotation with
container numbers,
proposed price, and
additional relevant
details
- Ability to create a
sales document with
the container number
and final price
- Ability to retain
record of initial and
final sales price
- Ability to issue
invoice for sale
- Ability to issue
cancellation of sales
document
- Ability to manage
release of sold
containers
EQP- Demand / It shall be possible to record - Ability to record SAP Standard

CSAL- Requests for requests for container sales incoming container
003 Container Sales per location received from sales quotation
potential buyers and manage requests (from agents
a validity and status for such or third party)
requests. - Ability to maintain
validity period for
sales quotation
requests
- Ability to maintain a
status for sales
quotation requests
(met / unmet)
EQP- List of Containers It shall be possible to - Report of containers Implementation 1654

CSAL- Flagged for Sale generate a list of containers that are flagged for
004 that have been flagged for sale (Eligible for
sale (Eligible for Sale/To be Sale/To be Sold)
Sold) per location (with

Business Blueprint

relevant details)
EQP- Sales Quotation It shall be possible to - Generation of a sales SAP Standard

CSAL- for Third-Party generate a quotation for the quotation (email
013 Buyers sale of containers with pre- output) for containers
defined information about with predefined
the container and output this information
via email to third-party (container number,
buyers. size- type, depot
location, quoted sale
price, etc.)
EQP- Sales Quotation It shall be possible to use a - Generation of a sales SAP 1777
CSAL- Template for standard form for the sales quotation (email StandardImplementation (Form)
005 Third-Party Buyers quotation sent to third party output) for containers
buyers with predefined
information
(container number,
size- type, depot
location, quoted sale
price, etc.)
EQP- Volume of It shall be possible to have - Report for volume of Implementation 1203
CSAL- Containers Sold visibility on the volume of containers sold with (under BI
008 containers sold with price average price per time scope)
information per time period, period, size-type (20' /
size-type, and location. 40'), TEUs, and
(this requirement is under BI location (continent /
scope) region / continent).
- Details for sales per
period per location
with details including
location of sale,
container
specifications, details
from the relevant
sales reference /
request (buyer,
invoice, etc.),
container contract
data (leased / owned,
and so on).
EQP- Maintenance of It shall be possible to - Ability to record Implementation Report

CSAL- Initial and Final maintain record of both the initial selling price under BI
007 Sales Price initial sales price of a quoted to buyer scope
container quoted to the (agent / third-party) (together
buyer (intercompany or third - Ability to record final with 491
party), as well as the final selling price agreed and 1203)
sales price agreed after with buyer (agent /

Business Blueprint

negotiation. third-party)
scope)It shall be possible to
maintain record of both the
initial sales price of a
container quoted to the
buyer (intercompany or third
party), as well as the final
sales price agreed after
negotiation.
EQP- Container Sales It shall be possible to create a - Ability to generate Implementation 1779
CSAL- Document sales document with details sales document (form) (FORM)
009 Template of the containers to be sold, with container
including agreed sales price number, details, and
using a standard form. final sales price of the
container
- Ability to send the
sales document to
buyer (agent / third
party via email)
EQP- Container Sales It shall be possible to create a - Ability to generate a SAP Standard
CSAL- Document sales document with details sales document with
014 of the containers to be sold, container number,
including agreed sales price. details, and final sales
price of the container
EQP- Update of It shall be possible to update - Ability to Implementation 2574

CSAL- Container SOLD container status to 'sold' with automatically update
015 Status the creation (and issuance) container status to
of a sales document for the SOLD and blocked
container. container (reason
code 'Sold' (SAL)
- Ability to remove
flag 'Eligible for sale /
to be sold' on
container with setting
of sold status
EQP- Status of It shall be possible to have - Report showing Implementation 491

CSAL- Container Sales visibility on the met and status of container (merged
010 Requests unmet requests for container sales requests per with 1203,
sales per location and time location per time under BI
period (validity). period (met, partially scope)
(this requirement is under BI met, unmet and
scope) open/valid, expired,
etc.)
EQP- Container Sales - It shall be possible to restrict - It shall be possible to SAP Standard

Business Blueprint

CSAL- Authorization access to container sales grant access to all
012 Rules requests and price data by sales requests
maintaining relevant role /references only to HO
authorizations. Sales Manager
- An agency shall be
able to access only the
sales
request/reference in
its country/area of
responsibility, and
access the price only
in the Sales request/
references in which
they are involved (i.e.
they entered the
request)
EQP- Container Sales It shall be possible to create - Ability to generate SAP Standard
CSAL- Invoicing and issue a formal invoice for an invoice (form) for
018 the containers sold to agents container sale
or third parties. - Ability to maintain a
link between the
relevant sales
reference (sales
request number ) and
the respective invoice
number
- Ability to have
visibility on sales
invoice sent
EQP- Notification of It shall be possible to notify - Ability to notify the Implementation 1978
CSAL- Payment the HO Equipment Sales HO sales manager
019 Collection for Manager about the when payment
Third Party collection for payment / against a sale is
Container Sales by payment status for container received via a
Head Office sale. workflow
EQP- Container Sales It shall be possible to create - Ability to generate Implementation 507
CSAL- Invoice Template and issue an invoice for the an invoice for
006 containers sold to agents or container sale using a
third parties using a standard standard template
template. (form)
- Ability to send the
invoice (form) to
agent / third party
buyer via email or
print
EQP- Cancellation / It shall be possible to amend - Ability to amend/ SAP Standard

Business Blueprint

CSAL- Amendment of or cancel a container sale cancel a container
017 Container Sales after the sales document / sales document and
Document or sales invoice has been issued sending the
Invoice to the buyer, by issuing a amendment/
subsequent credit note. cancellation / credit
memo to the buyer
(agent / third-party)
via email.
- Ability to record a
'reason for
cancellation' from a
predefined list for the
sales request (
Container Released
erroneously by depot,
Logistics needs for
export, Client
amendment or
cancellation, Others)
- Ability to
amend/cancel
container sale in the
system (retain the
request / reference
number, and generate
a new version of the
document)
credit note in case the
invoice has already
been issued
EQP- Container Sales It shall be possible to create - Ability to send the Implementation 1779
CSAL- Cancellation / and issue an amendment or sales amendment/
011 Amendment cancellation of a container cancellation
Template sale document. documents (via email)
from the system.
EQP- Container Sale After a container sale is - Ability to activate Implementation 2585
CSAL- Cancellation & cancelled, it shall be possible /retain the last sale
016 Flag for Sale to retain / reactivate the last flag on the container
sale flag (Eligible for Sale / To after a sale has been
be Sold' on a container. cancelled (the flag
was removed and
replaced be SOLD
status when the sales
document was issued
as described in EQP-
CSAL-015)

Business Blueprint
EQP- Container Sales It shall be possible to mark a - Mark container to be Implementation 42

MD- Status container to be sold with sold with a specific
032 specific statuses (To-Be Sold status in the passport.
/ Eligible for Sale) and - Ability to mass
maintain the status in the update sale status at
passport. container level using
filters
EQP- Container Sales It shall be possible to - Ability to copy the Implementation 42

MD- Reference maintain a 'sales reference' in sales reference into
037 the container master data the dedicated field in
(passport) when there is a container master data
corresponding sales process when the sales
in progress. quotation is sent to
the potential buyer
8.4 Process Leased Equipment Management (5.1.1.4.)
The process concerns the end-to-end procurement and return of leased equipment. Procurement captures details about
negotiations with the lessor, agreement creation and execution, equipment pickup or delivery and finally, invoicing and payment.
Leased containers comprise 70 - 80 percent of the overall fleet.

Business Blueprint
Figure 222222 : Leased Equipment Management

Business Blueprint
EQP- Logistics What-if analysis shall be available - Cost saving Roll-in for FBS
CCAL- Management Based regarding the choice of Sub-Lease From, calculation and
001 on What-If Cost One-Way, or Empty Repositioning based decision support to
Analysis on a cost saving estimation for planning optimize choice of
purposes (only).What-if analysis shall be logistics moves
available regarding the choice of Sub-
Lease From, One-Way, or Empty
Repositioning based on a cost saving
analysis.

Component Object
5.1.1.4.1. Manage leased The process covers negotiation and contract SAP TM Freight
equipment contracts preparation for purchase of leased equipment, as Agreement, Agreement,
well as handling contract expiry. SAP MM, SAP Purchase
FI- AP, SAP EM Order,
- Event Handler, Goods
SAP TM Receipt,
Master Data, Invoice,
Event,
Resource
5.1.1.4.2. Manage leased Execution of leased equipment contracts refers to SAP TM - Order Freight
equipment contract the process of issuing call-offs against existing Management Order
execution lease contracts, based on business need and
equipment demand in different locations.
5.1.1.4.3. Manage leased This process covers the details of managing SAP TM - Freight
equipment equipment: Freight Order Order,
pickup/delivery Pickup from an agreed lessor location at an Management, Forwarding
agreed time, or SAP EM - Event Order,
Handler, SAP Event,
Delivery by the lessor to an agreed location at
TM Master Resource
an agreed time.
Data,
5.1.1.4.4. Manage leased This process deals with the handling of the SAP TM Freight
equipment invoicing & recurring invoicing and subsequent payment for Charge Settlement
payment leased equipment. Management, Document ,

Business Blueprint

Component Object
SAP FI-AP Invoice
8.4.4.1 Manage Leased Equipment Contracts
The process covers negotiation and contract preparation for purchase of leased equipment.

Business Blueprint

Business Blueprint
Figure 232323 : Manage Leased Equipment Contracts
The fleet strategy process shall provide input regarding the expected volumes of containers that are to be leased during the
business year. Based on this information, negotiations with the lessors shall be initiated. Negotiations result in a general
agreement on volumes and prices and form the basis for creating leasing procurement contracts.
Lease contracts shall be maintained per lessor and all conditions like build-up and build-down period, per diem, handling charges,
pickup and redelivery quotas, and so on shall be maintained in these contracts. Each contract shall have a validity date. When the
lease contract approaches expiry, several alternatives are available (depending on factors like the age of leased containers, change
in negotiated rates, availability of a purchase option, and so on):
Purchase equipment:
If the option to purchase leased equipment is exercised at the end of a lease contract, the process shall be managed similarly
to the purchase of owned equipment. A purchase order shall be created, approved and sent to the lessor. An invoice shall
then be received against this purchase order from the lessor, verified and paid. At this point in time, changes in the equipment
master data shall be triggered and a fixed asset shall be created as of the datethe date following the expiry date of the leased
contract (as opposed to the date of creation of purchase order or payment).

Business Blueprint
Terminate contract:
If the decision to terminate a lease contract is made, it shall not be possible to extend it anymore, and all containers leased
under this contract shall be returned to the lessor or off-hired.
Extend validity of lease contract:

A lease contract may be extended under the same conditions. In this case, a new validity date shall be recorded.
In case some terms and conditions of the lease agreement are renegotiated with the lessor, the lease agreement shall be
extended under a new version.
Extend under another contract:

It may also be the case that the equipment under an expiring lease contract is moved to another existing lease contract
(usually with more favorable price and conditions).
Figure 242424 : Off-hire Leased Equipment
Solution:
The lease contract shall be modeled in SAP TM as a freight agreement (FA).

Business Blueprint
Note
Generic details regarding SAP TM agreements have been described in [BBP_PRM].
An agreement shall include contractual data, such as a purchasing organization, partners, terms of payment, validity dates, and so
on. Freight agreements (FAs) are also the basis for calculating charges payable to suppliers (in this case, the lessor).
Different freight agreement (FA) types shall be created to deal with the following contract types:
Classical long term agreement: committed for 3, 5, 7 or 8 years with fixed end date.
Off balance sheet agreement: long term agreement made with a bank and generally with a buy-out option at the end.
Long term life cycle agreement: the end date shall depend on the age of each container. The brand new container has a
longer life as compared to a used one.
Short term contract possibility to lease and return container at any time.
Long term with purchase option there is a possibility to purchase the container at the end of the agreement.
Flexible lease: possibility to redeliver container before the end date of the lease but with payment of penalty.
Sub-lease- (from) agreement
One way agreement
The general data section shall allow recording of general information about the agreement, for example, the organizational unit
responsible for the freight order (FO), the validity period of the agreement, and business partner details.
The items section contains the details of the agreement items. At least one item for the agreement shall be defined (relevant for
charge calculation). An Item iin the freight agreement shall correspond to a size-type.
The standard freight agreement shall be extended to be able to record the following information relevant for lease contracts (GAP
419):
On the header level:

No-extension flag
Minimum days of leasing
Build-up period
Build-down period
Repair criteria
On the item level (by size-type):

Off hire quota (per location)
Buyout amount
Buyout period
Depreciation rule and formula

Business Blueprint
Per-diem or rental costs shall appear in an automatically generated monthly freight order based on the calculation of monthly
rental days per container. This calculation of rental days shall take into account the number of calendar days in a month and all
events related to a container in that month, for example, on-hire date, off-hire date, date of total loss declaration, and so on (GAP
2716).
A calculation sheet shall be linked to each agreement item. The calculation sheet can be created from within the agreement, or an
existing calculation sheet can be referenced. A rate table may be maintained for each charge line in the calculation sheet.
Information related to the free rental days, rental per diem charges, pickup charges or credit, drop-off charges or credit, handling
in charges, handling out charges DPP charges, pre-trip and post-trip inspection charges (PTI) charges, repair lump sum charges at
off-hire with maximum andcoverage, and so on relevant for the freight agreement shall be maintained in a calculation sheet
(TCCS).
Note
A dedicated agreement type shall be customized for sub-lease-from contracts. If a sub-lease-from agreement is eligible
for a SWAP, a mutual freight agreement shall be created. Mutual agreements allow setting the same business partner as
both customer and service provider. In case of sub-lease, the mutual agreement shall allow creation of both sub-lease-to
call-off (forwarding order) and sub-lease-from call-off (freight order) against it.
It shall be possible to limit the access to the sensitive fields such as price, depreciation rule, and so on by role authorizations.
It shall also be possible to maintain hyperlinks in the freight agreement to link to documents stored in a separate storage location
(for example, the scanned contract stored in a document management system).
Note
CMA CGM currently uses Contratheque as a document management system to store contracts.
The Finance department shall be informed about freight agreement creation by a periodic report (under scope of BI).t.
Agreement validity shall be maintained using start and end dates and the agreement may be deactivated or released for use. To
monitor expiry dates, a standard task list (POWL) shall be used to display agreements valid or expiring within certain time frames.
Agreement may be extended with our without change in conditions.

Extension of an agreement with or without new version shall be possible. Different versions of agreements, with the same validity
period or with mutually exclusive validity periods can be maintained to ensure that a new agreement does not have to be created
each time an agreements validity period expires or the details of an agreement change depending on the time period.
Note
There can only be one released agreement version with the same validity period or an overlapping validity period.
However, there can be multiple released agreement versions with mutually exclusive validity periods.

Business Blueprint
It shall also be possible to revert to an earlier agreement version by deactivating the released version and releasing the earlier
version. Agreement versions may also be deleted. The version tab contains a list of the agreement versions, including the status of
each version.
If the validity of an agreement is updated, it shall be possible to update the validity of all or selected items in the agreement
simultaneously.
Upon saving, and agreement number shall be generated from a predefined number range. There shall also be a possibility to
record a name for the agreement in a separate field.
A standard approval workflow shall be used for the release of agreements. It shall be possible to specify that an approver is
notified for the release of an agreement, and whether the approver is allowed to edit agreements during the approval workflow.
Upon expiry, it may be decided to move all containers leased under one agreement to another agreement.
The system shall also allow to manually filter resources based on an attribute, for example a lease contract number (GAP 2655)
and to update a field in mass using mass maintenance functionality.
Note
In case there is a need to perform this automatically, an enhancement shall be made to develop a move functionality that
allows moving the resources from one freight agreement to another, and maintains the history of changes in the contract
reference field (GAP 42) in the resource master data as this is relevant for charge calculation.
In case of availability (and maintenance) of the purchase option in freight agreements (GAP 419), the leased containers may be
purchased at a predefined price at the end of the lease period.
The purchase of leased equipment follows the standard purchasing process of purchase order creation, goods receipt and
invoice verification..
A dedicated purchase order type (representing purchase option for leased containers) shall be created in MM to allow
reporting segregation and authorization management.
The purchase order shall be created manually by the user in MM. The SAP TM freight agreement reference shall be keyed in
custom fields in the purchase order (GAP 2606).
The user shall manually key the purchase order price according to the buyout amount maintained in the respective freight
agreement.
The asset shall already be created and used as an account assignment for this purchase order. It shall also be used to identify
the container number.
The purchase order shall be subject to approval A standard workflow (GAP 1931) shall be used for purchase order approval
before it is sent to the lessor
One-step goods receipt shall be done against the purchase order. This shall not trigger any inventory management goods
movement, but is only required as a statistical goods receipt to facilitate the invoice verification process.

Business Blueprint
Note
Additional details related to the purchasing process for leased containers have been described in [BBP_PRM].
Mass maintenance functionality shall be used to update the SAP TM resource master data to update the purchase order reference
in the dedicated field for contract reference (GAP 42).
Note
The creation of an asset in the correct asset class, based on the relevant field update, is to be managed by an
enhancement (in the area of Asset Accounting (GAP 2609)). Further details regarding the creation of assets are described
in [BBP_FIN_Asset].
If upon expiry, the (lease) agreement is to be terminated, a non-extension flag shall be checked on the freight agreement which
shall block the possibility to extend the agreement (GAP 419).
Setting of the non-extension flag shall also update the status of all resources leased under this agreement to eligible for off-hire
(GAP 2596). Maintenance of the off-hire status shall be managed as a custom field on the resource (GAP 42).
The build-down period is a contractually agreed period of time after the contract expiry within which all containers have to be
returned to the lessor. This period shall be recorded at the freight agreement header level (GAP 419). The equipment to be off-
hired shall be returned before the end of the pre-agreed build-down period.
The off-hire status identifies the equipment available for return and is an input for the process of returns management, which
deals with all details of the returns process including identification of return location, confirming availability of return quotas with
the lessor, creation of an off-hire service freight order, and so on.
Note
Details about off-hire freight orders and the off-hire management are described in further detail in [BBP_EQP_LM].
When the container with an off-hire status (eligible for off-hire or to-be off-hired) gates in at the lessors depot with the reference
of an (off-hire) freight order, the resource status shall be updated to off-hired and its validity end date shall be changed to the date
of gate-in (GAP 2717).
This process covers solution for leased equipment contracts and business partners which is part of integration points 1360 and
1480 as listed in section 7.5 of this document. Further details related to procurement processes can be found in [BBP_PRM].
Requirements

PUR- Data Authorization owned/ leased containers) authorizations for

Business Blueprint

003 includes confidential rights to display
information. It shall be possible financial information
to authorize or restrict access to maintained in
certain information maintained purchase contracts.
in the contract based on user
role and organization.
PRM- Manage end of [Equipment] When a leasing Implementation 2596

CTR- leasing contract / contract is not extended and
022 Leased equipment when end date is reached then
status management all container status attached to
regarding the the call-off shall be set to eligible
container for off-hire.
PRM- Off-hire quotas for [Equipment] The system shall Implementation 419
CTR- equipment in provide the ability to include off-
024 contracts hire quotas for equipment in
contracts.
It shall be possible to maintain
off-hire quotas at two levels:
- as per off-hire requests
- as per completion of off-hire
process
It shall be possible to modify
allowed quota on spot basis as
per negotiation with lessors/
lessee.
PRM- Limit the display [Equipment] The equipment Implementation 1858 (see
CTR- equipment depreciation rule in the contract details in
051 depreciation rule in should not be accessible except [BBP_PRM]
the contract by authorized roles.
PRM- Maintain different [Equipment] For Leased SAP Standard

CTR- lease contract types contract, we can have :
054 - Classical Long term agreement:
committed for 3, 5, 7 or 8 years
with fixed end date.
-Off balance sheet agreement:
long term agreement made with
a bank and generally with a buy
out option at the end. Off
balance sheet agreement rental
invoices are based on the
contractual payment schedule.
Invoice reconciliation for such
kind of agreement is then made
with the agreement payment
plan and not with the containers

Business Blueprint

tracking.
- Long term Life cycle
agreement: the end date
depends on the age of each
container. The brand new
container has longer life and a
used container can have shorter
validity if the container is aged.
- Short term contract - we take
the container and can return
anytime.
- Long term with purchase
option - at the end of the
agreement you can purchase if
you want
- Flexible Lease: possibility to
redeliver container before the
end date of the lease but with
payment of penalty.
All leased contract types will
have the same structure.
PRM- Record minimum [Equipment] For leased contract: Implementation 419

CTR- days of leasing in the it shall be possible to record in
055 lease contract the contract the minimum days
of leasing.
PRM- Record build-up [Equipment] For lease call-off, Implementation 419

CTR- period in the lease you have to pick up all
056 contract containers during the buildup
period. No pick up is authorized
after the buildup period.
PRM- Record build-down [Equipment] At the end of the Implementation 419

CTR- period in the lease lease agreement, the containers
057 contract have to be redelivered up to this
period. This period is defined in
the lease call-off.
Daily rental charge of any
Container on-hired after the
Build-down period shall increase
to the Post Build-down Rental.
When starting the build-down
period, the flag Eligible for off
hire should be activated on the
equipment.
PRM- Record free days in [Equipment] The contract shall Implementation 419

Business Blueprint

CTR- the lease contract take into account free days that
058 will influence the lease cost
calculation. The number of free
days can depend on pick-up or
drop-off location and the size-
type
PRM- Manage [Equipment] For lease, the Implementation 419

CTR- depreciation depreciation Formula includes :
061 calculation formula - Depreciation % per year, per
month or per day
- Depreciation period
- Depreciation period type (Day,
Month or Year)
- Maximum depreciation %
For some agreements with
purchase option, the formula
can be the buyout + remaining
per diem till the end date of the
agreement
Sometimes (rarely), it is a fixed
amount changing every year (no
calculation but a kind of DV
schedule)
PRM- Record purchase [Equipment] For each size/type Implementation 419

CTR- option in the lease from the lease contract, a check
062 contract box indicates that the
equipment can be purchased.
PRM- Record buy-out [Equipment] Lease contract: if Implementation 419

CTR- period in month in the contract is relevant for
063 the lease contract purchase option, a buy-out
period expressed in months will
be recorded in the contract.
PRM- Record buy-out [Equipment] Lease contract: if Implementation 419

CTR- amount in the lease the contract is relevant for
064 contract purchase option, the buy-out
amount per size/type to be paid
by CMA CGM shall be recorded
in the contract.
PRM- Maintain DPP [Equipment] Lease contract: the SAP Standard

CTR- amount in lease DPP amount will be recorded in
066 contract the contract.
PRM- Record repair [Equipment] The repair criteria Implementation 419

CTR- condition and are a drop down menu for repair
criteria in lease type selection. Multiple

Business Blueprint

067 contract selections of repair criteria are
possible.
PRM- Record rental per- [Equipment] If you return the SAP Standard
CTR- diem typologies in container before the minimum
069 the lease contract days of leasing (info stored on
the contract):
- For flexible lease: the system
shall calculate the penalty
perdiem to be paid to the leasing
company at the month of
container redelivery. For
instance: you have to keep a
container for 5 years minimum,
per diem is 0.50$. However you
are authorized to redeliver
earlier but per diem would be
then 0.60$ for the whole lease
period. So if you kept a container
2 years, then you have to pay the
additional 0.10$ for 2 years (that
leasing company will charge you
73$ penalty in the invoice of the
month of container redelivery).
For lease agreements with

variable per diem (most of the
time, it is 1way agreement): per
diem shall be changed each time
a container is reaching a specific
lease period (lease periods are
defined in the lease agreement)
For instance: Day 0 to 10: you
pay 0.00$ - Day 11 to 30: you pay
0.60$ - Day 31 to 365: you pay
0.70$ - Day 365 to more: 0.80$
PRM- Record on-hire costs [Equipment] In Lease contract, SAP Standard

CTR- for leased two main on hire costs are
076 equipment managed :
- Handling costs: defined by
size/type and point
- Pickup charges by size/type
Other fees are defined by
size/type, point
PRM- Record off-hire costs [Equipment] In Lease contract, SAP Standard

CTR- for leased two main ""Off Hire"" costs are

Business Blueprint

078 equipment managed during the On-Hire :
- Handling costs : defined by
Size/type and Point
- Delivery charges by Size/type
Size/type, Point, and so on.
PRM- Record Off-Hire [Equipment] In Lease contract, Implementation 419

CTR- Quota for Leased an "Off Hire" quota per Size/type
079 Equipment and point can also be managed.
The quota quantity can be
managed per month, per quarter
or per Agreement.
PRM- Calculate [Equipment] The depreciation Implementation 1496

CTR- depreciation value rules are defined globally for the
050 for total loss and contract while the renewal value
purchase option is defined per size/type. Both are
used in case of equipment total
loss or purchase option. The
system shall calculate the
depreciation value from the
reference contract for creation
of a purchase order for total loss
or purchase option.
PRM- Search Contract by [Equipment] The possibility to Implementation 2594

CTR- technical search contract by technical
080 specification specification (color, CMA CGM
logo) will be provided.
PRM- Per diem retroactive [Equipment] If a container is Implementation 1540

PO- update liked to off returned before the minimum
069 hire anticipation for days of leasing (according to the
Flexible Lease contract), the per diem will have
to change and the new per diem
will be applied for the period the
container has been kept. The
new per diem will be applied
retroactively.
EQP- Container Off-Hire It shall be possible to mark a - Mark container to be Implementation 42

MD- Status container to be off-hired with off-hired with a
010 specific statuses (To-Be Off specific status (To-Be
Hired / Eligible for Off-Hire) and Off Hired / Eligible for
maintain the status in the Off-Hire) in the
passport. passport.
- Ability to mass
update off-hire status
at container level

Business Blueprint

using filters (for
example: set all
containers aged 8
hired') (covered by
EQP-MD-004)
EQP- Equipment It shall be possible to maintain a One field for 'leasing Implementation 419, 2056
PUR- Contracts Per Diem per diem value for (all) per diem' charges
006 Calculation equipment related contracts. (paid to the lessor)
- One field for
'financial per diem'
charges (for financial
lease and bank loans)
- One field for
'amortization per
diem' (based on asset
accounting rules)
- One field for 'total
per diem' charges
- The fields shall be
filled manually by
Logistics department
except 'total per diem'
charges which shall be
automatically
calculated
- For each contract,
only the relevant
fields shall be filled
depending on the
contract type (For
example: for Owned
equipment, only
Amortization field
shall be used while for
Operational Lease,
only Leasing field
shall be used)
8.4.4.2 Manage Leased Equipment Contract Execution
The execution of leased equipment contracts refers to the process of issuing call-offs against existing lease contracts, based on
business need and equipment demand in different locations.

Business Blueprint

Business Blueprint
Figure 252525 : Manage Leased Equipment Contract Execution
Demand for equipment is received at the head office (area managers) from local agency managers. Tactical inventory
management analysis shall provide input regarding a preferred method of sourcing based on predefined rules and conditions.
If equipment leasing is recommended as a sourcing option, a decision to call-off leased equipment against lease contracts shall be
made.
The availability of equipment for leasing shall be checked with the respective leasing partner per location (via e-mail). Based on
this, the initial demand for equipment may be fully or partially met. In case it is not possible to fully satisfy the demand by leasing,
equipment availability might be secured with the next preferred sourcing method as proposed by tactical inventory management.
This may include sub-leasing, leasing for one-way journey, and so on.
Upon confirmation of equipment availability from a leasing partner, the call-off shall be created (approved) and issued to partner.
Incoterms, determining whether the equipment will be delivered by lessor or picked-up by CMA CGM, shall be maintained in the
call-off.
The leasing partner shall confirm the call-off by sending a call-off confirmation. In case of pickup from lessor location, this
confirmation shall include the relevant depot details required to manage equipment pickup. This call confirmation shall be
received at both, the agency and the head-office level.

Business Blueprint
Figure 262626 : Receive Call-off Confirmation from Lessor
Solution: Formatted: Font: 9 pt
The request for equipment is received from local logistic managers.
The functionality to analyze stock situation is required. It is assumed that the tool for resource planning shall cover this
requirement, either by default or by customer-specific enhancement. The user shall access a system or user interface to obtain
this information. Based on the stock condition, a decision shall be made whether or not to sub-lease equipment from partners.
A lease call-off shall be modeled in SAP TM as a freight order (FO) issued against a freight agreement FA) representing a lease
contract.
The (lease call-off) freight order shall be customized to be with restricted processing, meaning it shall not be transportation
planning or execution relevant.

Business Blueprint
Charges shall be calculated when a particular service is assigned to a freight order item to which the freight agreement is linked.
It shall be possible to record free rental days, pick-up or drop-off charges or credit per size-type and location in the (lease call-off)
freight order in case these conditions are call-off specific (GAP 2718). If information regarding free days is maintained at the (lease
call-off) freight order level, it shall overrule the information maintained in the freight agreement. This information shall also be
relevant for the monthly lease invoice verification process.
Note
Credit refers to money received from the lessor (like a rebate) and is in addition to free rental days. Formatted: SAP_NoteParagraph
Note
For one-way, free days shall depend on container size-type and drop-off location.
PTI charges shall be maintained as additional services under the items and the associated quantities shall be manually entered as
determined by the presence or absence of the corresponding service.
Note
PTI charges may also be relevant at the time of off-hire (esp. for Reefers), and shall be similarly recorded in the (off-hire)
Freight Order described in BBP_EQP_LM.
Incoterms shall be used to maintain which party is responsible for the delivery of leased equipment. Incoterms shall also therefore
determine which pickup charges shall be included in the (lease call-off) freight order.
Note
In case of sub-lease:
- A specific freight order type shall be created for sub-lease-from and one-way agreements
- For sub-lease swap, at the time of creation of a (sub-lease-from call-off) freight order, a (sub-lease-to confirmation)
forwarding order shall also be created.
In the case of a sub-lease-from resulting from a misuse of a third-party container by CMA CGM, the (sub-lease-from callfrom call-
off) freight order shall be created. When misuse is identified, standard search functionality and filters shall be used to ascertain if
there is already master data for the business partner and/or a freight agreement (for sub-lease-from) is in place.
A Misuse flag shall be available on the (sub-lease-from call-off) freight order type to identify the initiation of a sub-lease-from in
the case of misuse (GAP 2718).
For misused containers, therefore, when the (sub-lease-from call off) freight order is issued, the status of the resource shall be
manually updated to Eligible for off-hire.

Business Blueprint
The (lease) freight order shall be sent to the lessor using standard output management functions. The mode of communication
(for example, fax, e-mail, and so on.) shall be customizable. The history of sending and printing documents is displayed in the
Output Management tab.
Standard output management features include:

Choose the output method such as print, fax, and e-mail
Preview a document
Enter an attachment
Enter a note
Enter a recipient
Execute the action, such as printing and faxing a freight order
Note
It shall be possible to record specific instructions for one way lease type in the (one-way call-off) freight order output.
It shall be possible to regenerate and execute an action that has already been executed, for example, reprint a business document.
When an action is regenerated, the attributes can be changed, for example, entering a new recipient. The system shall also display
the status of an action after execution. If a particular action was not processed successfully, the system displays the cause of the
error.
In response to the (lease call-off) freight order, the lessor sends a confirmation (via e-mail outside the SAP system). This
confirmation shall include the pickup details (reference number, location, and validity period) in case the Incoterms maintained in
the freight order require pickup of containers by CMA CGM.
The pickup details essentially include the lessor's release order number. Since pickup of these leased containers may be done in
one or several batches, and by one or more parties, this lessor release order number shall be used as a reference in several
subsequent business documents.
An enhancement is needed to store the information from the lessor release order on the (lease call-off) freight order so as to make
it available for use in subsequent documents, for example, CMA CGM (depot release) service freight order issued to shippers to
pick the containers from lessor depot against a booking) (GAP 1531).
It shall therefore be verified if the lessor depot exists as location master data. If not, master data for the lessor depot shall be
created. Alternative location identifiers shall be used to identify a location as a lessor depot.
This process covers solution for leased equipment call-offs which is part of integration points 1360 and 1480 as listed in section 7.5
of this document. Further details related to procurement processes can be found in [BBP_PRM].
Requirements

Business Blueprint
PRM- Link the [Equipment] A purchasing Implementation 42

CTR- leased/owned reference document (call-off) will
090 equipment to a be linked to the leased/owned
purchasing reference equipment.
document
PRM- Calculate and store [Equipment] When creating a Implementation 480

PO- the end date of call-off, the system shall control
059 build-up in the call- that the pick-up is performed
off during the build-up period.
PRM- Definition of call-off [Equipment] Each call-off will Implementation 425

PO- validity dates have a validity date. When the
087 end date is reached, it shall not be
possible to on-hire any containers
under this reference
PRM- Identify if pick-up [Equipment] For lease call-off, SAP Standard Formatted: Font: BentonSans Book
CTR- has to be organized identify if the pick-up has to be
070 in the lease call-off organized or not by CMA CGM.
EQP- Integration of Lease It shall be possible to integrate - Ability to store the Implementation 1531
LEAS- Call-Off lease call confirmation (including information in the
006 Confirmation (from lessor's depot release lease call-off
lessor) into the Call- information) received from the confirmation received
Off Document lessor in the lease call-off from the lessor into
document the call-off document
(including any pick-up
depot details and
release reference
number)
EQP- Misuse Flag It shall be possible to identify if a - Ability to identify if a Implementation 2718, 2733
LEAS- (lease, sub-lease-from, sub-lease- lease, sub-lease-from
007 to) call-off was created for the call-off was created
case of container misuse. because a third-party
container was
misused by CMA
CGM
- Ability to identify if a
sub-lease-to
confirmation was
created because a
CMA CGM container
was misused by a
third party

Business Blueprint
8.4.4.3 Manage Leased Equipment Pickup or Delivery
This process covers the details of managing equipment for the following two options:
Pickup from an agreed lessor location at an agreed time
Delivery by the lessor to an agreed location at an agreed time.
Figure 272727 : Manage Leased Equipment Pickup/Delivery

Business Blueprint
Incoterms maintained in the lease call-off shall determine whether the equipment shall be delivered by lessor or picked-up from
lessor's depot.
In the scenario where the equipment is to be picked up from the lessor's depot, the lessor shall provide the depot location and all
required details for the pickup in the call-off confirmation. Equipment shall be stored in the lessor's depot (if possible) and released
against a booking (when consumed). Details of release against bookings are captured in 5.1.3.1.6. Manage Release Execution in
[BBP_EQP_LM].
In case it is not possible to store the equipment in lessor depot and no booking is available to consume the equipment, an empty
repositioning of the equipment from lessor depot to CMA CGM depot shall be managed. Details of this process are covered in
5.1.3.3.2. Manage Inland Empty Repositioning [BBP_EQP_LM].
After the release of equipment from the lessor depot, master data shall be created as soon as the equipment number is available.
This is referred to as leased equipment on-hiring, and it may happen at different points in the process depending on whether it is a
shipper pickup, intermodal empty repositioning move, and so on.
In the scenario where the containers shall be delivered by the lessor, depot (pool) shall be determined and a depot acceptance
order shall be issued to the depot for the expected equipment shipment from lessor. Details of these processes are described in
5.1.3.2.2. Manage Return depot Determination and 5.1.3.2.4. Manage Depot Acceptance Order in [BBP_EQP_LM].
A delivery confirmation shall be issued to the lessor including details of the depot where the equipment shall be delivered.
Upon arrival at CMA CGM depot, the equipment shall be gated-in and subsequently on-hired.

Business Blueprint
Figure 282828 : On-hire Leased Equipment
Solution:
According to the (lease call-off) freight order incoterms, it shall be determined whether the lessor is responsible for delivery of
leased containers, or if they will be picked up by CMA CGM (or a customer of CMA CGM who will use the container for a booking).
In case equipment cannot be assigned to a booking, it shall be transported empty either by the lessor or by CMA CGM.

Business Blueprint
In case of delivery by lessor when a container is transported without assignment to a booking, a forwarding order shall be created
for the transport with restricted processing meaning it shall not be planning-relevant. This forwarding order shall maintain a
reference to the (lease call-off) freight order. All subsequent documents such as a (Depot Acceptance Order) service freight order
shall maintain a reference to this forwarding order via the transportation unit, TU.
In case of delivery by lessor, the delivery depot shall be determined, and a (depot acceptance order) service freight order shall be
issued to the depot.
Note
Further details of this process have been covered in [BBP_EQP_LM].
The lessor shall be informed about the details of the delivery location (depot) by issuing a delivery confirmation. This information
shall essentially be the same as that contained in the (depot acceptance order) service freight order issued to the depot in
reference to the forwarding order mentioned above.
The data from the (depot acceptance order) service freight order shall be copied into a new output template and sent to the lessor
using output management functions (GAP 2720).
In case of delivery of leased container by the lessor, when the container gates in with the reference number of a (depot acceptance
order) service freight order which is linked to the forwarding order via the transportation unit (TU), a SAP TM resource (master
data) shall be created for each TU using the container number received via the gate-in event. The validity start of the resource
shall be the date of depot gate-in and the status of the resource shall be updated to on-hired (GAP 2726).
Note
The delivery by lessor scenario shall not be applicable in the case of sub-lease-from.
In case CMA CGM is responsible for the transfer of the container, they shall be repositioned empty to a CMA CGM depot. A (depot
acceptance order) service freight order shall be issued to the depot, which shall be linked to a (repositioning booking) forwarding
order and the (intermodal) transport order via the transportation unit (TU).
Note
The empty repositioning scenario is not applicable in the case of sub-lease-from. Further details regarding inland empty
repositioning of containers have been covered in [BBP_EQP_LM].
When a container gates into a depot with the reference to a (depot acceptance order) service freight order that is linked to the
(repositioning booking) forwarding order via the transportation unit (TU), a SAP TM resource (master data) shall be created for
each TU for the container number received via the gate-in event. The validity start date of the resource shall be the date of gate-
out from the lessor depot (relevant for charge calculation) and the status of the resource shall be updated to on-hired (GAP 2726).
Newly leased containers may also be assigned to customer bookings, in which case CMA CGM shall assign a third party (shipper or
carrier) to pick the containers directly from lessors depot for use.

Business Blueprint
Note
Pickup of container from lessor depot by shipper is referred to as merchant haulage. Pickup of container from lessor
depot by transport service provider is referred to as carrier haulage.
For carrier and merchant haulage, the depot details and the release reference number received from the lessor are subsequently
stored on the (lease call-off) freight order (GAP 1531) as described above. These shall be provided to the carrier or shipper
executing the actual transport as (depot release) service freight orders to enable them to pick the containers from the lessors
depot.
Note
Details of this process have been described in [BBP_EQP_LM].
When the container gates out of the lessor depot with the reference of a (depot release) service freight order related to a customer
booking via transportation unit (TU), and the container numbers are available via EDI message, a SAP TM resource (master data)
shall be created for each TU for the container number received via the gate-out event. The validity start date of the resource shall
be the date of gate-out from the lessor depot (relevant for charge calculation) and the status of the resource shall be updated to
on-hired (GAP 2726).
If however, no EDI message is received, the container numbers may be provided by the lessor at a later stage and the resource
master data creation could be performed by manually entering the event for the transportation unit (TU) requiring appropriate
configuration.
If the resource is not created until at the time of terminal gate-in (against a booking reference), upon receipt of the gate-in
message with the container numbers from the terminal, the containers shall be manually on-hired. Resource master data shall be
created for each transportation unit (TU) by adding a container number received via the terminal EDI message. If the date of gate
out from lessors depot is available, the validity start date of the resource shall be set to the date of gate out from the lessor depot.
If this information is not available the resource shall be created as of the date of terminal gate-in and subsequently corrected
manually by entering the gate out event from the lessors depot (from the TU). This manual correction may be, at the latest,
triggered during the lease invoice verification process. Finally the status of the resource shall be updated to on-hired.
Note
In the case of flexible lease or sub-lease-from, after on-hire has been reported, the status of the resource shall be set to
eligible for off-hire. For one-way, after on-hire the status of the resource shall be set to to be off-hired

Note
Summary of objects used:
Lease / Sub-Lease-From Contract Freight Agreement (FA)

Business Blueprint
Lease / Sub-Lease-From Call-off Freight Order (FO)
Requirements
PRM- Link between the [Equipment] The system shall keep a Implementation 42
CTR- equipment and the technical link between the
025 leasing contract ID equipment and the leasing contract
ID
[Equipment] A purchasing reference
document (call-off) will be linked to
the leased/owned equipment.
EQP- Activation and It shall be possible to add or remove - Create master data Implementation 2726,
MD- Deactivation of leased container (master data) from for leased container 2717
051 Leased (and Sub- fleet at the time of container 'on- when it is added to the
Leased) Container hire' and 'off-hire' respectively. fleet (on-hired)
when it is removed
from the fleet (off-
hired)
EQP- Delivery It shall be possible to send a delivery - Delivery confirmation Implementation 2720
LEAS- Confirmation to confirmation to the lessor, with (Form) with reference
008 Lessor required depot details and reference to the respective lease
number needed for the delivery of call-off, depot details
containers to CMA CGM depot and depot delivery
(Scenario: delivery of leased reference number.
containers by lessor)
8.4.4.4 Manage Leased Equipment Invoicing & Payment
This process deals with the handling of the recurring invoicing and subsequent payment for leased containers.

Business Blueprint
Figure 292929 : Manage Leased Equipment Invoicing & Payment
The leasing partner sends a monthly invoice (via a flat excel file). This invoice is at equipment level and can consist of around
200,000 line items, including per diem charges for each equipment, as well as charges for each event related to the equipment (for
example, handling charges at the time of on-hire).

Business Blueprint
Invoice verification for leased equipment requires all events for each equipment to be maintained, and the respective charges for
these events be pulled from the lease contracts. This information is reconciled against the invoice sent by the leasing partner (at
the equipment level).
Following invoice verification, some differences may be found. If valid, these shall be handled with the issuance of credit notes. If
however the differences are found to be due to errors in operational tracking and management of leasing containers, corrective
actions shall be taken.
Following are some checks and subsequent corrective actions that may be performed during lease invoice verification process:
Check any differences in the rates as maintained in the leasing contracts and as charged in the invoice (per diem, handling
charges, drop-off charges, pickup charges, PTI, lump sum repair, and so on):
o For the rate depending on the delivery or redelivery location (handlings, PUC, DOC), check the location.
o For the variable per diem, check the number of days on lease.
o Check if the pickup or drop-off credits negotiated with the lessor for a certain location have been included (and not
charged).
o Check if the charges from the correct contracts have been taken into account (new versions, new conditions of the
agreement or the transfer of the equipment to a new contract within the month).
o Check if the equipment has been invoiced more than once for the same kind of charge and for the same period.
Check any differences in number of days invoiced:

o Check if the free days have been taken into consideration.
o Check if the on-hire and off-hire dates are correct.
o Check if the equipment off-hired (either redelivered, declared as total loss or purchased) in the system appears in the
lessor invoice as leased.
o Check if the correct numbers of days are invoiced for any equipment declared in total loss (based on lessor policy of
stopping per diem charging as of the date of declaration, or at issuance of payment).
o Check if the equipment off-hired as per the invoice appears as leased in the system (action: update the system to capture
the actual status of the equipment which can be ascertained by documents like EIR, declaration of total loss, and so on in
the case of redelivery).
Check for equipment that is not recognized:

o Check if equipment was on-hired under the wrong contract (for instance equipment from one lessor was on-hired under
another lessors contract).
o Check if the equipment that is not recognized has been added to the invoice by error
o Check if the equipment was leased, but the on-hire was missed, or the equipment was meant to be leased, but was not
picked-up.
Check for leased equipment that has been missed in the invoice:
o Check if equipment was on-hired under the wrong contract (for instance equipment from one lessor was on-hired under
another lessors contract).
o Check if the equipment has not been included in the invoice by error.
o Check if the equipment was redelivered or declared in total loss (lessor stops invoicing), but not off-hired in the system

Business Blueprint
Check for equipment under the wrong contracts:

o Check if the equipment is on-hired under the incorrect contract from the same lessor (action: update equipment master
data to correct the contract reference).
o Check if the incorrect contract number is used by the lessor in the invoice.
Check if any charges have been wrongly invoiced:

o Check if the lump sum repairs, DOC, or handling in have been charged but the equipment was not redelivered but
declared in total loss.
o Check if any handling out charges, DOC, pre-trip inspection (PTI) charges have been invoiced while there are no on-hire
events.
o Check if any handling in charges, DOC, post-trip inspection (PTI) charges have been invoiced while there are no off-hire
events.
Check if the equipment size-type is correct:

o Check if the size-type is incorrectly invoiced or incorrectly maintained in the system.
Check if the invoicing period is correct:

o Check if all charges are relevant only for the current month.
o Check if the charge from a previous invoice (already paid) is not charged again.
It is important to mention that the lease invoice shall be paid to the partner before it undergoes the verification process. Following
verification, the differences (if any) shall be handled via issuance or receipt of debit or credit notes.
Solution:
Due to the high volume of line items (up to 200,000 items) in the invoice received from the lessor, it is not considered feasible to
use the standard invoice verification process for leased (and sub-leased) containers.
Note
The standard invoice verification process is defined in [BBP_FIN_AR_AP_BA].
It is therefore planned to use a dashboard to support this process. The verification of lessor invoices against the events reported at
the container level and the respective charges maintained in the freight agreements (lease or sub-lease-from contracts) using the
dashboard shall be an enhancement (GAP 482).
The dashboard shall be populated with all events related to the equipment, and the corresponding charges for these events as
maintained in the freight agreements (lease contracts).

Business Blueprint
Once a leasing invoice is received and captured in the dashboard, the invoice shall be posted and paid directly irrespective of any
possible discrepancies. Any discrepancies found (see step 3-5 below) shall either be resolved in FI-AP with a manual issuance of a
credit memo, or by identification and correction of the error.
The following scenario shall apply to invoice verification for leasing processes:
1. The dashboard shall be fed with the detailed invoice from the supplier (it shall be possible to accommodate multiple invoice
patterns from different lessors) and the (automatically created) monthly service or purchase orders based on events collected
in the respective month. These automatic service purchase orders shall be triggered by the freight settlement document
(FSD) based on-hire, off-hire and automatically generated monthly rental (generated automaticallyGAP 2716 at the end of
each month) freight orders..
Note
For each lease call-off, there shall be three freight orders:
- An (on-hire or lease call-off) freight order capturing all relevant on-hire costs
- An (off-hire) freight order to record the off-hire request to the lessor, and all associated off-hire costs.
- An automatically generated freight order to calculate per-diem or rental costs based on the calculation of monthly
rental days per container, taking into account the number of calendar days in a month and all events related to a
container in that month (for example, on-hire date, off-hire date, date of total loss declaration, and so on) (GAP 2716).
2. The dashboard shall highlight discrepancies between the expected charges per container and the charges invoiced by the
lessor (GAP 482).
3. Discrepancies shall be managed through a manual analysis process for each individual item.
4. When the mistake in the invoice is discovered to be on the lessor side: credit notes shall be created in FI-AP. If the error is on
CMA side, manual adjustments of SAP TM/SAP EM data shall be made to correct the reason for the discrepancy as described
above.
Note
High-level details of this enhancement and the associated GAP 482 (to be detailed further during implementation phase)
are described in [BBP_FIN_AR_AP_BA].
Note
Rental invoices for off-balance sheet lease agreement shall be reconciled with the contractual payment schedule and not
with container tracking. Formatted: English (United States)
This process covers solution for monthly payment and reconciliation for leased equipment which is part of integration points 1360
and 1480 as listed in section 7.5 of this document. Further details related to invoicing processes can be found in
[BBP_FIN_AR_AP_BA].

Business Blueprint
Requirements
EQP- Invoicing and It shall be possible to link the lease - Invoice verification and Implementation 482,
LEAS- Payment for Leased contract including payment payment for purchase 2716
004 Equipment conditions, and the creation of orders
purchase orders / call offs against - Credit notes receipt
these contracts for procurement of and management
leased equipment, to the associated
- Ability to control
invoice verification and payment
payment at container
process. It shall also be possible to
level (as containers
receive credit notes.
under the same call-off
may have different lease
start and end dates)
8.5 Process Equipment Sub-Lease-From Management (5.1.1.5.)
Sub-Lease-From is the lease of equipment from a third party, for example another shipping company. While more expensive than
the lease of containers directly from a lessor, sub-lease-from offers higher flexibility in the form of no minimum lease period
(containers can be off-hired anytime) and better availability of containers on short notice in deficit locations.
One-way is a type of sub-lease-from where equipment is subleased for a particular journey, and returned to sub-lease partner at
the end of the journey.
This process concerns the end- to-end procurement and return of sub-leased-from container, capturing details about negotiations
with sub-lease-from partner, agreement creation and execution, equipment pickup and finally, management of recurring invoicing
and payment.

Business Blueprint
Figure 303030 : Equipment Sub-Lease-From Management

Business Blueprint
EQP- Identification of It shall be possible to distinguish - Ability to identify SAP Standard

SLEA- Sub-Lease Swap vs. between the cases of a normal sub- sub-lease-to/from
004 Sublease From / To lease-to / from without counter containers with or
commitment, and the case of sub- without counter
lease swap with counter sub-lease-from/to
commitment. In the case of sub- containers with
lease swap it shall be possible to details of partner,
correlate the call-off for sub-lease contracts, etc.
from and the counter sub-lease to
call-off.
EQP- Balance of It shall be possible to have visibility - Report on Implementation 492

SLEA- Containers in Sub- on the volumes of containers in container volumes
005 Lease Swap sub-lease swap arrangements per in sub-lease swap
Arrangement partner. arrangements per
(this requirement is under BI scope) partner at a point in
time.
EQP- Sub-Lease Volumes It shall be possible to have visibility - Report on volumes Implementation 499 (under
SLEA- per Partner on volume of business per partner of containers per BI scope)
007 in sub-lease-to, sub-lease-from, size-type, per
one-way and Cabotage partner with pick-up
arrangements. / release date and
(this requirement is under BI scope) location per time
period
EQP- Status of Sub-Lease It shall be possible to track - Report showing Implementation 410 (under
SLEA- and One-Way containers in sub-lease and one- status of containers BI scope)
011 Containers way arrangements based on a in sub-lease and
specific status and have visibility on one-way
the pick-up and return date and arrangements
place. including details like
(this requirement is under BI scope) date of pick-up,
location of pick-up (
continent, region,
hub, point, pool),
current status (still
out or returned),
number of days in
use, reference
contract and partner
details where
relevant details for
return date and
location.

Business Blueprint
CCAL- Management regarding the choice of Sub-Lease calculation and
001 Based on What-If From, One-Way, or Empty decision support to
Cost Analysis Repositioning based on a cost optimize choice of
saving estimation for planning logistics moves
purposes (only).What-if analysis
shall be available regarding the
choice of Sub-Lease From, One-
Way, or Empty Repositioning
based on a cost saving analysis.

Component Object
5.1.1.5.1. Manage sub-lease-from The process covers the preparation of sub-lease- SAP TM Freight
contracts from contracts and the preceding negotiation Agreement, Agreement,
process. It also covers the management of sub- SAP TM Event,
lease-from contract validity. Master Data, Resource
SAP FI- AP, SAP
EM Event
Handler
5.1.1.5.2. Manage sub-lease-from Execution of sub-lease-from contract refers to the SAP TM - Order Freight
contract execution process of issuing call-offs based on business need Management Order
and equipment demand in different locations.
5.1.1.5.3. Manage sub-lease-from This process covers the details of managing SAP TM - Order Freight
pickup equipment pick-up from the sub-lease-from Management, Order,
partner and the following equipment on-hire SAP EM - Event Forwarding
process. Handler, SAP Order,
TM Master Event,
Data Resource
5.1.1.5.4. Manage sub-lease-from This process deals with the handling of the SAP TM Freight
invoicing & payment recurring invoicing and subsequent payment for Charge Settlement
the sub-leased equipment. Management, Document ,
SAP FI-AP Invoice

Business Blueprint
8.5.4.1 Manage Sub-Lease from Contracts
The process covers the preparation of sub-lease-from contracts and the preceding negotiation process.

Business Blueprint

Business Blueprint
Figure 313131 : Prepare Sub-Lease-From Contracts
A need for a sub-lease partner may be identified based on business demand. Potential partners are evaluated and approached for
negotiations. At the end of the negotiation process, basic contract conditions are agreed. This allows for the creation of a sub-
lease contract.

Business Blueprint
Sub-lease contracts shall be maintained per lessor and all conditions like build-up and build-down period, per diem, handling
charges, pickup and redelivery quotas, and so on shall be maintained in these contracts. Any changes in terms and conditions
during the life of the contract shall be maintained as new versions of the original contract.
If the sub-lease partner is valid for both sub-lease-from and sub-lease-to arrangements, parallel contracts with same terms and
conditions shall be maintained with the same conditions.
Each contract shall have a validity date. When the sub-lease contract approaches expiry, two possible options shall be available:
Terminate contract:
If the decision to terminate a sub-lease contract is made, the status for equipment under the contract shall be updated to To-
be off-hired. The off-hire status shall identifies the equipment available for return and is an input for the process of returns
management, which deals with all details of the returns process including identification of return location, confirming
availability of return quotas with the (sub) lessor, and so on. The equipment shall be returned during the pre-agreed build-
down period after contract expiry at which point in time the equipment master data shall be deactivated. This is referred to as
off-hire.
Sub-leased equipment may also be returned after a specific journey for which it was used (one-way), or when no longer
needed, as sub-lease provides higher flexibility in terms of no minimum lease periods.
Extend validity of (sub) lease contract:

A sub-lease contract may be extended. In this case, a new validity date or changes in contract conditions shall be recorded in a
new version of the contract.
Note
Solution for management of sub-lease-from contracts is covered in section 8.4.4.1 Manage Leased equipment Contracts
of this document.
Requirements

PUR- Data Authorization owned/ leased containers) authorizations for
003 includes confidential information. rights to display
It shall be possible to authorize or financial information
restrict access to certain maintained in
information maintained in the purchase contracts.
contract based on user role and
organization.
contracts.
It shall be possible to maintain

Business Blueprint

off-hire quotas at two levels:
process
allowed quota on spot basis as
per negotiation with lessor /
lessee.

the lease call-off.
Container then on hire after the
period, the flag Eligible for off
hire should be activated on the
equipment.
drop-off location and the size-
type
PRM- Manage [Equipment] For lease, the Implementation 419

CTR- depreciation depreciation Formula includes :
061 calculation formula - Depreciation % per year, per
month or per day
Month or Year)
purchase option, the formula can
be the buyout + remaining per
diem till the end date of the
agreement

Business Blueprint

schedule)
PRM- Limit the display [Equipment] The equipment Implementation 1858 (see
CTR- equipment depreciation rule in the contract details in
051 depreciation rule in should not be accessible except [BBP_PRM]
the contract by authorized roles.

PRM- Record repair [Equipment] The repair criteria Implementation 419

CTR- condition and are a drop down menu for repair
067 criteria in lease type selection. Multiple selections
contract of repair criteria are possible.
PRM- Identify if the lease [Equipment] A swap indicator has SAP Standard
CTR- contract is subject to to be managed in the Lease
073 lease swap Contract.

CTR- for leased two main on hire costs are
076 equipment managed :
size/type and point
size/type, point

CTR- for leased two main Off Hire costs are
078 equipment managed during the On-Hire :
Size/type and Point
PRM- Record Off-Hire [Equipment] In Lease contract, an Implementation 419

CTR- Quota for Leased Off Hire quota per Size/type and
079 Equipment point can also be managed. The
quota quantity can be managed
per month, per quarter or per
Agreement.
PRM- Calculate [Equipment] The depreciation Implementation 1496

CTR- depreciation value rules are defined globally for the
050 for total loss and contract while the renewal value
purchase option is defined per size/type. Both are
used in case of equipment total

Business Blueprint

loss or purchase option. The
system shall calculate the
depreciation value from the
reference contract and create a
purchase order for total loss or
purchase option.
PRM- Link between the [Equipment] The system shall Implementation

CTR- leasing contract and provide the ability to keep a link
026 the sublease between the leasing contract
contract for (CMA CGM as a customer) and
containers and the sublease contract (CMA CGM
vessels as a supplier).
PRM- Record rental per- [Equipment] If you return the SAP Standard
CTR- diem typologies in container before the minimum
069 the lease contract days of leasing (info stored on the
contract):
- For flexible lease: the system
shall calculate the penalty
perdiem to be paid to the leasing
company at the month of
container redelivery. For
instance: you have to keep a
container for 5 years minimum,
per diem is 0.50$. However you
are authorized to redeliver earlier
but per diem would be then 0.60$
for the whole lease period. So if
you kept a container 2 years, then
you have to pay the additional
0.10$ for 2 years (that leasing
company will charge you 73$
penalty in the invoice of the
month of container redelivery).
For lease agreements with

variable per diem (most of the
time, it is 1way agreement): per
diem shall be changed each time
a container is reaching a specific
lease period (lease periods are
defined in the lease agreement)
For instance: Day 0 to 10: you pay
0.00$ - Day 11 to 30: you pay
0.60$ - Day 31 to 365: you pay
0.70$ - Day 365 to more: 0.80$
EQP- Container Off-Hire It shall be possible to mark a - Mark container to be Implementation 42

Business Blueprint

MD- Status container to be off-hired with off-hired with a
010 specific statuses (To-Be Off Hired specific status (To-Be
/ Eligible for Off-Hire) and Off Hired / Eligible for
maintain the status in the Off-Hire) in the
passport. passport.
- Ability to mass
update off-hire status
at container level
using filters (for
example: set all
containers aged 8
hired') (covered by
EQP-MD-004)
8.5.4.2 Manage Sub-Lease-From Contract Execution
Execution of sub-lease-from contract refers to the process of issuing call-offs based on business need and equipment demand in
different locations.

Business Blueprint
Figure 323232 : Manage Sub-Lease-From Contract Execution

Business Blueprint
Demand for equipment is received at the head office (area managers) from local agency managers. Tactical inventory
management analysis shall provide input regarding a preferred method of sourcing based on predefined rules and conditions.
If sub-lease of equipment is recommended as a sourcing option, a decision to sub-leased equipment against sub-lease contracts
shall be made.
The availability of equipment for leasing shall be checked with the respective sub-lease partner per location (via e-mail). Based on
this, the initial demand for equipment may be fully or partially met. In case it is not possible to fully satisfy the demand by sub-
leasing, equipment availability might be secured with the next preferred sourcing method as proposed by tactical inventory
management. This may include leasing, leasing for one-way journey, and so on.
Upon confirmation of equipment availability from a leasing partner, the (sub-lease-from) call-off shall be created (approved) and
issued to partner.
In case of a sub-lease swap arrangement where same quantities of equipment are exchanged between two parties in different
locations, a parallel sub-lease-to call-off shall also be created with the same information.
The sub-lease partner shall confirm the call-off by sending a call-off confirmation which is received at both the agency and head
office level. The confirmation shall include the relevant depot details required to manage equipment pickup.
Figure 333333 : Receive Confirmation of Sub-Lease-From Reference

Business Blueprint
Note
Solution for sub-lease-from contract execution is covered in section 8.4.4.2 Manage Leased Equipment Contract
Execution of this document.
Requirements
EQP- Open / Called-off It shall be possible to have visibility - Report on the Implementation Under
SLEA- Quantity in Sub- on the open and called-off quantity volumes of containers BI
006 Lease Call-off in sub-lease-to and sub-lease-from that are still available scope
call-off. to be picked up (open
(this requirement is under BI scope) quantity) per sub-
lease-from contract,
partner and location, at
a point in time
- Report on the
volumes of containers
that are picked-up
(called-off) per sub-
a point in time
- Report on the
that are still to be
released (open
quantity) per sub-
lease-to contract,
a point in time
- Report on the
that are released
(called-off quantity)
per sub-lease-to
contract, partner and
location, at a point in
time.
PRM- Calculate and store [Equipment] When creating a call- Implementation 480
PO- the end date of build- off, the system shall control that the
059 up in the call-off pick-up is performed during the
build-up period.
PRM- Definition of call-off [Equipment] Each call-off will have a Implementation 425
PO- validity dates validity date. When the end date is
087 reached, it shall not be possible to
on-hire any containers under this

Business Blueprint

reference
PRM- Link the [Equipment] A purchasing reference Implementation 42

CTR- leased/owned document (call-off) will be linked to
090 equipment to a the leased/owned equipment.
purchasing reference
document
EQP- Integration of Lease It shall be possible to integrate lease - Ability to store the Implementation 1531
LEAS- Call-Off Confirmation call confirmation (including lessor's information in the
006 (from lessor) into the depot release information) received lease call-off
Call-Off Document from the lessor in the lease call-off confirmation received
document from the lessor into the
call-off document
(including any pick-up
depot details and
release reference
number)
EQP- Misuse Flag It shall be possible to identify if a - Ability to identify if a Implementation 2718,
LEAS- (lease, sub-lease-from, sub-lease-to) lease, sub-lease-from 2733
007 call-off was created for the case of call-off was created
container misuse. because a third-party
container was misused
by CMA CGM
sub-lease-to
confirmation was
created because a CMA
CGM container was
misused by a third
party
PRM- Output specific Display the specific instructions for Implementation 486
PO- instructions for on- on-hire of one-way lease in the lease
104 hire of one-way lease order form.
in the lease order
form
8.5.4.3 Manage Sub-Lease-From Pickup
This process covers the details of managing equipment pickup from the sub-lease-from partner and the on-hire process.

Business Blueprint

Business Blueprint
Figure 343434: Manage Sub-Lease from Pickup
The sub-lease partner provides the depot location and all required details for the pickup of equipment in the call-off confirmation.
Equipment shall be stored in the sub-lease partner's depot (if possible) and released against a booking (when consumed). Details
of release against bookings are captured in 5.1.3.1.6. Manage Release Execution in [BBP_EQP_LM].

Business Blueprint
In case it shall not be possible to store the equipment in sub-lease partner's depot and no booking shall be available to consume
the equipment, an empty repositioning of the equipment from lessor depot to CMA CGM depot shall be managed. Details of this
process are covered in 5.1.3.3.2. Manage Inland Empty Repositioning.
Note
As sub-leased equipment is called off to overcome deficit equipment situations, it will almost always be consumed for
commercial use. Empty repositioning of sub-leased equipment is not common practice.
As equipment is released from lessor depot, master data shall be created as soon as the equipment number is available. This is
referred to as leased equipment on-hiring, and it may happen at different points in the process depending on whether it is a shipper
pickup, intermodal empty repositioning move, and so on.

Business Blueprint
Figure 353535 : On-hire Sub-Leased Equipment
Note
Solution for sub-lease-from pickup or delivery management has already been covered in section 8.4.4.3 Manage Leased
Equipment Pickup or Delivery. Solution details for Surveyor contract and purchase order are described in sections
10.1.4.1.3 and 10.5.4.1.6 in [BBP_PRM].
Requirements
EQP- Default Status for It shall be possible to assign a default - After on-hire, the SAP Standard
SLEA- Flexible Lease, Sub- status to containers under flexible default status of
016 Lease From and One lease, sub-lease-from and one-way container under flexible
Way contracts right after on-hire. lease or sub-lease-from
contracts to be set to
'eligible for off-hire'
- After on-hire, the
default status of one-
way container to be set
to 'to be off-hired'
EQP- Activation and It shall be possible to add or remove - Create master data for Implementation 2726,
MD- Deactivation of leased container (master data) from leased container when it 2717
051 Leased (and Sub- fleet at the time of container 'on-hire' is added to the fleet
Leased) Container and 'off-hire' respectively. (on-hired)
when it is removed from
the fleet (off-hired)
8.5.4.4 Manage Sub-Lease-From Invoicing & Payment
This process deals with the handling of the recurring invoicing and subsequent payment for the sub-leased-from equipment.

Business Blueprint
Figure 363636: Manage Sub-Lease from Invoicing & Payment

Business Blueprint
Invoicing and payment for equipment sub-leased from partners follows the same process as that for leasing. For details of Formatted: Font: BentonSans Book
invoicing and payment for sub-lease-from, refer to section 8.4.4.4. Manage Leased Equipment Invoicing & Payment of this
document.

Note
The solution for sub-lease-from invoicing and payment is covered in section 8.4.4.4 Manage Leased Equipment Invoicing
& Payment of this document.
Requirements
EQP- Invoicing and It shall be possible to link the sub- - Invoice verification Implementation 482,
SLEA- Payment for Sub- lease-from contract including payment against purchase order 2716
002 Lease-from conditions, and creation of purchase for sub-lease-from.
Equipment orders (call-off) to the associated - Ability to control
invoice verification and payment payment at container
process. level (as containers
under the same call-off
may have different lease
start and end dates)
- Credit notes receipt
and management
8.6 Process Equipment Sub-Lease-To Management (5.1.1.6.)
Equipment may be sub-leased-to a partner that may be a shipping line, a trader, a forwarder, an agency, or an end-customer. Sub-
lease-to arrangements are typically short term, but in some cases can last up to a few years.
This process concerns the management of this process including details about agreement negotiation, equipment release and
finally, invoicing and collection of payment.

Business Blueprint
Figure 373737 : Equipment Sub-Lease-To Management

Business Blueprint
CCAL- Management regarding the choice of Sub-Lease calculation and
001 Based on What-If From, One-Way, or Empty decision support to
Cost Analysis Repositioning based on a cost saving optimize choice of
estimation for planning purposes logistics moves
(only).What-if analysis shall be
available regarding the choice of
Sub-Lease From, One-Way, or Empty
Repositioning based on a cost saving
analysis.
EQP- Identification of It shall be possible to distinguish - Ability to identify SAP Standard

SLEA- Sub-Lease Swap vs. between the case of a normal sub- sub-lease-to/from
004 Sublease From / To lease-to / from without counter containers with or
commitment, and the case of sub- without counter
lease swap with counter sub-lease-from/to
commitment. In the case of sub- containers with
lease swap it shall be possible to details of partner,
correlate the call-off for sub-lease contracts, etc.
from and the counter sub-lease to
call-off.
EQP- Balance of It shall be possible to have visibility - Report on Implementation 492 (under
SLEA- Containers in Sub- on the volumes of containers in sub- container volumes BI scope)
005 Lease Swap lease swap arrangements per in sub-lease swap
Arrangement partner. arrangements per
(this requirement is under BI scope) partner at a point in
time.
EQP- Open / Called-off It shall be possible to have visibility - Report on the Implementation Under BI
SLEA- Quantity in Sub- on the open and called-off quantity in volumes of Scope
006 Lease Call-off sub-lease-to and sub-lease-from call- containers that are
off. still available to be
(this requirement is under BI scope) picked up (open
quantity) per sub-
partner and
location, at a point
in time
- Report on the
volumes of
containers that are
picked-up (called-
off) per sub-lease-
from contract,

Business Blueprint

partner and
in time
- Report on the
volumes of
containers that are
still to be released
(open quantity) per
sub-lease-to
contract, partner
and location, at a
point in time
- Report on the
volumes of
containers that are
released (called-off
quantity) per sub-
lease-to contract,
partner and
in time.
EQP- Sub-Lease Volumes It shall be possible to have visibility - Report on volumes Implementation 499 (under
SLEA- per Partner on volume of business per partner in of containers per BI scope)
007 sub-lease-to, sub-lease-from, one- size-type, per
way and Cabotage arrangements. partner with pick-up
(this requirement is under BI scope) / release date and
location per time
period

Component Object
5.1.1.6.1. Manage sub-lease-to The process covers the preparation of sub-lease-to SAP TM - Forwarding
contracts contracts and the preceding negotiation process. It Agreement Agreement
also covers sub-lease-to contract expiry.
5.1.1.6.2. Manage sub-lease-to Execution of sub-lease-to contracts refers to the SAP TM - Order Forwarding
contract execution process of issuing call-offs based on equipment Management, Order,
availability and demand (from partners) in different SAP TM Freight
locations. Master Data, Order,
SAP EM - Event Event,

Business Blueprint

Component Object
Handler Resource
5.1.1.6.3. Manage sub-lease-to This process covers the details of managing SAP TM - Order Freight
redelivery equipment redelivery from sub-lease-to partner. Management, Order,
SAP TM Event,
Master Data, Resource
SAP EM - Event
Handler
5.1.1.6.4. Manage sub-lease-to This process deals with the recurrent generation of SAP TM Forwarding
invoicing and collection invoicing and subsequent collection of payment for Charge Settlement
the sub-leased-to equipment. Management, Document,
SAP FI-CA Invoice
8.6.4.1 Manage Sub-Lease-To Contracts
The process covers the preparation of sub-lease-to contracts and the preceding negotiation process. It also covers sub-lease-to
contract expiry management.
Cabotage is a type of sub-lease-to where the return date and location of the equipment may be agreed in advance with the sub-
lease partner and sub-lease during this agreed time period may be free of charge. Cabotage is often used to avoid costs related to
empty repositioning of equipment.

Business Blueprint
Figure 383838 : Manage Sub-Lease-To Contracts

Business Blueprint
A need for a sub-lease partner may be identified, or a request for partnership may be received from a third party. Often the same
sub-lease partner is valid for both sub-lease-from and sub-lease-to agreements (to be able to manage an equipment sub-lease
swap). Potential partners are evaluated and negotiations are carried out. At the end of the negotiation process, basic contract
conditions are agreed, which allow for the creation of a sub-lease contract.
Sub-lease contracts shall be maintained per partner (lessee) and all conditions like build-up and build-down period, per diem,
handling charges, pickup and redelivery quotas, and so on shall be maintained in these contracts. Any changes in terms and
conditions during the life of the contract shall be maintained as new versions to the original contract.
If the sub-lease partner is valid for both sub-lease-from and sub-lease-to arrangements, parallel contracts shall be maintained with
the same conditions.
Each contract shall have a validity date. When the sub-lease contract approaches expiry, two possible options shall be available:
Terminate contract:
If the decision to terminate a sub-lease-to contract is made, the equipment sub-leased under this contract shall be redelivered
by the partner. Equipment sub-leased-to partners may also be returned by partners before the expiry of the contract based on
an explicit return request by partner.
Extend validity of (sub) lease contract:

A sub-lease contract may be extended. In this case, a new validity date, together with changes in contract conditions (if any)
shall be recorded in a new version of the contract.
Solution:
A sub-lease-to contract shall be modeled in SAP TM as a forwarding agreement (FWA), using all the enhanced features of the
agreement (GAP 419).
Note
Forwarding and freight agreements represent the same technical object in SAP TM. Generic details regarding SAP TM
agreements are described in [BBP_PRM].
An agreement includes contractual data, such as sales organization, ordering party or carrier, terms of payment, validity dates,
and so on. Forwarding agreements (FWAs) are also the basis for calculating charges billable to customers (in this case, sub-lease
partner).
The general data section shall allow recording of general information about the agreement, for example, the organizational unit
responsible for the forwarding order (FWO), the validity period of the agreement, and business partner details.
The items screen area shall contain the details of the agreement items. At least one item for the agreement shall be defined
(relevant for charge calculation). In a forwarding agreement for sub-lease-to contracts, one item shall exist per equipment size-
type (identified by equipment type) for which the agreement applies. It shall be possible to define services (for example pickup or
handling services) as agreement items hierarchically below equipment size-type items.

Business Blueprint
A calculation sheet shall be linked to each agreement item. The calculation sheet can be created from within the agreement, or an
existing calculation sheet can be referenced. A rate table can be maintained for each charge line in the calculation sheet. By usage
of locations or zones as dimensions for the rate table it shall be possible to maintain charges for services specific to locations, for
example pickup charges.
The change documents section of the agreement shall allow the user to view all changes made to an agreement. The changes are
listed by date and time. It shall be possible to view the details of the changes at header level and at field level.
A dedicated agreement type shall be customized for sub-lease-to contracts.
In case of a sub-lease SWAP, a mutual agreement shall be used. Mutual agreements allow setting the same business partner as Formatted: Font: BentonSans Book
both customer and service provider. In case of sub-lease, the mutual agreement shall allow creation of both sub-lease-to call-off
(forwarding order) and sub-lease-from call-off (freight order) against it.
If an agreement is copied, the system shall copy the calculation sheets, rate tables, and scales created from within the agreement
or referenced in the agreement. If an agreement is deleted, the system shall delete the calculation sheets, rate tables, and scales
that were created from within the agreement, but not the ones referenced in the agreement.
Agreement validity shall be maintained using start and end dates and the agreement can be deactivated or released for use.
To monitor expiry dates, a standard task list shall be used to display agreements that are valid or expiring within certain time
frames. When the validity of an agreement is updated, the validity of all or selected items in the agreement shall also
simultaneously be updated.
Extension of an agreement with or without new version shall be possible. Different versions of agreements can be generated, with
the same validity period or with mutually exclusive validity periods to ensure that a new agreement does not have to be created
each time an agreements validity period expires or the details of an agreement change depending on the time period.
Note
There shall only be one released agreement version with the same validity period or an overlapping validity period. But
there can be multiple released agreement versions with mutually exclusive validity periods.
It shall also be possible to revert to an earlier agreement version by deactivating the released version and releasing the earlier
version. Agreement versions can also be deleted. The version tab shall contain a list of the agreement versions, including the
status of each version.
A standard approval workflow shall be used for the release of agreements. It shall be possible to specify that an approver is
notified for the release of an agreement and whether it is allowed to edit agreements during the approval workflow.
Requirements

Business Blueprint
contracts.
It shall be possible to maintain off-
hire quotas at two levels:
process
allowed quota on spot basis as per
negotiation with lessor / lessee.

the lease call-off.
Container then on hire after the
period, the flag Eligible for off hire
should be activated on the
equipment.
drop-off location and the size-type
PRM- Manage depreciation [Equipment] For lease, the Implementation 419

CTR- calculation formula depreciation Formula includes :
061 - Depreciation % per year, per
month or per day
Month or Year)
purchase option, the formula can
be the buyout + remaining per
diem till the end date of the
agreement

Business Blueprint

schedule)


CTR- for leased equipment two main on hire costs are
076 managed :
size/type and point
size/type, point

CTR- for leased equipment two main ""Off Hire"" costs are
078 managed during the On-Hire :
Size/type and Point
PRM- Record Off-Hire [Equipment] In Lease contract, an Implementation 419

CTR- Quota for Leased "Off Hire" quota per Size/type and
079 Equipment point can also be managed. The
quota quantity can be managed
per month, per quarter or per
Agreement.
8.6.4.2 Manage Sub-lease-To Contract Execution
Execution of sub-lease-to contracts refers to the process of issuing call-offs based on equipment availability and demand (from
partners) in different locations.

Business Blueprint
Figure 393939 : Manage Sub-Lease-To Contract Execution
Demand for additional equipment is received at the head office (area managers) from sub-lease partners. The stock situation is
then analyzed (per location, per pool) in combination with supply and demand forecasts. If the stock situation does not permit
sub-leasing equipment to partners, the request may be refused. When there is equipment available to sub-lease, an agreement
shall be reached with the partner regarding volumes and location.

Business Blueprint
In case of a sub-lease swap arrangement where same quantities of equipment are exchanged between two parties in different
locations, a parallel sub-lease-from call-off shall also be created with the same information.
In response to the partner's request for equipment sub-lease, a formal confirmation shall be created and issued to the partner. This
confirmation is at a location level that is it confirms the sub-lease of a certain quantity of equipment from a particular city. A copy
shall also be sent to the local release manager so that he or she can plan for the release of equipment.
Sub-leased equipment has to be released to partners at a particular release date and from a certain depot. This information shall
be captured in a release order, which is created and issued by the local release manager. Details of the process of release order
preparation are described in 5.1.3.1.2. Manage Release Order in [BBP_EQP_LM]. The information contained in the release order
enables the sub-lease partner to pick up the sub-leased equipment.
In case of an equipment misuse by third-party, the equipment shall be considered sub-leased-to this party, and a sub-lease-to
confirmation shall be issued in case a contract with the partner already exists (release information is not required in this case). If a
contract does not exist, it shall be created before a sub-lease-to confirmation for misuse can be issued.
When the sub-leased equipment is gated out of CMA CGM depot, the equipment master data is updated to reflect the status of
equipment as sub-leased-to a partner. The gate out is also the trigger to begin per diem charging for the sub-lease. In the case of
misuse, this change in equipment status is also required, but it is managed manually.
Solution:
The request for equipment availability is received from sub-lease partners via e-mail (outside of SAP system).
The functionality to analyze the stock situation is required. It is assumed that the tool for resource planning shall cover this
requirement, either by default or by customer-specific enhancement. The user accesses a system or user interface to obtain this
information. Based on the stock condition, a decision shall be made whether or not to sub-lease equipment to partners.
A sub-lease-to confirmation shall be modeled in SAP TM as a forwarding order (FWO) issued against a forwarding agreement
(FWA) representing a sub-lease-to contract. This forwarding order shall be one with restricted processing (configured on
forwarding order type level in Customizing) meaning it shall not be transportation planning relevant.
Items in the forwarding order shall be equipment, initially identified by equipment type in the forwarding agreement. For each
item, a transportation unit (TU) shall be created (required for independent charge settlement per container).
Note
At this point in time, container numbers are not assigned to the forwarding order items (and TUs). This shall be done later
during gate out from depot. In case of sub-lease-to for misuse, container numbers are already known and shall be
entered in the forwarding order.
This (sub-lease-to) forwarding order shall be enhanced to cover requirements for additional fields to record important contract
related information like the build-up period, and reference number (GAP 2733).

Business Blueprint
A misuse flag is needed in the (sub-lease-to) forwarding order to be able to identify when a container is sub-leased-to a partner
under misused. This shall be an enhancement (GAP2733).
For cabotage, the sub-lease start and end date shall already be fixed in the forwarding order. The pricing logic for this forwarding
order shall also be different in that the forwarding order can be free of charge up to an agreed return date after which a charge
may be applicable. This logic shall be maintained in a charge calculation sheets using an appropriate rate table.
Once all relevant details of the forwarding order are maintained, it shall be confirmed and the confirmation shall be sent to the
sub-lease partner using standard output management functionalities of the forwarding order object.
After the forwarding order has been issued to the sub-lease partner to confirm the location and quantity of containers to be sub-
leased, the containers have to be released from the depot. Release order shall be modeled in SAP TM as a service freight order.
The (depot release) service freight order shall be created manually and sent to the sub-lease partner using standard output
management functionalities. The forwarding order object retains the link to the (depot release) service freight order object (via
the transportation unit, TU).
Note
Further details about the (depot release) freight order are described in [BBP_EQP_LM].
In the case of a sub-lease-to resulting from a misuse of a CMA CGM container by a third party, the forwarding order (sub-lease-to
confirmation) shall be created. When the information of misuse by a third party is received, standard search functionality and
filters shall be used to ascertain if there is already master data for the business partner and/or a forwarding agreement (for sub-
lease-to) in place.
If the partner or agreement does not exist, it shall be created before (sub-lease-to confirmation) forwarding order can be created
and sent. If a forwarding agreement already exits, a forwarding order shall be created directly. This forwarding order shall be
customized to block creation of a (depot release) service freight order (as in the case of misuse, there is no container release
needed). This shall be an enhancement (GAP 2733).
For misused containers, therefore, when the (sub-lease-to confirmation) forwarding order is issued (status of forwarding order set
to confirmed), the status of the container (SAP TM Resource) shall manually be updated to sub-lease-to OUT, which shall trigger a
block on the resource (container) with a reason code for blocking (for example Sub-lease-to Misuse). Blocking makes the resource
unavailable for operational use.
For standard (planned) scenario of sub-lease-to, following the issuance of the (sub-lease-to confirmation) forwarding order and
the subsequent (depot release) service freight order to the sub-lease partner, the container shall gate out of the depot when it is
picked by the partner.
At this point in time, each transportation unit (TU) shall be assigned a resource (container) number. The resource shall be updated
with the predefined status for container sub-leased-to partner and blocked with reason code defined for sub-lease-to (for example
sub-lease-to OUT). The block on the resource shall be triggered as a follow up action of the status change.

Business Blueprint
An enhancement shall be needed to enable setting of sub-lease OUT status each time a resource (transportation unit) is gated
out under the reference of a (depot release) service freight order that is implicitly linked to a (sub-lease-to) forwarding order via
the transportation unit (TU), and subsequently blocking the resource with a predefined reason code (GAP 2734).
Example
SUB-LEASE-TO (MISUSE) BLOCK RESOURCE

- Set resource status to 'sub-lease-to OUT' - Setting of the 'sub-lease-to OUT' status on
manually the resource shall trigger a block on the
- Set resource status to 'sub-lease-to OUT' resource with appropriate reason code, e.g.:
SUB-LEASE-TO - Sub-lease-to
- Set resource status to 'sub-lease-to OUT' - Sub-lease-to (misuse)
automatically with gate out (GAP 2734)
It may be the case that the complete quantity of containers specified in the forwarding order (sub-lease-to confirmation) is not
picked up by the partner. This means that not all transportation units in the forwarding order have been assigned a resource
number at gate out. This information shall be transferred back to the forwarding order. It shall therefore be recognizable in the
forwarding order, which items do not have a resource number assigned to their TU. This shall be an enhancement (GAP 2733).
Based on this information, the (sub-lease-to) forwarding order shall resent to the partner with the updated quantity.
Note
Related to the requirement of sub-lease to (full) which was not considered before the BBP phase requirement freeze, it shall be
elaborated during the solution design phase to what extent the misuse process can be leveraged to cover the requirements of
sub-lease-full.
Requirements
EQP- Open / Called-off It shall be possible to have visibility - Report on the Implementation (under
SLEA- Quantity in Sub- on the open and called-off quantity volumes of containers BI
006 Lease Call-off in sub-lease-to and sub-lease-from that are still available scope)
call-off. to be picked up (open

Business Blueprint

(this requirement is under BI scope) quantity) per sub-
partner and location,
at a point in time
- Report on the
that are picked-up
(called-off) per sub-
at a point in time
- Report on the
that are still to be
released (open
quantity) per sub-
lease-to contract,
at a point in time
- Report on the
that are released
(called-off quantity)
per sub-lease-to
contract, partner and
location, at a point in
time.
PRM- Link the [Equipment] A purchasing reference Implementation 42

CTR- leased/owned document (call-off) will be linked to
090 equipment to a the leased/owned equipment.
purchasing reference
document
PRM- Calculate and store [Equipment] When creating a call- Implementation 480
PO- the end date of build- off, the system shall control that the
059 up in the call-off pick-up is performed during the
build-up period.
EQP- Misuse Flag It shall be possible to identify if a - Ability to identify if a Implementation 2718,
LEAS- (lease, sub-lease-from, sub-lease- lease, sub-lease-from 2733
007 to) call-off was created for the case call-off was created
of container misuse. because a third-party
container was misused
by CMA CGM
sub-lease-to
confirmation was
created because a
CMA CGM container

Business Blueprint

was misused by a third
party
EQP- Status update at It shall be possible to identify the Ability to identify Implementation 2734,
SLEA- release and redelivery release and redelivery of a container release of sub-lease-to 2735
017 of sub-lease-to under sub-lease-to arrangement, container from depot
containers and to trigger the predetermined (gate-out)
status updates - Ability to update the
container status to
reflect start of 'sub-
lease-to' (at depot
gate-out)
redelivery of sub-
lease-to container at
depot (gate-in)
- Ability to update the
container status to
reflect end of 'sub-
lease-to' (at depot
gate-in)
8.6.4.3 Manage Sub-Lease-To Redelivery
This process covers the details of managing equipment redelivery from sub-lease-to partner, including receipt of request from
partner for return of equipment, planning and communicating the return location, and managing the actual exchange of the
equipment with the partner.

Business Blueprint
Figure 404040: Manage Sub-Lease to Delivery
The sub-lease partner sends a request to redeliver equipment. This redelivery request is subject to approval based on redelivery
quotas as agreed in the sub-lease-to contract. If redelivery quota is not available, it shall be ascertained if the equipment may be
needed locally. If yes, redelivery may be possible despite non-availability of quotas. In case of no local need for containers, the
redelivery request may be refused.

Business Blueprint
If equipment redelivery is possible, a redelivery depot shall be selected. The details of this process are captured in 5.1.3.2.2.
Manage Return Depot determination in [BBP_EQP_LM]. The depot shall be informed about the expected equipment redelivery
through the issuance of a depot acceptance order, covered in detail by process 5.1.3.2.4. Manage Depot Acceptance Order
[BBP_EQP_LM].
The sub-lease partner shall also be informed about the redelivery depot by issuing a redelivery confirmation (in response to the
redelivery request).
When the equipment is redelivered at the assigned depot, there shall be a gate in event, which shall trigger a change in equipment
status to redelivered empty by the lessee. In parallel, the returns process shall also be initiated which covers activities like standard
equipment inspection and management of exchange documentation, and so on. Details of this process are covered under
5.1.3.2.6. Manage Container Return in [BBP_EQP_LM].
Gate in of equipment in a CMA CGM depot shall be the trigger to stop invoicing for equipment sub-leased to partners.
Solution:
Request from sub-lease partner for redelivery of containers shall be received via e-mail and managed outside the system.
Redelivery of sub-lease-to containers is subject to quota management. Off-hire quotas are specific to each sub-lease contract and
are defined in the forwarding agreement (GAP 419). These quotas shall be managed per location and adjusted with each
redelivered container. This management of consumed vs. available quota shall be an enhancement (GAP2701).
Before a redelivery request is accepted, this quota management functionality shall be accessed to ascertain if a redelivery quota
for sub-lease partner is available.
In case the quota is not available, the local stock situation shall be analyzed to check if the containers can be used locally. It is
assumed that the tool for resource planning shall cover this requirement, either by default or by customer-specific enhancement.
In case of no local demand, the sub-lease redelivery request may be refused (via e-mail outside of SAP).
In case redelivery is possible, a redelivery confirmation has to be issued to the sub-lease partner. This confirmation shall contain
details of the redelivery depot and the reference number needed to redeliver containers.
The data needed for this redelivery confirmation for the sub-lease partner is the same as maintained in the (depot acceptance)
service freight order which shall be implicitly linked to the (sub-lease-to) forwarding order via the transportation units (TUs). This
service freight order shall be created manually to inform the depot about the expected redelivery of containers. Details for this
service freight order are covered in [BBP_EQP_LM].
The data from the (depot acceptance) service freight order shall be combined with the forwarding order into a new output
template and sent to the sub-lease partner using functionality available under output management (GAP 2736).
Once the containers are redelivered at the depot, there shall be a gate in event. The status of the resources shall be updated to
reflect end of sub-lease. The assignment of this status shall be managed with an enhancement (enhancement (GAP 2735) based

Business Blueprint
on the logic that if a resource gates in with an existing status of 'sub-lease-to OUT'in with reference of a (depot acceptance) service
freight order number linked to a ( sub-lease-to ) forwarding order via the transportation unit, the status 'sub-lease-to redelivered'
shall be assigned. The assignment of this status shall trigger as a follow up action, the removal of block on the resource (GAP
2735). .
Depending on the condition of the redelivered container, the next status assigned shall either be to indicate that the container is
available in depot for use, or to mark it as damaged and start the MnR process.
In the case of cabotage, the return date and location shall already fixed be in the forwarding order (sub-lease-to confirmation), and
so no additional request shall be received for redelivery in this case. Ability to track planned vs. actual redelivery of sub-lease-to
and cabotage containers is covered by a report (GAP 1200).
Note
Summary of objects:
Sub-lease-to Contract Forwarding Agreement (FA)
Sub-lease-to Confirmation Forwarding Order Confirmation (FWO)
Sub-lease-to Invoice Forwarding Settlement Invoice in FICA
Requirements
EQP- Planned vs. Actual It shall be possible to provide - Report to track actual Implementation 1200
SLEA- Redelivery Date for visibility on the planned sub-lease- return date of sub-lease-
013 Sub-Lease-To to redelivery date based on the to containers in
Container redelivery request received from the comparison to the
partner, and the actual redelivery planned date (as
date of the containers in the depot. determined by the
redelivery request from
partner)
- Report shall be able to
display expected return
date/location for
container
number/agreement in
case of sub-lease-to
Output basic features:

- list the results sorting
ascending by planned
date (from closer date
date)

Business Blueprint

- highlight when planned
date is expired
- filter the output by
location and/or
agreement
EQP- Status update at It shall be possible to identify the Ability to identify Implementation 2734,
SLEA- release and release and redelivery of a container release of sub-lease-to 2735
017 redelivery of sub- under sub-lease-to arrangement, container from depot
lease-to containers and to trigger the predetermined (gate-out)
status updates - Ability to update the
container status to
reflect start of 'sub-
lease-to' (at depot gate-
out)
redelivery of sub-lease-
to container at depot
(gate-in)
container status to
reflect end of 'sub-lease-
to' (at depot gate-in)
EQP- Redelivery (Redelivery of sub-lease-to - Redelivery Implementation 2736

SLEA- Confirmation to Sub- containers by lessee):It: It shall be confirmation (Form) with
018 lease Partner possible to send a redelivery reference to the
(Lessee) confirmation to the lesseethe respective sub-lease-to
lessee, with required depot details confirmation, depot
and reference number needed for details and depot
the redelivery of containers to CMA delivery reference
CGM depot. number.
8.6.4.4 Manage Sub-Lease-To Invoicing and Collection
This process deals with the recurrent generation of invoicing and subsequent collection of payment for the equipment sub-leased-
to partners.

Business Blueprint
Figure 414141: Manage Sub-Lease to Invoicing and Collection
The invoice for the sub-lease partner is created monthly (in print, accompanied by a flat excel file containing all details at
equipment level). This invoice accumulates events related to equipment that is sub-leased to partners, and pulls the charges for
these events from the respective sub-lease contracts to determine the total charge. The accompanying flat file includes details of
these events, for example, handling charges at the time of on-hire, and so on.
Note
Issuance of invoice is followed by the standard collections process detailed in [BBP_FIN_INV].
Solution:
As mentioned above, the sub-lease-to contract between CMA CGM and the sub-lease partner shall be maintained as a SAP TM
forwarding agreement (FWA). This agreement shall be integrated with a calculation sheet and rate table to enable the system to
calculate charges. During charge calculation, the system uses the agreement and the calculation sheet, in order to determine a
rate.

Business Blueprint
Forwarding settlement shall be used to trigger the creation of invoices from SAP TM in FI-CA. FI-CA shall create the accounting-
relevant invoices to be sent to the customer.
Forwarding Settlement shall be enhanced to be able to calculate a charge based on the days between gate-out (sub-lease start)
and gate-in (sub-lease redelivered) as reported via Event Management in relation to the service freight orders for depot release
and depot acceptance linked to the (sub-lease-to) forwarding order. In addition, a monthly settlement shall be triggered
automatically using this logic (GAP 2737).
Any additional charges that may be known after the sub-lease container has been redelivered (for example charges related to
damages) shall be added manually or by using event-based charge calculation (integration with SAP Event Management).
With an event profile, different events may be configured for charge calculation. Rules can be defined based on which the system
performs the charge calculation in the forwarding order, for example, and event code, event status, business document in which
the event needs to be charged (forwarding order), and so on.
Service types may also be linked to events, which enable billing based on services. If a specific service type is assigned to an event
code, the system shall charge the customer for the service when the assigned event code occurs in the forwarding order. These
event profiles shall be maintained specific to the sub-lease partner by assigning different event profiles to the forwarding order
type.
Once the forwarding settlement is performed, the invoice shall be created in FI-CA and sent to the sub-lease partner. The form for
this sub-lease-to invoice is covered under Sundry invoices (GAP 2035). Details of the invoice items shall be attached to the invoice
in the form of an excel (GAP 2042).
Credit memos (if needed) shall be issued in reference to a forwarding settlement document, and sent to FI-CA similarly. Details of
credit memo management are covered under [BBP_FIN_AR_AP_BA] and [BBP_FIN_INV].
Example
Following is a sample sub-lease-to invoice.

Business Blueprint
Figure 424242 : (Sample) Invoice for Sub-lease-to Equipment

Business Blueprint
This process covers solution for sub-lease-to monthly invoicing which is part of integration points 1370, 740 and 490 as listed in
section 7.5 of this document. Further details related to procurement processes can be found in [BBP_FIN_AR_AP_BA] and
[BBP_INV]. Formatted: Font: 9 pt
Requirements
EQP- Sub-Lease-To It shall be possible to generate - Automatic Implementation 2035 (form),

SLEA- Invoice Templates and send an invoice for sub-lease generation of 2042 (excel
003 to other parties using a standard invoices for sub- attachment)
template. lease-to containers as
per a standard
template
- Possibility to send
the details of invoices
(list of container with
per diem, [start] &
[stop] date & place,
and so on) in excel
format
EQP- Sub-Lease-To It shall be possible to - Automatic Implementation 27373

SLEA- Invoicing automatically generate an calculation of charges
014 invoice for container sub-leased for sub-lease-to (at a
to other parties based on the container level) as per
terms maintained in the 'sub- the pricing conditions
lease to contract. maintained in the
respective sub-lease-
to contracts
EQP- Sub-Leased to It shall be possible to issue credit - Ability to issue SAP Standard
SLEA- Invoicing (Credit notes to partners against credit notes against
015 Memo previously issued invoices. previously issued
Management) invoices to sub-lease-
to partners.
8.7 Process Lost and Found Equipment Management (5.1.1.7.)
This process deals with:

Handling cases of lost equipment

Business Blueprint
Handling cases of damaged equipment

Handling cases of total loss equipment, including declaration of total loss for leased equipment
Handling found equipment

Business Blueprint
Figure 434343 : Lost and Found Equipment Management

Component Object
5.1.1.7.1. Manage lost equipment This process refers to the handling of lost N/A N/A
equipment including details of scenarios where
equipment may be considered lost.
5.1.1.7.2. Manage damaged This process covers the handling of containers that SAP TM Resource,
equipment are damaged. Damage may be: Master Data, Event
- The wear and tear of containers in the normal SAP EM - Event
course of business Handler
- Damage possibly caused by a third party while

the container is under its control
5.1.1.7.3. Manage declaration of This process deals with the management of total SAP MM, SAP Purchase
total loss loss declaration for equipment that may be lost, FI-AA, SAP FI- Order,
severely damaged / wrecked, or idle beyond a AP, SAP EM - Goods
certain time frame. Event Handler, Receipt,
SAP - TM, Invoice,
Master Data Event,
Asset,
Resource
5.1.1.7.4. Manage found This process covers the definition and handling of SAP TM Resource,
equipment found equipment. Master Data, Event,
SAP EM - Event Freight
Handler, SAP Order, Asset
TM Order
Management,
SAP FI-AA

Business Blueprint
8.7.4.1 Manage Lost Equipment
This process refers to the handling of lost equipment. Equipment is considered lost in the following cases:
It has been stolen.
It is not traceable.
It has fallen into the sea.
Figure 444444 : Manage Lost Equipment

Business Blueprint
There are two scenarios where equipment may be considered lost:
Equipment is lost onboard (falls into the sea):

Information about loss of container onboard is received at the head office either from the SSE department in the head office,
the respective line or from the legal department. Details of the incident including equipment numbers are available in a
statement of facts. If not already provided, this is requested from the relevant departments.
After the statement of facts is received, a decision is made regarding the filing of the insurance claim.
If the claim is to be filed, all required documents are collected and sent to the insurance partner who in turn provides a
confirmation of loss coverage (as defined in the insurance policy).
Equipment is missing or cannot be traced

Information about missing or untraceable equipment may be received from the third party (shipper or consignee, and so on),
or from the local agency.
When equipment is reported as lost, a recovery file shall be opened. This shall initiate the recovery process which includes the
identification of liable party (if any) and triggers the declaration of total loss to remove the equipment from the fleet.
Note
The recovery process shall be managed in the legacy recovery management application called iRecovery. Details of this
process are part of section 8.9 Recovery Management of this document.
All other steps of this process shall be executed manually, outside the SAP system.
8.7.4.2 Manage Damaged Equipment
This process covers the management of equipment that is damaged. Damage may be defined as the following:
The wear and tear of equipment in the normal course of business
Damage possibly caused by a third party while the equipment is under its control

Business Blueprint
Figure 454545 : Manage Damaged Equipment
At depot gate-in, the equipment undergoes the standard returns management process detailed in 5.1.3.2.6. Manage Container
Return in [BBP_EQP_LM]. Part of this process is the inspection of the equipment to ascertain the condition and identify any
damages. The equipment interchange report (EIR) shall be issued at the transfer of control from one party to another.
Based on this inspection, the equipment is found to be either damaged or not. If no damage is found, the status of the SAP TM
resource shall be updated to reflect that it is empty and available in depot for use. In case damage is identified, the status shall be
updated to reflect this and to block the resource in depot against operational use, with a predefined reason code. The status used
shall be one from the empty damaged group.
This information shall be transferred via an interface to the legacy maintenance and repairs system, iMars, where the MnR process
shall be initiated (GAP 54).
A damage flag shall also be activated automatically (in the equipment passport master data) at this time. In case of a false
damage, removal of the damage flag shall be (manually) triggered later from iMars together with the correction of the container
status.

Business Blueprint
Requirements
EQP- Percentage of It shall be possible to maintain for - Report of number of Implementation 2425
DMGE- Damaged Units each depot, the ratio of damaged damaged contained
001 Gated-In at Depot units gated-in per timeframe. For gated in at a depot per
example: out of 100 units gated in time frame.
in the past week, 20 are damaged.
scope)
EQP- Percentage of It shall be possible to maintain for - Report of number of Implementation 2425
DMGE- Damaged Units in each depot the percentage of damaged units per
002 Depot Stock damaged units among the total total stock per depot
stock per pool per point. per point.
scope)
EQP- Integration with It shall be possible to establish an - Containers gated in Implementation 54,1138,
M&R- iMars for Exchange interface with the legacy Empty Damaged 1851,
001 of Container Status Maintenance & Repair system (MED,MEI, MIR in the 2003
Information (iMars) to enable exchange of as-is) are transferred
container status information. to iMars and assigned
status Awaiting
Estimate in iMars
(Information inflow to
iMars)
- Confirmation about
repair completion to
trigger change of
container status to
reflect completion of
repair. This repair
completed status can
be triggered in both
directions -
(information outflow
from/inflow to iMars)
- The approval of the
estimate in iMars to
update the status of
the container in SAP to
reflect approval of the
estimate (information
outflow from iMars)
damage status

Business Blueprint

(information inflow
from iMars to SAP):
There are rules in
iMars to manage the
case when the
estimation is not
received within X
number of days for a
damaged container
(awaiting estimation in
iMars), the damaged
status is corrected. At
this point iMars
triggers the correction
of false damaged
status.
EQP- Damage Flag It shall be possible to maintain a - Activate 'damage' Implementation 42

MD- flag in the container passport (to flag in passport when
030 identify it as a damaged container the container gates in
(until the repair is completed). at depot and is
assigned any status
from the 'empty
damaged' group of
statuses
- Deactivate the
'damage' flag in the
passport when the
repair is completed

Business Blueprint
8.7.4.3 Manage Declaration of Total Loss
This process deals with the management of total loss declaration for equipment that may be lost, severely damaged, or idle
beyond a certain time frame.

Business Blueprint

Business Blueprint
Figure 464646 : Manage Declaration of Total Loss
For owned equipment, as it is ascertained that equipment confirms as total loss based on the three scenarios mentioned above, it
shall be marked with a total loss status for owned equipment. This total loss status differentiates between the case of total loss for
lost containers or for constructive total loss for wrecked or damaged containers.
The setting of this status shall be triggered by one of the following:

The recovery manager as part of the recovery process for lost or wrecked equipment
The idle equipment manager in case of idle equipment beyond a certain number of days
The MnR manager in some cases of damaged equipment
For owned equipment, the setting of a total loss status shall trigger the total loss declaration process. This is essentially the
deactivation of resource master data and retirement of corresponding asset.

Business Blueprint
Asset retirement refers to the removal of an asset from the asset portfolio, which in this case occurs due to the disposal of the
asset. The system shall automatically determine the amounts to be charged off for depreciation based on the date of retirement.
Further details about asset retirement are covered in [BBP_FIN_Asset].
For leased equipment, the total loss units shall be declared to the lessor and a total loss charge shall be paid as predetermined in
the leasing contract. The declaration of total loss is managed with a purchase order which for a (leased) idle container shall be
created manually by the head office idle manager, and that for a (leased) lost or (leased) damaged container is created by the
recovery or MnR managers.
A dedicated purchase order type shall be created for total loss purchase order. This shall drive the automatic price determination
according to information maintained in the lease contract (GAP 1496). The price schema linked to this purchase order type shall
allow the manual update of the predetermined price.
The total loss purchase order shall be subject to approval via workflow (GAP 1931). Approval of the total loss purchase order shall
trigger the update of container status to total loss declared for leased equipment (GAP 2613). After approval the total loss
purchase order shall be sent to the lessor.
One- step goods receipt is performed for the total loss purchase order.
Depending on the terms of the lease agreement, for some lessors, the date of creation of this total loss declaration purchase order
shall serve as the trigger to stop per diem charge. For others, it may be the date of release of total loss payment. This shall be
managed by an enhancement for an indicator in the supplier master data (GAP 1497).
The lessor issues an invoice against the total loss declaration. This shall be recorded and verified against the total loss purchase
order.
Invoice entry shall change resource status to total loss paid. This status update shall trigger the deactivation of the resource Formatted: Font: BentonSans Book
master data by changing the validity end date of the resource to the date of invoice entry (GAP 2584).
Upon receipt, the paper invoice shall be scanned and electronically stored in the system. It shall then be recorded in the system
with reference to the respective total loss purchase order.
When the purchase order number is keyed in for an invoice, relevant data shall be automatically retrieved from the purchase order,
code, tax code, account assignment, G/L account, and so on) coming from each purchase order line item.
The system shall propose value and quantity coming from purchase order items as a default value into invoice items. However,
this can be overwritten with inputs coming from the vendor invoice. A comparison shall then be made between total invoice line
items and header amounts of the invoice. Based on this comparison the invoice balance shall be calculated. The quantities and
values that are entered in SAP invoice line items shall also be compared against the purchase order line items sent to the vendor.

Business Blueprint
The invoice verification process shall check the accuracy of invoices received from vendors with respect to contents, prices, and
arithmetic, matching invoices with purchase orders goods receipts. It shall use the data scanned and/or entered previously in the
Purchasing and Goods Receipt application areas and pass on documents created when an invoice is posted to Financial
Accounting, Asset Accounting and Cost Accounting.
Invoice verification for invoice against purchase orders shall be subject to the following workflow approvals:
Approval to remove the blocking code from the Accounts Payable invoice and release it for payment.
Approval for OK to pay based on the invoice amount (subject to the authority matrix)

5. Releasing the document that meets the required criteria, for example amount limits
This process covers solution for declaration of total loss which is listed under integration point 1360 in section 7.4 of this document.
Further details related to procurement processes can be found in [BBP_PRM] [Error! Reference source not found.] aand those
related to invoice recording and payment processes can be found in [BBP_FIN_AR_AP_BA].
Requirements
EQP- List of Containers Declared It shall be possible to - Report of containers Implementation 1643 (Under
LEAS-001 in Total Loss have visibility on the declared in total loss BI Scope)
containers declared with filter for multiple
in total loss per time criteria including per
period and per lease time period, size-type,
contract. leasing partner,
(this requirement is contract number, and
under BI scope) so on.
EQP- Declaration of Total Loss A formal declaration - Form for declaration Implementation 459
LEAS- Output of a leased container of total loss (purchase
002 in total loss is made order)
to the lessor (through - Output of the
the creation of a declaration of total loss
purchase order) when (purchase order) to the
the container is lost lessor via email / in

Business Blueprint

or damaged beyond print
repair or when it is
idle above a certain
number of days. It
shall be possible to
output the
declaration of total
loss (purchase order)
to the lessor in print /
via email.
EQP- Invoice Verification for It shall be possible to - Invoice verification SAP Standard
LEAS-003 Declaration of Total Loss verify the invoice against total loss
received from the purchase order
lessor for total loss - Automatic payment
container against the of verified total loss
total loss declaration invoices
purchase order.
EQP- Update of Total Loss Status It shall be possible to - Ability to update the Implementation 2584
LEAS- for Leased Containers manage container container status to 2613
005 status during the 'Total Loss Declared'
total loss declaration with the date of
process with the declaration and the
relevant status last known location (at
updates triggered at approval of total loss
different points in the purchase order for
process. leased container, at
time of declaration in
iRecovery system for
owned container -
tracking move in as-is:
TLN/TLY for lost or idle
containers, and
CLY/CLN for
constructive total loss)
container status to
'Total Loss Invoice
Received/ Paid' at the
time of lessor total loss
invoice entry in finance
(tracking move in as-is:
MWI)
EQP- Integration with iRecovery It shall be possible to - Flag (check-box) for Implementation 1823
RECO- for Declaration of Total Loss manage an interface Total Loss declaration
004 with the legacy in iRecovery to trigger
recovery creation of total loss
management system declaration purchase

Business Blueprint

to be able to create a order for leased
purchase order for containers in SAP
total loss declaration. (information outflow
from iRecovery).
PRM- Calculate depreciation value [Equipment] The Implementation 1496

CTR-050 for total loss and purchase depreciation rules are
option defined globally for
the contract while
the renewal value is
defined per size/type.
Both are used in case
of equipment total
loss or purchase
option. The system
shall calculate the
depreciation value
from the reference
contract and create a
purchase order for
total loss or purchase
option.
PRM-PO- Declaration date for total [Equipment] The Implementation 2716

055 loss declaration date of
the total loss shall
stop the per diem
charging for the
respective container
by removing it from
the lease contract as
of this date.
This date can differ
from the date of total
loss purchase order
creation.
PRM-PO- Update off-hire date on [Equipment] Implementation 1498

090 Resource in case of Total Depending on lessor
Loss policy (as maintained
in lessor data), the
off-hire date on the
resource master shall
be updated either at
the time of total loss
purchase order
creation or at the
time of release of
total loss payment.

Business Blueprint
PRM- Indicator at supplier level to [Equipment] In the Implementation 1497

MD-009 stop per diem for total loss supplier master data,
process a special attribute
shall be maintained
to indicate if the
lessor stops per diem
charging as of the
date of declaration of
total loss (PO
creation) or after
release of payment
for total loss.
PRM-PO- Create purchase order for [Equipment} When SAP Standard

052 total loss declaring a total loss
for leased
equipment, a manual
purchase order shall
be created by CMA
CGM.
If the price of the
leasing is lower than
the "total loss price",
CMA CGM can decide
not to create a
purchase order to
declare the total lost
and keep leasing the
equipment.
PRM-PO- Determine purchase order [Equipment] When Implementation 1496

054 price for total loss HO Recovery
Manager, Head
Office Idle Full
Manager or Head
Office Maintenance
and Repair Manager
create the purchase
order for total loss,
the system shall
automatically
calculate the price of
the lost container
based on the
depreciation value
and the depreciation
formula from the
lease agreement.

Business Blueprint
PRM-PO- Change purchase order [Equipment] The Implementation 1496

068 price for total loss price of the purchase
order for total loss
can be manually
updated even though
it has been calculated
automatically.
PRM-PO- Approve purchase order for [Equipment] The SAP Standard

053 total loss purchase order for
total loss will be
issued to the lessor.
The purchase order
for total loss is
relevant for the
approval process.
PRM-PO- Manage approval workflow It shall be possible to Implementation 1931

098 for total loss purchase order manage approval
workflow for total
loss purchase order
PRM-LIV- Check Incoming invoice for [Equipment] Based SAP Standard

024 total loss on the total loss
purchase order, the
lessor sends an
invoice to CMA CGM.
This invoice shall be
checked in the
system.
EQP-MD- Total Loss Status It shall be possible to - Ability to maintain Implementation 42

049 maintain a 'total loss total loss status at the
status' on the container level
container level, and - Ability to update the
to update this status container status based
based on relevant on different triggers in
triggers in the total the total loss
loss declaration declaration process
process.
8.7.4.4 Manage Found Equipment
Found container is:

A container previously declared in total loss and subsequently found or located

Business Blueprint
A container that is found and cannot be traced to a legal owner
Based on whether or not the found container is damaged, and the extent of damage, it shall be eventually repaired or sold.

Business Blueprint
Figure 474747 : Manage Found Equipment

Business Blueprint
When a container gates in at a depot or terminal and is not recognized (as part of CMA CGM fleet), information about the
container is analyzed to ascertain if it can be treated as a found container. If this is the case, the Local Stock Manager shall inform
the HO Logistics Area Manager and Interchange Logistics Manager about the found container.
Legal owner of the found container shall be traced. This may be CMA CGM or a third party. Found container may be legally owned
by CMA CGM if:
Container was owned, and was lost and removed from fleet but the total loss was not paid (or not paid in full) by a liable party,
or
Container was leased, and was wrecked or lost, total loss was paid to the lessor but the total loss was not recovered (or not
recovered in full) by a third party.
If found container is traced to be owned by a third party and it is already onboard a vessel, the container shall be treated as
misused by CMA CGM and its return shall be managed. Details of this process are covered in section 8.5.4.2. Manage sub-lease-
from contract execution of this document.
If found container shall be traced to be owned by a third party and the location of the container shall either be in terminal or in
depot, the legal owner shall be informed accordingly. The legal owner shall then confirm if he or she would like to take the
container back into possession or not. In the former case, container shall be returned to the owner.
If the owner has a contract with the depot, the depot shall be informed to return the container to the stock of its rightful owner. If
the depot does not have a contract with the third party owning this equipment, the equipment shall be released to its owner. The
details of this process are covered under 5.1.3.1.2. Manage Release Order, and 5.1.3.1.5. Manage Release Order Execution in
[BBP_EQP_LM].
In case the owner does not want to take the found container back in possession, a request for a formal 'abandon' letter shall be
sent. This shall allow CMA CGM to add this container the fleet as an owned container, referred to as on-hiring.
A found container shall also be on-hired if CMA CGM is the legal owner, or if the legal owner could not be found.
On-hiring of found equipment as owned shall therefore be executed as following based on the three scenarios:
On-hired because third party legal owner does not want container:
o Resource master data and fixed asset shall be created.
o The fixed asset shall be created under a special class with a value if 1$, zero depreciation and scrap value of 1$.
On-hired because no legal owned is found:

o Resource master data and fixed asset shall be created.
o The fixed asset shall be created under a special class with a value if 1$, zero depreciation and scrap value of 1$.
On-hired because CMA CGM is the legal owner:

o Resource master data shall be reactivated.
o Fixed asset shall be reactivated if container was removed from fleet in the same financial year. An enhancement shall be
needed to check the asset related to the found container, and to reverse the asset deactivation posting. This
enhancement shall be managed in FI-AA.

Business Blueprint
o The fixed asset shall be created under a special class with a value if 1$, zero depreciation and scrap value of 1$ if container
was taken out of fleet in a different financial year, or if it was previously a leased container (total loss paid to lessor but
not recovered).
Once the found container is added to the fleet it needs to be available for operational use. It shall therefore be verified if the
container is empty or not.
If found container added to the fleet is full, it shall either at the terminal or onboard a vessel. In this case:
o If container is onboard a vessel, it shall resume its commercial cycle.
o If found container added to the fleet is at the terminal, it is either gated-in for export, or is in idle status.
o If container is found when idle on terminal, expedite idle/full process for an uncollected import shall be initiated.
Details of this process are described in 5.1.2.7.2. Uncollected Imports in [BBP_EQP_IM]
o If container is found when gated-in for export at terminal , it shall resume its commercial cycle
If found container added to the fleet is empty, it shall be checked for its condition. If damaged, the MnR process shall be
initiated. If not damaged, it shall be available as empty for use in depot.

Business Blueprint
Figure 484848 : On-hire Owned Equipment

Business Blueprint
Requirements
EQP- Identify Found It shall be possible to provide visibility '- Availability of a report Implementation 1643
LAFE- Containers Added to on found containers that were added to identify and list (Under
001 the Fleet to the fleet as owned assets during a found containers added BI
particular time period. to the fleet during a Scope)
(this requirement is under BI scope) time period- Availability
of a filter to identify and
list found containers
added to the fleet
during a time period
8.8 Process Maintenance & Repairs (MnR) Management (5.1.4.1.)
It is important that the equipment is in a sound condition to guarantee safe transport of cargo. The main objective of the MnR
department is to have equipment available for commercial use in the shortest possible time and to minimize repair idle time and
costs.
The MnR process deals with the identification and handling of damaged equipment to ensure efficient and timely repairs and
further availability of equipment for operational use after repair completion. This section describes the MnR processes managed in
the legacy MnR application, iMars, which are relevant for management of required interfaces.

Business Blueprint
Figure 494949 : Maintenance & Repairs (MnR) Management
PRM- Integration with It shall be possible to create a - Ability to trigger Implementation 1136
PO- iMars for purchase (in SAP) based on repair creation of a
091 Procurement of estimate approved/repair completed predefined purchase
M&R Services status in iMars (MnR legacy system). order type from
iMars in SAP

Business Blueprint

(information
outflow from iMars)
- Ability to transfer
all needed
information
(including value) for
the creation of the
purchase order via
an interface from
iMars to SAP
(information
outflow from iMars)
- Ability to update
the purchase order
in SAP in case of
change to the
purchase order in
iMars (information
outflow from iMars)
- Ability to perform
automatic service
receipt after
purchase order
creation in SAP
- Monthly invoice
creation for all
existing MnR
purchase orders and
service receipts in
SAP
EQP- Integration with It shall be possible to establish an - Container (all fleet, Implementation 54, 45, 46,
M&R- iMars - Master Data interface between SAP and the size-type, passport, 47, 48, 49,
003 legacy Maintenance & Repair system grade, full vs. 56, 1821
(iMars) to enable exchange of empty) (information
master data. inflow to iMars)
- Geographical
Referential -
country, city, state
(information inflow
to iMars)
- Pools (depot)
(information inflow
to iMars)
- Currencies and
Exchange rate
(information inflow
to iMars)
- Information about

Business Blueprint

last BL (information
inflow to iMars)
- Depreciation value
(information inflow
to iMars)
- Partners (repair
companies)
(information inflow
to iMars)
- Contracts
(including
depreciated value,
DDP, buyout value,
etc.) - (information
inflow to iMars)
EQP- Integration with It shall be possible to establish an - Repair completion Implementation 51

M&R- iMars for Container interface between SAP and the forecast date based
005 Availability Forecast legacy Maintenance & Repair system on iMars statistics
(iMars) to enable exchange of data (iMars does not
for forecasted availability of have the capability
container after repair. to provide this yet)
(information
outflow from iMars)
EQP- Integration with It shall be possible to establish an - Information about Implementation 54

M&R- iMars for Exchange interface between SAP and the preparation work on (Outbound
006 of Container Grade legacy Maintenance & Repair system container to trigger ODI Flow),
Information (iMars) to enable exchange of an update of 52
information related to container container grade in (Inbound)
grade. container master
data (reflected in
container passport)
(information inflow /
outflow from iMars)
EQP- Integration with It shall be possible to check if the - Whenever a repair Implementation 1138, 1852
M&R- iMars for Damage damage flag is activated in the estimate related to
007 Flag Check container passport based on specific a damaged
statuses in iMars. container is
approved in iMars
(iMars status:
estimate approved),
the damaged flag in
the passport should
already activated)
(information inflow
from iMars to SAP)
- Whenever a repair

Business Blueprint

estimate related to
a container is
rejected in iMars
(iMars status-
rejected to be sold),
the damaged flag in
the passport should
already activated)
(information inflow
from iMars to SAP)
damage status in
iMars to deactivate
the damaged flag in
the container
passport in SAP
(information inflow
from iMars to SAP)
EQP- Container Upgrade It shall be possible to request - Extract demand for Roll-in for FBS
TINV- Request based on upgrade of containers to food grade food grade
012 Forecasted Demand by the M&R department based on containers per
for Food Grade forecasted demand for food grade location from
Containers containers. booking data
- Visibility on
demand vs. supply
of food grade
containers per
location
EQP- Integration with It shall be possible to establish an - Containers gated Implementation 54, 1138,
M&R- iMars for Exchange interface with the legacy in Empty Damaged 1851, 2003
001 of Container Status Maintenance & Repair system (MED,MEI, MIR in
Information (iMars) to enable exchange of the as-is) are
container status information. transferred to iMars
and assigned status
Awaiting Estimate
in iMars
(Information inflow
to iMars)
- Confirmation
about repair
completion to
trigger change of
container status to
reflect completion
of repair. This repair
completed status

Business Blueprint

can be triggered in
both directions -
(information
outflow from/inflow
to iMars)
- The approval of
the estimate in
iMars to update the
status of the
container in SAP to
reflect approval of
the estimate
(information
outflow from iMars)
damage status
(information inflow
from iMars to SAP):
There are rules in
iMars to manage the
case when the
estimation is not
received within X
number of days for a
damaged container
(awaiting estimation
in iMars), the
damaged status is
corrected. At this
point iMars triggers
the correction of
false damaged
status.
EQP- Assignment of Non- Maintenance and repair may include - Ability to allocate Out-of-Scope
M&R- Logistics M&R activities like preparation of charge code to
004 Costs to Line / container for a specific use. These relevant
Customer costs may not be logistics related, department
but related to a booking / specific (Logistics Cost
customer requests (Value Added center or booking
Service- VAS). It shall be possible to cost item) as
maintain these costs within specific defined for each
cost categories and invoice them VAS identified in
directly to the line or customer (VAS Q2C stream
booked to the line).

Business Blueprint

Component Object
5.1.4.1.1. Prepare MnR contracts MnR contracts are maintained in the legacy Out of Scope N/A
Maintenance and Repairs system, iMars. Details of
the process are not in scope of this document.
5.1.4.1.2. Manage MnR contract This process describes details of the purchase of SAP MM, SAP Purchase
execution MnR services from supplier, and all details relevant FI-AP Order,
for the management of interfaces in this regard. Goods
Receipt,
Invoice
5.1.4.1.3. Manage MnR invoicing This process covers details related to payment for Out of Scope N/A
and payment MnR services, and all details relevant for the
management of interfaces in this regard.
8.8.4.1 Prepare MnR Contracts
Contracts for MnR services may be maintained as part of depot contracts or independently in the legacy Maintenance and Repairs
system, iMars. Details of the process are not in scope of this document.
8.8.4.2 Manage MnR Contract Execution
This process describes details of MnR contract execution and the purchase of MnR services from suppliers. Solution mapping is
limited to the management of required interfaces.

Business Blueprint

Business Blueprint
Figure 505050 : Manage MnR Contract Execution
Procurement of MnR services is managed in a legacy application called iMars where a repair estimate is created each time a
damage to equipment is identified. This repair estimate is subject to approval based on approval rules built in the application.
An interface shall be managed between iMars and SAP to allow for exchange of information for procurement of MnR services, and
subsequent invoice recording and payment through SAP.
MnR services' procurement process shall be initiated when a repair estimate for a damaged container is approved in iMars. This
information shall be transferred via an interface to SAP (GAP 1136) and a purchase order shall be created in the destination
system.
To be able to manage the purchase of MnR services in SAP, material master and supplier master data shall be maintained.

Business Blueprint
A (dedicated) purchase order type for purchase of MnR services shall allow reporting segregation and authorization management.
Updates to the purchase order triggered from iMars shall also be possible via the interface (GAP 1136).
Following the creation of the purchase order in SAP, a goods receipt shall be automatically recorded and an accounting document
shall be created with the posting of goods receipt.
This process covers the solution for integration point 1470 as listed in section 7.5 of this document. Further details related to
procurement processes can be found in [BBP_PRM].
Requirements
PRM- iMars system [Equipment] The system shall receive Implementation 1890
GSR- integration for Goods inbound goods receipt from iMars in
026 Receipt order to enable the invoice
verification.
EQP- MnR File Reference It shall be possible to maintain the - Ability to store MnR Implementation 42
MD- reference of the MnR file at the file reference on the
041 container level. container master for an
open MnR file against
the container number
MnR file number on the
container master until it
is replaced by another
(new) MnR file opened
for that container
8.8.4.3 Manage MnR invoicing and Payment
This process describes details of payment for MnR services to supplier. Solution mapping is limited to management of required
interfaces.

Business Blueprint
Figure 515151 : Manage MnR Invoicing and Payment
The MnR suppliers issue periodic invoices for all purchases made during the month. Upon receipt, the paper invoice shall be
scanned and electronically stored in the system.
In case of an invoice with purchase order reference, all the items in a purchase order can be settled together, regardless of whether
an item has been received in several partial deliveries.
The invoice shall be recorded in the system with reference to the purchase orders created during the relevant time period.
When the purchase order number is keyed in for an invoice, relevant data shall automatically be retrieved from the purchase order,
code, tax code, account assignment, G/L account, etc.) coming from each purchase order line item.

Business Blueprint
entered in the invoice screen. All item data coming from purchase orders shall be automatically proposed by the system and be
arithmetic, matching invoices with purchase orders goods receipts. It shall use the data scanned and entered previously in the
Purchasing and Goods Receipt application areas and passes on documents created when an invoice is posted to Financial
Approval to remove the blocking code from the Accounts Payable invoice and release it for payment.
In summary, the process of invoice entry, verification and payment shall include some or all of the following steps:
Upon verification of the invoice, payment to the MnR supplier shall be made.
Further details related to invoice recording and payment processes can be found in [BBP_FIN_AR_AP_BA].

Business Blueprint
Formatted: Font: BentonSans Bold, Font color: Gray-60%

8.9 Process Recovery Management (5.1.4.2.)
Recovery Management deals with the recovery of financial loss incurred due to loss or damage of a container by a third-party. The
process begins with identification of loss or damages that are caused by a third party, identification of the liable third-party, and
subsequently managing the invoicing and collection of the recovery amount. Recovery process is managed in a CMA-CGM legacy
system iRecovery, used by the Logistics Head Office, Regional Offices and Agencies.
This section describes the Recovery processes managed in the legacy recovery management application, iRecovery, which are
relevant for management of required interfaces.

Business Blueprint
Figure 525252 : Recovery Management

Business Blueprint
EQP- Integration with iRecovery for It shall be possible to - Flag for wreck to be Implementation 50,
RECO- Exchange of Container Status manage an interface with sold in iRecovery to 1853
002 Information the legacy recovery trigger activation of 'To
system to manage Be Sold' container flag
container status. in SAP (information
outflow from iRecovery)
- Flag for 'Declare in

total loss' in iRecovery
(dedicated flag) to
create the event
'declared in total loss for
owned containers (TLN)
or 'declared in
constructive total loss
for owned containers'
(CLN) in SAP with
declaration date and the
location of the last
event known for this
container except when
over board (XXUNK).
- In the case of events
for total loss declaration
for owned containers
(TLN/CLN), out of fleet
move (MWI) is created
at the same time in SAP.
- For leased containers,

iRecovery shall only
send information to SAP
to initiate the total loss
declaration process and
the Total loss /
constructive total loss
declared status
(TLY/CLY) shall be
posted only after the
approval of the total loss
PO (GAP 2613)
EQP- Integration with iRecovery for It shall be possible to - Flag (check-box) for Implementation 1823
RECO- Declaration of Total Loss manage an interface with Total Loss declaration in

Business Blueprint

004 the legacy recovery iRecovery to trigger
management system to creation of total loss
be able to create a declaration purchase
purchase order for total order for leased
loss declaration. containers in SAP
from iRecovery).
EQP- Integration with iRecovery - It shall be possible to '- Container Passport Implementation 56,
RECO- Master Data manage an interface with (information inflow to 607,
003 the legacy recovery iRecovery) 1822,
management system to - Recovery file number 1849,
be able to exchange (information outflow 2104,
master data. from iRecovery into 1821,
container passport) 48
- Depreciation value of
leased containers
(information inflow to
iRecovery)
- Tracking of container
lease cycle history
iRecovery)
- Data from 2 last
bookings/ Bill of Lading
- Name of customers,
cargo details, B/L
number (information
inflow to iRecovery)
- Company codes to
allow intercompany
invoicing to agents
iRecovery)
- Partner code (third-
party partner code is
used for reference on
the recovery file)
- Currency/ exchange
rate (information inflow
to iRecovery)
- City / location
iRecovery)

Business Blueprint

Component Object
5.1.4.2.1. Open recovery file This process identifies the relevant triggers initiating Out of Scope N/A
a recovery process.
5.1.4.2.2. Identify liable party Details regarding the processing of a recovery file Out of Scope N/A
are covered, including identification of and
communication with a liable party and management
of non-recovery (if applicable).
5.1.4.2.3. Manage recovery This process describes the details of issuing invoices SAP FI-CA Invoice
invoicing and collection for recovery, and collection of payment against
these invoices. Details required to manage
interfaces are covered.
8.9.4.1 Open Recovery File
This process identifies the relevant triggers initiating a recovery process.

Business Blueprint
Figure 535353 : Open Recovery File
Requirements
EQP- Recovery File It shall be possible to maintain the - Ability to store Implementation 42
MD- Reference reference of the recovery file at the recovery file reference
040 container level. on the container master
for an open recovery file
against the container
number

Business Blueprint

recovery file number on
the container master
until it is replaced by
another (new) recovery
file opened for that
container
8.9.4.2 Identify Liable Party
This process details the assignment of a recovery file to the respective local recovery manager and subsequent identification of a
liable party for damage or loss of a container. It also highlights interfaces into other processes, such as declaration of total loss and
recovery invoicing and collection.

Business Blueprint
Figure 545454 : Identify Liable Party

Business Blueprint
8.9.4.3 Manage Recovery Invoicing and Collection
This process covers intercompany and third-party recovery invoicing and collection. It also highlights interactions with other
processes such as sale and release of containers.

Business Blueprint

Business Blueprint
Figure 555555 : Manage Recovery Invoicing and Collection
In case of recovery for lost or wrecked container (declared in total loss), the Recovery agent at head office shall create an Formatted: Font: BentonSans Book
intercompany recovery invoice for the agent in FI-CA, transferring all required information for the invoice from iRecovery via an
interface (GAP 458). The collection against this invoice shall be reported to the head office via 'Netting', or a revenue posting
(against recovery from liable third-party) to head office.
The agent shall subsequently create a recovery invoice for the liable third party in FI-CA, transferring all required information for
the invoice from iRecovery via an interface (GAP 2351). This invoice from agent to third party shall be created for all cases of
recovery -i.e. for damaged (repairs to be recovered), wrecked and lost (residual value to be recovered) containers.
Creation and issuance of recovery invoices shall follow the process of sundry invoicing in FI-CA.
In case of total loss for owned containers, in order to calculate and register the correct gain or loss on asset retirement the
recovery invoice shall be linked to the de-activated asset and the equipment /asset information shall maintained on the recovery
invoice.

Business Blueprint
Note
Further details related to Recovery Invoicing have been described in [BBP_FIN_AR_AP_BA].
This process covers solution for integration point 2680 as listed in section 7.5 of this document. Further details related to sundry
invoicing and collection processes can be found in [BBP_FIN_AR_AP_BA].
Requirements
EQP- Integration with iRecovery for Third parties may lose or - Creation and Implementation 2351
RECO- Invoicing and Collection damage containers. Recovery issuance of
001 refers to process of charging intercompany
the liable party for the loss or invoice (head office
damage. It shall be possible to to agency) for cases
create and issue invoices for of total loss
recovery and manage (information outflow
subsequent collection by from iRecovery)
exchange of information - Creation and
between iRecovery and SAP issuance of invoice
via an interface. (agency to liable
third party) for
recovery amount
(case of damaged or
lost containers)
from iRecovery)
- Transfer of the
invoice number from
SAP to iRecovery to
update the recovery
file (information
inflow to iRecovery)
- Update the status
of payment in
recovery file (paid /
not paid) upon
collection of
payment
(information inflow
to iRecovery)

Business Blueprint
8.10 Process Seals and Spare Parts Procurement Management (5.1.4.3.)
This process deals with the procurement of seals and spare parts for reefers (reefer kits).

Component Object
5.1.4.3.1. Manage procurement of This process deals with the procurement of seals SAP MM Master
seals for sale to customers (as a value-added service - Data,
VAS). Contract,
Purchase
Order,
Goods
Receipt,
Invoice
5.1.4.3.2. Manage procurement of This process deals with the procurement of spare SAP MM Master
spare parts (reefer kits) parts for reefer containers (reefer kits). Data,
Contract,
Purchase
Order,
Goods
Receipt,
Invoice

Business Blueprint
Figure 565656 : Seals and Spare Parts Procurement
8.10.4 Process Step Detailed Requirements and Solution
8.10.4.1 Manage Procurement of Seals
This process deals with the procurement of seals for sale to customers (as a value-added service - VAS).

Business Blueprint
Figure 575757 : 5.1.4.3.1. Manage Procurement of Seals
Seals are sold to customers as a value-added service. They are tracked by serial numbers which are reported in the bill of lading
(B/L). Procurement of seals is managed by the Logistics department in order to ensure a consistent supply from dedicated
suppliers.
There are five types of seals (being purchased). The process of seals procurement deals with:
Selection of an appropriate supplier

Business Blueprint
Maintenance of required master data (material, suppliers)

Definition of purchasing contracts
Creation and issuance of purchase order
Payment against supplier invoice
The selection of an appropriate supplier shall be based on an analysis and comparison of supplier proposals and/or on the basis of
selection criteria.
After suitable suppliers have been selected, a contract for the purchase of seals shall be created.
The contract is a longer-term purchase agreement with a vendor for the supply of materials and services according to
predetermined conditions. A contract is valid for a certain period of time and covers a predefined purchase quantity or target
value.
A generic contract type shall be defined for purchase of seals. It is divided in two parts:
The header part shall contain general information such as: supplier, company code, purchasing organization, different
business partners, currency, validity period, payment terms, and header texts. Information from the header is common to all
contract items.
The item part shall include the material master, target quantity, price conditions, account assignment (for non-stocked
material), item text, and so on.
The contract shall allow the definition of a default currency type and communication language with the supplier. A payment
method specific to the supplier shall be defined for each contract based on the supplier master data. The contract type also allows
authorization rules to be set up to manage access to any sensitive data by different users.
The Finance department shall be informed each time a contract is created or updated.
To manage contract extensions or revisions, a new contract shall be created in reference to another one by copying all information
from the reference object.
When requests for purchase of seals are received, a purchase order shall be created and issued to the supplier.
A purchase order is a formal request to a supplier to supply goods or services at the condition stated in the contract or the
purchase order. When the purchase order is created against a contract, the system shall trigger all information from the contract
and copy it to the purchase order.
The purchase order is divided in two parts:

The header part shall contain general information such as supplier, company code, purchasing organization, business
partners, currency, payment terms, header texts, incoterms and so on.
The item part shall include: the material master, price conditions, order quantity, account assignment (for non-stocked
material), price conditions, tax code, item text, and so on.

Business Blueprint
Because no stock shall be managed (in SAP), an account assignment (cost center, asset, internal order, and so on) has to be used
for each purchase order item.
Any updates or changes made at header or item level in the purchase order shall be tracked in the system with a time stamp, user,
and actions performed information.
To differentiate between various versions of the purchase order, the standard versioning functions shall be activated for the
purchase order. When a purchase order version is not completed it cannot be used, and only the last active version shall be
relevant for purchasing process. The system shall keep the history of all previous versions.
This purchase order in SAP shall be subject to approval which shall be managed via workflow (GAP 1931).
The purchase order output can be customized to allow printing, e-mailing or EDI exchange with suppliers. A purchase order form
shall be used for the purchase of seals (GAP 486).
A purchase order usually requires that a goods receipt or a service acknowledgement is recorded. A goods receipt for purchase of
seals shall be managed in one-step. When the goods or service receipt shall be posted against a purchase order, an accounting
document shall be created.
A monthly invoice is received from the seals supplier. Upon receipt, the paper invoice shall be scanned and electronically stored in
the system.
The invoice shall then be recorded in the system with reference to the purchase orders created during the month.
When the purchase order number is keyed in for an invoice, relevant data shall be retrieved from the purchase order, automatically
populating the following information: invoicing party (vendor), payment terms, item data (amount, quantity, service code, tax
code, account assignment, G/L account, and so on) coming from each purchase order line item.

Business Blueprint
Invoice verification against purchase orders shall be subject to the following workflow approvals:
Approval to remove the blocking code from the accounts payable invoice and release it for payment.
Upon verification of the invoice, payment to the supplier is made.
This process covers the solution for integration point 2690 as listed in section 7.5 of this document.
Further details related to procurement processes can be found in [BBP_PRM] and those related to invoice recording and payment
processes can be found in [BBP_FIN_AR_AP_BA].
Requirements
PRM- Manage Procurement [Equipment] It shall be possible to - Maintain purchasing SAP

PO- of Seals manage procurement of seals as a contracts for Standard
094 standard purchasing process supported procurement of seals (5
by purchase order creation and types of seals with fixed
management of subsequent invoice price per year)
verification and payment. - Manual creation of
purchase order for
procurement of seals
- Ability to manage
monthly invoice
verification and payment
against purchase orders
issued during the month
- Planned or unplanned
delivery cost shall be
managed

Business Blueprint
[Equipment] It shall be possible to

PRM-
Manage Seals maintain purchasing contracts for SAP
CTR-
Purchasing Contracts procurement of seals (5 types of seals Standard
092
with fixed price per year)
[Equipment] It shall be possible to

PRM-
Manage Goods Receipt manage goods receipt of seals for SAP
GSR-
of Seals management subsequent invoice Standard
028
verification and payment.
[Equipment] It shall be possible to SAP

PRM- manage invoice verification for seals Standard
Manage Invoice
LIV- purchasing activity. A monthly invoice is
Verification for Seals
032 created with planned and unplanned
delivery costs.
PRM- Manage Suppliers for [Equipment] It shall be possible to SAP

MD- Seals Purchasing manage suppliers for seals purchasing Standard
012 Process process.
PRM- Manage Material [Equipment] It shall be possible to SAP

MD- Master Data for Seals manage material master data for seals Standard
013 Purchasing Process purchasing process.
8.10.4.2 Manage Procurement of Spare Parts (Reefer Kits)
This process deals with the procurement of spare parts for reefer con tainers (reefer kits).

Business Blueprint
Figure 585858 : 5.1.4.3.2. Manage Procurement of Spare Parts (Reefer Kits)
Reefer kits are reefer spare parts maintained onboard a vessel in order to repair possible malfunctioning (plugged in) reefers
during a voyage. The kits may be maintained on CMA CGM or on third party vessels and are specific to each reefer manufacturer
(for example, Carrier, Thermoking, Daikin, and so on).

Business Blueprint
Each reefer kit has a version that is maintained or updated each time a part number in the kit changes, for example, engine
modifications within the reefer. Information managed for each reefer kit includes the kit number, version number, and vessel
details.
Procurement of reefer kits is managed globally depending on vessel location for replenishment. In areas where suitable suppliers
are not available, a service provider may be engaged by means of a broker. The annual costs for reefer kits procurements are more
or less stable at around 2.5M $ per year and are absorbed by the M&R cost center within the Logistics department.
Procurement of reefer kits is currently managed in a legacy application called KIRA where a replenishment order is issued to
purchase additional spare parts when needed. An interface shall be managed between KIRA and SAP to allow for exchange of
information for procurement of reefer kits and subsequent invoice recording and payment through SAP.
To be able to manage purchase of reefer kits or spare parts in SAP, material master and supplier master data shall be maintained
in the system. The procurement process shall be triggered in KIRA with the creation of a replenishment order. This information
shall be received in SAP via an interface (GAP 1823), and a purchase order shall be created.
This (dedicated) purchase order type shall allow authorization management.
Because no stock shall be managed (in SAP), an account assignment (cost center, asset, internal order, and so on) has to be
managed for each purchase order item.
This purchase order in SAP shall be subject to approval which shall be managed via a workflow (GAP 1931).
Following the purchase process in KIRA, the goods receipt shall be recorded when the reefer kits are delivered as per the
replenishment order. This goods receipt shall be replicated from KIRA to SAP via an interface, and a one-step goods receipt shall
be processed in SAP against the purchase order (GAP 1890). An accounting document shall also be created with the posting of the
goods receipt.
The reefer kit supplier shall issue a monthly invoice for all purchases made during the month. Upon receipt, the paper invoice shall
be scanned and electronically stored in the system.
The invoice shall be recorded in the system with reference to the purchase orders created during the month. When the purchase
order number is keyed in for an invoice, relevant data shall be retrieved from the purchase order, automatically populating the
following information: invoicing party (vendor), payment terms, item data (amount, quantity, service code, tax code, account
assignment, G/L account, and so on.) coming from each purchase order line item.
this shall be overwritten with inputs coming from the vendor invoice. A comparison shall then be made between total invoice line

Business Blueprint
Approval to remove the blocking code from the accounts payable invoice and release it for payment
Upon verification of the invoice, payment to the supplier shall be made.
Finally, when a vessel is off-hired (rental period ends and vessel is redelivered to the owner), the reefer kits stored onboard the
vessel shall be removed and stored until they can be placed on another vessel. (Storage locations are only available in certain
locations and are managed by the MnR department (without tracking reorder point)).
This process covers the solution for integration point 2700 as listed in section 7.5 of this document. Further details related to
procurement processes can be found in [BBP_PRM] and those related to invoice recording and payment processes can be found in
[BBP_FIN_AR_AP_BA].
Requirements
PRM- Integration with KIRA [Equipment] It shall be possible to - Replicate approved Implementation 1890,
PO- for Procurement of establish an interface between SAP purchase order for 1823

Business Blueprint

093 Reefer Kits and the legacy reefer kits spare parts
management system (KIRA) to procurement from
enable procurement of reefer kits. KIRA to SAP via an
interface
- Perform monthly
invoice verification and
payment in SAP for
spare parts
procurement
PRM- Manage Suppliers for [Equipment] It shall be possible to SAP Standard

MD- Reefer Kits manage suppliers for reefer kits
010 Purchasing Process purchasing process
Manage Material [Equipment] It shall be possible to SAP Standard

PRM-
Master Data for manage material master data (spare
MD-
Reefer Kits parts) for Reefer kits purchasing
011
Purchasing Process process
PRM- Integration with KIRA [Equipment] It shall be possible to

GSR- for Goods Receipt establish an interface between SAP
027 and the legacy reefer kits Implementation 1890
management system (KIRA) to
register goods receipt.
EQP- Integration with KIRA KIRA is the legacy system used for - Master data (Vessel Implementation 1284
MD- - Master Data management of Reefer kits (spare name, container
009 parts for reefers on board vessels). numbers and
An interface between KIRA and SAP geographical location)
shall be established to allow
exchange of master data.

Business Blueprint
9 Integrated Solution Management and Technical

Solution Management
These topics are out of scope for the business blueprint deliverable. For further details on the expected content of a master data
concept document refer to [OoS_Sections].

Integrated Solution Management and Technical Solution Management AG or an SAP affiliate company. All rights reserved. 262
Business Blueprint
10 Technical/Development Related Items
10.1 Gaps
The following gaps are identified:
Gap ID Gap Short Description
42 Enhancement of the Resource (TM object) : additional Fields
45 Outbound Interface from SAP TM to iMars for Master Data Integration: Container Status (Empty or Full)
46 Outbound Interface from SAP TM to iMars to transfer information about container last booking/BL details
47 Outbound Interface from SAP (ECC/TM) to iMars to transfer Contracts data
48 Interface Outbound from SAP TM to iMars: Master Data Integration for M&R: Geographical Ref.
49 Outbound Interface from SAP TM to iMars for Master Data Integration for M&R: Partners (repair companies),
Pool (Depot)
50 Inbound Interface to SAP from iRecovery to Transfer information on 'To Be Sold' flag
51 Inbound Interface from iMars to SAP TM/EM to Transfer Forecasted Repair Completion Date
52 Inbound Interface to SAP from iMars to send Container Grade Information
54 Outbound interface from SAP TM to iMars/iRecovery: Master data integration: Fleet data & equipment data
56 Outbound Interface from SAP-AA to Transfer Depreciation Value of (OWNED) Containers to iRecovery and
iMars (via Web service)
607 Outbound Interface from SAP TM/EM to iRecovery for Lease Cycle
1138 Inbound interface from iMars to SAP TM to update the damaged flag without modifying the EM Event of the
Damaged Moves
1284 Outbound Interface SAP to KIRA for Master Data
1537 Maintain link between Equipment / Contract / Call Off
1654 List of containers Flagged for Sale
1779 Container Sales Document
1821 Outbound Interface from SAP (ECC) to iMars/iRecovery to transfer Currencies and Exchange rate information
1822 Inbound Interface from iRecovery to SAP ECC/TM to transfer Recovery File Number
1849 Outbound Interface from SAP to iRecovery to Transfer Bill of Lading Information
1851 Inbound Interface from iMars to SAP to transfer repair completion status
1852 Inbound Interface for iMars to SAP for Damage Flag Check
1853 Inbound Interface from iRecovery to SAP to transfer 'Declared in Total Loss' Status for Owned Containers

Technical/Development Related Items AG or an SAP affiliate company. All rights reserved. 263
Business Blueprint
1955 Outbound Interface from SAP-TM to Transfer Depreciation Value of (LEASED) Containers to iRecovery and
iMars (via Web service)
1978 Workflow to Notify about Payment Collection for Container Sale
2003 Inbound Interface from iMars to SAP: Transfer information about Approval of Repair Estimate
2022 Contact Expiration Flag
2042 Attachment to Sub-Lease Invoice
2104 Outbound interface from MDM/SAP to iRecovery to search partners
2425 Percentage of Damaged Units Gated-In at Depot and in Depot Stock
2564 Authorizations for Container Master Data
2570 ISO Code - Size-Type Relationship for Container Master Data
2571 Creation and Maintenance of Technical Specifications at Series Level
2573 Visibility on Valid and Overdue Container Certificates
2574 Update of Container SOLD Status
2585 Container Sale Cancellation & Flag for Sale
2596 Equipment 'off-hire' status based on lease contract expiry
2613 Update of Total Loss Container Status
2654 Consolidated GAP for Container Sales Process in TM
2655 Work list to filter containers by contract reference
2701 Off-Hire Quota Management for Leasing
2716 Automatic Calculation of Monthly Rental days and Costs for Leased (and sub-lease from) Containers
2717 Off - Hire of Leased Containers
2720 Lease Containers Delivery Confirmation to Lessor
2726 On - Hire of Leased Containers
2733 (Sub-lease-to confirmation) Forwarding Order
2734 Release of Container under Sub-Lease-To and Relevant Status Update
2735 Redelivery of Container under Sub-Lease-To and Relevant Status Update
2736 Sub-lease-to Redelivery Confirmation to Lessee
2737 Forwarding Settlement for Sub-Lease-To
2810 Owned Containers Delivery Confirmation to Supplier
2811 On - Hire of Owned Containers
2584 Update of Total Loss Paid Container Status at Invoice Entry
2718 (Lease call-off) Freight Order

Business Blueprint
[Owned containers - MM] Define a range of serial numbers at purchase order item level, not a list as standard,
329 and include a match code for these serials in search functionality
419 [TM] Agreement additional Fields
421 [Leased containers-TM] Field to record end date of build-down period
425 [TM] Freight order-Service order additional fields
459 Declaration of Total Loss (for a leased container) send by Email to the Lessor
480 [Leased containers-TM] Use contract build-up period into the call-off to calculate the end date of on-hiring
486 Purchase/Service/Freight order form
1136 Work-orders month compilation from IMARS) = Create one monthly PO in SAP
1493 Form for BV & CMC Purchase Order
1495 [MM] Purchase order additional fields
1496 Total Loss PO price calculation for lease container
1497 [MASTERDATA] Indicator at supplier level to stop Per Diem for Total loss process
1498 [Lease Container -TM ]Update Off Hire date on Equipment in case of Total Loss
1531 Integration of Lessor Release Order in (Lease Call-Off) Freight Order
1823 Inbound Interface Purchase Order Creation
1870 [Owned container] Record Logistical receipt for owned container
1890 Inbound interface for goods receipt
1931 Workflow linked to pPurchase order approval
[TM- Leasing Container] Automatic Creation of Purchase Order for surveyor Activity when thewhen the
1973 container is Off-hired.
2594 Search contract by technical specification
2606 Linked Original Lease Contract to Purchase Order Option
2820 Manage services definition at contract level
Further details about the gaps can be found in [GapList].
10.2 Custom Development
The topics in this BBP document are not a part of the SAP Custom Development specification.
Formatted: Normal

Business Blueprint

www.sap.com/contactsap Formatted: English (United States)
End of Document - Asset ManagementAsset ManagementAsset ManagementAsset Management Formatted: SAP_Emphasis

Formatted: SAP_Emphasis
2014 SAP AG or an SAP affiliate company. All rights reserved.

Finding The EAP Requisition

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Finding The EAP Requisition

Uploaded by

Copyright:

Available Formats

Business BlueprintBusiness Blueprint CUSTOMER ACCESS PERMITTED

SAPHIR - SAP - Equipment FOR

Asset ManagementAsset Management

Version Date Company Author/Editor Status Change Formatted Table

Customer Access Permitted for

1.0 30. September SAP Bushra Khan, Approved Figure 55 updated

Formatted: English (United States)

Customer Access Permitted for

Name Title Version Date Company Review / Approval

Customer Access Permitted for

1 About This Document ........................................................................................................................................................ 97

2 Solution Overview ......................................................................................................................................................... 1413

3 Assumptions and Constraints ......................................................................................................................................... 1918

4 Value Determination ...................................................................................................................................................... 2019

5 SAP Organizational Structure ........................................................................................................................................ 2927

6 Data Management .......................................................................................................................................................... 3028

7 Business Process Landscape .......................................................................................................................................... 3734

8 Business Process and Solution Design ........................................................................................................................... 5949

Customer Access Permitted for

8.3.3 Requirement List ................................................................................................................................... 8781

9 Integrated Solution Management and Technical Solution Management .................................................................... 262250

10 Technical/Development Related Items ...................................................................................................................... 263251

1 About This Document ..........................................................................................................................................................7

Customer Access Permitted for

2 Solution Overview ............................................................................................................................................................. 12

3 Assumptions and Constraints ............................................................................................................................................. 17

4 Value Determination .......................................................................................................................................................... 18

5 SAP Organizational Structure ............................................................................................................................................ 23

6 Data Management .............................................................................................................................................................. 24

7 Business Process Landscape .............................................................................................................................................. 30

8 Business Process and Solution Design ............................................................................................................................... 42

Customer Access Permitted for

8.6 Process Equipment Sub-Lease-To Management (5.1.1.6.) ........................................................................................ 161

9 Integrated Solution Management and Technical Solution Management ..........................................................................239

10 Technical/Development Related Items ............................................................................................................................ 240

Customer Access Permitted for

1 About This Document

o Light Blue: Normal process

o Dark Green: Integration points within Equipment Workstream Formatted: Font: 9 pt

o Light Green: Equipment status updates Formatted: Font: 9 pt

o Orange: Integration points across streams Formatted: Font: 9 pt

o Yellow: GAPs Formatted: Font: 9 pt

Formatted: Font: BentonSans Book

Customer Access Permitted for

Formatted: Font: BentonSans Regular Italic

1.2 Management/Executive Summary

Customer Access Permitted for

Equipment Asset Management covers the following topics:

Management of owned equipment procurement and sale

Management of equipment leasing (and sub-leasing)

Management of equipment damage and loss

Management of equipment maintenance and repair

Management of recovery for equipment loss

Management of procurement for seals and spare parts

Customer Access Permitted for

1.4 Related Documents

Document Document Title Version/ Filename Author Formatted Table

[ToBe_EQP] To Be Equipment Fleet 0.6.4 SAP_FGD-To- SAP Field Code Changed

[BBP_PRM] BBP Procurement 0.109 SAP-FND- SAP

[BBP_EQP_IM] BBP Inventory 0.100.9 SAP-FND- SAP

[BBP_EQP_LM] BBP Logistics 0.10 SAP-FND- SAP

[BBP_Q2C_Booking] BBP Documentation 0.99 SAP-FND- SAP

[BBP_NWK_CAPA_ALLO BBP Network Capacity 0.9 SAP-FND- SAP