Difference between revisions of "Change of Origin"
Jump to navigation
Jump to search
PeterHicks (talk | contribs) (Add documentation for Change Of Origin messages) |
MalcolmBovey (talk | contribs) m (Corrected Americanism "alternate" [sic]) |
||
(6 intermediate revisions by 5 users not shown) | |||
Line 3: | Line 3: | ||
When a train is due to start from a location other than the first location in the schedule, a change of origin message will be sent. | When a train is due to start from a location other than the first location in the schedule, a change of origin message will be sent. | ||
− | Trains may start from | + | Trains may start from an alternative location for two reasons: |
* When the previous working is terminated short of its destination and the return working will start from that location | * When the previous working is terminated short of its destination and the return working will start from that location | ||
Line 9: | Line 9: | ||
== Data structure == | == Data structure == | ||
+ | |||
+ | <pre> | ||
+ | { | ||
+ | "header": { | ||
+ | "msg_type": "0006", | ||
+ | "source_dev_id": "V3HS", | ||
+ | "user_id": "#QRP0059", | ||
+ | "original_data_source": "SDR", | ||
+ | "msg_queue_timestamp": "1511528282000", | ||
+ | "source_system_id": "TRUST" | ||
+ | }, | ||
+ | "body": { | ||
+ | "reason_code": "TH", | ||
+ | "current_train_id": "", | ||
+ | "original_loc_timestamp": "", | ||
+ | "train_file_address": null, | ||
+ | "train_service_code": "21734000", | ||
+ | "toc_id": "20", | ||
+ | "dep_timestamp": "1511540100000", | ||
+ | "coo_timestamp": "1511528280000", | ||
+ | "division_code": "20", | ||
+ | "loc_stanox": "16416", | ||
+ | "train_id": "321P42MP24", | ||
+ | "original_loc_stanox": "" | ||
+ | } | ||
+ | } | ||
+ | </pre> | ||
=== Header === | === Header === | ||
Line 20: | Line 47: | ||
|- | |- | ||
|source_dev_id | |source_dev_id | ||
− | | | + | |[[LATA]] or [[CICS Session]] of the inputting terminal |
+ | |- | ||
+ | |user_id | ||
+ | |[[NCI signon]] of the inputting user | ||
|- | |- | ||
|source_system_id | |source_system_id | ||
Line 27: | Line 57: | ||
|original_data_source | |original_data_source | ||
|Set to "TRUST DA" or "SDR" for a change of origin message | |Set to "TRUST DA" or "SDR" for a change of origin message | ||
+ | |- | ||
+ | |msg_queue_timestamp | ||
+ | | | ||
|} | |} | ||
Line 40: | Line 73: | ||
|dep_timestamp | |dep_timestamp | ||
|The planned departure time at the location where the train is being reinstated | |The planned departure time at the location where the train is being reinstated | ||
+ | |- | ||
+ | |loc_stanox | ||
+ | |The STANOX of the new origin of the train | ||
|- | |- | ||
|original_loc_stanox | |original_loc_stanox | ||
Line 64: | Line 100: | ||
|train_file_address | |train_file_address | ||
|The TOPS train file address, if applicable | |The TOPS train file address, if applicable | ||
+ | |- | ||
+ | |coo_timestamp | ||
+ | |The time at which the Change of Origin is entered into TRUST | ||
|} | |} | ||
+ | |||
+ | {{Navtable-DataFeeds}} | ||
+ | |||
+ | [[Category:Train Movement Data]] |
Latest revision as of 12:58, 20 September 2022
Contents
Overview
When a train is due to start from a location other than the first location in the schedule, a change of origin message will be sent.
Trains may start from an alternative location for two reasons:
- When the previous working is terminated short of its destination and the return working will start from that location
- When the train starts from, for example, Doncaster North Yard rather than the schedule location of Doncaster South Yard
Data structure
{ "header": { "msg_type": "0006", "source_dev_id": "V3HS", "user_id": "#QRP0059", "original_data_source": "SDR", "msg_queue_timestamp": "1511528282000", "source_system_id": "TRUST" }, "body": { "reason_code": "TH", "current_train_id": "", "original_loc_timestamp": "", "train_file_address": null, "train_service_code": "21734000", "toc_id": "20", "dep_timestamp": "1511540100000", "coo_timestamp": "1511528280000", "division_code": "20", "loc_stanox": "16416", "train_id": "321P42MP24", "original_loc_stanox": "" } }
Header
Field | Description |
---|---|
msg_type | Set to '0006' for an change of origin message |
source_dev_id | LATA or CICS Session of the inputting terminal |
user_id | NCI signon of the inputting user |
source_system_id | Set to "TRUST" for a change of origin message |
original_data_source | Set to "TRUST DA" or "SDR" for a change of origin message |
msg_queue_timestamp |
Body
Field | Description |
---|---|
train_id | The 10-character unique identity for this train at TRUST activation time |
dep_timestamp | The planned departure time at the location where the train is being reinstated |
loc_stanox | The STANOX of the new origin of the train |
original_loc_stanox | If the location has been revised, e.g. the new origin is 'out of plan' for the train, the STANOX of location in the schedule at activation |
original_loc_timestamp | The planned departure time associated with the original location |
current_train_id | Always blank |
train_service_code | Train service code as per schedule |
reason_code | The reason code for the cancellation, taken from the Delay Attribution Guide |
division_code | Operating company ID as per TOC Codes |
toc_id | Operating company ID as per TOC Codes |
train_file_address | The TOPS train file address, if applicable |
coo_timestamp | The time at which the Change of Origin is entered into TRUST |
Network Rail Open Data Feeds | |
---|---|
Data Feeds | About the Feeds • Account States • Durable Subscriptions • Example Code ( PHP / C# / Java / Ruby / Node.js) • Advanced Uses • FAQ • Release Notes |
RTPPM | RTPPM Feed |
Train Movements | Train Movements Feed • Train Activation • Train Cancellation • Train Movement • Train Reinstatement • Change of Origin • Change of Identity • Change of Location • TSPEED Field • Planned Cancellations • Cancellation Codes |
TD | TD Feed • C-Class Messages • S-Class Messages • Train Describers • TD Berths |
VSTP | VSTP Feed |
TSR | TSR Feed • Route Codes |
SCHEDULE | SCHEDULE Feed • Schedule and Location Records • Association Records • CIF Codes • How Scheduling Works • Allowances |
Reference Data | Reference Data Feed • TOC Codes • CIF Codes • Delay Attribution Codes • Identifying Locations (STANOX, TIPLOC, NLC and 3-Alpha Codes) • STANOX Geographical Areas • Train Planning data |