Why does Swift have two different System Service Agreements (SSA)?

Swift provides unique feature workflows based on customer profiles (i.e. carrier versus shipper) and, therefore, necessitates different SSA Agreements based on how customers interact within Swift.

Why are there two SSAs?

In today's current solutions, two SSAs (which outline the agreements and procedures within Swift) exist. 

Do I need to sign both SSA documents? 

    • YES: IF your business both stores or moves products along the ONEOK refined fuel pipeline and uses their own carriers to load at ONEOK refined fuel terminals.
    • NO: IF your business does only one of the above. The table below shows high-level differences between the Refined Fuel and Carrier SSA.

What are the differences between the two SSAs?

  • The table below shows high-level differences between the Refined Fuel and Carrier SSA.

Area

Refined Fuel Customer

Dispatch

Customer Segment

Refiner, Shipper, Inventory Owner, Supplier

Carrier

Legacy Applications

ATLAS

None

New Applications

Swift

Swift Dispatch

Onboarding Process

Portal, Customer Profile, ATLAS/Swift

Portal, Carrier App, Swift

SSA

SSA (core version, e-signed through Customer Profile app)

SSA (carrier version, e-signed through Carrier app)

Pricing

System Services price list

(for Refined Products or Crude)

Pricing is not set - all services are currently free

Insurance Requirements

None

Certificate of Insurance (COI) - Auto, Excess Umbrella, General Liability, Workers Compensation

APIs

Swift Complementary (Billing, Locations)
Swift+ (Loading, Shipping, Inventory)

Carrier BOL (PPU, In Beta)

General Terms & Condition

IRS 637, System Services selection, ACH Debit, Credit Check, SSA (refined fuels version)

Carrier Access Agreement, COI (insurance), SSA (carrier version)