IMO MSC AdHoc Working Group On Engineering Aspects

Review of the current document set MSC. 202(81) - 8. 1 to 9. 2

Players and Responsibilities ■ Ownership – IMO (Secretariat). Commercial-In-Confidence ■ Development and operation –

High-Level Architecture ■ Location – TBD (proposal to co-locate with the IDE) Commercial-In-Confidence ■

Database / XML Content I Commercial-In-Confidence ■ Housekeeping ■ Nominated LRIT DC, its Internet

Database / XML Content II Commercial-In-Confidence ■ Standing Orders ■ Flag – APR Interval

Distribution and update policy Commercial-In-Confidence ■ If the DDP is to be updated daily

Intersessional workplan (pre-Hamburg) Commercial-In-Confidence ■ IMO Secretariat / IT liaison (wb 14 -May) ■

Slides: 8

Download presentation

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

Review of the current document set MSC. 202(81) - 8. 1 to 9. 2 MSC. 210(81) – 11 MSC. 211(81) - … MSC 81 – Final Report IDE J-Paper - 3. 2. 4 IDC J-Paper - 4 Comms J-Paper - 2. 2. 7 -2. 2. 8 *DDP J-Paper Costing & Billing J-Paper - … Testing Protocols - 2. 2. 7. 2 Commercial-In-Confidence ■ ■ ■ ■ ■ 2

Players and Responsibilities ■ Ownership – IMO (Secretariat). Commercial-In-Confidence ■ Development and operation – IMO (IT). ■ Content management – Contracting Governments ■ Audit - IMSO 3

High-Level Architecture ■ Location – TBD (proposal to co-locate with the IDE) Commercial-In-Confidence ■ User interface – secure web-interface (similar to GISIS) ■ Database – Relational (pending IMO guidance) ■ Distribution philosophy - All information to all parties… ■ Distribution method – one full / partial copy to IDE (*onward release to DCs) ■ Distribution format – XML (human readable) ■ Version Management – full archiving and auditable. 4

Database / XML Content I Commercial-In-Confidence ■ Housekeeping ■ Nominated LRIT DC, its Internet address and Po. C ■ Port-/Coastal-/SAR-State Po. C (if not DC Po. C) ■ DDP version number ■ [Operational Status (OK / NOK) i. e. barring. ] ■ Geographic Parameters ■ Flag (global and multi-regional tracking) ■ Port(s) – Distance when time based could be > 1000 nm ■ Coastal – ≤ 1000 nm (closed multi-polygon from [baselines / boundary]) 5

Database / XML Content II Commercial-In-Confidence ■ Standing Orders ■ Flag – APR Interval (15 minutes - 6 hours) ■ Ports – Time (NOA / National ruling dependant) ■ Coastal – 3 options: continual / initial APR / none ■ Exclusions – list of CG / Flags ■ [Financials (Pricing) ■ APR (inc. historical) ■ PPR ■ Modify APR interval start / stop] 6

Distribution and update policy Commercial-In-Confidence ■ If the DDP is to be updated daily (monthly) then it is feasible to send out the entire plan each day (month) based on the following schedule (frequencies): Ø 00: 00 – 16: 00 Updates received Ø 16: 01 New plan, Plan 1 created Ø 16: 02 Plan 1 distributed to all data centres Ø 24: 00 all data centres use Plan 1 ■ The benefit of sending out the entire plan is that DCs will require less sophisticated programming than if updates are sent out, auditing will also be very simple as either a DC is using the correct plan at 24: 00 or it is not (all opposite to sending out a partial plan). 7

Intersessional workplan (pre-Hamburg) Commercial-In-Confidence ■ IMO Secretariat / IT liaison (wb 14 -May) ■ Use case development ■ XML schema development ■ Distribution and update process definition ■ Draft DDP Standard distribution to WG (wb 28 -May) ■ Drafting (wb 4 -June) ■ MSC AHWG LRIT (Hamburg) (wb 11 -June) 8