Land O Lakes Inspirage OTM-GTM Cloud SOW 2018-06-27 V11 PDF

DocuSign Envelope ID: A910E0EE-1809-4912-AEDC-75A0BEC80746
Land O’ Lakes
OTM Cloud Migration and GTM
Implementation
By
Inspirage, LLC
Date Submitted: 29 – June -2018
Revision: v11.0
Revised 21 – August - 2018
Inspirage Contacts
Paul Mathers
paul.mathers@inspirage.com
(301) 514-4426
Table of Contents
Master Service Agreement ................................................................................................................... 5
1. Project Overview ......................................................................................................................... 5
2. Scope 5
2.1. Overview .................................................................................................................................... 5
2.2. Project Scope and Definition ........................................................................................................ 6
2.2.1. Global Design Scope.......................................................................................................... 6
2.2.2. OTM/GTM Modules............................................................................................................ 6
2.2.3. Third Party Applications/Partners ....................................................................................... 6
2.2.4. OTM Scope ....................................................................................................................... 7
2.2.5. Transportation Order Management..................................................................................... 7
2.2.6. Transportation Planning .................................................................................................... 7
2.2.7. Transportation Execution ................................................................................................... 8
2.2.8. Freight Settlement ............................................................................................................ 8
2.3. GTM Scope ................................................................................................................................. 8
2.3.1. Item Classification ............................................................................................................. 8
2.3.2. Restricted Party and Sanctioned Country Screening ............................................................. 8
2.3.3. License Determination and Management ............................................................................ 8
2.3.4. Document Determination, Generation, and Management ..................................................... 9
2.3.5. AES Filing ......................................................................................................................... 9
2.4. Reporting ................................................................................................................................... 9
2.5. User Roles .................................................................................................................................. 9
3. Flow Diagrams .......................................................................................................................... 10
3.1. Item Classification Flow ............................................................................................................. 10
3.2. Customer/Vendor Compliance Screening Flow............................................................................. 10
3.3. Sales Order Screening Flow ....................................................................................................... 12
3.4. Delivery Screening Flow ............................................................................................................ 13
3.5. Shipment Screening Flow .......................................................................................................... 13
3.6. Transportation Planning Flow ..................................................................................................... 15
3.7. Transportation Execution Flow ................................................................................................... 16
3.8. Freight Settlement Flow ............................................................................................................ 17
4. Integration Diagram .................................................................................................................. 18
5. Responsibility Matrix ................................................................................................................. 20
6. Project Approach ...................................................................................................................... 24
6.1. Prepare .................................................................................................................................... 24
6.2. Define – Global Design .............................................................................................................. 24
6.3. Build ...................................................................................................................................... 25
6.4. Testing ..................................................................................................................................... 25

6.4.1. End to End/Integration/Solution Testing ........................................................................... 26
6.4.2. Regression Testing .......................................................................................................... 26
6.4.3. Performance Testing ....................................................................................................... 26
6.4.4. User Acceptance Testing ................................................................................................. 26
6.5. End-User Training ..................................................................................................................... 26
6.6. Deployment .............................................................................................................................. 27
6.7. Post Go Live Production Support ................................................................................................ 27
7. Assumptions ............................................................................................................................. 27
7.1. Timelines .................................................................................................................................. 27
7.2. Project Documentation .............................................................................................................. 27
7.3. Project Facilities ........................................................................................................................ 28
7.4. Project Site ............................................................................................................................... 28
7.5. Inspirage Resource Location ...................................................................................................... 28
7.6. Resource Continuity .................................................................................................................. 28
7.7. Project Language ...................................................................................................................... 28
7.7.1. System Access ................................................................................................................ 29
7.7.2. System Security .............................................................................................................. 29
7.7.3. Oracle System Review ..................................................................................................... 29
7.7.4. System Performance ....................................................................................................... 29
7.7.5. Limitations ...................................................................................................................... 29
7.7.6. Third-Party Applications ................................................................................................... 29
7.7.7. Project Assumptions ........................................................................................................ 30
7.8. Cross-Process Activities ............................................................................................................. 30
7.8.1. Project Management & Governance ................................................................................. 30
7.8.1.1. Project Management Responsibilities ................................................................................ 30
7.8.1.2. Escalation ....................................................................................................................... 31
7.8.1.3. Decision Timeliness ......................................................................................................... 31
7.8.1.4. Risk Monitoring and Mitigation ......................................................................................... 31
8. Resources................................................................................................................................. 31
8.1. LOL and Inspirage Executive Leadership Team ........................................................................... 31
8.2. LOL and Inspirage Project Steering Committee ........................................................................... 32
8.3. Inspirage Resources .................................................................................................................. 32
8.3.1. Delivery Sponsor ............................................................................................................. 32
8.3.2. Functional/Project Lead ................................................................................................... 33
8.3.3. OTM Functional Consultant .............................................................................................. 33
8.3.4. Lead GTM Functional Consultant ...................................................................................... 33
8.3.5. Technical Lead Consultant ............................................................................................... 34
8.3.6. Technical Consultant ....................................................................................................... 34

8.4. LOL Resources .......................................................................................................................... 34
8.4.1. Executive Sponsors ......................................................................................................... 35
8.4.2. Program/Project Manager ................................................................................................ 35
8.4.3. Super User(s)/Business Project Manager .......................................................................... 35
8.4.4. Subject Matter Experts (SME) .......................................................................................... 36
8.4.5. Business Systems Analyst ................................................................................................ 36
8.4.6. Change Management Lead .............................................................................................. 36
8.4.7. Quality Assurance (Testing) Lead and Tester(s) ................................................................ 36
8.4.8. Enterprise Integration Architect ....................................................................................... 37
8.4.9. Integration Lead ............................................................................................................. 37
8.4.10. Integration Developer(s) ................................................................................................. 37
8.4.11. ERP Technical Lead and Developer(s) .............................................................................. 37
8.4.12. IT Delivery Manager(s) .................................................................................................... 38
9. Change Request/Change Order Process ...................................................................................... 38
9.1. Change Request Process ........................................................................................................... 38
9.2. Change Order Process ............................................................................................................... 39
10. Estimated Work Plan and Deliverables ........................................................................................ 40
10.1. High-Level Plan ......................................................................................................................... 40
10.2. Project Deliverables................................................................................................................... 40
10.2.1. Acceptance of Project Deliverables ................................................................................... 42
11. Investment ............................................................................................................................... 43
11.1. Terms ...................................................................................................................................... 43
11.2. Fees and Expenses.................................................................................................................... 43
12. Signatures and Acceptance ........................................................................................................ 44
Master Service Agreement

