level-3-support

See below mail from Ground2 Air:

We would like to request the continuation of the SCAN development in Smartgo to ensure that, once a shipment has been declared secure, the appropriate security status (eCSD) is automatically generated in the OCI line of the FFM message.

SmartGo Actual Screen:

{width="314" height="184"}{width="543" height="82"}

As requested by Airline, after the screening information is entered in the SCAN field in Smartgo, the eCSD messaging format should appear in the FFM under the OCI line as per C-IMP standards.

The format should appear as follows:

/MU/ISS/RA/00003-01
///SS/SPX
///SM/XRY
///SN/GEORGE CLOONEY
///SD/04FEB1410

//OSS/RC/CHACC3MUMRU-WK

Where:

• ISS – Company issuing the security status (RA number to be stated; note that the “3” of RA3 must not be included, as this would be outside C-IMP standard).
• SS – Applicable security status as per IATA codes list (SPX or SHR).
• SM – Applied security method as per IATA codes list.
• SN – Name or staff ID of the screener.
• SD – Date and time when the security status was declared.
• OSS – Entity accepting the given security status (for MRU, Edelweiss with their ACC3 identifier).

Kindly let us know which necessary development needed to ensure that once the screening details are completed in the SCAN field, the eCSD data is correctly generated in the FFM OCI line in compliance with IATA C-IMP messaging standards.