Please enable JavaScript.
Coggle requires JavaScript to display documents.
Baker Hughes Integration FRD - Coggle Diagram
Baker Hughes
Integration FRD
Schedules
Schedules (BH) ==> Routes (Omnitracs)
Schedules (Routes) data must be pushed to BH MiddleWare component
Data from TD's (Orders)
that must be included
in push requests
Well API Number
Well (Service Location) data
TD frequency
Product Code
Plan date
Plan Quantity
Route data should be pushed when has been Dispatched
Treatment Definition
Treatment Definition (BH) ==> Order (Omnitracs)
TD will contain
data for the following
entities
Orders (Treatment Definitions)
Service Locations (Well locations)
Trucks
Drivers
Possible operations
considered in a TD
record
Create - Applies to
Order
Drivers
Service Locations
Trucks
Update - Applies to
Service Locations
Flag for "Downhole" or "Above Surface" TDs
Frequence: once per day
Order identifier in RNA will be: TreatmentID + Date logic (Start Date) == (Schedule ID)
All core data (Well locations, drivers, trucks) will be identified by ther TTS ID. This ID will be used as identifier per each related entity in RNA
Service Confirmation
Service Confirmation (BH) ==> Stops
Moments a Service Confirmation
must be pushed to MiddleWare
component
Stop is completed (TREATED)
Stop is cancelled (EXCEPTION)
Data to be pushed
Driver Name
Schedule ID (Route)
Actual Qty
Geo-Location
Completition/Cancelled DateTime
Actual gallons
Actual Truck number
Actual Driver
Actual execution timestamp
Exception (cancel) reasons
Driver notes
Driver Photos
Actual driver path and
ahead/behind schedule
New unassigned route
Routes created manually in RNA
Follow same processes for
Services Confirmations
and
Schedules
Schedule ID must be "0"
New customer, well, truck or driver
created in RNA will be pushed with ID "0"