Req ID Polycab Businesss Process High-level Requirement Description

Creation of Delivery through Interface

PC-001 Dispatch Planning from EBS to OTM

PC-002 Dispatch Planning Creation of Delivery Manually in OTM

Delivery Types to be Interfaced from EBS

PC-003 Dispatch Planning
via OIC

PC-004 Dispatch Planning Return Order Creation in OTM

Delivery Indicators for Order

PC-005 Dispatch Planning Categorization

PC-006 Dispatch Planning Maintenance of Commodity

Incompatibility

PC-007 Dispatch Planning Line Level Maintenance of Commodity

PC-008 Dispatch Planning Calendar Maintenance

PC-009 Dispatch Planning Order Planning

PC-010 Dispatch Planning Operational Dates

PC-011 Dispatch Planning Ship Unit Building

PC-012 Dispatch Planning Planning constraints on Order

PC-013 Dispatch Planning Full Order Cancellation Process

PC-014 Dispatch Planning Order Modification via SHIP CONFIRM

PC-015 Dispatch Planning Order - Hold status

PC-016 Dispatch Planning No Splitting of order

PC-017 Dispatch Planning Orders selection for Scheduled Bulk

Planning

PC-018 Dispatch Planning Orders selection for Manual Bulk Planning

PC-019 Dispatch Planning Transport Network

PC-020 Dispatch Planning Adhoc Shipment Planning

PC-021 Dispatch Planning Planning Constraints - Location Constraints

PC-022 Dispatch Planning Planning failed orders

PC-023 Dispatch Planning Pick up/Drop restrictions in Multistop

PC-024 Dispatch Planning Preferred Rate by Lane

PC-025 Procurement Freight Cost for Land

PC-026 Procurement HDC Volumetric Rates

PC-027 Procurement Accessorial Charges

PC-028 Procurement Accessorial Charges

PC-029 Procurement Half Yearly Fixed Rate

PC-030 Procurement Spot Tendering

PC-031 Procurement Spot Tendering

PC-032 Procurement Spot Tendering

PC-033 Dispatch Planning

PC-034 Dispatch Planning Shipment status visibility

PC-035 Dispatch Planning Adhoc Rates capturing for the return

shipment

PC-036 Dispatch Planning Shipment Cancellation

PC-037 Track and Trace ROAMBEE Interface

PC-038 Safex Interface

PC-039 Safex Interface

PC-040 Safex Interface

PC-041 Track and Trace Shipment Tracking Events

PC-042 Track and Trace Shipment Tracking Events information

PC-043 Track and Trace OTM Mobile App - Carrier Role

PC-044 Track and Trace Shipment Tracking Events-SMS

Upload / attach documents to OTM

PC-045 Track and Trace against shipments

Delivery Creation Interface from EBS to

PC-046 Interface OTM

PC-047 Interface Delivery Updates / Cancellations

PC-048 Interface Planned Shipment from OTM to SAP

PC-049 Frieght Settlement Invoice Generation in OTM

PC-050 Frieght Settlement Invoice Initimation to Transporter

PC-051 Frieght Settlement Invoice Validation by Transporter

PC-052 Frieght Settlement Two Level Approvals for the Invoice

PC-053 Frieght Settlement Cost Allocation

PC-054 Frieght Settlement Provisioning

PC-055 Frieght Settlement Shortages & Damages

PC-056 Frieght Settlement Master details as per Provisioning report

PC-057 Frieght Settlement Shipment Approval

PC-058 Master Data Location Interface

PC-059 Master Data Location Master

PC-060 Master Data Service Provider

PC-061 Master Data Rate Master

PC-062 Master Data Lead time for CheckIN/CheckOUT

PC-070 Track and Trace Lead time Penalty

PC-064 Master Data Itineraries

PC-065 Master Data Location Corporations

PC-066 Master Data Service Providers

PC-067 Master Data Rate Offering

PC-068 Master Data Lanes

PC-069 Master Data Reason codes

PC-071 Users User Creation

PC-072 Users User Preference

