radio technical commission fmiti s ifor maritime servicesrtcm.info/enav/185-2012-enav-027.pdf ·...

Radio Technical Commissionf M iti S ifor Maritime Services2012 Annual Assembly Meeting and Conference2012 Annual Assembly Meeting and Conference

Captain Joe RyanTHE SKIP’R, LLC (Norfolk, VA USA)

Chairman

Agenda

• e-Navigation Steering Committee

• SC 109 on Electronic Charting Technology

• SC 112 on Ship Radar

• SC 121 on AIS and ASM

• SC 129 on Portrayal of Navigation-related Informationy g

• SC 130 on EOIS

• SC 131 on Multi-system Navigation ReceiversSC 131 on Multi-system Navigation Receivers

2012 RTCM Annual Assembly Meeting and Conference 2


e‐Navigation Steering Committee


g

Chairman

e-Navigation Steering Committee

Established December 6, 2007 as an “Oversight Committee”under § 8 b of the RTCM Bylawsunder § 8.b of the RTCM Bylaws

• Advises the Board of Directors of significant activities in the area of e-Navigation and makes recommendations asthe area of e-Navigation and makes recommendations as to areas for study by Special Committees… by, for example:

– identifying issues for RTCM to take up

– preparing Terms of Reference for Special Committees

• Although a Board committee, membership is not limited to board members


Report on Issues Raised to the Board

