IALA E-140 : 2ED 2015

Proposes that National Members, and other appropriate Authorities providing marine aids to navigation services, establishing shore-based infrastructure for e-Navigation:1. Use the principles of a Service-Oriented Architecture (SOA) when designing and implementing their shore-based system(s): a SOA is a design pattern in which application components provide services to other components via a communications protocol typically over a network. The principles of service orientation are independent of any vendor, product or technology.2. Use user-requirements driven system design, including statements on human-centred design and/or quality levels of service, and a system engineering process: only clearly and consistently stated user requirements result in the technical service provided.3. Use information-orientation design for system layout: all technical solutions based on data modelling as a rule.4. Employ the principles of modularity and encapsulation, while preserving a holistic view of the system’s intended functionality.5. Apply a harmonized and ideally uniform model for all technical services provided by the system, regardless of technology, thus exploiting commonality.6. Use specifications from international standards to the largest extent possible and procure technical solutions based on functional specifications as a rule.7. Adhere to open system architecture and focus on open and standardised interfaces between components and services: avoid proprietary interfaces as a rule.8. Employ remote access techniques where feasible in order to allow for minimum number of technical operation and maintenance centres: components without remote access capabilities should be avoided as a rule.9. Implement life-cycle management: full life-cycle coverage of technical proposals should be considered before accepting them. Life-cycle management also prevents ‘quick-fix-solutions’ with their associated long-term costs.10. Document each and every functional aspect, ideally in a uniform overall documentation system: this is a pre-requisite for any quality management system.11. Provide role-based access to the components of the system: in particular, roles and personnel for technical operation and maintenance tasks on one hand and roles and personnel for system development and optimisation tasks on the other hand should be differentiated.12. Take into account regulatory constraints when designing the system architecture, and consider possible consequential amendments to existing regulations based on the development of that system architecture.13. Consider supporting concepts such as certification in general, quality management system in accordance with ISO 9001 series, environmental management in accordance with ISO 14000 series, IT security certification in accordance with ISO 27000 series, and the IMO Member State Audit Scheme (IMSAS).14. Introduce policy, change control, and operational governance structures to consistently adapt to ongoing developments, as appropriate and supportive of the above individual items.