TIA ICT – Detailed Design Gap Analysis

Workshop
TIA ICT – Detailed Design Gap
Analysis

Objective
CCMC Detailed Design Documents :
Speed Up , Higher Quality
Date: 22 Jan 2024
Venue: PMC Meeting Room
TIA ICT – Detailed Design Gap Analysis

Agenda
Part 1 : Introduction
• Why
• The Value Creation

Part 2: Our Observation & Suggestion

Part 3: Action Plans

• Detailed Design Train and Trainer Program
• Revised submission schedule
TIA ICT – Detailed Design Gap Analysis

PART 1
TIA ICT – Detailed Design Gap Analysis

TIA ICT Program Life Cycle

Level
of Execution
Activity Processes

Planning
Processes Controlling Closing
Processes Processes
Initiating
Processes

Project Start Project End Time

We are here
4
TIA ICT – Detailed Design Gap Analysis

Why 1?
Contractual Obligation

• Every major ICT sub-systems mentioned in F & P specifications

• First submission submit for PMC review , from 60% to 90%
TIA ICT – Detailed Design Gap Analysis

Why?
Faster ICT deliverables handover

• Every ICT system deliverables

need to conduct
comprehensive training
inclusive of Detailed Design to
• System Administrator
• Maintenance Staff
• Operational Staff
TIA ICT – Detailed Design Gap Analysis

Why?
Faster ICT Contract Closer

• Every ICT system deliverables

need to be signed off
TIA ICT – Detailed Design Gap Analysis
Why?
Poor ICT design increase Total Cost of Ownership

Investment $
Case Study :
An
International
Airport ICT
Infrastructure CoA
Total Cost of
Ownership is Price of Entry
20% of initial
investment
every year.
Time T1 T2 T3 T4 T5

What is your 600m project cost 120m annual maintenance!

Response ?
PROJECT OPERATIONS Upgrade OPERATIONS
Design & Build
8
 System Engineering
TIA ICT – Detailed Design Gap Analysis
Why?
System Engineering
• System Engineering
integrates all disciplines and
specialty groups into a team
effort forming a structured
development process that
proceeds from concept to
production to operation
• System Engineering considers
both business and technical
needs of all customers with
the goal of providing a
quality product that meets
the users needs
www.incose.org
One of the many reason we need Master
System Integrator !!
9
 TIA ICT – Detailed Design Gap Analysis
WHY ?

System Engineering V-Model TIA Integrated

MSI
ICT System of Systems

60% F & P

System MSI & Sub-

Owner System
owner
60% F & P MSI & Sub-
System
owner

System
Owner
MSI

MSI

www.incose.org

MSI Verification &Validation (V&V) efforts to ensure all activities leading to

TIA Integrated ICT System of Systems 10
 TIA ICT – Detailed Design Gap Analysis

As System Owner
• Ensure all functional Interoperability
requirements in F&P
are met. If not, Topology
highlight and explain. Reliability

• The required system Scalability

