Lloyds Register updated PowerPoint template style Marine default

1
Harmonising onboard information
Brian Sherwood JonesJonathan Earthy
2
Outline of talk

• e-nav as a harmonisation process
• Definitions and concepts
• Plotting a route ahead
• The harmonised zone
• Some initial barriers to starting harmonisation
• Organisational concerns role of the OOW, the
  race for usability
• The formal technical context what to
  standardise?
• Harmonising onboard information through-life
• Basis for harmonisation
• Required approach
• Scope and content of SCC notation

3
Definitions and concepts

• e-Navigation is the harmonised collection,
  integration, exchange, presentation and analysis
  of maritime information onboard and ashore by
  electronic means to enhance berth to berth
  navigation and related services, for safety and
  security at sea and protection of the marine
  environment.
• The concept of e-Navigation was proposed by IMO
  Member States in 2006 as a process for the
  harmonisation, collection, integration, exchange
  and presentation of maritime information.
• e-Navigation is a process that seeks to reassess
  (these) roles and ensure that mariners and shore
  operators are actively engaged in the process of
  navigation and not just monitoring it.

4
Plotting a route ahead
5
Can we avoid this please?
6
The harmonised zone
7
External influences
8
Organisational context
9
Formal technical context
10
Some initial barriers alarms and lack of
usability assurance
11
The race for usability
12
What is the role of the OOW / Bridge Team?
13
What to standardise when there is innovation?
14
Guidance for harmonisation
15
Lack of harmonisation onboard now
16
Consoles
17
Dimming
18
Integration work. Crew fixes gap between design
and operation
19
Impact on night vision and safe
watchkeeping(Sachdeva)
Does glow from the alarm display panels,
indicators and visual display units affect your
night vision and safe watch ability?
20
More serious integration work
21
Usability issues for equipment design

• Type approval and usability/ergonomics IEC 60945
  and non-testing.
• SOLAS V/15, Bridge Resource Management vs. One
  Man Bridge Operation and head-down mode.
• Incident analysis mode awareness, task
  performance, familiarisation.
• Basic ergonomics consoles, layout. Try to
  improve bridge design.

22
Objectives of SCC Notation

• Ship Control Centre Navigation bridge
  operational functions as appropriate e.g. OSV,
  PSSC, stern-acting tankers, office, cargo
  control.
• Less prescriptive more goal-setting for bridge
  design and equipment arrangement to allow for
  innovation.
• More user-centred and responsive to SOLAS V/15.
• Address the bridge system, and build links
  between the technical system and the human
  element.
• New approach to integrated systems.

23
Scope of SCC
SCC
24
Why SCC now? - baseline established

• Risk of collision, grounding, stranding continues
  to be significant. Automated bridges bring their
  own problems.
• IACS discussions on approach to SOLAS V/15
  concluded. Clarification of visibility
  requirements from SOLAS V/22.
• SN.1/Circ.265 Guidelines on the application of
  SOLAS Regulation V/15 to INS, IBS and bridge
  design published.
• No prospect of useful IMO Performance Standards
  for INS, IBS.
• Updated ISO 8468 published. Developments in IEC
  standards inc. 62288.

25
Need to allow for innovation
26
Balance to be found

• Enough guidance to be useful but without being
  too prescriptive.
• Use goals/risks/principles to allow for
  innovation but be specific enough to allow for
  limited capabilities in some sectors.
• Use by mainstream plan approval surveyors.
• An operability case is new.
• Use of process requirements is new.
• Through life linkages.

27
Technical background - usability

• ATOMOS I - IV
• ISO 17894 (now developed to Dependable Systems
  Review).
• BRM guidelines SN.1/Circ.265, ISO8468, IEC62288.
• MTO Sea project.
• Alarm design and management (Alert concept).

28
Technical background - dependability
Requirements of ISO 17894

• The system shall be demonstrably suitable for
  the user and the given task in a particular
  context of use.
