XFSU Mapping
XFSU Purpose¶
XFSU message is used to provide a Shipment Status update, discrepancy details or sometimes to provide complementary Customs information. It is also used to share Shipment milestones by Cargo-iQ members.
XFSU Mapping¶
FSU and XFSU messages are Shipment level messages, the entry point is the AWB number but it can also be used to provide status updates on part or split shipments.
Proposed mechanism¶
Shipment-level status¶
With messaging standards, status updates are at Shipment level, even when the update is about a split or part shipment. As a matter of fact it is currently very complicated to have proper Piece level status updates for two main reasons: From a technological point of view the messages (FSU/XFSU) can only convey Shipment level information and from an operations point of view very few stakeholders are fully capable of handling piece level information.
In a fully ONE Record environment the information is shared at Piece level. It implies that all Pieces are properly identified and that statuses can be applied on individial pieces within a shipment. This solves the issues with part or split shipments
For the sake of (X)FSU mapping with ONE Record, statuses are at Shipment level, meaning linked to a Shipment object. For that purpose we have added a new type of event, called StatusUpdateEvent.
The StatusUpdateEvent is a subtype of LogisticsEvent, thus it inherits all of LogisticsEvent properties and has additional properties listed below:
| Property | Data type | Description / Usage |
|---|---|---|
| partialPieceCount | int | Number of piece for the status, differs from total piece count of shipment in case of Part/Split shipment status |
| partialWeight | Value | Weight of the pieces for the status, differs from total weight of shipment in case of Part/Split shipment status |
| partialVolume | Value | Volume of the pieces for the status, differs from total weight of shipment in case of Part/Split shipment status |
| transferredFrom | Organization | Idenfities the Organization transferring the shipment, especially for RCT and TFD statuses |
| transferredTo | Organization | Identifies the Organization receiving the shipment, especially for TRM status |
| notifiedOrganization | Organization | Identifies the Organization notified, especially for NFD status |
| transportMovementReference | TransportMovement | Link to the TransportMovement to convey flight information when required |
Note
It is essential to note that these guidelines are only effective in the context of mapping between (X)FSU and ONE Record. ONE Record is by design Piece-centric and is ready for Piece level management.
Types of status updates¶
The mapping with ONE Record differs based on the kind of Status update. We identify 2 main use cases:
- Shipment status updates (e.g. RCS, FOH, etc.) are based on the usage of
StatusUpdateEventon the Shipment. - Providing additional information such as Security or Customs details, reffered to as (X)FSU-OCI. These do not require usage of
LogisticsEventbut the update of relevant obejcts.
| Code | Description | ONE Record mapping |
|---|---|---|
| DIS | An apparent error has occurred, on this date at this location, with the handling of the consignment or its documentation, which is further clarified by the accompanying discrepancy code | StatusUpdateEvent on Shipment |
| AWD | The arrival documentation has been physically delivered to the consignee or the consignee’s agent on this date at this location | StatusUpdateEvent on Shipment |
| AWR | The arrival documentation has been physically received from a scheduled flight at this location | StatusUpdateEvent on Shipment |
| NFD | The consignee or the consignee’s agent has been notified, on this date at this location, of the arrival of the consignment | StatusUpdateEvent on Shipment |
| ARR | The consignment has arrived on a scheduled flight at this location | StatusUpdateEvent on Shipment Details of Flight times on the TransportMovement |
| BKD | The consignment has been booked for transport between these locations on this scheduled date and this flight | StatusUpdateEvent on Shipment or Waybill |
| CCD | The consignment has been cleared by the Customs authorities on this date at this location | StatusUpdateEvent on Shipment |
| TRM | The consignment has been manifested and/or will be physically transferred to this carrier at this location | StatusUpdateEvent on Shipment |
| MAN | The consignment has been manifested for this flight on this scheduled date for transport between these locations | StatusUpdateEvent on Shipment |
| DLV | The consignment has been physically delivered to the consignee or the Consignee’s agent on this date at this location | StatusUpdateEvent on Shipment |
| DDL | The consignment has been physically delivered to the consignee’s door on this date at this location | StatusUpdateEvent on Shipment |
| DPU | The consignment has been physically picked up from the shipper’s door on this date at this location | StatusUpdateEvent on Shipment |
| RCF | The consignment has been physically received from a given flight or surface transport of the given airline | StatusUpdateEvent on Shipment |
| RCS | The consignment has been physically received from the shipper or the shipper’s agent and is considered by the carrier as ready for carriage on this date at this location | StatusUpdateEvent on Shipment |
| RCT | The consignment has been physically received from this carrier on this date at this location | StatusUpdateEvent on Shipment |
| TFD | The consignment has been physically transferred to this carrier on this date at this location | StatusUpdateEvent on Shipment |
| PRE | The consignment has been prepared for loading on this flight for transport between these locations on this scheduled date | StatusUpdateEvent on Shipment |
| CRC | The consignment has been reported to the Customs authorities on this date at this location | StatusUpdateEvent on Shipment |
| TGC | The consignment has been transferred to Customs/Government control | StatusUpdateEvent on Shipment |
| DEP | The consignment has physically departed this location on this scheduled date and flight for transport to the arrival location | StatusUpdateEvent on Shipment Details of Flight times on the TransportMovement |
| FOH | The consignment is on hand on this date at this location pending “ready for carriage” determination | StatusUpdateEvent on Shipment |
| DOC | Documents Received by Handling Party | StatusUpdateEvent on Shipment |
| FIW | Freight Into Warehouse Control | StatusUpdateEvent on Shipment |
| FOW | Freight Out of Warehouse Control | StatusUpdateEvent on Shipment |
| OSI | Other Service Information | |
| OCI | Update of SecurityDeclaration for eCSD information and CustomsInformation or other relevant data property for Customs information |
Status updates based on StatusUpdateEvent¶
As shown in the table above, most status updates can be made via a StatusUpdateEvent linked to Shipment object. In case of Split or Part shipment, the partial* properties need to be used.
When flight details are required, the corresponding TransportMovement needs to be linked. It will contain information such as flight identifier and movement times.
Usage of (X)FSU for OCI segment¶
With current messaging standards, (X)FSU is sometimes used to provide udpated Security information or Customs information. With ONE Record it is recommended to update the relevant objects instead (SecurityDeclaration or CustomsInformation).
More details can be found on the OCI Mapping detailed page