This Statement of Work ("SOW") dated 6/29/2018 (the "Effective Date”) is between Land O’Lakes, Inc.
(“Client”) and Inspirage, LLC (“Inspirage”), collectively referred herein as the “Parties”, and is being entered
into pursuant to and subject to the terms and conditions of the Master Services Agreement dated
5/12/2014, First Amendment dated 5/12/2016, Second Amendment dated 3/21/2018 (collectively the
“Agreement”) between Land O’ Lakes and Inspirage. In the event of any conflict between the terms of the
Agreement and this SOW, the provisions of this SOW shall control.
This agreement will be used as the binding document for scope, responsibilities, assumptions,
etc. Any documents previously shared between Land O’ Lakes Inc. and Inspirage are not
considered binding; however, they will be used by the solution team during the project as
appropriate.
1. Project Overview
Land O’ Lakes currently maintains OTM 6.2.7 on-premise for the Purina, Dairy, and Winfield
business units; each of these business units has its own separate JDE ERP system. There is
currently a completely manual transportation process for Nutra Blend using NetSuite. In
addition, for International shipments they use a combination of spreadsheets, access databases
and Amber Road to support Global Trade Compliance.
Inspirage has met multiple times with members of the Land O’ Lakes team to discuss migrating
their current OTM on-premise solution and their Global Trade Processes to the more modern
technology platform offered by Oracle Cloud. This Statement of Work reflects the scope,
approach, responsibilities and resource plan to provide consulting services in support of that
migration.
In moving to the latest cloud version of OTM/GTM the project team will purposefully not follow
a typical “lift-and-shift” approach as there are many opportunities to make substantial
improvements in business process and configuration, and to implement OTM Cloud and GTM
Cloud in a unified fashion. We will utilize the Global Design as well as Previous Health Check
research to determine overall project approach. The intent is to constrain changes in order to
limit the impact on existing integrations.
2. Scope
2.1. Overview
The move to the Cloud will provide an upgrade to Oracle’s most current technology.
This work shall be done in following Sequence:

1. Global Design for OTM and GTM for Dairy, Purina, Winfield and Nutra Blend
2. Migrate Dairy, Purina and Winfield to OTM Cloud and Implement GTM Cloud with staggered
testing and Go-Live
3. Implement Nutra-Blend OTM Cloud and GTM Cloud
2.2. Project Scope and Definition

This section describes the high-level scope of work for the overall project. The high-level scope
description within this section applies to the to-be OTM/GTM implementation for Dairy, Purina,
Winfield and Nutra Blend. Please note that all the scope information in this section is subject to
revision based on the global design phase.
2.2.1. Global Design Scope

The global design phase will produce a design document consisting of Visio process flow
diagrams and accompanying text descriptions describing the to-be end-to-end transportation
and global trade processes from functional and technical perspectives. The 7-week global
design phase will include:
 Business-unit-specific design sessions including gap analysis and proposed changes to workflow
agents
 Creation of draft design document – including development of process flows for To-Be Design
using the Trisotech BPMN template available to be downloaded and used within Visio for free.
 Design document review session
 Revision of draft design document to final document
 Final presentation
The global design document will provide information at a sufficient level of detail to direct
subsequent OTM/GTM configuration activities during the build phases. However, the global
design does not include detailed integration mapping which is completed during build phases.
Note: Global design will not document the as-is processes.
2.2.2. OTM/GTM Modules

OTM/GTM Modules to be implemented in the Oracle cloud include:
 Oracle Transportation Management (Core OTM)
 Operational Planning
 Freight Payment, Billing, and Claims
 Global Trade Management
 Trade Compliance
 Declarations Management
OTM/GTM Modules that will not be implemented as part of this project include:
 Fleet
 Sourcing
 Cooperative Routing
 Transportation Intelligence
 Global Trade Intelligence
2.2.3. Third Party Applications/Partners

Scope includes enabling the following Third-Party Applications
 Rateware
 PC Miler
 FourKites
 E2Open
 Descartes (Use determined based on results of global design)
 TradeWind Compliance (Use determined based on results of global design)
2.2.4. OTM Scope

OTM scope includes inbound and outbound transportation planning and execution of the
following types of shipments within the United States, Mexico and Canada:
 Truckload (TL)
 Less-than-truckload (LTL) shipments using common carriers
 Intermodal
 Parcel
 Rail
 Bulk
 CPU – Customer Pick-Up
 VMT – Vendor Managed Transportation
 Air
 International ocean container shipments via freight forwarder. Mindful of the potential goal of
elimination of Freight Forwarder.
2.2.5. Transportation Order Management

Inbound and outbound transportation requests originate upstream of OTM in the business-unit-
specific ERP systems including JDE and NetSuite. These are pushed to OTM via the LOL
integration layer, which transforms the transportation request data into OTM Order Release
data. The as-is process does not utilize the vendor “ready-to-ship” (RTS) process for inbound,
but we may determine as part of global design to change the to-be inbound process to utilize
RTS.
Additionally, the as-is process involves the so-called “rapid order entry” screen allowing
transportation requests to be entered directly into OTM via the OTM user interface. The to-be
process may preserve this ability to enter transportation requests directly into OTM for requests
having no upstream ERP representation This will be confirmed as part of the global design.
2.2.6. Transportation Planning

Scope for automated transportation planning involves selecting a set of order releases and
planning them into TL, LTL, and Ocean shipments having an assigned transportation mode and
common carrier which minimizes transportation cost subject to constraints.
The as-is planning process frequently involves labor-intensive and repetitive manual user
actions. These will be re-examined as part of global design with the goal of increasing
automation and reducing manual intervention.
2.2.7. Transportation Execution

Scope for transportation execution involves:
 The carrier tendering process to confirm the carrier assigned to each shipment,
 Communicating planned shipments back to the upstream ERP system to drive the pick/pack/ship
process,
 Communicating shipment actuals from the upstream ERP system back to OTM such that OTM has
accurate information required for freight settlement,
 Receiving electronic status messages from carriers such as “picked-up”,“delivered”, Location
Updates, and ETA Updates, and applying these messages to shipments to provide in-transit
visibility. ETA updates for subsequent stops will be re-calculated, and event generated out of
OTM.
 Existing Integration with FourKites and E2Open will continue to be used as in the current version.
E2open will no longer use LOL Integration layer, but direct integration.
2.2.8. Freight Settlement

Scope includes automated freight settlement whereby carriers send electronic invoices or paper
invoices to OTM or accounts payable, and OTM or accounts payable automates the match/pay
process, requiring human intervention on exceptions. This would also include the voucher from
OTM back to ERP’s.
2.3. GTM Scope

GTM scope includes:
 Item Classification
 Restricted Party and Sanctioned Country Screening
 License Determination and Management
 Document Determination and Management
 AES Filing
 The extent of use of 3rd party partners Descartes and Tradewind Compliance will be determined
during the Global Design
2.3.1. Item Classification

Global trade users will be enabled to leverage the GTM item classification workbench to assign
classification codes to items using classification data from Descartes. This would include
manually entering FTA Qualification status and user defined attributes/variables as needed.
2.3.2. Restricted Party and Sanctioned Country Screening

Using GTM will Automate the restricted party and sanctioned country screening process via
configured rules using black list data from Descartes.
2.3.3. License Determination and Management

Using GTM will automate the process of determining, assigning, and managing licenses for
global trade transactions via configured compliance rules.
2.3.4. Document Determination, Generation, and Management

Using GTM will automate the process of determining, generating, and managing documents for
global trade transactions via configured document determination rules.
2.3.5. AES Filing

Using GTM will automate the process of filing information with the U.S. Automated Export
System (AES) using the Descartes AES filing service.
2.4. Reporting
Scope for reporting includes operational reporting using BI Publisher. Fusion Transportation
Intelligence will not be used in this process. Reference the Responsibility Matrix for proposed
work breakdown for operational reporting. Real-time business intelligences will be explored
directly off the LOL Integration layer, with the potential to fallback to DB.XML in a batch mode
in a scheduled process.
2.5. User Roles

Scope includes configuration of OTM/GTM user roles which tailors the OTM/GTM user
experience depending on job responsibility. User roles configure the user’s menu, screens, and
permitted actions. The number of user roles will be confirmed during global design.
3. Flow Diagrams
“The following flows represent typical processes for the highlighted areas. These flows will be
reviewed during Global Design and are subject to change because of decisions made during the
design workshops”
Where you see “JDE” referenced in this section assume that means “JDE or NetSuite”.
Global Design will re-examine need for TradeWind FTA.
3.1. Item Classification Flow

The following diagram illustrates the high-level item classification flow:
Diagram description: Item creation or modification in JDE triggers Item Transformation in

Integration Layer resulting in Item creation or modification in OTM/GTM triggering Item
Classification Workflow. Item Classification workflow uses Descartes Item Classification Data
and TradeWinds FTA. The communication of bill-of-materials information from JDE to OTM/GTM
is not explicitly illustrated in this flow, however, we emphasize that bill-of-materials is in-scope
and will be accounted for as part of the implementation.
3.2. Customer/Vendor Compliance Screening Flow

The following diagram illustrates the customer/vendor compliance screening flow:
Diagram description: Customer creation or modification in JDE triggers integration layer

customer transformation resulting in creation or modification of contact in OTM/GTM which
triggers restricted party screening. If the contact is a restricted party, then activate a customer
hold.
3.3. Sales Order Screening Flow

The following diagram illustrates the sales order screening flow:
Diagram description: Sales order creation or modification in JDE triggers sales order
transformation resulting in creation or modification of trade transaction in OTM/GTM which
triggers compliance screening. If the transaction is non-compliant, activate a sales order hold
in JDE. Compliance screening uses Descartes restricted party data.
3.4. Delivery Screening Flow

The following diagram illustrates the delivery screening flow for the combined OTM/GTM
approach:
Diagram description: Delivery creation or modification in JDE triggers delivery transformation in

integration layer resulting in creation or modification of order release in OTM/GTM which results
in the creation of a trade transaction triggering compliance screening which conditionally results
in a delivery hold.
3.5. Shipment Screening Flow

The following diagram illustrates the shipment screening flow for the combined OTM/GTM
approach:
Diagram description: Pick/pack/ship JDE triggers Shipment Actuals Transformation in

integration layer resulting in shipment actuals update in OTM/GTM resulting in creation of a
trade transaction resulting in compliance screening. If the transaction is non-compliant it results
in a shipment hold, otherwise it triggers document determination and creation followed by the
AES workflow.
Diagram references TradeWind FTA. Global design will re-examine need for this service.
3.6. Transportation Planning Flow
Diagram Description: Delivery creation in ERP triggers order release creation in OTM/GTM
followed by bulk planning which creates planned shipment. Tendering workflow confirms
service provider assignment triggering shipment creation in ERP. Bulk planning uses external
distance and SMC rating engine. PC Miler 25 will be used for the distance engine.
3.7. Transportation Execution Flow
Diagram Description: Pick/Pack in ERP triggers shipment actuals update in OTM/GTM.

Shipment goes in-transit. FourKites or E2open pushes tracking event messages to OTM/GTM
triggering shipment status update. Carriers may also manually use the OTM Service Provider
and/ or corresponding mobile application to provide these shipment status updates.
3.8. Freight Settlement Flow
Diagram Description: Service provider pushes electronic invoice to OTM/GTM triggering invoice
match and approval processes resulting in creation of payment voucher pushed to financial
system authorizing payment to service provider.
4. Integration Diagram
The following diagram provides a high-level overview of the system integration for this project:
The following bullets reference the above diagram:

 There are four different ERP systems corresponding to the four different business units
 The LOL Integration Layer provides connectivity between
o ERP systems and OTM/GTM Cloud
o Service Providers (FourKites) and OTM/GTM Cloud
 E2open will leverage direct connections using HTTP external systems
 3rd Party software services communicate directly with OTM/GTM cloud
The following table enumerates the interfaces involved, subject to change based on global
design:
Interface Description
Item (4) There is an item interface for each of the 4 ERP systems
responsible for pushing item information from the ERP to
OTM/GTM
Location (4) There is a location interface for each of the 4 ERP
systems responsible for pushing location information
from the ERP to OTM/GTM
Order Release (4) There is an order release interface for each of the 4 ERP
systems responsible for pushing order release
information from the ERP to OTM/GTM
Global Trade Transaction (4) There may be a Global Trade Transaction interface for
each of the 4 ERP systems, subject to change based on
global design. There is an option for creating global
trade transactions from order releases and shipments
within OTM/GTM. However, there will likely be
requirements for screening in advance of transportation
planning, which will require these interfaces in addition

to the order release interfaces.
Global Trade Hold (4) There will be a Global Trade Hold interface for each of
the 4 ERP systems involved. When GTM determines that
a given involved party, order release, or shipment fails a
compliance rule, there is a hold placed in the
corresponding ERP system
Global Trade Remove Hold There will be a Global Trade Remove Hold interface for
(4) each of the 4 ERP systems involved. Removal of trade
transaction hold within GTM triggers removal of hold
within corresponding ERP system.
Planned Shipment (4) After transportation planning, OTM is responsible for
pushing planned shipments back to the corresponding
ERP system to drive pick/pack/ship. There is a planned
shipment integration for each ERP system.
Shipment Actuals (4) There is a shipment actual interface for each ERP
system. The shipment actual interface updates OTM
shipment information based on vehicle loading.
Truckload Tender Offer OTM pushes tender offer to TL service provider
Truckload Tender TL service provider accepts or rejects tender offer
Accept/Reject
Ocean Booking Electronic communication with Ocean freight forwarder
LTL Shipment Notification OTM pushes shipment notification to LTL service provider
Inbound Shipment Status Service provider (E2Open, FourKites) transmits shipment
status related information to OTM
Outbound Shipment Status OTM will generate ShipmentStatus to LOL status tracking
system (STAN, or JDE and NetSuite); this is especially
needed for Carrier entries into Service Provice portal or
OTM’s mobile application.
Invoice Servicer provider transmits electronic invoice to OTM for
freight settlement process
Allocation (4) OTM pushes cost allocation information to corresponding
ERP system
Voucher (4) OTM pushes payment voucher to corresponding ERP
system
Outbound Shipment This allows OTM to publish out ETA updates for
subsequent stops when a carrier event triggers ETAs to
be recalculated and updated.
Descartes There is an out-of-the-box interface between Descartes
and GTM for data required for item classification and
restricted party screening
Distance Engine There is an out-of-the-box interface between OTM and
the selected distance engine provider
SMC/Czar Lite There is an out-of-the-box interface between OTM and
SMC pertaining to LTL rating
FourKites FourKites transmits shipment status related information
to OTM
5. Responsibility Matrix
The following Matrix is an overall listing of the responsibilities associated with the project. This
is not designed to be a complete task list, but a listing by category and the team responsible.
‘LEAD’ is designed to communicate ownership of a task. In many if not most cases, Inspirage
and/or Land O’ Lakes will support these tasks as needed.
Task Inspirage LOL Comment

Environment
Acquire Oracle OTM/GTM cloud test and LEAD
production environments
Provide Inspirage with access to OTM/GTM LEAD LOL Oracle Cloud
cloud test and production environments Administrator is responsible
for this. See Project Team
Structure
Acquire all required 3rd party licenses such LEAD
as for distance engine, SMC, and Descartes
Acquire and install required SSL certificates LEAD
to permit communication between Oracle
cloud and LOL integration layer
Provide required 3rd party service license LEAD
credentials to Inspirage
Configuration of connectivity between LEAD Including documentation of
Oracle cloud and 3rd party services such as any key steps or
distance engine, SMC, E2Open and configurations that can be
Descartes shared with LOL
Project Management
Management of the Overall Project LEAD Inspirage functional lead
supports LOL project
manager
Publish and distribute weekly project status LEAD
report
Global Design
Provide detailed requirements during global LEAD
design sessions
Be prepared to make key design decisions LEAD
in a timely fashion during global design
phase
Create draft and final global design LEAD
document including Visio flow diagrams and
descriptions
Provide overall functional and technical LEAD Including documentation of
solution architecture any key steps or
configurations
General Division of Labor

Provide functional requirements pertaining LEAD
to Transportation and Global Trade
Provide required functional and technical LEAD Inspirage is not providing JDE
expertise pertaining to LOL ERP systems or NetSuite specific expertise
for this project
Responsibility for quality of data flowing LEAD
from ERP systems
Provide logical interface data maps to be LEAD This should include the ‘right-
used by LOL integration developers sizing’ of messages to support
Business Intelligence and
Operations, while minimizing
payload sizes for integration
over the Internet.
Provide expertise to handle ‘deleted’ LEAD Custom database triggers are
artifacts in OTM including withdrawn not available in Logistics
orders/ Order lines, and withdrawn/ deleted cloud.
shipments
Provide required technical expertise LEAD Applies to all integrations with
pertaining to building, testing, maintaining, OTM/GTM including with JDE
and troubleshooting LOL data integration instances, NetSuite, Carriers,
layer and all third-party software
services. LOL will be using
Mulesoft for these
integrations; Oracle FMW was
used for OTM 6.2.7 on-prem.
Provide required functional and technical LEAD
expertise pertaining to the configuration of
OTM and GTM
Provide CSV templates for loading of new LEAD
master data
Perform loading of new master data using LEAD
templates provided by Inspirage
Provide coaching and advice pertaining to LEAD
master data loading
Determination of which master data should LEAD
be transferred from on-premise to cloud
Actual transfer of existing master data from LEAD
on-premise to cloud based on LOL selection
Operational Report and Document LEAD
Development Using BI Publisher
General Overview of DB.XML for BI LEAD Need if we decide to use on-
Reporting needs prem OBI in scheduled mode.
Creation of Test Scripts LEAD
Identification of data and/or test LEAD Collaboration from Inspirage
transactions required to support testing will be included in this
process
Creation of data and/or test transactions to LEAD

support testing
Execution of Test Scripts LEAD
Execution of Load and Stress Testing LEAD
Systematic capture and reporting of defects LEAD
in configuration found during testing
Fixing reported defects in configuration LEAD
found during testing
Planning and executing performance testing LEAD
Managing any issues resulting from LEAD
performance testing
Security
Provide detailed requirements pertaining to LEAD
user roles, security, menus, and screen
configuration
Configuration of user roles LEAD
Item Classification
Configuration of item classification LEAD
workbench
Use item classification workbench to LEAD
classify items
Restricted Party Screening

Configure restricted party screening rules LEAD This will be done in
and workflow conjunction with LOL Project
Team
Provide template for importing of additional LEAD
blacklisted parties
Importing of additional blacklisted parties LEAD
using Inspirage-provided template
GTM License Determination

Provide specification, in functional terms, of LEAD
license determination rules
Provide template facilitating translation of LEAD
functional license determination rules into
GTM configuration
Use Inspirage-provided template to specify LEAD
actual GTM configuration pertaining to
license determination
Coaching of LOL Super-Users as part of LEAD
configuring GTM license determination rules
Configure workflow pertaining to license LEAD
determination
GTM Document Determination

Provide specification, in functional terms, of LEAD
document determination rules
Configure document determination rules LEAD
Configure workflow pertaining to document LEAD
determination
BI Publisher report development required to LEAD Inspirage is not providing BI
support document generation within GTM Publisher report developer for
this project
AES Filing
Configuration of GTM Declarations module LEAD
as part of AES filing
Auditing
Provide detailed requirements pertaining to LEAD
auditing
Configure GTM auditing feature LEAD
Transportation Planning
Configuration of Planning Parameters and LEAD
Itineraries
Provide rate loading templates LEAD
Loading of new rates using rate loading LEAD
templates
Configuration pertaining to selecting order LEAD
releases for planning
Configuration of transportation planning LEAD
workflow
Transportation Execution
Configuration of tendering workflow LEAD
Configuration of shipment status workflow LEAD
Overview of Multi-Leg Itinerary Planning LEAD
Freight Settlement
Configuration of Invoice Matching Rules LEAD
Configuration of Invoice Approval Rules LEAD
Configuration of Invoice Tolerance Rules LEAD
Configuration of Freight Settlement LEAD
Workflow
Training
On-the-job informal training of LOL Super LEAD
Users
Development and maintenance of overall LEAD
configuration blueprint document including
any configurations related to third party

applications as it pertains to the OTM/GTM
applications
Development of end-user training materials LEAD
Delivery of end-user training LEAD
Extensions
Provide functional specifications of any LEAD
customizations or extensions; to be
confirmed as part of global design
Provide custom code for any required LEAD
cloud-compatible customizations or
extensions at additional cost to be
determined (none determined at the time
of this writing)
Go-Live
Planning for go-live. Develop go-live check- LEAD
list
Provide advice and coaching pertaining to LEAD
go-live planning
Complete actual migration of OTM/GTM LEAD
configuration data from test to production
instances as part of go-live
Provide post-go-live support for a defined LEAD
duration
Change Management
Provide organizational change management LEAD
related to this project
6. Project Approach
The following is an overview of the project approach this Statement of Work is based on and
Project Tasks will be grouped by.
6.1. Prepare
The purpose of the prepare stage is to ensure that the system environment and project team
resources are ready when the full project begins. These activities will be completed by a small
Inspirage and LOL team.
• Pre-Project Checklist
• Prepare Project Kick-Off Presentation
6.2. Define – Global Design

The purpose of the define stage is to define the requirements for the overall solution.
Inspirage will lead requirements and design efforts relating to OTM/GTM.
• Audit the as-is process - comprehensive review of LOL use of OTM and GTM processes
• Identify cloud-incompatibilities
• Define the to-be process
• Design of cloud-incompatibility mitigations
• End-to-End process redesign for Dairy, Winfield and Purina
• End-to-End process design for Nutra Blend
• Define/Finalize approach to upgrade and migrate on-prem configurations to cloud
6.3. Build
The purpose of the build stage is to configure the components of the solution as documented in
the define stage. This includes performing configuration, loading master data, performing
integration configuration/development, and creating operational reports. LOL will complete unit
testing for those pieces of the build for which it has lead responsibility, and Inspirage completes
unit testing for its part of the build for which it has lead responsibility.
Inspirage will lead all configuration efforts including;
OTM
• Upgrade and migrate on-prem configuration to cloud - upgrade configuration to latest

version of OTM/GTM
• Mixture of automated and manual processes
• Upgrade and migrate on-prem master data to cloud (Transform for new design as
necessary)
• Configure redesign for Dairy, Purina, Winfield
• Configure design for Nutra Blend
• Configure cloud-incompatibility mitigations
• Update interface mapping changes to make cloud compatible
• Validate integration data mapping to support all third-party applications
• Configure workflow between OTM and GTM
GTM
 Configure workflow between OTM and GTM
 Configure item classification
 Configure restricted party and sanctioned country screening
 Configure license determination and management
 Configure document determination and management
 Configure AES Filing
6.4. Testing
The purpose of the Testing stage is to test the complete solution to ensure that it meets the
requirements specified in the Design stage. This stage includes solution testing (also called
“End to End” or “Integration” testing), regression testing, performance testing, and user
acceptance testing.
6.4.1. End to End/Integration/Solution Testing

During the testing stage, as mentioned above in build phase, various integrations as well as
other configurations will need to be adjusted to make the solution cloud compatible. The
purpose of the End to End testing is to test these changes to ensure all are working as
designed. End-to-end testing will be led by LOL and supported by Inspirage.
6.4.2. Regression Testing

LOL will conduct regression testing for the processes that were not expecting any change as
part of the project. This testing will be executed and managed by LOL. However, if any issues
are encountered because of this project resolutions will be managed jointly by Inspirage and
LOL
6.4.3. Performance Testing

During the build stage, every effort will be made to configure, develop, and load master data in
a way that will meet system performance requirements. The purpose of performance testing is
to validate the performance is acceptable for go-live and make performance tuning adjustments
as necessary. The steps for performance testing will be as follows:
• Define performance benchmarks; these will be defined during global design
• Determine whether system performance meets benchmarks
• Identify bottleneck areas if applicable
• Tune the system as necessary to meet benchmarks
Performance Testing will be led by LOL and supported by Inspirage.
6.4.4. User Acceptance Testing

User Acceptance Testing (UAT) occurs after performance testing and is focused on validating
usability and functionality of the solution as per the approved solution design. UAT is a
streamlined version of the solution testing effort, using actual end users as the testers, focusing
on how the system fits into their daily activities. LOL will be responsible for the UAT execution,
with support from Inspirage. UAT scripts will be scaled-back versions of the solution testing
scripts. LOL will be responsible for defining test scripts and rectifying issues for all on-premise
non-OTM/GTM applications. Inspirage will correct components for which it is responsible.
User Acceptance Testing will be led by LOL and supported by Inspirage.
6.5. End-User Training

End-User training will ensure that the identified LOL core team members are effectively trained
in the use of systems to drive success. While On-the-job informal training of LOL Super Users
will be done by Inspirage; this project will employ a train-the-trainer approach to support the
delivery of the system training. LOL core team members will create the needed OTM/GTM
training content. LOL core team members will be responsible to deliver training to identified end
users as required.
End-User training will be led by LOL and supported by Inspirage.
6.6. Deployment
The Deploy stage is where the solution goes live. Activities will include
• Super User Training – Led by Inspirage as described in the responsibility matrix and
supported by LOL
• Upgrade and Migrate On-Prem In-Flight Transactions to Cloud (Similar to config –
Transform to new design as necessary) – Led by LOL and supported by Inspirage. Based
on outcome of Global Design.
• Go-Live in the following sequence (Led by LOL and supported by Inspirage):
• Dairy OTM + GTM
• Purina OTM + GTM
• Winfield OTM + GTM
• Nutra Blend OTM + GTM
6.7. Post Go Live Production Support

Inspirage will provide 4 weeks of post Go-Live hypercare support for the project. The purpose
of this stage is to stabilize the solution post go-live and provide support as required. This could
include fixes for defects or requests for additional documentation.
7. Assumptions
7.1. Timelines
LOL is responsible for overall PMO activity, and as such, will own responsibility of managing all
participant deliverables in support of the timeline and budget. As part of the final Project Plan
created during the define phase, milestone dependencies will be documented, and
responsibilities assigned. Inspirage project lead will provide notification of risks in this area and
work with the LOL Program Manager for risk mitigation. Any delays outside of Inspirage control
could result in change order, or project extension. Inspirage project lead will work with the LOL
Project Manager to mitigate that risk.
7.2. Project Documentation

Inspirage will provide documentation throughout the project as it relates to project
administration during OTM/GTM solution design, and OTM/GTM configuration. Inspirage created
documentation will use Inspirage documentation conventions. Inspirage-created documentation
is limited to what has been called out in this statement of work. LOL will be responsible for
developing all other documentation (e.g., Standard Operating Procedures). All project
documentation will be stored on a dedicated Project SharePoint site. Task details will be
monitored and managed using VSTS.
7.3. Project Facilities

Facilities will be made available to the Inspirage team. Facilities include but are not limited to
the following: network infrastructure, telephone, access to meeting rooms, projectors, white
boards, printers, and photocopying machines.
If LOL requires on-site consultants to use LOL laptops, they will be ready prior to the start of
the project.
7.4. Project Site

The project site is the primary location where the project team can meet during the on-site
activities. This will enable the project team’s immediate access to LOL documents, key
personnel, and systems. The primary project site will be LOL corporate office located;
4001 Lexington Avenue
Building A
Arden Hills, MN
Additional project locations may be necessary for deployment activities or site visits. Work will
be completed remotely when possible to reduce travel costs.
7.5. Inspirage Resource Location

The Inspirage team will operate both onsite and offsite.
US based project team members will observe normal project work days as Monday to Thursday
when traveling on site. The project team will be available on Fridays for meetings and
completing project-related deliverables.
During offsite activities, Inspirage can use its infrastructure or LOL infrastructure for web
conferencing to facilitate all project discussions in a timely and effective manner.
7.6. Resource Continuity

If LOL postpones the project at any point longer than a 4-week period, Inspirage may not be
able maintain resource continuity, and there may be costs associated with transitioning
resources.
7.7. Project Language

English will be used at conversational level during project discussions.
English will be the primary language for the project documentation. Any translation required to
other languages is the responsibility of LOL.
English will be used as the language within OTM.

7.7.1. System Access

Connectivity to OTM will be direct through the network at all physical locations of LOL.
On site and remote access to OTM/GTM will be made available to Inspirage consultants. This
includes access to all environments. This access must be granted to resources prior to resources
first day on the project to avoid any delays.
7.7.2. System Security

LOL will be responsible for network and overall IT security for the production system and will
implement anti-hacking measures and other measures to prevent data theft.
7.7.3. Oracle System Review

Inspirage will work directly with Oracle and its subsidiaries as needed to support Oracle Service
and System Requirements as determined by Oracle Policies and System Review.
7.7.4. System Performance

OTM/GTM performance is affected by many variables, including hardware, platforms,
infrastructure, networks, integration approach, integrated system performance, configuration,
and customer expectations among others. While Inspirage will configure OTM/GTM with
performance in mind, it is not able to commit to a specific level of OTM performance.
7.7.5. Limitations
Inspirage will not be responsible for bugs or gaps in OTM/GTM or any third-party provided
software; however, it will work with LOL to log such issues with Oracle or the third-party
provider to help LOL resolve them in a timely manner. Delays to the project caused by software
bugs or gaps may trigger a change order.
7.7.6. Third-Party Applications

LOL will be responsible for obtaining/maintaining licenses for required third-party applications
as well as hosting as appropriate. During the design and build stage, Inspirage and LOL will
identify the need for OTM related 3rd party software and will configure OTM to connect to these
applications, assuming the applications are OTM-certified. These programs may include, but
are not limited to, the following:
• PC*Miler
• PCMiler Rail if applicable
• Here or ALK (mapping software)
• FourKites
• Rateware
• E2Open
• Descartes
• Tradewind
7.7.7. Project Assumptions

• Scope changes are limited by agreed-upon timeline/cost as outlined previously
• In Flight transaction data only will be migrated to OTM Cloud or via detailed design the project team
may opt instead for a strategy of overlapping the on-premise and cloud instances while the on-
premise instance is drained of inflight transactions.
• It is probable that a small number of SaaS incompatible customizations will be discovered during the
audit performed by Inspirage. As part of the audit, we will identify which of these customizations can
be covered with Cloud configuration. No specific customizations or extensions have been identified at
this time.
• OTM will be hosted in the Oracle Cloud. Standard functionality will be utilized; if customizations are
required, a change request will be triggered accordingly.
• Inspirage’ Rapid Value methodology and project templates will be utilized where appropriate
• Integration with OTM/GTM will be achieved using standard XML.
• Inspirage will support the integration effort by leading interface mapping meetings, creating
translation spreadsheets, and supporting testing efforts.
• LOL will own any carrier partner integration program communication, onboarding, and testing efforts.
• Inspirage resources will operate both onsite and offsite based on the project schedule and
milestones. During offsite activities, Inspirage will operate in the project’s time zone as necessary and
use its own infrastructure around web conferencing to facilitate project discussions. The Inspirage
team will be onsite for critical phases of the project
• The primary project location will be in the Continental United States. Inspirage will travel to other
facilities as necessary for effective project execution.
• English will be used at conversational level during project discussions. Project documentation will be
completed in English. OTM/GTM will be branded to use other supported languages as necessary.
• All travel is anticipated to the project/workshop location only – if other locations need to be included,
it is assumed they will have representatives that will meet centrally for project workshops. Inspirage
has a global presence and can support additional countries if required with additional resources.
• Commencing the training material development is subject to completion of design phase
• LOL will be responsible for ensuring deliverables provided by Inspirage are converted to LOL
corporate standards where required.
7.8. Cross-Process Activities

The following section outlines the project activities that span business processes.
7.8.1. Project Management & Governance
7.8.1.1. Project Management Responsibilities

The Inspirage Solution Architect/Project Lead will be responsible for the overall Inspirage
deliverables and management of Inspirage resources as discussed in the Responsibility Matrix.
The LOL Program Manager has overall responsibility which includes any internal escalations as
required to support the project and monitoring the entire project budget and timelines. Both the
Inspirage and LOL Project Lead will work closely together throughout the project.
7.8.1.2. Escalation
If the core LOL and Inspirage teams cannot agree on intended scope or any other area relating
to the project, an escalation process will be initiated, whereby the issue will be elevated to the
Steering Committee to make the final decision. The team leaders will work together to
document the issue and co-present the issue to the Steering Committee.
7.8.1.3. Decision Timeliness

Inspirage and LOL will work closely to ensure that project is delivered within the time line and
contain the scope as agreed upon in the solution document. To keep the project on track,
timely decisions must be made.
The turnaround time for decision-making by the LOL team for all critical matters (issues
impacting the budget or timeline) relating to the project is no more than 2 business days. For
all other decisions, the turnaround time is no more than 4 business days unless otherwise
agreed to by the project managers. If a decision cannot be made within this timeframe and it
is perceived to impact the project timeline, it will be escalated to the Steering Committee for a
decision to be made.
7.8.1.4. Risk Monitoring and Mitigation

Several areas of risk apply to this project. Some examples of risk factors are as follows:
• Data availability
• Data quality
• Lack of focus or involvement on the project from users
• Lack of leadership / sponsorship to provide project vision, priorities, and decisions
• Inability to make timely decisions
• LOL or 3rd party system availability
• Instance stability
• Product gaps
• Integration gaps
• Lack of follow through by change agents/management to change management activities
• And many others
The Inspirage and LOL Project Manager(s) will communicate known risks and issues and
recommend steps to mitigate the issues as part of the structured project reporting.
8. Resources
The following sections provide details on the roles associated with the project.
8.1. LOL and Inspirage Executive Leadership Team

The Executive Leadership team is responsible for building, maintaining, and strengthening the
partnership between LOL and Inspirage. This team will meet on an as needed basis, either in
person or via conference call to discuss project progress, review & resolve any issues, and set a
path to strengthen the partnership. This may entail quarterly calls during the project. After
which, meeting frequency may be adjusted based on project status. This team is responsible
for aligning LOL and Inspirage strategic project direction.
8.2. LOL and Inspirage Project Steering Committee

A project Steering Committee will consist of representation from LOL and Inspirage. This team
has the following responsibilities:
• Acts as point of escalation of issues that require decisions to be made.
• Manages issues and risks brought forward by the project managers
• Ensures that resources are assigned the project
• Approves project approach and methodology
• Reviews and provides approval on any requested scope changes
• Resolves matters relating to project scope, cost, time, issues and risk
• Provides the strategic influence on the rest of the organization and all stakeholders.
• Supports and champions the project for all stakeholders
A monthly meeting is recommended for this team. There may be times where more frequent or
ad-hoc meetings are required.
8.3. Inspirage Resources

Below are the roles that Inspirage will be providing as a part of this agreement.
Inspirage will do its best to provide resource continuity throughout the project. Excepting
instances out of its control (e.g., termination of employment), Inspirage will not remove a
resource from this engagement without permission from LOL. If a resource needs to be
replaced, Inspirage will attempt to replace the resource with another resource of similar skill
level. The parties will agree to a reasonable knowledge transfer and transition plan to an
equivalently qualified resource, knowledge transfer and handover period. This period shall be
not more than two weeks. The cost of knowledge transfer (e.g. reviewing documentation,
familiarization with LOL objectives) shall be the responsibility of Inspirage. Inspirage will use
reasonable effort to maintain the initially agreed project timings.
In addition, if resources are replaced at the request of LOL, the parties will agree to a
reasonable knowledge transfer and transition plan to appropriately qualified resources. The
cost of knowledge transfer shall be the responsibility of LOL with the exception of situations
where both parties have agreed there is a performance issue and in such case the cost of
knowledge transfer shall be the responsibility of the Inspirage.
8.3.1. Delivery Sponsor

Inspirage will designate one or more Delivery Sponsors. Responsibilities of this role are
as follows:
• Inspirage project champion
• Acts as executive contact point for the equivalent LOL executive sponsors
• Participates in Steering Committee meetings
The Delivery Sponsor is provided to LOL at no “additional” charge.
8.3.2. Functional/Project Lead

Inspirage will provide one Solution Architect/Project Lead. Responsibilities of this role
are as follows:
• Provides overall project leadership, direction, and, focus as it pertains to Inspirage resources
and project responsibilities
• Works with the LOL Project Manager to control scope, manage risks, manage timeline and
manage budget
• Responsible for making sure all the work assigned to Inspirage is completed on time per the
project plan
• Manage the portions of the project plan belonging to Inspirage
• Presents to the Steering Committee on a regular basis and escalates issues as needed.
• Leads roadmap stage
• Assists the LOL Project Manager with all project governance activities
• Provides documented weekly status report
• Provides overall guidance on the functional and technical design
• Leads the functional aspects of OTM design, solution definition, and documentation
• Provides functional expertise and knowledge to LOL
• Provides guidance to functional consultants
• Performs ongoing quality audits
• Supports test script creation, issue resolution, testing, post go-live support, and transitioning
the system to LOL
8.3.3. OTM Functional Consultant

Inspirage will provide one OTM Functional Consultant. Responsibilities of this role are as
follows:
• Configures the functional aspects of OTM as defined in the solution documentation
• Performs OTM functional troubleshooting during build, test & support
• Assists Inspirage Solution Architect/Lead with configuration documentation
• Support LOL on loading master data
• Provides configuration & solution overview used in the creation of test scripts
• Provides go-live support
• Provides functional system transition to LOL
8.3.4. Lead GTM Functional Consultant

Inspirage will provide one GTM Lead Consultant. Responsibilities of this role are as follows:
 Leads the GTM functional and technical configuration tasks
 Participates in the to-be design sessions
 Creates configuration for restricted party screening, sanctioned country screening, license
determination, etc.
 Supports testing activities
 Supports the creation of the test scripts and training material
 Provides go-live support

 Provides functional system transition to LOL
8.3.5. Technical Lead Consultant

Inspirage will provide one Technical Lead. Responsibilities of this role are as follows:
• Leads the technical aspects of OTM design, solution definition, and documentation
• Provides 777technical expertise and knowledge to LOL
• Provides guidance to technical consultants
• Performs OTM data migration from on-premise to cloud
• Performs ongoing quality audits.
• Performs Technical Consultant responsibilities as required
• Leads OTM-related interface mapping discussions and create interface mapping spreadsheets
• Participates with interface testing
• Configures the technical aspects of OTM as defined in the solution documentation
• Performs OTM technical troubleshooting during build, test & support
• Supports test script creation, issue resolution, testing, post go-live support, and transitioning
the system to LOL
• Provides technical solution and configuration insight to help LOL build test scripts
• Resolves OTM related testing issues
• Supports training preparations
• Supports the pilot go-live and deployment, and transitioning the system
• Supports system analysis & tuning
8.3.6. Technical Consultant

Inspirage will provide one Technical Consultant. Responsibilities of this role are as follows:
 Creates CSV master data import templates
 Creates business monitors
 Creates workflow automation agents
 Creates security profiles
 Assists in troubleshooting testing
 Conducts performance tuning
 Configuration required to enable Descartes integration
 Identifies and resolves technical configuration issues
 Mentors client resources in GTM technical functionality
 Participates in detailed design discussions
 Assists in troubleshooting issues with interfaces
8.4. LOL Resources

Below are the roles that LOL is expected to provide as a part of this project. Agreed upon roles
are critical and must be filled. Unfilled roles, or inadequate resource commitment will lead to
project delays and ultimately a change order for a timeline extension. This section provides
information that supplements the Project Team Diagram presented earlier in this document.
Each identified role is not necessarily a single resource; some roles can be filled by a single
resource, and some roles may require multiple resources. This at the discretion of LOL as
required by the project plan and timeline.
8.4.1. Executive Sponsors

LOL will designate one or more Executive Sponsor to the project. Responsibilities of this role
are as follows:
 Guides overall success of the project and the larger program
 Acts as the project champion within the executive steering committee
 Acts as the contact point for the equivalent Inspirage sponsors to meet on specific project
discussions.
 Additional resources acting in executive roles are welcomed. The executive sponsor will act as
the final decision-maker relating to the project and program.
8.4.2. Program/Project Manager

LOL will assign a single Program/Project Manager to the project. Responsibilities of this role are
as follows:
 Provide overall program and project leadership to maintain project continuity and timeline
 Works with the Inspirage Project Manager to create the overall project plan
 Manage all non-Inspirage Resources as required by the project plan and overall timeline
 Manage the non-OTM portions of the project plan
 Controls overall project scope and manages risks
 Monitors overall project timeline and budget
 Ensures that all the work assigned to LOL in the project plan is completed per the plan
 Presents project status in the Steering Committee meetings
 Escalates issues to the Steering Committee as needed
8.4.3. Super User(s)/Business Project Manager

LOL will assign at least one full-time Super User(s)/Business Project Manager to the project for
both the OTM and GTM Tracks. Responsibilities of this role are as follows:
 Acts as the primary contact for the OTM/GTM solution
 Contributes as needed during the configuration for clarifications on design and to make decisions
on configuration options. To the extent they are available, the super user is encouraged to take
part in the configuration of OTM/GTM, as it supports their on-going training of OTM/GTM
 Plays an active role in the various testing cycles throughout the project
 Acts as the key point of contact for level 1 support after the project go-live
 May also act as Change Agent and/or Training Lead
 Gathers, cleanses, and loads non-integrated master data (carriers, rates, equipment, etc.) into
OTM, both initially and on an ongoing basis after go-live; may require coordination with OTM
Support and Analytics team
 Inspirage will work with this role and will support the master data loading process.
8.4.4. Subject Matter Experts (SME)

LOL will assign one or more part-time Subject Matter Experts to the project. Responsibilities of
this role are as follows:
 Provides business-related guidance to the solution team throughout all stages of the project.
 Participate in design workshops and testing efforts as needed
8.4.5. Business Systems Analyst

LOL will assign one or more part-time Business Systems Analysts to the project.
Responsibilities of this role are as follows:
 Works with the Inspirage Technical Analyst to identify any changes that need to be done within
LOL systems to make the interfaces and/or other processes work per the design documentation
 Creates documentation relating to process changes within LOL systems
 Elicits and documents requirements for overall project
 Designs, documents, and coordinates the development of changes required in LOL systems
 Coordinates training relating to process changes within LOL systems
 Tests changes required in LOL systems
 Works with the Inspirage Technical Analyst and Technical Lead for integration mapping
 Acts as the liaison between the requirements for integrations and integration architect and
developers
 Learns the technical configurations within OTM and GTM cloud
8.4.6. Change Management Lead

LOL will assign one or more part-time Change Management Leads to the project.
 Develops Change Management plan
 Assists in creating and delivering communications to identified stakeholders based on direction
from Program/Project Manager
 Assists in Development of end-user training content
 Assists in delivering training to any LOL end-users not trained with the Core Team in the
fundamentals of OTM/GTM working with the Technical Team to create a training template.
 Coordinates training events in conjunction with Inspirage as required (e.g. logistics, invites etc.)
 Establishes training best practices that will be used as a benchmark to facilitate all workshops &
training sessions
8.4.7. Quality Assurance (Testing) Lead and Tester(s)

LOL will assign a full time Quality Assurance (Testing) Lead and Tester(s) to the project.
 Oversee all testing activities for this project; coordinate with appropriate resources
 Ensure testing coverage for all requirements; create test scripts and repository of scripts
 Where possible automate test scripts and supporting processes
 Execute identified test scripts per project plan
 Report all test failures and log associated defects; communicate with developers; complete
retests as needed
8.4.8. Enterprise Integration Architect

LOL will assign a part-time Enterprise Integration Architect to the project. Responsibilities of
 Help create the solution architecture based on outputs from the global design sessions
 Rationalize solution with the Enterprise Architect to ensure we are addressing business objectives
 Work with OAGi to ensure our enterprise /experience APIs address needs, and feature
enhancements for Semantic Refinement Tool (SRT)
 Mentor Integration Lead on Semantic Refinement Tool for rapid creation of standard APIs
 Assist with data mappings as needed
 Participate in code reviews
8.4.9. Integration Lead

LOL will assign a part-time Integration Lead to the project. Responsibilities of this role are as
follows:
 Completes the development of integration design specifications to and from multiple systems per
global design
 Coordinate with offshore Integration Developer resources
 Communicate status of development efforts
 Assist with data mappings as needed
 Support testing phase of project, coordinating with JDEdwards Business Systems Analysts and
Developers as necessary
8.4.10. Integration Developer(s)

LOL will assign a part-time Integration Architect and one or more Integration Developers to the
project. Responsibilities of this role are as follows:
 Completes the development of integrations to and from multiple systems per global design
 Validates integration development by completing unit testing
 Supports testing phase of project including bug fixing
8.4.11. ERP Technical Lead and Developer(s)

LOL will assign one or more part-time Subject Matter Experts to the project. Responsibilities of
 Creates technical designs and supporting documentation based on requirements and functional
designs provided by BSA
 Completes the development of changes required in LOL ERP systems
 Validates development by completing unit testing
 Supports testing phase of project including bug fixing
8.4.12. IT Delivery Manager(s)

LOL will assign a part-time Technical Infrastructure Owner to the project. Responsibilities of
 Procures any hardware/software needed to support the OTM/GTM solution (i.e. PC Miler, etc. as
listed the Third-Party Applications Section) with support from BSA and IT Procurement
o Business System Analysts and Program Manager may instead be used to support this
activity
9. Change Request/Change Order Process

The LOL and Inspirage Project Managers will work together to control deviations from this
agreement. When potential deviations are identified, they will be evaluated via the change
request process. If a change request is deemed necessary and it is approved, and it affects the
scope, costs, timeline, or resources of the project, a change order will be executed to update
this agreement.
9.1. Change Request Process

Upon identification of a potential change, Inspirage will collaborate with LOL to ensure that the
change is indeed required and to determine high-level impact. The considerations when
evaluating a change request are:
• Ensuring that the agreed-upon scope and process is well understood
• Evaluation of alternate systems and business processes that still achieve the same end goal
without making the change
• Cost / Benefit analysis
A change request may be initiated for the following:

• Timeliness of LOL or Inspirage deliverables
• Timeliness of LOL or Inspirage decision making
• Lack of Business Quality Data
• Change in Scope (Not Scoped)
• Change in Timeline
• Oracle product defects
• Impact considerations of other IT projects, including the current OTM implementation
Inspirage and LOL will determine the appropriate mechanism for communicating a change
request. Change requests will be documented and may require formal approval with electronic
signatures.
A change request will be disposed of in one of the following manners:

1. Unapproved: Change request will be archived for future reference. No further action.
2. Approved, no impact to project resourcing, costs, or timeline: Documentation will be
updated, and change will be accommodated.
3. Approved with impacts to project resourcing, costs, or timeline: Change order process will
be executed. See below.
It is important to limit the amount of time spent evaluating change requests. It is possible that
significant time spent evaluating change requests may lead to a change order.
Changes to this SOW will be managed through the procedure described in Change Order
Process section. This may result in adjustments to the Project Scope, Estimated Schedule,
Charges and other terms. These adjustments may include charges for any resulting additional
work or waiting time on a time and materials basis using the rates in Fees and Expenses
section. However, Inspirage will notify LOL of these charges in advance and obtain written
approval of such charges. If an assumption deviation is not resolved through Project Change
Control Procedure, then the issue will be resolved in accordance with the Escalation Procedure.
9.2. Change Order Process

1. Either party may propose changes to the scope, nature or time schedule of the services
being performed under this SOW. The party requesting the change order will inform the
other party’s Project Manager of a change order, specifying the additional functionality,
services, resources, or timeline required. This change order shall be submitted in writing.
2. The party shall promptly evaluate and provide a written response to each change order. The
written response shall include:
a. A description of the change required
b. A statement of availability of Inspirage personnel to support the change
c. The time frame or duration for the change
d. The estimated cost to LOL. The rate card in this statement of work will be used to
calculate change order costs.
e. The estimated impact on the project schedule
3. If the parties will mutually agree to the proposed changes:
a. Inspirage will create a change order amendment to this agreement outlining the
impact of the change.
b. Each signed change order shall constitute a formal modification to this agreement
and will be affected through a written amendment signed by both parties.
c. Documentation will be updated, and change will be accommodated.
In no event shall the scope, specifications, resources, costs, or timeline as defined in this
proposal be deemed altered, amended, enhanced, or otherwise modified, except through a
mutually agreed upon written change order executed by an authorized agent of both parties.
10. Estimated Work Plan and Deliverables
10.1. High-Level Plan

Below is a high-level timeline for the deployment of OTM/GTM. The detailed project plan will
be drafted during the Prepare Phase and finalized after design is complete.
M1 M2 M3 M4 M5 M6 M7 M8 M9 M10 M11 M12 M13 M14 M15 M16 M17 M18 M19
Sept Oct Nov Dec Jan Feb Mar April May June July Aug Sept Oct Nov Dec Jan Feb Mar
Global Design 1 1
Dairy,
Purina, WNFLD
Build 1 1 1 1 1 1
Test
IT Testing 1 1
Dairy 1 1
Purina 1 1
WNFLD 1 1
Deploy
Dairy 1 1
Purina 1 1
WNFLD 1 1
PROD SUPPORT
Post Go-LiveSupport 1 1 1 1
Nutra Blend
Build 1 1 1
Test 1 1
Deploy 1
PROD SUPPORT
Post Go-LiveSupport 1 1
10.2. Project Deliverables

Deliverables in this document are guidelines to confirm the team is managing to timeline
constraints defined in the project plan. Please note that the deliverables listed herein are not
tied to payments for services rendered. The below table is an outline of the deliverable
schedule. Project plan dates in the prepare phase will override dates as listed in the table
below.
Del# Deliverable Stage Acceptance

Week
1 Prepare documents Prepare In August
 Project charter
 Project plan
2 Define Completion – Global Design Define W7

 Detailed future state process flow
 Integration mapping specs
Dairy, Purina and Winfield

3 Configuration & Unit Test Build W33
 Updated design documentation (Detailed process flows,
configuration guide, integration mapping specs, master
data guide)
 Updated Integration mapping specs
4 Testing Test
 Completion of solution testing Dairy W36
 Completion of user acceptance testing Purina W40
 Updated design documentation (Detailed process flows, Winfield W44
data guide)
5 Production Support (Inspirage Responsibilities) Deploy

 Support of LOL Business and IT in managing through Dairy W37
issues that may arise. This would include interface as well Purina W41
as functional issues Winfield W45
6 Rollout Transition Support Post W48

 Knowledge transfer and transition as required to LOL Go-Live
Support Team (Timing to be determined by LOL and Support
Inspirage Project Management Team
Nutra Blend
7 Configuration & Unit Test Build W56
Configuration guide, integration mapping specs, Master
Data Guide)
8 Testing Test W60

 Completion of solution testing
 Completion of user acceptance testing
data guide)
9 Production Support Deploy W69
10 Rollout Transition Support Post W70

 Knowledge transfer and transition as required to LOL Go-Live