qualities. ( need input

from MSI for overall
Extensibility
System of Systems Architecture
Portability
Architecture Qualities Selection
Criteria
• Defined and published how the project
deliverables should be operated effectively
• Details included operational procedures
and processes, roles and responsibilities, Security
data, applications etc Evolve ability
• Complexities increase
• Fully operational (integrated) Mode
• Partially operational (integrated) Mode
• Stand alone operational (integrated)
Mode Performance
• Disaster Recovery operational (integrated Maintainability
) mode
???

11
 TIA ICT – Detailed Design Gap Analysis
As System Owner
• Identify Interfacing Points
as much as possible.
For the purposes of this project, an
interface is defined as the point
where there is an interaction across
the boundary of two entities:
considering common boundaries or
interconnection between systems,
equipment, and people.
The common physical point, boundary surface, or plane where two things touch, meet, or come
Physical Interface together.
(P) E.g., Party B will be supplying computer rack to data centre to be constructed by Party A. Part A needs
to ensure the floor design can sustain the computer rack weight.
• The common logical point where two systems interact. Interaction could be in the form of:
System Interface (S) • Network to Network Integration
• Integrating multiple system module into a single function e.g., Single Sign on.。
• Computer data packets flowing through devices e.g., getting through firewall.
• Displaying Software A from vendor X on hardware provided by vendor Y.
Information / data exchange to be passed between interfacing parties including but not limited to:
Information • Requirements
Interface (I) • Procedure, Standards, Drawings, Specifications
• Execution Requirements
Logistic Interface between parties including but not limited to:
Logistic Interface (L) • Scheduling/ Project Network Diagram
• Access to work areas
• Coordination of Works on site
• Coordination of completion, commissioning, and hand over
12
 TIA ICT – Detailed Design Gap Analysis

As System Owner
• You are not Alone
• MSI Team shall assist the System Owner Team in following
Coordination , Verification and Validation activities plus more

a. System to System interface

b. Multi-party System interface
c. System and Civil Works interface
d. System and MEP interface
 TIA ICT – Detailed Design Gap Analysis

Equipment Purchase Team

As System Owner
• Your High Quality Detailed Design will be UPS Sizing Team
appreciated
Enterprise Architecture Team

Detailed Network Design Team

Rack Management Team

Top priority Cyber Security Team

64 Rooms UPS
Design and Sizing Training Team

Requirements
ORAT Team

14
TIA ICT – Detailed Design Gap Analysis

PART 2
TIA ICT – Detailed Design Gap Analysis
F+P Doc #270500
D. Functional Specifications
1. Contractor shall provide a functional specification, in which all configurations (e.g. parameters, design of the GUI) and sequence of
operations and functions of the system are described in detail and which is the basic document for the implementation of the system.
2. Provide screenshots as example for each Common Launch Application (CLA) screen and all pre and post application screens.
3. Before starting the implementation, the document is to be reviewed by the Engineer.
E. Interface Control Document
1. Contractor to provide Interface Control Documents for each and every individual interface with systems referred or related to the
systems listed in 1.01.D: Related and Referenced Sections of the appropriate System Section.
2. Contractor to provide Interface Control Documents for each and every individual interface between the systems listed in 1.01.D:
Related and Referenced Sections and other systems located on the airport site.
3. Each ICD need to be reviewed by the involved suppliers and/or system integrator, involved in the realization of the interface.
4. The ICD needs to describe the interface in terms of the physical connectivity and description of the protocols.
5. The data to be exchanged is to be fully described in the protocol. Each type of message exchange between the two systems
involves passing a block of data and acknowledgement by the other system. Such data blocks can be defined as messages.
6. The ICD needs to describe the protocol description of each message.
7. The ICD is to define the full requirements for transfer of data between the two systems, in both directions if applicable.
8. Where data is to be stored in the Airport Operational Database and forwarded to other systems, it is necessary to describe the
interface for entry to the AODB.
Testing and Commissioning
• Items 3.8, page #28 and Item F (4) Page #34.

16
STRICTLY CONFIDENTIAL
TIA ICT – Detailed Design Gap Analysis

System Detail Design ….. What and Why

The System Does The system This solution and

How
What

Why
Are the Works proposed devices
components System is The proposed
Is the network implemented interfaces are
Architecture It meets F+P required
Is the Solution requirements Redundancy is
for TIA The testing and designed in this
commissioning is manner
Are is the SoW
done

17
STRICTLY CONFIDENTIAL
TIA ICT – Detailed Design Gap Analysis

• System Overview System Detail Design…..#1

• To describe the purpose of the system, and provide a conceptual design, along with some high-level design considerations.
• Its purpose is to provide a brief overview of the function of the system and the reasons for its development, its scope, and references to the development
context.
• System requirements and OS/App description for each device in the proposed solution
• Network Architecture and IP address and VLAN/Subnet design
• Interface / Logical interconnection
• Processing Logic and Input/Output flows
• Interface and Integration requirements (External and Internal)
• System Architecture
• To present the system architecture of the proposed solution, by viewing the system from various perspectives.
• Business aspect and operational aspect
• Information/Message and Data related consumption
• Cybersecurity and Antivirus
• Proposed Product Description
• Proposed Solution and how it meets the F+P requirements
• Proposed Solution Operational Concept
• Installation method and location and quantity
• What additional features to make it 100%
• Service Level Management
• System MTTR / MTBF and Availability – Redundancy
• Back and Recovery
• Testing and Commissioning Plans – “How” and “When” and “Where”
18
STRICTLY CONFIDENTIAL
TIA ICT – Detailed Design Gap Analysis

System Detail Design…..#2

• Table showing all the hardware / device proposed, which has quantity, location, software, OS, database and
warranty level.

Physical, Logical, Conceptual Diagrams

• Network Schematic showing the end-to-end connection, “how” and “where” for all devices and interfaces.
• System Architecture, “how” individual device / software make up the solution and what’s their importance
The hardware and Software interoperability
• Integration Schematic to show the system which interface with the proposed system
(Details on integration to be part of ICD)

Scope of Work Matrix – Inclusion and Exclusion

19
STRICTLY CONFIDENTIAL
TIA ICT – Detailed Design Gap Analysis

PART 3
TIA ICT – Detailed Design Gap Analysis
CCMC Doc PMC
CCMC
Submission Hygiene
internal QC
Check
Day 0
PMC & CAI Good
Start Doc
Review

PMC & CAI Comments CCMC

Comments Submit to Submits New
Review CCMC Draft NO
3 days 1 day 3 days

New Draft
NO Agreed by YES
Present to CAIC CAIC
PMC & Approves
CAI?
To discuss with Initial
2 days Operation Team and also
validate if any commercial for YES
additional VO items.
Proceed to
Implementation
TIA ICT – Detailed Design Gap Analysis

Part 3: Action Plans

• Detailed Design Train and Trainer Program – CCMC to provide Names of 2 representatives
• Revised submission schedule – CCMC to provide schedule
TIA ICT – Detailed Design Gap Analysis

Thank
You