1 / 19

AP234 Ship Operational Logs, Records, and Messages

AP234 Ship Operational Logs, Records, and Messages. Uwe Langbecker EMSA Co-ordinator MARVIN, Hamburg, April 1999. Outline. Typical scenarios Scope and key elements Team, Schedule Next steps. Engine Performance Logs. Shipboard operational database. Class society. Ship manager.

kermit-miranda
Télécharger la présentation

AP234 Ship Operational Logs, Records, and Messages

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AP234 Ship Operational Logs, Records, and Messages Uwe Langbecker EMSA Co-ordinator MARVIN, Hamburg, April 1999

  2. Outline • Typical scenarios • Scope and key elements • Team, Schedule • Next steps

  3. Engine Performance Logs Shipboard operational database Class society Ship manager MiTS Gateway sensors

  4. Fuel Oil Quality Reports Class society Shipboard operational database Ship manager

  5. Events - Data - Reports Events Data collection reports Operational_data, Standard MiTS Tags Noon_at_sea Variables to be logged Sensor A Filled parts included in AP234

  6. Sea voyage ended Pilot onboard Berthed Commenced loading Left berth Pilot disembarked Sea voyage commenced Interruption of sea voyage Sea voyage commenced Sea voyage ended Pilot onboard Pilot disembarked Sea voyage commenced Sea voyage ended Berthed Completed unloading (commenced loading) Ship events and activities Restricted By berth Restricted Open sea Restr .waters Open sea Restricted waters waters waters Port In port Port Delays Channel or water Port entrance departure T,O,E way passage entrance In port | Sea Interrupted Sea Restr. water Sea | | In port voyage sea voyage voyage passage voyage At sea Voyage/Voyage no Round trip=several consecutive voyages (Ref: MARINTEK)

  7. Scope (1) • Standard tags (harmonised with IEC 1162-4) from the control system for monitoring: • equipment and machinery status data • environmental observations • hull stress monitoring: real time measurements • navigational data • tank monitoring (tank surveillance) • Ship events and ship activities These trigger operational data to be collected into standardised reports or user defined reports.

  8. Standard tags IEC 1162 Example: Course (navigational data) • A Course is a type of operational data. • A Course is the horizontal direction in which a vessel is steered or intended to be steered, expressed as angular distance from north. • Course differs from heading. Angular distance is clockwise 0.0-359.99 and 90=East and 270=West, Ref IEC 1162-1. • The corresponding MiTS standard tag code is NAVCOURSE.

  9. Scope (2) • Standardised reports • Fuel oil quality report from laboratory to the ship • Bridge log for archiving • Requisition messages for requisition, purchase and transport of spare parts to the ship • Class society operational survey • Statutory survey ? (depends on IACS)

  10. Scope (3) • Information Quality • real time data and ship/shore data exchange • EMSA business case

  11. Currently developed in ASTM F25.05.06 by SLCSI project in USA supported by MARAD. • Expected as a New Work Item to ISO TC8/SC10 (a guide and requirements to the SSR). Ship Safety Record

  12. Scope (4) • Ship Safety Record (not included yet) • Includes • vessel particulars, certificates, crew, voyage, inspections, incidents, corrective actions, reports. • Made for • maritime organisations, ship owners, operators, regulatory bodies, port/flag state. • Required by • ISM Code for operators to keep such information. • authorities (in the future?), e.g. for a ship that approaches a port (subsets of the SSR).

  13. Scope (5) • Periodic/planned maintenance • out of scope • to be covered by AP226

  14. Relationship to AP226

  15. General Information • Project Leader • Stian Ruud (Det Norske Veritas, Stian.Ruud@dnv.com) • AP document • publicly available from SOLIS • Actively supporting countries • FR: Abder Seridji (BV) • DE: Uwe Langbecker (GL) • IT: Riccardo Poggi (RINA) • UK:Tim Turner (LR) • US: Raymond Kaufmann (Radix Systems Inc.)

  16. Some supporting Projects • DISC-II (EU) • Implementation of a demonstrator of the integrated shipboard database • SCLSI (US) • Ship Lifecycle Support Infrastructure • MARITIM (NO) • Ship Technology/Ship Operation • MARVIN (EU) - ? • virtual network for ship repair

  17. 1998 1999 2000 2001 Next steps: The ISO process • Preparatory stage • Working Draft • CD - Committee Draft (for ballot) • 4 months ballot • DIS - Draft International Standard • 5 months ballot • FDIS - Final DIS • 2 months ballot • IS - International Standard

  18. Next steps: Technical • Develop Application Activity Model • Integrate the Ship Survey Model (partly) • Clarify, whether Ship Safety Record to be integrated (partly) • Develop an EMSA Business Case on quality data • Develop an EXPRESS model structured as Application Modules • Define Conformance Classes • Review processes and definitions

  19. Next steps: Political • Establish informal co-operation with TC8/SC10 “Ship Technology” • Establish informal co-operation with IEC TC80/WG6 • Co-operate with IACS on the survey model

More Related