Docstoc

StB

Document Sample
StB Powered By Docstoc
					                                              Electronic
                        Consignment Security Declaration


                                                            Workshop
                                                 London,7th April 2011




Cargo Business Process Panel   1     INTERNATIONAL AIR TRANSPORT ASSOCIATION 2010
IATA Competition Law Compliance
Follow the prepared agenda.

Do not discuss:

   Pricing, including fares, service charges, commissions, etc.
   Bids on contracts or allocation of customers
   Geographic/Product market allocations
   Marketing plans, including expanding or withdrawing from markets
   Group boycotts
   Your commercial relations with agents, airlines or other third parties
   Any discussion aimed at influencing the independent business decisions of
    your competitors

“In case any of the above is discussed then we will ask you to leave
    the conference or the conference call may be terminated”



                              2
Agenda
1. Welcome & introduction (15 min)
2. Legal requirements (45 min)
3. Consignment Security Declaration Background (20 min)
4. Consignment Security Declaration Layout (70 min)


5. Business Process Overview (70 min)
6. IATA standard security data elements (45 min)
7. Proof of Concept Requirements (80 min)
8. Next steps (10 min)


                          3
Welcome & Introduction




 4
Background
 Security is a critical element the of the air cargo supply chain that
  is vital to world trade
 International standards on Security exist (e.g. ICAO Annex 17,
  WCO Safe, ISO 28000)
 Regional & national regulations are in place (e.g. EC 300/2008
  EU 185/2010, US 9/11 Commission Act of 2007)
 Air cargo industry has excellent track record on Security but
  Yemen event raised some concerns
 Regulators and industry are working together to further secure
  the air cargo supply chain while keeping the vital flow of
  commerce


                           5          INTERNATIONAL AIR TRANSPORT ASSOCIATION 2010
Initiatives and proposals
1. Short Term: Standard cargo security
   declaration providing an audit trail of
   who secured what, how & when

2. Mid Term: Standard advance electronic
   information process and timelines to
   improve risk assessment

3. Long Term: Standard supply chain
   security program internationally
   recognized in countries where there is
   none
                       6        INTERNATIONAL AIR TRANSPORT ASSOCIATION 2010
Legal Requirements
(EU & UK)




 7
Regulations – ICAO Annex 17
Each Contracting State shall:
 Establish measures to prevent dangerous devices from being
  introduced in a passenger aircraft
 Ensure that cargo carried onto a passenger aircraft is secure
  from the point security controls are applied until departure
 Establish a process for approval of regulated agents, if involved
  in implementing security controls
 Ensure that application of security controls is confirmed or
  accounted for by a regulated agents
 Ensure that security controls on all-cargo aircraft are set by
  security risk assessment carried out by the national authorities


                           8
Resolutions – IATA Reco. Practice 1630
 Intend to protect air carrier operation against acts of unlawful
  interference
 All Cargo to be carried on an aircraft should be subjected to security
  controls before being uplifted on the aircraft
 Airline can apply controls itself or controls have to be confirmed by a
  regulated agent
 Known Consignor cargo can be loaded onto all aircrafts and Account
  Consignor cargo on all-cargo aircraft only
 Appropriate authorities and/or air carriers may require a security
  declaration
 Security declaration shall be provided in paper, electronic format, or
  any other means that may be allowed in the future
 Security declaration will be provided by the Known/Account Consignor
  and/or Regulated agent and/or Air Carrier



                               9
Regulations – EC 300/2008 & EU 185/2010 (1/4)
 All cargo to be carried on an aircraft shall be secured
 Cargo secured upstream must be protected from interference
  until being loaded onto the aircraft
 Security controls can be done by a regulated agent, a known
  consignor or an account consignor
    Regulated agents and known consignors shall be approved by the
     authority
    Account consignors shall be designated by a regulated agent
 Regulated agents include third party logistic providers, air
  carriers and handling agents
 When accepting an “unsecured” consignment the regulated
  agent shall ensure that the consignment is screened and
  secured


                         10
Regulations – EC 300/2008 & EU 185/2010 (2/4)
 Regulated agent shall ensure that consignment tendered to the
  carrier or another regulated agent is accompanied by the
  appropriate documentation
 Documentation shall be in the form of an airway bill or in a
  separate declaration
 Document can be in writing or in an electronic format


     “Regulation 185 came into force in April 2010,
     Member States have until April 2013 for that.”




                        11
Regulations – EC 300/2008 & EU 185/2010 (3/4)
Documentation shall contain the following information:

