QIVA High Performance Global Supply Chains Corporate Overview April 14, 2018

Order Object Example – Shipment Summary Order Objects: Purchase Order/ Sales Order/ Quote Shipment/ASN Transport/BOL All order object screens have a similar appearance with differences around functions specific to each order type such as packing, releases. Items such as references, locations, parties, products, etc. can be added as required both manually and electronically. Qiva has been profitable for 10 out of 12 years Languages supported include: English Spanish French Italian Dutch Portuguese Danish Norwegian Swedish Flemish Finish

Order Object Example – Shipment: Products Order Summary: Purchase Order/ Sales Order/ Quote Shipment/ASN Transport/BOL Each order type has a series of screens that define the creation/edit process for the order that are viewable in a summary view as seen in the Shipment Summary example.

Order Object Example – Shipment: Packing Order Packing: Shipment level packing details are part of the shipment order object and can be captured electronically or manually as seen in the Packing screen. Products from an order are packed into groups defined by the user for conveyance. Line level references can be associated to the packing information such as serial or lot numbers, providing users the ability to track goods by an individual reference level.

Event Plan Example – Shipment Event Plan Event Plans: Event plans are an aggregate view across events that have been associated together to define workflow of processes, milestones, etc. for order objects and independent processes. Event plans serve as the basis of workflow creation, exception management, and tracking. The Event Plan to the right is representative of the types of events someone would use for a track and trace view.

Event Template Example - Summary Screen Event Plan Templates: Events can be associated and stored as an event plan template that is available for reuse by new order objects as either an original or updated event plan. The example screen is a summary view of an Event Plan Template with definition, use conditions, and applicable events. When an order/shipment arrives in the system, the template match engine applies the appropriate Event plan and schedules expected event dates and times for the shipment life-cycle.

Rate Contract Example – Summary Screen Contract Management: Contract Management allows users to maintain their contracted carrier rates and routing instructions for use in shipment booking and routing and transport creation. The contract contains the basic terms and conditions of the contract, trade lane definition, rates, and rate filters.

Rate Contract Example – Edit Lanes Screen Contract Management – Lane Maintenance: Contracts are divided by lanes, which represent actual lanes, shipping zones, and point to point lane definition. Each lane is then defined by details about the lane such as equipment, transit time, commodity, and rate. Depending on the mode of transportation the details describing the lane change to match mode and service type.

Rate Contract Example – Lane Rate Screen Contract Management – Rate Maintenance: Contract rates allow for the capture of both the base rate and any accessorials that may apply to the contract, which vary by mode. Contracts support multi currency requirements and various transit times.

Rate Inquiry Example – Rate Search Screen Qiva’s rate inquiry or rating process provides users with the ability to enter an origin and destination and then rate the shipment across all contracts available for that origin and destination pairing as defined by the contract lanes. This allows users to compare rates across all modes utilized in a single view without having to use multiple systems to determine the best rate usage.

Rate Inquiry Example – Query Results Screen The results from the rate inquiry are presented on-screen according to the filters applied to the query. Users can then select the rate desired and either view the contract or execute the shipment directly from this screen through the related task window to the right.

Route Guide Example – Summary Screen Route Guide Management: Routing guide includes a set of business rules corresponding to service level, lanes (origin destination pairs) and weight/cube set by Customer to ensure that the proper contracted carrier and service level is applied to a Transport Order prior to booking & tendering of shipments. Users are provided with a ranking of acceptable carriers for each transport order.

Booking Example – Request: Summary Screen Booking Request: The booking request and confirmation orders serve the specific purpose of request and confirmation for service and space across all modes of transportation.

Order Object Example – Transport Order: Summary Screen Transport Order Example The transport order serves as the order type that describes the method of conveyance such as a AWB, MBL, HBL, etc. The order supports the required specific references, parties, locations, charges, etc required by the various modes of conveyance.

Report Example – Sample of Generic Logistics Reports Reporting and alert mechanisms are supported by the Microstrategy 7i suite, providing users with a robust report writer and data analysis tool. The example screen is part of the master menu for standard logistics reports available to users. Super users have the ability to create, generate, distribute, and download reports based on metadata available to the user.