PC-073 Users User Data Access

PC-074 Users Data Restriction based on User Role

PC-075 Users User Menus

PC-076 Users User Role: ADMIN

PC-077 Users User Role: ***

PC-078 Track and Trace GATE OUT Event

PC-079 Frieght Settlement Consolidate Invoive

PC-080 Dispatch Planning RM Movement Special process tracking

PC-081 Procurement Billing to nearest warehouse

PC-082 Dispatch Planning PTL Movement

PC-083 Dispatch Planning Hazardous Movement Tracking

PC-084 Dispatch Planning AIR Movement Tracking

PC-085 Dispatch Planning Stop off Charges

PC-086 Dispatch Planning Documentation

PC-087 Frieght Settlement Multipoint Transporter Billing

PC-088 Freight Settlement Invoice Creation Restriction

Polycab Business Requirement Detailed Requirement Description
System should have ability to receive Deliveries from EBS via Automated
Interface for the below Sales order/Purchase order(ASN)/Return Order/Stock
Delivery Order created after processing of Transfer/Export/Import etc.
Sales order/Purchase order(ASN)/Return
Order/Stock Transfer/Export/Import
process will be interfaced. Delivery Orders will have the details like Item, Weight, EPD, Ship From, Ship
To, Line/SKU details(DRUMS/GUNNY BAGS/PALLET), Incoterms(for Exports),
Order Refnums Etc..

System Should have the ability to create and Edit Deliveries Manually for
Non DO Order process for RGP and NRGP Specific scenarios as listed Below.
movement 1. Manual Order Creation for Non DO Orders with the delivery type
2. Any Manual Updates required to be done in OTM?
3. Non DO order for Export machinery and other movement.

System should receive and maintain different Delivery Types from EBS for
Delivery type mapping in OTM different order types as part of Delivery Interface(Sales order/Purchase
order/Return Order/Stock Transfer/Export/Import)

Return Order Process for order return System should have ability to receive Return ordersfrom EBS to OTM via OIC
scenario from customer to Interface. These deliveries will be created and interfaced to OTM
retrospectively.
warehouse/Plant. Return Orders need to
be recorded in TMS application
All Return Orders should be Planned and executed with panelled transporters.

System should ability to provide Delivery Planning Visibility through indicators

via color coding:
-- White : New order created / Order not planned (PLANNING_NEW)
-- Green : Order planned into shipment (PLANNING_FINAL)
Indicator to understand the trip status -- Yellow : Order Unassigned (PLANNING_UNSCHEDULED)
-- Red : Planning Failed / Action required (PLANNING_FAILED)
-- Orange : For Fully Cancelled Orders (ORDER_CANCELLED)
-- Blue : For Order on Hold (ORDER_HOLD)

Process of restricting mixing of items in

single trip/shipment.
a. Boxes and coils can go with FMEG. OTM should provide the Flexibility to maintain the incompatibilities in OTM
b. HDC and LDC can go with each other for specific items
c. LDC drums and boxes can go with each
other.

Process of restricting mixing of items in

single trip/shipment. Workflows to be maintained in OTM to maintain the Commodity at line level
a. Boxes and coils can go with FMEG.
b. HDC and LDC can go with each other for Incompatible items or EBS system to send the details via order release
Interface
c. LDC drums and boxes can go with each
other.

Process on E-Com and other customers OTM should provide the ability to maintain the calendar with the pickup and
who has restriction over delivery time delivery window for each day of the weeks along with the holidays
window.
Indicator to understand Delivery order The system should provide an indicator for user to know if the delivery is
planning planned .
System should have ability to capture delivery time and Early Pickup date in
OTM as part of the order interface (for all types of orders)

Packaged material like Boxes/Gunny System should have the ability to capture Transport Handling Unit
bags/pallets/Drums should be interfaced information Like drum/Boxes/gunny bags/pallets etc.. while the Order release
along with Item and item weight
information in the Delivery order is interfaced to OTM. Each Transport Handling Unit Type should represented
interface. as a separate line item in OTM.