1.   Site name and address of the regulated agent or its unique identifier
2.   Unique identifier of the consignment (HWB or AWB)
3.   Content of the consignment
4.   Security status (SPX or SCO)
5.   Reason why the security status was issued
       KC, or AC or
       Means of screening adopted or
       Grounds for exempting the consignment from screening
6. Name of the person who issued the security status, or an equivalent
   identification and the date and time of issue
7. Site specific name and address or unique identifier of any regulated
   agent who has accepted the security status given to the consignment
   by another regulated agent


                               12
Regulations – EC 300/2008 & EU 185/2010 (4/4)
In case of Consolidation the documentation shall contain:

1. Site name and address of the regulated agent or its unique
   alphanumeric identifier
2. Unique identifier of the consignment (HWB or AWB)
3. The security status of the consignment

Such information shall be available:

 At any time before the consignment is loaded on the aircraft and
 Afterwards for the duration of the flight or for 24 hours.




                            13
Regulations – UK




                   14
Consignment Security
Declaration Background




      INTERNATIONAL AIR TRANSPORT ASSOCIATION 2010
Consignment Sec. Dec. Advisory Group (1/3)
 Established in September 2010
 Initially an e-freight requirements
 A standalone cargo security project after the Oct. 2010 event
 4 main objectives
   1. Comply with the cargo security regulations e.g. EC 300/2008;
      EU185/2010
   2. Enable replacement of a paper cargo security declaration by
      electronic means
   3. Provide recommendations on the business processes
   4. Provide recommendations on standard cargo EDI messages
      (CIMP & XML)


                         16
       Consignment Sec. Dec. Advisory Group (2/3)
        The advisory group is comprised of supply chain stakeholders*
             1. Shippers, Freight forwarders
             2. Airlines, Ground Handlers
             3. Regulators


        The advisory group has developed 3 main deliverables
             1. Functional specifications (process & rules)
             2. Consignment Security Declaration layout (data elements)
             3. Recommendations to IATA standards (resolutions, EDI
                messages)


* TIACA, FIATA (DGF, K&N, Agility), IATA (AF, CV, LH, 5X), GHA (Cargologic), Regulators (UK, NL, EC)
                                              17
Consignment Sec. Dec. Advisory Group (3/3)
The IATA electronic Security Declaration Advisory Group set up a
process compliant with security requirements where:

 Secure operators exchange and archive security information
  electronically ensuring that only secure cargo is flown
 Authorities have an audit trail along the supply chain of who has
  secured what, how and when
 Standard paper layout of the electronic cargo security declaration
  can be re-produced at any point and time in the supply chain
 Standard paper cargo security declaration can also be used when
  the electronic one is not yet accepted or implemented


                         18
Consignment Security
Declaration Layout




 19
Consignment Security Layout
 The Advisory Group drafted one single layout that is:
    Easy to understand and compliant with regulations
    Applicable for direct and consolidation shipments
    Useable for all regulated agents (at house & master)
    For Cargo and potentially Mail (support from UPU)
    Able to include ad-hoc country textual statements e.g.
     emergency amendment




                         20
Business Process Overview




 21
Business Process – Consolidation (1/4)

                                      Appropriate
      1                                Authority
       a     2
        1
         b             SLI                                           Carrier
                 3

  Known Consignor or
  Account Consignor
                                                   Regulated Agent
      (Shipper)           Regulated Agent           (Handling Agent
                        (Freight Forwarder)     or self-handled Carrier)




                             22
Business Process – Consolidation (2/4)

                                       Appropriate
                                        Authority



   Known Consignor or                                               Regulated Agent
   Account Consignor          6                                        (Carrier)
       (Shipper)
                                              8
                          4
                                              7      FW Regulated Agent
                          Regulated Agent                   (Handling Agent
                        (Freight Forwarder)           B or self-handled Carrier)
    Unsecure Cargo                 5




                          23
Business Process – Consolidation (3/4)

                                     Appropriate
                                      Authority

                                                                  1
                                                                   2   Carrier
                                              9
  Known Consignor or
                                                             1     FWB
  Account Consignor
      (Shipper)          Regulated Agent
                                             1
                                                              1    /FFM
                       (Freight Forwarder)             Regulated Agent
                                              0        (Handling Agent
                                                   or self-handled Carrier)


                        Unsecure Cargo




                          24