Support Team (Timing to be determined by LOL and Support
Inspirage Project Management Team)
We expect the entire engagement will last 74 weeks from start to finish (this includes a
shutdown of the project during year end in December 2019). Various sections of the project to
share some overlap. Please see the detail below:
• Prepare
• Define – Global Design – 7 weeks
• Dairy, Purina, Winfield
• Support of Integration “Jump Start” period – 8 weeks
• Build – 18 weeks
• Test – 20 weeks
• Deploy – 13 weeks
• Go Live Support – 4 weeks
• Nutra Blend
• Support of Integration “Jump Start” period – 9 weeks
• Build – 12 weeks
• Test – 8 weeks
• Deploy – 5 weeks
• Go Live Support – 4 weeks
Below are key project dates: Dates are dependent on completion of the commercial agreement.
The dates below are illustrative only. Some dates may be adjusted based on outcomes of
global design
• Prepare start: Week of 08/13/2018
• Project start: TBD – Expected Start Week 09/17/2018
• Dairy Go-Live: TBD - Expected Go-Live Week 05/27/2019
• Purina Go-Live: TBD - Expected Go-Live Week 06/24/2019
• Winfield Go-Live: TBD - Expected Go-Live Week 07/22/2019
• Nutra Blend Go-Live: TBD - Expected Go-Live Week 01/20/2020
• Project End: TBD – Expected Project End Week 02/21/2020
Inspirage will deliver project status reports every week. Each report will include:
 Key accomplishments in that period
 Upcoming activities for the next period
 Issue/risks/watch-outs with due dates and mitigation plans – this should be all-inclusive on