System should have the ability to capture planning related constraints and
then use these constraints during the Shipment Planning in order to produce
Delivery order can be updated with
constraints like truck type, transporter the desired output. Example,
(Requested user to send if any such constraints are required)
etc.. for restricting indent/trip/shipment
creation process These constraints can be added/updated in OTM after the delivery is created
in OTM, before planning.

The System should be able to receive and support the following order
Process of cancelling delivery order in cancellation scenarios from EBS:
New TMS. 1. Order cancelled before it is planned into a shipment
2. Order cancelled after it is planned but before SHIP CONFIRM.

The System should be able to support the order modification during SHIP
CONFIRM if any short pick at the time of picking and loading.
Actual Delivery Order quantity update
after SHIP confirm process.
No other order updates are sent to OTM after Ship Confirm in EBS. Any
quantity changes will be interfaced to OTM via SHIP CONFIRM Updates

The system should allow the users to Manually Hold and Unhold some orders
from planning. The orders with HOLD status will not participate in the
To get confirmation from Polycab
planning run till the Hold is released.There should be logic defined to hold the
orders in EBS System as well

Currently business is manually spliting the delivery order and assign in to trip.
Order Split Process when Bulk order is OTM will create multiple shipment to single bulk order. And the information
received.
will be sent to EBS
Automating the delivery order planning OTM Should provide the Saved Query(consolidating the orders) for the user to
process select the set of orders.
The system should have the ability select Order for planning .
Manual Delivery Order Planning

The system should be able to support the below mentioned Transport

Network Models
- Direct (Point to Point)
- Multipick & Multi Drop

Ability to Plan Shipments on an ad hoc basis. User must be able to plan the
shipments using OTM UI on a need basis.
1.The user can perform Manual Bulk Plan
Manual Delivery Order Planning
2.The user can perform Manual Planning
A) Direct Plan
B) Show Routing Option

Route Restriction based on vehicle type All type of vehicle cannot go to certain customer due to route retrictions. OTM
should be able to restrict certain Equipment type for certain customer during
for certain customer
planning.
 Because of any reason if the orders are failed in planning.Operational Team
will rectify the root cause and manually plan the Delivery's. Any Approvals
required in this case?

System should have the ability to restrict the number of Pickup or Drops on a
shipment.
5 Pickups and 2 drop points for sales
order for customer. For E.g.: Drop/Pickup stops should be restricted to 3 for a particular lane
means whenever the shipment is built for the lane the OTM planning engine
will check that the drop/pickup should not be more than 3.

One transporter can have a priorty over OTM will support the assignment of preferred transporters by lanes. Planners
may manually override the preferred transporter assignment in OTM.
other. Although transporter can be In case if Polycab has some specified carriers which are preferred for a lane,
changed by business at any time. OTM allows the user to plan the shipment for that carrier.

The System should be able to Calculate Shipment Rates for all land
movements (FTL & PTL).
Rate calculation for the trip/Shipment 1.Per Tonnage
2.Per BOX
3.Per Kg

For certain movements volumetric weight is calculated and rating of those

shipment is done based on volumetric weight. OTM should have the ability to
Volumetric Weight calculation process maintain the HDC DIM Factor (Volumteric weight) against the per kg rates for
selected movements

The System should be able to calculate and apply fixed Accessorial Cost to
shipment.
Examples
Additional cost calculation apart from -- Fuel Charges(40% of the negotiated freight)
base freight -- Demurrage (Detention and penalty)
-- Under weight Charges.
-- Other charges

OTM Should Provide the ability to manually add additional accessorial cost
against shipment
Manual addition of additional cost on
trip/Shipment -- Over Dimentional charges for org 29 A, 12A, 12B
-- Loading, unloading, extra distance charges
-- OWC in KM covered

Currently, Polycab contract is re-newed every 6 month/1 year basis. OTM

Contract Date update. should support such rate model where rates are expired after this specified
date.