Business Process – Consolidation (3/4)
                          1          Sec.   Appropriate   Sec.     1
                           5         Dec.    Authority    Dec.      5

                                                                 1
                        SLI /                      FWB /          4
                                                                            Carrier
                                                    FFM
                        FWB                  1
   Known Consignor or
   Account Consignor                          3
       (Shipper)                                          Regulated Agent
                            Regulated Agent               (Handling Agent
                          (Freight Forwarder)         or self-handled Carrier)




                                25
IATA Standard Security
Data Element




 26
       Related CIMP Standards
    IATA has amended its Cargo Interchange Message Procedures (CIMP) to
     facilitate the exchange of the security declaration data that can be used:
          As the electronic security declaration
          To establish the audit trail
          To populate the paper security declaration
    Some data elements are editorially amended
    New data elements are included:
            Screening methods (SM)
            Security Status (SS, the format is aaa)
            Screening exemptions (the format is aaaa)
            Security status name of the issuer
            Security Status Date and Time (SD)
            Security Textual Statement (ED)
            Expiry date (ED)




Cargo Business Process Panel           27            INTERNATIONAL AIR TRANSPORT ASSOCIATION 2010
       IATA Standard cargo security messages /codes
      IATA endorsed in December 2010 the standard cargo security
      messages and codes recommended by the advisory group

       Security Statuses                                   Methods of screening
          NSC: Cargo has not been secured yet for            PHS: Physical Inspection and/or hand search
           Passenger or All-Cargo Aircraft                    VCK: Visual check
          SPX: Cargo Secure for Passenger and All-           XRY: X-ray equipment
           Cargo Aircraft                                     EDS: Explosive detection system
          SCO: Cargo Secure for All-Cargo Aircraft Only      RES: Remote explosive scent tracing explosive
                                                               detection dogs
       Screening Exemptions:                                  FRD: Free running explosive detection dogs
        5 standard codes                                     VPT: Vapor trace
                                                              PRT: Particle trace
                                                              MDE: Metal Detection Equipment
                                                              AOM: Subjected to any other means*


* Textual description needed
                                           28
Consolidation Shipments Process (1/4)
                                                     Appropriate
                                                      Authority


                                  SLI                                                Carrier


     Known Consignor or
     Account Consignor
                                                                  Regulated Agent
         (Shipper)                       Regulated Agent           (Handling Agent
                                       (Freight Forwarder)     or self-handled Carrier)




Unique ID for the consignment - SLI#
Consignment Content
NSC if unsecure cargo
KC ID or AC Reference – of Shipper




                                               29
Consolidation Shipments Process (2/4)
                                                          Appropriate
                                                           Authority



    Known Consignor or                                                                           Carrier
    Account Consignor
        (Shipper)


                                       Regulated Agent                             Regulated Agent
                                     (Freight Forwarder)                            (Handling Agent
                                                                                or self-handled Carrier)
      Unsecure Cargo
                             Store in Operating System
                 Regulated agent (f reight f orwarder) screens unsecure cargo:

                 Regulated Agent ID – of f reight f orwarder or if sub-contracted
                 Unique ID f or the Consignment – HWB#
                 Consignment Content
                 SPX
                 Screening method or grounds f or exemption
                 Security Status Issue
                 - Name or Employee ID - of f reight f orwarder
                 - Date/time
                 Security Status Issue if sub-contracted
                    - Regulated Agent ID if applicable - of f reight f orwarder sub-contractor
                     - Name or Employee ID - of f reight f orwarder sub-contractor
                     - Date/time         30
Consolidation Shipments Process (3/4)
                                                              Appropriate
                                                               Authority


                                                                                            Regulated Agent
             Known Consignor or                                                                (Carrier)
             Account Consignor
                 (Shipper)
                                                                    FWB            Regulated Agent
                                                Regulated Agent
                                                                                    (Handling Agent
                                              (Freight Forwarder)
                                                                                or self-handled Carrier)



                                                                 Regulated agent (freight forwarder) security
                                                                 statement in respect of a consolidation:

                                                                 Regulated Agent ID – of freight forwarder
                                                                 Unique ID for the Consignment – AWB#
                                                                 Consignment Content – consolidation
                                                                 Either SCO or SPX




                                                  security information may be included in the OCI line of FHL
Note: when bilaterally agreed between the parties,31
Consolidation Shipments Process (4/4)




Regulated agent (GHA or self-handled airline) secure un-secure cargo :

