Project44 Carrier Aggregator

Project44 provides a direct pass-through to Carrier APIs for LTL quoting, tendering, tracking, and document retrieval. For Project44 tracking see the Project44 tracking API article. Project44 provides users the ability to complete the following actions.

• Get LTL Carrier Quotes.

• Tender to LTL Carriers.

• Load Tracking Visibility.

• Document Retrieval.

• Support for Hazardous Materials quoting and tendering.

Project44 provides “push” status updates to the TMS via a sites-based web service. Inbound LTL load status packets are processed as Platform Events. Starting or stopping Project44 LTL load tracking sends outbound packets that are processed by the QueuedTransactionJob.

Setup

Enter Credentials

Enable the Project44 integration by completing the following steps.

1. Navigate to TMS Admin.

2. Select Credentials. 

3. Select the Global Services tab.

4. Find Project44 in the list and open the card. 

5. Check the Enabled and Receive Updates boxes.

6. Enter the User ID and Password 1 into the text fields. 

7. Click the Save button when finished.

Valid credentials are required from a Project44 subscription. See examples in the table below.

Inbound Packet IP Ranges: Any post-backs from Project44 that do not originate from this IP mask are rejected as a security feature. Any changes to this range are provided by Revenova.

Navigate to TMS Admin, Configuration and confirm the Use Platform Events For boxes are checked for Project44, Project44 Tracking, and Project44 Unified Tracking.

Remote Site Settings

Upgrading from previous versions of the TMS may have outdated information. Check that the Remote Site Settings for the Project44 integration URL are up to date.

There are TWO remote site settings required. One for the API and one for the BOL document URL.

1. Click the Setup gear icon in the top right corner.

2. From the drop-down, click Setup.

3. In the Quick Find Toolbar type Remote Site Settings and click the link.

4. From the list of remote sites find Project44 and click the Edit link.

5. Update the Remote Site URL to match the Service URL below: 

   1. Service URL: https://na12.api.project44.com 

   2. Test Service URL: https://na12.api.sandbox.p-44.com

6. Request from Project44 what customer-specific URL documents are available from and add it as a Remote Site Setting. 

   1. It is in a format such as: https://prod-44742-images.s3.amazonaws.com.

Partner Community Setup

Project44 relies on a “push” approach to event processing, and requires a webhook to send information to the TMS. Create an API Site to accept inbound API traffic.

1. Create a Salesforce Site for API Guest User Access.

2. Set the public access for the Site.

3. Activate and Publish the Site.

4. Enter the API URL into the field for Inbound API Community URL under TMS Admin, in the Configuration section. 

5. Add the following extension to the end of the URL to match the example below: /services/apexrest/rtms/tmslistener?org=00D180000008oA9EAI&source=Project44&pwd=4wGFDgnT950Ovg1

6. Send the post-back URL, the customer company name and contact info to support.americas@project44.com.

Project44 LTL Tracking webhook:

{API Community URL} /services/apexrest/rtms/tmslistener?org= {18-character org id} &source=Project44&pwd= {credentials code field}

Example: https://revenova.my.site.com/api/services/apexrest/rtms/tmslistener?org=00D180000008oA9EAI&source=Project44&pwd=4wGFDgnT950Ovg1

The Salesforce-generated API Community URL is case sensitive.

Project44 Setup

Navigate to the Project44 website and log in.

1. Enter the Carrier credentials for each Carrier to quote/tender.

   Warning:

   To properly tender, track, and manage documents with Carriers, the following information must be configured correctly.

   1. All Carrier credentials are present and correct. Billing information for the Carrier must also be correct.

   2. Account login groups are configured correctly. Blank values are acceptable when not using login groups.

   3. The SCAC fields in the Project44 portal should match the SCAC fields on the Carrier Transportation Profile.

      1. When entering a Capacity Provider Account Code field, do NOT enter a dash (-) between the SCAC Code and Reference Number. Enter a an underscore (_) between the values so the TMS can parse the values.

   The following error displays if a Carrier is not enabled correctly in the Project44 website:

   