OTM system should have the ability to send Planned shipment details to
carrier portal (TRANSPORT EG) where spot bidding is done.
TRANSPORT EG Spot bidding process - Direct Spot bit during shipment creation.
- Spot bid after contracted transporter has declined or did not place the
vehicle.

TRANSPORT EG Bid approval process OTM system should have the ability to receive Shipment and bid information
like Transporter,Equipment, Cost as an update to OTM.
OTM should have the ability to confirm tender and send shipment interface to
TRANSPORT EG Tendering process EBS once all bidding process is competed
Functionality to dd more deliveries to a System should have ability to add or remove deliveries to an to an existing
trip/shipment planned shipments without replanning them again.
 The system should provide visibility to the user in form of indicators for
various shipment statuses.
Tracking trip/shipment status at each --- White : Shipment is created
milestone --- Red : Shipment not reaching on time
--- Yellow :Shipment is Tendered
--- Green : Shipment Utilization Passed/Tender Accepted

OTM Should provide the Provision to capture the Adhoc Rates for Return
Customer Return process Shipments from customer when customer returns with his own transporter to
the warehouse.

The system should allow the users to cancel the shipment in case cancellation
message is received from EBS
Trip Cancellation Users should be able to unassign the shipment in case of any cancellation.
OTM should send a notification message to EBS if the Planned shipment is
already sent.

Interface to be developed from RoamBee to OTM to capture the real time

tracking events in OTM
Track and trace for the trip/shipment
Note:Checking with other customers on the availability of alterate systems
where tracking can be done parallelly

OTM should be able to send shipment information to safex for booking and
Track and trace for PTL Shipment - Order safex will send back way bill/ docket number to OTM for reference. After
booking Booking way bill can be tracked in safex

Track and trace for PTL Shipment - OTM should be able to capture shipment tracking information sent/posted by
Tracking Shipment Safex at certain interval.

Track and trace for PTL Shipment - POD OTM should be able to capture POD image sent by Safex and E-POD process
flow will be triggered in OTM.

OTM Should be configured to capture the below shipment events,

• Arrival of Vehicle(GATE IN/GATE OUT)
• Departure of Vehicle
• POD
• Enroute Completion
Events /Alerts Capturing in OTM
• Alerts
These events can be,
-- Added manually in OTM
-- Interfaced from Third Party Systems

Data capture in OTM during gate out OTM Should Capture the RFID Number, Weight, Truck number with the GATE
event OUT Events

Freight Forwarders / Carriers may be given access to OTM mobile app to

perform the below activities,
-- Adding Shipment Events Like POD, Vehicle Arrival /
MOBILE App Facility
Departure(GATEIN/GATE OUT)
-- POD Confirmation (Including Photo and Signature)
-- POD Receipt Time
 OTM Should have the ability to sent SMS at the time of GATE IN
SMS Triggering with the GATE IN Events Events.Alignment needs to be done with the SMS gateway with Polycab on
this requirement

The system should have the ability to upload documents against OTM
Document Upload Functionality business objects
Ex: Scanned POD Copy/E way Bill/Transporter Frieght Invoice

Deliveries Document once created in EBS will be sent to OTM via OIC .
Following order details would flow from SAP to TM (Some of these would be
optional for Primary)
EBS delivery number with date and time (would be the planning order in TM).
EBS order number
Order type.
Order reason
Ship to & sold to party code(Involved Party).
Delivery Order Interface Ship from location code.
Late delivery date
Early pickup date & time. .
Order statuses – delivery created, Invoiced
Item details (Item ID, quantity, base unit of packing, gross & net weight &
volume).
ORG COde
Business Area
Special Instructions

Once SHIP CONFIRM is completed in EBS this would trigger an order

modification message to OTM via OTM OIC. Order Updates/Modification is
triggered only when PGI is done in EBS any other Delivery updates before ship
Delivery Order Updates confirm will not trigger updates to OTM.
This Interface also supports the delivery Cancellation. If any delivery cancelled
in EBS, an update will be sent to OTM Realtime.
 The System should be able to interface planned shipment information to EBS
after tender acceptance, for further processes in EBS.