all aspects of project, whether it is schedule delays, resource problems, normal project
operational issues, etc.
 Upcoming milestones
 Phase-wise deliverables status updates
 Site status updates
10.2.1. Acceptance of Project Deliverables

When Inspirage delivers a deliverable, LOL will have the opportunity to review the deliverable
for an acceptance period of 10 calendar days (the “Acceptance Period”). Acceptance of the
deliverable will take place on the Acceptance Date, which will be the first date on which any of
the following events occurs:(a) LOL provides Inspirage written notice of acceptance; or, (b); or,
(c) the Acceptance Period expires without LOL having given Inspirage written notice of any
failure to substantially conform to applicable specifications described herein (“Defect”). If LOL
delivers to Inspirage a timely notice of Defects and Inspirage agrees that the items specified in
the notice are Defects, Inspirage will correct the described Defects in a timely manner. After
redelivery, the parties shall again follow the acceptance procedures set forth in this Section.
Inspirage and LOL each agree to work diligently to achieve acceptance of a deliverable at the
earliest possible date, subject to the acts and omissions of applicable third-party licensors, and
LOL will work diligently to put the deliverable in live production operations.
11. Investment
11.1. Terms
This is a Time and Materials engagement.
• Consulting costs will be billed on a bi-weekly basis, as hours are consumed.
• Inspirage will adhere to the LOL Travel Policy. Travel related expenditures will adhere to
Section 3 of the Agreement and fees will be capped at a maximum of twelve percent (12%)
of the total project cost.
• Inspirage resources will be expected to enter their time worked on the project on a weekly
basis in Clarity our project management tool. Time sheets are due by noon on Fridays. On
weeks where the end of the month falls there will be the requirement to submit two
timesheets.
• Any applicable taxes are not included in the costs below and will be invoiced as an additional
line item.
• Payment terms are Net 30.
11.2. Fees and Expenses

