1 / 28

Information Technology in Ship Operations F1: IT-Standards project

Nauticus Integration and Standardisation & ISO/WD 10303-234 presented by Stian Ruud / DNV 27. April 1999. Information Technology in Ship Operations F1: IT-Standards project. Norwegian Research program 1994-1997 funded by the Norwegian Research Council (NFR).

atira
Download Presentation

Information Technology in Ship Operations F1: IT-Standards project

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. Nauticus Integration and Standardisation&ISO/WD 10303-234presented by Stian Ruud / DNV 27. April 1999

  2. Information Technology in Ship OperationsF1: IT-Standards project Norwegian Research program 1994-1997 funded by the Norwegian Research Council (NFR). About 50 Norwegian companies participated in program DNV project manager for the IT-Standards project F1: Høegh Fleet Services, Barber International, Kongsberg NC Automation, Marinor, Visma/SpecTec, MMS, Sintef Electronics and Cybernetics, MARINTEK, DNV Petroleum Services, DNV

  3. Exchange of information from ship to shore Shipboard operational database (EDIMAR) Ship operator MiTS Gateway sensors

  4. Business cases as defined by Høegh Pilot Ship Noon at sea event report, Noon at port report Fuel and lubrication oil consumption and stock Running hours data Environmental data Bunkering data Energy consumption Port departure Hull and propeller performance data Bridge log Performance test main engine and auxiliary engine data Voyage plan and delay data

  5. The problem System A System B X

  6. The EXPRESS/STEP solution Prepared a Ship Operations Data Model in EXPRESS, ISO 10303-11 based on Høegh Fleet Services business cases in 1996. EXPRESS defines one exchange format independent of proprietary systems (software, hardware and operating systems) SW suppliers need standard solutions for exchange of data DNV wants standardised solutions for exchange of ship operational technical data (4000 ships) from ships to Nauticus/DNV Interface between ISO (European Marine STEP Association EMSA) and IEC standardisation (MiTS Forum)

  7. 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 in Ship Operations Data Model 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)

  8. Conceptual structure of Ship Operations Data Model Data collection reports Events Operational_data, Standard MiTS Tags Variables to be logged/recorded Noon_at_sea Sensor A Filled parts included in New Work Item (NWI) to ISO

  9. Standard tags IEC 1162… in ISO 10303-NWI Course (navigational data) A Course is a subtype 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.

  10. Engine Performance Test Demonstrator Shipboard operational database (EDIMAR, Marinor) Nauticus Høegh Marinor MiTS Gateway sensors Kongsberg NorControl Automation

  11. Fuel oil quality report demonstrator Shipboard operational database (EDIMAR, Marinor) DNV Petroleum Services, EPM Høegh EDIMAR, Marinor

  12. Barber International purchase system and requisition messages AMOS RAST Integration module, EXPRESS msg’s ASTRO shore office purchase system, Lysaker

  13. Proposalfor aNew Work Item (application protocol) to ISOTC184/SC4 onShip Operational Logs, Records, and MessagesSubmitted January 1998

  14. Scope (1): Standard tags and ship events Harmonisation with IEC 1162-4 standard tags related to operational data from the monitoring system covering navigational data equipment and machinery status data; environmental observations tank surveillance hull stress monitoring ship events and ship activities definitions for triggering collection of operational data from the monitoring system into standardised reports or non-standardised user defined reports. ;

  15. Scope (2): Standardised reports in NWI Fuel oil quality report from laboratory to the ship Bridge log Requisition messages for requisition, purchase and transport of spare parts to the ship Ship Survey Model (LR requested DNV to include this). The public part of the class related information (equipment maintenance and failures transferred to AP226)

  16. Scope (3) covers future scope as proposed in Ship Safety Record developed in USA

  17. Scope (3): Ship Safety Record Common format and definition of Ship Safety Record (SSR) data Maritime organisations, ship owners, operators, regulatory bodies, port/flag state Maintained by Operator who is required by ISM Code to keep such information Before arriving a port, authorities may request ship to submit subsets of SSR. Vessel particulars, Certificates, Crew, Voyage, Inspections, Incidents, Corrective actions, Reports Note: This is currently developed in ASTM F25.05.06 by SLCSI project in USA supported by MARAD. The standard is considered to be submitted as a New Work Item to ISO TC8/SC10 and will establish a guide and requirements to the SSR.

  18. Ship Safety Record (contents) a) vessel particulars; b) vessel status; c) crew requirements , the identification of crew positions, the corresponding license and training requirements, medical certificates, and required drills; d) crew status, the identification of crew members, their certificates, training and medical records, and working hours; e) voyage specific data, the voyage specific data including ports, cargo carried, loading pat-tern, ballast condition, and critical events; f) record of inspection, the record of incidents including port state restrictions, unscheduled downtime, near misses, and pollution incidents; g) record of incidents; h) corrective actions needed for the ship including procedures, equipment, documentation, and a deficiency log; i) reports including automatic identification system view, ship damage to coastal state.

  19. Ship Application Protocols AP 215 Ship arrangements AP 216 Ship moulded forms AP 217 Ship piping AP 218 Ship structures AP 226 Ship mechanical systems AP 234 Ship Operational Logs, Records and Messages

  20. Establishing consensus of PNWI 6 countries voted yes to participate, 11 to scope USA voted no, propose to move to TC8/SC10 Proposal for a Joint Working Group under TC8/SC10 is withdrawn from Beijing meeting (5-10. October) European Classification Societies (EMSA) need more time to consider the impact of TC8 leadership Need to clarify position of IACS Prepare for a solution in San Fransisco January 1999.

  21. ISO TC8/SC10 Ship Tech./Comp. Appl. IEC TC80/WG6 navigatnl, environmntl IEC TC18… machinery tags ISO TC184/SC4 STEP SOL-AP SSR? Supporting doc? WG 1 Fleet managmnt Ship Operational Logs, Joint Working Group IACS EMSA Projects: MARITIM: Ship Technology/Ship Operation DISC II: EU Demonstrator Ship Life Cycle Support Infrastructure SLCSI Ship Safety Record SOCP & RAM-SHIPNET MARVIN 5. Framework EU programs (interSOL) IMO

More Related