Following shipment details would flow from OTM to EBS via Planned
Shipment message once user performs Ready to Dispatch action against the
shipment in OTM.
Vendor code / Single Dummy Vendor code for self-pickup (Name field to be
updated by the user)
From location code
Indent(Trip/Shipment) Creation Order IDs
Shipment ID
Equipment type ID – Required for reporting
Equipment Number
Shipment cost – total shipment cost along with allocated order costs.
GL Codes
Default status of approved or approval not required to be sent from OTM to
EBS, cost changes in existing shipment & claims
Additional details to be added post requirement discussion

OTM Should provide the flexibility to create Invoices in OTM on the addition
Bill Creation in OTM of POD Event.Invoice Should Capture all the costs that’s captured at the
Shipment Level(Multiple POD=One invoices will happen on Plant as well as
Warehouse)

Notification to Transporter OTM should sent the Initimations to that Transporter on the event of Invoice
creation

Validation by Transporter OTM Should allow the transporter to validate the invoices and submit any
additional charges to be added on to the Invoice

Once the Transporter validates and submits the Invoice(PTL-Consolidated

Invoice & FTL-Individual Invoice) validations has to happen at the below two
Invoice Approval by Logistics & Finance levels in OTM(Approval rules to be maintained in OTM)(like If cost is
Team exceeding 5000 needs approval)
1.Validation & Approval by Logistics Team
2.Validation & Approval by Finance Team

OTM should provide the ability to allocate the cost against ITEM Level at the
Allocate Cost weight basis.

OTM should provide the ability to send the Planned shipment interface to the
Provisioning Report to the Accounts team accounts team capturing all the details as per the provisioning report that’s
captured on monthly or yearly basis

OTM Should provide the provision to Logistics Team to add the Shortages and
Shortages & Damages addition Damages as per the POD received.These cost should be added as saperate
line items in invoice. Invoice will have to go through the approval process to
get this settled finally.

Master details that’s part of Provisioning report that’s not directly available at
Provisioning report masters the shipment level needs to populated at the Shipment remark & refnum
levels
 OTM Should have the ability to Validate the frieght cost and the percentage
Value before the approval of Shipment.
1.OTM Should compare the freight cost base and the percentage value
maintained(if any) against the ship from Location if the value is less than
Intent Approval for limit 5000,No Approvals are required
2.OTM Should compare the freight cost base and the percentage value
maintained(if any) against the ship from Location if the value is greater than
5000,Approvals are required

OTM should provide the ability to receive the location details from EBS and
match the details to the Location system in OTM
Location Interface
Location updates to be received which will have the activation/deactivation
flags for the respective Locations

OTM to maintain the route level restrictions for selected cutomers.Custom

Location Master Interface restriction of Equipment(Truck Type) to be maintained at selected customer
locations within the Location Master

OTM should provide the ability to receive the Service Provider details from
EBS and match the details to the Location/Servprov details in OTM
Transporter Interface
Activation & Deactivation flags to be received with the updates from EBS

System should have information of rate records offered by carriers / service

Rate Master Upload providers .OTM looks for valid rate records while planning shipments.

OTM Should maintain the different Lead time at Equipment type required
OTM Should maintain pickup window of 24 hours .Transporter not placing
Delivery order pickup window for with this 24 hours will get a penalty worth 1000 Ruppes for Stock Transfer &
transporter SO

The System should be able to configure Itineraries (routing options) which

Route Master Upload represent Polycab transportation network.
Direct
Multi-Stop

Location Master Interface System should have information related to Corporations (A corporation is a
record that groups the various locations for each company)
System should have information of various service providers related to
Transporter Interface
transportation like land transporters,freight forwarders, 3PL vendors etc..
System should have the information on various rate offerings provided by
Transporter Contract Upload carriers/service providers. OTM looks for valid rate contracts while planning
shipments

Lane Master Upload System should have information on lane information like source
region/geography, destination region/geography

System should have information on various reason codes to be maintained.