The specification of NMEA standards in RTCM standardsRTCM Papers: 014-2012-eNav-019 (#4)p ( )

054-2012-BD-477 (#4.F.a.)058-2012-eNav-020 (#4)

• RTCM systems/equipment shall accept data: “in accordance with at least one NMEA interface standard”“in the following formats, according to the applicable standard(s)”

• RTCM standards shall specify both: “NMEA sentence formatter(s)” and“NMEA sentence formatter(s)” and“NMEA network message PGN(s)”

The verbiage selected was decided by collaboration between the RTCM e-Navigation Steering Committee Chair and the NMEA Technical Director.


Report on Issues Raised to the Board

The Board directed the e-Navigation Steering Committee to:

• “guide the eNavigation group Sub-Committees”

• without change to the RTCM Standards Development PoliciesRTCM Paper: 117-2005-BD-385RTCM Paper: 117-2005-BD-385

The e-Navigation Steering Committee Chair has provided guidance to SC 109 (for 10900.6) and SC 112 (for 11201.2).


Coordination of Standards Development

• Consistent Scope– Generic verbiage that does not “assume” for national authorities…

• Consistent Structure– References

• Provisions (i.e., “applied” standards)

I di ibl D t (i di tl f d d t )• Indispensible Documents (i.e., directly referenced documents)

• Useful Documents (i.e., indirectly referenced documents)

• Other Documents (i e used but not otherwise referenced)• Other Documents (i.e., used, but not otherwise referenced)

– Terms & Definitions



• Consistent Structure (cont’d)– Application of International Standards

• IEC 60945

• IEC 62288• IEC 62288

• ClassesF (i th l “ ti l)– Four (i.e., three plus “recreational)

• NMEA StandardsI f d d– Interface standards“shall comply with at least one NMEA interface standard”

– Installation standards…



• Methods of Testing– “manufacturers must make available test documentation demonstrating

compliance with…”

• Applicable clauses of international standardspp

• NMEA interface standards


Stability of IEC “General” Standards

IEC 62288 Ed.27/25/14

IEC 62288 Ed.17/25/08

' 08 2008 2009 2010 2011 2012 2013 2014 ' 14

IEC 60945 Ed.4.0 Corrig.14/14/08

IEC 60945 Ed. 4.0 Corrig.1 -----------------------Apr.2008-Apr.2015IEC 62288 Ed.1--------------Jul.2008-Jul.2015IEC 62288 Ed.2--------------


Stability of IEC “ECS-related” Standards

IEC 61993‐2 Ed.28/24/12

IEC 62376 Ed.19/16/10

IEC 61174 Ed.39/26/08

' 04 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 ' 15

TodayIEC 61996‐2 Ed.211/21/07

IEC 62376 Ed.1---------------Sep.2010-Sep.2014IEC 61174 Ed.3---------------Sep.2008-Sep.2015IEC 61996-2 Ed.2------------Nov.2007-Nov.2017IEC 61993-2 Ed.2------------Aug.2008-Aug.2018

M d ith Offi Ti li 2010 ffi ti liMade with Office Timeline 2010 www.officetimeline.com


Stability of IEC “Radar” Standards

' 04 ' 15

IEC 61993‐2 Ed.28/24/12

IEC 62376 Ed.19/16/10

IEC 62288 Ed.1/Ed.27/25/08

IEC 62388 Ed.1/Ed.212/13/07

IEC 61996‐2 Ed.211/21/07

IEC 62252 Ed.17/20/04

' 04 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 ' 15

TodayIEC 61174 Ed.39/26/08

IEC 60945 Ed.4.0 Corrig.14/14/08

IEC 62388 Ed.1/Ed.2--------------Dec.2007-Dec.2013IEC 62252 Ed.1-----------------Jul.2004-Jul.2014

Made with Office Timeline 2010 www officetimeline comMade with Office Timeline 2010 www.officetimeline.com


e-Navigation Paper/Presentation

RTCM – Moving Forward with eNavigationRTCM Paper: 067-2012-eNav-026.r4p



Special Committee 109Electronic Charting Technology


g gyBob FeatherFeather Soft (Portsmouth, VA USA)

Chairmanan Associate of THE SKIP’R, LLC

Chairman

10900 Standard Notional Schedule

• Fall 2012 Complete 10900.6 CDV

• Fall 2013 Complete 10900.7 CDV

• Fall 2014 Complete 10900.8 CDV p


10900.6 Work Program

• Voyage Data Recording

• Software Updating

• Low or doubtful data integrity indication

• Generic computer hardware

• Coordinate with SC 121 for AIS requirementsq

• Coordinate with SC 112 for radar requirements– Advanced from 10900.7


Voyage Data Recording

• Considered application of IEC 61996-2 on Simplified Voyage Data Recorders (S-VDR)Voyage Data Recorders (S-VDR)– Received USCG request and recommendations

– Completed review of IEC 61996-2Completed review of IEC 61996 2

– Indentified clauses for “provisions”

– In the process of applying “clarifications”p pp y g

• Will be included in 10900 6 CD for CommentWill be included in 10900.6 CD for Comment


Software Updating

• Develop an ECS software cross-reference/matrix– Review IMO MSC.1/Circ.1389

– Review IMO SN.1/Circ.266/Rev.1

• Deferred to 10900.7


Data Integrity

• Considered data integrity issues– Reviewed IEC 62376

– Determined additional 10900.5 verbiage to be unnecessary…deleted

• Will be included in 10900.6 CD for Comment


Generic Computer Hardware

• Develop hardware cross-reference/matrix– Review IEC 62376

– Review IEC 60945



Coordinate with SC 121

• Consider restoring verbiage related to AIS binary messaging deleted from 10900 5 CDVdeleted from 10900.5 CDV – Received and reviewed 12100.0 CD and CDV

– Reviewed deleted verbiageReviewed deleted verbiage

– In the process of restoring deleted verbiage…

• Will use the term “ASM” in lieu of “binary messaging”y g g

• Will be included in 10900 6 CD for CommentWill be included in 10900.6 CD for Comment

• Will also be identified for review by NMEA… verify list of sentence formatters & network message PGNs– verify list of sentence formatters & network message PGNs



• Consider requirements for radar video images– Received and reviewed 12100.0 CD and CDV

– Radar video images not yet specified

• SC 112 waiting to identify NMEA OneNet video formats• SC 112 waiting to identify NMEA OneNet video formats

• Will address with SC 112

• May be included in 10900.6 CDV


Additional Steering Committee Direction

• Revise as directed– Revised Scope

– Revised References

Revised Terms & Definitions– Revised Terms & Definitions

– In the process of applying International Standards

– In the process of adding a fourth classIn the process of adding a fourth class

– Revised verbiage related to NMEA interface standards

– Added verbiage related to NMEA installation standardsg

• NMEA 0400 does not yet address ECDIS or ECS, only chart plotters

– Have not yet addressed methods of testing


Revised Work Program

• 10900.6– Coordinate with Steering Committee and SC 112 for:

• Application of IEC 60945

• Application of IEC 62288• Application of IEC 62288

• AIS/radar target association

• NMEA sentence formatters and network message PGNsNMEA sentence formatters and network message PGNs

• Radar video images



• 10900.7– Coordinate with SC130 for EOIS requirements

– Consider dynamic adjustment of depth data using AIS ASM

Incorporate IEC 62288 Ed 2 0– Incorporate IEC 62288 Ed. 2.0

• 10900.8C di t ith SC 129 f dditi l t l i t– Coordinate with SC 129 for additional portrayal requirements


Revised Notional Schedule

• Fall 2012 Complete 10900.6 CD for Comment

• Spring 2013 Complete 10900.6 CDV

• Spring 2014 Complete 10900.7 CDV p g p

• Fall 2015 Complete 10900 8 CDVFall 2015 Complete 10900.8 CDV


Upcoming Meetings

November 2012?

Identification of ASM– Identification of ASM

– Review in preparation of CD for Comment

January 2013?

– Joint meeting with Steering Committee & SC 112

• IEC 60945 allocation by class

• IEC 62288 allocation by class– AIS/radar target associationAIS/radar target association

• NMEA sentence formatters & network message PGNs

• Radar video imagesRadar video images



Special Committee 112Ship Radar


pBrian VladRaymarine (Merrimack, NH USA)

ChairmanChairman

11201 Standard

New Version 2.0 of:RTCM Recommended Standards for Marine Radar EquipmentRTCM Recommended Standards for Marine Radar Equipment Installed on Ships of Less Than 300 Tons Gross TonnageRTCM PAPER 71-95/SC 112-STDV i 1 1 (1995 10 10)Version 1.1, (1995-10-10)


11201.2 Standard Notional Schedule

• Winter 2012 Complete 11201.2 CD for Comment

• Summer 2012 Complete 11201.2 CDV


11201.2 Work Program

• Use IEC 62388 as the basis for the new edition– Consider IEC 62252

– Consider RTCM PAPER 71-95/SC 112-STD

C di i h SC 130 f EOIS i• Coordinate with SC 130 for EOIS requirements


11201.2 Status

CD for Comment circulated (closing date of 31 Oct)(closing date of 31 Oct)

Open itemsChart display– Chart display

– AIS/radar target association

– Screen sizes and resolutionsScreen sizes and resolutions

– Distribution of radar video images

– Power ratings

– CARPET simulations



• Consider requirements for EOIS positioner (and camera) control (e g for LOPs)control (e.g., for LOPs)

• 13000 standard not sufficiently developed




• Format as directed– Preliminarily addressed scope

– Formatted references

Formatted terms & definitions– Formatted terms & definitions

– Applied international standards

– Accounted for four classesAccounted for four classes

– Adopted verbiage related to NMEA interface standards

– Adopted verbiage related to NMEA installation standardsp g

– Preliminarily addressed methods of testing



• 11201.2 CDVAdd P ti & CARPET i l ti– Address Power ratings & CARPET simulations

– Incorporate IEC 62388 Ed. 2.0 CDV

– Coordinate with Steering Committee and SC 109 for:Coordinate with Steering Committee and SC 109 for:• Application of IEC 60945

• Application of IEC 62288

• Chart display

• AIS/radar target association

• Screen sizes and resolutionsScreen sizes and resolutions

• NMEA sentence formatters and network message PGNs

• Radar video images



• 11201.3– Coordinate with SC130 for EOIS requirements

– Incorporate IEC 62288 Ed. 2.0

11201 4• 11201.4– Coordinate with SC 129 for additional portrayal requirements


Revised Notional Schedule



• Fall 2015 Complete 11201.4 CDVp


Upcoming Meetings

December 2012?

– Adjudication of CD comments

January 2013?

– Joint meeting with Steering Committee & SC 109



– Chart display

– AIS/radar target association

– Screen sizes and resolutions

• NMEA sentence formatters & network message PGNs

• Distribution of radar video images



Special Committee 121 AIS & ASM

Captain Joe RyanTHE SKIP’R, LLC (Norfolk, VA USA)Brian TetreaultUSACE Coastal & Hydraulics Laboratory

Chairman(Vicksburg, MS USA)

Chairman, ASM TWG


• Fall 2011 Complete 12100.0 CD for Comment



12100 Standard

“This Standard specifies the minimum requirements for the development of new Application-Specific Messages (ASM) anddevelopment of new Application-Specific Messages (ASM) and methods to qualify them against those requirements.”

“It is intended for use by national competent authorities inIt is intended for use by national competent authorities in determining which whether ASM to should be allowed for transmission in their jurisdictions designated area(s).”


12100 Outline

• Requirements

– General• Parameters

• Structure

• DocumentationDocumentation

– AIS• Parameters

• Structure

• Documentation

– VDSMS• Structure

• Methods of Qualification

• Checklists2012 RTCM Annual Assembly Meeting and Conference 42

12100.0 Status

• CDV circulated ( l i d t f 31 O t)(closing date of 31 Oct)



• Format as directed– Have not yet revised scope

– Formatted references

Formatted terms & definitions– Formatted terms & definitions

– International standards are not applicable

– Classes are not applicableClasses are not applicable

– Interface standards are not applicable

– Installation standards are not applicablepp

– Addressed methods of qualification


Report on International ASM

Qualification of ITU-R M.1371 (IFM 0 & 2 thru 5) and IMO SN 1/Circ 289 (FI 16 thru 32)IMO SN.1/Circ.289 (FI 16 thru 32)

• Completed initial evaluation against 12100.0 CDV

• In the process of adjudicating evaluations and identifying edits to• In the process of adjudicating evaluations and identifying edits to 12100.0 CDV– 4.1.1.1

“A ASM h ll h i t ”“An new ASM shall have a version parameter…”

– 4.1.3“Each ASM shall be documented. The documentation shall should include…”

– 4.2.3.1“The documented purpose of an AIS ASM shall should include guidance for its operational use…”


Pending Work

• Review other messages:– USACE Lock & Dam Status


Upcoming Meetings

December 2012?

Steering Committee– Steering CommitteeAdjudication of CDV comments

January 2013?

– Review of CDV adjudication?




Chairman

SC 129 on Hiatus

• Status– Awaiting IEC 62288 Ed. 2.0

– CDV 2013-02?



Captain Joe RyanTHE SKIP’R, LLC (Norfolk, VA USA)Pat RichardsonFLIR (Santa Barbara, CA USA)

ChairmanChairman


• Winter 2012 Complete 13000.0 CD for Comment

• Summer 2012 Complete 13000.0 CDV


SC 130 Work Program

• Develop the 13000.0 Standard for EOIS

• Determine the types of data required to interface EOIS with other navigational systems and equipment

D i h f i d f h h f d• Determine the formats required for the exchange of data between EOIS and other navigational systems and equipment q p– Make recommendation to NMEA

• NMEA 0183

• NMEA 2000

• Develop the 13001.0 Standard for interfacing with EOIS


No Report



Special Committee 131Multi‐system Navigation Receivers


y gCDR Harry WilsonUSCG (Washington, DC USA)

ChairmanChairman

Issues

• GNSS– Receiver Automated Integrity Monitoring (RAIM)

– Interference, jamming and spoofing

C bi d di i i i• Combined radio-navigation receivers– GNSS

A t ti• Augmentation

– Terrestrial

C t i• Component receivers


GNSS

• The 61108 (series) standards do not provide sufficient requirements for or guidance with respect to:requirements for, or guidance with respect to:– RAIM

• especially across the GNSS constellationsespecially across the GNSS constellations

– signal interference, jamming and spoofing


Combined Radio-navigation Receivers

• Combined radio-navigation receivers can result in improved positioning performanceimproved positioning performance…– IMO promulgates Performance Standards for:

• GPS [MSC.112(73)]GPS [MSC.112(73)]

• GLONASS [MSC.113(73)]

• DGPS & DGLONASS [MSC.114(73)][ ( )]

• Combined GPS & GLONASS [MSC.115(73)]

• Galileo [MSC.233(82)]

– IMO will develop new Performance Standards forMulti-system Shipborne Navigation Receivers [MSC 90/28]


… New IMO Performance Standards

IMO MSC 90 is directing NAV 59 (2013) to“develop new performance standards for maritime receiversdevelop new performance standards for maritime receivers that can use a number of different radio-navigation systems, or combinations of systems” ll i i l h k [MSC 90/28 25 25]allocating two sessions to complete the work [MSC 90/28, 25.25]


SC 131 Work Program…

• Should SC 131 develop a requirements for Multi-system Shipborne Navigation ReceiversMulti-system Shipborne Navigation Receiversas a precursor for IMO Performance Standards? – Should those requirements constitute an RTCM standard?



• Should SC 131 develop requirements/guidance with respect tointerference related to GNSS receivers?interference related to GNSS receivers?– Should those requirements constitute a separate RTCM standard ?

– Should those requirements be incorporated into the standard forShould those requirements be incorporated into the standard for multi-system shipborne navigation receivers (e.g., as an Annex)?



• Should SC 131 develop requirements/guidance with respect toRAIM related to GNSS receivers?RAIM related to GNSS receivers?– Should those requirements constitute a separate RTCM standard ?




• Should SC 131 develop a requirements for component receivers?component receivers?– Should those requirements constitute a separate RTCM standard ?



Upcoming Meetings

• Oct/Nov/Dec?– Review TOR [RTCM Paper 066-2012-SC131-001]

• Recommend any changes to the Board of Directors via the e-Navigation Steering Committeeg g

– Input must be submitted to the Board of Directors prior to 13 Dec

– Draft Work Program

• Align notional schedule to provide input to IMO NAV?


Other Business