• It shall deliver correct, timely, sufficient and
  unambiguous services to its users and other
  systems.
• The components of the system shall perform
  correctly throughout the systems lifecycle.
• Typically, isolated attempts to achieve this
  occur in safety, human element, integration,
  documentation and quality management.

29
Technical background dependability
30
Structure and content - 1

• 1. General
• 2. Plans and documentation
• Yard
• Bridge integrator
• Operator documentation
• 3. Bridge functions
• 4. Bridge environment
• Movement, consoles, chairs
• Noise, vibration, lighting,
• Interior, safety, stowage
• Visibility

31
Structure and content - 2

• 5. Bridge systems and equipment dependability
• 6. Bridge systems and equipment usability
• Controls
• Displays
• Alarms
• 7. Primary bridge functions Navigation
• 8. Additional bridge functions
• 9. Additional bridge functions - Offshore
  support
• 10. Additional bridge functions - Double acting
  ships

32
Structure and content - 3

• 11. Additional bridge functions - Rescue
• 12. Additional bridge functions - Fire fighting
• 13. Additional bridge functions Passenger
  safety
• 14. Additional bridge functions
  Office/administration
• 15. Testing, trials and surveys

33
Operating philosophy

• Roles and responsibilities of the bridge team and
  pilot under all operational conditions.
• Including
• task assignments, transfer of control,
  transitional arrangements when operational
  conditions change,
• cross-checking and supervision, use of trainees,
• response to alarms, operation under failure
  conditions.

34
In summary

• Address the real risks
• Allow for innovation
• More user-centred approach
• Allow for range of operational functions in SCC
• Based on long-standing research and standards
  development.

35
Thank you, any questions?
For more information, please contact Lloyds
Register 71 Fenchurch Street London, EC3M 4BS T
44 (0)207 423 2304E jonathan.earthy_at_lr.org
The Lloyds Register Group works to enhance
safety and approve assets and systems at sea, on
land and in the air because life matters.
36
Charts and radar screen commerce and usability
37
NMRI INT-NAV (Fukuto et al)
38
NMRI INT-NAV imagery (from earlier installation)
39
Information requirements - Yard

• GA, description
• Bridge drawings
• Workstations
• Visibility, windows
• Lighting, ventilation, heating
• Block diagrams
• Equipment list
• Dependability information

40
Information provision and assurance

• GA, description
• Bridge drawings
• Workstations
• Visibility, windows
• Lighting, ventilation, heating
• Block diagrams
• Equipment list

• Restrictions on intended operation
• Bridge functions, operating philosophy
• Competency for personnel involved in
  developing, maintaining, using system
• Quality system
• Integration and test plans
• Requirements spec

• Block diagram
• Operating manuals
• Operating philosophy
• Training requirements
• Familiarisation requirements

• SN.1/Circ. 265 evidence for SOLAS V/15 (BRM)
• Evidence that tasks have been considered in the
  design (including visibility)
• Usability assessment
• Life cycle documentation, records
• Evidence of dependability

41
Testing, trials and survey

• 15.1 General
• 15.1.1 Any uncertainty regarding achievement of
  safe and effective operation is to be resolved to
  the satisfaction of the surveyor by testing with
  representative users.
• 15.1.2 The system is to be surveyed through life
  at periodical surveys. Information on alterations
  and amendments is to be in accordance with Part
  6, Chapter 1, 1.4 as appropriate.

42
Operator documentation

• Block diagram
• Operating manuals
• Operating philosophy
• Training requirements
• Familiarisation requirements

43
Bridge integrator information

• Restrictions on intended operation
• Bridge functions, operating philosophy
• SN.1/Circ. 265 evidence for SOLAS V/15 (BRM)
• Evidence that tasks have been considered in the
  design (including visibility)
• Usability assessment
• Competency for personnel involved in
  developing, maintaining, using system.
• Quality system
• Integration and test plans
• Requirements spec
• Life cycle documentation, records
• Evidence of dependability

44
Bridge for the Nintendo generation