2. For customer-specific pricing:

   1. Create a Login Group for each customer.

   2. Populate the customer-specific credentials for each Login Group.

   3. Copy the Carrier API Login Group field from Project44 into the customer Transportation Profile (in the TMS, on the Rates tab)  with the Login Group Key.

   4. Project44 supports a login group cascade concept. This allows for defining two login groups and setting the Carrier API Login Group field at both the customer and default Transportation Profile levels. When quotes are retrieved from Project44, two queries are made - one with each login group. Any quotes received from the first query are masked out of the second query.

   5. Configure Carrier Pickup Notes on the Project44 website to prevent tenders from failing. (Note could be too long).

3. Multiple contracts for a given capacity provider can be set up by providing unique names in the Project44 portal.

4. See the Project44 Tracking article for additional tracking setup in the Project44 website (Reference Data Keys).

Other Setup

1. A Bill of Lading Number is NOT generated by Project44. The BOL # is generated and passed from the TMS during the tender operation.

2. A Bill of Lading Number must be present to use the Truckload load tracking API.

3. Load status API calls may return signed BOL and POD images.

Notes:

• The default Tracking Provider for a Carrier is selected on the Carrier's Transportation Profile on the  Settings tab.

• Only tracking integrations with credentials display as possible options in the Tracking Provider picklist.

• Select Project44 as the default Tracking Provider for tracking LTL Mode loads.

• The Project44 integration only supports 2 Stop Loads. If more than 2 Stop locations are included on a Load, no information returns.

• Project44 LTL tracking does not support the same location for Pickup and Delivery Stops. If the same location is used as a Pickup and Delivery, users receive an error.

TMS Admin

Carrier Services

The following settings under TMS Admin → Carrier Services control when a PRO Number is generated.

Warning: Create 1 Carrier Service per SCAC/Transportation Profile, Mode, and API Provider (Project44). Rates do not return from Project44 If multiple Carrier Services are created for the same SCAC and Mode.

Pickup Only: Check the Pickup Only box on Project44 Carrier Services to not immediately generate a PRO Number. If the PRO Number changes later in the load lifecycle the tracking data will be invalid.

If requesting quotes with the TMS Web Service, it is possible to override the timeout period with the LTL API Timeout Override (Seconds) field in TMS Admin → Configuration. This field only applies when quoting through Project44 with the Revenova Web Service.

SMC3 Quoting + Project44 Tender/Track/Images

You may set up hybrid API carrier services that use SMC3 for quoting and Project44 for tendering, tracking, and image retrieval. These Carrier Services should be set up with the SMC3 RateWare Credentials Id.

Integration Calls

Troubleshoot mismatched Carrier Quotes and Rate Entries with the following components.

• API Quote Audit Log (Quotes)

• Load Match Test (Rate Entries)

LTL Quotes Request

Carrier quotes returned from Project44 contain the laneType in the response that is stored in the Direct/Interline field. Filter out Carrier quotes returned from Project44 in the Customer Portal by setting the Portal Quote Direct/Interline Filter field on the Transportation Profile.

Request Quotes in a Specific Currency

Project44 supports quoting in the following currencies.

• USD

• CAD

• MXN

• EUR

Add the Carrier Quote Preferred Currency field to the Load TMS1 field set to select a preferred currency when creating Loads. If no currency is selected, the User default currency is included.

Single currency orgs do not include the Carrier Quote Preferred Currency field when requesting quotes from Project44.

Tender Load Request

The Create a Shipment Request sends the Load, Stop, and other relevant information to the Carrier in the Tender request.

Each Carrier Quote returned from the Rate Quote Query Response contains a unique ID that is stored in the Carrier Quote Reference field. This field is included in the request.

The following logic determines the information sent to Project44 for Pickup or Delivery Instructions in the request.

• When First and Last Stop Instructions fields and Pickup/Delivery Number fields all contain values, the following is sent in the request.

  • “(Instructions) - PU#: (Pickup/Delivery Number)” is sent in the pickupNote element.

  • “(Instructions) - Dlvy#: (Pickup/Delivery Number)” is sent in the deliveryNote element.

• When no Instructions field(s) contain values, the following is sent in the request.

  • “PU#: Pickup/Delivery Number”

  • “Dlvy#: Pickup/Delivery Number”