The following rate and estimated hours by resources were used to come up with the total
investment required. As the project progresses, some of the resource hours could vary to
support the needs of the project. The Inspirage Project lead and LOL project manager will work
together to best balance the appropriate resources within the overall budget constraint.
Days Hours Group Skill Level/Position Currency Rate/Hr. Total

185 1,480 NA Logistics Project Manager/OTM Functional USD $185 $273,800
185 1,480 NA Logistics OTM Functional Lead USD $185 $273,800
320 2,560 NA Logistics OTM Technical Lead USD $185 $473,600
150 1,200 IN Logistics OTM Technical Consultant USD $100 $120,000
185 1,480 NA Logistics GTM Functional Lead USD $185 $273,800
150 1,200 IN Logistics GTM Functional Consultant USD $100 $120,000
1175 9,400 USD $1,535,000
12. Signatures and Acceptance

"BILL TO" ADDRESS
CUSTOMER NAME & BILLING ADDRESS (If different from address at left)
Name LAND O'LAKES, INC Facility

Address 4001 Lexington Ave N Address
City Arden Hills, MN 55126-2998 City
Country USA Country

Attention: TBD Phone: Attention: Phone:
Agreement (MSA) No. Customer Project Anticipated Anticipated
Purchase Number Commencement Completion
Order Number Date Date
Dated 09/10/2018 01/13/2020
LAND O'LAKES, INC Project Manager/Phone
#
LAND O'LAKES, INC Project Sponsor/Phone