Reason codes can be applied for all type of shipment modification. (Reason
Codes describe why a particular event or action occurred. For example, an
event may state that the shipment is delayed and the reason code states that
the shipment was delayed because of bad weather.)

List of users need to be provided which will be created in OTM in alignment

with the listed roles for Sub Process User Roles
User Preference will be defined which will specify on screen preferences such
as time zone, currency, wt./vol. UOMs, etc..
Polycab to provide confirmation on accesses to specific screens and type of
access (view/edit) that needs to be granted for each of the user roles.
 OTM data should be restricted based on User Role, User Associated Depots
and but Business unit (AP Tertiary and CP1)
Separate User menus should be provided for each Role and necessary screens
should be configured for each user Role.

User Role: ADMIN need to be created in OTM to have admin access over the
entire OTM Modules.
This role will have view/edit access to all the objects and transactions of OTM

To be Discussed
E-Way bill, LR Number, Weigh Bridge Information, IRN number to be updated
Truck checkout information capture
to OTM during Ship confirm
OTM Should provide the access to transporter to consolidate the Invoices
Invoice consolidation by transporter weekly as well as monthly for PTL Movements
DO interface during RM movement when OTM should have capability to capture Delivery Order for Raw material
ASN is created. movement

Bill to, Ship to scenario OTM should have capability to generate invoice for nearst bill to
ex: Solar item movement in ahmedabad location/warehouse but the dispatch will happen from other
location/warehouse to a ship to party directly.

In case of PTL movement business is dispatching based on cases/boxes and

PTL movement scenario freight cost will be calculated based on per case/box contract as applicable.
OTM should have the capability to plan this PTL orders on case level.

OTM should have ability to define hazardous material and plan the shipment
Hazardous scrap\Scrap movement accordingly. Although freight cost/invoicing will not be involved.

Air Movement tracking Polycab panel transporter will be responsible for air movement delivery. OTM
should have ability to plan delivery orders for these specific transporters.

Multipoint loading stop off charges are OTM should have capability to maintain stop off charge as master and apply
present as 1000 it during multistop shipment.
Cut off time for document generation and OTM should have a capability to restrict document upload for transporter
upload for transporter with a cut off time

Transporter with multiple sites for Transporter will have multiple locations based on state/region and invoice
invoicing and billing should happen to said location where truck is placed and dispatched.

Future date invoice cannot be created Future date invoice cannot be created and previous dated invoice greater
and previous dated invoice greater than 1 than 1 year cannot be created
year cannot be created
Review Comments Design Comments System involved

New Interface has to

be built via OIC EBS-OIC-OTM

New Interface has to

be built via OIC EBS-OIC-OTM

EBS-OIC-OTM

System should have ability to receive Return ordersfrom EBS to OTM via OIC New Interface has to
Interface. These deliveries will be created and interfaced to OTM be built via OIC.
retrospectively. EBS-OIC-OTM
Delivery order has to
be interfaced
All Return Orders should be Planned and executed with panelled transporters.

Order default status OTM

Master Data OTM

Automation Agents OTM

Master Data OTM

 OTM

EBS-OIC-OTM

Each Transport
System should have the ability to capture Transport Handling Unit Handling Unit Type
information Like drum/Boxes/gunny bags/pallets etc. along with dimension sould be mapped with EBS-OIC-OTM
information, while the Order release is interfaced to OTM. Each Transport item and represent a
Handling Unit Type should represented as a separate line item in OTM. single line item in
OTM.

System should have the ability to capture planning related constraints and
then use these constraints during the Shipment Planning in order to produce
the desired output. Example,
(Requested user to send if any such constraints are required) Updated OTM

These constraints can be added/updated in OTM after the delivery is created

in OTM, before planning.

EBS-OIC-OTM

EBS-OIC-OTM

OTM

Workaround has to be
There is a scenario of order split delivery, where the order (DO) of more than discussed with OTM
50 ton or above is expected to be planned into multiple shipments
business

OTM

OTM

OTM

OTM

OTM
 OTM

