Objectives

1. Improve accuracy and efficiency in the general freight despatching process.

2. Standardize integration output from Customer system.

3. Enable more advanced reporting to enable analysis such as accurate association of freight cost to orders.

Components

• Customer System

Customer's system used as the source system for order data. Provider order data is exportable into an EDI file that will act as a data feed to the Message Transmitter process

• Customer Workstation

Customer uses their consigning workstations to access the OneFlo portal to be able to access OneFlo functionality. 

• OneFlo Portal

OneFlo is a cloud based, multi-carrier, Logistics Management System designed for consigning, manifesting & tracking consignments, tracking carrier performance & enabling logistics-based reports for analyzing supply chain activity. Order Lookup is accessed via the OneFlo Portal.

• OneFlo Order Integration Service

The Order Integration service (Installing Order Lookup) is designed to increase the efficiency of the despatch process by identifying and loading order data based on EDI files. The service identifies order EDI files and loads the contents as an order into OneFlo. Once loaded the order is accessible in the OneFlo portal and upon selecting the order all order data is mapped to the consignment creation form. The population of this data reduces data entry required by the despatch teams and increases accuracy of the consignment data.

• OneFlo Postback Report

In order to populate consignment number against the original Order in efm a OneFlo Postback data file can be generated on a nightly schedule. This data file will be transferred over to Customer where a efm service will load the file data to update Orders. This function requires Customer to nominate an FTP server that OneFlo can use to place the nightly batch file.

Information Requirements

Customer order data required may vary depending on the process the Order Lookup integration is intended to achieve.

The following specification defines an XML structure for the Order Detail. When the source system can only produce a CSV, please consult the efm Technical Solutions Contact assigned.

Order Detail Information

Address Type Information

Item Type Information

Example Files

XML

<OrderData xmlns:xsd="http://www.w3.org/2001/XMLSchema">
	<OrderDetail>
		<OrderReference>3081973</OrderReference>
		<Service>IPECX</Service>
		<References>
			<Reference>ExtraReference</Reference>
		</References>
		<Receiver>
			<Name>Receiver Name</Name>
			<Address1>89 Koala St</Address1>
			<Locality>Footscray</Locality>
			<State>VIC</State>
			<Postcode>3011</Postcode>
			<ContactName>Receiver Contact</ContactName>
			<ContactPhone>+6134567890</ContactPhone>
		</Receiver>
		<Items>
			<Code>CA25SP</Code>
			<Length>0.280</Length>
			<Width>0.280</Width>
			<Height>0.090</Height>
			<Weight>1.544</Weight>
			<Description>Box of Nails</Description>
		</Items>
	</OrderDetail>
</OrderData>