#
LAND O'LAKES, INC Sponsor/Phone #
Consultant Engagement Manager/Phone #
Consultant Executive Sponsor
Services/Deliverables (“Work”) to be provided Work Rate

Units
(Per the appended Statement of Work/high-level Project per Unit Services
Plan): (Hours) (Hr.) (USD) (A)
Project Manager/OTM Functional 1,480 $185

$273,800
OTM Functional Lead 1,480 $185
$273,800
OTM Technical Lead 2,560 $185
$473,600
OTM Technical Consultant 1,200 $100
$120,000
GTM Functional Lead 1,480 $185
$273,800
GTM Functional Consultant 1,200 $100
$120,000
TOTAL Services
(B) Expense Estimate (will be billed at actual incurred) $1,535,000
(A) Prices are estimated in US Dollars; applicable taxes are extra.

(B) Travel expenses are not included in the rates and are listed on a separate line.
Travel expenses will be billed in actual. Inspirage will follow LOL Travel Policies and
make a very sincere effort to keep expenses to a minimum including working remotely
when possible and in alignment with program/project on-site needs.
(C) Rates are time and material.
(D) Invoices are to be emailed to <apinvoices@landolakes.com> on a weekly basis and
will reference Land O’ Lakes Purchase Order number
(E) Invoices submitted for reimbursement of expenses are to be itemized for actual
costs/expenses incurred.
(F) Payment Terms are Net 30
AGREED: LAND O'LAKES, INC ACCEPTED: Inspirage
By____________________________________ By __________________________
Jorge Garcia
Name _________________________________ Name _Marc Marshall___________
Sr. Sourcing Director
Title __________________________________ Title __VP Business Development_
8/27/2018 | 8:34 AM CDT 8/27/2018 | 7:04 AM PDT
Date __________________________________ Date ________________________