System should have the ability to restrict the number of Pickup or Drops on a
shipment.
For E.g.: Drop stops should be restricted to 3 for a particular lane means OTM
whenever the shipment is built for the lane the OTM planning engine will
check that the drop should not be more than 3.
Similary - Pick up stops should not be more than 2 stops--Please check

OTM

Rate Basis OTM

OTM

OTM

OTM

OTM

OTM-OIC-
TRANSPORT EG

OTM

OTM-OIC-EBS

OTM
 OTM

OTM

EBS-OIC-OTM

ROAMBEE-OTM

OTM

E-way bill number, LR Number, IRN number to be recieved as a part of Ship Added a saperate line
confirm (actual shipment) from EBS. RFID as captured during gate-in will be on ship confirm OTM
returned at the gate out.

OTM Mobile App

For this we need to align for SMS gateway with Polycab, let us follow up on OTM
this

OTM

INTERFACE
MAPPING

INTERFACE
MAPPING
 INTERFACE
MAPPING

OTM

OTM

OTM

OTM

Distinction of cases
and boxes is based on OTM
contracted RR

OTM

OTM will capture the

details in the Invoice OTM
Remarks

OTM
 OTM

INTERFACE
MAPPING

INTERFACE
MAPPING

INTERFACE
MAPPING

OTM

OTM

OTM

OTM

OTM

OTM

OTM

OTM

OTM

To be discussed OTM

To be discussed OTM

To be discussed OTM
To be discussed OTM

To be discussed OTM

To be discussed OTM

To be discussed OTM

OTM

OTM

OTM

OTM

OTM

OTM

OTM

OTM

OTM

OTM

OTM
Movement Type Requirement Source Key Business Stakeholder Req. Priority Complexity Fit/Gap

Req. Workshop 1 High Fit

Req. Workshop 5 Low GAP

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Low Fit

Req. Workshop 4 Medium Fit

Req. Workshop 1 High Fit

Req. Workshop 4 Low Fit

Req. Workshop 4 Low Fit

Req. Workshop 4 Low Fit

Req. Workshop 2 Medium Fit

Req. Workshop 5 Low Fit

Req. Workshop 1 High Fit

Req. Workshop 3 Medium GAP

Req. Workshop 2 Medium Fit

Req. Workshop 3 Medium GAP

Req. Workshop 3 Medium Fit

Req. Workshop 1 High Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 2 Medium Fit

Req. Workshop 2 Medium Fit

Req. Workshop 2 Medium Fit

Req. Workshop 2 Medium Fit

Req. Workshop 2 Medium Fit

Req. Workshop 5 Low Fit

Req. Workshop 3 Medium Fit

Req. Workshop 1 High Fit

GAP

GAP

Req. Workshop 1 High Fit

Req. Workshop 2 Medium Fit

Req. Workshop 2 Medium GAP

Req. Workshop 3 Medium FIT

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium

Req. Workshop 1 High Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 3 Medium GAP

Req. Workshop 4 Medium FIT

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 4 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium Fit

Req. Workshop 3 Medium GAP

Req. Workshop 3 Medium GAP

Req. Workshop 3 Medium Fit

Comments OTM Modules

Order Management

Integrating
Shipment
information to EBS
is a challenge as
Delivery order is not
interfaced. Further
discussion is needed
with business
Order Management
Business has to
provide field to
differentiate each
type of order and
map with business
process
Order Management

To Get clarity on the

process of adding
truck type and
transporter
Order Management

Order Management

Order Management

Order Management

Location Manager
Order Management

Order Management

Order Management

Order Management

Order Management

Order Management

Order Management

Order Management

Order Management

Order Management

Shipment Management

Shipment Management

Location Manager
Order Management

Contract and Rate

Management
Planning Parameters

Service Provider Manager

Contract and Rate

Management

Contract and Rate

Management

Contract and Rate

Management

Contract and Rate

Management

Contract and Rate

Management

Shipment Management

Shipment Management

Shipment Management

Shipment Management
 Shipment Management

Contract and Rate

Management

Shipment Management

