Stakeholders

The general activities, requirements, and responsibilities of the Master System Integration (MSI) Team are summarised as follows:

  • Facilitate the infrastructure, operational and technical integration between all of the systems from engineering, through construction and commissioning phase and throughout ORAT.
  • Provide a common coordination platform between Special Airport Systems, MEP, Architectural and the Client.
  • Coordinate with Campus-wide Master Systems Integrator, whose role is to ensure the systems within all campus buildings are seamlessly integrated.
  • To be active during different phases of the project until the final completion and handing over.
  • Airport
    • Airport ICS
    • Airport Ops/ORAT
    • Apron Operations
    • Airport Emergency Services
    • Performance Standards & Projects
    • Aviation Security
    • Operations Planning
    • Airport Air Navigation services
    • Airport Planning
    • Airport Engineering
    • Airport Facility Management
    • Airport Strategic Development
    • Airport Free Zone
    • Safety and Security
    • Duty-Free
    • In-flight Catering
    • Hospitality
    • Cargo
  • Project Teams
  • Major Airlines
  • Board of Airline Representatives
  • Airlines Operators Committee (AOC)
  • Local Telephone Company(s)
  • Customs
  • Immigration
  • Police
  • CID
  • Civil Aviation Authority (CAA)
  • Tourism Authority
  • Department of Transportation
  • Traveling Public / Meeters & Greeters
  • Airport Tenants/Concessionaires

 Introduction

The correct application of high technology systems is vital to the efficient and effective operation of any airport operation.  The SAS and ICT systems will become a key asset to Airport. The Contractor Shall ensure that the systems are designed for it properly to reflect the needs of its operations, and layout.

The Contractor Shall work with the regulatory authorities, international bodies and the airlines. 

A key consideration for any airport terminal project is system integration.  Integration brings enhanced performance, greater functionality, increased flexibility, reduced costs, reduced maintenance overheads, and system longevity.  However, experience has shown that true integration is difficult to achieve and is rarely successful unless it is managed robustly from the earliest stages of a project.  As a result, the Contractor Shall  pay particular attention to the system integration strategies, the integration of particular systems, interface testing and the overall ‘tuning’ of the integrated systems.  

At the heart of the airport’s information systems sit the Information Broker (IB) / Airport Operational Data Base (AODB). This is the central depository of data for the airport’s information systems.  The importance of the architecture of this database and its interaction with other systems cannot be overemphasized. As part of this strategy, the Contractor Shall establish an independent interface testing facility for the project. This facility would be used to test and prove all system software and hardware interfaces prior to site installation. The Contractor Shall confirm its understanding that some of the SAS/ICT systems for the expansion of the Airport must be interfaced with existing airport systems in a manner that is both seamless and does not cause any disruption to existing airport operations.  This will include interfaces to existing airfield, aircraft management and terminal systems (where applicable).

Finally, the Contractor Shall acknowledge the fact that the installation of many items of ICT equipment and the testing of the resultant systems cannot occur until very late in the construction period.  Sensitive high technology equipment should not be installed until a clean, stable and safe environment exists and it cannot be fully tested until services (e.g. electrical, HVAC) are operating. In effect, the installation of ICT equipment is on the project’s ‘critical path’ of activities and, as a result, can be a significant project risk.  The Contractor Shall confirm that he will take particular care to ensure that the subcontractor is instructed to model, check and test the ICT systems (especially the interfaces) before they are introduced to the site. 

Deployment of SAS and ICT Expertise and Experience

The Contractor Shall confirm its ability to design and manage the installation of the SAS and ICT systems for the Airport, with sufficient evidence.

The Contractor must demonstrate that he has specific experience in the design and implementation of each of the above-mentioned systems for airport clients.  In addition, the Contractor must demonstrate his experience of working with cutting edge ICT technologies for a wide range of non-airport clients. 

Early SAS and ICT Design Development Stage

During this Stage, the Contractor Shall perform planning the design of the SAS-ICT systems.  This Shall include preparing the strategic plan, the ICT design processes, and the activity planning schedule.  As part of this work, the Contractor Shall identify key stakeholders and design interfaces. Actual design work would commence with a review of existing information on the required ICT systems and a pre-design validation against the Scope Requirement.  To achieve this, the Contractor will be provided with access to stakeholders (where available) and experts on the existing airport special systems (if any) but under the supervision and approval by the Owner/Engineer. During this stage, the Contractor Shall begin to detail stakeholder/user requirements and their business processes. 

Discussions will also be held with the utilities design consultant to establish principles for the interconnection of the new facilities to airport campus telecommunications services. The MSI Shall also attend meetings with other utilities providers like electrical services, water services, and sewerage services to ascertain if there will be any interconnections. 

The Contractor Shall prepare and detailed report at the end of this Stage for approval by the Owner/Engineer.

Draft Final SAS and ICT Design Development Stage

The Draft Final Design development stage Shall be used to review each system in terms of its purpose, scope, performance, physical extent, core technology sets, logical connectivity requirements, and interfaces and outline specifications.  Overall system architectures Shall be designed (including the vertical integration of networked services).  Outline systems diagrams Shall be prepared to indicate the major components of each system and their inter-relationship with other equipment and systems (including existing airport systems). Solutions to issues such as the separation of network services and network security Shall be developed.  RF frequency planning will be undertaken, and wireless propagation estimates Shall be made. The stage Shall begin to detail the energy and space requirements for each system and this information will be coordinated with the emerging designs for the other aspects of the Airport design (e.g. architectural and MEP).

A connectivity study Shall be undertaken to begin the design of the SCN and ascertain its overall topology. A challenge to ICT specialists working on new developments in the absence of a user community who can provide details of day-one user ICT requirements, and as such, the Contractor Shall prepare a detailed list of Assumptions he has made to address requirements where users have not been named. Likewise, it is common to find that stakeholder representatives are unable to define detailed business processes at such an early stage of the design (especially against the background the rapid evolution of ICT products) and as such, the Contractor Shall prepare a detailed list of Assumptions he has made to address requirements.

The Contractor Shall prepare and detailed report at the end of this Stage for approval by the Owner/Engineer.

Final SAS and ICT Design Development Stage

This stage Shall commence with value engineering and system integration workshops.  This will review the agreed design deliverables and seek opportunities to add value to the eventual systems.  This review Shall also be used as an opportunity to check sustainability issues. A detailed coordination exercise Shall be held with the other disciplines to capture any outstanding network connectivity requirements.  Network traffic estimates Shall be prepared and a network management plan developed. A particular issue will be to capture configuration requirements for the primary databases (e.g. AODB). Any outstanding special studies Shall be undertaken at this time. The Contractor is expected to review detailed deliverables from this stage of the design including schematics and detailed systems architectures, plans and layouts, configuration schedules and interface stacks.  Further, design review Shall include detailed technical specifications for each of the individual systems, including final design, equipment selection, initial assembly, site installation, and testing instructions.

The Contractor Shall prepare and detailed report at the end of this Stage for approval by the Owner/Engineer.

Construction Stage Design Inputs

During the initial period of this stage, the Contractor Shall take particular care to monitor and review the various sub-contractor / manufacturer’s submittals to ensure their compliance against the design intent. The Contractor Shall take care to monitor material submittals and check that any product changes maintain the overall needs of the project.

The Contractor shall take particular care in the review of sub-contractor/manufacturer’s development of system interface designs (e.g. as detailed on their ‘shop drawings’) and to identify all the system interface issues as early as possible and ensure that the subcontractor has a formal methodology for their design and testing.