- Regulated Agent ID – of handler/airline (a) or (g) if sub-contracted
- Unique ID for the Consignment – AWB# (b)
- Consignment Content - consolidation (c)
- SPX (d)
- Screening method or grounds for exemption (e)
Security Status Issue (f)
- Name or Employee ID - of handler/airline
- Date/time
Security Status Issue (f) if sub-contracted
- Regulated Agent ID if applicable – of handler/airline sub-contractor (a
- Name or Employee ID – of handler/airline sub-contractor
- Date/time                                         32
Consignment Security Declaration
Process & Layout example

                                            Authority



  Known Consignor or                                                         Carrier
                       SLI
  Account Consignor
                                                   FWB
      (Shipper)
                                                            Regulated Agent
                               Regulated Agent               (Handling Agent
                             (Freight Forwarder)         or self-handled Carrier)




               Unsecure Cargo                Unsecure Cargo




                                    33
Proof of Concept
Requirements




 34
Goals of Proof of Concept exercise
Two separate goals:

1. To prove it is possible and viable in practice to use a standard
   electronic Consignment Security Declaration (eCSD) to exchange data
   between proscribed parties, and produce hard copies of a Cargo
   Security Declaration from the electronic record where required, in
   compliance with EC & UK Regulations and in compliance with the EU’s
   trading partners requirements to secure the Airfreight Supply Chain

2. To fine tune the standard eCSD usage and process that can be
   proposed for common adoption by EU member states in compliance
   with EC & other Countries Regulations, which can also be
   recommended to like minded states wishing to implement an Aviation
   Security programme under the ICAO Annex 17.


                           35
Scope to be discussed and determined

 Outbound from the UK
 Transit and transfer out of scope
 General cargo and special cargo out of scope
 Known and unknown cargo
 Known and/or Account Consignor, Regulated Agent
  (FF/GHA), Air Carrier (IT service provider if any)
 Able to exchange security information
 Able to produce paper security declaration on ad-hoc
  basis


                     36
  Proposed PoC Plan (for discussion)



                                  II.                           IV.            V. ‘Go Live’     VI. Validate
        I.                                          III.
                               Validate                      ‘Wet run’            (paper        legislative
    Confirm                                      Technical
                    KO        process                         tests      Go - produced        compliance,
      PoC         Meeting
                                                   Build                  live
                                for all                       (paper              on site      propose plan
  Participants                                    and test
                             participants                    carried in         from data        for wider
/ Stakeholders
                                                              parallel)        on demand)        adoption
(includes                 (includes         (includes
vendors of                                                                                    (includes
                          validation of     vendors of
Stakeholder                                                                                   validation
                          process with      Stakeholder
software                                                                                      with
                          authorities)      software
solutions                                                                                     authorities)
                                            solutions




                                            37
       Proposed timings (for discussion)
        April 11              May 11             Jun 11           Jul 11            Aug 11           Sep 11    Oct 11   Nov 11



              I. Confrm       Kick-
             Participants     off

                               II. Review business
                                      process


                                            III. Technical build and test


                                                                 IV. Wet run tests
                                                                 (paper still there)


Not all participants required to follow exactly same timing                V. Prepare for Go Live   Go live
Several steps can be performed partly in parallel => up to
each participant to identify opportunities to anticipate on
following steps                                                                                  VI. Monitor
Timing for next steps to be confirmed after each preceding                                     and document
step has been completed
Technical build will be critical path => scope in such a way
as to stay within time




                                                           38
Freight forwarders requirements

 Support EDI (e.g. CIMP or XML messages)
 Send air waybill data messages to the carrier
  containing the secure cargo information ( e.g. SCO or
  SPX)
  Note: It may be agreed bi-laterally that the secure
  information will also be included into the House
  waybill messages.
 Archive house and air waybill data containing the
  secure cargo information
 Produce paper security declaration from electronic
  records on an ad hoc basis as needed.
                     39
Carriers (handling agent or self-handled carrier) requirements

 Support EDI (e.g. CIMP or XML) messages
 Receive air waybill and status messages containing
  the secure cargo information ( e.g. SCO for all cargo
  and all mail aircraft and SPX)
 Archive air waybill data and status data including
  security information
 Produce paper security declaration from electronic
  records on an ad hoc basis as needed.




                        40
Next Steps




      INTERNATIONAL AIR TRANSPORT ASSOCIATION 2010
Immediate Next steps
 April 14th 2011: IATA to engage IT service providers
 May 5th 2011: Traders (FF’s, Airlines, GHA’s) to confirm
  their participation to:
                   wolstenhoc@iata.org
 Mid May 2011: Kick Off Meeting w/c




                     42
More Information?



      www.iata.org/cargosecurity




              43

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:12
posted:6/5/2011
language:English
pages:43