IMO MSC AdHoc Working Group On Engineering Aspects

IMO MSC Ad-Hoc Working Group On Engineering Aspects of LRIT Version 1. 1 Julian Longson, OPI - CIRM. email: longson@purplefinder. com PS-PSPRES-20070320 Commercial-In-Confidence Data Distribution Plan – Status Review 3/3/2021

1 Document set references to DDP Commercial-In-Confidence 1. MSC. 202(81) - Sections 8. 1 to 9. 2 inclusive. 2. MSC. 210(81) – 11 (also application of 12 and 13) 3. MSC. 211(81) - no reference. 4. MSC 81 Final Report - tbc 5. MSC 82 Final Report - tbc 6. IDE J-Paper - 3. 2. 4 7. IDC J-Paper - 4 8. Comms J-Paper - 2. 2. 7 -2. 2. 8 9. *DDP J-Paper - will evolve from this document. 10. Costing & Billing J-Paper - … 11. Testing Protocols - 2. 2. 7. 2 *Note: the above references relate to main DDP sections - other sections may contain minor references to the DDP. 2

2 - Players and Responsibilities 1. Management – IMO (Secretariat). Commercial-In-Confidence 2. Development, operation and maintenance– IMO. 3. Content management – SOLAS Contracting Governments 4. Oversight - IMSO ■ *Note: the formal audit of the DDP system is outside the scope of this Working Group. 3

3 - High-Level Architecture 1. [Location] – TBD (Action: Secretariat) Commercial-In-Confidence ■ *Note: the location shall be based upon IMO policy and is outside the scope of this Working Group. It likely to form part of GISIS in order to enjoy the same international data protection privileges, etc. 2. User interface – Secure web-interface similar to GISIS confirmed. ■ *Note: the formal audit of the DDP system is outside the scope of this Working Group. 3. Database – Relational model confirmed. ■ *Note: the vendor selection is outside the scope of this Working Group. 4. Distribution philosophy - Open, all information to all parties confirmed. ■ *Note: pursuant to MSC. 202(81) 8. 2. 4

3 - High-Level Architecture cont… 5. [Distribution model] – TBD (Action: Secretariat) Commercial-In-Confidence 1. *Note: under consideration is to distribute, using push or pull technology, the DDP to the DC’s directly using the DDP system or via the IDE. The current IMO distribution model is based on the ‘Pull’ mechanism. The model shall be based upon IMO policy and is outside the scope of this Working Group. 6. [Distribution structure] - TBD (Action: Working Group) 1. *Note: under consideration is to distribute a full or partial copy. 7. Distribution format – Human readable XML confirmed. 8. [XML schema] - TBD (Action: Working Group) 1. *Note: this should be undertaken in consultation with the Secretariat. 1. Version Management – full archiving and oversight audit confirmed. 5

4 - Database / XML Content I Commercial-In-Confidence 1. Housekeeping 1. Nominated LRIT DC, its Internet address and Po. C. 2. Port-/Coastal-/SAR-State Po. C (if not DC Po. C). 3. DDP version number (system generated by DDP system). 4. [Operational Status (OK / NOK)] – TBD (Action: Working Group). *Note: requires clear justification if Performance Standard is to be changed. Alternative approach to include pricing subsystem in IDE to handle this information. 2. Geographic Parameters - Analysis required (Action: Working Group) 1. Flag - global and / or multi-region polygon tracking (IDC only). 2. Port – single-polygon from baseline calculated from NOA time ruling and assumed average vessel speed…unclear. 1. *Note: Neighbouring-state “Mushroom” polygon type 3. Coastal – multi-polygon ≤ 1000 nm from baselines *Note: all polygons should be closed. 6

4 - Database / XML Content cont… Commercial-In-Confidence 3. Standing Orders - Analysis required (Action: Working Group) 1. Flag – APR Interval (15 minutes - 6 hours with discrete intervals) 2. Ports – APR Interval as per Flag above…unclear. 3. Coastal – 3 options: continual / initial APR / none 4. Exclusions – list of CG / Flags using UNCTAD country codes. 5. [Financials (Pricing)] - TBD (Action: Working Group) 1. APR (inc. historical) 2. PPR 3. Modify APR interval start / stop *Note: requires clear justification if Performance Standard is to be changed. Alternative approach to include pricing subsystem in IDE to handle this information. 7

5 - Distribution and update policy Commercial-In-Confidence 1. The DDP will be updated periodically and for control purposes a structured distribution and update policy is required. By way of example it is feasible to send out the DDP each day based on the following schedule: 1. 00: 00 – 16: 00 Updates received 2. 16: 01 New plan, Plan 1 created 3. 16: 02 Plan 1 distributed to all data centres 4. 24: 00 all data centres use Plan 1 *Note: the same frequency model could be used for a weekly, monthly, etc. DDP update cycle. 2. Auditing will also be straightforward as either a DC is using the correct plan at 24: 00 or it is not. 8

6 - WG Intersessional workplan (pre-Hamburg) 1. OPI liaison with IMO Secretariat / IT liaison (wb 21 -May) 1. Clarification / discussion of current Working Group view. Commercial-In-Confidence 2. OPI liaison with IMO Secretariat / IT liaison (wb 4 -June) 1. Update OPI re. DDP system location and distribution model. 3. MSC AHWG LRIT Hamburg (wb 11 -June) 1. OPI to provide a verbal overview / presentation of current status. 2. Use-Case Analysis of Geographic Parameters and Standard Orders particularly with respect to Port-State data access. 3. Consideration of Operational Status flag and Financial info. 4. Commence XML schema specification. 4. MSC LRIT Intersessional (wb 9 -July) 1. Secretariat will submit a paper to clarify system specification. 9