Third Party Interface

Shipment Management

Third Party Interface

Shipment Management
Third Party Interface
Shipment Management
Third Party Interface
Shipment Management

Shipment Management

Shipment Management

Mobile app
enhanced
functionality needs
to be checked
OTM Mobile Maps
Alignment is needed
with business on
SMS gateway before
considering this
requirement
Shipment Management

Document Management

Interface Manager

Interface Manager
Interface Manager

Financials

Financials

Financials

Financials

Financials

Financials

Financials

Financials
Financials

Master Data

Master Data

Master Data

Master Data
Master Data

Master Data

Master Data

Master Data

Master Data

Master Data

Master Data

Master Data

User Manager

User Manager

User Manager
User Manager

User Manager

User Manager
User Manager

Shipment Management
Financials

Order Management

Financials

Shipment Management

Order Management

Order Management

Contract and Rate

Management

Document Management

Financials

Financials
S.No Interface Name Source System Destination System Comments/Remarks
1 Order Release Interface EBS OTM
2 Order Release Update EBS OTM
3 Planned Shipment Interface OTM EBS
4 Planned Shipment Interface OTM TRANSPORT EG
5 Response Interface from Transporter TRANSPORTEG OTM
6 Voucher Interface OTM ACCOUNT SYSTEM
7 Location Interface EBS OTM
8 Service Provider Interface EBS OTM
9 Item Interface EBS OTM
10 SAFEX Interface-Inbound to OTM SAFEX OTM
11 SAFEX Interface-Outbound to OTM OTM SAFEX
12 Tracking event Interface from EBS EBS OTM
Sl No Assumption
1 Manual Selection of transporter and selection of type of vehicle required based on order size.
2 Bulk Plan to be scheduled with a cut off time in OTM
3 Picking Confirmation to be received as actual shipment or order update?
4 Damages and shortages from Transporter will be tracked in Emails
5 GL Codes to mapped to Invoice
6 For Each Transporter Invoice will be consolidated for a selected period of time
7 Sales reutn interface during RMA generation ( RMA percentage to be checked if it is applicable in OTM). Without DO
8 Panneled transporter movement from Plant to Port for exports
9 Shipping instructions tracking for export's (Is integration required)
10 freight forwarder and transporter ( How to handle freight forwarder freight cost).
11 Documentation to exports-(Where to handle it?)
12 Demurrage charges in Exports. This is very rare should we track this ?
13 Sample orders Air movement?
14 Air Movement for normal orders as seen in plant visit
15 Utilzing truck more than 100% based on order availibility - How to add this?
16 Inbound movement from Port to nearest plant. ( Should we handle Freight forwarder Payment ?)
17 Transport EG contracts to be integrated with OTM rate master for freight contract processes
18 RM Movement with to-pay scenario to record freight cost.
Wire business less than 2 lakh order - Customer has to be paid.
fulfillment order (for WRE) of less than INR 2 lakh value is applicable for CFA freight payment
19 Fulfillment orders (for LDC) of less than INR 5 lakh value is applicable for CFA freight payment.
20 For Some shipment POD should by pass as at warehouse POD is not recieved.

Leased truck with multiple trip tracking - OTM should have the ability to Understand leased truck
21 (dedicated) and calculate number of trips per day based on truck number.

Leased truck with multiple trip costing- OTM should have the ability to split the cost against the
22 calculated number of trips on a day level. Cost has to be apportioned(SPLIT) on Org level.
23 E-Parivahan Interface not in scope
24 POC to be given for Spot Bidding Process
25 No Region Masters will be maintained
 Comment
Mass Update Functionality to be given

licable in OTM). Without DO interface.

Ashok Comment- This is not the

requirement of Polycab - Please check
on this. This can be generated as a
report
Shashank Comment- If MIS is created
this can create a gap in invoicing and
freight settlement

Ashok Comment- This is not the

requirement of Polycab - Please check
on this. This can be generated as a
report
Shashank Comment- If MIS is created
this can create a gap in invoicing and
freight settlement