Land O Lakes Inspirage OTM-GTM Cloud SOW 2018-06-27 V11 PDF

Uploaded by

Document Information

Original Description:

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

Land O Lakes Inspirage OTM-GTM Cloud SOW 2018-06-27 V11 PDF

Uploaded by

Copyright:

Available Formats

DocuSign Envelope ID: A910E0EE-1809-4912-AEDC-75A0BEC80746

Date Submitted: 29 – June -2018

Revised 21 – August - 2018

6.4. Testing ..................................................................................................................................... 25

8.3.6. Technical Consultant ....................................................................................................... 34

Master Service Agreement

This work shall be done in following Sequence:

2.2. Project Scope and Definition

2.2.1. Global Design Scope

Note: Global design will not document the as-is processes.

2.2.2. OTM/GTM Modules

2.2.3. Third Party Applications/Partners

2.2.4. OTM Scope

2.2.5. Transportation Order Management

2.2.6. Transportation Planning

2.2.7. Transportation Execution

2.2.8. Freight Settlement

2.3. GTM Scope

2.3.1. Item Classification

2.3.2. Restricted Party and Sanctioned Country Screening

2.3.3. License Determination and Management

2.3.4. Document Determination, Generation, and Management

2.3.5. AES Filing

2.5. User Roles

Global Design will re-examine need for TradeWind FTA.

