Statuses And Data To Communicate
NOTE:
TMC recommends using Code Key 17 (Repair Site), Code Key 24 (Repair Status), Code Key 52 (Parts Status), and Code Key 76 (Reason for Delay). For example, the following conditions can be described by VMRS:
- Parts arrived - Code Key 52, Code 10 "Arrived."
- Invoiced - Code Key 24, Code 12, "Waiting for Payment."
- Repair started, but temporarily stopped - Code Key 24, Code 13, "Repair Suspended."
NOTE:
The API should support the following methodology and implementation recommendations:
- Updates should occur every 15 minutes for any RO/Cases with data that has changed. The API should only send data that has changed.
- A master sync of all open RO/Cases should occur at every 24 hours.
- If the API uses a master sync, the client should have input on how far back the API should go back when pulling data.
- The API should support a protocol to manage transmission of data if the API is offline for some period of time (days/hours).
- A methodology to synchronize data between the two business systems/databases should be used to limit network traffic and overhead.
- The API should limit the size of data transmission to avoid errors in transmission and efficient network traffic and overhead.