Specialist Airport Systems / Master Systems Integration

 

(Note: MSI, SAS MSI, Contractor – are used interchangeably but refer to the same entity. These terms should be normalized depending on the Owner definitions.)

Introduction

The following sections generally define what is expected of the Contractor. It is the minimum requirements and Shall be viewed as such.

Scope of Work for Master Systems Integration

Scope of works for Special Airport System MSI Team covers the integration and project delivery coordination support for the SAS systems and the interfaces connecting SAS to other systems of MEP, Utilities and Architectural works.

The activities of SAS MSI are as follows:

  • PMO for the proposed experts (schedule, reporting, System Assurance, Document control)
  • Capture Stakeholders requirements,
  • Develop ConOps & IT Model, ICDs, RAM program, Master Test Plan, Integration plan in line with ICT Master plan
  • Perform Technology briefings every 6 months
  • Configuration & Asset data acquisition for SAS
  • Review & amend existing specifications (systems, interfaces) if needed
  • Review & provide comments on existing/new system architecture/design
  • Review & provide comments on vendors Testing procedures & method statements
  • Define requirements for Training, O&M Manuals,
  • Design LAB Test environment and support vendors for their tests & reports
  • Testing & commissioning: support vendors for their tests & reports
  • Attend ORAT if required

The systems of the SAS group may be classified into the following groups:

  • Airport Operations Systems
  • Security Screening Equipment
  • Passenger Processing System
  • Immigration System
  • Passenger Information System
  • Information Technology System
  • Security Systems
  • Hold Baggage Screening System

 Overall Approach

The Contractor Shall use a variety of tools and techniques that will ensure a fully integrated and operationally friendly suite of end-user computers, servers, databases, gigabit Ethernet network, building services command and control equipment (like Building Management System, Fire Alarm System, Security, and Access Control to name a few).

The tools and techniques utilized for the design development of an integrated environment include Detailed Design Documents / Interface Control Documents, IP Addressing Schemes and Interface Activity Schedules. The process of assembling this information will be structured around an Interface Control Working Group (ICWG) made up of all stakeholders and providers of the various systems. The output from this Interface Control Working Group will be final design documents that are all approved and signed by the interfacing parties and submitted to the Employer/Engineer for approval.

The Contractor Shall Provide a unified Graphical User Interface (GUI) Template that will be accomplished via a variety of computer technology tools including; servers, databases, middleware, protocol converters, network interface devices, and application software.

Integration Approach

The Contractors MSI Team Shall verify that the proposed design(s) sufficiently responds to the concept of operation that it serves.

Operational capability is the processes that the Stakeholder performs to provide an operational outcome e.g. departure of passengers and bags. The primary objective is to deliver operational, safe and maintainable capabilities to support the stakeholder’s process in delivering the operations.

 Integration Life Cycle

The Contractor Shall use the V model of systems development. It is important to note that the V model starts with the concept of operation, which will either be received from the Employer or developed jointly with the Stakeholders formulating their requirements.

The concept of operation is the cornerstone as it enables us to define in turn the use cases for the corresponding systems which will be the ultimate test as to the delivered system meeting the requirements.

The next level down in orange corresponds to the system-level integration which will mainly lead to overall technical performance and availability verification when subsystems are connected.

The next level down in yellow corresponds to the site acceptance of each individual subsystem is installed which is a key element mandatory to enable to test when connected.

Project Overview

Early in the project, the Master System Integrator Shall develop the systems integration approved interfacing protocols document which will be submitted to the Employer/Engineer for approval. Upon approval, this document will be issued to all systems providers to further guide them in the equipment selections. This will ensure that systems providers submit systems that can be integrated. The Master Systems Integrator Shall review and endorse all systems prior to the material submitted to the Employer/Engineer.

The Master System Integrator Shall provide a detailed System Integration Program which will drive the systems development to ensure the integration activities meet the overall project program.

Templates of the Detailed Design Documents / Interface Control Documents, IP Addressing Schemes and Interface Activity Schedules Shall be provided to the Employer/Engineer for approval. These templates will then be provided to all systems providers and will be the first order of business for the Interface Control Working Group (ICWG).

The Contractor Shall provide System Integration Method Statements for the pre-commissioning, testing, commissioning and final testing of the Systems Integration environment.

During the Testing and Commissioning Phase, the Master Systems Integrator Shall be responsible for Failure Mode Testing. Considering the integrated environment, should a system restart or need some software maintenance, it is important to know the impact on the integrated environment. This activity will ensure that fall back documentation and procedures are available should the situation arise.

The Contractor Shall be responsible for the Training of the Employers Staff to understand the complete Systems Integration Environment.

The Contractor, briefly summarized in this document, Shall be responsible for the following key elements of the works:

  • The MSI is to facilitate the integration between all of the systems starting from the shop drawing engineering phase, through the construction and the commissioning phase, and throughout ORAT.
  • MSI Shall lead the process of developing and finalizing the DDD’s/ICDs between all systems and shall present them to the client for approval. The Contractor Shall also lead the process of capturing all of the external system interfaces.
  • The Contractor Shall capture system operational requirements and distribute to each system the required parameters for each user interface and commissioning/configuration function. These will be seamlessly incorporated into the Detailed Design Documents / Interface Control Documents and form part of the Operational Readiness and Trials (ORAT) process.