3.1. Item Classification Flow

Diagram description: Item creation or modification in JDE triggers Item Transformation in

3.2. Customer/Vendor Compliance Screening Flow

Diagram description: Customer creation or modification in JDE triggers integration layer

3.3. Sales Order Screening Flow

3.4. Delivery Screening Flow

Diagram description: Delivery creation or modification in JDE triggers delivery transformation in

3.5. Shipment Screening Flow

Diagram description: Pick/pack/ship JDE triggers Shipment Actuals Transformation in

3.6. Transportation Planning Flow

3.7. Transportation Execution Flow

Diagram Description: Pick/Pack in ERP triggers shipment actuals update in OTM/GTM.

3.8. Freight Settlement Flow

The following bullets reference the above diagram:

planning, which will require these interfaces in addition

Task Inspirage LOL Comment

General Division of Labor

Creation of data and/or test transactions to LEAD

Restricted Party Screening

GTM License Determination

GTM Document Determination

any configurations related to third party

6.2. Define – Global Design

Inspirage will lead requirements and design efforts relating to OTM/GTM.

Inspirage will lead all configuration efforts including;

• Upgrade and migrate on-prem configuration to cloud - upgrade configuration to latest

6.4.1. End to End/Integration/Solution Testing

6.4.2. Regression Testing

6.4.3. Performance Testing

Performance Testing will be led by LOL and supported by Inspirage.

6.4.4. User Acceptance Testing

User Acceptance Testing will be led by LOL and supported by Inspirage.

6.5. End-User Training

End-User training will be led by LOL and supported by Inspirage.

6.7. Post Go Live Production Support

7.2. Project Documentation

7.3. Project Facilities