1. To Do
1.1. Cross Reference Service
1.1.1. MDM
1.2. Order Management
1.3. Inventory Service
2. ideas
2.1. Could we use AI to populate many of these data elements and keep them up to date?
2.2. Being the clearinghouse for fuel freight
2.2.1. add a funding option (carrier gets paid in 1 day for a fee)
2.3. Establishing the "index" fair price for freight for every OD pair in the US
3. Use Cases
3.1. Inventory Readings
3.2. Orders
3.2.1. Load Tender
3.2.1.1. Fuel Orders
3.2.1.1.1. site
3.2.1.1.2. products
3.2.1.1.3. source
3.2.1.1.4. prices
3.2.1.1.5. counterparty
3.2.1.1.6. carrier
3.2.2. Load Updates
3.2.2.1. schedule
3.2.2.1.1. eta
3.2.2.2. driver
3.2.2.3. asset
3.2.2.4. BOL
3.2.2.4.1. BOL #
3.2.2.4.2. Supplier
3.2.2.4.3. products
3.2.2.4.4. time
3.2.3. Load Closure
3.2.3.1. drop date/time
3.2.3.2. drop products/qty
3.2.3.3. assessorials
3.3. Prices/Cost
3.3.1. rack price
3.3.2. spot prices
3.3.2.1. opis, argus, platts
3.3.2.2. nymex, cbot
3.3.3. build database over time
3.3.3.1. normalize and compare
3.4. Invoices
3.5. Allocations?
3.6. TelaPoint Integration
3.7. Gravitate to Gravitate
3.8. Carrier Capacity
4. Stakeholders
4.1. Suppliers
4.1.1. with shipper designation
4.2. Carriers
4.2.1. SCAC
4.3. Retailers
4.4. Wholesalers
4.4.1. dealers
4.5. Customers
4.5.1. site owners
4.6. Brands
4.6.1. jobbers
4.7. Terminal owners
5. Downstreat Fuel Supply Chain Digital Twin Cross Referencing
5.1. Future
5.1.1. model the entire fuel supply chain
5.1.2. Retail Price
5.1.2.1. sources
5.1.2.1.1. gasbuddy
5.1.2.1.2. WEX
5.1.2.1.3. web scraping
5.1.2.2. Over time
5.1.2.2.1. correlations
5.1.2.2.2. forecast of prices
5.2. Universal Standard
5.2.1. Supply
5.2.1.1. Suppliers/Sellers by Rack
5.2.1.2. Available Products
5.2.1.2.1. dsl
5.2.1.2.2. gas
5.2.1.2.3. other
5.2.1.3. carding
5.2.1.3.1. requirements
5.2.1.3.2. carded drivers
5.2.1.4. trailer/tank certifications
5.2.1.5. other information
5.2.1.5.1. wait times
5.2.1.5.2. planned and unplanned outages
5.2.1.6. transactions
5.2.1.6.1. BOL's
5.2.1.6.2. allocations, shipments, storage
5.2.1.6.3. TAS integration?
5.2.2. Current Standards
5.2.2.1. Conexxus
5.2.2.2. DTN
5.2.2.3. Opis
5.3. 150,000 US Sites
6. Data Elements
6.1. Sites
6.1.1. Owner
6.1.1.1. record owner
6.1.2. location
6.1.2.1. address
6.1.2.1.1. geo location (and fence)
6.1.3. meta data
6.1.3.1. sharing, permissions
6.1.4. federal site ID?
6.1.5. status
6.1.5.1. open, closed, transitioning
6.1.6. tanks
6.2. Tanks
6.2.1. tank number (ATG)
6.2.2. federal list
6.2.2.1. Federal ID?
6.2.3. sizes
6.2.3.1. 20k
6.2.4. charts
6.2.4.1. master list
6.2.4.2. deminsions
6.2.5. brand
6.2.5.1. unbranded
6.2.5.2. Shell, Chevron, etc
6.2.6. Owner
6.2.7. products
6.2.7.1. 87E10
6.2.8. meta data
6.2.8.1. Access
6.2.8.2. sharing
6.2.9. status
6.2.9.1. open, closed, transitioning
6.3. Terminal
6.3.1. Terminal Geolocation. Geofence (polygon)
6.3.2. TCN - federal unique id
6.3.3. Terminal Owner
6.3.3.1. pipeline system
6.3.3.2. refinery source
6.3.4. TAS
6.3.5. Suppliers
6.3.6. Products
6.3.7. Loading codes
6.3.7.1. prices
6.4. Carriers
6.4.1. trucks
6.4.2. trailers
6.4.3. drivers
6.4.3.1. safety records
6.4.3.2. carding
6.4.3.3. licenses and certifications
6.5. Tenants
6.5.1. Carriers
6.5.2. Retailer
6.5.3. Wholesaler
6.6. Counterparties
7. Transactional Data
7.1. inventory levels
7.1.1. ATG make/model
7.1.2. sources
7.1.2.1. direct (agent)
7.1.2.2. acumera
7.1.2.3. titan, etc
7.1.3. sales
7.1.3.1. forecast
7.1.4. build database over time
7.1.4.1. normalize and compare
7.2. Loading
7.2.1. Supply Prices
7.2.1.1. $1.00
7.2.1.1.1. Counter Party
7.2.1.1.2. Product
7.2.1.1.3. Supplier
7.2.1.1.4. Terminal
7.2.1.1.5. Type
7.2.1.1.6. Contract
7.2.1.2. $2.00
7.2.1.2.1. Secondary Options
7.2.2. Loading Code
7.2.2.1. Marathon
7.2.2.2. FW Terminal
7.2.2.3. Supply Type
7.2.2.3.1. Contract
7.2.2.4. Contract
7.2.2.4.1. Number or Name
7.2.2.4.2. Day Deal
7.2.2.5. Product
7.2.2.5.1. NL
7.2.2.6. Required Fields
7.2.2.6.1. Minimum
7.2.2.6.2. Other