• When both First and Last Stop location Instructions and Pickup/Delivery Number fields contain no values, the pickupNote and deliveryNote elements are not included in the request.

Hazmat Loads Tendered via Project44 require a value for the HazMat Packaging Group field. Add None as a picklist value to send no value.

TMS Fields Included in Create a Shipment Request

*Requestor Location Address fields are based on the user performing the actions that trigger the API call to Project44.

• Internal requests performed by TMS users sends the User address fields.

• Customer Portal requests send the Carrier Account owner address fields.

  • If no Carrier Account Owner fields are populated on the Load, the First Stop Account location address fields on the Load are sent.

**Requestor Contact fields are based on the user performing the actions that trigger the API call to Project44.

• Internal requests performed by TMS users sends the internal user contact information.

• Customer Portal requests send the Carrier Account owner Contact fields.

***Shipment Identifiers are sent if a Value exists for a Load in the TMS. The Type fields sent are hard-coded by the TMS based on the existing Values.

If there is no colon in the Carrier Quote Reference field, the SCAC is sent as the capacityProviderAccountGroup code.

HazMat Contact Information

• The HazMat Contact Company Name is first sent from the Line Item HazMat Contact Account Name. If no value exists, the First Stop Location Account Contact Company Name with the HazMat role is sent.

• The HazMat Contact Contact Name is first sent from the Line Item HazMat Contact Name. If no value exists, the First Stop Location Account Contact Name with the HazMat role is sent.

• The HazMat Contact Phone Number is first sent from the Line Item HazMat Contact. If no value exists, the First Stop Location Account Contact with the HazMat role Phone Number is sent.

• The HazMat Contact Email is first sent from the Line Item HazMat Contact. If no value exists, the First Stop Location Account Contact with the HazMat role Email is sent.

• The HazMat Contact Fax is first sent from the Line Item HazMat Contact. If no value exists, the First Stop Location Account Contact with the HazMat role Fax Number is sent.

Sample Create a Shipment Request Payload

{
  "accessorialServices": [
    {}
  ],
  "apiConfiguration": {
    "allowUnsupportedAccessorials": true,
    "enableUnitConversion": true,
    "fallBackToDefaultAccountGroup": true,
    "noteConfiguration": {},
    "pickupOnly": true,
    "preScheduledPickup": true
  },
  "capacityProviderAccountGroup": {
    "code": "string",
    "accounts": []
  },
  "capacityProviderQuoteNumber": "string",
  "carrierCode": "string",
  "currencyCode": "USD",
  "customsInfo": {
    "customsBrokerLocation": {}
  },
  "deliveryNote": "string",
  "deliveryWindow": {
    "date": "2019-08-24",
    "startTime": "15:00",
    "endTime": "17:00"
  },
  "destinationInvolvedParties": [
    {}
  ],
  "destinationLocation": {
    "address": {},
    "contact": {}
  },
  "directionOverride": "SHIPPER",
  "emergencyContact": {
    "companyName": "string",
    "contactName": "string",
    "phoneNumber": "string",
    "phoneNumberCountryCode": "string",
    "phoneNumber2": "string",
    "phoneNumber2CountryCode": "string",
    "email": "string",
    "faxNumber": "string",
    "faxNumberCountryCode": "string"
  },
  "enhancedHandlingUnits": [
    {}
  ],
  "handlingUnitTypeQuantities": [
    {}
  ],
  "lengthUnit": "IN",
  "lineItems": [
    {}
  ],
  "originInvolvedParties": [
    {}
  ],
  "originLocation": {
    "address": {},
    "contact": {}
  },
  "paymentTermsOverride": "PREPAID",
  "pickupNote": "string",
  "pickupWindow": {
    "date": "2019-08-24",
    "startTime": "15:00",
    "endTime": "17:00"
  },
  "requesterLocation": {
    "address": {},
    "contact": {}
  },
  "shipmentIdentifiers": [
    {}
  ],
  "totalHandlingUnits": 0,
  "totalLinearFeet": 0,
  "weightUnit": "LB"
}

Sample Create a Shipment Response Payload

{
  "id": 674543219,
  "infoMessages": [
    {}
  ],
  "shipmentIdentifiers": [
    {}
  ]
}

TMS Field Updates