Change of Identity: Difference between revisions
m categorisation |
Tom Cairns (talk | contribs) Add scenario for 0002 messages at least where revised_train_id not shown as the current ID |
||
(4 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
One or more Change of Identity messages may be sent for a non-passenger (freight or engineering) train, after activation, where the class of the train is to change. This will happen if the train will run without wagons (i.e. a Class 6 service runs as a Class 0), or if the train is carrying a wagon with a defect and must run at a slower speed. | |||
== Data structure == | |||
<pre> | |||
{ | |||
"header": { | |||
"msg_type": "0007", | |||
"source_dev_id": "V2WX", | |||
"user_id": "#WAELKNK", | |||
"original_data_source": "SDR", | |||
"msg_queue_timestamp": "1511531881000", | |||
"source_system_id": "TRUST" | |||
}, | |||
"body": { | |||
"current_train_id": "", | |||
"train_file_address": "BAX", | |||
"train_service_code": "56609010", | |||
"revised_train_id": "86417G1J24", | |||
"train_id": "86678V1J24", | |||
"event_timestamp": "1511531880000" | |||
} | |||
} | |||
</pre> | |||
=== Header === | === Header === | ||
Line 17: | Line 36: | ||
|- | |- | ||
|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 23: | Line 45: | ||
|- | |- | ||
|original_data_source | |original_data_source | ||
|Set to "TOPS" for an change of identity message | |Set to "SDR" or "TOPS" for an change of identity message | ||
|- | |||
|msg_queue_timestamp | |||
| | |||
|} | |} | ||
Line 39: | Line 64: | ||
|- | |- | ||
|revised_train_id | |revised_train_id | ||
|The new 10-character unique identity for this train | |The new 10-character unique identity for this train. You should continue to track the original train_id field as well, as some other message types will not contain this new ID. | ||
|- | |- | ||
|train_file_address | |train_file_address | ||
Line 51: | Line 76: | ||
|- | |- | ||
|} | |} | ||
{{Navtable-DataFeeds}} | |||
[[Category:Train Movement Data]] | [[Category:Train Movement Data]] |
Latest revision as of 13:56, 4 November 2019
Overview
One or more Change of Identity messages may be sent for a non-passenger (freight or engineering) train, after activation, where the class of the train is to change. This will happen if the train will run without wagons (i.e. a Class 6 service runs as a Class 0), or if the train is carrying a wagon with a defect and must run at a slower speed.
Data structure
{ "header": { "msg_type": "0007", "source_dev_id": "V2WX", "user_id": "#WAELKNK", "original_data_source": "SDR", "msg_queue_timestamp": "1511531881000", "source_system_id": "TRUST" }, "body": { "current_train_id": "", "train_file_address": "BAX", "train_service_code": "56609010", "revised_train_id": "86417G1J24", "train_id": "86678V1J24", "event_timestamp": "1511531880000" } }
Header
Field | Description |
---|---|
msg_type | Set to '0007' for an change of identity 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 identity message |
original_data_source | Set to "SDR" or "TOPS" for an change of identity message |
msg_queue_timestamp |
Body
Field | Description |
---|---|
train_id | The 10-character unique identity for this train at TRUST activation time |
current_train_id | If this is the second or subsequent change of identity for a train, this field will contain the revised_train_id field from the previous change of identity message |
revised_train_id | The new 10-character unique identity for this train. You should continue to track the original train_id field as well, as some other message types will not contain this new ID. |
train_file_address | The TOPS train file address, if applicable |
train_service_code | Train service code as per schedule |
event_timestamp | The time, in milliseconds, when the train's identity was changed |
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 • TIPLOC Records • 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 (BPLAN) |