PROTANK - Production Schedule (Bulk/Liquid Products)
What is
Processing of bulk/liquid products i.e. Silos of material which can be mixed and delivered out in bulk, in a Retail/distribution mode. The C2C interaction is usually Weighbridge software but can be SCADA(3rd party blending procedures) or ATH (Autoterm facility). The control of the C2C is in S01/view/stocks where ftp addresses and user names are maintained.
General
The Production Schedule will list purchase and sale orders/fixings and manufacturing orders.
The status of each item changes according to the processes completed e.g. production put ‘on hold’, transport divert order to another depot, the order is loaded and weighed. The updated status is shown on the refreshed schedule to provide up to date information about the current status of orders/deliveries. The order/fixing information being transferred to the Weighbridge software does not change the status but the Release No shown on the screen, when highlighted, indicates that the order has yet to be transferred.
There is the feature to show either a single Depot/Terminal or view all depots.
There are 2 sequences in the Production Schedule.
a) Standard:-
Today’s schedule (all items for today regardless of status)
All incomplete items in ascending date sequence
Incomplete is defined as not being marked as delivered (shipping status) and not sales invoiced
b) History:-
All items (complete and incomplete) in descending date sequence. User specifies how many days to view.
Colour coding is used to highlight the status of the items on the schedule.
Features of the Production Schedule:-
- Print mixing/production sheets (DOCDES), use explicit named folder 'MixingSheet'.
- Print minibulk tickets (DOCDES)
- Print feed tags (DOCDES), use explicit named folder 'FeedTag'.
- Mark the order as Routed (i.e. transport have specified which depot to use)
- Mark as Manufactured
- Mark the order as On Hold
- Send order details to Weighbridge software (enables load weights etc to be completed/returned to PROTANK)
- Send Sales order details to ATH process (enables load weights etc to be completed/returned to ALOAD)
- Send order details to SCADA software for production mix only.
- Create Manufacturing Orders, 2 styles one for MATPRO and the other TRADE/Mix style
- Create Inter Terminal Transfers i.e. movement of goods between Company locations
- Create Group Minibulk fixings
- Create Delivery returns, in full or part
- Manual override of stock movements for more precision
- Maintain memo for special conditions e.g. can not manufacture/deliver due to lack of resource
- Maintain Customer Delivered Weights, company S01 option
- Allow resubmission of orders/fixings to Weighbridge software
- Filtering
- Colour coding for order status
- Drill to full TRADE screen (read only)
- Standard display styles can be customised
- Print Delivery Notes (DOCDES), use explicit named folder 'DeliveryNotes'.
- Print Sample Stickers (DOCDES) for Sales, use explicit named folder 'SampleStickers'. Automatic print of default nominated Template where a S01 configured Printer has been nominated or alternatively the CMP profile can apply/maintain the users preferred Printer
- Transport/Rotation subsystem
The Weighbridges are accessed via the service WB with its activation and frequency controlled by RPP; this results in the regular export/import of load details to/from the Weighbridge.
Production Schedule
- Deliveries out (sales)
- Intakes (purchases)
- Manufacturing orders (pre-mix)
- Returns
- Minibulks
- Inter Terminal Transfers
- General
- Technical
- Processing Information
Deliveries Out
orders are created from EXPED/TRADE/ in the call-off screen.
They will be created allocated and assigned to the transit account (ctrl50_transbucket), a customer tank or a purchase contract.
A mixing/production sheet can be created basis the current formulation (PQIS) applicable to the Sale Quality field, ex CLI/TRADE.
The orders will appear in the Production Schedule for the relevant terminal/depot in date sequence available for their delivery details to be transferred to the Weighbridge software.
When the order is transferred to WB software, it is marked in ITAS and the details are sent as a text file with a specific name, using ftp. The file name for sending and receiving and the file location are stored by terminal/depot, S01 setup.
The weights and vehicle details are maintained in the Weighbridge software. The information for each order is appended to a completion file which is retrieved by the ITAS Weighbridge service and the details are updated into the ITAS database.
For sales invoiced on loaded weights(CLI/TRADE) the weight from the Weighbridge will update the orders final weight (ctrl50_pneumwtcode ) and will adjust contract quantity (split and header) if there is a difference between loaded and ordered weights. For sales invoiced on customer weights the final weight will be entered manually via the Production Schedule.
A Stock journal is created to move the loaded quantity from stock units into the transit account, basis the current formulation applicable to the sale quality. The order is updated with the create date and time of the formulation for traceability in the PQIS system.
Documents – weigh ticket from WB software, Feed Tag and Mixing Sheet from ITAS basis the quality (PQIS)
The Status of the delivery is updated and the change is visible on the PROTANK grid.
Intakes
Purchase orders are created from EXPED/TRADE in the call-off screen from their purchase contract.
The purchase order is transferred to the Weighbridge software. When the order is transferred, it is marked in ITAS and the details are sent as a text file with a specific name, using ftp. The file name for sending and receiving and the file location are stored by terminal/depot, S01 setup.
The weights and vehicle details are maintained in the Weighbridge software. The information for each order is appended to a completion file which is retrieved by the ITAS Weighbridge service and the details are updated into the ITAS database.
A stock journal created to move the intake quantity from the purchase WIP account (created as per setup in S01) to the destination stock unit. The purchase will be allocated to its stock unit.
Any costs on the purchase will be included in the stock movements
Manufacturing Orders
These are created by PROSCHED with the contract reference – aaaaMO.000 where ‘aaaa’ is the terminal code and ‘MO’ stands for Manufacturing order.
The target stock unit, quantity and quality are entered, whereby a mixing/production sheet can be produced indicating the quantities to be taken from the stock units which are part of the formulation.
When the Terminal Operator has created the order the actual values are maintained on the Manufacturing Order in ITAS to create the administration records. Quantities basis the formulation can be defaulted. The target stock unit will be updated with the release number for traceability and Feed Tag production.
If the Terminal is configured to communicate with SCADA (S01/View/Stocks/Locations) the mixing sheet/recipe details can also be sent to that IP (see below for more technical description of file content)
If the Terminal is configured to communicate with SCADA (S01/View/Stocks/Locations) the mixing sheet/recipe details can also be sent to that IP (see below for more technical description of file content)
Returns
Returns are generated in PROTANK using the original order/fixing as a template for a new fixing for ZERO quantity. The return order is transferred to the Weighbridge as per the original delivery. The returned quantity is weighed over the weighbridge and the target stock unit can be entered. The information from the Weighbridge is subsequently retrieved and used to update the original fixing.
If a target stock unit is entered the original order and stock movement will be adjusted with a movement into that unit. If no target unit is entered the returned amount will be placed into a temporary stock unit (cubit) and is available for the next loading of the same product. The return will be included on the new mixing sheet for traceability.
Minibulk
A group fixing is created for several real fixings.
The Group is to be created from production schedule by picking real fixings so these are marked as being part of the group.
The Group fixing is transferred to the Weighbridge and used as the basis for the Weighbridge ticket. No stock movements are created once it is processed.
When the weights per minibulk are known the Group minibulk is recalled in PROSCHED and the ‘Enter Delivery Details’ feature is activated. The delivered and returned details can be entered per minibulk.
Group minibulks are similar to Manufacturing orders in the way that records are created with a contract ID of aaaaMB.000 where ‘aaaa’ is the terminal code and MB indicates minibulk.
The fixing reference of the real fixings is maintained in the group fixing pump memo for visibility. Each individual real fixing is marked with the Group fixing reference.
Minibulk tickets are produced from the Production Schedule to be passed to the lorry driver for each of the real fixings.
Inter Terminal Transfers
Internal Contracts between terminals are created in TRADE with no price or quantity. An empty freight cost may be included on the purchase side of the internal pair to be completed when the transfer is created.
In the Production Schedule the Terminal Transfer option is used and the appropriate internal sale contract is selected in order to create a sale fixing at the origin terminal and a purchase fixing at the destination terminal. The quality code, quantity and (optionally) a cost are entered. A transit WIP is created and allocated to the sale and purchase.
The fixings are treated as standard sales and purchases with some exceptions.
When the sale is processed the stock journal is created basis the formulation linked to the quality. The movements are between the stock units and the transit account.
When the transfer arrives at its destination the value taken into the destination stock unit is the value of the transit account plus any costs on the purchase fixing.
When the purchase fixing is moved into stock the original sale fixing is marked as delivered.
Transport/Rotation [1Q18]
Transportation and Rotation includes the confirmation of routing and the assignment of movements to a Rotation Index. A Rotation represents the use of a truck for a period of time. Haulier rates per route and per km are used in the calculation of the costs.
Transportation
Transportation relies on the S01 configuration ctrl30_rotations = ‘Y’.
Transportation is an option triggered from the main PROTANK Toolbar. Once activated Transportation and Rotation details may be maintained.
Activation of Transportation icon removes the user to the Transportation screen where the Call-Offs are listed according to the filters and various features/functions are enabled.
Transportation Function
Call-Offs which match the selections are listed. Functionality exists at Call-Off level or at function level.
Modify – enter Memo and dates on a row by row basis
Modify Order – full order modification as PROTANK main screen
Maintain Rotation – jumps to a rotation if one has been entered in the filter
Add to Rotation – Call-Offs not already on a Rotation (transport plan) may be added
Toolbar functions
Confirm/Cancel Transport – a new form is opened when the Call-Offs matching selections may be marked as confirmed (updates transport confirmation date) or the existing confirmation may cancelled (removes date marking)
Maintain Rotations – leads to full Rotation maintenance
Confirm/Cancel Transportation
Undelivered Call-offs are presented for Transportation Confirmation or Cancellation of Transportation Confirmation (the setting or unsetting of Confirmation Date). The presented data must match the Haulier and Year/Week filters. Other prompted details are used in documentation.
After completion of the action documentation may be presented for sending to the Haulier/Internal reasons.
From this screen Call-offs may be added to rotations.
Maintain Rotations
Maintaining Rotations allows the creation, modification, closing, deletion of rotations.
Validation and Summary Report may be generated
The rotation number is system configured from the year and the week of the start date.
The list of items includes Call-offs that have been added to the rotation, movements that have been inserted, missing journeys that have been inserted and the allowance row.
The order of movements may be modified by highlighting the row to move and by using the arrows.
Under ‘edit’ it is possible to:-
Insert Row – enter from and to locations of a movement
Add Allowance Row – 7% or 10% allowance which is applied against the total kms to increase the cost
Deassign – remove the Call-off from the rotation
Insert missing journeys – If the end location of one journey does not match the start location of the next journey a row to match the locations may be entered as an empty truck movement
Toolbar functions
Delete Rotation – allows deletion of the rotation if no Call-Offs are assigned
Deassign all Call-Offs – Deassigns all Call-Offs in one action
Close Rotation – Mark the Rotation as Closed
Re-Open Rotation – Allow the Closed Rotation to be re-opened
Reporting
Rotation Validation is used as a statement of the cost of the rotation
Rotation Summary lists the Call-offs with their cost contribution to the rotation
Technical
Siemen interface.
This is very explicit set of APIs that operate with a middleware which then communicates with Siemen software
SCADA output.
There are 2 variations of content. The file is transferred using ftp and the results of the task are secured in itas directory /log/xx_scadaftp.log and the file itself is secured in DOCMAN directory SCADA.
SCADA Format U
| Nr | Description | Field Size | Offset | Example | ITAS Data |
| 1 | Company | 2 | 1 | gb | ITAS company code |
| 2 | Terminal | 4 | 3 | GLA | phys01_terminal |
| 3 | Release Number | 8 | 7 | 12345678 | phys01_releasenr |
| 4 | Order Quantity | 5 | 15 | 10000 | phys01_conquan |
| 5 | Commodity Code 2 | 6 | 20 | 10345 | phys01_origin |
| 6 | Commodity Description | 40 | 26 | good molasses | phys01_commod*full |
| 7 | Quality Code | 8 | 66 | 10345 | phys01_quality |
| 8 | Buyer Name | 40 | 74 | Mr. Smith | phys01_buyer*title |
| 9 | PC Date | 8 | 114 | 31122014 | pqis_pcdate |
| 10 | PC Time | 6 | 122 | 142531 | pqis_pctime |
| 11 | Tank ID 1 | 12 | 128 | G001.GLA | pqist_tank |
| 12 | Percentage Tank ID 1 | 9 | 140 | 80.123456 | pqist_perc |
| 13 | Tank Id 2 | 12 | 149 | G020.GLA | pqist_tank |
| 14 | Percentage Tank ID 2 | 9 | 161 | 19.876544 | pqist_perc |
| 15… | Subsequent tanks |
Row 2 consists of the file termination character, “$”.
SCADA Format S
The following EOE web services are supported:
1. EOECreateCallOff
2. EOECreateMO
3. EOECreateReturn
4. EOEDeleteCallOff
5. EOEDeleteMO
6. EOEDeleteReturn
7. EOEInstructionSheet
8. EOEInstructionSheetMO
9. EOEProcessDelivery
10. EOEProcessIntake
11. EOEProcessMO
12. EOEProcessReturn
13. EOESetGroup
14. EOESetInstruction
15. EOESetStatus
16. EOESetStatusMO
17. EOEUpdateCallOff
18. EOEUpdateMO
Their layouts are displayed below
SOAPAction: "http://www.hivedome.net/EOECreateCallOff"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOECreateCallOff xmlns="http://www.hivedome.net/">
<Terminal>string</Terminal>
<comp>string</comp>
<phys01Rec>
<TakeonRef>string</TakeonRef>
<Counterparty>string</Counterparty>
<CP_details>
<Title>string</Title>
<Addr1>string</Addr1>
<Addr2>string</Addr2>
<Addr3>string</Addr3>
<Addr4>string</Addr4>
<Zip>string</Zip>
<Phone>string</Phone>
<Geog>string</Geog>
<Prov>string</Prov>
<Region>string</Region>
<Grid>string</Grid>
</CP_details>
<Terminal>string</Terminal>
<DelClient>string</DelClient>
<DC_details>
<Title>string</Title>
<Addr1>string</Addr1>
<Addr2>string</Addr2>
<Addr3>string</Addr3>
<Addr4>string</Addr4>
<Zip>string</Zip>
<Phone>string</Phone>
<Geog>string</Geog>
<Prov>string</Prov>
<Region>string</Region>
<Grid>string</Grid>
</DC_details>
<StartPer>int</StartPer>
<EndPer>int</EndPer>
<Commod>string</Commod>
<Origin>string</Origin>
<Grade>string</Grade>
<WtCode>string</WtCode>
<ConQuan>decimal</ConQuan>
<PackCode>string</PackCode>
<Bags>double</Bags>
<ClRef>string</ClRef>
<Quality>string</Quality>
<ConType>string</ConType>
<Ccy>string</Ccy>
<Thirdparty>string</Thirdparty>
<Spot>string</Spot>
<TransMode>string</TransMode>
<Afi>string</Afi>
<RelNo>long</RelNo>
<DelivTime>string</DelivTime>
<AmPm>string</AmPm>
<SampleCode>string</SampleCode>
<Vessel>string</Vessel>
<Vehicle>string</Vehicle>
<VehicleDriver>string</VehicleDriver>
<VehicleReg>string</VehicleReg>
<TruckType>string</TruckType>
<HaulageAcc>string</HaulageAcc>
<HA_details>
<Title>string</Title>
<Addr1>string</Addr1>
<Addr2>string</Addr2>
<Addr3>string</Addr3>
<Addr4>string</Addr4>
<Zip>string</Zip>
<Phone>string</Phone>
<Geog>string</Geog>
<Prov>string</Prov>
<Region>string</Region>
<Grid>string</Grid>
</HA_details>
<BuyerOrderNo>string</BuyerOrderNo>
<BuyerSecRef>string</BuyerSecRef>
<DelOrderNo>string</DelOrderNo>
<DelSecRef>string</DelSecRef>
<TrailerPlate>string</TrailerPlate>
<TransporterOrderNo>string</TransporterOrderNo>
<Expeditor>string</Expeditor>
<EX_details>
<Title>string</Title>
<Addr1>string</Addr1>
<Addr2>string</Addr2>
<Addr3>string</Addr3>
<Addr4>string</Addr4>
<Zip>string</Zip>
<Phone>string</Phone>
<Geog>string</Geog>
<Prov>string</Prov>
<Region>string</Region>
<Grid>string</Grid>
</EX_details>
<ExpeditorOrderNo>string</ExpeditorOrderNo>
<Buyer>string</Buyer>
<BA_details>
<Title>string</Title>
<Addr1>string</Addr1>
<Addr2>string</Addr2>
<Addr3>string</Addr3>
<Addr4>string</Addr4>
<Zip>string</Zip>
<Phone>string</Phone>
<Geog>string</Geog>
<Prov>string</Prov>
<Region>string</Region>
<Grid>string</Grid>
</BA_details>
</phys01Rec>
</EOECreateCallOff>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOECreateMO"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOECreateMO xmlns="http://www.hivedome.net/">
<terminal>string</terminal>
<comp>string</comp>
<phys09Rec>
<phys09_releasenr>long</phys09_releasenr>
<phys09_unique>int</phys09_unique>
<phys09_contract>string</phys09_contract>
<phys09_client>string</phys09_client>
<CP_details_phys09>
<Title>string</Title>
<Addr1>string</Addr1>
<Addr2>string</Addr2>
<Addr3>string</Addr3>
<Addr4>string</Addr4>
<Zip>string</Zip>
<Phone>string</Phone>
<Geog>string</Geog>
<Prov>string</Prov>
<Region>string</Region>
<Grid>string</Grid>
</CP_details_phys09>
<phys09_quality>string</phys09_quality>
<phys09_wtcode>string</phys09_wtcode>
<phys09_loaded>double</phys09_loaded>
<phys09_loadeddate>int</phys09_loadeddate>
<phys09_orderdate>int</phys09_orderdate>
<phys09_targetdate>int</phys09_targetdate>
<phys09_destwip>string</phys09_destwip>
<phys09_memo>string</phys09_memo>
<phys09_pumpmemo>string</phys09_pumpmemo>
</phys09Rec>
<phys60Details>
<phys60>
<phys60_tank>string</phys60_tank>
<phys60_qty>double</phys60_qty>
<phys60_loaddiff>string</phys60_loaddiff>
</phys60>
<phys60>
<phys60_tank>string</phys60_tank>
<phys60_qty>double</phys60_qty>
<phys60_loaddiff>string</phys60_loaddiff>
</phys60>
</phys60Details>
<status>string</status>
</EOECreateMO>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOECreateReturn"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOECreateReturn xmlns="http://www.hivedome.net/">
<comp>string</comp>
<contract>string</contract>
<status>string</status>
</EOECreateReturn>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOEDeleteCallOff"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOEDeleteCallOff xmlns="http://www.hivedome.net/">
<comp>string</comp>
<contract>string</contract>
</EOEDeleteCallOff>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOEDeleteMO"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOEDeleteMO xmlns="http://www.hivedome.net/">
<comp>string</comp>
<releasenr>long</releasenr>
<unique>int</unique>
</EOEDeleteMO>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOEDeleteReturn"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOEDeleteReturn xmlns="http://www.hivedome.net/">
<comp>string</comp>
<contract>string</contract>
</EOEDeleteReturn>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOEInstructionSheet"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOEInstructionSheet xmlns="http://www.hivedome.net/">
<contract>string</contract>
<comp>string</comp>
<code>string</code>
<pcdate>long</pcdate>
<pctime>long</pctime>
<ret>string</ret>
<del>string</del>
<phys10Details>
<phys10>
<phys10_tank>string</phys10_tank>
<phys10_qty>double</phys10_qty>
<phys10_value>double</phys10_value>
<phys10_rectype>string</phys10_rectype>
</phys10>
<phys10>
<phys10_tank>string</phys10_tank>
<phys10_qty>double</phys10_qty>
<phys10_value>double</phys10_value>
<phys10_rectype>string</phys10_rectype>
</phys10>
</phys10Details>
</EOEInstructionSheet>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOEInstructionSheetMO"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOEInstructionSheetMO xmlns="http://www.hivedome.net/">
<comp>string</comp>
<releasenr>long</releasenr>
<unique>long</unique>
<code>string</code>
<pcdate>long</pcdate>
<pctime>long</pctime>
<del>string</del>
<phys10Details>
<phys10>
<phys10_tank>string</phys10_tank>
<phys10_qty>double</phys10_qty>
<phys10_value>double</phys10_value>
<phys10_rectype>string</phys10_rectype>
</phys10>
<phys10>
<phys10_tank>string</phys10_tank>
<phys10_qty>double</phys10_qty>
<phys10_value>double</phys10_value>
<phys10_rectype>string</phys10_rectype>
</phys10>
</phys10Details>
</EOEInstructionSheetMO>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOEProcessDelivery"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOEProcessDelivery xmlns="http://www.hivedome.net/">
<comp>string</comp>
<contract>string</contract>
<loadDate>int</loadDate>
<vehicleReg>string</vehicleReg>
<ticket>string</ticket>
<HHR>decimal</HHR>
<parcelRef>string</parcelRef>
<wtCode>string</wtCode>
<quantity>double</quantity>
<PCDate>int</PCDate>
<PCTime>int</PCTime>
<tankList>
<udtTank>
<Tank>string</Tank>
<Owner>string</Owner>
<Qty>double</Qty>
</udtTank>
<udtTank>
<Tank>string</Tank>
<Owner>string</Owner>
<Qty>double</Qty>
</udtTank>
</tankList>
</EOEProcessDelivery>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOEProcessIntake"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOEProcessIntake xmlns="http://www.hivedome.net/">
<comp>string</comp>
<contract>string</contract>
<loadDate>int</loadDate>
<vehicleReg>string</vehicleReg>
<ticket>string</ticket>
<HHR>decimal</HHR>
<parcelRef>string</parcelRef>
<owner>string</owner>
<wtCode>string</wtCode>
<quantity>double</quantity>
<tank>string</tank>
</EOEProcessIntake>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOEProcessMO"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOEProcessMO xmlns="http://www.hivedome.net/">
<comp>string</comp>
<releasenr>long</releasenr>
<unique>long</unique>
<loadDate>int</loadDate>
<quantity>double</quantity>
<tankList>
<udtTank>
<Tank>string</Tank>
<Owner>string</Owner>
<Qty>double</Qty>
</udtTank>
<udtTank>
<Tank>string</Tank>
<Owner>string</Owner>
<Qty>double</Qty>
</udtTank>
</tankList>
</EOEProcessMO>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOEProcessReturn"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOEProcessReturn xmlns="http://www.hivedome.net/">
<comp>string</comp>
<contract>string</contract>
<loadDate>int</loadDate>
<vehicleReg>string</vehicleReg>
<ticket>string</ticket>
<HHR>decimal</HHR>
<parcelRef>string</parcelRef>
<owner>string</owner>
<wtCode>string</wtCode>
<quantity>double</quantity>
<tank>string</tank>
</EOEProcessReturn>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOESetGroup"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOESetGroup xmlns="http://www.hivedome.net/">
<contract>string</contract>
<comp>string</comp>
<grpno>long</grpno>
</EOESetGroup>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOESetInstruction"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOESetInstruction xmlns="http://www.hivedome.net/">
<comp>string</comp>
<targDetails>
<targ_quality>string</targ_quality>
<targ_terminal>string</targ_terminal>
<targ_descr>string</targ_descr>
<targ_pumpselection>int</targ_pumpselection>
<targ_destination>int</targ_destination>
<targ_refracrange>string</targ_refracrange>
<targ_directloadout>string</targ_directloadout>
<targ_filterbypass>int</targ_filterbypass>
</targDetails>
<pqisDetails xmlns="">
<pqis_quality>string</pqis_quality>
<pqis_terminal>string</pqis_terminal>
<pqis_pcdate>int</pqis_pcdate>
<pqis_pctime>int</pqis_pctime>
<pqis_descr>string</pqis_descr>
<pqis_brix>decimal</pqis_brix>
<pqis_drymatters>decimal</pqis_drymatters>
<pqis_tsas>decimal</pqis_tsas>
<pqis_cp>decimal</pqis_cp>
<pqis_ash>decimal</pqis_ash>
<pqis_k>decimal</pqis_k>
<pqis_canperc>decimal</pqis_canperc>
<pqis_beetperc>decimal</pqis_beetperc>
<pqis_cmsperc>decimal</pqis_cmsperc>
<pqis_ligperc>decimal</pqis_ligperc>
<pqis_h2operc>decimal</pqis_h2operc>
<pqis_rate>int</pqis_rate>
<pqis_directloadout>string</pqis_directloadout>
<pqis_chloride>decimal</pqis_chloride>
<pqis_tsai>decimal</pqis_tsai>
<pqis_oil>decimal</pqis_oil>
<pqis_mg>decimal</pqis_mg>
<pqis_targbrix>decimal</pqis_targbrix>
<pqis_targdrymatters>decimal</pqis_targdrymatters>
<pqis_targtsas>decimal</pqis_targtsas>
<pqis_targcp>decimal</pqis_targcp>
<pqis_targash>decimal</pqis_targash>
<pqis_targk>decimal</pqis_targk>
<pqis_targtanka>string</pqis_targtanka>
<pqis_targtankb>string</pqis_targtankb>
<pqis_targchloride>decimal</pqis_targchloride>
<pqis_targtsai>decimal</pqis_targtsai>
<pqis_targoil>decimal</pqis_targoil>
<pqis_targmg>decimal</pqis_targmg>
<pqis_targmoisture>decimal</pqis_targmoisture>
<pqis_refracrange>string</pqis_refracrange>
<pqis_cost>decimal</pqis_cost>
<pqis_costTSAS>decimal</pqis_costTSAS>
<pqis_costDM>decimal</pqis_costDM>
<pqis_costCP>decimal</pqis_costCP>
<pqis_memo>string</pqis_memo>
<pqis_inits>string</pqis_inits>
<pqis_costTSASplusone>decimal</pqis_costTSASplusone>
<pqis_costDMplusone>decimal</pqis_costDMplusone>
</pqisDetails>
<pqistDetails>
<pqist>
<pqist_quality>string</pqist_quality>
<pqist_terminal>string</pqist_terminal>
<pqist_pcdate>int</pqist_pcdate>
<pqist_pctime>int</pqist_pctime>
<pqist_tank>string</pqist_tank>
<pqist_perc>double</pqist_perc>
<pqist_descr>string</pqist_descr>
</pqist>
<pqist>
<pqist_quality>string</pqist_quality>
<pqist_terminal>string</pqist_terminal>
<pqist_pcdate>int</pqist_pcdate>
<pqist_pctime>int</pqist_pctime>
<pqist_tank>string</pqist_tank>
<pqist_perc>double</pqist_perc>
<pqist_descr>string</pqist_descr>
</pqist>
</pqistDetails>
</EOESetInstruction>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOESetStatus"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOESetStatus xmlns="http://www.hivedome.net/">
<contract>string</contract>
<comp>string</comp>
<code>string</code>
<ret>string</ret>
</EOESetStatus>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOESetStatusMO"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOESetStatusMO xmlns="http://www.hivedome.net/">
<comp>string</comp>
<releasenr>long</releasenr>
<unique>long</unique>
<code>string</code>
</EOESetStatusMO>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOEUpdateCallOff"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOEUpdateCallOff xmlns="http://www.hivedome.net/">
<Terminal>string</Terminal>
<comp>string</comp>
<contract>string</contract>
<expedDetails>
<phys01_terminal>string</phys01_terminal>
<phys01_clref>string</phys01_clref>
<phys01_delclient>string</phys01_delclient>
<DC_details_exped>
<Title>string</Title>
<Addr1>string</Addr1>
<Addr2>string</Addr2>
<Addr3>string</Addr3>
<Addr4>string</Addr4>
<Zip>string</Zip>
<Phone>string</Phone>
<Geog>string</Geog>
<Prov>string</Prov>
<Region>string</Region>
<Grid>string</Grid>
</DC_details_exped>
<phys01_quality>string</phys01_quality>
<phys01_conquan>double</phys01_conquan>
<phys01_samplecode>string</phys01_samplecode>
<phys01_period>string</phys01_period>
<phys01_startper>long</phys01_startper>
<phys01_ampm>string</phys01_ampm>
<phys01_vessel>string</phys01_vessel>
<phys01_vehicle>string</phys01_vehicle>
<phys01_vehicledriver>string</phys01_vehicledriver>
<phys01_vehiclereg>string</phys01_vehiclereg>
<phys01_trucktype>string</phys01_trucktype>
<phys01_haulageacc>string</phys01_haulageacc>
<HA_details_exped>
<Title>string</Title>
<Addr1>string</Addr1>
<Addr2>string</Addr2>
<Addr3>string</Addr3>
<Addr4>string</Addr4>
<Zip>string</Zip>
<Phone>string</Phone>
<Geog>string</Geog>
<Prov>string</Prov>
<Region>string</Region>
<Grid>string</Grid>
</HA_details_exped>
<phys01_buyer>string</phys01_buyer>
<BA_details_exped>
<Title>string</Title>
<Addr1>string</Addr1>
<Addr2>string</Addr2>
<Addr3>string</Addr3>
<Addr4>string</Addr4>
<Zip>string</Zip>
<Phone>string</Phone>
<Geog>string</Geog>
<Prov>string</Prov>
<Region>string</Region>
<Grid>string</Grid>
</BA_details_exped>
<phys01_counterparty>string</phys01_counterparty>
<CP_details_exped>
<Title>string</Title>
<Addr1>string</Addr1>
<Addr2>string</Addr2>
<Addr3>string</Addr3>
<Addr4>string</Addr4>
<Zip>string</Zip>
<Phone>string</Phone>
<Geog>string</Geog>
<Prov>string</Prov>
<Region>string</Region>
<Grid>string</Grid>
</CP_details_exped>
<phys01_delivtime>string</phys01_delivtime>
<phys01_buyerorderno>string</phys01_buyerorderno>
<phys01_buyersecref>string</phys01_buyersecref>
<phys01_delorderno>string</phys01_delorderno>
<phys01_delsecref>string</phys01_delsecref>
<phys01_transmode>string</phys01_transmode>
<phys01_trailerplate>string</phys01_trailerplate>
<phys01_transporterorderno>string</phys01_transporterorderno>
<phys01_expeditor>string</phys01_expeditor>
<EX_details_exped>
<Title>string</Title>
<Addr1>string</Addr1>
<Addr2>string</Addr2>
<Addr3>string</Addr3>
<Addr4>string</Addr4>
<Zip>string</Zip>
<Phone>string</Phone>
<Geog>string</Geog>
<Prov>string</Prov>
<Region>string</Region>
<Grid>string</Grid>
</EX_details_exped>
<phys01_expeditororderno>string</phys01_expeditororderno>
<phys01_afi>string</phys01_afi>
<phys09_pumpmemo>string</phys09_pumpmemo>
<phys09_quality>string</phys09_quality>
</expedDetails>
<phys60Details>
<phys60>
<phys60_tank>string</phys60_tank>
<phys60_qty>double</phys60_qty>
<phys60_loaddiff>string</phys60_loaddiff>
</phys60>
<phys60>
<phys60_tank>string</phys60_tank>
<phys60_qty>double</phys60_qty>
<phys60_loaddiff>string</phys60_loaddiff>
</phys60>
</phys60Details>
<update>int</update>
</EOEUpdateCallOff>
</soap:Body>
</soap:Envelope>
SOAPAction: "http://www.hivedome.net/EOEUpdateMO"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<EOEUpdateMO xmlns="http://www.hivedome.net/">
<terminal>string</terminal>
<comp>string</comp>
<phys09Rec>
<phys09_releasenr>long</phys09_releasenr>
<phys09_unique>int</phys09_unique>
<phys09_contract>string</phys09_contract>
<phys09_client>string</phys09_client>
<CP_details_phys09>
<Title>string</Title>
<Addr1>string</Addr1>
<Addr2>string</Addr2>
<Addr3>string</Addr3>
<Addr4>string</Addr4>
<Zip>string</Zip>
<Phone>string</Phone>
<Geog>string</Geog>
<Prov>string</Prov>
<Region>string</Region>
<Grid>string</Grid>
</CP_details_phys09>
<phys09_quality>string</phys09_quality>
<phys09_wtcode>string</phys09_wtcode>
<phys09_loaded>double</phys09_loaded>
<phys09_loadeddate>int</phys09_loadeddate>
<phys09_orderdate>int</phys09_orderdate>
<phys09_targetdate>int</phys09_targetdate>
<phys09_destwip>string</phys09_destwip>
<phys09_memo>string</phys09_memo>
<phys09_pumpmemo>string</phys09_pumpmemo>
</phys09Rec>
<phys60Details>
<phys60>
<phys60_tank>string</phys60_tank>
<phys60_qty>double</phys60_qty>
<phys60_loaddiff>string</phys60_loaddiff>
</phys60>
<phys60>
<phys60_tank>string</phys60_tank>
<phys60_qty>double</phys60_qty>
<phys60_loaddiff>string</phys60_loaddiff>
</phys60>
</phys60Details>
<update>int</update>
</EOEUpdateMO>
</soap:Body>
</soap:Envelope>