MRO / M &E Project - ppra.org.pkppra.org.pk/doc/15-9/2pia159-210.pdf · A4 PRODUCT REQUIREMENT ......

INVITATION TO BID

Implementation of MRO/ M&E Project

Pakistan International Airlines Corporation, the national flag carrier, plans to implement a proven, time-

tested, internationally acclaimed and airline specific Maintenance Repair Overhaul (MRO) /

Maintenance & Engineering (M&E) solution catering to its requirements in the following areas:

Engineering & Airworthiness functions

Quality Assurance

Aircraft Line, Cabin & Base Maintenance

Engine Overhaul, Components Overhaul

Aircraft Material/Rotables Management.

Checks & Schedule Planning

Outsourced Maintenance

Resources Allocation & Performance Monitoring

Third Party Clients Management.

A/C Lease-in /out support.

Documentation / Library functions

Bidding documents, which are containing detailed terms and conditions, method of procurement,

procedure for submission of bids, bid security, bid validity, opening of bid, evaluation criteria,

clarification / rejection of bids, performance guarantee etc. are available for the interested bidders at

www.piac.com.pk

Tenders are called on “Single Stage Two Envelope” basis. The bids, prepared in accordance with the

instructions in the bidding documents, must reach at General Manager Procurement, Supply Chain

Department (Store Building), PIA Head Office, Karachi on or before October 2, 2017 up to 1030

hrs (PST). Bids will be opened the same day at 1100 Hrs. (PST). This advertisement with complete

RFP is also available on PPRA website at www.ppra.org.pk

Bidders are required to submit two (hard & soft copy format) copies each of the technical & commercial

bid marked as “Original” & “Copy”.

Local bidders are required to submit a pay order in the name of PIACL as a tender fee PKR 6,000.00

along with technical proposal.

Bids must be valid for 180 days.

PIAC reserves the right to reject any or all bids or cancel the procurement process at any stage in line

with PPRA rules.

General Manager Procurement

Supply Chain Management

PIA Head Office, Karachi.

Ph: +9221 99044423

Email: [email protected]

[email protected]

[email protected]

Page 1 of 189

MRO / M&E Project Request for Proposal

REQUEST FOR PROPOSAL

MRO / M&E PROJECT Pakistan International Airlines Corporation (Limited)

Ref: PIACL/SCM/ MRO M&E (Engg.)/11/17 www.piac.aero

Page 2 of 189


TABLE OF CONTENTS

SECTION ITEM SUBJECT PAGE

SECTION A PROJECT DETAIL 5

A1 PROJECT DETAILS 6

1 Project Background 6

2 Locations 6

3 Business Objectives 7

4 Information Technology (IT) Objectives 7

5 PIA Fleet Size & Composition 8

6 Definitions / Terms Used 8

A2 PROJECT ORGANIZATION 9

A3 PROJECT COMPONENTS & IMPORTANT MILESTONE 10

1 Project Components 10

2 Phase-wise Objectives 10

A4 PRODUCT REQUIREMENT (MRO/M&E PACKAGE) 12

1 Overview of Solution Requirements 12

2 General Requirements 13

3 Technology Requirements 17

A5 PIA EXISTING SYSTEMS, APPLICATIONS & INFRASTRUCTURE 22

1 Existing Systems 22

2 Details of Existing Systems Requiring Interface 23

3 Existing Infrastructure 24

SECTION B INSTRUCTIONS TO BIDDERS (ITB) 29

B1 INSTRUCTIONS FOR BID SUBMISSION 30

1 Introduction / Scope of Bid 30

2 The Request for Proposal Document 31

3 Clarification of RFP Document 31

4 Amendment to RFP Document 32

5 Preparation of Proposals 33

6 Proposed Prices 35

7 Documents Establishing Contractor’s Eligibility and

Qualifications.

37

8 Documents Establishing Products, Services Eligibility &

Conformity to RFP

37

Page 3 of 189



9 Bid Bond 38

10 Period of Validity of Proposals 39

11 Tender Proceedings 39

12 Submission of Proposals 40

13 Deadline for Submission of Proposals 41

14 Opening of Proposals by PIA 41

15 Clarification of Proposals 41

16 PIA’s Right to accept any Proposal and to reject any or All

Proposals

41

17 Evaluation & Finalization of Selection 42

18 Confidentiality 42

19 Bidder’s Profile 43

20 Legal Binding 43

21 Performance Guarantee 43

22 Signing of Contract 43

23 Contacting PIAC 44

B2 SUMMARY OF REQUIREMENTS 45

B3 TEMPLATE FORMS 46

B4 FORMAT & CONTENTS OF PROPOSAL 67

1 General Proposal Requirements 67

2 Required Format of the Proposal 67

SECTION C PRODUCT DETAILS (MRO PACKAGE & ADD-ONS) 72

C1 OBJECTIVES 73

C2 FUNCTIONAL REQUIREMENTS 74

C3 GENERAL REQUIREMENTS 99

SECTION D SERVICES REQUIREMENTS 102

D1 IMPLEMENTATION 103

D2 TRAINING 106

D3 DATA MIGRATION 109

D4 DOCUMENTATION 110

D5 WARRANTY AND MAINTENANCE SUPPORT 111

D6 VERSION AND UPGRADES 112

D7 INFORMATION NEEDS AND APPLICATION REQUIREMENTS 113

Page 4 of 189



D8 SYSTEM SECURITY 113

SECTION E PRODUCT REQUIREMENTS 114

E1 DBMS AND DATABASE ADMINISTRATION TOOLS 115

E2 APPLICATION DEVELOPMENT TOOLS 116

E3 QUERY AND REPORT GENERATOR TOOLS 117

E4 INTERIM SERVERS AND OPERATING SYSTEM 117

E5 3RD. PARTY SOFTWARE 118

SECTION F HARDWARE REQUIREMENTS 119

F1 HARDWARE 120

SECTION G BIDDER’S QUALIFICATION, EXPERIENCE & EVALUATION 122

G1 BIDDER’S QUALIFICATIONS AND EXPERIENCE 123

G2 EVALUATION 125

SECTION H REQUIREMENTS COMPLIANCE MATRIX 130

H1 GLOBAL REQUIREMENTS – GENERAL 131

H2 GLOBAL REQUIREMENTS – TECHNICAL 137

H3 GLOBAL REQUIREMENTS – OTHERS 145

H4 FUNCTIONAL REQUIREMENTS – MRO/M&E SOLUTION 149

H5 SERVICES REQUIREMENTS 170

H6 HARDWARE REQUIREMENTS 178

SECTION I COMPLETION AND COMPLIANCE CHECKLIST 181

I1 PROPOSAL COMPLETION CHECKLIST 182

I2 PRODUCTS AND SERVICES 183

I3 BUSINESS INFORMATION AND APPLICATION NEEDS 188

I4 MRO PACKAGE REQUIREMENTS 189

Page 5 of 189


SECTION A

PROJECT DETAIL

Page 6 of 189


A1. PROJECT DETAILS

1. Project Background

Pakistan International Airlines (PIA) is set to renew its IT landscape in line with its

changing business requirements. ERP from Oracle has already gone live in core business

area of the airline. Reassessment of business processes and further upgrade of the

information technology environment are the focused objectives.

In order to achieve greater operational efficiencies and to facilitate the realization of growth

targets, PIA has decided to implement a comprehensive Maintenance& Engineering

(M&E) IT solution which will be the best combination of technology products and services

at a reasonable cost.

The main components of the project are:

▪ Business process study / business process alignment with best industry practices

▪ Procurement of MRO / M&E system and supporting infrastructure

▪ MRO / M&E Solution implementation, integration, training and rollout

▪ Post-implementation support

With rapid implementation methodologies and accelerated deployment options available in

best of the breed MRO / M&E solutions, it is PIA‘s intention to complete the implementation,

training and rollout in minimum time period. The Contractor must recommend a suitable rapid

implementation approach to help ensure project success within the proposed timeline. Since

time is of essence, the proposed timeline will be fixed and strictly adhered to

2. Locations

The locations intended to be covered under the scope of the MRO / M&E Solution

implementation are as follows: -

▪ PIA Head Office at Karachi

▪ PIA Engineering, all locations in Karachi, Islamabad & Lahore as well as the PIA

line stations

▪ PIA Stores, Hangers and Workshops (all locations)

▪ PIA Computer Center at Karachi

Page 7 of 189


3. Business Objectives

To operate efficiently and effectively by having streamlined business processes, integrated

information systems and best industry practices, aimed at optimum utilization of available

resources within engineering department and across the entire organization.

It is the ultimate goal of PIA engineering department, to keep the entire fleet in airworthy

condition at all times. The new system shall support this goal by providing functionalities

as:

▪ Engineering & Airworthiness management;

▪ Management of airworthiness directives (ADs), service bulletins (SBs) and

engineering orders (EOs);

▪ Configuration management;

▪ Maintenance planning document (MPD) and maintenance program management;

▪ Maintenance planning and scheduling;

▪ Maintenance control and line maintenance;

▪ Heavy maintenance;

▪ Engine maintenance;

▪ Back shop and component maintenance;

▪ Tools and ground service equipment;

▪ Repair and warranty management; and

▪ Quality assurance & regulatory compliance;

▪ Client Order Management.

▪ A/C Lease in/out

▪ Documentation Management

Form the commercial point of view, the on-time performance and dispatch reliability of the

entire fleet is of essence. A well-structured maintenance planning supported by the

system shall support this objective. The number of Aircraft-On-Ground (AOG) situations to

be reduced.

With transparent data and streamlined business processes, PIA Engineering to be in a

position for more cost efficiency and a higher performance.

PIA Engineering also operates as engineering service provider to other airlines and a key

player in the 3rd party MRO business in the region. With the new MRO / MRO / M&E IT

functionalities, the PIA Engineering shall be more attractive for the 3rd party market.

4. Information Technology (IT) Objectives

Keeping in-line with the organization’s vision and mission, the Information Technology

department at PIA has formulated the following objectives:

▪ To implement industry standard systems / solutions which are integrated, adaptive

and flexible to both internal and external challenges and evolve as technology

Page 8 of 189


progresses and must be capable to meet present and future airline industry

challenges.

▪ To carefully plan and deploy resources to ensure continuity of Information

Technology services and its availability on 24x7 hours basis.

▪ To ensure that Information Technology is effectively applied to business needs.

▪ To provide technology tools to PIA staff for capturing and harnessing the knowledge

base with the latest in IT, for timely management decision support.

▪ Information Security and Audit Trails for transactional data.

▪ To incorporate data analytics including predictive, and suggestive analytics for right

decisions.

5. PIA Fleet Size & Composition

PIA current fleet is composed of both narrow body & wide-body aircraft from Boeing

777 family, Airbus A320 family, ATR42/72. The combined numbers at the moment

stands at 35 with an expected growth upto 50 aircraft in near future.

6. Definitions / Terms used.

i. Wherever word “PIA” is used, it should be read and understood as “Pakistan

International Airlines Corporation Limited (PIACL)”

ii. The term “MRO / M&E Solution” is invariably used to be read and understood

as an IT Solution / Software / System / Package for an airline MRO / M&E.

Page 9 of 189


A2. Project Organization

The “Project Management Office”, established at PIAC Head Office at Karachi,

Pakistan, will be the focal points of project management and implementation activities.

One of the benefits of managing this project through the “Project Management Office”

is that this office has already experience of implementation of ERP in PIA at all

stations throughout the globe.

Also, the flexibility of incorporating the required high level of technical/functional

resources in each discipline, PMO office has expertise in the areas of implementation

of Oracle ERP (Oracle e-Business Suite).

This Project Management Office (PMO) will remain in operation for the whole duration

of the project.

PMO team along with Engineering department and ICT, comprising of professionals

having experience in MRO / M&E processes & requirements, with network

management & ERP deployment. The PMO Team would be collaborating with PIA’s

management, and IT staff through various stages of this project. Besides PMO, a

Project Steering Committee will be there to oversee the progress and make decisions

on key issues.

The successful MRO / M&E Contractor would become a part of the PMO office till the

completion of project.

Page 10 of 189


A3. PROJECT COMPONENTS & IMPORTANT MILESTONES

1. Project Components

The various components of the project are:

▪ MRO / M&E System Implementation Strategy

▪ Detailed design, plan and the blue print

▪ Power user, end user and role based access management

▪ Infrastructure evaluation and recommendations for upgrade

▪ Monitoring the project

▪ System Customization

▪ Data migration

▪ System Testing

▪ Performance Tuning and Acceptance Testing

▪ Technical training and End User Trainings

▪ Cutover

▪ Post Cutover Support

2. Phase-wise Objectives

The following are the phase-wise objectives of the project:

2.1. Implementation Strategy

▪ Implementation strategy shall be adopted after due consideration to project

scope, applicable constraints and magnitude of business improvement goals.

Bidder must provide detailed implementation methodology.

▪ PIAC at its discretion may interview the nominated consultants to assess their

technical expertise and reserves the right to accept a consultant or ask for

replacement of any or all consultant. PIAC at its discretion may also ask for

replacement of any consultant at any stage of the project if PIAC considers that

the said consultant is engaged in questionable activities or the performance of

the consultant is not at par with required standard.

▪ Implementation of procedures and controls for a reasonable level of systems

security, audit ability, confidentiality, reliability, integrity, and business continuity.

▪ Conversion/ Migration of historical and live data, efficiently and accurately.

▪ Smooth and seamless transition to new systems without any disturbance to the

ongoing operational activities of PIAC.

Page 11 of 189


▪ Prepare conceptual design and highlight parameters that will be configured in the

MRO / M&E system in accordance with PIA business requirements. It should

also include complete workflow for transaction approvals and escalation.

▪ Provide integration solutions where MRO / M&E SYSTEM will be integrated with

Oracle ERP applications and other applications running in PIA as described in

Section A, sub-section A5-1.

▪ The vendor has to ensure that all software supplied is free from defects/ bugs/

flaws/ security holes etc. Warranty periods for hardware/software should be

clearly mentioned.

▪ Smooth transition from existing related applications to the new MRO / M&E

solution.

2.2. Training

▪ Preparation of the user community for change through appropriate knowledge

transfer and end- user training.

▪ Prepare and implement a comprehensive training plan to train the trainers/power

users, technical users end users.

▪ Gain acceptance for new systems by actively involving key users in driving the

acceptance testing process and achieving cut-over to the new environment.

▪ Provide a sufficient number of properly qualified MRO / M&E system experts for

each specific area mentioned in the RFP. These should cover – as a minimum –

experts having implementation experience in airline of size comparable to PIA in

engineering areas.

2.3. Post Implementation Support

▪ At no extra cost to PIAC, Contractor will provide a team of certified experts to be

stationed at PIA locations for post implementation support for a minimum period of

six months preferably to ensure optimum and seamless operations of systems and

processes.

▪ Specify a detailed support program and mechanism.

▪ Contractor must provide at least Three years post implementation warranty for

software and hardware. The Contractor has to ensure that all software and

hardware supplied are free from defects / bugs / flaws / security holes, etc.

Page 12 of 189


▪ Warranty periods for hardware / software should be clearly mentioned and must be

accordance with section D, subsection D5

▪ Any discrepancies, mismatches and resource constraints experienced during the

support period which were not specified in the Proposal will be responsibility of the

Contractor.

A4. Product Requirement (MRO / M&E Package)

1. Overview of Solution Requirements

PIAC desires to procure an MRO / M&E Solution for PIAC’s engineering business needs

which would comprise the following: -

▪ An MRO / M&E Package which is well integrated with Oracle ERP and

interfaced with applications used in Flight Operations, Corporate Safety &

marketing planning.

▪ Add-on or Custom Built Applications shall be acceptable if minimum.

▪ Future/Trending Value added modules and add-ons.

▪ Easy and cost-effective transformability of the MRO / M&E solution into an

MRO IT Solution, in the event PIA desires to transform the Engineering &

Maintenance into an independent business unit (an MRO).

The solution to PIAC’s business needs should cover all the features that marketplace is

widely offering in airline industry and must meet the specific needs of PIAC. Bidders are

expected to match the requirements to the features/functionality in a cost-effective way.

To that end, it is expected the Technical Proposal submitted in response to this RFP

Document will clearly describe how the Bidder expects to meet the business needs of

PIAC.

Further, Bidders are expected to suggest solutions that will require minimum customization

to bring upon the best industry processes & practices, and minimum modification or add-

ons, maximum or completely seamless integration between applications, lower systems

implementation risk, while at the same time providing the best possible performance at an

economical price.

Bidder shall present a written technical proposal to address the requirements in the

following Sections. Proposals must declare any requirements the Bidder cannot satisfy.

Sufficient details should be included to demonstrate the Bidder’s knowledge of the Project

and their ability to satisfy each requirement.

Page 13 of 189


2. General Requirements

The following narrative represents a summary of the general requirements envisioned by

PIAC in the MRO / M&E Solution.

2.1. Common Characteristics

Common characteristics represent capabilities that should be shared by all functional

areas of the MRO / M&E Solution. They are to be considered along with the more

specific functional requirements that follow in the design of a system.

2.2. Integration

The MRO / M&E software should support modern “best industry practices”, with data

located in one integrated system shared across all organizational units. The

software should support enterprise-wide business processes with a goal of

eliminating multiple handling of data and increasing data accuracy. The proposed

MRO / M&E System should be capable to integrate with Oracle ERP applications

and to interface with existing applications running in PIA (refer Section A5-1).

2.3. Configuration

PIA desires to procure a system that will require minimum software modification to

meet its business requirements. The software should allow for easy tailoring and

customization to meet those requirements without changing software code or

requiring add-on changes to parameters, software switches, processing rules, and

other tailoring approaches may be acceptable. The tailoring should be accomplished

in a way that does not adversely impact the future installation of system upgrades

released from the IT solution provider.

2.4. Technology Interfaces

The Bidder should provide standard application programming interfaces, tools and

methodologies that allow future releases to accommodate interfaces without

reprogramming. A standard approach to interfaces should be employed to avoid

multiple, unique approaches for different systems. The Bidder will have to ensure, at

its own cost, availability of APIs for both its proposed system as well as system

running in PIAC. The software should be capable to integrate with applications

already running in PIAC through Web-services, Application Programming (APIs), or

through data exports in a secure and efficient manner. Bidder must ensure to provide

XML-based APIs wherever these are required.

Page 14 of 189


2.5. User Interface

The system should provide an intuitive, user-friendly, and easy-to-use interface that

minimizes the need for training. The system should have a common look and feel

across all applications. Content-sensitive / online help should be available for all

applications and should allow for customization. The system must address the

needs of infrequent or low volume users as well as those who use the system

several hours each day. The system must be equally usable from remote locations

as from the Head Office. Web-based access should be supported.

Business rules should be incorporated into the system such that the rules are applied

at the time information is entered into the system. The system should identify entry

errors, inconsistencies or logical disorder at the time data is entered. Processing of

the transaction should be suspended and/or re-routed to resolve the problem in “real

time”. Any unsuccessful transaction due any reason, should be notified and

prompted to the user for re-entry.

2.6. Security & Authorization

The system must support multiple levels of security. This includes protecting certain

fields from unauthorized access. In addition, access to certain functions and data

must be protected until they are approved by PIAC’s concerned policy makers.

Changes in assignment or termination should automatically trigger a review of the

employee’s security privileges. Comprehensive logs of transactions and security

incidents must be maintained for auditing purposes. System should provide

authorization, authentication, integrity and non-repudiation facilities for critical

transactions. System should be capable to maintain logs etc. System should be

capable of secure remote login. System should support electronic signature and time

stamp etc.

2.7. Reporting / Inquiry

The system must include comprehensive reporting tools that allow for easy access to

authorized data. Executive interfaces to the data with “drill down” capability to

examine details should be included in the reporting tools. It should also be possible

to create reports that reflect status as of a specified point in time. Standard reports

should be included that will serve as models for customized reporting as well as

provide for basic functional reports. Report wizards or similar techniques should be

available to guide users through report creation. The system must be designed such

that reporting activities do not compromise the responsiveness of the interactive

system.

Page 15 of 189


Reports should be formatted to print on local PC and LAN attached printers as well

as on centralized high-speed printers. It should be possible to deliver fixed reports to

users on a pre-determined schedule to be reviewed online, to be retained online or

to be printed at the user’s discretion.

The system should be able to demonstrate useful demographic and forecasting

capabilities; support text based searches and provides departments the ability to

develop ad hoc reports at their discretion. The system must include a data

dictionary or similar provision to allow non-technical users to identify the appropriate

data elements for inclusion in their reports.

2.8. Data Analytic Tools

PIAC desires decision support tools and information bases that are fully integrated

with the system to facilitate strategic planning, tactical operations and organization-

wide analysis.

The system should support the easy movement of data to common packaged PC-

based applications such as Microsoft Office and text files.

The system should include the ability to locate information / guidance material or text

through a search capability on relevant historical maintenance records of

aircraft/engine/components.

The system should be capable of producing “what if” scenarios to support decision-

making.

2.9. Communication

The system should foster information sharing at all levels of the organization. For

example, policy directives and goals should be incorporated into engineering

maintenance planning process; various functional units of engineering and other

departments should be able to share required information e.g. schedules, material

requirements and job specifications etc.

2.10. Flexibility

The system should be easily reconfigurable to respond to changes in business

practices, policy directives, organization structure, statutes and regulations. As

business requirements change, the system should also change to support the new

requirements. Flexibility should extend both to enterprise-wide as well as industry

specific practices.

Page 16 of 189


2.11. System Availability

Overall it should be a highly available solution. It must be available for access by

authorized personnel from anywhere at any time of the day or night (24 x 7

availability). The system must be equally usable from remote locations as from the

Head Office.

2.12. Transaction Timing

The system must support real time processing. Changes to data or the status of

processes should be immediately available in the system. System operations should

not artificially constrain the business processes supported by the system.

The system must support effective time/date stamping for transactions, including

both future and retroactive changes. The authority for such transactions must be

included in the security capabilities of the system with access roles and audit trails.

The assignment of a retroactive date must generate the changes required to bring

the system up to the current date.

2.13. Online Documentation and Training

The system must include customizable online documentation and training materials

such as context-specific help, search capability, business process documentation

and process maps.

2.14. Storage/Record Retrieval

Record collection and retention is an important organizational requirement. The

ability to easily archive, retain and access records is required. Records retention

procedures must allow information to be stored in a way that can be accessible

indefinitely.

2.15. System Security

System provided must be secure and meet all standard security requirements i.e.

Identification, Authentication, Authorization and Integrity. System should allow

implementation of industry standard security policies and capable to evolve to meet

security challenges, provide roles based access, and audit trails for the system

controls and transactions.

Page 17 of 189


3. Technology Requirements

3.1. New Technology

The system should be designed in such a way as to easily allow the incorporation of

new technologies, as they become available.

3.2. Multiple Environments

In addition to the production environment, the system must support independent

copies for training, development, and quality control / test. These environments must

be sufficiently isolated from production and from each other so that operations in one

environment will not affect those of another.

The environments will be employed as follows:

▪ Production – all production processing will be performed in this environment.

▪ Development – all development activities including unit and system testing will

be conducted in this environment.

▪ Quality Control / Testing – after all development unit and system testing has

been completed, this environment will provide a system for divisions/units to

check the quality and testing of enhancements/modifications before they are

“accepted” into production.

3.3. System Performance

The system must be responsive and available. The system should support rapid fail-

over or redeployment in the event of problems or planned maintenance. Ninety-nine

percent of all fail-over events must take place in less than five minutes. Any volume

(batch) processing must not interfere with online responsiveness or availability.

3.4. Archive and Purge

The system must support the periodic archival and purging of unused or obsolete

information. Archived information should be available for historical reporting. The

system should remain continuously available during archiving/purging

3.5. Recovery

The system must automatically recover to the last complete prior transaction in the

event of a failure. The system must clearly indicate to the user that a transaction

Page 18 of 189


failed and that it must be re-entered. Recovery must occur without operator

intervention. Bidder must provide contingency and back-up recovery procedures with

guaranteed SLA (Service Level Agreement).

3.6. Backup / Recovery and Reorganization

The system must provide for the unattended daily backup of all information and data

to a media that can be stored offsite for disaster recovery purposes. Backups must

not prevent the system from being available at all times and must not disrupt system

operations. Database reorganizations should not significantly impair the availability

of the system.

3.7. Print Management

The system should provide a method for managing the print environment for report

distribution so that reports are directed to the appropriate print facility. Both high

speed centralized printing facilities as well as local LAN-based printing facilities will

be employed. Users should be able to print reports and documents on local printers.

3.8. Fallback Solution

In case the system or parts of the system is not operative, a manual or semi-manual

fallback solution to be developed, to continue the MRO / M&E operation. After restart

of the system. It must be possible to update the system accordingly.

3.9. Ability for system and license updates

The bidder should guarantee that the provided MRO / M&E Package’s customization

or modification shall be ready for any future updates. This guarantee shall also be

given for any underlying software such as DBMS, Operating System, Network

Management and other tools. Also, the Bidder may give further advices updating the

system to major or minor releases. It is in PIAC discretion to follow the advice.

3.10. Technology Architecture

The Contractor should provide recommendations of the technology architecture

under which the proposed MRO / M&E Package will operate, with the following

features preference:

Page 19 of 189


▪ N-tiered Client/Server architecture incorporating thin presentation-logic-client

communicating with client-neutral, server-based applications, communicating with

the database

▪ Thin client, for remote users

▪ Applications distributed at servers located at Head Office

▪ Centralized database, located at Head Office

While designing the technology architecture, the Contractor should ensure that the

following are kept under consideration:

▪ Solution should be scalable with complete platform independence – PIA does not

intend to be tied down to a single platform

▪ Solution should be effortlessly portable from one system to another

▪ Should provide support for different flavors of UNIX, Windows etc.; however, it

should be a totally interoperable solution

▪ There must be open source support. In this context, the Contractor must specify

the current scenario vis-à-vis the solution offered and the future roadmap

▪ Optimization of licensing costs for the platform software

▪ PIA’s existing Local and Wide Area Network, and minimization of Wide Area

Network bandwidth requirements,

▪ Simplicity of System Administration and Operations,

▪ Ease of business continuity planning and execution.

▪ Cloud based hosting capability

Contractors should present a number of architecture options, providing pros and

cons of each option, as well as the Contractors recommended option.

3.11. Server Hardware

a) The Contractor should provide both its minimum and optimum configuration

requirements for Application and Database Servers to run the MRO / M&E Package

and other applications, consistent with the MRO / M&E features and proposed

technology architecture (3.10 above), and multiple environment requirements (3.2

above). The recommended configuration should cater for the existing load as well

as annual volume growth of 10-15% for the next five years. The configuration

should be capable of retaining data for at least eleven years (that is, current year

plus ten years’ historical record). The solution must be redundant, reliable and

consistently available to allow uninterruptible 24x7 operations.

b) The main servers will be housed in PIAC’s Information Technology Department.

The production server configuration should include redundant (RAID-5) data

storage (including SAN) and multiple processors and cater for compatibility with

PIAC’s existing LAN / WAN environment. The Contractor should take into

Page 20 of 189


consideration the areas of performance and scalability, reliability and fault tolerance

while recommending Server configurations.

c) Contractor must provide performance guarantees of the solution under different

Contractor must provide performance guarantees of the solution under different

during overload, during partial system failure, etc.

d) Optionally availability of cloud based solution is required with price and

methodology.

e) PIA reserves the rights to choose the options of:

• Purchasing of new Hardware

• Up-gradation of existing Hardware

• Adaptation of Cloud technology

3.12. Systems and Network Management Tools

Bidders are required to recommend suitable Systems and Network Management

Tools. The Systems Management Tools should ensure proper planning,

configuration, and problem handling of IT resources and support such tasks as: -

▪ Defining, resolving, and managing problems;

▪ Operating networks and multi-vendor systems;

▪ Distributing and managing software and data;

▪ Controlling operations;

▪ Planning and managing performance;

▪ Administering security;

▪ Maintaining asset information; and

▪ Planning for the future capacity of systems.

3.13. Data Support

The solution should be able to support multiple data types – text, image, voice,

video, 3D animation, etc.

It should be able to support data upload to and download from different systems in

multiple formats. Besides simple upload / download facility it should also be able to

communicate and support data interchange with mobile devices such as cellular

phones, handheld terminals, PDAs, etc. It should also be able to support other

devices such as scanners, barcode readers, biometric devices, card readers, RFID

devices, etc.

Page 21 of 189


Support for important messaging / data formats / standards must include, as a

minimum, Aircraft Communication Addressing and Reporting System (ACARS),

SITATEX, ASCII, SMS, XML, Spec 2010, S1000D, MS-Office, Lotus Notes, etc.


The system supports authentication methods that will assure that only authorized users are able to access protected data and transactions.

These include support for:

a) Digital Signatures

b) PKI Infrastructure

3.15. Web-enablement

The proposed System should be Internet ready and allow web-enabled access to

users from anywhere across the world through a web portal. It should also be

compliant with the Service Oriented Architecture (SOA).

3.16. Workflow

The proposed System should be capable of providing Workflow functionality to users by which information and requests could be automatically routed to the concerned levels for approval.

3.17. Others

Besides above –mentioned characteristics the proposed MRO / M&E SYSTEM

should also be capable of:

▪ Supporting multi-currency

▪ Supporting user defaults

▪ Supporting user defined screens/dashboards.

▪ Supporting multiple date formats

▪ Providing easy development of user defined reports

▪ Supporting user defined fields

▪ Scheduling of jobs for unattended operations

▪ Maintaining effective dates of master file data

3.18. Mobile Technology Support

Solution provided by bidders must be compatible / available on all mobile (cell phone) and

iPad/tablets.

Page 22 of 189


A5. PIA Existing Systems, Applications& Infrastructure.

1. EXISTING SYSTEMS

This sub-section describes those applications & systems which are utilized &

accessed for Maintenance & Engineering functional requirements or for which

information interchange / interface mechanism exists

1.1 Oracle ERP Main business application suite

1.2 AIMS Airline Information Management System

1.3 Sabre Products Schedule Planning, Slot/Fleet Manager System, Air

Vision etc.

1.4 AirOps System PIA may acquire any new AirOps System

1.5 Any other software Will be decided at the time of requirement gathering

➢ It is required that the proposed MRO/M&E to integrate with Oracle ERP

in a seamless manner. It is also required that MRO / M&E system be

interfaces with AIMS & Sabre applications, in order to provide

maintenance planning functionality.

1.6 PAMMIS (PIA Aircraft Maintenance Management Information System)

➢ This is the legacy system, developed in-house & currently under used in

Engineering & Maintenance department, and which PIA intends to replace with

best of the breed MRO / M&E System.

Page 23 of 189


2. DETAILS OF EXISTING SYSTEMS REQUIRING INTERFACE

2.1. Oracle ERP

Oracle ERP is the core business application responsible to manage major airline

business areas. i.e.;

a) Finance

b) Budgeting,

c) Purchasing & Logistic,

d) Human Resources,

e) Training & Qualifications

f) Safety Management System

➢ Contractors are required to provide seamless integration with MRO / M&E

solution.

2.2 AIMS (Airline Information Management System)

AIMS are Windows 2000/2003 client-server based software for airline crew, aircraft, and

flight management and operations control. The proposed MRO/M&E solution is required

to be interfaced with AIMS to cater to Maintenance Planning & Scheduling.

Modules requiring Interface

• Aircraft scheduling and assignment

• Movement and control

AIMS at PIA

Following is an overview of how AIMS is being used at PIA:

• Commercial Planning Section (CPS) prepares flight schedule for next one month in

Sabre AirFlite Application. Copy of flight schedule is sent to the Engineering

department to ensure Aircraft availability.

• Signed copies are sent back to CPS regarding confirmation of Aircraft availability by

engineering department.

System Related Information

Application Category Acquired System

Operating System Windows 2000 or 2003

Database Oracle 9i

Front End Delphi , C-Sharp

Application Source

Code

Not available. Any changes to standard application are made by vendor upon

request.

APIs

Not available. The only interface available is known as AIMS Report Generator.

All customized reports developed by PIA IT department are published through

this interface, which can be accessed by AIMS users through AIMS Menu.

Page 24 of 189


2.3 SABRE AIROPS SUITE

Introduction

AirOps provides centralized, real time access to critical data such as flight, passenger,

crew, maintenance, aircraft, airport, weather, payload and navigational, as well as fuel

data. Currently PIA is in the process of implementing this application suite. The

proposed MRO / M&E Solution is required to be interfaced with

this solution.

Currently PIA is using the following modules:

• Sabre Dispatch Manager (used by Flight Dispatch Section)

• Sabre Movement Manager (used by Flight Control Section)

Sabre Dispatch Manager (Flight Planning)

It enables Flight Operations department to operate its own

dispatching and flight planning system. It interfaces with

virtually all passenger reservations and message switching

systems and provides centralized functionality of mainframe

dispatch systems in a flexible client / server setting.

Sabre Movement Manager

It enables PIA to monitor and schedule daily maintenance and flight operations. It

uses a Gantt chart to graphically show flight leg information from a central database.

This module presents information about current operations and maintenance events,

which assist in evaluating problems and determining cost-effective solutions.

Additional modules included in the system.

• The Maintenance Routine module

• The Sabre EC – slots real time slot request and management module

• The browser-based Flight Information Display System provides real-time updates

of the latest flight departure and arrival information.

Information Flow

• Thereafter, following information is updated / tracked through this application:

▪ Flight departure and arrival time reporting

▪ Any changes in the flight schedule (delays, cancellations, diversions, etc.) are updated in the system by Flight Control Section.

• Aircraft maintenance information is also updated in the system. This assists the

Flight Dispatch Section to prepare flight schedule in accordance with fleet

availability.

Sabre AirOps

Maintains;

- Flight

Departure/Arrival

Time

- Passenger

- Crew

- Aircraft

Maintenance

- Weather

- Payload

- Navigational &

Fuel Data

Page 25 of 189


2.4 PAMMIS

The existing system which will be replaced by MRO / M&E solution. This information is

provided

Further details of some of in-house Engineering application is as under which would

particularly be useful in determining the data migration process.

Following are the main functionality which exist in PAMMIS system

• Tech. Log / Fleet Performance

• Rotables Management

• Maintenance Program & Task Cards

• Outsourced Maintenance

• Configuration Management

• AD/SB Management

• Man-hours Planning

Module /

Application

Name

Purpose / Details Hardware

Platform

Programming

Language

Operating

System

Database /

File

Structure

PAMMIS (PIA

Aircraft

Maintenance

Management

Information

System)

Tracks the

movement of aircraft

parts that come to

Engineering

Department for

maintenance

IBM

MP2003 VisualGen

VM/ESA

VSE/ESA DB2/VSE

Page 26 of 189


3. EXISTING INFRASTRUCTURE

3.1 Servers

The IT Department at PIA maintains a number of servers and storage arrays to

support various applications. Some of these applications have been developed in-

house while some have been acquired from third-party vendors. A certain number

of applications are also hosted externally.

After implementation of ERP most of the small isolated software are replaced with

ERP, resulting reduced the number of ERP server. Currently PIA is using Oracle

Exadata and Exalogic machine to maintain its database and ERP application

respectively.

The block diagram shown below represents how different applications and modules

are connected to the 10 GBPS backbone:

Page 27 of 189


3.2 ERP Servers and DR Site

Below mentioned picture is showing the architecture of PIA ERP servers and its

connectivity with DR site.

3.3 Connectivity

The fundamental purpose of a communications system is the exchange of data

between two parties. Communications networks are designed by interconnecting

a variety of devices. This is done to help share the information and make

efficient use of common resources available within an organization.

A high-level block diagram representing the PIA network is given below:

Page 28 of 189


3.3.1 Local Area Network (LAN)

The PIA LAN is centered at the Computer Centre building situated next to PIA Head

Office, in the vicinity of Jinnah International Airport. It is based on a fiber- optic

backbone and serves different locations as follows:

3.3.2 Wide Area Network (WAN)

PIA also supports major WAN connectivity linking all its regional and local offices to

PIA Computer Centre. The WAN setup is being done in two phases as follows:

Page 29 of 189


SECTION B

INSTRUCTIONS TO BIDDERS (ITB)

Page 30 of 189


B1. Instructions for Bid Submission

1 Introduction /Scope of Bid

The Bidders are invited to submit a detailed Technical Proposal and an item wise

Financial/Commercial proposal for Products and Services required as per the

requirements detailed in the bidding documents.

The assignment may be implemented in accordance with sequence as defined in

section A (A3) in the RFP or in parallel as per critical path identified by Bidder and

agreed by PIAC. The performance of the Bidder under each set of tasks must be to

PIAC’s satisfaction1 . In each case Bidder shall complete task satisfactorily before

initiating next sequential task.

The Bidders must familiarize themselves with local conditions and take them into

account in preparing their proposals. PIAC will provide the inputs specified in the RFP

and reasonably assist the Bidder in obtaining administrative licenses and permits

needed to carry out the project, and make available relevant project data and reports.

However, procurement of licenses, permits etc. shall not be PIAC’s responsibility.

By submitting a Proposal, the Contractor agrees to be legally bound by the terms and

conditions set out in this RFP. The Proposal will be considered as a binding offer from

the Contractor subject to acceptance by PIA.

1.1 Eligible Contractors

Original Solution Providers /authorized implementation partners / joint ventures are

eligible to participate in the bid. In case of joint ventures, Lead Contractor to be

specifically defined alongside partners. The Lead contractor would take the entire

responsibility of the submitted bid. Offers received through

brokers/agents/intermediaries shall not be considered.

1.2 Products and Services

i. Phrase “MRO / M&E Solution” is synonymously used as “MRO / M&E Package”

or “MRO / M&E System”, and means that all of the

products/solutions/software/training/licenses/ and related services to be

provided by the selected Bidder under the contract (as per the bidding

documents)

ii. The word “company” used in this section (B) & section (G), means “Pakistan

International Airlines Corporation Limited”

1PIAC will issue a completion certificate for each stage and a final completion certificate on completion of

the project.

Page 31 of 189


1.3 Cost of Bidding

The Bidders shall bear all costs associated with the preparation and submission of

its proposal, and Pakistan International Airline, hereinafter referred to as “PIAC”,

will in no case be responsible or liable for those costs or any of the losses to the

bidder, regardless of the conduct or outcome of the bidding process.

2 The Request for Proposal Document

2.1 Content of RFP Documents

The contents of the RFP Documents are listed below and should be read in

conjunction with any addenda issued in accordance with ITB:

Section A Project Details

Section B Instructions to Bidders

Section C Product Detail (MRO / M&E Package and Add-Ons)

Section D Service Requirements

Section E Product Requirements (Others)

Section F Hardware Requirements

Section G Bidder’s Qualification, Experience& Evaluation

Section H Requirements Compliance Matrix.

Section I Completion and Compliance Checklist.

2.2 Contractors must examine all instructions, forms, terms, specifications and

other information in the RFP Documents. Each Contractor by submitting its

proposal shall be deemed to have satisfied itself as to all the conditions and

circumstances affecting the scope of work and bid amount / contract price.

2.3 Failure to furnish all information required by the RFP Documents or to submit a

Proposal not substantially responsive to the RFP Documents in every respect

will be at the Contractor‘s risk and may result in the rejection of their Proposal

and the Contractor shall not hold PIA liable for such rejection in anyway

whatsoever. PIA reserves the right to verify at its sole discretion any or all

information submitted in response to the RFP Document. Any false information

or misrepresentation or non-disclosure may result in rejection of the entire

Proposal

3 Clarification of RFP Document

PIAC has made every effort to make the RFP Document as clear as possible. However,

in a project of this size and complexity, Bidders may need more clarifications.

Bidders may request for clarification on any of the RFP documents up to seven days

before the proposal submission date. Any request for clarification must be sent in

Page 32 of 189


writing by paper mail, cable, telex, facsimile, or electronic mail to the PIAC’s address

indicated in the RFP. PIAC may respond by cable, telex, facsimile, or electronic mail

to such requests and will send written copies of the response (including an explanation

of the query but without identifying the source of inquiry) to all parties who intend to

submit proposals.

Contact Address

General Manager (Procurement)

Supply Chain Management (Store Building)

PIA Head Office

Airport, Terminal-1

Karachi 75200

PAKISTAN

Ph: +92-21-99044423


4 Amendment to RFP Documents

4.1 PIA may modify the RFP Documents by issuing addenda, for any reason, and at any time prior to the deadline for submission of Proposals. Any addenda to the RFP Documents shall be considered part of the RFP Document.

4.2 All Contractors will be notified of the addenda in writing by newspapers, email,

letter or facsimile, all such Contractors shall confirm the receipt of such

addenda to PIA and it shall be binding on them.

To allow Contractors reasonable time to take any addenda into account in preparing

their Proposals, PIA may, at its own discretion, extend, as necessary, the deadline

for the submission of proposal.

Page 33 of 189


5 Preparation of Proposals

5.1 Language of Proposals

Proposals and all correspondence and documents relating to the proposals

exchanged by the Bidders and PIAC shall be in English.

5.2 Documents Comprising the Proposal

Bidders will be required to submit separate proposals along with implementation

plan for Complete MRO / M&E Implementation each comprising of following two

proposals.

➢ Technical Proposal (one Original and one Copy “Soft Copy and Hard Copy)

➢ Financial/Commercial Proposal (one Original and one Copy)

a) The relevant completed “Proposal Form” and all Price Schedules as included in

Section B, Subsection B3 – Template Forms, completed and duly signed.

b) Bid security furnished in accordance with ITB Sub-section 8;

c) A full description of the technical solution to the business requirements

described in Sections C – Product Requirements (MRO / M&E Solution & Add-

ons), Section D – Services Requirements and Section E – Product

Requirements (Others).

d) The completed Requirements Compliance Matrix (Section H), Completion

Checklist & Compliance Checklists (Section I, Subsections I1 to I4).

5.3 Technical Proposal

In preparing the Technical Proposal, Bidders are expected to examine the

documents constituting this RFP in detail. Deficiencies in providing the information

requested may result in rejection of a proposal.

While preparing the Technical Proposal, Bidders must give particular attention to

the following:

▪ If a Bidder considers that it does not have all the expertise for the assignment, it

may, subject to PIAC’s prior approval, obtain a full range of expertise by

associating with individual Bidder and/or other Bidders or entities in a joint

venture as appropriate. Bidders may associate with other parties invited for this

assignment (through this RFP or the earlier invitation for Expression of Interest)

only with approval of PIAC.

▪ It is desirable that the majority of the key professional staff proposed by the

Bidder should be its permanent employees or have an extended and stable

working relationship with it.

Page 34 of 189


▪ Proposed professional staff must, at a minimum, have sufficient experience in the required field, preferably working under conditions similar to those prevailing in the country of the assignment.

▪ Alternative professional staff shall not be proposed, and only one curriculum

vitae (CV) may be submitted for each position.

Reports to be issued by the Bidders as part of this assignment must be in English

language.

5.3.1 Information Required

a) Detailed project plan with timeframe for task and sub task.

b) A brief description of the bidder’s organization and an outline of recent

experience on assignments of a similar nature. For each assignment, the

profiles of the staff proposed, duration of the assignment, contract amount,

and bidder’s involvement.

c) Any comments or suggestions on the Terms of Reference and on the data,

a list of products/services, and facilities to be provided by PIAC.

d) A description of the methodology and work plan for implementation of the

project.

e) The list of the proposed staff team by specialty, the tasks that would be

assigned to each staff team member, and their timing.

f) CVs recently signed by the proposed professional staff and the authorized

representative submitting the proposal. The format of CV must be as per

format attached in Section B, subsection B3. Key information should

include number of years working for the firm/entity and degree of

responsibility held in various assignments during the last ten (10) years.

g) Estimates of the total staff input (professional and support staff; staff time)

needed to carry out the project, supported by bar chart diagrams showing

the time proposed for each professional staff team member.

h) A detailed description of the proposed methodology, staffing, and

monitoring of training, if the RFP specifies training as a major component

of the project.

i) Any additional information requested in the RFP.

j) Technical team training, end-user training.

The Technical Proposal shall not include any financial information.

Page 35 of 189


5.4 Financial Proposal

In preparing the Financial Proposal, Bidders are expected to take into account the

requirements and conditions outlined in the RFP documents. The Financial

Proposal should list all costs associated with the project, further broken-down into

per module costs, costs of licenses if any, hardware, software, cost of operating

software, database software or any other software with required number of licenses

for each component of the application, operating system or any other utility

software required, cost of training, post implementation support, cost of warranties

if any etc. If appropriate, these costs should be broken down by activity and, if

appropriate, into foreign and local expenditures. Bidders must quote all prices of

their goods and services in USD only

5.4.1 Proposals must remain valid for 180 days after the submission date. During

this period, the bidder is expected to keep available the professional staff

proposed for the assignment. PIAC will endeavor to complete

discussions/clarifications within this period. However, if necessary, PIAC

may require extension in the said validity period. The proposal submitted by

the bidders shall comprise the following:

5.4.2 The relevant completed “Proposal Form” and all Price Schedules as

included in Section B3.

5.4.3 A full description of the technical solution to the business requirements

described in Sections C – Product Requirements (MRO / M&E Package&

add-ons) and Section D – Services Requirements.

5.4.4 The successful bidder will be required to furnish, on or before the date of the

signing of the contract, a performance guarantee equal to 5% (five percent)

of total value of the contract price/successful bid amount from a reputable

scheduled bank acceptable to PIAC.

The Bidder is required to deposit earnest money equal to 2% of the bid submitted

for MRO / M&E Solution implementation, with the bid at the time of submission of

the bid. The earnest money shall be furnished in the form of a pay order of a

scheduled bank in favor of PIAC. The earnest money will be returned to

unsuccessful bidder for which unsuccessful bidder has to submit a written request.

The earnest money deposited by the successful bidder will be kept as security

deposit until project is completed satisfactorily. No interest will be payable on

earnest money to successful or unsuccessful bidder.

6 Proposed Prices

6.1 The Contractor must provide the prices of the proposed Solution using the

Price Schedule Templates provided in Subsection B3.

Page 36 of 189


6.2 Prices provided on the Price and Recurrent Costs Schedules (as per

Templates) shall be listed individually in the following manner:

6.2.1 Unit and total prices of products offered, inclusive of all taxes and duties paid.

6.2.2 Separate prices for each item of the hardware/software/ software licenses etc.


6.2.4 Prices for implementation services.

6.2.5 Prices for training Master Trainers, Power Users and End Users etc. local and

foreign component to be mentioned separately.

6.2.6 Recurrent costs after the expiration of the warranty period on the Recurrent

Costs Form, as follows:

6.2.6.1 The cost of all software updates, recurrent licensing fees, and any

other items needed to operate the MRO / M&E Solution, plus any other

recurrent supply of products specified in the RFP Document

6.2.6.2 The cost of all maintenance and technical support services, and any

other recurrent services specified in the RFP Document, including all

taxes payable by the Bidder thereon.

6.2.6.3 Cost of post implementation support along with number of experts

stationed at PIAC premises.

6.2.7 Totals of Products, Services and Recurrent Costs, on the Proposal Price

Summary Form.

6.2.8 There should be no hidden costs. Any cost not mentioned and to be incurred

later for proper fault free execution of the project is the responsibility of the

Bidder.

6.2.9 All costs are to be quoted in USD and must be fixed.

6.2.10 Payment will be milestone based as per format attached in Section B,

subsection B3. Bidder is required to provide the confirmation if agreed with

payment schedule.

6.3 Contractor‘s separation of price components in accordance with ITB Subsection

6, item 6.2 will be solely for the purpose of facilitating the comparison of

proposals and will not in any way limit PIA‘s right to contract on any of the terms

offered.

Page 37 of 189


6.4 Prices quoted by the Contractor shall be fixed maximum prices during the

Contractor‘s performance of the contract. Proposals submitted with adjustable

price quotations will be rejected and the Contractor shall not hold PIA liable in

anyway whatsoever for such rejection.

7 Documents Establishing Contractor’s Eligibility and Qualifications

The documentary evidence of the Contractor’s qualifications and ability to perform

the contract if its proposal is accepted shall establish to PIAC’s satisfaction:

7.1 That, in the case of a Contractor not doing business in Pakistan, the Contractor

will be able (if awarded the Contract), to carry out the installation,

implementation, support, maintenance, and other service obligations

prescribed in the RFP Documents. Documentary evidence supporting the

aforementioned must be provided;

7.2 That the Contractor and any Sub-contractors have the financial, technical, and

staff capabilities to support the MRO / M&E Solution, and have a successful

performance history, appropriate for their role in fulfilling the contract.

7.3 Each Sub-contractor must sign a Letter of Authorization / Joint Venture

Agreement authorizing the Lead Contractor to act on its behalf. A copy of this

Letter of Authorization / Joint Venture agreement must be submitted along with

the Proposal. The Lead Contractor shall be completely responsible for all

contract services to be performed. The Lead Contractor must demonstrate

that all aspects of this RFP Document have been carefully and completely

considered.

7.4 No substitution of a Sub-contractor shall be allowed during the term of this

contract. Failure of a Sub-contractor to perform as expected shall not relieve

the Lead Contractor of its duties to perform on the whole requirement and the

Lead Contractor shall be liable for any / all loss(es) / damage(s) that PIA may

suffer as a result of failure of a Sub-contractor to perform any / all of its

obligations under this contract.

8 Document Establishing Products, Services Eligibility & Conformity to RFP

8.1 Pursuant to ITB Sub-section 5.2, the Contractor shall furnish, as part of its

Proposal, documents establishing the eligibility and conformity to the RFP

Documents of all products and services that the Contractor proposes to supply

under the contract. This includes all the information/evidences needed to

evaluate the contractor as set forth in section G (Bidder’s Qualifications, Experience

& Evaluation).

Page 38 of 189


8.2 The documentary evidence of conformity of the products and services to the

RFP Documents may be in the form of written descriptions, literature, diagrams,

certifications and client references, including:

8.2.1 A detailed description of the essential technical and performance

characteristics of the products;

8.2.2 An item-by-item commentary on PIAC’s Product and Services Requirements, as detailed in Sections C, D & E, demonstrating the substantial responsiveness of the proposed solution to the specifications provided; and

8.2.3 A confirmation that the Contractor shall accept responsibility for the

successful integration and interoperability of all proposed products and other PIA systems as required by the RFP Documents. (refer Section A, sub-section A5-1)

9 Bid Bond

9.1 Pursuant to ITB Sub-section 9, the Contractor shall furnish, along with its

Financial Proposal, a bid bond for 2% (two percent) of the total amount of the

Products, Services and Support Prices.

9.2 The bid bond is required to protect PIA against the risk of the Contractor’s

conduct that would warrant the security’s forfeiture, as per ITB Sub-section 9,

item 9.7.

9.3 The bid bond shall be denominated in USD, shall be valid for One Hundred

and Eighty (180) days beyond the validity of the Proposal, and shall be in one

of the following forms:

9.3.1 A bank guarantee by a Pakistani Scheduled bank of the Contractor’s

choice, in the form provided in the RFP Documents;

9.3.2 A Pay Order / Demand Draft drawn on a Pakistani Scheduled bank.

9.4 Any Proposal not secured in accordance with ITB Sub-section 9, items 9.1

and 9.3 will be rejected by PIA and the Contractor shall not hold PIA liable in

anyway whatsoever for any such rejection.

9.5 Unsuccessful Contractors’ bid bond will be discharged or returned as

promptly as possible after the expiration of the period of Proposal validity

prescribed by PIA pursuant to ITB Sub-section 10.

Page 39 of 189


9.6 The successful Contractor’s bid bond will be discharged upon the Contractor

signing the contract, pursuant to ITB Sub-section 22, and furnishing the

performance guarantee, pursuant to ITB Sub-section 21.

9.7 The bid bond may be forfeited:

9.7.1 If a Contractor attempts to withdraw its Bid before the date stipulated in

the RFP for the validity of the Bid or any extension in this date agreed

between the Company and the Contractor,

9.7.2 If a Contractor attempts to modify or amend its Bid without the approval

/ consent of the Company before the date stipulated in the RFP for the

validity of the Bid or any extension to this date agreed between the

Company and the Contractor,

9.7.3 The Contractor shall not hold the Company liable in anyway

whatsoever for the amount so forfeited by the Company.

10 Period of Validity of Proposals

Proposals shall remain valid for at least 180 days from the date of Proposal submission

or any extension thereof, prescribed by PIAC. A Proposal valid for a shorter period

shall be rejected by PIAC.

11 Tender Proceedings

For sake of clarity, the PPRA (Public Procurement Regulatory Authority of Pakistan) guidelines for Single stage – two envelope procedure, which are as follow, shall be followed.

11.1 The bid shall comprise a single package containing two separate envelopes. One envelope shall contain the financial proposal while the other one shall contain the technical proposal;

11.2 The envelopes shall be marked as “FINANCIAL PROPOSAL” and

“TECHNICAL PROPOSAL” in bold and legible letters to avoid confusion; 11.3 Initially, only the envelope marked “TECHNICAL PROPOSAL” shall be

opened; 11.4 The envelope marked as “FINANCIAL PROPOSAL” shall be retained in the

custody of PIA without being opened; 11.5 PIA shall evaluate the Technical Proposal in a manner prescribed in the RFP

documents, without reference to the price(s) and reject any proposal which does not conform to the specified requirements;

Page 40 of 189


11.6 During the Technical evaluation, no amendments in the technical proposal

shall be permitted; 11.7 The financial proposals of bids shall be opened publicly at a time, date and

venue announced and communicated to the bidders in advance; 11.8 After the evaluation and approval of the technical proposal(s), PIA shall at a

time within the bid validity period, publicly open the financial proposals of the technically accepted bids only. The financial proposal of bids found technically non-responsive shall be returned un-opened to the respective bidders; and

11.9 The bid found to be the lowest evaluated (as per prescribed criteria) shall be

accepted.

12 Submission of Proposals

12.1 The Bidder is required to submit an original and one copy of each of its

Technical and Commercial Proposals clearly mark each “ORIGINAL BID” or

“COPY OF BID”, as appropriate. In the event of any discrepancy between

them, the original shall govern.

12.2 The Technical and Commercial Proposals shall be typed or written in indelible

ink and shall be signed by a person or persons duly authorized to bind the

Bidder to the contract

12.3 Bidders are required to submit their offer in sealed envelopes either in person

or through courier. Each offer should be clearly marked as “Bid for MRO / M&E

solution” at top of the envelope.

12.4 The Technical and Financial Proposals shall be submitted in separately sealed

envelopes, each marked “Technical Proposal” and “Financial Proposal”

accordingly, and bearing the name and complete return address of the Bidder,

be addressed to:


Supply Chain Department (Store Building)

PIA Head Office

Airport, Terminal-1

Karachi 75200

PAKISTAN

Ph: +92-21-99044423


Page 41 of 189


13 Deadline for Submission of Proposals

13.1 Proposals must be received by PIAC at the address and by the time

specified in the RFP Document covering letter. Proposals received after

this deadline will be rejected and returned to the Bidder unopened.

13.2 PIAC may, at its discretion, extend this deadline for the submission of

Proposals, in which case all rights and obligations of PIAC and Bidders

previously subject to the deadline will thereafter be subject to the deadline

as extended.

13.3 PIAC reserves the right to reject any or all proposals or divide the business

in more than one bidder or not to implement the MRO / M&E solution.

14 Opening of Proposals by PIA

14.1. PIA will open all Technical Proposals at a place and time to be advised in

the covering letter by PIA. Contractors or their authorized representatives may attend the opening, and those who are present shall sign a register evidencing their attendance.

14.2. No Proposal shall be rejected at the time of Proposal opening, except for late Proposals, which shall be returned unopened to the Contractor.

14.3. The Commercial Proposals of Contractors will be opened subsequently and evaluated. Contractors will be informed of the place and time by PIA.

15 Clarification of Proposals

15.1. During evaluation of Proposals, PIA may, at its discretion, ask the Contractor for a clarification of its Proposal. The request for clarification and the response shall be in writing, and no change in the prices or substance of the Proposal shall be sought, offered, or permitted during evaluation of the Proposal.

15.2. PIA may request the Contractor to arrange site visits for its reference sites.

15.3. PIA may also request the Contractor to give “proof of concept” by developing prototypes of specific scenarios identified by PIA.

16 PIA’s Right to accept any Proposal and to reject any or All Proposals

16.1. PIA reserves the right (without limitation to any other right whatsoever) to accept or reject any Proposal, or to annul the bidding process and reject all

Page 42 of 189


Proposals at any time prior to contract award without incurring any liability to the affected Contractor or Contractors.

16.2. PIA also reserves the right (without limitation to any other right whatsoever) to award the consolidated contract in its entirety to a single Contractor or to award it in parts to more than one Contractor without incurring any liability to the affected Contractor or Contractors.

17 Evaluation &Finalization of Selection.

17.1. After receipt of proposals from the Contractors, PIA will evaluate and study the submitted proposals. PIA does not bind itself to award the contract to the lowest or to any Contractor but will take into consideration all relevant facts and aspects. Finalization of the Contract between the successful Contractor and PIA will be held in the presence of members of PIA’s Project team and Steering committee at PIA Head Office. The aim is to reach agreement on all points and sign a contract.

17.2. Having selected the successful Contractor on the basis of, among other

things, an evaluation of the total solution offered, proposed methodology (work plan), verifiable successful implementations, and proposed key professional staff, PIA expects to finalize a contract on the basis of the products and available expertise named in the proposal. Before contract finalization, PIA will require assurances that products and experts will be actually available. PIA will not consider substitutions during contract finalization unless both parties agree that undue delay in the selection process makes such substitution unavoidable or that such changes are critical to meet the objectives of the assignment.

17.3. The finalization of the contract with the successful Contractor will conclude

with a review of the agreed draft, to be signed by PIA and the Contractor, ensuring successful delivery and completion of the project. PIA and the successful Contractor will initial the agreed draft of the contract. If this process fails, PIA may invite the next Contractor for the award of the assignment. In this regard, Contractors should submit draft copies of their proposed contracts and Service Level Agreements along with their Technical Proposals.

18 Confidentiality

18.1 Information relating to evaluation of proposals and recommendations concerning awards will not be disclosed to the Bidder or to other persons not officially concerned with the process. The Bidder shall maintain complete confidentiality of its proposal and shall not disclose the proposal or any terms thereof to any unrelated person or any third party. The Bidder shall also keep confidential all its discussions and negotiations with PIAC.

Page 43 of 189


18.2 For the purpose of this RFP all Bidders receiving or responding to this RFP

are considered potential contractors and have been identified throughout the

RFP accordingly.

19 Bidder’s Profile

In assessing a potential contractor’s ability to provide the MRO / M&E System

Renewal Program solution to PIAC, PIAC is seeking details of the Bidders’

structure including:

19.1 The core activities of the business; 19.2 The products and/or services provided; and 19.3 The future Plans of the bidder.

20 Legal Binding

By submitting a Proposal, the Bidder agrees to be legally bound by the terms and

conditions set out in this RFP. The Proposal will be considered as a binding offer

from the supplier capable of acceptance by PIAC. If during the course of any

discussions or negotiations PIAC and the Bidder agrees to vary any terms or the

Proposal, the Proposal will be deemed to be amended to the extent of the agreed

variation and PIAC may accept the Proposal as deemed amended.

21 Performance Guarantee

21.1. Within five (5) working days of the receipt of notification of award of the

Contract from PIA, the successful Contractor shall furnish a Performance Guarantee for 5% (five percent) of Contract value in accordance with the conditions of Contract, using the Performance Security Form provided in the RFP document.

21.2. In case joint venture is successful in the bidding process, the Lead Member of such joint venture will be responsible to PIA for performance of obligations under the agreement as principal obligator.

22 Signing of Contract

22.1 Within four (04) working days of receipt of the Performance Guarantee in

accordance with ITB Sub-section 21, PIA will send the successful Contractor the Contract Form provided in the RFP documents, incorporating all agreements between the parties.

22.2 Within four (04) working days of receipt of the Contract Form, the successful Contractor shall sign and date the contract and return it to PIA.

Page 44 of 189


22.3 By mutual agreement in writing, the contract signature date may be postponed by up to fifteen (15) days.

23 Contacting PIA

Any effort by the Contractor to unethically influence PIA in the process of evaluating Proposals and in decisions concerning award of the contract will result in the rejection of the Contractor’s Proposal.

The Contractors submitting proposals should attach a declaration that:

23.1 They will not obtain or induce the procurement of the contract or any right,

interest, privilege, or other obligation or benefit related to the contract from PIA or the Government of Pakistan, or any subdivision or agency thereof, through any corrupt business practice.

23.2 They will not give or agree to give and shall not give or agree to give to

anyone within or outside Pakistan either directly or indirectly through any person or organization, including affiliates, agents, associates, brokers, consultants, directors, promoters, shareholders, sponsors or subsidiaries, any commission, gratification, bribe, finder’s fee or kickback, whether described as consultation fee or otherwise, with the object of obtaining or inducing pursuant to the contract or any right, interest, privilege or other obligation or benefit related to the contract in whatsoever form.

23.3 They have made and will make full disclosure of all contracts and

arrangements with all persons / organizations in respect of or related to the proposed contract with PIA and have not taken any action or will not take any action to circumvent the above declaration, representation or warranty.

23.4 They agree to pay compensation to PIA in an amount equivalent to the direct

losses to PIA, which would include the sum of any commission, gratification, bribe, finder’s fee or kickback that would otherwise have been given to PIA in the form of a concession, given by the parties submitting proposals for the purpose of corruptly obtaining or including the procurement of the contract or any right, interest or other obligation or benefit related to this contract in whatsoever form from the parties submitting proposals, if it shall ultimately be determined by a final judicial decision that the party submitting proposals has so obtained or induced the procurement of the contract, or any right, interest, privilege or other obligation or benefit related to such contract.

P

age 45

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

B2

SU

MM

AR

Y O

F R

EQ

UIR

EM

EN

TS

This

schedu

le lis

ts a

ll majo

r com

ponents

of th

e M

RO

/ M&

E S

olu

tion

to b

e p

rocure

d th

rou

gh th

is R

equest fo

r Pro

posal.

Furth

er d

eta

ils a

nd e

xa

ct s

pecific

atio

ns fo

r each ite

m a

re in

clu

ded in

the S

ectio

ns C

, D a

nd E

.

Item

Typ

e

Descrip

tion

P

roje

ct

Site

(s)

MR

O / M

&E

P

ackage

Applic

atio

n s

oftw

are

module

s to

meet th

e A

pplic

atio

ns re

qu

irem

ents

as p

er d

eta

ils in

Sectio

n C

. A

lso, a

ny A

dd-o

n re

qu

ired fo

r MR

O / M

&E

solu

tion, if a

ny

Head O

ffice

Oth

er

Locatio

ns

3rd P

arty

S

oftw

are

A

s re

quire

d b

y th

e p

rop

osed M

RO

/ M&

E P

ackage a

nd A

dd-o

n A

pp

lica

tions

Head O

ffice

DB

MS

A

s re

quire

d b

y th

e p

rop

osed M

RO

/ M&

E P

ackage a

nd A

dd-o

n A

pp

lica

tions

Head O

ffice

Hard

ware

Recom

mended c

onfig

ura

tion o

f hard

ware

and

opera

ting s

yste

m s

oftw

are

for th

e P

roductio

n

Enviro

nm

ent w

ill be p

rovid

ed b

y th

e C

ontra

cto

r and it s

hall n

ot b

e b

indin

g o

n P

IA to

pro

cure

th

is fro

m th

e C

ontra

cto

r. In

terim

Applic

atio

n / D

ata

Serv

er(s

) inclu

din

g O

pera

ting S

yste

ms a

s re

quire

d b

y th

e p

rop

osed

M

RO

/ M&

E S

olu

tion fo

r Tra

inin

g, D

evelo

pm

ent, T

estin

g a

nd Q

uality

Assura

nce

Enviro

nm

ents

will b

e p

rovid

ed b

y th

e C

ontra

cto

r at its

ow

n c

ost

Head O

ffice

Oth

ers

A

pplic

atio

n D

evelo

pm

ent T

ools

, Query

and R

eport G

enera

ting T

ools

, Syste

m A

dm

inis

tratio

n

Tools

, Opera

ting S

yste

ms, S

yste

ms M

anagem

ent T

ools

, etc

. H

ead O

ffice

Insta

llatio

n /

Imple

menta

tion

Serv

ices

Insta

llatio

n, c

onfig

ura

tion a

nd im

ple

menta

tion o

f Hard

ware

an

d O

pera

ting S

yste

m, M

RO

/ M&

E

Sta

ndard

Softw

are

, Add

-on A

pplic

atio

ns, 3

rd Party

Applic

atio

ns.

Head O

ffice

Oth

er

Locatio

ns

Tra

inin

g

End U

ser,

Po

wer

Use

r and M

ana

gem

ent

train

ing fo

r M

RO

/

M&

E,

Add-o

n and 3

rd P

arty

Applic

atio

ns, T

echnic

al tra

inin

g fo

r De

velo

pers

and A

dm

inis

trato

rs o

n A

pplic

atio

n D

evelo

pm

ent

Tools

, Reportin

g T

ools

, DB

MS

, DB

A to

ols

, OS

, Syste

m M

anag

em

ent T

ools

, etc

.

Head O

ffice

Oth

er

Locatio

ns

Data

Mig

ratio

n

Develo

pm

ent o

f Stra

tegy&

Pla

n fo

r mig

ratio

n o

f data

from

legacy s

yste

ms a

nd m

anual re

cord

s.

Head O

ffice

Recurre

nt

Serv

ices

Post-Im

ple

menta

tion s

upport fo

r thre

e y

ears

(afte

r Warra

nty

Perio

d) fo

r MR

O / M

&E

Package,

Add-o

n a

pplic

atio

ns, H

ard

ware

and 3

rd Party

So

ftware

Main

tenance a

nd

Support

All L

ocatio

ns

Page 46 of 189


B3 TEMPLATE FORMS

Notes for Contractors on the Template Forms

1. The Contractor shall complete and submit with its Proposal the Proposal

Form and the required Price Schedules and in accordance with the

requirements included in Section B, Subsection B3.

2. The Contractor should provide the Bid Bond as per the form included in this

Subsection.

3. The Performance Guarantee form should not be completed by the Contractor

at the time of their Proposal preparation. Only the successful Contractor will

be required to provide Performance Guarantee as per the form included in

Section B. PIA, however reserves the right, in case of failure on part of the

Contractor to provide the aforesaid Performance Guarantee in accordance to

the instructions as laid down in Instruction to Bidders (ITB) Section B1, sub-

section 20, within the specified time, to forfeit the bid security furnished by the

Contractor.

Page 47 of 189


Proposal Form

To:


Procurement and Logistics Building

PIA Head Office

Airport Terminal-1

Karachi 75200

PAKISTAN

Dear Sir:

Having examined the Request for Proposal Documents including Addenda Nos. [insert

numbers, if issued and applicable], the receipt of which is hereby duly acknowledged, we,

the undersigned, offer to produce, deliver, install, implement, support and maintain the

MRO / M&E Solution in full conformity with the said RFP Documents.

We undertake, if our Proposal is accepted, to implement the MRO / M&E Solution in

accordance with the Project milestones agreed with PIA.

We certify that a bid bond for 2% (two percent) of the total amount of the proposal is

submitted along with Financial Proposal.

If our Proposal is accepted, we will provide a Performance Guarantee in the form and in the

amounts, and within the times stipulated in the Request for Proposal Documents.

We agree to abide by this Proposal for a period of 180 days from the date fixed for

Proposal submission, or any extended date, and it shall remain binding upon us and may

be accepted at any time before the expiration of that period. Until a formal Contract is

prepared and executed, this Proposal, together with your written acceptance thereof and

your notification of award, shall constitute a binding Contract between us.

We understand that you are not bound to accept the lowest or any Proposal you may

receive.

Dated this ________________ day of ________________ 20______.

_______________________________________________________

[Signature] [In the capacity of]

Duly authorized to sign Proposal for and on behalf of _____________

Page 48 of 189


Bidding Organization Profile

[Provide a brief (not more than five pages) description of the background and organization of your firm/entity and each sub-contractor for this assignment.]

Page 49 of 189


Bidder’s Experience

[Using the format below, provide information on each assignment for which your firm, and each associate for this assignment, was legally contracted either individually as a corporate entity or as one of the major companies within an association, for carrying out services similar to the ones requested under this

assignment. Attach details on separate sheet if necessary.]

Assignment name:

Approx. value of the contract (in current USD):

Country/State/Province: Location within country:

Duration of assignment (months):

Name of Client:

Total No of staff-months of the assignment: (If applicable)

Address:

Approx. value of the services provided by your firm under the contract (in current USD):

Start date (month/year): Completion date (month/year):

No of professional staff-months provided by Sub-Contractor:

Name of Sub-Contractor, if any:

Name of senior professional staff of your firm involved and functions performed (indicate most significant profiles such as Project Director/Coordinator, Team Leader):

Narrative description of Project:

Description of actual services provided by your staff within the assignment:

Page 50 of 189


Description of Approach, Methodology &

Project Plan for the Project

[In order to ensure timely completion of this project, the consultant/service provider should submit a

methodology and detailed Project Plan including the estimated completion timeline of each area/sub area

of the scope]

Page 51 of 189


Team Composition and Task Assignments

[Using the format below, provide information regarding the nominated project team for this assignment

based on proposed methodology and work plan. Depending upon skill sets, experience and technology

certifications as mentioned in CV and subject to the submission of documentary evidences]

Professional Staff / Nominated Project Team

Name of Staff Position Assigned Area/Task Assigned

in this Project Skill Sets and Technology

Certification Name(s)

Page 52 of 189


Curriculum Vitae (CV) for Professional Staff

[CVs should be submitted for Nominated Project Team/Professional Staff only]

1. Proposed Position:

2. Name of Firm [Insert name of firm proposing the staff]:

3. Name of Staff [Insert full name]:

4. Date of Birth: Nationality:

5. Education [Indicate college/university and other specialized education of staff member, giving

names of institutions, degrees obtained, and dates when obtained]:

6. Technology Certification(s) Achieved [Provide name of all the technology certification achieved

by the staff]

____________________________________________________________________________________

_

7. Other Trainings [Indicate significant training since, education under 5, were obtained]:

8. Countries of Work Experience: [List countries where staff has worked in the last ten years]:

9. Languages [For each language indicate proficiency: good, fair, or poor in speaking, reading, and

writing]:

10. Employment Record [Starting with present position, list in reverse order every employment held

by staff member since graduation, giving for each employment (see format here below): dates of

employment, name of employing organization, positions held.]:

From [Year]: To [Year]:

Employer:

Positions held:

11. Detailed Tasks Assigned

Page 53 of 189


[List all tasks to be performed under this assignment]

12. Work Undertaken that Best Illustrates Capability to Handle the Tasks Assigned

[Among the assignments in which the staff has been involved, indicate the following information for

those assignments that best illustrate staff capability to handle the tasks listed under point 11.]

Name of assignment or project:

Year:

Location:

Client:

Main project features:

Positions held:

Activities performed:

13. Certification:

I, the undersigned, certify that to the best of my knowledge and belief, this CV correctly describes myself,

my qualifications, and my experience. I understand that any willful misstatement described herein may

lead to my disqualification or dismissal, if engaged.

Date:

[Signature of staff member or authorized representative of the staff] Day/Month/Year

Full name of authorized representative:

Pag

e 5

4 o

f 189

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Pro

du

cts

Pric

e S

ch

edule

Nam

e o

f Contra

cto

r

Page _

__ o

f ____

Item

N

o.

Pro

duct D

escrip

tion

Contra

cto

r P

roposal

Refe

rence

Pro

duct

Pro

ducer

Partn

er o

r Sub-

contra

cto

r R

esponsib

le fo

r S

upply

an

d

Insta

llatio

n

Quantity

Unit

Pric

e2

(US

D)

Tota

l Pric

e3

(US

D)

(1)

(2)

(3

) (4

) (5

) (6

) (7

) = (5

) x (6

)

MR

O / M

&E

Packag

e

&A

dd

-on

A

pp

licatio

ns

Subto

tal

DB

MS

Subto

tal

3rd P

arty

So

ftware

Subto

tal

Hard

ware

: Subto

tal

Clo

ud

Serv

ices

: S

ubto

tal

Oth

er P

rod

ucts

: Subto

tal

TO

TA

LS

A

dditio

nal M

RO

/ M&

E

Lic

ensin

g C

ost P

er U

ser4

Sig

natu

re o

f Contra

cto

r

-----------------------------------------------------

2Pric

es in

clu

de a

ll taxes p

ayable

by th

e C

ontra

cto

r there

on.

3In c

ase o

f dis

cre

pan

cy b

etw

een u

nit p

rice a

nd to

tal, th

e u

nit p

rice s

hall p

revail. S

imila

rly, s

ubto

tals

shall p

revail o

ver to

tals

. 4 P

rice fo

r Each A

dditio

nal M

RO

/ M&

E U

ser s

hould

be

pro

vid

ed s

epara

tely

Page 5

5 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Serv

ices P

rice S

ch

ed

ule

(Prio

r to M

ain

ten

an

ce)

Nam

e o

f Contra

cto

r

Page _

__ o

f ____

Sig

natu

re o

f Contra

cto

r

_________

____

____

____

___

___

___

5S

erv

ice

pric

es in

clu

de a

ll taxe

s p

aya

ble

by th

e C

on

tracto

r the

reo

n.

6In

case o

f dis

cre

pancy b

etw

een u

nit p

rice a

nd to

tal, th

e u

nit p

rice s

hall p

revail. S

imila

rly, s

ubto

tals

shall p

revail o

ver to

tals

.

Item

N

o.

Serv

ice D

escrip

tion

Contra

cto

r P

roposal

Refe

rence

Partn

er o

r Sub-

contra

cto

r R

esponsib

le fo

r Serv

ice

D

eliv

ery

Quantity

U

nit P

rice

5 (U

SD

) T

ota

l Pric

e6

(US

D)

(1)

(2)

(3

) (4

) (5

) (6

) = (4

) x (5

)

Imp

lem

en

tatio

n

• M

RO

/ M&

E

Package

• A

dd

-on A

pplic

atio

ns

• 3

rd Party

Softw

are

S

ubto

tal

Tra

inin

g

• M

aste

r Tra

iners

•

End

-users

•

Technic

al

• A

pps D

ev T

ool

• R

eportin

g T

ool

• D

BA

Tool

• D

BM

S

• O

pera

ting S

yste

m

• S

ys A

dm

in / M

gm

t. •

Oth

ers

S

ubto

tal

Data

Mig

ratio

n

D

ocu

me

nta

tion

Oth

er

T

OT

AL

S

Page 5

6 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Recu

rren

t Co

sts

Sch

ed

ule

(Pric

es d

urin

g th

e m

ain

tenance p

erio

d fo

r first th

ree y

ears

)

Nam

e o

f Contra

cto

r

Page _

__ o

f ____

Sig

natu

re o

f Contra

cto

r

________

___

____

____

___

___

____

_

7The a

nnual c

ost s

hould

indic

ate

the to

tal c

osts

for th

e y

ear in

clu

siv

e o

f all ta

xes.

Ma

xim

um

com

pounded c

osts

per a

nnum

afte

r exp

iratio

n o

f the

warra

nty

perio

d (in

US

D)7

Ye

ar 1

Y

ear 2

Y

ear 3

T

ota

l Recurre

nt C

osts

Main

ten

an

ce F

ee:

MR

O / M

&E

Package

Add-o

n A

pplic

atio

n

3rd P

arty

Softw

are

DB

MS

Su

b-to

tal

Recu

rren

t So

ftware

Lic

en

sin

g

Fees:

MR

O / M

&E

Package

Add-o

n A

pplic

atio

n

3rd P

arty

Softw

are

DB

MS

Su

b-to

tal

Hard

ware

main

ten

an

ce c

osts

C

lou

d S

erv

ices

co

sts

O

ther re

cu

rren

t co

sts

T

OT

AL

S

Page 5

7 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Pro

po

sal P

rice S

um

mary

Fo

rm

Nam

e o

f Contra

cto

r

P

age _

__ o

f ____

Pro

ducts

Pric

e T

ota

l S

erv

ices P

rice T

ota

l R

ecurre

nt C

osts

Tota

l T

ota

l P

roposal

Pric

e:

Am

ount in

US

D

Sig

natu

re o

f Contra

cto

r

Page 5

8 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Pro

po

sed

Paym

en

t Pla

n

Team

Mo

biliz

atio

n

10

%

Pro

ject C

on

trol B

oo

k

5%

Gap

An

aly

sis

10

%

So

lutio

n D

esig

n

10

%

Syste

m C

on

figu

ratio

n

10

%

Data

Mig

ratio

n

10

%

User A

ccep

tan

ce T

est

15

%

Go

Liv

e P

rod

uctio

n

15

%

Po

st G

o L

ive

15

%

Page 5

9 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Bid

Bo

nd

Fo

rm

BA

NK

GU

AR

AN

TE

E N

O._

_____________

DA

TE

D: _

___________________________

AM

OU

NT

: _________________________

EX

PIR

Y: _

_________________________

Pakis

tan In

tern

atio

nal A

irlines C

orp

ora

tion L

imite

d

Kara

chi A

irport

Kara

chi

BID

BO

ND

AS

PE

R T

EN

DE

R N

O. _

____________

FO

R _

___________

WH

ER

EA

S

_________________________________________________

(here

inafte

r calle

d

“the

Contra

cto

r”) has

subm

itted

to

PA

KIS

TA

N

INT

ER

NA

TIO

NA

L

AIR

LIN

ES

(h

ere

inafte

r calle

d

“the

Com

pany”)

a

bid

date

d

___

day

of

____________ y

ear _

____, fo

r the e

xecutio

n o

f the a

bo

ve w

ork

.

AN

D W

HE

RE

AS

it

is pro

vid

ed by th

is bid

th

at

the C

ontra

cto

r shall

furn

ish th

e C

om

pany w

ith security

by w

ay of

an

unq

ualifie

d b

ond o

r guara

nte

e fo

r the d

ue fu

lfillment o

f certa

in m

atte

rs re

latin

g to

this

Bid

.

AN

D

WH

ER

EA

S

________________________

_________________________

have

at

the

req

uest

of

the

Contra

cto

r

agre

ed to

giv

e s

uch s

ecurity

.

NO

W T

HE

RE

FO

RE

WE

____________________________________________ o

f ________________________________

________________________________________________

_

_______________________________________

___underta

ke,

subje

ct

to

the

follo

win

g

term

s,

to

pay

to

the

Com

pany

unconditio

nally

and irre

vocably

on its

first w

ritten d

em

and s

uch s

um

s a

s m

ay b

e c

laim

ed b

y it in

writin

g u

pto

a m

axim

um

of

US

D _

____________ a

s re

cord

ed o

n th

e R

eq

uest fo

r Pro

posal.

1.

The C

om

pany m

ay c

laim

paym

ent h

ere

under if e

ither:

Page 6

0 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

1.1

Befo

re th

e d

ate

stip

ula

ted in

the R

eq

uest fo

r Pro

posal fo

r the v

alid

ity o

f the B

id o

r any e

xte

nsio

n to

this

date

agre

ed b

etw

een th

e C

om

pany a

nd th

e C

ontra

cto

r, the C

ontra

cto

r atte

mpts

to w

ithdra

w, m

odify

, or a

mend h

is

bid

; or

1.2

The C

om

pany has ag

reed w

ith th

e C

ontra

cto

r th

at

a C

ontra

ct

will

be execute

d,

but

the C

ontra

cto

r fa

ils to

execute

the fo

rmal C

ontra

ct D

ocum

ent w

hen re

queste

d to

do s

o b

y th

e C

om

pany; o

r

1.3

At th

e tim

e o

f ente

ring in

to a

Contra

ct w

ith th

e C

om

pany to

underta

ke a

nd c

om

ple

te th

e w

ork

, the C

ontra

cto

r

fails

to p

rovid

e th

e B

onds a

nd G

ua

rante

es re

quire

d b

y s

uch C

ontra

ct.

2.

Paym

ent s

hall b

e m

ade h

ere

under o

n th

e C

om

pany’s

first w

ritten d

em

and to

us s

tatin

g th

at o

ne o

r more

of th

e a

bove e

vents

has o

ccurre

d w

ithout a

ny re

fere

nce to

the c

ontra

cto

r; and w

ithout fu

rther c

onditio

n o

r substa

ntia

tion a

nd w

ithout th

e n

ecessity

of a

ny p

roceedin

gs w

hate

ver, w

heth

er ju

dic

ial o

r oth

erw

ise b

ein

g in

stitu

ted b

y th

e C

om

pany.

3.

The B

ond s

hall re

main

in fu

ll forc

e a

nd e

ffect u

ntil th

e d

ate

when th

e C

ontra

cto

r shall h

ave e

xecute

d th

e fo

rmal C

ontra

ct

Docum

ent a

nd p

rovid

ed th

e n

ecessary

Bonds a

nd G

uara

nte

es th

ere

under o

r upon th

e w

ritten re

jectio

n b

y th

e C

om

pany o

f the

Contra

cto

r’s B

id, w

hic

hever is

earlie

r, at w

hic

h tim

e th

e B

ond s

hall a

uto

matic

ally

expire

and b

e o

f no fu

rther e

ffect.

IN W

ITN

ES

S W

HE

RE

OF

this

Bond h

as b

een d

uly

sig

ned a

nd s

eale

d o

n th

e _

____ d

ay o

f ________________ y

ear

______.

For a

nd o

n b

ehalf o

f

__________________________________

_______________

___________________

______________

______

Offic

er

Manag

er

Witn

esses:

1

. _________________ 2

. __________________

Page 6

1 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Fo

rm o

f Co

ntra

ct A

gre

em

en

t T

HIS

A

GR

EE

ME

NT

is

m

ade

the

_____

day

of

_______

___

year

____

_

betw

een

Pakis

tan

Inte

rnatio

na

l A

irline

s

(here

inafte

r calle

d “P

IA”) o

f the o

ne p

art a

nd [n

am

e o

f Contra

cto

r] of [c

ity a

nd c

ountry

of C

ontra

cto

r] (here

inafte

r calle

d

“the C

ontra

cto

r”) of th

e o

ther p

art:

WH

ER

EA

S P

IA in

vite

d P

roposals

fo

r certa

in pro

ducts

an

d ancilla

ry serv

ices,

viz

., M

RO

/

M&

E S

olu

tion an

d has

accepte

d a

Pro

posal b

y th

e C

ontra

cto

r for th

e s

upply

of th

ose p

roducts

and s

erv

ices in

the s

um

of [c

ontra

ct p

rice in

word

s a

nd fig

ure

s] (h

ere

inafte

r calle

d “th

e C

ontra

ct P

rice”).

NO

W T

HIS

AG

RE

EM

EN

T W

ITN

ES

SE

TH

as fo

llow

s:

1.

In th

is A

gre

em

ent w

ord

s a

nd e

xpre

ssio

ns s

ha

ll have th

e s

am

e m

eanin

gs a

s a

re re

spectiv

ely

assig

ned to

them

in th

e

Conditio

ns o

f Contra

ct re

ferre

d to

.

2.

The fo

llow

ing d

ocum

ents

shall b

e d

eem

ed to

form

and b

e re

ad a

nd c

on

stru

ed a

s p

art o

f this

Agre

em

ent, v

iz.:

(a) In

stru

ctio

ns to

Co

ntra

cto

rs;

(b)

Sum

mary

of R

equire

ments

;

(c) P

roduct a

nd S

erv

ices R

equire

ments

;

(d)

Genera

l Instru

ctio

ns a

nd C

onditio

ns o

f Contra

ct;

(e) S

pecia

l Term

s a

nd C

onditio

ns o

f Contra

ct;

(f) C

ontra

cto

r’s P

roposa

l.

3.

In c

onsid

era

tion o

f the p

aym

ents

to b

e m

ade b

y P

IA to

the C

ontra

cto

r as h

ere

inafte

r mentio

ned, th

e C

ontra

cto

r here

by

cove

nants

with

PIA

to p

rovid

e th

e p

roducts

an

d s

erv

ices a

nd to

rem

edy d

efe

cts

there

in in

confo

rmity

in a

ll respects

with

the p

rovis

ions o

f the a

gre

em

ent.

4.

PIA

here

by c

oven

ants

to p

ay th

e C

ontra

cto

r in c

onsid

era

tion o

f the p

rovis

ion o

f the p

roducts

and s

erv

ices a

nd th

e

rem

edyin

g o

f defe

cts

there

in, th

e C

ontra

ct P

rice o

r such o

ther s

um

as m

ay b

ecom

e p

ayab

le u

nder th

e p

rovis

ions o

f the

Contra

ct a

t the tim

es a

nd in

the m

anner p

rescrib

ed b

y th

e C

ontra

ct.

5.

Unle

ss e

xpre

ssly

sta

ted

here

in, w

here

ver a

ny p

erio

d o

r perio

ds o

f time a

re s

pecifie

d, th

e p

artie

s h

ere

to a

gre

e th

at tim

e

shall b

e th

e e

sse

nce o

f the C

ontra

ct.

Page 6

2 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

6.

Unle

ss e

xpre

ssly

sta

ted h

ere

in, th

e fa

ilure

of o

ne p

arty

to e

xerc

ise a

ny o

ptio

n, rig

ht o

r rem

edy u

nder th

e C

ontra

ct o

r to

dem

and c

om

plia

nce o

f an

y o

blig

atio

n o

f the o

ther p

arty

, shall n

ot c

onstitu

te a

waiv

er o

f any s

uch o

ptio

n, rig

ht o

r rem

ed

y

or th

e p

erfo

rmance th

ere

of.

7.

Each o

f the rig

hts

and o

blig

atio

ns c

onta

ined in

this

Contra

ct s

hall b

e d

eem

ed to

be d

istin

ct a

nd s

evera

ble

so th

at if o

ne

such rig

hts

an

d o

blig

atio

ns s

hall b

e d

ecla

red o

r becom

e ille

gal, v

oid

or u

nenfo

rceable

, then

the re

main

ing rig

hts

and

oblig

atio

ns s

ha

ll (unle

ss th

e e

ffect is

to fru

stra

te th

e fu

ndam

enta

l basis

of th

is C

ontra

ct) c

ontin

ue in

full fo

rce a

nd e

ffect.

8.

The C

ontra

cto

r shall n

ot a

ssig

n a

ny o

f its d

utie

s / o

blig

atio

ns u

nder th

is c

ontra

ct to

any th

ird p

arty

.

9.

The p

artie

s to

the C

ontra

ct s

hall n

ot b

e lia

ble

for a

ny lo

ss, c

laim

s o

r dem

ands o

f any n

atu

re w

hats

oe

ver a

nd s

ha

ll not b

e

deem

ed in

bre

ach o

f this

Contra

ct b

ecause o

f an

y d

ela

y o

r failu

re in

observ

ing o

r perfo

rmin

g a

ny o

f the c

onditio

ns o

r

pro

vis

ions h

ere

of if s

uch d

ela

y o

r failu

re is

caused b

y o

r aris

es o

ut o

f any c

ircum

sta

nces w

hats

oe

ver, b

eyon

d th

e

affe

cte

d party

’s co

ntro

l, in

clu

din

g (b

ut

with

out

limitin

g th

e gen

era

lity of th

e fo

regoin

g),

decla

red or

undecla

red w

ar,

sabota

ge, b

lockad

e, re

vo

lutio

n, p

olic

e a

ctio

n, rio

ts o

r dis

ord

er, e

mbarg

oes o

r trad

e re

stric

tion

s o

f any s

ort, g

overn

ment

or q

uasi-g

overn

ment a

ctio

n, a

cts

of G

od, fire

, flood, e

arth

qu

akes, e

xplo

sio

n, a

ccid

ent, ra

dia

tion, s

trike, lo

ckouts

or o

ther

Labo

ur d

ispute

s o

r dis

aste

rs.

10

. T

he C

om

pany s

hall h

ave th

e rig

ht to

term

inate

the C

ontra

ct:

• If th

e C

ontra

cto

r, in th

e ju

dgm

ent o

f the c

om

pan

y, is

or h

as b

een e

ngag

ed in

corru

pt o

r fraudu

lent p

ractic

es in

com

petin

g fo

r or e

xecutin

g th

e C

ontra

ct

• If th

e C

ontra

cto

r com

mits

a b

reach o

f any o

f the te

rms a

nd c

onditio

ns o

f this

Contra

ct

In a

ny c

ase th

e C

om

pany te

rmin

ate

s th

e c

ontra

ct o

n a

ny o

f the a

fore

said

reasons, th

e C

ontra

cto

r shall b

e lia

ble

for a

ll

dire

ct lo

sses, d

am

ages a

nd c

harg

es in

curre

d b

y th

e C

om

pany, in

rela

tion to

the te

rmin

atio

n o

f this

contra

ct.

11

. A

ll dis

pute

s o

r an

y d

iffere

nce o

r questio

n w

hic

h m

ay a

rise b

etw

een th

e p

artie

s h

ere

to o

r an

y p

ers

on c

laim

ing th

ere

of,

touchin

g o

r aris

ing o

ut o

r in re

spect o

f this

Contra

ct o

r the s

ubje

ct m

atte

r there

of s

hall b

e re

ferre

d to

the a

rbitra

tion

in

accord

ance w

ith th

e A

rbitra

tion A

ct 1

940, e

ach p

arty

shall a

ppo

int its

ow

n A

rbitra

tor a

nd th

e d

ecis

ions in

such a

rbitra

tion

pro

ceed

ings s

hall b

e fin

al a

nd b

indin

g o

n b

oth

the p

artie

s. T

he p

artie

s s

ubm

it to th

e ju

risdic

tion o

f the c

ourts

of K

ara

chi,

PA

KIS

TA

N.

Page 6

3 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

IN

WIT

NE

SS

, wh

ere

of th

e p

artie

s h

ere

to h

ave

caused th

is A

gre

em

ent to

be e

xecute

d o

n th

e d

ay a

nd

ye

ar firs

t above w

ritten.

Sig

ned, s

eale

d, a

nd d

eliv

ere

d b

y th

e

said

[na

me o

f repre

senta

tive] (fo

r PIA

)

in th

e p

resence o

f [nam

e o

f witn

ess]

Sig

ned, s

eale

d, a

nd d

eliv

ere

d b

y th

e

said

[na

me o

f repre

senta

tive] (fo

r the C

ontra

cto

r)

in th

e p

resence o

f [nam

e o

f witn

ess]

Page 6

4 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Pe

rform

an

ce

Gu

ara

nte

e F

orm

BA

NK

GU

AR

AN

TE

E N

O._

______

____

___

DA

TE

D:

____

____

___

___

____

_____

____

_

AM

OU

NT

:

____

____

___

___

____

_____

__

_

EX

PIR

Y: _

____

___

___

____

____

___

___

__

Pakis

tan In

tern

atio

na

l Airlin

es C

orp

ora

tion L

imite

d

Kara

chi A

irport

Kara

chi

Dear S

ir,

PE

RF

OR

MA

NC

E G

UA

RA

NT

EE

DE

SC

RIP

TIO

N O

F W

OR

K _

____

____

___

___

_____

____

___

___

____

_____

____

Where

as,

we

unders

tand

that

yo

u

ha

ve

pla

ced

a

Work

C

ontra

ct

No.

_______

___

___

___

___

___

____

date

d

____

____

___

___

____

with

____

___

___

____

____

____

_

(The

Contra

cto

r) fo

r th

e

above

mentio

ned

work

and

that

in

accord

ance w

ith th

e te

rms o

f the c

ontra

ct, th

e C

ontra

cto

r is re

quire

d to

furn

ish a

Bank G

uara

nte

e in

respect o

f its o

blig

atio

ns

under th

e s

aid

contra

ct fo

r an a

mount e

qual to

5%

(five p

erc

ent) o

f the to

tal c

ontra

ct v

alu

e v

iz (a

mount o

f contra

ct in

word

s

and fig

ure

s).

No

w,

there

fore

, in

con

sid

era

tion of

the abo

ve,

we,

(Nam

e and ad

dre

ss of

Bank)

here

by G

UA

RA

NT

EE

irre

voca

bly

and

uncond

ition

ally

the d

ue p

aym

ent to

you u

pon d

em

and o

f first w

ritten s

uch s

um

or s

um

s n

ot e

xcee

din

g (a

mou

nt o

f gu

ara

nte

e

in w

ord

s a

nd fig

ure

s) w

ithout w

hats

oever rig

ht o

f obje

ctio

n in

the e

ven

t that th

e c

ontra

cto

r fails

to p

erfo

rm o

r fulfill a

ny o

f the

term

s a

nd c

onditio

ns o

f the c

ontra

ct a

t the tim

e o

r durin

g th

e p

erio

d s

pecifie

d th

ere

fore

in th

e c

ontra

ct, p

rovid

ed th

at a

ny

dem

and h

ere

under is

rece

ived in

writin

g a

t this

offic

e w

ithin

the v

alid

ity o

f this

guara

nte

e a

ccom

panie

d b

y y

our w

ritten

decla

ratio

n to

us th

at th

e C

ontra

cto

r has fa

iled to

com

ply

with

the te

rms o

f the c

ontra

ct, a

nd s

uch d

ecla

ratio

n s

hall b

e

Page 6

5 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

accepte

d b

y u

s a

s c

onclu

siv

e p

roof th

at th

e a

mount c

laim

ed is

due to

you, a

nd w

e s

hall fo

rthw

ith p

ay y

ou th

e e

ntire

am

ount

cla

imed.

Our lia

bility

un

der th

is g

uara

nte

e s

hall n

ot b

e a

ffecte

d b

y a

ny d

ispute

or d

iffere

nce b

etw

ee

n y

ou

and th

e C

ontra

cto

r or b

y a

ny

forb

eara

nce o

r indulg

en

ce g

rante

d b

y y

ou to

the C

ontra

cto

r or b

y a

ny o

ther s

ecurity

held

by y

ou fro

m th

e C

ontra

cto

r rela

ting

to th

e a

bove

-mentio

ned

Contra

ct o

r any v

aria

tion in

the c

ontra

ct o

r any o

ther m

atte

r or th

ing w

hic

h m

ight o

therw

ise a

ffect o

ur lia

bility

here

und

er.

We fu

rther g

uara

nte

e th

at n

o c

hange o

r additio

n to

or o

ther m

odific

atio

n o

f the te

rms o

f the C

ontra

ct s

hall in

an

yw

ay re

lease

us fro

m a

ny lia

bility

und

er th

is G

uara

nte

e a

nd w

e h

ere

by w

aiv

e n

otic

e o

f any s

uch c

han

ge, a

dditio

n o

r modific

atio

n.

This

Guara

nte

e w

ill rem

ain

valid

until ........................................... a

nd a

ny c

laim

s h

ere

under m

ust b

e re

ceiv

ed b

y th

at d

ate

,

afte

r whic

h th

is g

uara

nte

e w

ill becom

e n

ull a

nd v

oid

, and m

ust b

e re

turn

ed to

us fo

r cancella

tion.

This

guara

nte

e s

ha

ll be c

onstru

ed in

accord

ance w

ith th

e la

ws o

f Pakis

tan.

For a

nd o

n b

eha

lf of

____

____

___

___

____

_____

____

___

___

____

_____

____

___

____

____

___

___

____

_

____

____

___

___

____

__

Offic

er

M

an

ager

Witn

esses:

1. _

_____

___

____

___

_ 2

. ________

____

___

___

Page 6

6 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Co

ns

ortiu

m R

es

po

nsib

ility F

orm

N

am

e o

f Firm

8

Fo

rm o

f B

usin

ess

9 R

ole

in P

roje

ct10

Resp

on

sib

ilities

11

Pro

du

ct o

r S

erv

ice

12 to

be

Pro

vid

ed

Jo

int V

en

ture

A

gre

em

en

t13

Refe

ren

ce a

nd

Date

Lead C

ontra

cto

r

For e

ach p

artn

er lis

t, the s

taff m

em

bers

wh

o w

ill be a

part o

f the p

roje

ct, th

eir p

roposed ro

les a

nd th

e m

inim

um

com

mitte

d

man-d

ays fo

r each p

ers

on.

____

____

___

___

____

_____

____

___

___

____

_____

____

Sig

natu

re a

nd

Sta

mp

of A

uth

oriz

ed

Lead

Co

ntra

cto

r

8 E

nte

r the

na

me o

f ea

ch

of th

e C

onso

rtium

/ Jo

int V

en

ture

/ Su

b-C

on

tracte

d firm

s, s

tartin

g w

ith th

e L

ea

d C

on

tracto

r 9

Sta

te w

heth

er In

div

idual, S

ole

Pro

prie

tor, L

imite

d L

iability

Com

pan

y, P

artn

ers

hip

, Corp

ora

tion, e

tc.

10 S

tate

the ro

le o

f the F

irm o

n th

e P

roje

ct i.e

. whe

ther L

ead C

ontra

cto

r, Pro

ject M

an

ager, S

oftw

are

Su

pplie

r, Softw

are

Develo

pe

r, Tra

iner, e

tc.

11 C

learly

list a

ll the k

ey re

sponsib

ilities th

e F

irm w

ould

be

und

erta

kin

g o

n th

e P

roje

ct

12 In

clu

de a

time s

chedule

for p

rovis

ion o

f pro

ducts

and

serv

ices o

f each p

artn

er

13 C

opy(s

) of A

gre

em

ent(s

) to b

e a

ttached

Page 67 of 189


B4. Format and Contents of Proposal

1. General Proposal Requirements

1.1 Proposals should be prepared simply and provide a straightforward, concise

description of the Bidder’s capabilities to satisfy the requirements of this RFP.

1.2 Bidders must follow all formats and address all portions of the RFP set forth herein

providing all information requested. Bidders may retype or duplicate any portion of

this RFP for use in responding to the RFP, provided that the proposal clearly

addresses all of PIAC's information requirements.

1.3 Bidders must respond to every subsection under the Technical Proposal and Cost

Proposal sections. Bidders must label each response to RFP requirements with the

section and subsection numbers or Proposal Reference IDs associated with the

subject requirement in this RFP.

1.4 Proposals must not contain extraneous information. All information presented in a

Proposal must be relevant in response to a requirement of this RFP, must be

clearly labeled, and, if not incorporated into the body of the Proposal itself, must be

referenced to and from the appropriate place, within the body of the Proposal.

1.5 Proposals shall be prepared on standard A4 size paper. Foldouts containing charts,

spreadsheets, and oversize exhibits are permissible. Proposal pages must be

numbered and responses must be identified by the related RFP section number.

1.6 Bidders shall divide their responses to this RFP into a Technical Proposal and a

Financial Proposal. Financial Proposal and pricing information should not be

included in the Technical Proposal. Inclusion of Price Proposal or pricing in the

Technical Proposal shall make the proposal non-responsive.

2. Required Format of the Proposal

Each Contractor can submit only one Proposal. Bidders shall prepare their Bids

using the following structure and form.

2.1 Executive Summary

The Bidder’s response concerning its ability to satisfy the qualification, eligibility,

business and technical requirements as stated in the RFP Document. The Bidder

should summarize the proposed technical and service solution and qualitatively

describe its advantages in the Executive Summary.

2.2 Bidder’s Qualification and Experience

The Bidder should provide information regarding his eligibility, qualification and

relevant experience to perform the requirements under Section G, sub-section G1–

“Bidder’s Qualification and Experience” of this RFP.

Page 68 of 189


2.3 MRO / M&E Package

Complete details should be provided of the MRO / M&E Package that is being

proposed as part of the solution. The MRO / M&E Package’s general functional

description and capabilities, with particular reference is defined in Section C –

Product Requirements (MRO / M&E Package& add-ons). The MRO / M&E Package

should have all integrated modules and should seamlessly interface with PIAC’s

existing internal and external software with an overview of integration and data

transfer mechanisms. The security and manageability features should also be

highlighted. The Bidder should elaborate on the extent and efforts for customization

required to satisfy the functional requirements. Bidder should provide contingency

and backup plans/procedures with guaranteed Service Level Agreements.

Licensing cost for M&EIT System users should be provided as follows:

• 350 - 500 MRO / M&E users

• 501 - 750MRO / M&E users

• 751 - 1000MRO / M&E users Unit cost for each MRO / M&E user

• If enterprise licensing option is available, please specify

• Optionally tail based / revenue based licensing model

In case of concurrent users License may be reduce accordingly.

Contractor must also specify an “Escrow” arrangement for the availability of source

code necessary to support the proposed solution in case the Contractor or the

principal vendors cease to exist, discontinue this line of business or are

incapacitated in any way to support the proposed solution.

2.4 Database Management System (DBMS)

Complete details of the DBMS are to be provided, including features and

capabilities, adherence to industry standards, portability and openness, with

reference.

Features and capabilities of the Database Administration Tools that are proposed

should be provided.

2.5 Query and Report Generator Tools

Complete description of the tools that are being provided with MRO / M&E Package

standard functionality for End-User ad-hoc query and report generation, including

capabilities for ease-of-use and learning.

2.6 Implementation Strategy

The Bidder should provide details of the implementation strategy to be adopted, and

include a component-wise high-level plan. Details should be provided of the project

Page 69 of 189


organization that will be maintained. The Project progress reporting mechanism is to

be highlighted. Details of how the resources identified will be utilized during the

various phases of the Project should be described. The quality assurance process to

be followed for products and services, as well as responsibilities, should be

described. Implementation tasks requirements are detailed in Sub Section D1.

Detailed time schedule shall be provided highlighting main milestones and activities

in detail with overall time span. Bidders must clearly specify the facilities required by

their consultants during implementation.

2.7 Interim Server(s)

A complete description of the hardware configuration and performance expectations

of the proposed Interim Server should be provided. The Contractor should also

describe the contingency arrangements that will be in effect for the period that the

Interim Server(s) is required, as well as maintenance responsibilities. The Site

Specifications for installation of the Server(s) must be provided to enable PIA to cater

for the requirements.

2.8 Training to Users and Management

Details of Training to be conducted by the successful Bidder should be provided,

with description of type, content, duration and location of courses for each of the

identified personnel levels, with reference to Sub Section D - Services

Requirements. Also describe the training material to be provided on completion of

the course as well as certification/examination method to be followed. Following

table indicates the approximate number of users that would require training

2.9 Data Migration

All details of data conversion strategy and process have to be defined, in accordance with details outlined in Section D, sub-section-D3.Acquiring of any third-party industry solution by the contractor for data migration should be described, and

USER GROUPS EXPECTED ROLES NUMBER

Senior Management (DCE and above)

➢ Report / MIS review

➢ Transaction review and approval

➢ Limited transaction entry / edit

80

Power / Key Users (IT, Others) ➢ System parameterization and configuration Master trainers

50

End Users ➢ Transaction entry / edit

➢ Transaction approvals

➢ Report / MIS / Document viewer

800

Technical Users (IT Department) ➢ Technical Support 25

Page 70 of 189


licensing cost of such solution should be part of ‘Migration’ cost as specified in Section-B4, Form Services Price Schedule (Prior to Maintenance). PIA may decide at its own discretion, not to migrate the legacy data at all, or limit the functions/time-frame, and shall declare it in writing as part of contract.

2.10 3rd Party Software Interfaces

Contractor will be responsible to ensure that required 3rd party software, operating

systems, system management and monitoring tools, backup and recovery software,

database administration tools, disaster recovery and business continuity tools, APIs /

interfaces, etc. are all made available, documented, designed, implemented and

operational to meet PIA’s requirements in the proposed MRO / M&E solution. These

should be clearly spelt out in the Technical Proposal and corresponding pricing

shown in the Price Proposal.

2.11 Documentation

Details of documentation have to be provided for MRO / M&E and other

Applications. It should describe a summary of contents, media on which provided,

and the number of hard and soft copies. The Bidder should address the needs of

End user as well as technical (operations, support and development).

2.12 Post-Implementation Warranty / Support

Details of post-implementation support during and after warranty period that will be

provided after the expiry of the warranty should be provided for each required

component with reference to Section D - Services Requirements. The type of

support, coverage, location from which support will be provided, should be

described, as well as the level of expertise that will be employed for support. Also

describe the escalation process that is to be followed, and the service levels. A

description of the handling of various categories of problems and response times

should be provided along with the cost.

2.13 Technology Architecture

Details of the proposed technology architecture under which the MRO / M&E

solution will be implemented should be provided, consistent with modern n-tiered

client/server and distributed computing design and details provided in Section C –

Product Requirements (MRO / M&E Package and Add-Ons).

2.14 Recommendations for Hardware Configuration and System Management Tools

The Bidder should provide its recommendations for the platform configuration for

server hardware to run the MRO / M&E Package and other applications. The

proposed MRO / M&E Package and DBMS shall be platform independent so that

shall give PIAC liberty for choosing any appropriate platform in the future.

Page 71 of 189


Bidder has to propose complete hardware solution and minimum network

infrastructure.

PIAC reserves the right to purchase hardware/operating software from the

successful Bidder or any other vendor of its choice.

2.15 Add-on Applications

Where the suite of MRO / M&E modules does not meet all the functional

requirements of PIA, and the Contractor proposes to custom-build application(s) as

Add-ons to the MR&E IT to fulfill the requirements, details of the application

development methodology, development platform and tools, and extent of

development complexity are to be provided. Their capability to integrate seamlessly

with the core MRO / M&E Solution and other proposed external software utilities

and modules should be described, with an overview of integration and data transfer

mechanisms. The ownership rights of the Add-on applications will rest with PIA,

including all Intellectual Property Rights. The Contractor‘s (or Consortium Partner‘s)

experience of developing and implementing such Custom-Built applications must be

highlighted.

2.16 Requirements from PIA: The Contractor must specify in detail the facilities to be

provided by PIA for effective implementation. The Technical Proposal must

clearly mention the responsibilities of PIA and the Contractor during different phases

of the project.

2.17 Comments / Suggestions (Optional): The Contractor should provide any comments

or suggestions on the Terms of Reference

2.18 List of all deliverables during the projects.

Page 72 of 189


SECTION C

PRODUCT DETAIL (MRO / M&E PACKAGE & ADD-ONS)

Page 73 of 189


C1 OBJECTIVES

This section describes the functional requirements that the MRO / M&E

Solution is required to meet.

Requirement are sub-divided into two sub-sections C2 & C3.

Sub-section C2 covers all the functional areas of PIA Engineering & Maintenance

department, while functionality requirements are based upon as-is processes /

workflows / practices or activates, which are currently handled through various

mean; i.e.;

▪ PAMMIS (PIA Aircraft Maintenance Management Information System);

or

▪ by way of using Microsoft Access/Excel; or

▪ by using home-grown applications; or

▪ by using all paper-based documentations & records, manually tracked

functions, with little or no system support.

Sub-Section C3 describes general requirements of MRO/M&E Solution mainly

addressing add-ons, data/information formats, trending technologies & other

product enhancing features.

PIA intends to introduce the best of the breed IT functionality modules into its

Maintenance & Engineering, therefore it is required that wherever applicable, the

“best industry practices, processes & templates” to be introduced / suggested to

meet or exceed the functional requirements outlined in following sub-sections

(C2 & C3).

Page 74 of 189


C2 FUNCTIONAL REQUIREMENTS

1.0 Required Engineering Functionality

1.1 MPD Management

▪ Import / upload of Maintenance Planning Document (MPD) as delivered by the

aircraft OEM in digital format, both initial issue and subsequent revisions.

▪ For non-customized MPD delivery, a filter according the PIAC effectivity shall

generate customized MPD variant/version.

▪ Capability to generate the difference report between two consecutive revisions of the

MPD for the purpose of PCAA approval.

▪ Customization of the MPD as per peculiar PIAC requirements.

▪ Notification to the key users upon upload of new/revised or customized MPD.

▪ Define MEL and update according to fleet configuration.

1.2 Reliability Management

▪ Reliability and Performance analysis of A/C System, Engine & Components, on the

basis of the defects & rectification data arising of unscheduled maintenance, on

aircraft, engine and components.

▪ The No Fault Found (NFF) analysis / reporting aircraft system/chapter-wise

▪ MTBUR analysis of the aircraft components. The system should suggest MPD

adjustment accordingly.

▪ Engine, APU trend / performance monitoring, through engine condition monitoring&

oil consumption.

▪ Support for CofM & CofA renewal process.

▪ Monitor aircraft configuration for ETOPS, RVSM compliance

▪ Flight incidents & Pilot Reports data classification upon entry into the system

▪ The aircraft/ fleet utilization to be stored into the system through an interface.

1.3 Document Management

▪ An automated upload/update of OEM Manuals with

The system shall ensure an airworthy update and revision management of all OEM documents used for aircraft maintenance and engineering. But also, airframe structure drawing to be up-loaded via internet access.

▪ Upload and register SB’s

All Service Bulletins (SB’s) and Airworthiness Directives (AD’s) to be registered in

the system

▪ Revise aircraft & aircraft component manuals

The revision management process shall ensure, the revisions are applied at the

central library but also, that all revised documents receive all end user.

Page 75 of 189


▪ Technical Library Function

All aircraft & aircraft components manuals should be made available in a catalogued

manner in the library. The library should be connected to the OEMs sites at back

end for continued up-t-date manual contents of the manuals. User sections should

have access to the updated OEM manuals/documents as per their work center

requirements, defined in the user section capability list. There should be a

notification to the end user whenever a revised manual is updated. Technical

documents to be made available on desktop PC as well as android, apple devices.

▪ Maintain Internal PIAC Manuals.

PIAC own manuals to be maintained, approved and revised. The system shall

support this process.

1.4 Task Card Management

▪ Upload OEM Task Cards (TC)

PIAC is widely using the Task Cards provided by the OEM. A functionality to be provided to upload and revise master Task Cards. The system shall have functionality to store and manage those document types for further use.

▪ Create/Update/ modify TC

Beside pre-defined TC’s there must be a functionality to write, maintain and revise PIAC own TC’s. For structural damages and major repairs, creation and approval of TC to be supported.

▪ Inclusion of relevant procedures from AMM

Task cards should be enhanced with more detailed instructions, text and graphical elements of the embedding relevant content from OEM manuals with reference. Any change in the OEM manual should automatically update the task card to that extent, with revised manual reference.

▪ Release Master TC for service.

Once the master TC is finally edited and/ or revised. This TC to be get approval by a

second authority. This could be supported by a workflow solution. When the approval

is granted, the TC to be released for using in the production, replacing the old

version. When the master TC is released for production, The TC content is reduced

to the concerned tail sign, the order number is added to the TC and the TC attached

to a WP. The TC if required on colored paper with bar code, tail sign text and

graphic. Also, the required material to be on the TC and will create the BoM by

turning the master TC into production.

1.5 Modification Process

❖ Evaluate & approve AD, SB, SIL Evaluation of Airworthiness Directives from regulatory bodies like FAA, EASA & OEM Service Bulletins, Service Information Letters & similar literature for applicability to PIA fleet or installed components.

Page 76 of 189


❖ Create Engineering Order The AD/SB, if evaluated applicable to PIA fleet/components to be converted to a change order with specific actions defined along with material and Mh consumption required. Reference to the relevant maintenance data / instruction to be provided for implementation.

❖ Status Fleet Modification Such modification if implemented on aircraft, the aircraft technical record as well as master configuration record to be updated as applicable.

❖ Status Engine/ Component Modification The modification performed on Engine / aircraft components shall translate into appropriate modification status of Engine / aircraft component, with interchangeability (one-way, two-way) appropriately inserted into fleet master configuration data.

❖ Planning & staggering Fleet Modifications Optimized modification plan to be suggested keeping into view the target time (for time barred modifications), available maintenance slots, QPA, spare float, and modification kit availability/lead times. A close loop monitoring through charts to be provided.

❖ List of performed SB’s

Modification status report of the aircraft, engine or components, with modifications performed in a particular time period should be supported.

❖ Configuration control.

Configuration control of the aircraft or engine to be ensured, with part number/serial

number applicability of sub component / assemblies to be validated upon installation

on aircraft or engines. All applicable ADs & mandatory SBs pending for

incorporation, to be highlighted in terms of open change orders for fleet/tail, Engine

or components with appropriate in time alerts mechanism (email, dashboard etc.) to

key stake holders, specifically the engineering and quality assurance divisions.

Page 77 of 189


2.0 Required functionality for Aircraft Phase-in/-Out

The functionality is more importantly required whenever an aircraft is inducted in PIA

through purchase or lease and later phased-out through sale or lease-return.

Technical record is especially important for speedy lease return.

2.1 Aircraft master data

▪ Create aircraft/ engine master data when a new aircraft to be introduced, the Aircraft/ Engine master data to be created.

▪ Create aircraft/ engine master structure & locations

When a new aircraft type to be introduced in the fleet a new structure of this aircraft or variant to be defined. Based on this fleet structure, the aircraft/ engine master structure and location to be defined. The technical locations shall consist of ATA chapters and Zonal information in a hierarchical structure in assays and sub assay.

2.2 Initial data entry

▪ Initial provisioning, upload Recommended Spare Parts List (RSPL)

For the induction of a new aircraft type the recommended spare parts list to be uploaded. An editing functionality shall allow producing versions of this RSPL file. Based on the final agreed parts list, the procurement process to be initiated.

▪ Upload and maintain readiness log

Also, the readiness log to be uploaded to complete the as is configuration.

▪ Upload A/C, engine, component history

The aircraft, engine and component history to be updated.

▪ Upload MPD, MEL

In case of a new aircraft type, the respective MPD and the Minimum Equipment List

(MEL) to be updated and customized according to the PIAC needs.

▪ Upload Tech-Log, MEL status, Open defects

The actual aircraft status concerning technical logbook, MEL related items and

deferred defects to be uploaded into the system.

▪ Upload modification status

The modification status to be uploaded.

▪ Maintain status/ letter checks performed

The due date and the history of the letter checks performed to be updated.

▪ Enter flown flight hours, block hours, landings cycles, days.

The flown flight hours, clock hours, cycles and days to be updated for the aircraft,

engine and leach Line Replaceable Unit (LRU).

Page 78 of 189


2.3 Aircraft phase out

▪ Create Readiness Log

By phasing out an aircraft, a readiness log to be provided. But also, concerned stock

to be reviewed for surplus.

▪ Create Mod Status

A report to be created of the entire aircraft/ engine modification status

▪ Create Maintenance Status

A report to be created of the current maintenance status and the entire maintenance

history.

▪ Create Tech-Log, MEL status, Deferred Defects

A report to be created concerning the actual open items, such as Technical Logbook

entries, MEL related items and deferred defects.

2.4 Engine Change

▪ Remove & extract complete data set

By engine removal, all engine related data to be removed from the aircraft data set. In case of foreign repair, a report to be created and transferred to the vendor, with all concerned engine information.

▪ Upload complete data set

Engine overhaul, repair and modifications concerned data to be uploaded to the system. At engine installation, all concerned data to be linked with the concerned aircraft.

Page 79 of 189


3.0 Required Functionality for Line Maintenance

3.1 Line Maintenance Planning

▪ Long/ medium-term planning (summer/winter/hajj)

Based on the PIAC flight schedule and the PIAC maintenance program (Preamble)

in the long term planning a first schedule of the letter checks (A Check and below)

are done. Together with the expected non-routine work, the needed component

changes and the modifications, to ground time and the needed man hours are

defined.

In the medium term planning each ground time will be adjusted, the bill of work will be finalized and the bill of material defined. The total load will be mapped against the available capacity.

▪ Short-term planning

The deferred defects will be translated to a Bill of Work (BoW). All needed manpower, tools, spares and documents are prepared and assigned to the planned job.

▪ Work load/ capacity planning

The expected workload will be balanced against the available capacity. Further actions to be arranged such as additional capacity or postpone of work packages. Also, flexible shift pattern to be arranged by the system.

▪ Hangar/ A/C visit plan

As a result of the long/ medium term planning, the hangar visit plan is defined. It

represents the needed hangar slots of all PIAC & client letter checks.

▪ Assign Work Package to Work Center/ Shift/ individual staff

The defined work packages to be assigned to a particular work center and shift. In case some work packages cold not completed in a shift, it will be rescheduled by production planning and again assigned to a work center and shift. The major criteria are a priority/ alert list showing the latest due date of a job and also the aircraft availability.

▪ Flight Coverage Planning

▪ For flights, where a Ground Engineer to be attended, the flight coverage planning shall be possible. An optimal flight coverage roster shall be possible for all flights scheduled in a calendar month, taking care of aircraft scheduled, and fly-to station capability.

▪ Dispatch spares, tools, documentation to line station The spares, defined at the Bill of Material (BoM) is already blocked by a

reservation functionality. Also, the needed tools. When Production planning assigns a work package to a work center/ shift, the due date and the location is defined. Production Planning (PP) will also create a transportation order for providing the needed spares and tools at the needed location. When the work packages are performed a dispatch, order will return the tools to the tolls store and location, the replaced components to be dispatched to the salvage store.

▪ Provision of line stations

The provision of line stations with staff, tools, document and spare kit to be planned

and renewed.

Page 80 of 189


3.2 Scheduled Maintenance

▪ Bill of Work (BoW)

The BoW is a list of work packages (WP) to be performed in Line and Base maintenance. Each WP consist of a number of job cards (JC). Each WP has a unique identification number.

▪ Bill of Material (BoM)

The BoM defines the needed routine material (Rotables and consumables) for performing the WP. This list is a master file attached with the BoW master file. Needed routine material can be part of the master JC and the BoM to be extracted of it. Same with the needed tools and equipment.

▪ Needed Tools and Equipment

The needed tools and equipment, such as remedies, stairs, GSE to be planned by PP and dispatched to the WC. The list of required tools and equipment is part of the WP.

▪ Execute Work Package and Task Cards

Planned TC and WP to be performed are stored in the system as master documents. They consist of all needed field such as a unique ID, A/C type and effectivity, ATA chapter and Zone the needed Mh and qualification. When WP and TC are transformed from planning stage and turned into operation, the tail sign, the due date and a unique order number is added. A bare code is printed at the JC representing the order number. A cover sheet representing the WP and showing all JC within the WP.

▪ Schedule Major component change (MIC)

PP will create out of a forecast of hard times and regular inspections. Out of this list, the needed tasks for the coming shift are to be defined. The needed JC are selected and will be part of the WP.

▪ Release A/C to service

After performing the planned maintenance services, the A/C will be release to service. This is noted in the system. Any limitations such as remaining life due to MEL items is also noted and are the base for planning new maintenance activities.

▪ Shift hand over

The shift hand over to be supported by providing a list of open items.

3.3 Unscheduled Maintenance

▪ Record defects and corrective action.

The defect description and a number of describing filed including tail sign, ATA chapter and location, to be entered. The functionality shall also indicate repetitive defects. When the repair strategy is already defined during the investigation, it is noted in the corrective action field but also as a deferred defect. When the corrective action is completed, the open case will be closed. The defect notification to be used for further fleet analysis and for the fleet Reliability Report.

▪ Trace deferred defects

Tracing functionality shall locate deferred defects for further actions. An open defect

notification will also create a Maintenance Repair Order.

▪ Indicate MEL items

The system shall display the MEL list. An attribute shall declare the deferred defect as a MEL item and define the remaining life, if appropriate. In case of MEL item for each fight a report to be produced for pilot briefing. The MEL item to be traced on the alert list for high priority maintenance actions.

Page 81 of 189


3.4 Post Maintenance Process

▪ Update A/C, component records

➢ When and component change is performed, the respective S/N will be posted in the System. The replaced S/N (U/S part) will keep the accumulated counters. The new serviceable unit located in the A/C will accumulate counters to its remaining life. With the component change, the A/C will get an update of the as is configuration.

➢ In case of a modification (performing AD or SB) the new mod status of this A/C is noted. Subsequent changes in the system concerning MPD and TC are initiated. Also, the mod campaign will get notice of accomplishment of this A/C.

By accomplishing the WP, the related A/C counters are set to zero. When the A/C

starts again operation, all A/C counters and the subsequent Engine/ APU/ Component

counters will continue to collect the operational counts. The rescheduling of the next

maintenance activities will start.

▪ Report performed tasks

The performed WP’s are reported as complete, when the WP cover page is clocked-out by bar code scanning. The WP will be deleted from the WP backlog and transferred to the performed tasks. All dirty finger prints are archived by using the WP ID as the leading discriminator.

▪ Archive task cards

After performing the TC, the documents are archived for legal purposes for a

minimum of two year or for tracing A/C, Component history back-to-birth.

Page 82 of 189


4.0 Required Functionality for Cabin Maintenance

4.1 Maintenance Planning

▪ Define/ update a maintenance program for CM &A/C cleaning. A regular schedule to be defined for cabin maintenance items and aircraft exterior, interior & deep cleaning.

▪ Define Instruction cards for CM

Instruction card to be defined for cabin maintenance.

▪ Plan CM according the maintenance program

According to the defined maintenance program, the CM work packages are planned

and scheduled.

▪ Plan capacity according to work load

According to the maintenance schedule, the capacity to be assigned.

4.2 Customer Feedback

▪ Interface to customer complaint system

An interface to be created between the system and the PIAC customer feedback

system. All Cabin related items to be transferred.

▪ Corrective action feedback

The corrective actions to be recorded and reported back to the customer feedback

system.

▪ Statistics according customer feedback

Statistics are generated concerning customer feedback and cabin maintenance

activities.


▪ Record defects from CBL or inspection and report corrective action; see also Line

Maintenance (LM) defect management

▪ Trace deferred defects same as LM

▪ Indicate MEL items Same as LM

Page 83 of 189


5.0 Required Functionality for Base Maintenance

5.1 Base Maintenance Planning

▪ Long/ medium-term check planning Base Maintenance Events

In the long term planning a forecast is given by the system for letter check due date and ground time based on standards parameter. This forecast in used for ground time staggering, budget planning and hangar capacity planning. In the medium planning the bill of work to be defined, the bill of material, together with planning adjustments, load and capacity planning. The routine and non-routine work packages are defined. The required tools are defined.

▪ Work Package Management

The standards Work Packages consist of several Job Cards are compiled and edited according to production planning and work optimization criteria. JC to be linked to WP’s and WP to be liked to a project plan.

▪ Hangar/ A/C visit plan; refer Line Maintenance para (3.1)

▪ Work Load Planning see Line Maintenance (3.1)

▪ Job Card creation/ update/ revise see Aircraft Engineering

▪ Event project planning with flow charts and mile stones

The project plan shall be a graphical representation of WP’ along a time line. By meeting the external time criteria, the Production Planner shall have the possibility shifting the WP’s along the time line to match with the available capacity. Also, an automated planning using capacity and load planning shall be possible.

▪ Forward/ Backward event planning (incl. Gantt-Chart).

Various planning scenarios to be possible such as forwards planning by using a

fixed start date and backward planning by using a fixed end date.

▪ Progress monitoring, monitor costs

By using shop floor data collection and the JC completion note, the work progress to be monitored. With the shop floor data collection, the consumed man hours to be collected. Also, consumed parted and exchanged LRU’s to be posted to the Work Order.

▪ Monitor consumed Man hour (Mh) & spares

The consumed spared and respective costs, the repair abroad costs and the

consumed man hour to be monitored on daily basis to control the costs.

5.2 Base Maintenance Operation

▪ Interface deferred defects from LM

The deferred defects to be transferred to the base maintenance event at the time of

aircraft roll in. The deferred defect to be transferred into a Repair Order.

▪ Shop floor data collection.

All Job Cards to be submitted will be assigned to an Order Number. By using a bare code beginning and end of the work to be done is registered. Also, when a component change is due, the in and out Serial Number (S/N) to be notified and subsequent processes to be triggered. But also queries at the Material Master and available stock to be done.

▪ Entering snags, planning rectification.

When visual inspections and system checks are required by the WP, upcoming discrepancies to be notified. Attributes to be added concerning the location, the nature of defect and the causing document (e.g. CPCP). A repair order to be generated with some production planning attributes such as expected man hours,

Page 84 of 189


needed spares and tools. The closure of the defect notification to be recognized by the system. Some observations to be notified and transferred to Engineering work place, such as CPCP.

▪ Shift hand over

A functionality to support shift handover in case the open WP or JC could not

completed within the current shift.

▪ Capacity Planning

Functionality offered to balance workload and available capacity.

▪ Close loop repair

Parts replaced for A/C and returned from shops after repair to be traced and

planned in a close loop parts management.


▪ Transfer defect to LM

When the aircraft roll out after the base maintenance is due, the open items are to

be transferred to line maintenance and kept as Repair Orders.

▪ Update A/C configuration & counters

Modifications, and component changes reflects changes in the aircraft configuration. Configuration update shall be most preferable done automatically by posting a component change. Manual update to be provided as well.

▪ Archive documents

All major activities are recorded as database transactions. But also, the used and stamped documents (dirty finger prints) to be archived according to the legal requirements. A logic link with the respective data base entry leads to a powerful knowledge base.

▪ Post check analysis

Analysis functions to be provided to allow reviewing and analyze performed checks. Also, the recorded Mh to be available for updating the standard Mh per TC.

Page 85 of 189


6.0 Required Functionality for Component Overhaul Shops


a) Medium-term capacity planning/ Shop visit forecast

Based on the shop visit history, and also on removal forecast for scheduled and unscheduled removals, the shop workload to be predicted. The Shop budget and needed capacity to be defined from this data. The system should support annual man-hour plan revised in real time at quarterly intervals.

b) Work Priority Management

Based upon component backlog, aircraft demand, stock level, scheduled component

expected arising & available manpower, system shall suggest a priority maintenance

list.

c) Capacity/ workload planning

Based on the work orders in the shop the workload and capacity planning to be

performed with standards parameters.

d) Monitor costs, monitor consumed Mh & spares.

Dynamic view of man hours & material consumption during the course of a

component maintenance and a report of Mh. & material consumed and cost of

production.

e) LRU repair status

Notwithstanding there is an in-house repair or a repair abroad request was generated, the actual repair status and a forecast concerning the serviceability is given by the system.

f) Planning for consumables.

System should support planning for consumables required during scheduled &

unscheduled maintenance, based upon HTCL, consumption history, average TAT, etc.

g) LRU Status / Location review

At any time, the current status and location of an LRU all serial numbers, a single serial number with installation/removal location and work-order history, its fleet applicability, alternate part numbers, shall be reportable by the system. Component hold up for consumables to carry status of consumables’ procurement phase.

6.2 Component Maintenance Workflow

➢ Work order / Input registration

➢ Work package / Bill of work compilation.

➢ Job issuance at shop production floor.

➢ Maintenance execution

➢ Defect notification & repair procedure.

➢ Work package data entry into system.

➢ Post consumables to repair order.

➢ Component release tag printing / sign-off.

➢ Shop-out / closure of work-order.

➢ Update LRU status & counters.

Page 86 of 189


6.3 Shop Support functions a) Process Flow for Contracted Maintenance / Repair Abroad

Contracted maintenance repair orders process flow with;

▪ Visibility of status of serial number/part numbers under such

maintenance.

▪ Processing/evaluation/approval of contracted maintenance repair

estimates/invoices/warranties as part of Repair Abroad work flow.

b) Scrap Process The scrap process to be supported by the system. The LRU to be deleted from the

system, re-order request to Rotables section & notification to ERP for assets

valuation adjustment.

c) Components requiring consumable During components’ maintenance, consumables are required such as spares, sub-

assemblies and other material.

▪ System should support request generation for consumables to stock rooms. I

▪ If the consumables are NIL in stock, then relevant purchase requisition should be

possible.

▪ The shop manager should be able to analyze the procurement & usage history and

make adjustments to quantity required.

▪ Reporting capability for all such components holdup during consumables’

procurement phase. Filters to be used for critical / AOG components as per demand /

priority.

d) Third Party Customer Component Maintenance

▪ Third party work order Loading at shop floor

▪ Customer approval for cost estimates.

▪ Closure of customer work-order and intimation to Business division.

▪ Handing over of customer components to the originator.

e) Shop Capability Management& Control

Component Capability List (CCL) management ensuring all required pre-

requisites;

▪ Shop Test-Equipment/Tools, alternate Test-Equipment/Tools approval &

registration.

▪ Ensure availability of all applicable material / tools as per CCL.

▪ Ensure Tool/Test Equipment has valid calibration/service life during use.

▪ Work order generation for shop to be restricted for non-CCL components.

▪ Ensure up-to-date maintenance data / OEM manuals for work-orders under

maintenance.

▪ Updated certifying staff list with all pre-requisite courses/training validity

check.

f) Fractional Work Order Process

Page 87 of 189


Inter-shop fractional work to be facilitated, where main work order is being

processed in allocated shop while for fractional work components is temporarily

moved to other shop, and returned upon job completion.

g) Tool store functions

▪ Shop tools management including calibration control

▪ Consumable Material/Chemicals storage in specified quantity with shelf life

control

▪ Tools, equipment Repair/Calibration processing (in-house / abroad)

▪ Issuance of tools on permanent and temporary basis and ensure their timely calibration.

▪ Issuance of consumable material with reference of work order. ▪ Keep an up-to-date inventory of all variety tools/equipment used in respective

shops

6.4 Component Engineering a) Up-to-date OEM Component Maintenance Manuals & documents

System should support that all maintenance manuals are updated and as per

latest revision.

b) SBs, ADs Component modification process

Workflow for component modification process to be supported by the system.

• Evaluation of modification

• Planning for modification, with generation of staggered plan for all applicable LRUs.

• The Mod kits to be ordered / planned.

• Removal request generation from aircraft / stock room for shop as per plan.

• Modification Sheet generation as part of work package.

• After modification, the interchangeability to be updated. Also, the aircraft master parts list/configuration to be updated.

c) Archive Technical Records

All maintenance records to be archived, for audit requirements.

a) Defect notification.

LRU defects to be described in a defect notification. The data are used for the component reliability report and as knowledge base for future maintenance.

d) Component reliability report.

Thee component reliability to be monitored based upon component removals, shop

findings and NFF. The same to be reported / projected as and when required filtered

for a date interval, ATA chapter, shop group, or a single component.

e) System should support the work instruction card to be created, updated and

revised.

f) Alternate Tools / Material Approval

System should maintain record of approved alternate tools / material with a cross-

reference list.

Page 88 of 189


6.5 Work flow for Repair &Modification shop Repair and modification of Mechanical components of airframe, engine, APU, L/G involves multi stage work package. System should support work flow involving following machine shop stages;

• Machining / grinding

• Welding, brazing

• Heat treatment

• Precision measuring

• Metallographic inspection / Hardness testing

• Surface treatment

• Bench fitting

• Plating / plasma / paint.

6.6 Workshop Equipment Maintenance

a) Fixed equipment Maintenance Shop

• Maintenance all the fixed installation of Power Plant, L/G & components overhaul shops’ mechanical machines, Test Rigs, workshop equipment, O/H cranes, compressors, cylinder chargers and other rotary equipment.

• Keep record of complete inventory of the workshop equipment and maintain the maintenance history for each type of equipment in the database.

b) Tool / Test Equipment Local Fabrication ❖ Fabricate/ repair various kinds of special tools/ fixture/equipment as suggested

by manufacturer through drawings manuals and samples. ❖ Approval by Technical Services Engineering and issuance of the compliance

certificate and recording into the system

Page 89 of 189


7.0 Required Functionality Concerning Quality Assurance

7.1 Quality Assurance (Audit) ▪ Define Yearly Audit Plan and define audit program/assigning teams for individual

audits. ▪ Preparing checklist for the specific area of audit, recording of Non-Compliances,

after execution of audit, for different levels (Level I, II, III) and time limit for corrective action. Follow up of NCRs till such time corrective actions are accepted and verified.

▪ Defining and conducting audits of Line Stations and Technical Handling Agents. Recording of Non-Compliances and their corrective actions.

▪ Audit Reports including Compliances and Non-Compliances for all audits (Base Station/Line Stations/Technical Handling Agents)

▪ Conducting and follow up of un-scheduled Audits whenever asked by Management / Regulatory Authority.

▪ Evaluation of potential Vendors and recommendation. Record of all vendors approved by Chief Engineer (QA).

▪ Assessment of CCL cases submitted for approval of Chief Engineer (QA). ▪ Assessment of Certifying Staff posted at Base and at different Line Stations and

record of Company Authorizations issued with expiry monitoring.

7.2 Quality Assurance (Maintenance) ▪ Selecting flights for different destinations and scheduling / assigning teams for ramp

inspections. Recording of Findings / Observations for different categories (1, 2, 3), corrective actions submitted by the concerned section and follow up till such time the findings are closed.

▪ Scheduling / assigning teams for spot checks of different areas of Engineering & Maintenance. Recording of Findings/Observations, corrective actions and follow up till such time findings are closed.

▪ Unscheduled Ramp Inspections and Spot Checks when ever asked by Management or Regulatory Authority.

7.3 Human Factor / SMS ▪ Reporting of SMS/HSE/Human factor related issues. ▪ Analysis, Risk assessment and their mitigation actions follow up of reported issues. ▪ Risk assessment of findings raised during internal audit.

7.4 Examination ▪ Record of submitted applications for PCAA licenses and Company Approvals.

Scrutiny and status of submitted applications. ▪ Conducting of Company Approval Exams by extracting questions from Question

Data Bank (QDB) and issue approval certificate to successful candidates. ▪ Record of Technical Qualifications (Licenses and Company Approvals) of PIA

Engineering & Maintenance Personnel.

7.5 Chief Engineer Secretariat ▪ Approval of vendors and their Quality Monitoring. Blacklisting or removal from list of

approved vendors as a result of quality monitoring. ▪ Record of Concessions / Limited Authorization issued by PCAA and issuing LA

termination report after concession / limited authorization expiry. ▪ Liaison with different sections of PIA and Regulatory Authority regarding incidents /

delays and their investigations. ▪ Liaison with PCAA for renewal of Licenses. (Application Acceptance / Scrutiny /

Submission to PCAA & Follow up)

Page 90 of 189


8.0 Maintenance Operations Support Center Procurement and logistics functions of PIA Engineering are performed on Oracle ERP. There should be 2-way interface / data-exchange capability necessary for functions defined here under.

8.1 Material Planning& Management

▪ Upload Readiness Log

As a major source for the aircraft configuration the Readiness Log to be uploaded. The functionality supports a comfortable automated upload / semiautomatic upload of data notwithstanding is the first A/C of a fleet or a subsequent one.

▪ Upload and maintain initial provisioning data

The initial provisioning to be supported by uploading the RSPL file notwithstanding it is the first A/C of a fleet or a subsequent one. A comfortable editing functionality shall support material planner by modifying the recommended and to actual Part Number (P/N) and quantity.

▪ Maintain Aircraft structure/ location

The aircraft master structure and location to be defined. This to be done by

uploading the readiness Log, and/ or by editing the master structure.

▪ Maintain Material Master Data

The material master parts list to be uploaded and edited. Also, the interchangeability

and the PIAC internal master P/N to be defined.

▪ Plan consumable based on planning parameters & past consumption

Beside the initial provisioning the subsequent material consumption of consumables and repairable to be planned. Functionality shall support this process by providing statistical data concerning past consumptions, calculations based on planning parameters but also an event forecast and the respective routine materials. Calculations concerning the reliability of on condition components and failure rates to be provided.

▪ Material provision for planned maintenance.

Based on the PIAC fleet maintenance forecast for letter checks, material planner shall get all needed information for planning provision of planned and unplanned material. Also, the derived from the standard BoM for letter checks budgeting information to be derived for financial planning for future checks.

▪ Monitor consumption and stock level

Material planner also need information on stock consumption in a given time frame. Based on this and on procurement parameters the reorder level to be optimized and populated to the inventory system maintaining in ERP.

▪ Material request.

Consumables and demanded to requested by the users to be requested by the system. The request shall have several levels of urgencies and the expected delivery date. When a material request s handled automatically the service level and the material budget to be updated.

Page 91 of 189


8.2 Rotables Control (LRU)

▪ Plan LRU float

The LRU float to be optimized, based on the net requirements for the fleet, the needed Turn Around Time (TAT) for overhaul and the logistic times. The needed information such as MTBUR to be provided for the float calculation.

Control lifetime

The system shall monitor the life time of LRU’s and Life Limited Parts (LLP’s) no matter if it is a hard time item or to be monitored on condition. If an assay is replaced from the aircraft, all subsequent sub-assay’s to be also removed automatically.

▪ Component history

The complete component history to be tracked and traceable in the system.

Working papers to be attached to this information in an electronic format.

▪ Component tracking

The actual location to be traced in the system whether it installed in the aircraft,

dispatched, at store or in a repair cycle.

▪ Shelf life / Environmental Conditions for storage

Some component may have a shelf life. Those components to be monitored. A report

will inform about reaching the end of a shelf life. Environmental conditions for storage

to be part of component master data.

8.3 Loan/ Borrowing

▪ Administrate loan of parts/ equipment / tools

When PIAC loan parts/ equipment and tools to other airlines, the loan and the return of

the goods to be monitored by the system.

▪ Administrate borrowing of parts/ equipment / tools

Also, when PIAC will borrow parts/ equipment / tools from other airlines. The borrowing and return of the goods to be monitored. The system shall also display LRU’s installed in the aircraft on loan basis.

▪ Support component pooling concept

In case of a component pooling concept. The system shall support exchange parts

based on a pooling contract.

8.4 Component exchange program

Support for component exchange program / Component support program. ❖ Contracts management for CEP/CSP. ❖ Work flow for entire CSP loop, starting from;

• components’ removal from aircraft,

• request generation to CSP vendor for provision of replacement part,

• dispatch of removed component to the CSP vendor,

• tracking of replacement part till arrival in PIA stock

• tracking of removed part till it reaches designated location, with early alerts to avoid late penalty.

❖ Component out/in history

In case part to be handled on an exchange program, the component history shall go with the component to the supplier. The exchanged part to be returned shall come with its documentation. The information deleted from the system and transferred to the supplier and received from the supplier and uploaded to the system in an electronic format.

Page 92 of 189


❖ Keeping track of NFF and generate appropriate alerts if the numbers tend to exceed the allowed limit.

❖ Reporting capability for components send to CSP in a given time frame with all serial numbers removal data (defect, aircraft, etc.

8.5 Contracted Maintenance

Aircraft Components are sent for repair to contracted repair stations outside PIA, where there is no in-house capability exist, or there doesn’t exist any parts exchange (CSP) or pooling arrangement. Support for such contracted maintenance should exist in the system thru an interface with ERP. System should generate a work order to track and coordinate such maintenance. ▪ The status of the component, expected return into the stock / system based

estimated through defined TAT keeping in view of the standard process parameters.

▪ Repair reports integration to the component history record upon return.

▪ Provision to update the respective system parameters & work order closure when a

component is scrap is approved on repair agency site or an offer for serial number

exchanged is approved from management.

▪ System shall maintain Permanent repair abroad list (PRA) for components sent on

contracted maintenance on routine basis, with all contract parameters defined such as

repair cost (power by the hour, flat rate, etc.), repair facility address, certification

warranty etc.

8.6 Warranty management

System should support Warranty management. Generally following broad

categories of warranty events occur in PIA.

i. Repair Warranty

▪ Components returned from contracted maintenance in stock room with valid

warranty should be offered on priority for aircraft demand.

▪ If a component is removed from aircraft and is still under warranty, the

relevant sections to be immediately notified for speedy process of return

dispatch to the repair agency.

▪ Last repair report should be readily available to correlate last repair area/parts

with current defect.

ii. Purchase Warranty

▪ Purchased Component with valid warranty should be issued on priority.

▪ If the component is removed from aircraft and is still under purchase

warranty, the relevant sections to be immediately notified for speedy process

of return dispatch to the repair agency.

iii. Induction Warranty

The warranty by virtue of new fleet/aircraft induction provided by the aircraft

manufacturer and applicable for 3-5 years typically. Individual serial numbers

warranty expiry shall vary in accordance with part of readiness log of a

particular MSN of aircraft.

❖ A warranty expiry field as part of component record should be maintained as long as the component is under warranty. For all 3 classes of warranty, an FOC work order to be generated automatically with water mark on the work order

Page 93 of 189


9.0 Required Functionality for Engineering Business Development

9.1 Client Contract

a) Define Client Master Agreement

The Client General Agreement with all general terms to be stored in the system.

This agreement is the client master document for the client maintenance order. b) Define Client Maintenance Order

The Client Maintenance Order defines the actual terms for the actual client order.

The terms could be a fixed price order, based on time and material, a flat rate or on

condition. The actual operation and the cost data collection to be mapped with the

client orders and the respective terms. c) Client Contact Details data base

A client data base shall contain all needed client master data, but also the client

history including performed order but also lost proposals in a bidding process.

9.2 Order Management

a) Define Client Order System according to the contract terms

A client order system according to the contract terms to be defined. The client order covering all relevant sub order to be defined. The sub order is defined related to the various order types such as routine and non-routine maintenance, modifications, defect rectifications, subcontracting, engineering services and others. According to production needs, those orders may have suborders. All orders are linked together. Collected data such as Mh and consumed materials shall be displayed on each level in the hierarchical order system.

b) Monitor Client Order progress

The progress of the client order to be monitored displaying the order start date and the expected completion date. This to be done also for all sub-orders. Also, the consumed Mh and materials to be displayed, as well as the subcontract orders.

c) Monitor Mh & parts costs

The Mh & consumed parts to be monitored for client orders. This functionality shall

ensure and monitor profitability of the client order.

d) Monitor Repair abroad costs and progress

Especially for client orders but also for the PIAC operation the Repair Abroad Orders to be monitored concerning progress and completion date but also concerning the accumulated costs.

e) Order progress information accessible by the Client

The client shall have the capability to access via web PIAC production system and

monitor the progress of his orders

9.3 Proposal Management

a) Define master proposal.

Proposal Masters are defined and used as text modules for an actual proposal to be

submitted. The modules represent the scope of services of PIAC Engineering b) Store customized proposal

According to the client needs and the PIAC Engineering capability a proposal has to be designed. The proposal to be stored in the system, the proposal status to be monitored: such as pre-proposal, submitted, in negotiation, agreed. Also, no longer

Page 94 of 189


valid proposal to be kept to follow the client history. The calculation scheme also to be attached to the proposal

c) Monitor proposal success rate

Some functionality is needed to monitor the hit rate in the sales process.

d) Capability List

A capability list based on fleet, engines and part numbers and the respective activity type to be stored in the system. This is to be displayed to the market, but also used to calculate the scope of service and the costs for subcontracting.

9.4 Profitability Analysis

a) Calculate client order profitability

The client proposal is calculated with a particular profitability perception. This is to be monitored during performing the client order. Finally, after completion of the client order, the profitability of this order to be calculated.

b) Calculate complete client profitability

By maintaining the client relationship, further contracts to be performed by PIAC

Engineering. A profitability analysis along with the client history to performed.

c) Profitability analysis by region & products

PIAC Engineering Sales and Marketing needs further information for strategic and tactic decisions. For that reasons contract volume and profitability analysis to be performed by region and offered products. Also, an analysis concerning the target budget and actual performed volume per region and product to be monitored.

Page 95 of 189


10.Required Functionality concerning Power Plant Overhaul Power Plant overhaul has the facility to maintenance / repair / overhaul for Engines, APUs

& Landing Gears of various types. Functionality description outlined here in sub-section 10

to be considered applicable all of the three.

10.1 Production Planning

▪ Long-term planning Engine/ APU/ Component shop visits

Based on the LLP, hard time, on condition, engine removals, Engine Health monitoring data, on above information, shop visit to be planned and the first scope of work to be defined.

▪ Production/ capacity planning

The planned work load and the available human resource capacity to be balanced.

▪ Forward/ Backward event planning (incl. projection thru Gantt-Chart)

The engine/ landing gear shop visit to be planned on a project chart to show the duration of subsequent steps in a Gantt-Chart. A forward and backward planning to be provided. By getting real time data and feedback by production the chart shall be updated.

▪ The Bill of Work (BoW) and subsequently the Bill of Material (BoM) to be

defined on several steps according to the several inspections performed. Also, a full

integration between BoM and the subsequent material planning processes are

essential. Available parts locked others to be procured.

▪ Engine/ module disassemble management

For engine disassembly, the as is hierarchical parts list with part number, serial number and mod status to be provided. This list to be provided at the disassembly table to check the as is parts list and mark those parts to be removed from the engine. The parts to be removed, a removal tag to be generated by the system

▪ Engine/ module/ component build-up control

By building-up the engine a new hierarchical parts list to be defined by using disassembly parts list as a master. The new parts to be installed also to be notified in the parts list. A final check to be done by mirroring the new parts list against the former one and check modification status and the compatibility of parts.

▪ Other related functions performed in the shop

• Man-Power Planning in engine Overhaul shop section.

• Plan the Overhaul of engines/APUs and testing in-accordance with approved schedule maintained by TSE and manufacturer maintenance manuals.

• Plan the overhaul/ repair of engines/APU’s and engines components, not covered in PIA Engineering capability, at a third-party facility, in coordination with Repair abroad section.

• Components’ scrap process workflow.

• Inter shop engines /APU’s / parts movement tracking.

• Processing of vendors’ repair estimates/invoices/warranty claim.

• Maintaining history of LLPs.

• While estimating engine repair completion time, TAT of items sent to for third-party repair should be considered thru integration with related system/module.

Page 96 of 189


10.2 Engineering Functions related to Engine/APU/LG

▪ Modification status dashboard

The engine/ APU/ landing gear/ component modification status review for all serial numbers available in the system, including a hierarchical modification status view of the installed subassemblies.

▪ Modification management

Provision for complete modification cycle, starting from modification planning, scheduling, execution (in-house or from third-party), release and update of relevant system parameters.

▪ Update Engine/APU/ LRU counters & status

System should provide the capability for complex assembly management where counters (Fh/Fc/Days) of main as well as sub-assembly(s) are updated in parallel, whether on aircraft or in shop. The sub-assembly counters to be taken separately upon removal from the main unit (Engine/APU/LG). For any new subassembly installed, this becomes part of the complex assembly and respective counter are update along with main unit.

▪ Update Engine/ APU/ LG modification history

Any repair or modification to be added to the unit life record, with attachments as required.

▪ Update serialized components

The master parts list and the as-is parts list including LLP’s to be maintained, kept

and updated.

▪ Archiving performed work and all related documents.

All working documents and certificates to be archived and linked with the related

unit. The LLP’s and related component history to be updated. The record should be

easily printable reviewable for audit purposes.

▪ Create/ update/ revise Shop Work Sheet

System should provide capability for creation /update of work/task-sheets to be created, which are part of work package. All created work/task sheets should be maintained in a catalogue.

▪ Shop finding reports Defects and discrepancies identified by inspection to be entered in the system. The defect notification shall use a thesaurus, in order to allow statistical analysis. In case of parts the leading discriminator shall be the part number, in other cases the ATA chapter. The defect notification to be used for the reliability management, but shall also trigger the repair or scrap process.

▪ Updated OEM manuals

System should support the availability of updated Engine/APU/LG & Component

manuals thru Documentation management function.

10.3 Engine Health Monitoring

The system should either indigenously support the Engine Health Monitoring or

through an interfaced third-party application.

The EHM should be based upon industry best practices.

10.4 Shop/ Work Place Control

▪ Work center performance monitoring

Page 97 of 189


Production planning shall monitor work load and performance at each work center. The backlog to be displayed, as well as open time slots.

▪ Backlog priority management at Work Center

A priority management to be available for the work order backlog. Especially the

priorities between close loop parts and repair for stock to be well balanced.

▪ Mh and Machine hour recording

For each work order, the man hours and machine hours to be recorded by using

base code: clock-in and clock-out

▪ Tracking & tracing parts in the shop

Using the clock-in and clock-out information, parts to be traced and tracked in the

workshop by acknowledge arrival & departure of the part at the work center (WC).

▪ Multi stage component routing

In case a unit to be overhauled consists of several assays and sub assays, a multi stage routing and component tracking to be available. The system shall provide support to define time limits for each work order to optimize the turnaround time of the complete unit.

10.4.1 Engine/APU Maintenance/Overhaul Work Flow. System should provide process flow for Engine / APU shop functions;

• Disassembly, cleaning, inspection assembly of engines.

• Static and dynamic balancing of rotating group.

• Maintenance support like BSI, inspections, parts replacement. ▪ Video imaging and recording on large gas turbine engines as and when applicable. ▪ Fan blades replacement. ▪ Overhaul, buildup of APUs.

10.4.2 Engine/APU Test &QEC Build up section Work Flow. ▪ Test & troubleshooting of engines /APU’s. ▪ Troubleshooting, Trim Balancing, Preservation of engines and component

replacement related to b/up of engines. ▪ Support workflow for engine buildup. ▪ Support workflow for incoming and outgoing inspections and identify shortages for

completion engine / APU build up.

10.4.3 Landing Gear Shop Work Flow. Support workflow for landing gear maintenance, of various types.

▪ Material Planning for hard-time components. ▪ Subassembly removals including harnesses for shop test/repair. ▪ Assembly completion including L/G harness installation.

• Testing & Release.

10.5 Budgeting & Financial Control (through integration with ERP)

▪ Budget planning for Engine/ APU/ Component OH

Based on the fleet plan, the engine/ APU/LG& installed component removal rate; the number of shop visits to be defined. Based on these key figures, the needed material & Mh recourses for in-house repair and the expected budget for subcontracting repair abroad to be calculated.

▪ Repair/ overhaul cost control

The repair/ modification of each engine/ APU component to be monitored by posting the spares / subcontracting costs and the consumed Mh on the Repair/ overhaul order.

Page 98 of 189


11. Required Functionality for Tools Managements, & Standards Lab

11.1 Tools Master Data

a) Define tools, GSE and figures locations & quantity

All tools GSE and other units to be registered with location and quantity

b) Define tools master data.

The master data to be maintained

c) Functionality for reservation, in-use, available tools

A requisition functionality to be in place with availability status and to block the required tool for a period.

d) Transportation order for tools

A dispatch order to be defined for transport the tools

e) Statistics concerning utilization

Statistical function for concerning usage of tools.

f) Maintenance planning of tools & repair

Maintenance plan for fools and repairs. Also, a repair order to be submitted.

11.2 Calibration of tools

a) Register tools

All tools to be calibrated to be registered in the system, with ownership specified.

b) Schedule tools calibration

a) A scheduling functionality to be available for calibration purposes. Optimal

planning with staggering of Cal required equipment visits to Standards Lab. The forecast for calibration is given to concerned department by providing a report.

c) Report compliance

A calibration report is given and the calibration results are notified. The serviceable or unserviceable status of the tools is marked. This status will have an impact to the tools reservation system.

11.3 Standards Lab Functions PIA maintains an Electrical & a mechanical Standard Lab. Both operates in a similar fashion, and supports calibration services for electrical/electronic & mechanical equipment calibration.

MRO / M&E system should support following work flow; b) Tools/equipment work order generation as received from tools store. c) Calibration check/adjustment/repair performed and recording the results in

the system. d) Issuance of Calibration sticker / certificate with next due date. e) Intimation to respective tool store for receiving of the calibrated

tool/equipment. f) Where local Cal/repair capability not exist, sending the tool/equipment for

contracted maintenance g) Capability for Tracking of Cal/Repair cycle at Standards Lab by the concerned

tools store / user section.

Page 99 of 189


C3 General Requirements of the MRO / M&E System

1. Ability for Integration with ERP &Interfacing with Sabre, IBM Lotus Notes

➢ Oracle ERP system controls all major PIAC resources. A smooth integration between the Oracle ERP, and MRO / M&E system is required. The following areas for integration are highlighted:

Financial Accounting, Financial Control, Budgeting, Purchasing, Logistic, HR, Training & Qualifications.

➢ Sabre Products AirFlite, AirCentre & Sabre AirVision applications are used in Flight planning &scheduling. An interface to MRO / M&E Solution is required at minimum; Following areas for interfacing are specifically highlighted; Schedule/Slot/Fleet management, Flight Plan/Movement manager

➢ AIMS ➢ Any other Application

2. MIS & Reporting

▪ Key Performance Indicators (KPI) to be reported for all major sections in PIAC

Engineering on regular basis. The KPI to be defined by PIAC.

▪ The PIAC Engineering Management shall get regular reports concerning the regular and un-regular operation.

3. The System will control the day-by-day work

▪ All work packages, tasks and business activities will be initiated and controlled by

the system.

▪ Subsequently all Labels, Orders and Certificates are printed by the System.

4. Drill down option and flexible reporting

a) From the top to the bottom it must be possible to generate more details if required.

From the individual A/C to a BoW, to the individual WP, to the JC and finally to the

details of each JC must be possible.

b) Beside a number of regular used reports, a flexible report generator shall prepare

reports on occasional basis.

c) Tracing of information

Within the system, it should be possible to trace information along a logical path. It

should be possible to see a component removal order, follow the PIAC intern

dispatch order of the part, see the request for proposal, the repair order, the customs

Page 100 of 189


clearance, the QA reports, the invoice, the invoice verification process, the final

payment posting etc.

d) Dashboard for Management / Planning & Maintenance Operation Center

A Dashboard for showing on PC and scalable to large screen regarding status of the entire fleet whether on ground or in air. Inflight defects reporting to be supported through ACARS or other industry tools, while on ground current maintenance activity (planned / required) as highlighted trough Tech log, MIC, deferred defects, unscheduled events etc. should be displayed. Option to select a single station, bay, fleet or aircraft, or grouping of more than one should be possible.

5. Flexibility

a) Organizational changes shall be easily addressed in the System by re-configuration.

b) In case of outsourcing of parts of the production units (e.g. Base Maintenance,

Engine OH), the system shall be able to be customized accordingly.

6. Advanced MRO / M&E Concepts

a) System Should support e-Tech-Log (incl. Cabin Log), with tablet / mobile solutions

both online and offline (with seamless synchronization upon network availability)

b) Airplane / Engine Health monitoring,

c) Analytics Tools for predictive & prescriptive troubleshooting of defects. Future

upgradability for IoT solutions.

d) RFID, Smart card, barcode based emerging trends.

e) Solution provided by bidders must be compatible / available on all mobile/cell

phone, tablets &iPad.

7. Required Interfaces of the new MRO / M&E System

a) The Aircraft log data (Fh, Cycles, Landings) shall be entered at one location at PIAC. -

Or automated upload of the SITA telex. This shall be done within PIAC operations. The

MRO / M&E System shall have an interface for a real-time data upload. ACARS shall

be used where possible.

b) The Aircraft Rotation Plan shall be available online for PIAC-Engineering. LM

Production Planning shall actively use the displayed ground time for the medium and

Page 101 of 189


short term maintenance task planning. The Aircraft rotation plan will show interactively

the planned A/C assignments to routes and the slots maintenance events.

c) The Commercial Flight Schedule shall be online available for long and medium-term

planning. PIAC Engineering will request online slots for letter checks (A, B, C, D).

d) PIAC Operations will monitor operational performance and A/C dispatch reliability. An

online interface will provide the data for PIAC Engineering

e) PIAC Finance is responsible for the Financial Budget and Financial Accounting. The

data are shared with PIAC Engineering on online basis for performance monitoring and

planning purposes. This would require an interface with Oracle ERP.

f) Automated upload /availability of all up-to-date (current revision) OEM manuals, such

as AMM, IPC, SRM, EMM, TSM and others using the S1000D standards.

g) The Service Bulletins (SBs), ADs, etc. shall be auto up-loaded from OEM website.

h) Material Master Data shall be up-loaded using the AMTOSS and SPEC 2000 data

standards.

i) Upload of Vendor capability list, price list, availability status and others, for contracted

maintenance.

j) Electronic exchange of agreements, purchase order, delivery/ repair status, invoice,

payments. Supported formats shall be XML, SPEC2000 and others. An international

B2B communication platform to be interfaced for exchanging procurement and repair

status information.

k) The new System shall support a WEB Portal to provide major information and data for

production to an Intranet Web Portal. It is the target, to avoid time consuming and

outdated paper based distribution of information.

l) The system to be ready for RFID applications to be integrated. Also, the PIAC

employee ID card to be read for employee acknowledgement, specifically to monitor

job/task Mh. consumption.

m) Working papers such as Job Cards and parts tags to be printed with barcode. Bar

code readers to be integrated for man hour recording and parts tracking.

Page 102 of 189


SECTION D

SERVICES REQUIREMENTS

Page 103 of 189


D1. Implementation

1. As part of its proposal, the Bidder must submit an Implementation Strategy and Plan

which caters for the following, to be performed by the Bidder: -

1.1 Installation of the Interim Server(s) including the Operating System.

1.2 Installation of all supplied application software, DBMS software,

Development/Query and Report Writer/Database Administration Tools and

any other required Utilities, on the Interim Server/s.



any other required Utilities, on the Permanent Servers.

1.4 Implementation of Database security features

1.5 Development of Business Requirement Document for each functional area,

which maps the business process for the parameterization of MRO / M&E

Package. This document should be based on PIAC’s reengineered business

processes that would be made available to the Contractor. PIA will review

and approve this document within ten working days of submission before

Contractor can start work on parameterization / configuration of the MRO /

M&E.

1.6 Development of business case scenarios for testing MRO / M&E Package.

1.7 Parameterization of supplied Software i.e. the configuration of application

software via selection of in-built values, setting up of tables, etc. to meet the

business requirements.

1.8 Software modifications, where required, to supplied Application software and

development of extensions and/or modules to meet the business

requirements.

1.9 Design and development of customized reports, screens, workflows, etc.

PIAC will try to maximize the use of standard reports, screens and workflows

available in the proposed solution; however, the Contractor cannot set an

upper limit to the number of customization that it will undertake.

1.10 Integration with PIAC’s other applications such as Oracle ERP, Sabre

applications, AIMS, PIAC website, etc.





1.12 Unit, Integration and System testing prior to User Acceptance testing.

1.13 Data conversion activities.

1.14 Design and implementation of Online and Batch job operational procedures

until implementation is successfully completed at all locations.

1.15 Bidder will provide regular progress reports of the project pinpoint

obstacles/short comings if experienced well in time.

Page 104 of 189


1.16 Quality Assurance for Bidder related activities.

1.17 Any other tasks required in successful delivery of the supplied products and

services.

2. The Contractor must utilize airline industry specific rapid implementation templates

to ensure quick implementation. Details of such templates should be submitted with

the Technical Proposal.

3. A detailed comprehensive project plan is to be prepared by Contractor and

submitted as a part of the proposal. The plan shall be mutually approved and

incorporated as part of contract and reviewed at regular intervals.

4. The Contractor must submit a detailed project organization structure identifying, by

name, the specific individuals who would be assigned different tasks of this project.

4.1 The Contractor must assign a full-time Project Manager to manage this Project.

This person must be from the list of Lead Consultants submitted by the

Contractor in response to the EOI. He / she must have the experience of

implementing the proposed MRO / M&E SOLUTION in at least two airlines.

His/her detailed CV including experience of managing MRO / M&E IT and other

Projects, MRO / M&E IT Package Certification, if any, the number of MRO / M&E

projects managed and the number of years on each project, etc. must be

submitted along with the Proposal.

4.2 A personnel roster containing detailed responsibilities of Contractor staff who

shall be assigned by the Contractor to perform duties or services under the

contract should also be provided. The roster should include estimated number

of hours to be worked on the project for each person broken down in different

phases of the project; it should also clearly identify the start and end dates for

each phase. These staff members should be from the list of implementers

provided in response to the EOI.

4.3 If additional members are assigned to the project, their detailed CVs should be

submitted as part of the proposal. PIA recognizes that occasional substitution of

Contractor staff may be necessary after an apparent bid winner is determined

and during the project. Staff proposed as substitutes must have qualifications

equivalent to or better than those being replaced and must be approved by PIA.

5. The Contractor must provide, by phase, the proposed number of personnel to be

based on-site at PIAC’s premises. Space and other logistical requirements to be

provided by PIAC to the Bidder’s Implementation Team should be specified.

6. The Contractor’s implementation plan must take into consideration the business

priority areas and applications.

Page 105 of 189


7. The Contractor will develop a system turnover plan which indicates the conditional

criteria required to fully turn over the daily operation of the system to PIA technical

staff. At a minimum, the turnover plan must include the state of readiness required

for system turnover and all required documentation.

8. System Performance: During system installation, the Bidder will evaluate

performance factors including, but not limited to, transaction volumes, response

times, CPU utilization, and input/output activity. The Bidder will be responsible for

tuning the application to meet acceptable response times.

9. The Contractor must submit a detailed Testing Methodology. The Bidder may

perform Unit, Integration, and Systems Tests off-site; however, the official Systems

Test and all User Acceptance Tests must be performed on-site using PIAC’s testing

environment.

10. Capacity Evaluation: The Contractor will conduct a Capacity Test that will include stress

and volume testing. Capacity testing shall include a stress test that includes simulation

of at least 30% of the system workload and volume tests that test the database activity

against at least 30% of the data volume. The Contractor will document, the conclusions

resulting from the test.

11. Project Management and Reporting: The Bidder is required to maintain a project

plan covering its components of the project and each individual phase. The plan

shall include project organization, work break down structures, schedules, critical

path determination, and other features required to track and manage this project.

12. Project Quality Management: In its proposal, the Contractor must describe its

approach for assuring the quality of its components on this project. The proposal

must demonstrate an understanding of the Contractor’s ultimate responsibility for

quality and define a comprehensive set of reasonable and effective practices for

fulfilling that responsibility. Contractor must also specify whether third party audit /

quality assurance visits will be undertaken and who will bear the cost of these visits.

13. Acceptance Testing: PIAC’s M&E Team will conduct a rigorous acceptance test of the

system. PIA user staff and information system specialists will exercise all system

functional aspects using appropriate test data (use cases developed from real-time PIA

engineering & maintenance operations) to assure that the system meets defined

business and technical performance requirements. During this test, PIAC’s MRO / M&E

Team will identify required modifications and document them through the problem

resolution or change management processes (described below) as appropriate. The

Contractor shall modify the system as required and provide new versions of modified

components to PIA for testing. PIA will notify the Contractor in writing when it

determines that the system is acceptable.

Page 106 of 189


14. Problem Resolution: The Contractor and PIAC’s MRO / M&E Team will cooperate to

resolve system problems found during acceptance testing and production use,

including the warranty period. PIA will prioritize and report problems in a written

format. The Contractor shall track these problems to closure and report their status.

The Contractor shall evaluate each reported problem, estimate the time needed to

resolve the problem, identify potential impacts on the system and the project, and

report to PIA. If PIA decides to proceed, the Contractor shall resolve the problem

according to its assigned priority.

15. Change Management: PIAC’s MRO / M&E Team and Contractor will cooperate in

managing changes to previously agreed upon system functional capabilities. PIAC’s

contractor will identify potential functional changes and propose these to the

Contractor in writing. The Contractor shall evaluate each proposal, identify potential

impacts on the system and the project timeline, and report to PIA. If PIA decides to

proceed, it will prioritize the change and authorize the Contractor in writing to

perform the work. The Contractor shall track the status of in progress change orders

and report to PIA upon request. However, cost escalation will not be allowed under

any circumstances.

16. Configuration Management: The Contractor shall manage version releases of all

contract deliverables and certain other critical documents as determined by PIA.

This process shall assure that the status of all deliverables is known, that only

approved versions are released for production use, that prior released versions can

be recreated, and that changes are made to released deliverables only when

authorized by PIA. The final release of each controlled deliverable must reside in a

library (preferably computer based) under PIA control.

17. The contractor will ensure that the MRO / M&E solution is in compliance with

regularity requirements of PIA’s Organization approval under Pakistan Civil Aviation

Authority’s ANO-145. PIA Quality Assurance will apply to Pakistan Civil Aviation for

compliance verification audit. The contractor will be required to cooperate with the

PCAA audit team, by providing functionality demonstrations and reports as required.

Any non-compliance shall be addressed by the contractor in liaison with PIA QA & IT

Team, till compliance is verified.

D2. Training

1. Training is required in two main areas: (a) Technical Support Staff, and (b) Systems

Users. Technical Support Staff will comprise of System Operators, System

Administrators, Database Administrators and Developers. Systems Users will

comprise the staff from different functional areas of Engineering & Maintenance, at

all stations. Three levels of Systems Users are currently identified as: Key Users

(responsible for system parameterization in the future), End Users and Senior

Management (who are expected to be provided System Overview). It must be

classroom based training.

Page 107 of 189


2. As part of the proposal, the Contractor must describe in detail its approach to

meeting the training requirements for each audience. The description must include

methods proposed to deliver both training and documentation. The Contractor

should describe the general content of all training materials, training courses, and

documentation proposed.

3. The Contractor will be required to develop a Training Strategy to ensure that all

identified Systems Users and Technical Support Staff is thoroughly trained in the use

and support of the system. Training for Key Users must be imparted early in the

implementation stage, preferably in the first month, to enable them to actively

participate in the parameterization process

4. The Training Strategy should include a training solution to support the training of

users throughout PIA Engineering & Maintenance covering all functionalities and

Add-on applications. The Contractor will be required to develop formalized

classroom training sessions, to be delivered by their staff, for each of the user groups

identified to ensure that the trainees become familiar with all the system features of

the implemented applications. In addition, where required, for technical staff,

informal training should also be included.

5. For PIA technical staff, the Training Strategy should include a plan to train the

required staff in the Development and Administration tools supplied, and provide

them the knowledge to efficiently operate, use and maintain the system independent

of Contractor assistance. Technical training materials must be comprehensive and

detailed.

6. The Training Strategy will address, at a minimum, the following:

a) Description of the Course, the Course outline, specifications of the number and

appropriateness of staff who will attend, probable dates for classes, etc.

b) Proposed content of all training materials.

c) Description of proposed software / tools (these may include training aids,

manuals, on-line references, quick reference guides or templates, or computer

based training), and their use during the training.

d) Details of the physical locations to be used for training.

e) Training evaluation methodology

f) The names, qualification and ―Formal Training‖ experience in man-months, of

the instructors for each training course.

7. The Contractor is required to provide materials for training users in central and

remote locations. The User Staff training materials must cover, at a minimum, the

following topics:

a) Systems Overview

• systems benefits;

• data inputs, outputs, and reports produced;

• major systems business functions;

Page 108 of 189


• Users‘ Manual contents and usage;

b) Systems Usage

• entering data and data validation;

• data correction and user help features;

• menu and system function traversal;

• problem recovery;

• report contents, report generation / suppression;

• search and inquiry features;

• record update procedures;

c) Systems Operation

• job recovery;

• job scheduling;

• job cycles (daily, monthly, quarterly, annual, and special);

• special forms usage;

8. The Contractor must provide material for training Technical Staff such as database

administrators, system administrators, operators, and developers. This material

must cover all aspects of systems design, operation, and maintenance including, at a

minimum, the following topics:

• application and database design and architecture;

• application structure and module / sub-module / program / subroutine

relationships;

• application start-up / shut-down procedures;

• application back-up, recovery, and restart procedures;

• data dictionary structure and maintenance procedures;

• database logical and physical organization, and maintenance procedures;

• application security features;

• audit and testing procedures;

• system data entry; checking, correction, and validation procedures;

• user help procedures and features;

• system troubleshooting and system tuning procedures and features;

• system administration functions management;

• setting and changing system password and user ID security features;

• system interface processing;

• on-line and batch processing procedures;

• unique processing procedures;

• report generation procedures;

• Menu structures, chaining, and system command mode operations.

9. PIA requires the training material on CDs. All training material provided by the

Contractor will be reproduced and used as needed by PIA.

Page 109 of 189


10. Cost of Foreign Training, if proposed, should be included in the Contractor‘s

Commercial Proposal and include all expenses related to travel, accommodation,

tuition fees and other incidentals.

D3. Data Migration

1. PIA currently uses internally developed application named ‘PAMMIS’ (PIA Aircraft

Maintenance Management Information System). The underlying database is

IBMDB2 format.

2. The application is used to perform functions such as Engineering, Tech-Log, LRU

Management, Tools & Calibration, Fleet Performance, Work package & Check

Planning, Readiness Log, Shop functions with Operator Mh, AD/SB records, and

certain other minor functions of the entire PIA fleet.

3. The Bidder should include, as a part of its proposal, a Data Migration Strategy which

includes description of its general approach to the data migration process for

configuration, seed, history &cutover data.

4. The Data Migration Strategy must address, at a minimum, the following:

a) Migration process (automated or manual, verification procedures)

b) Migration schedule / time frame

c) Migration preparation task outline

d) The resources that will be required.

e) Any training requirements

f) The programming effort that will be undertaken OR acquiring of third-party

industry solution/application, should also be described.

5. The Successful bidder would be required to prepare a Detailed Migration Plan, which

must address the following:

a) Identify data elements to be migrated.

b) Identify any special forms and procedures

c) Identify any control procedures and evaluation criteria.

d) Identify, with the assistance of the PIAC, the personnel needed to participate

in the migration of the data.

e) Plan any interim file maintenance requirements.

f) Develop migration programs (This includes specifications, program coding,

test plans, and complete testing)/acquire third-party industry solutions.

g) Present migration plan, procedures & program to PIAC for approval.

6. PIAC expects the Bidder to perform the following tasks: -

Study the existing application and databases and;

a) Ensure smooth transition without compromising routine operations and

without any downtime.

Page 110 of 189


b) Design and develop/acquire a solution including intermediate utility (if any) to

migrate the data from existing databases to the new databases, ensuring data

cleansing and integrity.

c) Demonstrate and test this data migration on sample test data from existing

live applications.

d) Develop and document all operational and technical areas for above solution

D4. Documentation

1. As part of its Technical Proposal, the Contractor must describe the level and types

of documentation that will be delivered. This documentation must cover each level of

operation, for example: user, security administrator, database administrator,

operator, developer, etc.

2. Two complete hardcopy sets of documentations for all Bidder supplied components

for this Project must be furnished, in addition to softcopies on CDs.

3. The Manuals should feature clear organization of content, easy to understand

language, useful graphic presentations, and a thorough index and glossary. These

will under the following categories:

• Detailed process manuals

• User manuals

• Operational manuals

4. These manuals must address the view of the system required by business unit staff

(end users). It must contain sufficient information to enable the user to

independently operate the system, troubleshoot simple problems, and correct

problems. The manual must be able to serve as a reference guide and a teaching

aid. It must cover all facets of system functions and operations, including:

• Complete instructions for the users, completely explaining the use of each

system function;

• System usage scenarios, based on real world examples drawn from the day-

today workloads of typical users, that fully describe and explain the salient

features and operation of the system;

• How input data are stored and related between system records;

• How to generate/suppress standard and ad hoc reports;

• Normal report distribution;

• Prioritization processing, system determined priorities, and user override

procedures;

• System log-on, log-off, and security features;

• Error messages and error correction procedures;

• Help features and usage;

• System troubleshooting;

• Mandatory data fields and default data values;

• Traversing system menus;

Page 111 of 189


• Screen layouts and contents;

• Inquiry functions

5. In conjunction with the Users’ Manual, Quick Reference cards will be produced by

the contractor, which will be an immediate aid to the user and quickly describe

operations.

6. The Technical Manuals must address the view of the system required by

developers, administrators and other technical personnel. It should provide an

understanding of the application; database design and file structures; relationships

between programs, security; troubleshooting; special constraints; and other

operational guidelines.

7. Copies of all licenses, warranties, maintenance agreements and similar materials for

all Bidder delivered components of the project must be furnished separately.

8. Contractor must submit sample copies of all documents that it will prepare / deliver

to PIA during the course of this project.

D5. Warranty and Maintenance Support

1. The Bidder will provide warranty services for a period of at least one year for

software and a minimum of three years for hardware by ensuring that the system in

every way meets the specifications stated in this RFP. The warranty begins upon

PIAC’s written final acceptance of the system14. All warranty support services,

whether on- or off-site, are to be rendered free-of-charge to PIAC; the Bidder shall

be responsible for any travel costs associated with warranty support services. The

warranty to be also given for the underlying DBMS.

2. Separate and apart from the warranty support services, the Bidder shall provide

support (“Maintenance”) services for Applications, and DBMS beginning upon the

end of the warranty services and extend upto three (3) year thereafter.

3. The Bidder must describe in detail in the Technical Proposal its User and Technical

Support Plan for the warranty and maintenance periods, covering the resources,

timing and procedures that will be available to provide this support. The plan must

include identifications of procedures for on-site and off-site maintenance during

normal hours of operation, for:

• On-site fault diagnostic techniques;

• Remote or tele-diagnostic fault diagnostic techniques;

• Average time to arrive on-site;

• Mean time to fix major system components; •Fault escalation procedures;

• Maintenance of error logs.

4. The Bidder must specify the various categories of problems it will support and

describe the severity levels of problems. The escalation process must assure

Page 112 of 189


appropriate management contacts can be made in the event that the support

response is not effective. PIAC would like to sign a Service Level Agreement (SLA)

(that would include penalties for non-performance or poor delivery) for maintenance

support with the Contractor.

5. Details of the establishment of an effective “Hot Line Telephone and Support Desk”

service should be provided. Internet enabled support, if available, should be

highlighted.

6. PIAC may require the Contractor to develop additional customized reports, screens,

workflows, etc. during the maintenance and support period. Contractor must specify

in its Technical Proposal a solution to accommodate PIAC’s requirement. The Price

Proposal must contain the pricing mechanism for additional development /

customization.

7. The Bidder should provide a list of clients for which MRO / M&E Package

Maintenance Support is, or has been provided during the past three years. Details of

the modules supported should be included.

____________________________________________________________________

14Acceptance

The MRO / M&E Solution shall be deemed accepted upon the successful completion of Acceptance Testing of all supplied applications and modules, conducted in accordance with PIA's Acceptance Criteria which will test the desired functionality and interoperability of Contractor supplied applications and modules.

D6. Version and Upgrades

1. Contractor must ensure that training material / software / process documents are

duly licensed for the purpose of implementation and use by PIAC of the MRO / M&E.

These are to be of latest version and Contractor must ensure up-gradation of all

modules / material / process documents during the warranty period and as part of

after-warranty maintenance support.

2. During the implementation and subsequent rollout Contractor would be responsible

to arrange and provide free version upgrades of all components under its

responsibility. Contractor must ensure that at the time of handing over the solution to

PIAC all components are of the latest release and that the total solution is certified

by the Contractor for completeness.

3. All updates. Additional features, version and upgrades will be part of the cost and

PIAC will not pay any such cost for the change, within warranty period.

Page 113 of 189


D7. Information Needs of the management and Application Requirements

PIAC requires management information systems that support its decision makers by

fulfilling their daily information needs and also assisting them in creating different

scenarios and providing what-if analysis.

The CEO, CTO and other key senior management personnel are responsible for managing the day-to-day operations of PIAC with respect to Engineering & Maintenance. Their information needs pertain to monitoring, controlling and directing the operational and financial management activities of Engineering & Maintenance particularly; ▪ Close and thorough monitoring of on ongoing & planned maintenance events,

projects& their associated cost. ▪ Safety & regularity Audit compliance status, plans & associated costs if any.

The information should be available as desired, and may require interfacing with PIA internal systems. The format of information shall aim at comprehension, analysis & decision making.

D8. System Security

System must be secure enough to handle the internal and external threats. SSL

security and firewall must be integral part of the proposed solution.

Page 114 of 189


SECTION E

PRODUCT REQUIREMENTS (OTHERS)

Page 115 of 189


E1 DBMS and Database Administration Tools

The Contractor is required to supply the latest version of DBMS that effectively supports

the proposed MRO / M&E Package. To this extent certification of MRO / M&E

manufacturer that the particular version of the DBMS is supported by the MRO / M&E

should be provided.

1 Database schema definition, management, query and reporting facilities must be

provided.

2 Historical transactions must be maintained by the DBMS. Facilities for reviewing

transactions, multiple transaction roll back and transaction log reporting are required.

3 Database update facilities must include features such as the use of working copies and

status reporting on query and update operations.

4 The system must provide locking mechanisms for update and delete operations.

5 The system must maintain concurrent control mechanisms to ensure the correctness of

transactions and to detect and resolve deadlocks on the network.

6 The system must support authorization lists and groups for create, read, update and

delete.

7 The provision of on-line facilities to manage transactions and overall on-line system

performance is desirable.

8 The system must provide users and applications with distribution independence.

Users do not need to know where database objects are located.

9 The system must operate in a distributed environment where different nodes of the

network run at different functional levels.

10 The system must have the ability to automatically recover and restore the database

fully to the last consistent state after a media or system or database failure.

11 The ability to notify users as to what transactions were being processed but not written

to the database during a crash is highly desirable.

12 The system should have archive logs and checkpoint facilities and the capability to roll

back / undo to any one checkpoint.

13 The system must continue to be available to users during any backup process or

alteration of the database schema’s and definitions.

14 The system must support one-to-one, one-to-many and many-to-one relationships.

Page 116 of 189


15 The system must be capable of working in a multi-tier environment, and provide the

appropriate tools for partitioning the location of the processing. All tuning must be

independent to the user.

16 All information in the database must be represented as values in the table.

17 Null value support (as opposed to empty character strings, blank characters or zero)

must be available for all data types.

18 Database recovery must be made in minimum acceptable downtime. Acceptable

downtime is to be negotiated and agreed upon

19 DBMS should have a support for ELT

20 DBMS should have support for SAN storage and cluster environment

21 Load balancing and failover must be supported to minimize down time

22 DBMS should support DR sites and automatic standby configurations. It must be

capable of operating in the DR environment and support synchronous as well as

asynchronous data replication at remote DR site

23 DBMS should be capable of supporting large amounts of data in terra bytes

24 DBMS should have support for transmission of data from other new systems as well as

exiting legacy systems

25 It should support libraries to enable backup on tape and disk drives

26 It should have support for new firewalls and n-tier network architecture.

27 It should have support for Analytics, OLAP, OLTP and DSS systems

For effective monitoring and management of the database, the Contractor is required to

provide, as part of its solution, Database Administration Tools that will help database

administrators in database monitoring, storage analysis, capacity planning and

performance monitoring and including trend analysis, size estimation and table creation.

E2 Application Development Tools

All application development and maintenance will be carried out on the centrally located

development server. The Contractor will be required to propose and supply application

development tools, consistent with the proposed MRO / M&E Package. It is expected that

the proposed solution comes with a built-in 4GL development environment tool set.

Page 117 of 189


E3 Query and Report Generator Tools

The Contractor must provide complete query and report generator functionality, preferably

within the provided system. The report generator functionality must include a scheduling or

production process for routine reporting.

The report generator functionality must be robust and oriented to the skills of "average"

desktop systems users and should support SQL. Formatting and statistical capabilities

such as averaging, multi-level sub-totaling, percent change comparisons, standard

mathematical operations and financial calculations is required. Generated reports must be

able to be saved in several output formats, at a minimum: Data Analytics, web-services,

APIs, XML MS Word, MS Excel, Text, PDF, HTML and XML.

The Contractor must describe its query and report generator systems in detail in the

Technical Proposal.

E4 Interim Servers and Operating System

1. PIA intends to purchase, the Server hardware and Operating System software required

for the MRO / M&E Application and Database.

2. PIAC’s purchase of the required Server Hardware and Operating System software will

depend on the selected Contractor’s recommended architecture in accordance with

details provided in Section E – Subsection E4.

3. However, in order to avoid any delay in meeting the Project completion milestone, and

to cater for the lead time required by PIA in the procurement process, the Contractor is

required, as part of its proposal to provide, without any cost to PIA, an Interim Server

and Operating System Software, as follows:

3.1 The Server, (or Servers) will be installed by the Contractor at PIAC’s Computer

Centre.

3.2 The Server(s) will be used for the purpose of configuration of the MRO / M&E

Package, development of Add-on applications, training of staff, and testing the

system.

3.3 All necessary hardware components such as CD-ROM drives, tape drives (for

back up purposes), etc. should also be provided on an interim basis.

3.4 Software components, such as DBMS, Development tools, 3rd party

Software, etc. provided by the selected Contractor will be initially used on the

Interim Server.

4. It is anticipated that the Server(s) will be required for a period of approximately six to

nine months from the date of supply of Server Hardware, Operating System Software

and MRO / M&E Package Software.

5. Subsequent to PIA purchasing and installing the required Permanent Server Hardware

and Operating System software, the Contractor will be required to re-install all MRO /

Page 118 of 189


M&E, Add-on applications, DBMS, database administration tools, application

development tools, query / report generating tools, 3rd party software, etc. on the

Permanent Server(s).

6. The details of the proposed Interim Server(s) hardware Configuration and Operating

System software are to be provided by the Contractor in its proposal.

7. The configuration of these machines should be capable to support the number of users

as specified by the Contractor in its plan.

8. In its proposal, the Contractor will provide site specification requirements for the

installation and operation of the Interim Server(s). It will be the responsibility of PIA to

cater to the prescribed site specifications.

9. PIA - at the end of implementation and rollout - may at its discretion, decide to purchase

the interim servers provided by the Contractor. In this regard, the Contractor should, as

part of its Price Proposal, separately mention the cost at which it would offer these

machines for sale to PIA. However, this cost component should not be added to the

total bid price, nor should it be used to calculate the bid bond amount.

E5 3rd. Party Software

1. In order to effectively manage and run the complete solution some other 3rd party

software and application programming interfaces (APIs) may also be required to

integrate various applications and execute and monitor the complete solution.

2. Contractor will be responsible to ensure that all required 3rd party software, operating



interfaces, etc. are made available, documented, designed, implemented and

operational to meet PIAC’s requirements in the proposed MRO / M&E solution.

3. It is the responsibility of the Contractor to offer PIA a complete solution in all respects –

delays or costs arising out of any shortcoming will have to be borne by the Contractor.

Page 119 of 189


SECTION F

HARDWARE REQUIREMENTS

Page 120 of 189


F1 HARDWARE

The Contractor must evaluate and prepare an appropriate configuration to run the

proposed MRO / M&E solution. PIA is looking for a high-availability solution including

servers, clustering design, and disaster recovery recommendations besides maintenance /

repair options needed for the associated infrastructure.

1 Contractor should submit details of the proposed configuration, including layout

diagram detailing model designation(s), memory size, number of CPUs, type of drives

with capacity and counts.

2 The offered solution should comply with the Open Systems Architecture and latest

technology trends.

3 The solution should be scalable, both horizontally and vertically.

4 The hardware should be sized keeping in view the operational requirements of the

MRO / M&E and associated applications.

5 The hardware should be fully capable of hosting the MRO / M&E certified database.

6 The hardware must allow each partition of the MRO / M&E environment to be isolated

in such a way that a software fault in one partition will not have an impact on another

partition.

7 All software required for clustering of servers and implementation of DRP should be

included in the solution.

8 The solution should be fully supported by the Contractor for not less than ten years

from the date of supply. It should remain capable of being supported, upgraded and

extended by the Contractor during this period.

9 The solution provided should be accompanied with complete documentation, operating

manuals, system diagrams, startup and recovery procedures and all other information

required for proper and efficient operation.

10 Contractor should provide all technical material and verifiable benchmarks related to

the proposed solution. The hardware should be certified by the MRO / M&E principal

vendor for the operation of the MRO / M&E and be reasonably expected to be certified

for future versions of the MRO / M&E during the expected life of the hardware.

11 Contractor should provide information on warranties on the equipment and any options

regarding warranty extension. Principal’s assurance is required for parts availability

after expiry of warranty period.

12 The Contractor must provide a thorough and contemporary 3rd party testing software

for acceptance and load testing. The testing should be done according to system

equipment specifications as well as generally accepted practices.

Page 121 of 189


13 All test results should be completely documented by the Contractor. Complete test

documentation including results of the 3rd party load / stress testing software should be

provided to PIA.

14 Based on PIAC’s high availability requirements, failover design should be based on

protecting single point of failure.

15 For high availability on the application layer, the solution should implement log on load

balancing between the application servers. It should not need any form of reallocation

of resources between servers. The application environment should be sized and

designed such that upon failure of an application server (based on single point of

failure), minimum degradation of performance is experienced.

16 A Disaster Recovery (DR) design should be provided which provides a seamless, pragmatic DR process. It should integrate within the overall design of the MRO / M&E landscape.

17 The DR process should be simple to execute. A step-by-step process and procedure

is required to minimize the potential for human error in a time of crisis and disaster.

Additionally, the DR design must be easily tested with minimal impact on day-today

operations.

Page 122 of 189


SECTION G

BIDDER’S QUALIFICATION, EXPERIENCE

&

EVALUATION

Page 123 of 189


G1. Bidder’s Qualifications and Experience

Technical Proposals shall provide the following information (referencing the subsections in

sequence) to evidence the Bidder’s qualifications to deliver the services sought under this

RFP:

1 A brief, descriptive statement indicating the Bidder’s qualifications and solution to deliver

the supply and services sought under this RFP. This should cover at least the following

topics:

a) MRO / M&E solution providers should have verifiable Airline / Aviation references

for proposed solution of their MRO / M&E Package. Minimum two complete

verifiable MRO / M&E references are to be provided

b) Reference based on individual modules shall not be considered towards MRO /

M&E reference.

c) Experience with the relevant target platform(s) and architectural components.

2 A brief description of the Bidder’s background and organizational history including:

1.1. Years in business;

1.2. Location of offices and local Infrastructure;

1.3. Form of business (i.e., individual, sole proprietor, corporation, partnership, joint

venture, Limited Liability Company, etc.).

3 A personnel roster and resumes of key people who shall be assigned by the Bidder to

perform duties or services under the contract. The resumes shall detail each

individual’s title, education, current position with the Bidder, MRO / M&E Package

Certification and employment history. Bidders must include a brief commentary on

each individual’s experience and suitability related to the services to be performed. The

lead consultants must have sufficient airline experience and completed at least one

MRO / M&E implementation cycles. The top consultant/ project manager must have

sufficient airline experience and completed at least two implementation cycles. Top and

lead consultant to be assigned for the complete project duration and must be full time

onside at the project location in Karachi. Also, the other team members must have

sufficient airline background and functional knowledge accepted by PIAC.

4 Where applicable, a letter from its Principal or Supplier, as the case may be, that it is

authorized to represent, acts as agent, and/or provide the products or services required

under this RFP.

5 A statement as to whether there is any pending litigation against the Bidder; and if such

litigation exists, attach an opinion of counsel as to whether the pending litigation will

impair the Bidder’s performance in a contract under this RFP.

6 Documentation of financial responsibility, financial stability, and sufficient financial

resources to provide the scope of services (and any related equipment) to PIAC in the

volume projected and within the time frames required; said documentation shall

include:

Page 124 of 189


• A description of the Bidder organization’s size, longevity, client base;

• A statement as to whether, in the last ten (10) years, the Bidder has filed (or had

filed against it) any bankruptcy or insolvency proceeding, whether voluntary or

involuntary, or undergone the appointment of a receiver, trustee, or assignee for

the benefit of creditors; and if so, an explanation providing relevant details; and

• Other pertinent financial information by which PIAC may reasonably formulate an

opinion about the relative stability and financial strength of the Bidder. This

information must include the most recent audited financial statement.

• Last 5 years’ earnings in IT Projects.

7 The Proposal should provide the following details of each MRO / M&E client in tabular

form.

• Client Name and Address

• Nature of Assignment

• MRO / M&E Package and list of modules implemented

• Date of Assignment Completion

• Nature of Client’s Business

• Type of Service provided

• Contact Person’s Name and Contact details.

Page 125 of 189


G2 Evaluation

1.0 Evaluation of Bidders

Evaluation process of the bidders involve Technical Evaluation as well as Financial

evaluation. The evaluation is based on data submitted by the bidder and which should

be substantiated with verifiable evidence. PIA may ask the vendors to demonstrate its

functional capability through presentation, with real-time functionality scenario, use case

or scripted simulation.

2.0 Criteria for Technical and Commercial Evaluation of M&E Solution & Contractor

Mandatory Requirements

Sr. No

Attributes Requirements

01 Off-the shelf solution of International Repute Literature/ brochure / catalogue of Product, user manual and technical documents

02 Details of litigation/sub-judice cases (if any) Certificate/ Letter

03 Income tax (NTN), Sales Tax Registration Certificate Provide certificates

04 Web enabled application Compulsory

05 Provision of on line bugs tracking / reporting system Compulsory

06 Search record Functionality Provide efficient Search functionality in all modules

07 Reports Capability to generate multiple reports as per requirement of different modules

08 Upgrades Provide software enhancements, updates & patches in the package. (with no hidden charges)

09 Audited Financial Statements for preceding 3 years Audited financial statements

10 Undertaking of no outstanding claims against PIA Appropriate undertaking

11 Integration with Oracle ERP, and interfacing with Sabre applications, AIMS (Section A5-1).

Compulsory

3.0 Weightage of Technical & Commercial Evaluation

Technical Bid: 70% Commercial Bid: 30%

Technical bids with scores of 70 points and above will be considered responsive and will be

considered for further commercial evaluation.

1- Technical Bid Score: Marks obtained by Firm / 100 * 70 = _______________

2- Commercial Bid Score: M/B * W = _______________

M → Minimum Bid B → The bid W → Weight (30)

Total Score = Technical Bid Score + Commercial Bid Score

_______________________________________________________________________

Note: PIA reserve the right to reject the proposal if any of the above mentioned requirements are not fulfilled.

Page 126 of 189


4.0 Technical Evaluation Performa

A – Business Profile

Sr. No.

Attributes Max

Score

Score Distrib-ution

Requirements

1 Authorized Product dealer/ Partner

4

4 Principal MRO / M&E IT vendor directly participating

3 OEM / Principal provide confirmation about the successful implementation of proposed solution in writing.

1 Authorized dealer/ partner participating

2 Financial Strength 4

4 More than or equal to USD 1 million turnover with MRO / M&E IT services revenue being 80%

3 USD 0.75 to 0.99 million turnover with MRO / M&E IT services revenue being 80% or more

2 USD 0.50 to 0.74 million turnover with MRO / M&E IT services revenue being at least 80% or more

3 Company established (No. of years) as of 30-June-2017.

4

4 15 or more years

3 10 years or more

2 05 years or more

4 Country Presence 3

3 Principal MRO / M&E IT vendor has office in Pakistan

2 Principal MRO / M&E IT vendor has authorized dealer/partner in Pakistan

1 Presence in Region

Total 15

Sections Max Score

Score Obtained

A. Business Profile 15

B. Experience 15

C. Product details 40

D. Composition of team assigned

16

E. Training 04

F. Compliance 10

Total 100

Page 127 of 189


B – Experience

Sr. No.

Attributes Max

Score

Score Distrib-ution

Requirements

5

Successful Full-scale implementations of MRO / M&E IT solution in last 5 years in airlines of PIA size - 30 aircraft.

10

10 More than 5such Implementations

5 More than 3 such Implementations


6

Number of reference able Full-scale Implementations of MRO / M&E IT solution In last 5 years

5

5 10 or more Implementations

3 5-9 Implementations

2-4 Implementations

Total 15

C – Product details

Sr. No.

Attributes Max

Score

Score Distrib-ution

Requirements

7 Compliance of Product with Functional Requirements of RFP

30

30 90%-100% compliance (all modules)

25 80%-90% compliance.


5 70-79 % flexibility.

8 Warranty with Free Maintenance & Operational Support after complete implementation.

10

10 Free for more 3 years or more

5 Free for up to 2 years

3 Free for up to 1 year

Total 40

Page 128 of 189


D – Composition of Team Assigned to Implement MRO / M&E Solution

Sr. No.

Attributes Max

Score

Score Distrib-ution

Requirements

9 Project Manager (PM) experience of MRO / M&E implementation (in airlines of PIA size - 34 aircraft)

4

4 3 or more such MRO / M&E implementations as Project Manager and PMP Certification

2 At least 2 such MRO / M&E implementations as Project Manager and PMP Certification


10 Project Functional Lead (at least 2 resources)

4

4 10 or more years of Solution Delivery Experience

2 Over 7 years of Solution Delivery Experience


11 Project Size Team 4

4 At least 30 Resources of which 75% are functional and the rest technical (systems admin and reports/forms and add-on developers)



12 Experience Level and Relevance of Proposed Team

4

4 High (each resource has at least 5 years of experience) and combined team experience is more than 200 person-years)

3 Moderate (each resource has at least 3 years of experience) and combined team experience is more than 150 person years)

2 Low (each resource has at least 2 years of experience) and combined team experience is more than 100 person-years)


Total 16

Page 129 of 189


E – Training

Sr. No.

Attributes Max

Score

Score Distrib-ution

Requirements

13 Contractor Training Team size made available for training

4 5 Class Room Based Training

1 Online Training

Total 4

F – Compliance

Sr. No.

Attributes Max

Score

Score Distrib-ution

Requirements

14 Extent of Compliance with PIA‘s Suggested Timelines and Payment Terms

10

10 Fully Compliant (both timelines and payment terms)

5 Significantly Compliant (payment terms only)

3 Partially Compliant (timelines only)

Total 10

Page 130 of 189


SECTION H

REQUIREMENTS COMPLIANCE MATRIX

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

31

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H1

G

LO

BA

L R

EQ

UIR

EM

EN

TS

– G

EN

ER

AL

Deta

iled b

elo

w a

re th

e g

lob

al re

quire

ments

applic

ab

le fo

r the e

ntire

solu

tion. C

ontra

cto

rs m

ust p

rovid

e th

eir re

spon

ses in

the “

Resp

on

se” c

olu

mn a

nd p

rovid

e a

dd

itiona

l info

rmatio

n / c

larific

atio

n in

the “

Rem

ark

s” c

olu

mn.

Vendor re

spo

nse m

ust b

e re

stric

ted to

:

Sr. N

o.

Resp

on

se

Rem

ark

s

1.

S

= S

tandard

featu

re a

vaila

ble

M

odule

/ sta

ndard

featu

re o

f the p

roposed s

olu

tion

2.

E

= E

nhancem

ent th

rough A

dd

-on / 3

rd party

utility

D

escrip

tion o

f Add

-on / U

tility a

nd th

e tim

e re

quire

d to

config

ure

/ develo

p / im

ple

ment it.

In s

uch c

ases C

ontra

cto

r has to

ensure

that a

ppro

pria

te c

osts

have b

een in

corp

ora

ted in

th

e C

om

merc

ial P

roposal

3.

N

= N

o / C

annot b

e p

rovid

ed

Nil

In c

ase th

e C

ontra

cto

r does n

ot p

rovid

e a

resp

onse, it w

ill be c

onsid

ere

d a

s “

N”.

The C

ontra

cto

r should

pro

vid

e th

e re

spo

nse b

y fillin

g u

p th

e c

olu

mns "

Resp

on

se" a

nd "

Rem

ark

s" o

nly

. Any c

ha

nges,

such a

s a

dditio

n, d

ele

tion, o

r modific

atio

n o

f row

conte

nts

in th

e R

FP

docum

ent, w

ill be c

onsid

ere

d a

s a

n in

va

lid re

sponse

to th

e R

FP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

32

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - G

EN

ER

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

1

Co

mm

on

Ch

ara

cte

ristic

s

1.1

Com

mon c

hara

cte

ristic

s a

re s

hare

d b

y a

ll are

as o

f the M

RO

/ M&

E S

olu

tion

2

In

teg

ratio

n

2.1

Softw

are

supports

m

odern

“b

est

busin

ess pra

ctic

es”,

with

data

lo

cate

d in

one

in

tegra

ted s

yste

m s

hare

d a

cro

ss a

ll org

aniz

atio

nal u

nits

. Inte

gra

tion w

ith O

racle

E

RP

&

in

terfa

cin

g w

ith S

abre

applic

atio

ns,

& A

IMS

is

pro

vid

ed as part

of

the

offe

red s

olu

tion.

2.2

It w

ill als

o

be

inte

gra

ted

with

fu

ture

m

odule

s

usin

g

the

sam

e

develo

pm

ent

language / p

latfo

rm

3

C

on

figu

ratio

n

3.1

Softw

are

w

ill re

quire

m

inim

um

softw

are

m

odific

atio

n

to

meet

its

busin

ess

require

ments

. It

will

allo

w fo

r easy config

ura

tion to

m

eet

those re

quire

ments

w

ithout c

hangin

g s

oftw

are

code o

r requirin

g A

dd

-ons

4

T

ech

no

log

y In

terfa

ces

4.1

The B

idder s

hould

pro

vid

e s

tandard

applic

atio

n p

rogra

mm

ing in

terfa

ces, to

ols

and

meth

odolo

gie

s

that

allo

w

futu

re

rele

ases

to

accom

modate

in

terfa

ces

with

out

repro

gra

mm

ing.

4.2

A

sta

ndard

appro

ach

to

inte

rfaces

is

availa

ble

to

avoid

m

ultip

le,

uniq

ue

appro

aches fo

r diffe

rent s

yste

ms

4.3

The B

idder w

ill have to

ensure

, at its

ow

n c

ost, a

vaila

bility

of A

PIs

for b

oth

its

pro

posed syste

m as w

ell

as syste

m ru

nnin

g in

P

IAC

. T

he softw

are

should

be

capable

to

in

tegra

te

with

applic

atio

ns

alre

ady

runnin

g

in

PIA

C

thro

ugh

Web

-serv

ices, A

pplic

atio

n P

rogra

mm

ing (A

PIs

), or th

rough d

ata

exports

in a

secure

and

effic

ient m

anner.

4.4

B

idder m

ust e

nsure

to p

rovid

e X

ML

-based A

PIs

where

ver th

ese a

re re

quire

d.

5

U

ser In

terfa

ce

5.1

The s

yste

m w

ill have a

com

mon lo

ok a

nd fe

el a

cro

ss a

ll applic

atio

ns

5.2

Scre

en la

belin

g w

ill be a

vaila

ble

in E

nglis

h

5.3

Onlin

e h

elp

will b

e a

vaila

ble

for a

ll applic

atio

ns a

nd w

ill allo

w fo

r custo

miz

atio

n

5.4

The s

yste

m w

ill be a

ccessib

le u

sin

g s

tandard

pers

onal c

om

pute

r thro

ugh b

row

ser

5.5

Syste

m w

ill allo

w o

penin

g m

ultip

le s

essio

ns

5.6

Syste

m w

ill allo

w fo

r sw

itchin

g b

etw

een d

iffere

nt p

rogra

ms w

ithout firs

t havin

g to

exit fro

m th

e s

yste

m.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

33

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - G

EN

ER

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

5.7

Syste

m w

ill allo

w d

efin

ing n

avig

atio

nal m

enus th

at c

an b

e c

reate

d b

y e

nd

-users

accord

ing to

their jo

b re

quire

ments

5.8

Busin

ess ru

les w

ill be in

corp

ora

ted in

to th

e s

yste

m s

uch th

at th

e ru

les a

re a

pplie

d

at th

e tim

e in

form

atio

n is

ente

red in

to th

e s

yste

m

5.9

The

syste

m

will

have

valid

atio

n

routin

es

/ para

mete

rs

to

identify

erro

rs,

inconsis

tencie

s o

r additio

nal re

quire

ments

at th

e tim

e d

ata

is e

nte

red

6

S

ecu

rity &

Au

tho

rizatio

n

6.1

The syste

m supports

m

ultip

le le

vels

of

security

w

hile

pro

vid

ing

sin

gle

sig

n-o

n

facility

to th

e u

sers

6.2

Indiv

idual fie

lds w

ill be p

rote

cte

d fro

m u

nauth

oriz

ed a

ccess

6.3

Access to

certa

in fu

nctio

ns a

nd d

ata

will b

e p

rote

cte

d u

ntil th

ey a

re a

ppro

ved b

y

PIA

C’s

concern

ed p

olic

y m

akers

6.4

Applic

atio

n s

ecurity

will b

e in

tegra

ted w

ith d

ata

base s

ecurity

. Data

files / ta

ble

s

will o

nly

be a

ccessed th

rough th

e M

RO

/ M&

E; d

irect a

ccess th

rough d

iffere

nt

query

languages w

ill not b

e p

ossib

le

6.5

Tem

pla

tes o

r gro

up fu

nctio

ns w

ill be p

rovid

ed to

facilita

te m

ain

tenance

6.6

Changes

in

assig

nm

ent

(em

plo

yee

transfe

rs)

or

term

inatio

n

/ re

tirem

ent

will

auto

matic

ally

trigger a

revie

w o

f the e

mplo

yee’s

security

priv

ileges

6.7

Com

pre

hensiv

e lo

gs o

f transactio

ns a

nd s

ecurity

incid

ents

will b

e m

ain

tain

ed fo

r auditin

g p

urp

oses. S

yste

m w

ill be c

apable

to m

ain

tain

audit tra

ils a

nd lo

gs

6.8

Syste

m

will

pro

vid

e

auth

oriz

atio

n,

auth

entic

atio

n,

inte

grity

and

non

-repudia

tion

fa

cilitie

s fo

r critic

al tra

nsactio

ns

6.9

Passw

ord

length

and a

ccepta

ble

chara

cte

r com

bin

atio

n a

s p

er in

dustry

sta

ndard

s

are

supporte

d

6.1

0

S

yste

m w

ill allo

w settin

g up of

passw

ord

change fre

quency and th

e num

ber

of

pre

vio

us p

assw

ord

s th

at c

ould

not b

e re

peate

d

6.1

1

S

yste

m w

ill forc

e u

sers

to c

hange th

eir p

assw

ord

s a

fter p

re-d

efin

ed in

terv

als

6.1

2

S

yste

m w

ill allo

w s

ecure

rem

ote

login

and w

ill support d

igita

l sig

natu

re a

nd tim

e

sta

mp, e

tc.

7

R

ep

ortin

g / In

qu

iry

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

34

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - G

EN

ER

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

7.1

The s

yste

m w

ill inclu

de c

om

pre

hensiv

e in

quiry

/ reportin

g to

ols

that a

llow

for e

asy

access to

auth

oriz

ed d

ata

7.2

“Drill d

ow

n” c

apability

to e

xam

ine d

eta

ils w

ill be a

vaila

ble

7.3

It will a

lso b

e p

ossib

le to

cre

ate

reports

that re

flect s

tatu

s a

s o

f a s

pecifie

d p

oin

t in

time

7.4

Sta

ndard

reports

will b

e in

clu

ded to

serv

e a

s m

odels

for c

usto

miz

ed re

portin

g a

nd

to p

rovid

e fo

r basic

functio

nal re

ports

7.5

Report w

izard

s o

r sim

ilar te

chniq

ues w

ill be a

vaila

ble

to g

uid

e u

sers

thro

ugh re

port

cre

atio

n

7.6

The

syste

m

will

be

such

that

reportin

g

activ

ities

do

not

com

pro

mis

e

responsiv

eness o

f the in

tera

ctiv

e s

yste

m

7.7

Reports

w

ill be

form

atte

d

to

prin

t on

local

PC

and

LA

N

atta

ched

prin

ters

, centra

lized h

igh-s

peed p

rinte

rs a

s w

ell a

s o

ver in

tern

et a

nd in

tranet

7.8

It will b

e p

ossib

le to

deliv

er fix

ed re

ports

to u

sers

on a

pre

-dete

rmin

ed s

chedule

to

be re

vie

we

d o

nlin

e, to

be re

tain

ed o

nlin

e o

r to b

e p

rinte

d a

t the u

ser’s

dis

cre

tion

7.9

Syste

m w

ill be able

to

deliv

er

the re

ports

usin

g its

ow

n m

essagin

g /

work

flow

engin

e a

s w

ell a

s P

IAC

’s e

mail s

yste

m, L

otu

s N

ote

s

7.1

0

T

he s

yste

m w

ill be a

ble

to d

em

onstra

te u

sefu

l dem

ogra

phic

and fo

recastin

g

capabilitie

s

7.1

1

T

he s

yste

m w

ill support te

xt-b

ased, p

ara

mete

rized a

nd w

ild-c

ard

searc

hes

7.1

2

S

yste

m w

ill pro

vid

e u

sers

the a

bility

to d

evelo

p a

d h

oc re

ports

at th

eir d

iscre

tion

7.1

3

T

he s

yste

m w

ill inclu

de a

data

dic

tionary

or s

imila

r pro

vis

ion to

allo

w n

on

-technic

al

users

to id

entify

the a

ppro

pria

te d

ata

ele

ments

for in

clu

sio

n in

their re

ports

8

D

ata

An

aly

tic T

oo

ls

8.1

PIA

desire

s d

ecis

ion s

upport to

ols

and in

form

atio

n b

ases th

at a

re fu

lly in

tegra

ted

with

the s

yste

m to

facilita

te s

trate

gic

pla

nnin

g, ta

ctic

al o

pera

tions a

nd o

rganiz

atio

n

wid

e a

naly

sis

– th

ese w

ill be a

vaila

ble

8.2

The s

yste

m w

ill support th

e e

asy m

ovem

ent o

f data

to c

om

mon p

ackaged P

C-

based a

pplic

atio

ns s

uch a

s M

icro

soft O

ffice

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

35

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - G

EN

ER

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

8.3

The s

yste

m w

ill be c

apable

of p

roducin

g “

wh

at if”

scenario

s to

support d

ecis

ion-

makin

g

9

C

om

mu

nic

atio

n

9.1

The s

yste

m w

ill foste

r info

rmatio

n s

harin

g a

t all le

vels

of th

e o

rganiz

atio

n. F

or

exam

ple

, polic

y d

irectiv

es a

nd g

oals

will b

e in

corp

ora

ted in

to th

e b

udget p

lannin

g

pro

cess;

departm

ents

w

ill be

able

to

share

purc

hasin

g

inte

ntio

ns

and

specific

atio

ns

and “b

est b

usin

ess p

ractic

es” w

ill be re

adily

availa

ble

for c

onsulta

tion

9.2

The s

yste

m w

ill pro

vid

e a

sin

gle

pla

ce fo

r users

to q

uic

kly

access in

form

atio

n a

nd

update

s o

n o

rganiz

atio

nal n

ew

s a

nd p

olic

ies

10

F

lexib

ility

10.1

The

syste

m

will

be

easily

re

config

ure

d

to

respond

to

changes

in

busin

ess

pra

ctic

es, p

olic

y d

irectiv

es, o

rganiz

atio

n s

tructu

re, s

tatu

tes a

nd re

gula

tions

10.2

Fle

xib

ility w

ill exte

nd b

oth

to e

nte

rpris

e-w

ide a

s w

ell a

s in

dustry

specific

pra

ctic

es

11

S

yste

m A

vaila

bility

11.1

Overa

ll it will b

e a

hig

hly

availa

ble

solu

tion

11.2

The s

yste

m w

ill be a

vaila

ble

for a

ccess b

y a

uth

oriz

ed p

ers

onnel fro

m a

nyw

here

at

any tim

e o

f the d

ay o

r nig

ht (2

4 x

7 a

vaila

bility

)

11.3

The s

yste

m w

ill be e

qually

usable

from

rem

ote

locatio

ns a

s fro

m th

e H

ead O

ffice

11.4

Web-b

ased a

ccess w

ill be s

upporte

d

12

T

ran

sactio

n T

imin

g

12.1

The s

yste

m w

ill support re

al tim

e o

pera

tions. C

hanges to

data

or th

e s

tatu

s o

f pro

cesses w

ill be im

media

tely

availa

ble

in th

e s

yste

m

12.2

Syste

m opera

tions w

ill not

constra

in th

e busin

ess pro

cesses supporte

d by th

e

syste

m

12.3

The s

yste

m w

ill support e

ffectiv

e d

atin

g fo

r transactio

ns, in

clu

din

g b

oth

futu

re a

nd

retro

activ

e c

hanges. T

he a

uth

ority

for s

uch tra

nsactio

ns w

ill be in

clu

ded in

the

security

capabilitie

s o

f the s

yste

m

12.4

The a

ssig

nm

ent o

f a re

troactiv

e d

ate

will g

enera

te th

e c

hanges re

quire

d to

brin

g

the s

yste

m u

p to

the c

urre

nt d

ate

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

36

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

G

LO

BA

L R

EQ

UIR

EM

EN

TS

- GE

NE

RA

L

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

13

O

nlin

e D

ocu

men

tatio

n a

nd

Tra

inin

g

13.1

The s

yste

m w

ill inclu

de c

usto

miz

able

onlin

e d

ocum

enta

tion a

nd tra

inin

g m

ate

rials

such a

s c

onte

xt-s

pecific

help

, searc

h c

apability

, busin

ess p

rocess d

ocum

enta

tion

and p

rocess m

aps

13.2

Conte

xt s

ensitiv

e h

elp

will in

clu

de:

13.2

.1

M

enu o

ptio

ns

13.2

.2

T

abs

13.2

.3

D

ata

entry

field

s

13.2

.4

B

utto

ns

13.2

.5

Ic

ons

14

S

tora

ge / R

eco

rd R

etrie

val

14.1

Record

colle

ctio

n and re

tentio

n is

an im

porta

nt

org

aniz

atio

nal

require

ment.

The

ability

to e

asily

arc

hiv

e, re

tain

and a

ccess re

cord

s is

require

d

14.2

Record

s re

tentio

n p

rocedure

s w

ill allo

w in

form

atio

n to

be s

tore

d in

a w

ay th

at c

an

be a

ccessib

le in

defin

itely

15

S

yste

m S

ecu

rity

15.1

Syste

m p

rovid

ed is

secure

and m

eets

all s

tandard

security

require

ments

i.e.

Identific

atio

n, A

uth

entic

atio

n, A

uth

oriz

atio

n a

nd In

tegrity

15.2

Syste

m a

llow

s im

ple

menta

tion o

f industry

sta

ndard

security

polic

ies a

nd is

capable

to

evolv

e to

meet s

ecurity

challe

nges

15.3

Deta

ils o

f the p

roposed s

ecurity

tools

is p

rovid

ed

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

37

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H2

G

LO

BA

L R

EQ

UIR

EM

EN

TS

– T

EC

HN

ICA

L

Deta

iled b

elo

w a

re th

e te

chnic

al re

quire

ments

applic

able

for th

e e

ntire

solu

tion. C

ontra

cto

rs m

ust p

rovid

e th

eir re

sponses

in th

e “

Resp

on

se” c

olu

mn a

nd p

rovid

e a

dditio

nal in

form

atio

n / c

larific

atio

n in

the “

Rem

ark

s” c

olu

mn.

Vendor re

spo

nse m

ust b

e re

stric

ted to

:

Sr. N

o.

Resp

on

se

Rem

ark

s

1.

S

= S

tandard

featu

re a

vaila

ble

M

odule

/ sta

ndard

featu

re o

f the p

roposed s

olu

tion

2.

E

= E

nhancem

ent th

rough A

dd

-on / 3

rd party

utility

D

escrip

tion o

f Add

-on / U

tility a

nd th

e tim

e re

quire

d to

config

ure

/ develo

p / im

ple

ment it.

In s

uch c

ases C

ontra

cto

r has to

ensure

that a

ppro

pria

te c

osts

have b

een in

corp

ora

ted in

th

e C

om

merc

ial P

roposal

3.

N

= N

o / C

annot b

e p

rovid

ed

Nil

In c

ase th

e C

ontra

cto

r does n

ot p

rovid

e a

resp

onse, it w

ill be c

onsid

ere

d a

s “

N”.

The C

ontra

cto

r should

pro

vid

e th

e re

spo

nse b

y fillin

g u

p th

e c

olu

mns "

Resp

on

se" a

nd "

Rem

ark

s" o

nly

. Any c

ha

nges,

such a

s a

dditio

n, d

ele

tion, o

r modific

atio

n o

f row

conte

nts

in th

e R

FP

docum

ent, w

ill be c

onsid

ere

d a

s a

n in

va

lid re

sponse

to th

e R

FP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

38

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

1

N

ew

Tech

no

log

y

1.1

The s

yste

m is

desig

ned in

such a

wa

y th

at it e

asily

allo

ws th

e in

corp

ora

tion o

f new

te

chnolo

gie

s, a

s th

ey b

ecom

e a

vaila

ble

2

M

ultip

le E

nviro

nm

en

ts

2.1

The s

yste

m s

upports

multip

le e

nviro

nm

ents

. These e

nviro

nm

ents

are

suffic

iently

is

ola

ted fro

m e

ach o

ther s

o th

at o

pera

tions in

one e

nviro

nm

ent

does n

ot a

ffect

those o

f anoth

er. T

he e

nviro

nm

ents

are

as fo

llow

s:

2.1

.1

P

roductio

n –

all p

roductio

n p

rocessin

g w

ill be p

erfo

rmed in

this

enviro

nm

ent

2.1

.2

D

evelo

pm

ent –

all d

evelo

pm

ent a

ctiv

ities in

clu

din

g u

nit a

nd s

yste

m te

stin

g w

ill be

conducte

d in

this

enviro

nm

ent

2.1

.3

Q

uality

Contro

l / Test –

afte

r all d

evelo

pm

ent, u

nit a

nd s

yste

m te

stin

g h

as b

een

com

ple

ted, th

is e

nviro

nm

ent w

ill be u

sed fo

r User A

ccepta

nce T

estin

g b

efo

re th

e

syste

m is

accepte

d in

to p

roductio

n

2.1

.4

T

rain

ing –

for a

ll in-h

ouse im

ple

menta

tion a

nd p

ost im

ple

menta

tion tra

inin

g

activ

ities

3

S

yste

m P

erfo

rman

ce

3.1

The s

yste

m is

responsiv

e a

nd a

vaila

ble

; it supports

rapid

fail-o

ver o

r redeplo

ym

ent

in th

e e

vent o

f pro

ble

ms o

r pla

nned m

ain

tenance. N

inety

-nin

e p

erc

ent o

f all fa

il-over e

vents

will ta

ke p

lace in

less th

an fiv

e m

inute

s

3.2

Any v

olu

me (b

atc

h) p

rocessin

g w

ill not in

terfe

re w

ith o

nlin

e re

sponsiv

eness o

r availa

bility

3.3

Syste

m a

vaila

bility

figure

s o

f the p

roposed s

olu

tion a

re p

rovid

ed. In

case v

ario

us

com

ponents

have d

iffere

nt v

alu

es, th

ese a

re s

pecific

ally

mentio

ned.

4

A

rch

ive a

nd

Pu

rge

4.1

The s

yste

m s

upports

perio

dic

arc

hiv

al a

nd p

urg

ing o

f unused o

r obsole

te

info

rmatio

n

4.2

Arc

hiv

ed in

form

atio

n is

availa

ble

fo

r his

toric

al

reportin

g in

such a m

anner

that

querie

s

can

be

perfo

rmed

on

arc

hiv

ed

data

usin

g

auto

mate

d

data

re

trieval

functio

ns

4.3

A c

om

ple

te d

ata

arc

hiv

al p

lan is

pro

vid

ed

5

R

eco

very

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

39

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

5.1

The syste

m auto

matic

ally

re

covers

to

th

e la

st

com

ple

te prio

r tra

nsactio

n in

th

e

event o

f a fa

ilure

5.2

The s

yste

m c

learly

indic

ate

s to

the u

ser th

at a

transactio

n fa

iled a

nd th

at it m

ust b

e

re-e

nte

red. R

ecovery

occurs

with

out o

pera

tor in

terv

entio

n

5.3

Contin

gency

and

backup

recovery

pro

cedure

s

with

guara

nte

ed

Serv

ice

Level

Agre

em

ents

(SLA

s) h

ave b

een p

rovid

ed

6

B

acku

p / R

eco

very

an

d R

eo

rgan

izatio

n

6.1

The s

yste

m p

rovid

es fo

r the u

natte

nded d

aily

backup o

f all in

form

atio

n a

nd d

ata

to

a m

edia

that c

an b

e s

tore

d o

ffsite

for d

isaste

r recovery

purp

oses

6.2

Syste

m s

upports

diffe

rent ty

pes o

f backups s

uch a

s:

6.2

.1

F

ull b

ackup

6.2

.2

In

cre

menta

l backup

6.2

.3

O

nlin

e b

ackup

6.2

.4

O

ffline b

ackup

6.3

Backups d

o n

ot p

revent th

e s

yste

m fro

m b

ein

g a

vaila

ble

at a

ll times a

nd d

o n

ot

dis

rupt s

yste

m o

pera

tions

6.4

There

is n

o p

erfo

rmance d

egra

datio

n d

urin

g d

ata

backup

6.5

Data

base re

org

aniz

atio

ns d

o n

ot s

ignific

antly

impair s

yste

m a

vaila

bility

6.6

The c

alc

ula

tion o

f time ta

ken to

backup d

ata

with

respect to

data

siz

e in

cre

ase h

as

been p

rovid

ed.

7

P

rint M

an

ag

em

en

t

7.1

The syste

m pro

vid

es a m

eth

od fo

r m

anagin

g th

e prin

t enviro

nm

ent

for

report

dis

tributio

n s

o th

at re

ports

are

dire

cte

d to

the a

ppro

pria

te p

rint fa

cility

. It cate

rs to

both

hig

h s

peed c

entra

lized p

rintin

g fa

cilitie

s a

s w

ell a

s lo

cal L

AN

-based p

rintin

g

facilitie

s th

at w

ill be e

mplo

yed in

additio

n to

prin

ting o

ver in

tern

et / in

tranet

8

F

allb

ack S

olu

tion

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

40

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

8.1

Syste

m

Should

support

functio

nality

, if

syste

m

or

parts

of

the

syste

m

is

not

opera

tive, a

manual o

r sem

i-manual fa

llback s

olu

tion to

be d

evelo

ped, to

contin

ue

the M

RO

/

M&

E opera

tion.

Afte

r re

sta

rt of

the syste

m.

It m

ust

be possib

le to

update

the s

yste

m a

ccord

ingly

.

9

A

bility

for s

yste

m a

nd

licen

se u

pd

ate

s

9.1

Pro

vid

ed M

RO

/ M&

E P

ackage’s

custo

miz

atio

n o

r modific

atio

n s

hall b

e re

ady fo

r any fu

ture

update

s. T

his

guara

nte

e s

hall a

lso b

e g

iven fo

r any u

nderly

ing s

oftw

are

such a

s D

BM

S, O

pera

ting S

yste

m, N

etw

ork

Managem

ent a

nd o

ther to

ols

.

10

T

ech

no

log

y A

rch

itectu

re

10.1

Recom

mendatio

ns o

f the te

chnolo

gy a

rchite

ctu

re u

nder w

hic

h th

e p

roposed M

RO

/ M

&E

Package w

ill opera

te a

re p

rovid

ed, w

ith th

e fo

llow

ing fe

atu

res p

refe

rence:

10.1

.1

N

-tiere

d

Clie

nt/S

erv

er

arc

hite

ctu

re

incorp

ora

ting

thin

pre

senta

tion

-logic

-clie

nt

com

munic

atin

g w

ith c

lient-n

eutra

l, serv

er-b

ased a

pplic

atio

ns, c

om

munic

atin

g w

ith

the d

ata

base

10.1

.2

T

hin

clie

nt, fo

r rem

ote

users

10.1

.3

A

pplic

atio

ns d

istrib

ute

d a

t serv

ers

locate

d a

t Head O

ffice

10.1

.4

C

entra

lized d

ata

base, lo

cate

d a

t Head O

ffice

10.2

Able

to s

upport d

iffere

nt n

etw

ork

based s

erv

ices / p

roto

cols

such a

s:

10.2

.1

T

CP

/IP

10.2

.2

D

HC

P

10.2

.3

W

INS

10.2

.4

D

NS

10.2

.5

N

etB

EU

I

10.2

.6

LD

AP

10.2

.7

F

TP

10.2

.8

D

LC

10.3

Syste

m is

able

to s

upport o

pen s

pecific

atio

ns fo

r AP

Is / m

iddle

ware

applic

atio

ns

such a

s:

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

41

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

10.3

.1

C

OM

/ DC

OM

10.3

.2

C

OR

BA

10.3

.3

R

MI

10.3

.4

A

LE

10.3

.5

M

Q S

erie

s L

ink

10.3

.6

O

LE

/ CO

M2

10.3

.7

O

DB

C

10.4

It is a

ble

to in

tegra

te w

ith In

tern

et te

chnolo

gie

s s

uch a

s:

10.4

.1

H

TT

P

10.4

.2

X

ML

10.5

Scala

ble

arc

hite

ctu

re is

supporte

d, s

uch a

s:

10.5

.1

S

MP

10.5

.2

M

PP

10.5

.3

C

luste

ring

10.6

While

desig

nin

g th

e te

chnolo

gy a

rchite

ctu

re, th

e fo

llow

ing a

re k

ept u

nder

consid

era

tion:

10.6

.1

S

olu

tion is

scala

ble

with

com

ple

te p

latfo

rm in

dependence w

ithout ty

ing d

ow

n P

IA

to a

sin

gle

pla

tform

10.6

.2

S

olu

tion is

effo

rtlessly

porta

ble

from

one s

yste

m to

anoth

er

10.6

.3

It

pro

vid

es

support

for

diffe

rent

flavors

of

UN

IX;

how

eve

r, it

is

a

tota

lly

inte

ropera

ble

solu

tion

10.6

.4

T

here

is o

pen s

ourc

e s

upport. In

this

conte

xt, th

e c

urre

nt s

cenario

vis

-à-v

is th

e

solu

tion o

ffere

d a

nd th

e fu

ture

roadm

ap a

re p

rovid

ed

10.6

.5

O

ptim

izatio

n o

f licensin

g c

osts

for th

e p

latfo

rm s

oftw

are

10.6

.6

P

IAC

’s exis

ting Local

and W

ide A

rea N

etw

ork

, and m

inim

izatio

n of

Wid

e A

rea

Netw

ork

band

wid

th re

quire

ments

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

42

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

10.6

.7

S

implic

ity o

f Syste

m A

dm

inis

tratio

n a

nd O

pera

tions

10.6

.8

E

ase o

f busin

ess c

ontin

uity

pla

nnin

g a

nd e

xecutio

n

11

S

erv

er H

ard

ware

11.1

The re

com

mended config

ura

tion cate

rs fo

r th

e exis

ting lo

ad as w

ell

as annual

volu

me g

row

th o

f 10

-15%

for th

e n

ext fiv

e y

ears

11.2

The config

ura

tion is

capable

of

reta

inin

g data

fo

r at

least

ele

ven years

(th

at

is,

curre

nt y

ear p

lus te

n y

ears

’ his

toric

al re

cord

)

11.3

The s

olu

tion is

redundant, re

liable

and c

onsis

tently

availa

ble

to a

llow

unin

terru

ptib

le

24x7 o

pera

tions

11.4

The p

roductio

n s

erv

er c

onfig

ura

tion in

clu

des re

dundant (R

AID

5) d

ata

sto

rage a

nd

multip

le p

rocessors

and c

ate

rs fo

r com

patib

ility w

ith P

IA’s

exis

ting L

AN

/ WA

N

enviro

nm

ent

11.5

The

are

as

of

perfo

rmance

and

scala

bility

, re

liability

and

fault

tole

rance

while

re

com

mendin

g S

erv

er c

onfig

ura

tions h

ave b

een ta

ken in

to c

onsid

era

tion

11.6

Perfo

rmance

guara

nte

es

of

the

solu

tion

under

diffe

rent

scenario

s

such

as

concurre

nt

users

durin

g norm

al

work

ing,

durin

g data

backup,

durin

g overlo

ad,

durin

g p

artia

l syste

m fa

ilure

, etc

. have b

een p

rovid

ed

12

S

yste

m a

nd

Netw

ork

Man

ag

em

en

t To

ols

12.1

Suita

ble

S

yste

ms and N

etw

ork

M

anagem

ent

Tools

have been re

com

mended.

These to

ols

will e

nsure

pro

per p

lannin

g, c

onfig

ura

tion, a

nd p

roble

m h

andlin

g o

f IT

resourc

es a

nd s

upport s

uch ta

sks a

s:

12.1

.1

defin

ing, re

solv

ing, a

nd m

anagin

g p

roble

ms

12.1

.2

opera

ting n

etw

ork

s a

nd m

ulti-v

endor s

yste

ms

12.1

.3

dis

tributin

g a

nd m

anagin

g s

oftw

are

and d

ata

12.1

.4

contro

lling o

pera

tions

12.1

.5

pla

nnin

g a

nd m

anagin

g p

erfo

rmance

12.1

.6

adm

inis

terin

g s

ecurity

12.1

.7

m

ain

tain

ing a

sset in

form

atio

n

12.1

.8

pla

nnin

g fo

r the fu

ture

capacity

of s

yste

ms

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

43

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

13

Data

Su

pp

ort

13.1

T

he s

olu

tion w

ill support m

ultip

le d

ata

types –

text, im

age, v

oic

e, e

tc.

13.2

T

he s

yste

m w

ill support d

ata

uplo

ad to

and d

ow

nlo

ad fro

m d

iffere

nt s

yste

ms in

m

ultip

le fo

rmats

13.3

B

esid

es s

imple

uplo

ad / d

ow

nlo

ad

facility

it will a

lso c

om

munic

ate

and s

upport d

ata

in

terc

hange w

ith m

obile

devic

es s

uch a

s:

13.3

.1

cellu

lar p

hones

13.3

.2

handheld

term

inals

13.3

.3

PD

As, e

tc.

13.4

S

yste

m w

ill support o

ther d

evic

es s

uch a

s:

13.4

.1

Scanners

13.4

.2

barc

ode re

aders

13.4

.3

bio

metric

devic

es

13.4

.4

card

readers

13.4

.5

RF

ID d

evic

es, e

tc.

13.5

S

upport fo

r importa

nt m

essagin

g / d

ata

form

ats

/ sta

ndard

s w

ill inclu

de, a

s a

m

inim

um

:

13.5

.1

Airc

raft C

om

munic

atio

n A

ddre

ssin

g a

nd R

eportin

g S

yste

m (A

CA

RS

)

13.5

.2

SIT

AT

EX

13.5

.3

AS

CII

13.5

.4 S

MS

13.5

.5 X

ML

13.5

.6 S

pec 2

010

13.5

.7 S

1000D

13.5

.8 M

S-O

ffice

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

44

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

13.5

.9 Lotu

s N

ote

s, e

tc.

14

Syste

m S

ecu

rity

14.1

T

he s

yste

m s

upports

auth

entic

atio

n m

eth

ods th

at w

ill assure

that o

nly

auth

oriz

ed

users

are

able

to a

ccess p

rote

cte

d d

ata

and tra

nsactio

ns

14.2

T

hese in

clu

de s

upport fo

r:

14.2

.1

dig

ital s

ignatu

res

14.2

.2

PK

I infra

stru

ctu

re

15

Web

-en

ab

lem

en

t

15.1

T

he p

roposed s

yste

m is

Inte

rnet re

ady a

nd a

llow

s w

eb

-enable

d a

ccess to

users

fro

m a

nyw

here

acro

ss th

e w

orld

thro

ugh a

web p

orta

l

15.2

T

he s

yste

m is

com

plia

nt w

ith th

e S

erv

ice O

riente

d A

rchite

ctu

re (S

OA

)

16

W

ork

flow

16.1

The

pro

posed

syste

m

will

pro

vid

e

Work

flow

fu

nctio

nality

to

users

by

whic

h

info

rmatio

n a

nd re

quests

could

be a

uto

matic

ally

route

d to

the c

oncern

ed le

vels

for

appro

val

17

O

thers

17.1

Som

e o

ther re

quire

ments

inclu

de:

17.1

.1

S

upportin

g m

ulti-c

urre

ncy

17.1

.2

S

upportin

g u

ser d

efa

ults

17.1

.3

S

upportin

g u

ser d

efin

ed s

cre

ens

17.1

.4

S

upportin

g m

ultip

le d

ate

form

ats

17.1

.5

S

upportin

g u

ser d

efin

ed fie

lds

17.1

.6

S

chedulin

g o

f jobs fo

r unatte

nded o

pera

tions

17.1

.7

M

ain

tain

ing e

ffectiv

e d

ate

s o

f maste

r file d

ata

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

45

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H3

G

LO

BA

L R

EQ

UIR

EM

EN

TS

– O

TH

ER

S

Deta

iled b

elo

w a

re o

the

r glo

bal re

qu

irem

ents

applic

able

for th

e e

ntire

solu

tion. C

ontra

cto

rs m

ust p

rovid

e th

eir re

spo

nses in

the “

Resp

on

se” c

olu

mn a

nd p

rovid

e a

dd

itiona

l info

rmatio

n / c

larific

atio

n in

the “

Rem

ark

s” c

olu

mn.

Vendor re

spo

nse m

ust b

e re

stric

ted to

:

Sr. N

o.

Resp

on

se

Rem

ark

s

1.

S

= S

tandard

featu

re a

vaila

ble

M

odule

/ sta

ndard

featu

re o

f the p

roposed s

olu

tion

2.

E

= E

nhancem

ent th

rough A

dd

-on / 3

rd party

utility

D

escrip

tion o

f Add

-on / U

tility a

nd th

e tim

e re

quire

d to

config

ure

/ develo

p / im

ple

ment it.

In s

uch c

ases C

ontra

cto

r has to

ensure

that a

ppro

pria

te c

osts

have b

een in

corp

ora

ted in

th

e C

om

merc

ial P

roposal

3.

N

= N

o / C

annot b

e p

rovid

ed

Nil

In c

ase th

e C

ontra

cto

r does n

ot p

rovid

e a

resp

onse, it w

ill be c

onsid

ere

d a

s “

N”.

The C

ontra

cto

r should

pro

vid

e th

e re

spo

nse b

y fillin

g u

p th

e c

olu

mns "

Resp

on

se" a

nd "

Rem

ark

s" o

nly

. Any c

ha

nges,

such a

s a

dditio

n, d

ele

tion, o

r modific

atio

n o

f row

conte

nts

in th

e R

FP

docum

ent, w

ill be c

onsid

ere

d a

s a

n in

va

lid re

sponse

to th

e R

FP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

46

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - O

TH

ER

S

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

1

D

BM

S A

ND

DA

TA

BA

SE

AD

MIN

IST

AT

ION

TO

OL

S

1.1

Data

base s

chem

a d

efin

ition, m

anagem

ent, q

uery

and re

portin

g fa

cilitie

s p

rovid

ed

1.2

His

toric

al tra

nsactio

ns w

ill be m

ain

tain

ed b

y th

e D

BM

S. F

acilitie

s fo

r revie

win

g

transactio

ns,

multip

le

transactio

n

roll

back

and

transactio

n

log

reportin

g

are

availa

ble

1.3

Data

base u

pdate

facilitie

s in

clu

de fe

atu

res s

uch a

s th

e u

se o

f work

ing c

opie

s a

nd

sta

tus re

portin

g o

n q

uery

and u

pdate

opera

tions.

1.4

The s

yste

m p

rovid

es lo

ckin

g m

echanis

ms fo

r update

and d

ele

tes o

pera

tions.

1.5

The s

yste

m m

ain

tain

s c

oncurre

nt c

ontro

l mechanis

ms to

ensure

the c

orre

ctn

ess o

f tra

nsactio

ns a

nd to

dete

ct a

nd re

solv

e d

eadlo

cks o

n th

e n

etw

ork

.

1.6

The s

yste

m s

upports

auth

oriz

atio

n lis

ts a

nd g

roups fo

r cre

ate

, read, u

pdate

and

dele

te

1.7

There

is a

pro

vis

ion o

f on

-line fa

cilitie

s to

manage tra

nsactio

ns a

nd o

vera

ll on

-line

syste

m p

erfo

rmance.

1.8

The s

yste

m p

rovid

es u

sers

and a

pplic

atio

ns w

ith d

istrib

utio

n in

dependence. U

sers

do n

ot n

eed to

know

whe

re d

ata

base o

bje

cts

are

locate

d.

1.9

The syste

m opera

tes in

a dis

tribute

d enviro

nm

ent

where

diffe

rent

nodes of th

e

netw

ork

run a

t diffe

rent fu

nctio

nal le

vels

.

1.1

0

T

he s

yste

m h

as th

e a

bility

to a

uto

matic

ally

recover a

nd re

sto

re th

e d

ata

base fu

lly

to th

e la

st c

onsis

tent s

tate

afte

r a m

edia

failu

re.

1.1

1

T

he a

bility

to n

otify

users

as to

what tra

nsactio

ns w

ere

bein

g p

rocessed b

ut n

ot

writte

n to

the d

ata

base d

urin

g a

cra

sh is

availa

ble

.

1.1

2

T

he s

yste

m h

as c

heckpoin

t facilitie

s a

nd th

e c

apability

to ro

ll back / u

ndo to

any

one c

heckpoin

t.

1.1

3

T

he s

yste

m w

ill contin

ue to

be a

vaila

ble

to u

sers

durin

g a

ny b

ackup p

rocess o

r alte

ratio

n o

f the d

ata

base s

chem

a’s

and d

efin

itions.

1.1

4

T

he s

yste

m w

ill support o

ne

-to-o

ne, o

ne-to

-many a

nd m

any-to

-one re

latio

nship

s.

1.1

5

T

he s

yste

m is

capable

of w

ork

ing in

a m

ulti-tie

r enviro

nm

ent, a

nd p

rovid

es th

e

appro

pria

te to

ols

for p

artitio

nin

g th

e lo

catio

n o

f the p

rocessin

g. A

ll tunin

g w

ill be

independent to

the u

ser.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

47

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - O

TH

ER

S

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

1.1

6

A

ll info

rmatio

n in

the d

ata

base is

repre

sente

d a

s v

alu

es in

the ta

ble

.

1.1

7

N

ull

valu

e support

(as opposed to

em

pty

chara

cte

r strin

gs,

bla

nk chara

cte

rs or

zero

) is a

vaila

ble

for a

ll data

types.

1.1

8

D

ata

base re

covery

will b

e m

ade in

min

imum

accepta

ble

dow

ntim

e. A

ccepta

ble

dow

ntim

e w

ill be n

egotia

ted a

nd a

gre

ed u

pon

1.1

9

D

BM

S h

as a

support fo

r ELT

1.2

0

D

BM

S h

as s

upport fo

r SA

N s

tora

ge a

nd c

luste

r enviro

nm

ent

1.2

1

Load b

ala

ncin

g a

nd fa

ilover a

re s

upporte

d to

min

imiz

e d

ow

n tim

e

1.2

2

D

BM

S w

ill support

DR

site

s and auto

matic

sta

ndby config

ura

tions.

It

will

be

capable

of o

pera

ting in

the D

R e

nviro

nm

ent a

nd s

upport s

ynchro

nous a

s w

ell a

s

asynchro

nous d

ata

replic

atio

n a

t rem

ote

DR

site

1.2

3

D

BM

S w

ill support la

rge a

mounts

of d

ata

in te

rra b

yte

s

1.2

4

D

BM

S w

ill have s

upport fo

r transm

issio

n o

f data

from

oth

er n

ew

syste

ms a

s w

ell

as e

xitin

g le

gacy s

yste

ms

1.2

5

It w

ill support lib

rarie

s to

enable

backup o

n ta

pe a

nd d

isk d

rives

1.2

6

It h

as s

upport n

ew

firew

alls

and n

-tier n

etw

ork

arc

hite

ctu

re

1.2

7

It w

ill support O

LA

P, O

LT

P a

nd D

SS

syste

ms

2

A

PP

LIC

AT

ION

DE

VE

LO

PM

EN

T T

OO

LS

2.1

The p

roposed s

olu

tion h

as a

built-in

4G

L d

evelo

pm

ent e

nviro

nm

ent to

ol s

et

3

Q

UE

RY

AN

D R

EP

OR

T G

EN

ER

AT

OR

TO

OL

S

3.1

The re

port g

enera

tor fu

nctio

nality

inclu

des a

schedulin

g o

r pro

ductio

n p

rocess fo

r ro

utin

e re

portin

g

3.2

The re

port g

enera

tor fu

nctio

nality

supports

Stru

ctu

red Q

uery

Language (S

QL)

3.3

It als

o

supports

in

dustry

sta

ndard

re

port

genera

tors

such

as

Cry

sta

l R

eports

, B

usin

ess O

bje

cts

, etc

.

3.4

Report g

enera

tor h

as fo

rmattin

g a

nd s

tatis

tical c

apabilitie

s s

uch a

s:

3.4

.1

A

vera

gin

g

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

48

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - O

TH

ER

S

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

3.4

.2

M

ulti-le

vel s

ub-to

talin

g

3.4

.3

P

erc

ent c

hange c

om

paris

ons

3.4

.4

S

tandard

math

em

atic

al o

pera

tions

3.4

.5

F

inancia

l calc

ula

tions

3.5

Genera

ted re

ports

are

able

to b

e s

aved in

severa

l outp

ut fo

rmats

, such a

s:

3.5

.1

M

S W

ord

3.5

.2

M

S E

xcel

3.5

.3

T

ext

3.5

.4

P

DF

3.5

.5

H

TM

L

3.5

.6

X

ML

4

IN

TE

RIM

SE

RV

ER

S

4.1

Specific

atio

ns a

re p

rovid

ed fo

r inte

rim s

erv

ers

that w

ill be u

sed fo

r MR

O / M

&E

config

ura

tion, a

dd

-on s

oftw

are

develo

pm

ent, u

ser tra

inin

g, e

tc.

4.2

All n

ecessary

hard

ware

com

ponents

are

als

o p

rovid

ed

4.3

The c

onfig

ura

tion o

f these m

achin

es w

ill support th

e n

um

ber o

f users

as s

pecifie

d

in th

e p

lan.

5

3

RD P

AR

TY

SO

FT

WA

RE

5.1

All

require

d

3rd

party

softw

are

, opera

ting

syste

ms,

syste

m

managem

ent

and

monito

ring to

ols

, backup and re

covery

softw

are

, data

base adm

inis

tratio

n to

ols

, dis

aste

r re

covery

and busin

ess contin

uity

to

ols

, A

PIs

/

inte

rfaces,

etc

. w

ill be

made availa

ble

, docum

ente

d,

desig

ned,

imple

mente

d and opera

tional

to m

eet

PIA

C’s

require

ments

in th

e p

roposed M

RO

/ M&

E s

olu

tion.

5.2

A com

ple

te solu

tion in

all

respects

has been offe

red to

P

IA – dela

ys or

costs

aris

ing o

ut o

f any s

hortc

om

ing w

ill be b

orn

e b

y th

e C

ontra

cto

r.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

49

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H4

FU

NC

TIO

NA

L R

EQ

UIR

EM

EN

TS

– M

RO

/ M&

E S

OL

UT

ION

Deta

iled b

elo

w a

re th

e te

chnic

al re

quire

ments

applic

able

for th

e e

ntire

solu

tion. C

ontra

cto

rs m

ust p

rovid

e th

eir re

sponses

in th

e “

Resp

on

se” c

olu

mn a

nd p

rovid

e a

dditio

nal in

form

atio

n / c

larific

atio

n in

the “

Rem

ark

s” c

olu

mn.

Vendor re

spo

nse m

ust b

e re

stric

ted to

:

Ve

nd

or

Sc

ore

. R

es

po

nse

R

em

ark

s

4

S =

Sta

nda

rd fe

atu

re a

va

ilable

M

od

ule

/ sta

nd

ard

featu

re o

f the

pro

po

sed

so

lutio

n

3

E =

En

han

cem

ent

Th

e re

qu

ired

fun

ctio

na

lity c

an

be

de

ve

lop

ed

by th

e b

uild

-in 4

GL

or th

e re

po

rt ge

ne

rato

r. Futu

re re

lea

se

s

of th

e p

rovid

ed

syste

m a

re n

ot a

ffecte

d.

2

A =

En

han

cem

ent th

rou

gh A

dd

-on

/ 3rd

pa

rty u

tility

De

scrip

tion

of A

dd

-on

/ Utility

an

d th

e tim

e re

quire

d to

co

nfig

ure

/ de

ve

lop

/ imp

lem

en

t it. In s

uch

ca

se

s

Co

ntra

cto

r ha

s to

ensu

re th

at a

pp

rop

riate

costs

ha

ve

be

en in

co

rpo

rate

d in

the C

om

me

rcia

l Pro

posa

l

0

N =

No

/ Ca

nn

ot b

e p

rovid

ed

N

il

In c

ase th

e C

ontra

cto

r does n

ot p

rovid

e a

resp

onse, it w

ill be c

onsid

ere

d a

s “

N”.

The C

ontra

cto

r should

pro

vid

e th

e re

spo

nse b

y fillin

g u

p th

e c

olu

mns "

Resp

on

se" a

nd "

Rem

ark

s" o

nly

. Any c

ha

nges,

such a

s a

dditio

n, d

ele

tion, o

r modific

atio

n o

f row

conte

nts

in th

e R

FP

docum

ent, w

ill be c

onsid

ere

d a

s a

n in

va

lid re

sponse

to th

e R

FP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

50

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

1.0

F

un

ctio

nal R

eq

uire

men

t co

ncern

ing

Airc

raft E

ng

ineerin

g

Resp

on

se

S/E

/A/N

Rem

ark

1.1

M

PD

Pro

ces

s

❖

Read n

ew

MP

D v

ers

ion

/ auto

mate

d u

plo

ad

❖

Custo

miz

atio

n F

ilter fo

r non-c

usto

miz

ed d

eliv

ery

of M

PD

❖

D

iffere

nce re

port fo

r pre

-& p

ot-re

vis

ion o

f MP

D

❖

MP

D c

usto

miz

atio

n to

genera

te M

ain

tenance P

rog

ram

for fle

et-

wis

e/ta

il num

ber-w

ise

.

❖

Rele

ase c

usto

miz

ed/re

vis

ed M

PD

(OM

P)

to s

erv

ice, a

nd n

otify

the k

ey u

sers

. ❖

D

efin

e M

EL.

1.2

R

elia

bility

Man

ag

em

en

t ❖

R

elia

bility

Re

port, A

/C, C

hapte

r, Engin

e,

Com

ponent

❖

Dis

patc

h R

elia

bility

❖

N

FF

Reports

❖

M

TB

UR

Repla

cem

ents

❖

E

ngin

e, A

PU

perfo

rmance

monito

ring

❖

Mon

itor C

ofM

, CofA

rene

wal &

reportin

g

❖

Mon

itor E

TO

PS

, RV

SM

com

plia

nce

❖

Flig

ht in

cid

ents

, Pilo

t Reports

❖

F

leet u

tilizatio

n re

ports

.

1.3

D

ocu

men

t Man

ag

em

en

t ❖

U

plo

ad O

EM

Ma

nuals

& e

nsure

contin

ue

d u

pdate

d re

vis

ion

sta

tus.

❖

Uplo

ad a

nd re

gis

ter S

B’s

, AD

’s

❖

Revis

e a

ircra

ft manuals

❖

T

echnic

al

Lib

rary

fu

nctio

ns

with

e

-dis

tributio

n

of

docum

ents

❖

M

ain

tain

PIA

Inte

rnal M

anua

ls

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

51

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

1.4

T

ask C

ard

Man

ag

em

en

t ❖

U

plo

ad O

EM

TC

❖

C

reate

/Update

/ modify

TC

❖

In

clu

sio

n / h

yperlin

kin

g o

f rele

vant m

ain

tenance

pro

cedure

/re

fere

nce fro

m A

MM

. ❖

R

ele

ase M

aste

r TC

for s

erv

ice

1.5

M

od

ificatio

n P

rocess

❖

Evalu

ate

& a

ppro

ve S

B, A

D

❖

Cre

ate

Engin

eerin

g O

rder

❖

Sta

tus F

leet M

odific

atio

n

❖

Sta

tus E

ngin

e/ C

om

ponent M

od

ificatio

n

❖

Pla

nnin

g &

sta

ggerin

g F

leet M

odific

atio

ns

❖

Lis

t of p

erfo

rmed S

B’s

❖

C

onfig

ura

tion c

ontro

l

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

52

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

2.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Airc

raft In

du

ctio

n a

nd

Ph

ase o

ut

R

esp

on

se

S/E

/A/N

Rem

ark

2.1

A

ircra

ft maste

r data

❖

C

reate

airc

raft/ e

ngin

e m

aste

r data

❖

C

reate

airc

raft/ e

ngin

e m

aste

r stru

ctu

re &

locatio

ns

2.2

In

itial d

ata

en

try

❖

Initia

l pro

vis

ionin

g, u

plo

ad R

SP

L

❖

Uplo

ad a

nd m

ain

tain

readin

ess lo

g

❖

Uplo

ad A

/C, e

ngin

e, c

om

ponent h

isto

ry

❖

Uplo

ad M

PD

, ME

L

❖

Uplo

ad T

ech-L

og, M

EL s

tatu

s, O

pen

defe

cts

❖

U

plo

ad m

odific

atio

n s

tatu

s

❖

Main

tain

sta

tus/ le

tter c

hecks p

erfo

rmed

❖

Ente

r flow

n flig

ht h

ours

, blo

ck h

ours

, landin

gs c

ycle

s, d

ays

2.3

A

ircra

ft ph

ase o

ut

❖

Cre

ate

Read

iness L

og

❖

Cre

ate

Mo

d S

tatu

s

❖

Cre

ate

Ma

inte

nance S

tatu

s

❖

Cre

ate

Tech-L

og, M

EL s

tatu

s, D

efe

rred D

efe

cts

2.4

E

ng

ine C

han

ge

❖

De-lin

k th

e d

ata

set o

f rem

oved E

ngin

e fro

m th

e a

ircra

ft curre

nt d

ata

and c

reate

report.

❖

Uplo

ad c

om

ple

te d

ata

set o

f the in

sta

lled E

ngin

e a

nd lin

k

it to th

e c

oncern

ed a

ircra

ft data

set.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

53

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

3.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Lin

e M

ain

ten

an

ce

R

esp

on

se

S/E

/A/N

Rem

ark

3.1

L

ine M

ain

ten

an

ce P

lan

nin

g

❖

Long/ m

ediu

m-te

rm p

lannin

g (s

um

mer/w

inte

r/hajj)

❖

Short-te

rm p

lannin

g

❖

Work

load/ c

apacity

pla

nnin

g

❖

Hangar/ A

/C v

isit p

lan

❖

Assig

n W

ork

Package to

Work

Cente

r/ Shift/ in

div

idu

al s

taff

❖

Dis

patc

h s

pare

s, to

ols

, docum

enta

tion to

line s

tatio

n

❖

Pro

vis

ion o

f line s

tatio

ns

❖

Pla

n fo

r Flig

ht C

overa

ge.

3.2

S

ch

ed

ule

d M

ain

ten

an

ce

❖

Bill o

f Work

(BO

W)

❖

Bill o

f Mate

rial (B

OM

)

❖

Neede

d T

ools

and E

qu

ipm

ent

❖

Execute

Work

Package a

nd T

ask C

ard

s

❖

Schedule

Majo

r com

ponent c

hang

e (M

IC)

❖

Rele

ase A

/C to

serv

ice

❖

Shift h

and o

ver

3.3

U

nsch

ed

ule

d M

ain

ten

an

ce

❖

Record

defe

cts

and c

orre

ctiv

e a

ctio

n

❖

Tra

ckin

g o

f defe

rred d

efe

cts

❖

Indic

ate

ME

L ite

ms

3.4

P

ost M

ain

ten

an

ce P

rocess

❖

Update

A/C

, com

ponent re

cord

s

❖

Report p

erfo

rmed ta

sks

❖

Arc

hiv

e T

ask c

ard

s

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

54

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

4.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Cab

in M

ain

ten

an

ce

R

esp

on

se S/E

/A/N

Rem

ark

4.1

M

ain

ten

an

ce P

lan

nin

g

❖

Defin

e/ u

pdate

a m

ain

tenance p

rogra

m fo

r CM

, but a

lso fo

r A/C

exte

rior c

lean

ing.

❖

Defin

e In

stru

ctio

n c

ard

s fo

r CM

❖

Pla

n C

M w

ork

accord

ing th

e m

ain

tenance p

rog

ram

❖

Pla

n c

apacity

accord

ing

to w

ork

load

/main

tenance s

chedule

4.2

C

usto

mer F

eed

back

❖

Inte

rface to

custo

mer c

om

pla

int s

yste

m

❖

Do c

orre

ctiv

e a

ctio

n

❖

Sta

tistic

s a

ccord

ing c

usto

mer fe

edback

4.3

U

nsch

ed

ule

d M

ain

ten

an

ce

❖

Record

defe

cts

from

CB

L o

r inspectio

n a

nd re

port

❖

Tra

ce d

efe

rred d

efe

cts

❖

Indic

ate

ME

L ite

ms

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

55

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

5.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Base M

ain

ten

an

ce

R

esp

on

se S

/E/A

/N

Rem

ark

5.1

B

ase M

ain

ten

an

ce P

lan

nin

g

❖

Long/ m

ediu

m-te

rm c

heck p

lannin

g B

ase M

ain

tenance E

ve

nts

❖

Work

Package M

an

age

ment

❖

Job C

ard

cre

atio

n/ u

pda

te/ re

vis

e

❖

Hangar/ A

/C v

isit p

lan

❖

Work

Load P

lannin

g

❖

Event p

roje

ct p

lann

ing w

ith flo

w c

harts

and m

ile s

tones

❖

Forw

ard

/ Backw

ard

eve

nt p

lannin

g (in

cl. G

antt-C

hart)

❖

Pro

gre

ss m

onito

ring, m

onito

r costs

thru

dashbo

ard

s

❖

Mon

itor c

onsum

ed M

h &

spare

s

5.2

B

ase M

ain

ten

an

ce O

pera

tion

❖

Inte

rface d

efe

rred d

efe

cts

from

LM

❖

Shop flo

or d

ata

colle

ctio

n

❖

Ente

ring s

nags, p

lannin

g re

ctific

atio

n

❖

Shift h

and o

ver

❖

Capacity

Pla

nnin

g

❖

Clo

se lo

op re

pair / v

isib

ility o

f fractio

nal w

ork

offlo

ade

d to

oth

er

shops.

5.3

P

ost M

ain

ten

an

ce P

rocess

❖

Tra

nsfe

r defe

ct to

LM

❖

Update

A/C

config

ura

tion &

counte

rs

❖

Arc

hiv

e d

ocum

ents

❖

Post-C

heck a

naly

sis

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

56

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

6.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Co

mp

on

en

t Overh

au

l

Resp

on

se

S/E

/A/N

Rem

ark

6.1

M

ain

ten

an

ce

Pla

nn

ing

❖

Med

ium

-term

capacity

pla

nnin

g/ S

hop v

isit fo

recast

❖

Main

tena

nce b

acklo

g, p

riority

managem

ent b

ased o

n

airc

raft d

em

and, m

anpow

er a

nd s

tock le

vel

❖

Capacity

/ work

loa

d p

lan

nin

g

❖

Mon

itor c

osts

, monito

r consum

ed M

h &

spare

s

❖

Pla

nnin

g fo

r consum

able

s

❖

LR

U S

tatu

s &

Locatio

n re

vie

w.

6.2

C

om

po

ne

nt M

ain

ten

an

ce

Wo

rk F

low

❖

Work

ord

er / S

hop

-In re

gis

tratio

n

❖

Wok p

ackage c

om

pila

tion

❖

Job Is

suance a

t pro

ductio

n flo

or. (c

lock-in

)

❖

Main

tena

nce E

xecutio

n / p

rogre

ssiv

e s

tatu

s

❖

Defe

ct n

otific

atio

n &

repair

pro

cedure

.

❖

Work

package e

ntry

into

syste

m

❖

Postin

g o

f Mate

rial c

onsum

ed to

work

ord

er

❖

Com

ponent re

lease ta

g

❖

Shop o

ut / c

losure

of w

ork

ord

er C

lock &

clo

ck-o

ut

6.3

S

ho

p S

up

po

rt Fu

nc

tion

s

❖

Pro

cess F

low

for C

ontra

cte

d M

ain

tena

nce.

❖

Com

ponent S

cra

p P

rocess

❖

Com

ponents

requirin

g C

onsum

able

s

❖

Third

-Party

custo

mer c

om

ponents

handlin

g

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

57

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

❖

Shop C

ap

ability

managem

ent &

contro

l

❖

Fra

ctio

nal W

ork

Ord

er p

rocess

❖

Tool S

tore

functio

ns

6.4

C

om

po

ne

nt E

ng

ine

erin

g

❖

Up-to

-date

com

ponent m

ain

tenance m

anuals

. ❖

S

Bs, A

Ds; C

om

ponent m

odific

atio

n p

rocess

❖

Arc

hiv

e te

chnic

al re

cord

s

❖

Defe

ct n

otific

atio

n

❖

Com

ponent re

liability

report

❖

Work

Instru

ctio

n C

ard

cre

atio

n/ u

pd

ate

/ revis

e.

❖

Alte

rnate

Tools

/Mate

rial a

ppro

val

6.5

W

ork

flow

for R

ep

air &

Mo

dific

atio

n s

ho

p

With

pro

gre

ssiv

e m

ove

me

nt o

f wo

rk p

iece

s to

are

as lik

e

Mach

inin

g/ g

rind

ing, W

eld

ing, b

razin

g, H

eat tre

atm

ent, P

recis

ion

measurin

g, M

eta

llogra

phic

inspectio

n / H

ard

ness te

stin

g, S

urfa

ce

treatm

ent, B

ench fittin

g, P

latin

g / p

lasm

a / p

ain

t. Etc

.

6.7

W

ork

sh

op

Eq

uip

me

nt M

ain

ten

an

ce

❖

F

ixe

d e

qu

ipm

ent M

ain

ten

an

ce

Sh

op

❖

T

oo

l / Te

st E

qu

ipm

ent L

oca

l Fab

rica

tion &

app

rova

ls.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

58

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

7.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Co

mp

on

en

t Overh

au

l

Resp

on

se

S/E

/A/N

Rem

ark

7.1

Q

ua

lity A

ss

ura

nc

e (A

ud

it)

❖

De

fine

Au

dit P

lan

/Pro

gra

m

❖

Pre

pa

ring C

he

cklis

t, Re

co

rdin

g a

nd

Fo

llow

up

of N

on

-

Co

mp

lian

ce

s

❖

Co

nd

uct a

nd

Fo

llow

Up

of L

ine S

tatio

n a

nd

Te

ch

nic

al H

an

dlin

g

Age

nts

Au

dit

❖

Un

sch

edu

led

Au

dits

❖

Au

dit R

ep

orts

❖

Eva

lua

tion

an

d R

eco

rd o

f Ap

pro

ve

d V

end

ors

❖

Asse

ssm

en

t of C

ase

s s

ub

mitte

d fo

r Com

pa

ny C

ap

ab

ility L

ist

Ad

ditio

n / E

nha

ncem

en

t

❖

Asse

ssm

en

t and

Re

cord

of C

om

pa

ny A

uth

oriz

atio

ns / L

imite

d

Au

tho

riza

tion

s

7.2

Q

ua

lity A

ss

ura

nc

e (M

ain

ten

an

ce

)

❖

Ra

mp

Inspe

ctio

n o

n flig

hts

rea

dy fo

r de

pa

rture

❖

Sp

ot C

he

cks o

f diffe

ren

t se

ctio

n o

f PIA

En

gin

ee

ring &

Ma

inte

na

nce

❖

Un

sch

edu

led

Ra

mp

Insp

ectio

ns / S

po

t Ch

ecks

7.3

H

um

an

Fa

cto

r / SM

S

❖

SM

S / H

um

an

Fa

cto

r / HS

E re

late

d re

po

rting, a

na

lysis

,

reco

mm

en

datio

ns a

nd im

ple

me

nta

tion

inclu

din

g a

na

lysis

of

Inte

rna

l Aud

it find

ings.

HS

E/S

MS

Ac

tivity

Ha

za

rd &

Ris

k M

an

ag

em

en

t

❖

Su

ppo

rt for H

SE

/SM

S H

aza

rd/R

isk a

ctiv

ity re

gis

tratio

n a

nd

mitig

atio

n c

on

trols

man

age

me

nt.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

59

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

7.4

E

xa

min

atio

n

❖

Scru

tiny o

f rece

ive

d A

pp

lica

tion

s a

nd

Re

co

rd o

f Qu

alific

atio

ns

(Lic

en

se

s a

nd C

om

pan

y A

pp

rova

ls)

❖

Co

nd

uctin

g c

om

pa

ny a

pp

rova

ls e

xa

ms e

xtra

ctin

g p

ap

ers

from

Qu

estio

n D

ata

Ba

nk (Q

DB

)

7.5

C

hie

f En

gin

ee

r Sec

reta

riat

❖

Issu

an

ce

of C

ertific

atio

n A

uth

oriz

atio

n / L

ist o

f Ce

rtifyin

g S

taff

❖

Ap

pro

va

l of v

en

do

rs, th

eir Q

ua

lity M

on

itorin

g a

nd a

ctio

ns a

s a

resu

lt of m

on

itorin

g

❖

Re

co

rd o

f Lim

ited

Au

tho

riza

tion

s is

su

ed

from

Re

gu

lato

ry

Au

tho

rity

❖

Incid

en

ts / D

ela

ys (R

ep

ortin

g to

PC

AA

, inve

stig

atio

ns)

❖

Re

co

rd o

f Lic

en

se

s (F

or S

cru

tiny a

nd R

ene

wa

l from

PC

AA

)

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

60

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

8.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Mate

rial M

an

ag

em

en

t

Resp

on

se

S/E

/A/N

Rem

ark

8.1

M

ate

rial P

lan

nin

g

❖

Uplo

ad re

adin

ess lo

g

❖

Uplo

ad a

nd m

ain

tain

initia

l pro

vis

ionin

g d

ata

❖

Main

tain

Airc

raft s

tructu

re/ lo

catio

n

❖

Main

tain

Mate

rial M

aste

r data

❖

Pla

n c

onsum

able

based

on p

lann

ing p

ara

mete

rs &

past

consum

ptio

n

❖

Mate

rial p

rovis

ion fo

r pla

nne

d m

ain

tenance

❖

Mon

itor c

onsum

ptio

n a

nd s

tock le

vel

❖

Mate

rial re

qu

est fu

nctio

ns

8.2

R

ota

ble

s C

on

trol (L

RU

)

❖

Pla

n L

RU

float

❖

Contro

l lifetim

e

❖

Com

ponent h

isto

ry

❖

Com

ponent tra

ckin

g

❖

Shelf life

/ Enviro

nm

enta

l Cond

itions d

ata

8.3

L

oan

/ Bo

rrow

ing

❖

Adm

inis

ter lo

an o

f parts

/ equip

ment / to

ols

❖

Adm

inis

ter b

orro

win

g o

f parts

/ equip

ment / to

ols

❖

Handle

parts

on e

xchan

ge b

asis

❖

Support c

om

ponent p

oo

ling c

oncept

8.4

C

om

po

ne

nt e

xc

ha

ng

e p

rog

ram

❖

Contra

cts

managem

ent fo

r CE

P/C

SP

.

❖

Work

flow

for e

ntire

CS

P lo

op, w

ith tra

ckin

g a

bility

.

❖

Com

ponent o

ut/in

his

tory

❖

NF

F T

rackin

g

❖

Reportin

g c

apab

ility fo

r com

ponents

in C

SP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

61

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

8.5

C

on

trac

ted

Ma

inte

nan

ce

/ Re

pa

ir Ab

roa

d

❖

The s

tatu

s o

f the c

om

ponent, &

expecte

d re

turn

time.

❖

Repair re

ports

inte

gra

tion to

the c

om

ponent h

isto

ry re

cord

❖

Syste

m update

fo

r scra

p at

repair

ag

ency site

or

repla

cem

ent

com

ponent o

ffer.

❖

Syste

m s

hall m

ain

tain

Perm

anent re

pair a

bro

ad lis

t (PR

A).

8.6

W

arra

nty

man

ag

em

en

t su

pp

ort

❖

Rep

air W

arra

nty

❖

Pu

rch

ase W

arra

nty

❖

Ind

uctio

n W

arra

nty

as p

art o

f airc

raft re

ad

iness lo

g.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

62

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

9.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Bu

sin

ess D

eve

lop

men

t

Resp

on

se

S/E

/A/N

Rem

ark

9.1

C

lien

t Co

ntra

ct

❖

Defin

e C

lient M

aste

r

Agre

em

ent

❖

Defin

e C

lient M

ain

ten

an

ce

Ord

er

❖

Clie

nt C

onta

ct D

eta

ils d

ata

base

9.2

O

rder M

an

ag

em

en

t

❖

Defin

e C

lient O

rder S

yste

m a

ccord

ing to

the c

ontra

ct te

rms

❖

Mon

itor c

lient O

rder P

rogre

ss

❖

Mon

itor M

h &

parts

costs

❖

Mon

itor R

epa

ir abro

ad c

osts

and p

rogre

ss

❖

Ord

er p

rogre

ss in

form

atio

n a

ccessib

le b

y th

e C

lient

9.3

P

rop

osal M

an

ag

em

en

t

❖

Defin

e m

aste

r pro

posal

❖

Sto

re c

usto

miz

ed p

ropo

sal

❖

Mon

itor p

roposal s

ucce

ss

rate

❖

Capab

ility lis

t

9.4

P

rofita

bility

An

aly

sis

(thru

ER

P In

terfa

ce

)

❖

Calc

ula

te c

lient o

rder p

rofita

bility

❖

Calc

ula

te c

om

ple

te c

lient p

rofita

bility

❖

pro

fitability

an

aly

sis

by re

gio

n &

pro

ducts

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

63

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

10.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Po

wer P

lan

t Overh

au

l

Resp

on

se

S/E

/A/N

Rem

ark

10.1

P

rod

uctio

n P

lan

nin

g

❖

Long-te

rm p

lannin

g E

ng

ine/ A

PU

/ Com

ponent s

hop

vis

its

❖

Pro

ductio

n/ c

apacity

pla

nnin

g

❖

Forw

ard

/ Backw

ard

eve

nt p

lannin

g (in

cl. p

roje

ctio

n th

ru G

antt-

Chart)

❖

Cre

ate

/ update

BoW

& B

oM

❖

Engin

e/ m

odule

dis

asse

mble

managem

ent

❖

Engin

e/ m

odule

/ com

ponent b

uild

-up c

ontro

l

❖

Com

ponent S

cra

p p

rocess

❖

Fra

ctio

nal W

ork

(inte

r-shop) p

rocess

❖

Contra

cte

d m

ain

tenance / re

pair a

bro

ad w

ork

flow

❖

Ma

inta

inin

g L

LP

’s h

isto

ry

10.2

E

ng

ine E

ng

ineerin

g

❖

Mod

ificatio

n s

tatu

s d

ashboard

❖

Mod

ificatio

n m

anagem

ent

❖

Update

Engin

e/A

PU

/ LR

U c

ounte

rs &

sta

tus

❖

Update

Engin

e/ A

PU

/ LG

modific

atio

n s

tatu

s.

❖

Cre

ate

/ update

/ revis

e S

hop W

ork

Sheet

❖

Shop F

indin

g R

ep

orts

❖

Update

seria

lize

d c

om

ponents

❖

Arc

hiv

ing o

f technic

al re

cord

s.

❖

Update

/ revis

e O

EM

manuals

10.3

E

ng

ine H

ealth

Mo

nito

ring

❖

In

dig

en

ous s

upp

ort fo

r EH

M.

Or S

upport fo

r EH

M th

rough th

ird-p

arty

inte

rfaced a

pplic

atio

n.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

64

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

10.4

S

ho

p/ W

ork

Pla

ce C

on

trol

❖

Work

cente

r monito

ring

❖

Backlo

g p

riority

managem

ent a

t Work

Cente

r

❖

Mh a

nd M

achin

e h

our re

cord

ing

❖

Tra

ckin

g &

tracin

g p

arts

in th

e s

hop

❖

Engin

e/m

odule

teard

ow

n m

anagem

ent

❖

Multi

sta

ge

com

ponent

routin

g

❖

En

gin

e/A

PU

/LG

main

ten

an

ce W

ork

flow

.

❖

En

gin

e

/ A

PU

T

est

&

QE

C

Bu

ildu

p

sectio

n

wo

rkflo

w.

❖

Lan

din

g G

ear S

ho

p W

ork

flow

.

10.5

B

ud

getin

g &

Fin

an

cia

l Co

ntro

l (thru

ER

P in

terfa

ce)

❖

Budget p

lannin

g fo

r Engin

e/ A

PU

/ Landin

g

Gear

❖

Repair/ o

verh

aul c

ost

contro

l

❖

Mon

itor p

erfo

rmance

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

65

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

11.0

F

un

ctio

nal R

eq

uire

men

ts fo

r To

ols

an

d E

qu

ipm

en

t& S

tan

dard

L

ab

Resp

on

se

S/E

/A/N

Rem

ark

11.1

T

oo

ls M

aste

r data

❖

Defin

e to

ols

, GS

E a

nd fig

ure

s lo

catio

ns &

quantity

❖

Defin

e to

ols

maste

r data

❖

Functio

nality

for re

serv

atio

n, in

-use,

availa

ble

❖

Tra

nsporta

tion o

rder fo

r tools

❖

Sta

tistic

s c

oncern

ing u

tilizatio

n

❖

Main

tena

nce p

lannin

g o

f tools

& re

pair

11.2

C

alib

ratio

n o

f too

ls

❖

Regis

ter to

ols

❖

Schedule

tools

calib

ratio

n

❖

Report c

alib

ratio

n c

om

plia

nce

11.3

S

tan

da

rd L

ab

s F

un

ctio

ns

❖

Too

ls / e

qu

ipm

en

t wo

rk o

rde

r

❖

Ca

libra

tion

ch

eck/a

dju

stm

en

t with

refe

ren

ce

to s

tan

da

rds

❖

Ca

libra

tion

stic

ke

r/ce

rtificate

s

❖

Intim

atio

n to

ow

ne

r tool s

tore

❖

Su

b-c

on

tractin

g fo

r no

-ca

pab

ility ite

ms

❖

Equ

ipm

en

t un

de

r Ca

l trackin

g b

y u

se

r se

ctio

n.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

66

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

C3-1

G

en

era

l Fu

nctio

nal R

eq

uire

men

ts o

f the M

RO

/ M&

E S

yste

m

R

esp

on

se

S/E

/A/N

Rem

ark

1

Ab

ility fo

r Inte

gra

tion

with

ER

P &

inte

rfacin

g w

ith o

ther

Ap

plic

atio

ns

❖

Ora

cle

ER

P s

yste

m c

ontro

ls a

ll majo

r PIA

resourc

es. A

sm

ooth

in

tegra

tion b

etw

ee

n th

e E

RP

, exis

ting a

pplic

atio

n ru

nnin

g in

P

IAC

and th

e M

RO

/ M&

E s

yste

m is

require

d.

➢

T

he fo

llow

ing a

reas fo

r inte

gra

tion a

re h

ighlig

hte

d:

Fin

ancia

l Accountin

g, F

inancia

l Contro

l, Budg

etin

g,

Purc

hasin

g, L

og

istic

, HR

, Tra

inin

g &

Q

ualific

atio

ns/C

ertific

atio

ns

❖

Sab

re A

irCentre

&

S

abre

A

irVis

ion ap

plic

atio

ns are

used in

F

light

pla

nn

ing

&sche

dulin

g.

An

inte

rface

to

MR

O

/ M

&E

S

olu

tion is

req

uire

d a

t min

imum

. ➢

The fo

llow

ing a

reas fo

r inte

rfacin

g a

re s

pecific

ally

hig

hlig

hte

d;

Schedule

/Slo

t/Fle

et

managem

ent,

Flig

ht

Pla

n/M

ovem

ent

manager, A

CA

RS

managem

ent.

2

MIS

& R

ep

ortin

g

❖

Key P

erfo

rmance In

dic

ato

rs to

be re

porte

d fo

r all m

ajo

r sectio

ns in

PIA

Engin

ee

ring o

n re

gu

lar b

asis

. The K

PI to

be

defin

ed b

y P

IA.

❖

The P

IA E

ngin

eerin

g M

anag

em

ent s

hall g

et re

gula

r rep

orts

concern

ing th

e re

gula

r and u

n-re

gula

r opera

tion.

3

Th

e S

yste

m w

ill co

ntro

l the d

ay-b

y-d

ay w

ork

❖

A

ll work

packages, ta

sks a

nd b

usin

ess a

ctiv

ities w

ill be in

itiate

d

and c

ontro

lled b

y th

e s

yste

m.

❖

Subsequ

ently

all L

abels

, Ord

ers

and C

ertific

ate

s a

re p

rinte

d b

y

the S

yste

m.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

67

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

4

Drill d

ow

n o

ptio

n a

nd

flexib

le re

po

rting

❖

F

rom

the to

p to

the b

otto

m it m

ust b

e p

ossib

le to

genera

te

reports

with

more

deta

ils if re

quire

d.

❖

Besid

e re

gu

lar u

sed re

ports

, a fle

xib

le re

port g

enera

tor fo

r occasio

nal u

se.

❖

Tra

cin

g o

f info

rmatio

n a

long a

logic

al p

ath

. ❖

D

ashbo

ard

for m

anagem

ent / p

lanners

for liv

e s

tatu

s o

f fleet

and m

ain

tenance in

pro

gre

ss &

oth

er re

late

d in

form

atio

n.

5

Fle

xib

ility

c) O

rganiz

atio

nal c

han

ges s

hall b

e e

asily

addre

ssed in

the

Syste

m b

y re

-config

ura

tion.

d)

In c

ase o

f outs

ourc

ing p

arts

of th

e p

roductio

n (e

.g. B

ase

Main

tena

nce, E

ngin

e O

H), th

e s

yste

m s

hall b

e a

ble

to b

e

custo

miz

ed a

ccord

ingly

.

6

Ad

va

nc

ed

MR

O / M

&E

Co

nc

ep

ts

❖ S

upport e

-Tech-L

og / w

-Cabin

-Log

❖

Airp

lan

e / E

ngin

e H

ea

lth m

onito

ring,

❖

Analy

tics

Tools

fo

r pre

dic

tive

&

pre

scrip

tive

defe

ct

managem

ent/ tro

uble

sh

ootin

g

❖

Futu

re u

pgra

da

bility

for Io

T s

olu

tions.

❖

RF

ID

❖

Sm

art c

ard

❖

B

arc

ode b

ase

d

❖

Oth

er e

merg

ing tre

nds in

avia

tion (d

escrib

e in

Rem

ark

s

colu

mn)

❖

Support fo

r mobile

technolo

gy in

clu

din

g c

ell p

hones, ta

ble

ts &

iP

ads.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

68

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

7

Req

uire

d In

terfa

ces o

f the n

ew

MR

O / M

&E

Sys

tem

❖

The A

ircra

ft log d

ata

(Fh, C

ycle

s) e

ntry

at o

ne

locatio

n in

PIA

. T

he M

RO

/ M&

E S

yste

m s

hall h

ave a

n in

terfa

ce fo

r a re

al-tim

e

data

uplo

ad. A

CA

RS

shall b

e u

se

d w

here

possib

le.

❖

The A

ircra

ft Rota

tion P

lan s

hall b

e a

va

ilable

on

line fo

r Pla

nnin

g

sectio

ns o

f PIA

Engin

eerin

g, s

ho

win

g in

tera

ctiv

ely

the p

lan

ned

A

/C a

ssig

nm

ents

to ro

ute

s a

nd th

e s

lots

main

tenance e

ve

nts

.

❖

The C

om

merc

ial F

light S

chedule

shall b

e o

nlin

e a

vaila

ble

for

long a

nd m

ediu

m-te

rm p

lan

nin

g.

❖

PIA

Opera

tions w

ill monito

r opera

tional p

erfo

rmance a

nd A

/C

dis

patc

h re

liability

. An o

nlin

e in

terfa

ce w

ill pro

vid

e th

e d

ata

for

PIA

Engin

eerin

g.

❖

P

IA

Fin

ance

is

responsib

le

for

the

Fin

ancia

l B

udget

and

Fin

ancia

l A

ccountin

g.

The

data

are

share

d

with

P

IA

Engin

eerin

g o

n o

nlin

e b

asis

for p

erfo

rmance m

onito

ring a

nd

pla

nnin

g p

urp

oses.

❖

Auto

mate

d u

plo

ad o

f all O

EM

manuals

, such a

s A

MM

, IPC

, S

RM

, EM

M, T

SM

and o

thers

usin

g th

e S

1000

D s

tandard

s

❖

Auto

matic

uplo

ad o

f SB

’s, A

D’s

,

❖

Mate

rial M

aste

r data

shall b

e u

p-lo

aded u

sin

g th

e A

MT

OS

S

and S

PE

C200

0 d

ata

sta

ndard

s

❖

Uplo

ad o

f Vendor c

apability

list, p

rice lis

t, availa

bility

sta

tus a

nd

oth

ers

(ER

P)

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

69

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

❖

E

lectro

nic

exch

ange o

f agre

em

ents

, purc

hase o

rder, d

eliv

ery

/ re

pair

sta

tus,

invoic

e,

pa

ym

ents

. S

upporte

d fo

rmats

shall

be

ED

I, X

ML,

SP

EC

2000

and

oth

ers

. A

n

inte

rnatio

na

l B

2B

com

munic

atio

n

pla

tform

to

be

inte

rfaced

for

exchangin

g

pro

cure

ment a

nd re

pair s

tatu

s in

form

atio

n.

❖

The n

ew

Syste

m s

hall s

upport a

WE

B P

orta

l to p

rovid

e m

ajo

r in

form

atio

n a

nd d

ata

for p

roductio

n. It is

the ta

rget, to

avoid

tim

e

consum

ing

and

outd

ate

d

paper

base

d

dis

tributio

n

of

info

rmatio

n.

❖

The s

yste

m to

be re

ady fo

r RF

ID a

pplic

atio

ns to

be in

tegra

ted.

Als

o,

the P

IAC

em

plo

ye

e ID

card

to

be re

ad fo

r em

plo

yee

ackno

wle

dgem

ent.

❖

T

he w

ork

ing p

apers

such a

s J

ob C

ard

s a

nd p

arts

tags to

be

prin

ted w

ith b

arc

ode. B

ar c

ode re

aders

to b

e in

tegra

ted fo

r m

an h

our re

cord

ing a

nd

parts

trackin

g.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

70

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H5

S

ER

VIC

ES

RE

QU

IRE

ME

NT

S

Deta

iled b

elo

w a

re th

e s

erv

ices re

quire

ments

. Contra

cto

rs m

ust p

rovid

e th

eir re

sponses in

the “

Resp

on

se” c

olu

mn a

nd

pro

vid

e a

dditio

nal in

form

atio

n / c

larific

atio

n in

the “

Rem

ark

s” c

olu

mn.

Vendor re

spo

nse m

ust b

e re

stric

ted to

:

Sr. N

o.

Resp

on

se

Rem

ark

s

1.

Y

= Y

es

Deta

ils o

f how

the s

erv

ices w

ould

be p

rovid

ed

2.

N

= N

o / C

annot b

e p

rovid

ed

Nil

In c

ase th

e C

ontra

cto

r does n

ot p

rovid

e a

resp

onse, it w

ill be c

onsid

ere

d a

s “

N”.

The C

ontra

cto

r should

pro

vid

e th

e re

spo

nse b

y fillin

g u

p th

e c

olu

mns "

Resp

on

se" a

nd "

Rem

ark

s" o

nly

. Any c

ha

nges,

such a

s a

dditio

n, d

ele

tion, o

r modific

atio

n o

f row

conte

nts

in th

e R

FP

docum

ent, w

ill be c

onsid

ere

d a

s a

n in

va

lid re

sponse

to th

e R

FP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

71

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

SE

RV

ICE

S R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

1

IM

PL

EM

EN

TA

TIO

N

1.1

An Im

ple

menta

tion S

trate

gy h

as b

een s

ubm

itted th

at c

overs

:

1.1

.1

In

sta

llatio

n o

f the In

terim

Serv

er(s

) inclu

din

g th

e O

pera

ting S

yste

m.

1.1

.2

In

sta

llatio

n o

f all s

upplie

d A

pplic

atio

n s

oftw

are

, D

BM

S s

oftw

are

, Develo

pm

ent /

Query

and R

eport W

riter / D

ata

base A

dm

inis

tratio

n T

ools

and a

ny o

ther re

quire

d

Utilitie

s, o

n th

e In

terim

Serv

er(s

).

1.1

.3

In

sta

llatio

n o

f all s

upplie

d A

pplic

atio

n s

oftw

are

, D

BM

S s

oftw

are

, Develo

pm

ent /

Query

and R

eport W

riter / D

ata

base A

dm

inis

tratio

n T

ools

and a

ny o

ther re

quire

d

Utilitie

s, o

n th

e P

erm

anent S

erv

ers

.

1.1

.4

Im

ple

menta

tion o

f Data

base s

ecurity

featu

res

1.1

.5

Develo

pm

ent o

f Busin

ess R

equire

ment D

ocum

ent fo

r each fu

nctio

nal a

rea w

hic

h

maps th

e b

usin

ess p

rocess fo

r the p

ara

mete

rizatio

n / c

onfig

ura

tion o

f MR

O / M

&E

P

ackage.

T

his

docum

ent

will

be

based

on

PIA

C’s

re

engin

eere

d

busin

ess

pro

cesses p

rovid

ed b

y P

IA.

1.1

.6

D

evelo

pm

ent o

f busin

ess c

ase s

cenario

s

1.1

.7

P

ara

mete

rizatio

n o

f supplie

d S

oftw

are

i.e. th

e c

onfig

ura

tion o

f applic

atio

n s

oftw

are

via

sele

ctio

n of

in-b

uilt

valu

es,

settin

g up of

table

s,

etc

. to

m

eet

the busin

ess

require

ments

.

1.1

.8

S

oftw

are

m

odific

atio

ns,

where

re

quire

d,

to

supplie

d

Applic

atio

n

softw

are

and

develo

pm

ent o

f exte

nsio

ns a

nd / o

r module

s to

meet th

e b

usin

ess re

quire

ments

.

1.1

.9

In

tegra

tion

with

P

IAC

’s

oth

er

applic

atio

ns

such

as

Ora

cle

E

RP

, S

abre

applic

atio

ns, A

IMS

, PIA

website

, etc

.

1.1

.10

D

esig

n a

nd d

evelo

pm

ent o

f custo

miz

ed re

ports

, scre

ens, w

ork

flow

s, e

tc. T

here

is

no u

pper lim

it to th

e c

usto

miz

atio

n th

at w

ill be u

nderta

ken

1.1

.11

D

esig

n, d

evelo

pm

ent a

nd in

itial s

et u

p o

f data

bases.

1.1

.12

T

estin

g S

trate

gy. U

nit, In

tegra

tion a

nd S

yste

m te

stin

g p

rior to

User A

ccepta

nce

testin

g.

1.1

.13

D

ata

mig

ratio

n activ

ities.

These in

clu

de pre

para

tion of

data

mig

ratio

n s

trate

gy,

and u

nderta

kin

g d

ata

mig

ratio

n a

ctiv

ities a

s p

er s

ectio

n D

, sub

-sec: 3

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

72

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

SE

RV

ICE

S R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

1.1

.14

D

esig

n a

nd im

ple

menta

tion o

f Onlin

e a

nd B

atc

h jo

b o

pera

tional p

rocedure

s u

ntil

imple

menta

tion is

successfu

lly c

om

ple

ted a

t all lo

catio

ns.

1.1

.15

P

rogre

ss re

portin

g o

n C

ontra

cto

r rela

ted a

ctiv

ities.

1.1

.16

Q

uality

Assura

nce fo

r Contra

cto

r rela

ted a

ctiv

ities.

1.1

.17

A

ny

oth

er

tasks

require

d

in

successfu

l deliv

ery

of

the

supplie

d

pro

ducts

and

serv

ices.

1.2

Airlin

e in

dustry

specific

rapid

imple

menta

tion te

mpla

tes w

ill be u

tilized to

ensure

quic

k im

ple

menta

tion. D

eta

ils o

f such te

mpla

tes a

re s

ubm

itted w

ith th

e T

echnic

al

Pro

posal

1.3

A d

eta

iled c

om

pre

hensiv

e p

roje

ct p

lan is

pre

pare

d a

nd s

ubm

itted a

s a

part o

f the

pro

posal.

1.4

A d

eta

iled p

roje

ct o

rganiz

atio

n s

tructu

re h

as b

een s

ubm

itted:

1.4

.1

Id

entify

ing th

e s

pecific

indiv

iduals

who w

ould

be a

ssig

ned d

iffere

nt ta

sks o

f this

pro

ject.

1.4

.2

Assig

n a

full-tim

e P

roje

ct M

anager to

manage th

is P

roje

ct. T

his

pers

on m

ust b

e

from

the lis

t of L

ead C

onsulta

nts

subm

itted b

y th

e C

ontra

cto

r in re

sponse to

the

EO

I. He / s

he m

ust h

ave th

e e

xperie

nce o

f imple

mentin

g th

e p

roposed M

RO

/

M&

E S

OLU

TIO

N in

at le

ast tw

o a

irlines. H

is/h

er d

eta

iled C

V in

clu

din

g e

xperie

nce

of

managin

g

MR

O

/ M

&E

IT

and

oth

er

Pro

jects

, M

RO

/

M&

E

IT

Package

Certific

atio

n, if a

ny, th

e n

um

ber o

f MR

O / M

&E

pro

jects

managed a

nd th

e n

um

ber

of y

ears

on e

ach p

roje

ct, e

tc. m

ust b

e s

ubm

itted a

long w

ith th

e P

roposal.

1.4

.3

Conta

inin

g a pers

onnel

roste

r conta

inin

g deta

iled re

sponsib

ilities of

Contra

cto

r sta

ff assig

ned

to

perfo

rm

dutie

s

or

serv

ices.

T

he

roste

r in

clu

des

estim

ate

d

num

ber o

f hours

to b

e w

ork

ed o

n th

e p

roje

ct fo

r each p

ers

on b

roken d

ow

n in

diffe

rent p

hases o

f the

pro

ject c

learly

identify

ing th

e s

tart a

nd e

nd d

ate

s fo

r each

phase.

T

hese

sta

ff m

em

bers

are

fro

m

the

list

of

imple

mente

rs

pro

vid

ed

in

response to

the E

OI.

1.4

.4

S

ubstitu

tes to

the n

om

inate

d s

taff w

ill have q

ualific

atio

ns e

quiv

ale

nt to

or b

ette

r th

an th

ose w

ho w

ill be re

pla

ced.

1.5

The C

ontra

cto

r must p

rovid

e, b

y p

hase, th

e p

roposed n

um

ber o

f pers

onnel to

be

based o

n-s

ite a

t PIA

C’s

pre

mis

es, a

nd s

pace a

nd o

ther lo

gis

tical re

quire

ments

to

be p

rovid

ed b

y P

IA d

urin

g Im

ple

menta

tion

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

73

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

SE

RV

ICE

S R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

1.6

T

he C

ontra

cto

r’s im

ple

menta

tion p

lan ta

kin

g due consid

era

tion to

th

e busin

ess

prio

rity a

reas a

nd a

pplic

atio

ns.

1.7

A s

yste

m tu

rnover p

lan w

ill be d

evelo

ped th

at w

ill indic

ate

the c

onditio

nal c

riteria

re

quire

d to

fully

turn

over th

e d

aily

opera

tion o

f the s

yste

m to

PIA

technic

al s

taff.

At a

min

imum

, the tu

rnover p

lan w

ill inclu

de th

e s

tate

of re

adin

ess re

quire

d fo

r syste

m tu

rnover a

nd a

ll require

d d

ocum

enta

tion.

1.8

Durin

g

syste

m

insta

llatio

n,

the

Contra

cto

r w

ill evalu

ate

perfo

rmance

facto

rs

inclu

din

g, b

ut n

ot lim

ited to

, transactio

n v

olu

mes, re

sponse tim

es, C

PU

utiliz

atio

n,

and in

put / o

utp

ut a

ctiv

ity. T

he C

ontra

cto

r is re

sponsib

le fo

r tunin

g th

e a

pplic

atio

n

to m

eet a

ccepta

ble

response tim

es.

1.9

The C

ontra

cto

r m

ust

subm

it a deta

iled T

estin

g M

eth

odolo

gy.

The B

idder

may

perfo

rm

Unit,

Inte

gra

tion,

and

Syste

ms

Tests

off-s

ite;

how

eve

r, th

e

offic

ial

Syste

ms T

est a

nd a

ll User A

ccepta

nce T

ests

must b

e p

erfo

rmed o

n-s

ite u

sin

g

PIA

C’s

testin

g e

nviro

nm

ent.

1.1

0

The C

ontra

cto

r will c

onduct a

Capacity

Test th

at w

ill inclu

de s

tress a

nd v

olu

me

testin

g. C

apacity

testin

g s

hall in

clu

de a

stre

ss te

st th

at in

clu

des s

imula

tion o

f at

least 3

0%

of th

e s

yste

m w

ork

load a

nd v

olu

me te

sts

that te

st th

e d

ata

base a

ctiv

ity

again

st

at

least

30%

of

the data

volu

me.

T

he C

ontra

cto

r w

ill docum

ent,

the

conclu

sio

ns re

sultin

g fro

m th

e te

st

1.1

1

The C

ontra

cto

r will p

repare

and s

ubm

it weekly

pro

gre

ss re

ports

to P

IA o

n e

ach

com

ponent o

f the P

roje

ct u

nder w

hic

h it is

responsib

le

1.1

2

Pro

ject

Quality

M

anagem

ent:

In its

pro

posal,

the C

ontra

cto

r must

describ

e its

appro

ach fo

r assurin

g th

e q

uality

of its

com

ponents

on th

is p

roje

ct. T

he p

roposal

must d

em

onstra

te a

n u

nders

tandin

g o

f the C

ontra

cto

r’s u

ltimate

responsib

ility fo

r quality

and d

efin

e a

com

pre

hensiv

e s

et o

f reasonable

and e

ffectiv

e p

ractic

es fo

r fu

lfilling th

at re

sponsib

ility.

1.1

3

Accepta

nce T

estin

g: P

IAC

’s M

&E

Team

will c

onduct a

rigoro

us a

ccepta

nce te

st

of th

e s

yste

m. P

IA u

ser s

taff a

nd in

form

atio

n s

yste

m s

pecia

lists

will e

xerc

ise a

ll

syste

m fu

nctio

nal a

spects

usin

g a

ppro

pria

te te

st d

ata

(use c

ases d

evelo

ped fro

m

real-tim

e P

IA e

ngin

eerin

g &

main

tenance o

pera

tions) to

assure

that th

e s

yste

m

meets

defin

ed busin

ess and te

chnic

al

perfo

rmance re

quire

ments

. D

urin

g th

is

test, P

IAC

’s M

RO

/ M&

E T

eam

will id

entify

require

d m

odific

atio

ns a

nd d

ocum

ent

them

th

rough

the

pro

ble

m

resolu

tion

or

change

managem

ent

pro

cesses

(describ

ed belo

w)

as appro

pria

te.

T

he C

ontra

cto

r shall

modify

th

e syste

m as

require

d a

nd p

rovid

e n

ew

vers

ions o

f modifie

d c

om

ponents

to P

IA fo

r testin

g. P

IA

will

notify

th

e

Contra

cto

r in

w

riting

when

it dete

rmin

es

that

the

syste

m

is

accepta

ble

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

74

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

1.1

4

Pro

ble

m R

esolu

tion: T

he C

ontra

cto

r and P

IAC

’s M

RO

/ M&

E T

eam

will c

oopera

te

to re

solv

e s

yste

m p

roble

ms fo

und d

urin

g a

ccepta

nce te

stin

g a

nd p

roductio

n u

se,

inclu

din

g th

e w

arra

nty

perio

d. P

IA w

ill prio

ritize a

nd re

port p

roble

ms in

a w

ritten

form

at.

T

he C

ontra

cto

r shall

track th

ese pro

ble

ms to

clo

sure

and re

port

their

sta

tus. T

he C

ontra

cto

r shall e

valu

ate

each re

porte

d p

roble

m, e

stim

ate

the tim

e

needed to

resolv

e th

e p

roble

m, id

entify

pote

ntia

l impacts

on th

e s

yste

m a

nd th

e

pro

ject, a

nd re

port to

PIA

. If PIA

decid

es to

pro

ceed, th

e C

ontra

cto

r shall re

solv

e

the p

roble

m a

ccord

ing to

its a

ssig

ned p

riority

1.1

5

Change M

anagem

ent: P

IAC

’s M

RO

/ M&

E T

eam

and C

ontra

cto

r will c

oopera

te in

managin

g

changes

to

pre

vio

usly

agre

ed

upon

syste

m

functio

nal

capabilitie

s.

PIA

C’s

MR

O / M

&E

Team

will id

entify

pote

ntia

l functio

nal c

hanges a

nd p

ropose

these to

the C

ontra

cto

r in w

riting. T

he C

ontra

cto

r shall e

valu

ate

each p

roposal,

identify

pote

ntia

l impacts

on th

e s

yste

m a

nd th

e p

roje

ct tim

elin

e, a

nd re

port to

PIA

. If

PIA

decid

es to

pro

ceed,

it w

ill prio

ritize th

e c

hange and auth

oriz

e th

e

Contra

cto

r in w

riting to

perfo

rm th

e w

ork

. The C

ontra

cto

r shall tra

ck th

e s

tatu

s o

f

in

pro

gre

ss

change

ord

ers

and

report

to

PIA

upon

request.

H

ow

ever,

cost

escala

tion w

ill not b

e a

llow

ed u

nd

er a

ny c

ircum

sta

nces.

1.1

6

Config

ura

tion M

anagem

ent: T

he C

ontra

cto

r will m

anage v

ers

ion re

leases o

f all

contra

ct d

eliv

era

ble

s a

nd c

erta

in o

ther c

ritical d

ocum

ents

as d

ete

rmin

ed b

y P

IA.

1.1

7

Ensure

re

gula

tory

com

plia

nce

with

P

CA

A

AN

O-1

45.

The

contra

cto

r w

ill be

require

d

to

coopera

te

with

th

e

PC

AA

audit

team

, by

pro

vid

ing

functio

nality

dem

onstra

tions a

nd re

ports

as re

quire

d. A

ny n

on

-com

plia

nce s

hall b

e a

ddre

ssed

by th

e c

ontra

cto

r till com

plia

nce is

verifie

d.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

75

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

SE

RV

ICE

S R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

2

T

RA

ININ

G

2.1

Tra

inin

g S

trate

gy h

as b

een s

ubm

itted a

s p

art o

f the T

echnic

al P

roposal

2.2

It describ

es in

deta

il the a

ppro

ach to

meetin

g th

e tra

inin

g re

quire

ments

for e

ach

type o

f audie

nce

2.3

The g

enera

l conte

nt o

f all tra

inin

g m

ate

rials

, train

ing c

ours

es, a

nd d

ocum

enta

tion

pro

posed h

as b

een d

escrib

ed in

the T

echnic

al P

roposal

2.4

Pro

vis

ion o

f Tra

inin

g M

ate

rial fo

r Technic

al s

upport s

taff &

syste

m u

sers

3

D

AT

A M

IGR

AT

ION

3.1

A d

escrip

tion o

f the g

enera

l appro

ach to

the d

ata

mig

ratio

n p

rocess (m

anual a

nd

auto

mate

d) fo

r his

toric

al, s

eed, a

nd c

uto

ver d

ata

has b

een p

rovid

ed.

3.2

Mig

ratio

n a

ppro

ach / s

trate

gy a

ddre

sses th

e fo

llow

ing:

3.2

.1 M

igra

tion p

rocess (a

uto

mate

d o

r manual, v

erific

atio

n p

rocedure

s)

3.2

.2 M

igra

tion s

chedule

3.2

.3

M

igra

tion p

repara

tion ta

sk o

utlin

e

3.2

.4

Resourc

e re

quire

ments

3.2

.5

Tra

inin

g R

equire

ments

3.2

.6

Pro

gra

mm

ing e

ffort/u

se th

ird-p

arty

applic

atio

n

3.3

Expecta

tions fro

m B

idders

:

3.3

.1

If s

uccessfu

l will p

repare

a d

eta

iled p

lan fo

r data

mig

ratio

n. (S

ectio

n: D

, D3

-5)

3.3

.2

W

ill ensure

sm

ooth

transitio

n w

ithout s

yste

m d

ow

ntim

e.

3.3

.3

W

ill desig

n / a

cquire

rele

vant p

rogra

m/s

oftw

are

to e

nsure

data

cle

ansin

g/in

tegrity

3.3

.4

D

em

onstra

te &

test d

ata

thru

sam

ple

s ta

ken fro

m liv

e s

yste

m.

3.3

.5 D

evelo

p &

docum

ent a

ll opera

tional a

reas o

f the a

bove s

olu

tion

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

76

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

SE

RV

ICE

S R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

4

D

OC

UM

EN

TA

TIO

N

4.1

Contra

cto

r will p

rovid

e u

ser m

anuals

that w

ill cover a

s a

min

imum

the fo

llow

ing:

4.1

.1

C

om

ple

te in

stru

ctio

ns fo

r the u

sers

, com

ple

tely

expla

inin

g th

e u

se o

f each s

yste

m

functio

n;

4.1

.2

S

yste

m u

sage s

cenario

s, b

ased o

n re

al w

orld

exam

ple

s d

raw

n fro

m th

e d

ay-to

-day w

ork

loads o

f typic

al u

sers

, that fu

lly d

escrib

e a

nd e

xpla

in th

e s

alie

nt fe

atu

res

and o

pera

tion o

f the s

yste

m;

4.1

.3

H

ow

input d

ata

are

sto

red a

nd re

late

d b

etw

een s

yste

m re

cord

s;

4.1

.4

H

ow

to g

enera

te / s

uppre

ss s

tandard

and a

d h

oc re

ports

;

4.1

.5

N

orm

al re

port d

istrib

utio

n;

4.1

.6

P

rioritiz

atio

n p

rocessin

g, s

yste

m d

ete

rmin

ed p

rioritie

s, a

nd u

ser o

verrid

e

pro

cedure

s;

4.1

.7

S

yste

m lo

g-o

n, lo

g-o

ff, and s

ecurity

featu

res;

4.1

.8

E

rror m

essages a

nd e

rror c

orre

ctio

n p

rocedure

s;

4.1

.9

H

elp

featu

res a

nd u

sage;

4.1

.10

S

yste

m tro

uble

shootin

g;

4.1

.11

M

andato

ry d

ata

field

s a

nd d

efa

ult d

ata

valu

es;

4.1

.12

T

ravers

ing s

yste

m m

enus;

4.1

.13

S

cre

en la

youts

and c

onte

nts

;

4.1

.14

In

quiry

functio

ns

4.2

Contra

cto

r will p

rovid

e te

chnic

al m

anuals

that w

ill cover a

s a

min

imum

the

follo

win

g:

4.2

.1

A

ddre

sses th

e v

iew

of th

e s

yste

m re

quire

d b

y d

evelo

pers

, adm

inis

trato

rs a

nd o

ther

technic

al p

ers

onnel.

4.2

.2

P

rovid

es a

n u

nders

tandin

g o

f the a

pplic

atio

n; d

ata

base d

esig

n a

nd file

stru

ctu

res;

rela

tionship

s b

etw

een p

rogra

ms, s

ecurity

; trouble

shootin

g; s

pecia

l constra

ints

; and

oth

er o

pera

tional g

uid

elin

es

4.3

Contra

cto

r has s

ubm

itted s

am

ple

copie

s o

f all p

roposed d

ocum

ents

that it w

ill pre

pare

/ deliv

er to

PIA

durin

g th

e c

ours

e o

f this

pro

ject.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

77

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

SE

RV

ICE

S R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

5

W

AR

RA

NT

Y A

ND

MA

INT

EN

AN

CE

SU

PP

OR

T

5.1

Contra

cto

r will p

rovid

e w

arra

nty

serv

ices fo

r a p

erio

d o

f thre

e y

ears

by e

nsurin

g

that th

e s

yste

m in

every

way m

eets

the s

pecific

atio

ns s

tate

d in

this

RF

P

5.2

Separa

te

and

apart

from

th

e

warra

nty

support

serv

ices,

the

Contra

cto

r shall

pro

vid

e s

upport (“M

ain

tenance”) s

erv

ices fo

r Applic

atio

ns, a

nd D

BM

S b

egin

nin

g

upon th

e e

nd o

f the w

arra

nty

serv

ices a

nd e

xte

nded u

p to

thre

e (3

) year th

ere

afte

r

5.3

Contra

cto

r has p

rovid

ed its

User a

nd T

echnic

al S

upport P

lan d

eta

iling th

e

follo

win

g:

5.3

.1

O

n-s

ite fa

ult d

iagnostic

techniq

ues;

5.3

.2

R

em

ote

or te

le-d

iagnostic

fault d

iagnosin

g te

chniq

ues;

5.3

.3

A

vera

ge tim

e to

arriv

e o

n-s

ite;

5.3

.4

M

ean tim

e to

fix m

ajo

r syste

m c

om

ponents

;

5.3

.5

F

ault e

scala

tion p

rocedure

s;

5.3

.6

M

ain

tenance o

f erro

r logs.

5.4

Contra

cto

r will e

sta

blis

h H

otlin

e a

nd H

elp

desk s

upport

5.5

Contra

cto

r has s

pecifie

d a

solu

tion to

accom

modate

PIA

’s re

quire

ment o

f additio

nal

custo

miz

ed re

ports

durin

g th

e m

ain

tenance a

nd s

upport p

erio

d.

6

V

ER

SIO

NS

AN

D U

PG

RA

DE

S

6.1

Contra

cto

r has a

ssure

d th

at tra

inin

g m

ate

rial / s

oftw

are

/ pro

cess d

ocum

ents

will

be d

uly

licensed fo

r the p

urp

ose o

f imple

menta

tion a

nd u

se b

y P

IA fo

r the E

RP

. T

hese w

ill be of

late

st

vers

ion and C

ontra

cto

r w

ill ensure

up

-gra

datio

n of

all

module

s / m

ate

rial / p

rocess d

ocum

ents

durin

g th

e w

arra

nty

perio

d a

nd a

s p

art o

f afte

r-warra

nty

main

tenance s

upport.

6.2

Durin

g th

e im

ple

menta

tion a

nd s

ubsequent ro

llout C

ontra

cto

r will b

e re

sponsib

le

to

arra

nge

and

pro

vid

e

free

vers

ion

upgra

des

of

all

com

ponents

under

its

responsib

ility. C

ontra

cto

r will e

nsure

that a

t the tim

e o

f handin

g o

ver th

e s

olu

tion

to P

IA all

com

pon

ents

are

of

the la

test

rele

ase and th

at

the to

tal

solu

tion is

certifie

d b

y th

e C

ontra

cto

r for c

om

ple

teness.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

78

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H6

H

AR

DW

AR

E R

EQ

UIR

EM

EN

TS

D

eta

iled b

elo

w a

re th

e h

ard

ware

require

ments

. Contra

cto

rs m

ust p

rovid

e th

eir re

sponses in

the “

Resp

on

se” c

olu

mn a

nd

pro

vid

e a

dditio

nal in

form

atio

n / c

larific

atio

n in

the “

Rem

ark

s” c

olu

mn.

Vendor re

spo

nse m

ust b

e re

stric

ted to

:

Sr. N

o.

Resp

on

se

Rem

ark

s

1.

Y

= Y

es

Deta

ils o

f how

the h

ard

ware

require

ments

will b

e fu

lfilled

2.

N

= N

o / C

annot b

e p

rovid

ed

Nil

In c

ase th

e C

ontra

cto

r does n

ot p

rovid

e a

resp

onse, it w

ill be c

onsid

ere

d a

s “

N”.

The C

ontra

cto

r should

pro

vid

e th

e re

spo

nse b

y fillin

g u

p th

e c

olu

mns "

Resp

on

se" a

nd "

Rem

ark

s" o

nly

. Any c

ha

nges,

such a

s a

dditio

n, d

ele

tion, o

r modific

atio

n o

f row

conte

nts

in th

e R

FP

docum

ent, w

ill be c

onsid

ere

d a

s a

n in

va

lid re

sponse

to th

e R

FP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

79

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

HA

RD

WA

RE

RE

QU

IRE

ME

NT

S

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

1

H

AR

DW

AR

E

1.1

Contra

cto

r has s

ubm

itted deta

ils of

the pro

posed c

onfig

ura

tion, in

clu

din

g la

yout

dia

gra

m d

eta

iling m

odel d

esig

natio

n(s

), mem

ory

siz

e, n

um

ber o

f CP

Us, ty

pe o

f driv

es w

ith c

apacity

and c

ounts

.

1.2

The

offe

red

solu

tion

com

plie

s

with

th

e

Open

Syste

ms

Arc

hite

ctu

re

and

late

st

technolo

gy tre

nds.

1.3

The s

olu

tion is

scala

ble

, both

horiz

onta

lly a

nd v

ertic

ally

.

1.4

The h

ard

ware

is s

ized k

eepin

g in

vie

w th

e o

pera

tional re

quire

ments

of th

e M

RO

/ M

&E

and a

ssocia

ted a

pplic

atio

ns.

1.5

The h

ard

ware

is fu

lly c

apable

of h

ostin

g th

e M

RO

/ M&

E c

ertifie

d d

ata

base.

1.6

The h

ard

ware

allo

ws e

ach p

artitio

n o

f the M

RO

/ M&

E e

nviro

nm

ent to

be is

ola

ted in

such a

way th

at a

softw

are

fault in

one p

artitio

n w

ill not h

ave a

n im

pact o

n a

noth

er

partitio

n.

1.7

All s

oftw

are

require

d fo

r clu

ste

ring o

f serv

ers

and im

ple

menta

tion o

f DR

P is

in

clu

ded in

the s

olu

tion.

1.8

The s

olu

tion w

ill be fu

lly s

upporte

d b

y th

e C

ontra

cto

r for n

ot le

ss th

an te

n y

ears

fro

m th

e d

ate

of s

upply

. It will re

main

capable

of b

ein

g s

upporte

d, u

pgra

ded a

nd

exte

nded b

y th

e C

ontra

cto

r durin

g th

is p

erio

d.

1.9

The

solu

tion

pro

vid

ed

will

be

accom

panie

d

with

com

ple

te

docum

enta

tion,

opera

ting m

anuals

, syste

m dia

gra

ms,

sta

rtup and re

covery

pro

cedure

s and all

oth

er in

form

atio

n re

quire

d fo

r pro

per a

nd e

fficie

nt o

pera

tion.

1.1

0

Contra

cto

r will p

rovid

e a

ll technic

al m

ate

rial a

nd v

erifia

ble

benchm

ark

s re

late

d to

th

e p

roposed s

olu

tion. T

he h

ard

ware

is b

y th

e M

RO

/ M&

E p

rincip

al v

endor fo

r the

opera

tion o

f the M

RO

/ M&

E a

nd is

reasonably

expecte

d to

be c

ertifie

d fo

r futu

re

vers

ions o

f the M

RO

/ M&

E d

urin

g th

e e

xpecte

d life

of th

e h

ard

ware

.

1.1

1

C

ontra

cto

r has pro

vid

ed in

form

atio

n on w

arra

ntie

s on th

e equip

ment

and any

optio

ns re

gard

ing w

arra

nty

exte

nsio

n. P

rincip

al’s

assura

nce fo

r parts

availa

bility

afte

r expiry

of w

arra

nty

perio

d is

als

o p

rovid

ed.

1.1

2

T

he

Contra

cto

r has

to

pro

vid

e

thoro

ugh

and

conte

mpora

ry

3rd

party

te

stin

g

softw

are

for a

ccepta

nce a

nd lo

ad te

stin

g. T

he te

stin

g w

ill be d

one a

ccord

ing to

syste

m e

quip

ment s

pecific

atio

ns a

s w

ell a

s g

enera

lly a

ccepte

d p

ractic

es.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

80

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H

AR

DW

AR

E R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

1.1

3

A

ll test re

sults

will b

e c

om

ple

tely

docum

ente

d b

y th

e C

ontra

cto

r. Com

ple

te te

st

docum

enta

tion in

clu

din

g re

sults

of th

e 3

rd p

arty

load / s

tress te

stin

g s

oftw

are

will

be p

rovid

ed to

PIA

.

1.1

4

B

ased

on

PIA

C’s

hig

h

availa

bility

re

quire

ments

, fa

ilover

desig

n

is

based

on

pro

tectin

g s

ingle

poin

t of fa

ilure

.

1.1

5

For h

igh a

vaila

bility

on th

e a

pplic

atio

n la

yer, th

e s

olu

tion w

ill imple

ment lo

g o

n

load b

ala

ncin

g b

etw

een th

e a

pplic

atio

n s

erv

ers

. It does n

ot n

eed a

ny fo

rm o

f re

allo

catio

n o

f resourc

es b

etw

een

serv

ers

. The a

pplic

atio

n e

nviro

nm

ent is

siz

ed

and desig

ned such th

at

upon fa

ilure

of

an applic

atio

n serv

er

(based on sin

gle

poin

t of fa

ilure

), min

imum

degra

datio

n o

f perfo

rmance w

ill be e

xperie

nced.

1.1

6

A

Dis

aste

r Recovery

(DR

) desig

n is

pro

vid

ed w

hic

h p

rovid

es a

seam

less, p

ragm

atic

D

R p

rocess. It in

tegra

tes w

ithin

the o

vera

ll desig

n o

f the M

RO

/ M&

E la

ndscape.

1.1

7

The D

R p

rocess is

sim

ple

to e

xecute

. A s

tep

-by-s

tep p

rocess a

nd p

rocedure

is

pro

vid

ed to

min

imiz

e th

e p

ote

ntia

l for h

um

an e

rror in

a tim

e o

f cris

is a

nd d

isaste

r. A

dditio

nally

, the D

R d

esig

n c

an b

e e

asily

teste

d w

ith m

inim

al im

pact o

n d

ay-to

-day o

pera

tions.

Section I – Completion & Compliance Checklist Page 181 of 189


SECTION I

COMPLETION AND COMPLIANCE CHECKLIST



I1 PROPOSAL COMPLETION CHECKLIST

RFP Reference

Requirement Description Yes / No Section

Sub section Item

B B3 Completed All Forms

a) Proposal Form b) Biding Organization & Experience c) Bidders Experience d) Description of Approach, Methodology & Project plan e) Team composition & task assignment f) CV of professional staff

g) Products Price Schedule h) Services Prices Schedule i) Recurrent Cost Schedule j) Proposal Price Summary k) Bid Bond l) Form of Contract Agreement m) Performance Guarantee n) Consortium Responsibility (if applicable)

B1 7.2.3 Declaration of accepting responsibility for the successful integration and interoperability of all proposed products and other PIA systems as required by the RFP documents (reference Section A5-1)

B1 8 Bid Bond

B1 4.2 Original plus One hardcopy of Technical and Commercial Proposals

B1 4.2A Softcopy of Technical Proposal

B1 11.4 Technical and Commercial Proposals provided separately, clearly marked and sealed, as required

B4 Proposal in Format, as specified in Section B3 – Format and Contents of Proposal

B1 22.1, 22.2

Declaration of not inducing or influencing the bidding / evaluation process

D D1 3 Comprehensive Project Plan

4 Project Organization Structure and Personnel Roster

E E1 DBMS And Database Administration Tools

F F1 Hardware specifications and design layout

G G1 Bidder’s Qualifications and Experience

H Requirements Compliance Matrix

I Completion and Compliance Checklist



I2 PRODUCTS AND SERVICES

RFP Reference Requirement Description

Contractor Proposal Ref.

& Page Section Sub section Item

E E1 DATABASE MANAGEMENT SYSTEM AND DATABASE ADMINISTRATION TOOLS

E2 APPLICATION DEVELOPMENT TOOLS

E3 QUERY AND REPORT GENERATION TOOLS

E4 INTERIM SERVERS

3 The Contractor is required, as part of its proposal to provide an Interim Server and Operating System Software.

4

It is anticipated that the Server(s) will be required for a period of approximately six to nine months from the date of supply of Server Hardware, Operating System Software and MRO / M&E Package Software.

5 The Contractor will be required to re-install all MRO / M&E, 3rd Party, Custom-built software, DBMS, Database, Development tools, etc. on the Permanent Server(s).

6 The details of the proposed Interim Server(s) hardware Configuration and Operating System software are to be provided by the Contractor in its proposal.

7 The configuration of machines should be capable to support the number of users as specified by the Contractor in its plan.

8 In its proposal, the Contractor will provide site specification requirements for the installation and operation of the Interim Server(s).

9

PIA - at the end of implementation and rollout - may at its discretion, decide to purchase the interim servers provided by the Contractor. In this regard, the Contractor should, as part of its Price Proposal, separately mention the cost at which it would offer these machines for sale to PIA. However, this cost component should not be added to the total bid price, nor should it be used to calculate the bid bond amount.

E5 3RD PARTY SOFTWARE

2

Contractor will be responsible to ensure that all required 3rd party software, operating systems, system management and monitoring tools, backup and recovery software, database administration tools, disaster recovery and business continuity tools, APIs / interfaces, etc. are made available, documented, designed, implemented and operational to meet PIA’s requirements in the proposed MRO / M&E solution.

3 It is the responsibility of the Contractor to offer PIA a complete solution in all respects – delays or costs arising out of any shortcoming will have to be borne by the Contractor.

D D1 IMPLEMENTATION


1.2 Installation of all supplied Application software, DBMS software, Development / Query and Report Writer / Database Administration Tools and any other required Utilities, on the Interim Server(s).

1.3 Installation of all supplied Application software, DBMS software, Development / Query and Report Writer / Database Administration Tools and any other required Utilities, on the Permanent Server(s).

1.4 Implementation of Database security features.

1.5

Development of Business Requirement Document for each functional area which maps the business process for the parameterization / configuration of MRO / M&E Package. This should be based on PIA’s reengineered business processes that would be made available to the Contractor.

1.6 Development of business case scenarios

1.7 Parameterization of supplied Software i.e. the configuration of application software via selection of in-built values, setting up of tables, etc. to meet the business requirements.






1.8 Software modifications, where required, to supplied Application software and development of extensions and / or modules to meet the business requirements.

1.9 Design, development and initial setup of databases.

1.10 Integration with PIA’s other applications such as Oracle ERP, Sabre applications, IBM Lotus Notes, AIMS, Aero-Exchange, PIA website, etc.

1.11

Design and development of customized reports, screens, workflows, etc. PIA will try to maximize the use of standard reports, screens and workflows available in the proposed solution; however, the Contractor cannot set an upper limit to the number of customization that it will undertake.



1.14 Design and implementation of online and batch job operational activities until implementation is successfully completed at all locations.

1.15 Progress reporting on Contractor related activities.

1.16 Quality Assurance for Contractor related activities.

1.17 Any other tasks required in successful delivery of the supplied products and services.

2 Contractor must utilize airline industry specific rapid implementation templates to ensure quick implementation. Details of such templates should be submitted with the Technical Proposal.

3

A detailed comprehensive business plan is to be prepared by Contractor and submitted as a part of project. The business plan shall be mutually approved and incorporated as part of contract and reviewed at regular intervals.

4

The Contractor must submit a detailed project organization structure identifying, by name, the specific individuals who would be assigned different tasks of the project.

The Contractor must assign a full-time Project Manager to manage this Project. This person must be from the list of Lead Consultants submitted by the Contractor in response to the EOI. He / she must have the experience of implementing the proposed MRO / M&E in at least two airlines. His / her detailed CV including experience of managing MRO / M&E and other projects; MRO / M&E certification, if any; number of MRO / M&E projects managed; number of years on each project; etc. must be submitted along with the Technical Proposal.

A personnel roster containing detailed responsibilities of Contractor staff should also be provided. It should include the estimated number of hours to be worked on the project for each person broken down in different phases of the project; it should also clearly identify the start and end dates for each phase. These staff members should be from the list of implementers provided in response to the EOI. Detailed CVs of additional members should be provided.

5 The Contractor may perform Unit, Integration, and Systems Tests offsite; however, the official Systems Test and all User Acceptance Tests must be performed on-site using PIAC’s testing environment.

6 The Contractor must provide, by phase, the proposed number of personnel to be based on-site at PIAC’s premises, and space and other requirements to be provided by PIA during Implementation.

7

The Contractor will develop a system turnover plan which indicates the conditional criteria required to fully turn over the daily operation of the system to PIA technical staff. At a minimum, the turnover plan must include the state of readiness required for system turnover and all required documentation.

8 The Contractor’s implementation plan must take into consideration the business priority areas and applications.






9

System Performance: During system installation the Contractor will evaluate performance factors including, but not limited to, transaction volumes, response times, CPU utilization, and input / output activity. The Contractor will be responsible for tuning the application to meet acceptable response times.

10 Capacity Evaluation: The Contractor will conduct a Capacity Test will include stress and volume testing.

11

Project Management and Reporting: The Contractor is required to maintain a project plan covering its components of the project and each individual phase. The Contractor will be required to prepare and submit weekly progress reports to PIA on each component of the Project under which it is responsible.

12

Project Quality Management: In its proposal, the Contractor must describe its approach for assuring the quality of its components on this project. Contractor must also specify whether third party audit / quality assurance visits will be undertaken and who will bear the cost of these visits.

13

Acceptance Testing: PIA will conduct a rigorous acceptance test of the system. During this test, PIA will identify required modifications and document them through the problem resolution or change management processes (described below) as appropriate. The Contractor shall modify the system as required and provide new versions of modified components to PIA for testing. PIA will notify the Contractor in writing when it determines that the system is acceptable.

14

Problem Resolution: The Contractor and PIA will cooperate to resolve system problems found during acceptance testing and production use, including the warranty period. PIA will prioritize and report problems in a written format. The Contractor shall track these problems to closure and report their status upon request.

15

Change Management: PIA and Contractor will cooperate in managing changes to previously agreed upon system functional capabilities. PIA may identify potential functional changes; however, cost escalation will not be allowed under any circumstances.

16 Configuration Management: The Contractor shall manage version releases of all contract deliverables and certain other critical documents as determined by PIA.

17

The Bidder must assign a full-time Project Manager to manage this Project. His/her detailed CV including experience of managing MRO and other Projects, MRO Package Certification, if any, the number of MRO projects managed and the number of years on each project, etc. must be submitted along with the Proposal.

D2 TRAINING

2

As a part of the proposal, the Contractor must describe in detail its approach to meeting the training requirements for each audience. The description must include methods proposed to deliver both training and documentation. The Contractor should describe the general content of all training materials, training courses, and documentation proposed.

3

The Training Strategy should include a training solution to support the training of end users throughout PIA in the functionality of the various MRO and Add-on applications components.

The Contractor is required to develop materials for training users in central and remote offices.

The Contractor must provide material for training Technical Staff such as database administrators, system administrators, operators, and developers.

4 Cost of Foreign Training, if proposed, should be included in the Contractor’s Financial Proposal and include all expenses related to travel, accommodation, tuition fees and other incidentals.






D3 DATA MIGRATION

4 The Conversion Strategy must address, at a minimum, items a) to f)

5 Undertake to submit data Migration Plan, as per Section: D, D3-5

6 Ensure smooth transition, data cleansing & integrity, document all areas.

D4 DOCUMENTATION

1

As part of its Technical Proposal, the Contractor must describe the level and types of documentation that will be delivered. This documentation must cover each level of operation, for example: user, security administrator, database administrator, operator, developer, etc.

2 Two complete hardcopy sets of documentations for all Contractor supplied components for this Project must be furnished, in addition to softcopies.

3 The manuals should feature clear organization of content, easy to understand language, useful graphic presentations, and a thorough index and glossary.

4

These manuals must address the view of the system required by business unit staff (end users). It must contain sufficient information to enable the user to independently operate the system, troubleshoot simple problems, and correct problems.

5 In conjunction with the Users’ Manual, Quick Reference cards will be produced by the contractor, which will be an immediate aid to the user and quickly describe operations.

6

The Technical Manuals must address the view of the system required by developers, administrators and other technical personnel. It should provide an understanding of the application; data base design and file structures; relationships between programs, security; troubleshooting; special constraints; and other operational guidelines.

7 Copies of all licenses, warranties, maintenance agreements and similar materials for all Contractor delivered components of the project must be furnished separately.

8 Contractor must submit sample copies of all documents that it will prepare / deliver to PIA during the course of this project.

D5 WARRANTY AND MAINTENANCE SUPPORT

1

The Contractor will provide warranty services for a period of at least one year for software and a minimum of three years for hardware. The warranty will begin on PIA’s written final acceptance of the system. All warranty support services are to be rendered free of charge to PIA. Contractor will be responsible for all related costs during this period.

2

Separate and apart from the warranty support services, the Contractor shall provide Maintenance services for Applications, and DBMS beginning upon the end of the warranty services and extended upto three (3) years thereafter.

3

The Contractor must describe in detail in the Technical Proposal its User and Technical Support Plan for the warranty and maintenance periods, covering the resources, timing and procedures that will be available to provide this support.

4 The Contractor must specify the various categories of problems it will support and describe the severity levels of problems.

5 Details of the establishment of an effective “Hot Line Telephone and Support Desk” service should be provided.

6

PIA may require the Contractor to develop additional customized reports, screens, workflows, etc. during the maintenance and support period. Contractor must specify in its Technical Proposal a solution to accommodate PIA’s requirement. The Price Proposal must contain the pricing mechanism for additional report development / customization.

7

The Contractor must provide a list of clients in Pakistan and abroad for which MRO / M&E Maintenance Support is, or has been provided during the past three years. Details of modules supported should be included.



RFP Reference

Requirement Description Contractor

Proposal Ref. & Page Section

Sub section Item

D6 VERSION AND UPGRADES

1

Contractor must ensure that training material / software / process documents are duly licensed for the purpose of implementation and use by PIA of the MRO / M&E. These are to be of latest version and Contractor must ensure up-gradation of all modules / material / process documents during the warranty period and as part of after-warranty maintenance support.

2

During the implementation and subsequent rollout Contractor would be responsible to arrange and provide free version upgrades of all components under its responsibility. Contractor must ensure that at the time of handing over the solution to PIA all components are of the latest release and that the total solution is certified by the Contractor for completeness.

F HARDWARE

1

The Contractor must evaluate and prepare an appropriate configuration to run the proposed MRO / M&E solution. PIA is looking for a high-availability solution including servers, clustering design, and disaster recovery recommendations besides maintenance / repair options needed for the associated infrastructure.

The response must address all items 1) to 17)



I3 BUSINESS INFORMATION AND APPLICATION NEEDS

RFP Reference



Sub section Item

D D7 Information Requirements of the management.

C / H4 Functional Information Requirements

1.0 Functional Requirement concerning Aircraft Engineering

2.0 Functional Requirements for Aircraft Induction and Phase out

3.0 Functional Requirements for Line Maintenance

4.0 Functional Requirements for Cabin Maintenance

5.0 Functional Requirements for Base Maintenance

6.0 Functional Requirements for Component Overhaul

7.0 Functional Requirements for Quality Assurance

8.0 Functional Requirements for Maintenance Operation Support Center

9.0 Functional Requirements for Business Development

10.0 Functional Requirements for Power Plant Overhaul

11.0 Functional Requirements for Tools and Equipment& Standards Labs

12.0 General Functional Requirements of the MRO / M&E System



I4 MRO / M&E PACKAGE REQUIREMENTS



& Page Section Sub section

Item

A A4 1. OVERVIEW OF SOLUTION REQUIREMENTS

A A4 2 GENERAL REQUIREMENTS

2.1 Common Characteristics

2.2 Integration

2.3 Configuration

2.4 Technology Interfaces

2.5 User Interface

2.6 Security & Authorization

2.7 Reporting / Enquiry

2.8 Data Analytic Tools

2.9 Communication

2.10 Flexibility

2.11 System Availability

2.12 Transaction Timing

2.13 Online Documentation and Training

2.14 Storage / Record Retrieval

2.15 System Security

A A4 3. TECHNOLOGY REQUIREMENTS

3.1 New Technology

3.2 Multiple Environments

3.3 System Performance

3.4 Archive and Purge

3.5 Recovery

3.6 Backup and Reorganization

3.7 Print Management

3.8 Fallback Solution

3.9 Ability for system and license updates


3.11 Server Hardware

3.12 System and Network Management Tools

3.13 Data Support

3.14 Authentication for accessing protected data & transactions

3.15 Web-enablement

3.16 Workflow

3.17 Others

INVITATION TO BID

Implementation of MRO/ M&E Project

Pakistan International Airlines Corporation, the national flag carrier, plans to implement a proven, time-

tested, internationally acclaimed and airline specific Maintenance Repair Overhaul (MRO) /

Maintenance & Engineering (M&E) solution catering to its requirements in the following areas:

Engineering & Airworthiness functions

Quality Assurance

Aircraft Line, Cabin & Base Maintenance

Engine Overhaul, Components Overhaul

Aircraft Material/Rotables Management.

Checks & Schedule Planning

Outsourced Maintenance

Resources Allocation & Performance Monitoring

Third Party Clients Management.

A/C Lease-in /out support.

Documentation / Library functions

Bidding documents, which are containing detailed terms and conditions, method of procurement,

procedure for submission of bids, bid security, bid validity, opening of bid, evaluation criteria,

clarification / rejection of bids, performance guarantee etc. are available for the interested bidders at

www.piac.com.pk

Tenders are called on “Single Stage Two Envelope” basis. The bids, prepared in accordance with the

instructions in the bidding documents, must reach at General Manager Procurement, Supply Chain

Department (Store Building), PIA Head Office, Karachi on or before September 18, 2017 up to

1030 (PST). Bids will be opened the same day at 1100 Hrs. (PST). This advertisement with complete

RFP is also available on PPRA website at www.ppra.org.pk

Bidders are required to submit two (hard & soft copy format) copies each of the technical & commercial

bid marked as “Original” & “Copy”.

Local bidders are required to submit a pay order in the name of PIACL as a tender fee PKR 6,000.00

along with technical proposal.

Bids must be valid for 180 days.

PIAC reserves the right to reject any or all bids or cancel the procurement process at any stage in line

with PPRA rules.

General Manager Procurement

Supply Chain Management

PIA Head Office, Karachi.

Ph: +9221 99044423


[email protected]

[email protected]

Page 1 of 189


REQUEST FOR PROPOSAL

MRO / M&E PROJECT Pakistan International Airlines Corporation (Limited)

Ref: PIACL/SCM/ MRO M&E (Engg.)/11/17 www.piac.aero

Page 2 of 189


TABLE OF CONTENTS


SECTION A PROJECT DETAIL 5

A1 PROJECT DETAILS 6

1 Project Background 6

2 Locations 6

3 Business Objectives 7

4 Information Technology (IT) Objectives 7

5 PIA Fleet Size & Composition 8

6 Definitions / Terms Used 8

A2 PROJECT ORGANIZATION 9

A3 PROJECT COMPONENTS & IMPORTANT MILESTONE 10

1 Project Components 10

2 Phase-wise Objectives 10

A4 PRODUCT REQUIREMENT (MRO/M&E PACKAGE) 12

1 Overview of Solution Requirements 12

2 General Requirements 13

3 Technology Requirements 17

A5 PIA EXISTING SYSTEMS, APPLICATIONS & INFRASTRUCTURE 22

1 Existing Systems 22

2 Details of Existing Systems Requiring Interface 23

3 Existing Infrastructure 24

SECTION B INSTRUCTIONS TO BIDDERS (ITB) 29

B1 INSTRUCTIONS FOR BID SUBMISSION 30

1 Introduction / Scope of Bid 30

2 The Request for Proposal Document 31

3 Clarification of RFP Document 31

4 Amendment to RFP Document 32

5 Preparation of Proposals 33

6 Proposed Prices 35

7 Documents Establishing Contractor’s Eligibility and

Qualifications.

37

8 Documents Establishing Products, Services Eligibility &

Conformity to RFP

37

Page 3 of 189



9 Bid Bond 38

10 Period of Validity of Proposals 39

11 Tender Proceedings 39

12 Submission of Proposals 40

13 Deadline for Submission of Proposals 41

14 Opening of Proposals by PIA 41

15 Clarification of Proposals 41

16 PIA’s Right to accept any Proposal and to reject any or All

Proposals

41

17 Evaluation & Finalization of Selection 42

18 Confidentiality 42

19 Bidder’s Profile 43

20 Legal Binding 43

21 Performance Guarantee 43

22 Signing of Contract 43

23 Contacting PIAC 44

B2 SUMMARY OF REQUIREMENTS 45

B3 TEMPLATE FORMS 46

B4 FORMAT & CONTENTS OF PROPOSAL 67

1 General Proposal Requirements 67

2 Required Format of the Proposal 67

SECTION C PRODUCT DETAILS (MRO PACKAGE & ADD-ONS) 72

C1 OBJECTIVES 73

C2 FUNCTIONAL REQUIREMENTS 74

C3 GENERAL REQUIREMENTS 99

SECTION D SERVICES REQUIREMENTS 102

D1 IMPLEMENTATION 103

D2 TRAINING 106

D3 DATA MIGRATION 109

D4 DOCUMENTATION 110

D5 WARRANTY AND MAINTENANCE SUPPORT 111

D6 VERSION AND UPGRADES 112

D7 INFORMATION NEEDS AND APPLICATION REQUIREMENTS 113

Page 4 of 189



D8 SYSTEM SECURITY 113

SECTION E PRODUCT REQUIREMENTS 114

E1 DBMS AND DATABASE ADMINISTRATION TOOLS 115

E2 APPLICATION DEVELOPMENT TOOLS 116

E3 QUERY AND REPORT GENERATOR TOOLS 117

E4 INTERIM SERVERS AND OPERATING SYSTEM 117

E5 3RD. PARTY SOFTWARE 118

SECTION F HARDWARE REQUIREMENTS 119

F1 HARDWARE 120

SECTION G BIDDER’S QUALIFICATION, EXPERIENCE & EVALUATION 122

G1 BIDDER’S QUALIFICATIONS AND EXPERIENCE 123

G2 EVALUATION 125

SECTION H REQUIREMENTS COMPLIANCE MATRIX 130

H1 GLOBAL REQUIREMENTS – GENERAL 131

H2 GLOBAL REQUIREMENTS – TECHNICAL 137

H3 GLOBAL REQUIREMENTS – OTHERS 145

H4 FUNCTIONAL REQUIREMENTS – MRO/M&E SOLUTION 149

H5 SERVICES REQUIREMENTS 170

H6 HARDWARE REQUIREMENTS 178

SECTION I COMPLETION AND COMPLIANCE CHECKLIST 181

I1 PROPOSAL COMPLETION CHECKLIST 182

I2 PRODUCTS AND SERVICES 183

I3 BUSINESS INFORMATION AND APPLICATION NEEDS 188

I4 MRO PACKAGE REQUIREMENTS 189

Page 5 of 189


SECTION A

PROJECT DETAIL

Page 6 of 189


A1. PROJECT DETAILS

1. Project Background

Pakistan International Airlines (PIA) is set to renew its IT landscape in line with its

changing business requirements. ERP from Oracle has already gone live in core business

area of the airline. Reassessment of business processes and further upgrade of the

information technology environment are the focused objectives.

In order to achieve greater operational efficiencies and to facilitate the realization of growth

targets, PIA has decided to implement a comprehensive Maintenance& Engineering

(M&E) IT solution which will be the best combination of technology products and services

at a reasonable cost.

The main components of the project are:

▪ Business process study / business process alignment with best industry practices

▪ Procurement of MRO / M&E system and supporting infrastructure

▪ MRO / M&E Solution implementation, integration, training and rollout

▪ Post-implementation support

With rapid implementation methodologies and accelerated deployment options available in

best of the breed MRO / M&E solutions, it is PIA‘s intention to complete the implementation,

training and rollout in minimum time period. The Contractor must recommend a suitable rapid

implementation approach to help ensure project success within the proposed timeline. Since

time is of essence, the proposed timeline will be fixed and strictly adhered to

2. Locations

The locations intended to be covered under the scope of the MRO / M&E Solution

implementation are as follows: -

▪ PIA Head Office at Karachi

▪ PIA Engineering, all locations in Karachi, Islamabad & Lahore as well as the PIA

line stations

▪ PIA Stores, Hangers and Workshops (all locations)

▪ PIA Computer Center at Karachi

Page 7 of 189


3. Business Objectives

To operate efficiently and effectively by having streamlined business processes, integrated

information systems and best industry practices, aimed at optimum utilization of available

resources within engineering department and across the entire organization.

It is the ultimate goal of PIA engineering department, to keep the entire fleet in airworthy

condition at all times. The new system shall support this goal by providing functionalities

as:

▪ Engineering & Airworthiness management;

▪ Management of airworthiness directives (ADs), service bulletins (SBs) and

engineering orders (EOs);

▪ Configuration management;

▪ Maintenance planning document (MPD) and maintenance program management;

▪ Maintenance planning and scheduling;

▪ Maintenance control and line maintenance;

▪ Heavy maintenance;

▪ Engine maintenance;

▪ Back shop and component maintenance;

▪ Tools and ground service equipment;

▪ Repair and warranty management; and

▪ Quality assurance & regulatory compliance;

▪ Client Order Management.

▪ A/C Lease in/out

▪ Documentation Management

Form the commercial point of view, the on-time performance and dispatch reliability of the

entire fleet is of essence. A well-structured maintenance planning supported by the

system shall support this objective. The number of Aircraft-On-Ground (AOG) situations to

be reduced.

With transparent data and streamlined business processes, PIA Engineering to be in a

position for more cost efficiency and a higher performance.

PIA Engineering also operates as engineering service provider to other airlines and a key

player in the 3rd party MRO business in the region. With the new MRO / MRO / M&E IT

functionalities, the PIA Engineering shall be more attractive for the 3rd party market.

4. Information Technology (IT) Objectives

Keeping in-line with the organization’s vision and mission, the Information Technology

department at PIA has formulated the following objectives:

▪ To implement industry standard systems / solutions which are integrated, adaptive

and flexible to both internal and external challenges and evolve as technology

Page 8 of 189


progresses and must be capable to meet present and future airline industry

challenges.

▪ To carefully plan and deploy resources to ensure continuity of Information

Technology services and its availability on 24x7 hours basis.

▪ To ensure that Information Technology is effectively applied to business needs.

▪ To provide technology tools to PIA staff for capturing and harnessing the knowledge

base with the latest in IT, for timely management decision support.

▪ Information Security and Audit Trails for transactional data.

▪ To incorporate data analytics including predictive, and suggestive analytics for right

decisions.

5. PIA Fleet Size & Composition

PIA current fleet is composed of both narrow body & wide-body aircraft from Boeing

777 family, Airbus A320 family, ATR42/72. The combined numbers at the moment

stands at 35 with an expected growth upto 50 aircraft in near future.

6. Definitions / Terms used.

i. Wherever word “PIA” is used, it should be read and understood as “Pakistan

International Airlines Corporation Limited (PIACL)”

ii. The term “MRO / M&E Solution” is invariably used to be read and understood

as an IT Solution / Software / System / Package for an airline MRO / M&E.

Page 9 of 189


A2. Project Organization

The “Project Management Office”, established at PIAC Head Office at Karachi,

Pakistan, will be the focal points of project management and implementation activities.

One of the benefits of managing this project through the “Project Management Office”

is that this office has already experience of implementation of ERP in PIA at all

stations throughout the globe.

Also, the flexibility of incorporating the required high level of technical/functional

resources in each discipline, PMO office has expertise in the areas of implementation

of Oracle ERP (Oracle e-Business Suite).

This Project Management Office (PMO) will remain in operation for the whole duration

of the project.

PMO team along with Engineering department and ICT, comprising of professionals

having experience in MRO / M&E processes & requirements, with network

management & ERP deployment. The PMO Team would be collaborating with PIA’s

management, and IT staff through various stages of this project. Besides PMO, a

Project Steering Committee will be there to oversee the progress and make decisions

on key issues.

The successful MRO / M&E Contractor would become a part of the PMO office till the

completion of project.

Page 10 of 189


A3. PROJECT COMPONENTS & IMPORTANT MILESTONES

1. Project Components

The various components of the project are:

▪ MRO / M&E System Implementation Strategy

▪ Detailed design, plan and the blue print

▪ Power user, end user and role based access management

▪ Infrastructure evaluation and recommendations for upgrade

▪ Monitoring the project

▪ System Customization

▪ Data migration

▪ System Testing

▪ Performance Tuning and Acceptance Testing

▪ Technical training and End User Trainings

▪ Cutover

▪ Post Cutover Support

2. Phase-wise Objectives

The following are the phase-wise objectives of the project:

2.1. Implementation Strategy

▪ Implementation strategy shall be adopted after due consideration to project

scope, applicable constraints and magnitude of business improvement goals.

Bidder must provide detailed implementation methodology.

▪ PIAC at its discretion may interview the nominated consultants to assess their

technical expertise and reserves the right to accept a consultant or ask for

replacement of any or all consultant. PIAC at its discretion may also ask for

replacement of any consultant at any stage of the project if PIAC considers that

the said consultant is engaged in questionable activities or the performance of

the consultant is not at par with required standard.

▪ Implementation of procedures and controls for a reasonable level of systems

security, audit ability, confidentiality, reliability, integrity, and business continuity.

▪ Conversion/ Migration of historical and live data, efficiently and accurately.

▪ Smooth and seamless transition to new systems without any disturbance to the

ongoing operational activities of PIAC.

Page 11 of 189


▪ Prepare conceptual design and highlight parameters that will be configured in the

MRO / M&E system in accordance with PIA business requirements. It should

also include complete workflow for transaction approvals and escalation.

▪ Provide integration solutions where MRO / M&E SYSTEM will be integrated with

Oracle ERP applications and other applications running in PIA as described in

Section A, sub-section A5-1.

▪ The vendor has to ensure that all software supplied is free from defects/ bugs/

flaws/ security holes etc. Warranty periods for hardware/software should be

clearly mentioned.

▪ Smooth transition from existing related applications to the new MRO / M&E

solution.

2.2. Training

▪ Preparation of the user community for change through appropriate knowledge

transfer and end- user training.

▪ Prepare and implement a comprehensive training plan to train the trainers/power

users, technical users end users.

▪ Gain acceptance for new systems by actively involving key users in driving the

acceptance testing process and achieving cut-over to the new environment.

▪ Provide a sufficient number of properly qualified MRO / M&E system experts for

each specific area mentioned in the RFP. These should cover – as a minimum –

experts having implementation experience in airline of size comparable to PIA in

engineering areas.

2.3. Post Implementation Support

▪ At no extra cost to PIAC, Contractor will provide a team of certified experts to be

stationed at PIA locations for post implementation support for a minimum period of

six months preferably to ensure optimum and seamless operations of systems and

processes.

▪ Specify a detailed support program and mechanism.

▪ Contractor must provide at least Three years post implementation warranty for

software and hardware. The Contractor has to ensure that all software and

hardware supplied are free from defects / bugs / flaws / security holes, etc.

Page 12 of 189


▪ Warranty periods for hardware / software should be clearly mentioned and must be

accordance with section D, subsection D5

▪ Any discrepancies, mismatches and resource constraints experienced during the

support period which were not specified in the Proposal will be responsibility of the

Contractor.

A4. Product Requirement (MRO / M&E Package)

1. Overview of Solution Requirements

PIAC desires to procure an MRO / M&E Solution for PIAC’s engineering business needs

which would comprise the following: -

▪ An MRO / M&E Package which is well integrated with Oracle ERP and

interfaced with applications used in Flight Operations, Corporate Safety &

marketing planning.

▪ Add-on or Custom Built Applications shall be acceptable if minimum.

▪ Future/Trending Value added modules and add-ons.

▪ Easy and cost-effective transformability of the MRO / M&E solution into an

MRO IT Solution, in the event PIA desires to transform the Engineering &

Maintenance into an independent business unit (an MRO).

The solution to PIAC’s business needs should cover all the features that marketplace is

widely offering in airline industry and must meet the specific needs of PIAC. Bidders are

expected to match the requirements to the features/functionality in a cost-effective way.

To that end, it is expected the Technical Proposal submitted in response to this RFP

Document will clearly describe how the Bidder expects to meet the business needs of

PIAC.

Further, Bidders are expected to suggest solutions that will require minimum customization

to bring upon the best industry processes & practices, and minimum modification or add-

ons, maximum or completely seamless integration between applications, lower systems

implementation risk, while at the same time providing the best possible performance at an

economical price.

Bidder shall present a written technical proposal to address the requirements in the

following Sections. Proposals must declare any requirements the Bidder cannot satisfy.

Sufficient details should be included to demonstrate the Bidder’s knowledge of the Project

and their ability to satisfy each requirement.

Page 13 of 189


2. General Requirements

The following narrative represents a summary of the general requirements envisioned by

PIAC in the MRO / M&E Solution.

2.1. Common Characteristics

Common characteristics represent capabilities that should be shared by all functional

areas of the MRO / M&E Solution. They are to be considered along with the more

specific functional requirements that follow in the design of a system.

2.2. Integration

The MRO / M&E software should support modern “best industry practices”, with data

located in one integrated system shared across all organizational units. The

software should support enterprise-wide business processes with a goal of

eliminating multiple handling of data and increasing data accuracy. The proposed

MRO / M&E System should be capable to integrate with Oracle ERP applications

and to interface with existing applications running in PIA (refer Section A5-1).

2.3. Configuration

PIA desires to procure a system that will require minimum software modification to

meet its business requirements. The software should allow for easy tailoring and

customization to meet those requirements without changing software code or

requiring add-on changes to parameters, software switches, processing rules, and

other tailoring approaches may be acceptable. The tailoring should be accomplished

in a way that does not adversely impact the future installation of system upgrades

released from the IT solution provider.

2.4. Technology Interfaces

The Bidder should provide standard application programming interfaces, tools and

methodologies that allow future releases to accommodate interfaces without

reprogramming. A standard approach to interfaces should be employed to avoid

multiple, unique approaches for different systems. The Bidder will have to ensure, at

its own cost, availability of APIs for both its proposed system as well as system

running in PIAC. The software should be capable to integrate with applications

already running in PIAC through Web-services, Application Programming (APIs), or

through data exports in a secure and efficient manner. Bidder must ensure to provide

XML-based APIs wherever these are required.

Page 14 of 189


2.5. User Interface

The system should provide an intuitive, user-friendly, and easy-to-use interface that

minimizes the need for training. The system should have a common look and feel

across all applications. Content-sensitive / online help should be available for all

applications and should allow for customization. The system must address the

needs of infrequent or low volume users as well as those who use the system

several hours each day. The system must be equally usable from remote locations

as from the Head Office. Web-based access should be supported.

Business rules should be incorporated into the system such that the rules are applied

at the time information is entered into the system. The system should identify entry

errors, inconsistencies or logical disorder at the time data is entered. Processing of

the transaction should be suspended and/or re-routed to resolve the problem in “real

time”. Any unsuccessful transaction due any reason, should be notified and

prompted to the user for re-entry.

2.6. Security & Authorization

The system must support multiple levels of security. This includes protecting certain

fields from unauthorized access. In addition, access to certain functions and data

must be protected until they are approved by PIAC’s concerned policy makers.

Changes in assignment or termination should automatically trigger a review of the

employee’s security privileges. Comprehensive logs of transactions and security

incidents must be maintained for auditing purposes. System should provide

authorization, authentication, integrity and non-repudiation facilities for critical

transactions. System should be capable to maintain logs etc. System should be

capable of secure remote login. System should support electronic signature and time

stamp etc.

2.7. Reporting / Inquiry

The system must include comprehensive reporting tools that allow for easy access to

authorized data. Executive interfaces to the data with “drill down” capability to

examine details should be included in the reporting tools. It should also be possible

to create reports that reflect status as of a specified point in time. Standard reports

should be included that will serve as models for customized reporting as well as

provide for basic functional reports. Report wizards or similar techniques should be

available to guide users through report creation. The system must be designed such

that reporting activities do not compromise the responsiveness of the interactive

system.

Page 15 of 189


Reports should be formatted to print on local PC and LAN attached printers as well

as on centralized high-speed printers. It should be possible to deliver fixed reports to

users on a pre-determined schedule to be reviewed online, to be retained online or

to be printed at the user’s discretion.

The system should be able to demonstrate useful demographic and forecasting

capabilities; support text based searches and provides departments the ability to

develop ad hoc reports at their discretion. The system must include a data

dictionary or similar provision to allow non-technical users to identify the appropriate

data elements for inclusion in their reports.

2.8. Data Analytic Tools

PIAC desires decision support tools and information bases that are fully integrated

with the system to facilitate strategic planning, tactical operations and organization-

wide analysis.

The system should support the easy movement of data to common packaged PC-

based applications such as Microsoft Office and text files.

The system should include the ability to locate information / guidance material or text

through a search capability on relevant historical maintenance records of

aircraft/engine/components.

The system should be capable of producing “what if” scenarios to support decision-

making.

2.9. Communication

The system should foster information sharing at all levels of the organization. For

example, policy directives and goals should be incorporated into engineering

maintenance planning process; various functional units of engineering and other

departments should be able to share required information e.g. schedules, material

requirements and job specifications etc.

2.10. Flexibility

The system should be easily reconfigurable to respond to changes in business

practices, policy directives, organization structure, statutes and regulations. As

business requirements change, the system should also change to support the new

requirements. Flexibility should extend both to enterprise-wide as well as industry

specific practices.

Page 16 of 189


2.11. System Availability

Overall it should be a highly available solution. It must be available for access by

authorized personnel from anywhere at any time of the day or night (24 x 7

availability). The system must be equally usable from remote locations as from the

Head Office.

2.12. Transaction Timing

The system must support real time processing. Changes to data or the status of

processes should be immediately available in the system. System operations should

not artificially constrain the business processes supported by the system.

The system must support effective time/date stamping for transactions, including

both future and retroactive changes. The authority for such transactions must be

included in the security capabilities of the system with access roles and audit trails.

The assignment of a retroactive date must generate the changes required to bring

the system up to the current date.

2.13. Online Documentation and Training

The system must include customizable online documentation and training materials

such as context-specific help, search capability, business process documentation

and process maps.

2.14. Storage/Record Retrieval

Record collection and retention is an important organizational requirement. The

ability to easily archive, retain and access records is required. Records retention

procedures must allow information to be stored in a way that can be accessible

indefinitely.


System provided must be secure and meet all standard security requirements i.e.

Identification, Authentication, Authorization and Integrity. System should allow

implementation of industry standard security policies and capable to evolve to meet

security challenges, provide roles based access, and audit trails for the system

controls and transactions.

Page 17 of 189


3. Technology Requirements

3.1. New Technology

The system should be designed in such a way as to easily allow the incorporation of

new technologies, as they become available.

3.2. Multiple Environments

In addition to the production environment, the system must support independent

copies for training, development, and quality control / test. These environments must

be sufficiently isolated from production and from each other so that operations in one

environment will not affect those of another.

The environments will be employed as follows:

▪ Production – all production processing will be performed in this environment.

▪ Development – all development activities including unit and system testing will

be conducted in this environment.

▪ Quality Control / Testing – after all development unit and system testing has

been completed, this environment will provide a system for divisions/units to

check the quality and testing of enhancements/modifications before they are

“accepted” into production.

3.3. System Performance

The system must be responsive and available. The system should support rapid fail-

over or redeployment in the event of problems or planned maintenance. Ninety-nine

percent of all fail-over events must take place in less than five minutes. Any volume

(batch) processing must not interfere with online responsiveness or availability.

3.4. Archive and Purge

The system must support the periodic archival and purging of unused or obsolete

information. Archived information should be available for historical reporting. The

system should remain continuously available during archiving/purging

3.5. Recovery

The system must automatically recover to the last complete prior transaction in the

event of a failure. The system must clearly indicate to the user that a transaction

Page 18 of 189


failed and that it must be re-entered. Recovery must occur without operator

intervention. Bidder must provide contingency and back-up recovery procedures with

guaranteed SLA (Service Level Agreement).

3.6. Backup / Recovery and Reorganization

The system must provide for the unattended daily backup of all information and data

to a media that can be stored offsite for disaster recovery purposes. Backups must

not prevent the system from being available at all times and must not disrupt system

operations. Database reorganizations should not significantly impair the availability

of the system.

3.7. Print Management

The system should provide a method for managing the print environment for report

distribution so that reports are directed to the appropriate print facility. Both high

speed centralized printing facilities as well as local LAN-based printing facilities will

be employed. Users should be able to print reports and documents on local printers.

3.8. Fallback Solution

In case the system or parts of the system is not operative, a manual or semi-manual

fallback solution to be developed, to continue the MRO / M&E operation. After restart

of the system. It must be possible to update the system accordingly.

3.9. Ability for system and license updates

The bidder should guarantee that the provided MRO / M&E Package’s customization

or modification shall be ready for any future updates. This guarantee shall also be

given for any underlying software such as DBMS, Operating System, Network

Management and other tools. Also, the Bidder may give further advices updating the

system to major or minor releases. It is in PIAC discretion to follow the advice.

3.10. Technology Architecture

The Contractor should provide recommendations of the technology architecture

under which the proposed MRO / M&E Package will operate, with the following

features preference:

Page 19 of 189


▪ N-tiered Client/Server architecture incorporating thin presentation-logic-client

communicating with client-neutral, server-based applications, communicating with

the database

▪ Thin client, for remote users

▪ Applications distributed at servers located at Head Office

▪ Centralized database, located at Head Office

While designing the technology architecture, the Contractor should ensure that the

following are kept under consideration:

▪ Solution should be scalable with complete platform independence – PIA does not

intend to be tied down to a single platform

▪ Solution should be effortlessly portable from one system to another

▪ Should provide support for different flavors of UNIX, Windows etc.; however, it

should be a totally interoperable solution

▪ There must be open source support. In this context, the Contractor must specify

the current scenario vis-à-vis the solution offered and the future roadmap

▪ Optimization of licensing costs for the platform software

▪ PIA’s existing Local and Wide Area Network, and minimization of Wide Area

Network bandwidth requirements,

▪ Simplicity of System Administration and Operations,

▪ Ease of business continuity planning and execution.

▪ Cloud based hosting capability

Contractors should present a number of architecture options, providing pros and

cons of each option, as well as the Contractors recommended option.

3.11. Server Hardware

a) The Contractor should provide both its minimum and optimum configuration

requirements for Application and Database Servers to run the MRO / M&E Package

and other applications, consistent with the MRO / M&E features and proposed

technology architecture (3.10 above), and multiple environment requirements (3.2

above). The recommended configuration should cater for the existing load as well

as annual volume growth of 10-15% for the next five years. The configuration

should be capable of retaining data for at least eleven years (that is, current year

plus ten years’ historical record). The solution must be redundant, reliable and

consistently available to allow uninterruptible 24x7 operations.

b) The main servers will be housed in PIAC’s Information Technology Department.

The production server configuration should include redundant (RAID-5) data

storage (including SAN) and multiple processors and cater for compatibility with

PIAC’s existing LAN / WAN environment. The Contractor should take into

Page 20 of 189


consideration the areas of performance and scalability, reliability and fault tolerance

while recommending Server configurations.

c) Contractor must provide performance guarantees of the solution under different

Contractor must provide performance guarantees of the solution under different

during overload, during partial system failure, etc.

d) Optionally availability of cloud based solution is required with price and

methodology.

e) PIA reserves the rights to choose the options of:

• Purchasing of new Hardware

• Up-gradation of existing Hardware

• Adaptation of Cloud technology

3.12. Systems and Network Management Tools

Bidders are required to recommend suitable Systems and Network Management

Tools. The Systems Management Tools should ensure proper planning,

configuration, and problem handling of IT resources and support such tasks as: -

▪ Defining, resolving, and managing problems;

▪ Operating networks and multi-vendor systems;

▪ Distributing and managing software and data;

▪ Controlling operations;

▪ Planning and managing performance;

▪ Administering security;

▪ Maintaining asset information; and

▪ Planning for the future capacity of systems.

3.13. Data Support

The solution should be able to support multiple data types – text, image, voice,

video, 3D animation, etc.

It should be able to support data upload to and download from different systems in

multiple formats. Besides simple upload / download facility it should also be able to

communicate and support data interchange with mobile devices such as cellular

phones, handheld terminals, PDAs, etc. It should also be able to support other

devices such as scanners, barcode readers, biometric devices, card readers, RFID

devices, etc.

Page 21 of 189


Support for important messaging / data formats / standards must include, as a

minimum, Aircraft Communication Addressing and Reporting System (ACARS),

SITATEX, ASCII, SMS, XML, Spec 2010, S1000D, MS-Office, Lotus Notes, etc.


The system supports authentication methods that will assure that only authorized users are able to access protected data and transactions.

These include support for:

a) Digital Signatures

b) PKI Infrastructure

3.15. Web-enablement

The proposed System should be Internet ready and allow web-enabled access to

users from anywhere across the world through a web portal. It should also be

compliant with the Service Oriented Architecture (SOA).

3.16. Workflow

The proposed System should be capable of providing Workflow functionality to users by which information and requests could be automatically routed to the concerned levels for approval.

3.17. Others

Besides above –mentioned characteristics the proposed MRO / M&E SYSTEM

should also be capable of:

▪ Supporting multi-currency

▪ Supporting user defaults

▪ Supporting user defined screens/dashboards.

▪ Supporting multiple date formats

▪ Providing easy development of user defined reports

▪ Supporting user defined fields

▪ Scheduling of jobs for unattended operations

▪ Maintaining effective dates of master file data

3.18. Mobile Technology Support

Solution provided by bidders must be compatible / available on all mobile (cell phone) and

iPad/tablets.

Page 22 of 189


A5. PIA Existing Systems, Applications& Infrastructure.

1. EXISTING SYSTEMS

This sub-section describes those applications & systems which are utilized &

accessed for Maintenance & Engineering functional requirements or for which

information interchange / interface mechanism exists

1.1 Oracle ERP Main business application suite

1.2 AIMS Airline Information Management System

1.3 Sabre Products Schedule Planning, Slot/Fleet Manager System, Air

Vision etc.

1.4 AirOps System PIA may acquire any new AirOps System

1.5 Any other software Will be decided at the time of requirement gathering

➢ It is required that the proposed MRO/M&E to integrate with Oracle ERP

in a seamless manner. It is also required that MRO / M&E system be

interfaces with AIMS & Sabre applications, in order to provide

maintenance planning functionality.

1.6 PAMMIS (PIA Aircraft Maintenance Management Information System)

➢ This is the legacy system, developed in-house & currently under used in

Engineering & Maintenance department, and which PIA intends to replace with

best of the breed MRO / M&E System.

Page 23 of 189


2. DETAILS OF EXISTING SYSTEMS REQUIRING INTERFACE

2.1. Oracle ERP

Oracle ERP is the core business application responsible to manage major airline

business areas. i.e.;

a) Finance

b) Budgeting,

c) Purchasing & Logistic,

d) Human Resources,

e) Training & Qualifications

f) Safety Management System

➢ Contractors are required to provide seamless integration with MRO / M&E

solution.

2.2 AIMS (Airline Information Management System)

AIMS are Windows 2000/2003 client-server based software for airline crew, aircraft, and

flight management and operations control. The proposed MRO/M&E solution is required

to be interfaced with AIMS to cater to Maintenance Planning & Scheduling.

Modules requiring Interface

• Aircraft scheduling and assignment

• Movement and control

AIMS at PIA

Following is an overview of how AIMS is being used at PIA:

• Commercial Planning Section (CPS) prepares flight schedule for next one month in

Sabre AirFlite Application. Copy of flight schedule is sent to the Engineering

department to ensure Aircraft availability.

• Signed copies are sent back to CPS regarding confirmation of Aircraft availability by

engineering department.

System Related Information

Application Category Acquired System

Operating System Windows 2000 or 2003

Database Oracle 9i

Front End Delphi , C-Sharp

Application Source

Code

Not available. Any changes to standard application are made by vendor upon

request.

APIs

Not available. The only interface available is known as AIMS Report Generator.

All customized reports developed by PIA IT department are published through

this interface, which can be accessed by AIMS users through AIMS Menu.

Page 24 of 189


2.3 SABRE AIROPS SUITE

Introduction

AirOps provides centralized, real time access to critical data such as flight, passenger,

crew, maintenance, aircraft, airport, weather, payload and navigational, as well as fuel

data. Currently PIA is in the process of implementing this application suite. The

proposed MRO / M&E Solution is required to be interfaced with

this solution.

Currently PIA is using the following modules:

• Sabre Dispatch Manager (used by Flight Dispatch Section)

• Sabre Movement Manager (used by Flight Control Section)

Sabre Dispatch Manager (Flight Planning)

It enables Flight Operations department to operate its own

dispatching and flight planning system. It interfaces with

virtually all passenger reservations and message switching

systems and provides centralized functionality of mainframe

dispatch systems in a flexible client / server setting.

Sabre Movement Manager

It enables PIA to monitor and schedule daily maintenance and flight operations. It

uses a Gantt chart to graphically show flight leg information from a central database.

This module presents information about current operations and maintenance events,

which assist in evaluating problems and determining cost-effective solutions.

Additional modules included in the system.

• The Maintenance Routine module

• The Sabre EC – slots real time slot request and management module

• The browser-based Flight Information Display System provides real-time updates

of the latest flight departure and arrival information.

Information Flow

• Thereafter, following information is updated / tracked through this application:

▪ Flight departure and arrival time reporting

▪ Any changes in the flight schedule (delays, cancellations, diversions, etc.) are updated in the system by Flight Control Section.

• Aircraft maintenance information is also updated in the system. This assists the

Flight Dispatch Section to prepare flight schedule in accordance with fleet

availability.

Sabre AirOps

Maintains;

- Flight

Departure/Arrival

Time

- Passenger

- Crew

- Aircraft

Maintenance

- Weather

- Payload

- Navigational &

Fuel Data

Page 25 of 189


2.4 PAMMIS

The existing system which will be replaced by MRO / M&E solution. This information is

provided

Further details of some of in-house Engineering application is as under which would

particularly be useful in determining the data migration process.

Following are the main functionality which exist in PAMMIS system

• Tech. Log / Fleet Performance

• Rotables Management

• Maintenance Program & Task Cards

• Outsourced Maintenance

• Configuration Management

• AD/SB Management

• Man-hours Planning

Module /

Application

Name

Purpose / Details Hardware

Platform

Programming

Language

Operating

System

Database /

File

Structure

PAMMIS (PIA

Aircraft

Maintenance

Management

Information

System)

Tracks the

movement of aircraft

parts that come to

Engineering

Department for

maintenance

IBM

MP2003 VisualGen

VM/ESA

VSE/ESA DB2/VSE

Page 26 of 189


3. EXISTING INFRASTRUCTURE

3.1 Servers

The IT Department at PIA maintains a number of servers and storage arrays to

support various applications. Some of these applications have been developed in-

house while some have been acquired from third-party vendors. A certain number

of applications are also hosted externally.

After implementation of ERP most of the small isolated software are replaced with

ERP, resulting reduced the number of ERP server. Currently PIA is using Oracle

Exadata and Exalogic machine to maintain its database and ERP application

respectively.

The block diagram shown below represents how different applications and modules

are connected to the 10 GBPS backbone:

Page 27 of 189


3.2 ERP Servers and DR Site

Below mentioned picture is showing the architecture of PIA ERP servers and its

connectivity with DR site.

3.3 Connectivity

The fundamental purpose of a communications system is the exchange of data

between two parties. Communications networks are designed by interconnecting

a variety of devices. This is done to help share the information and make

efficient use of common resources available within an organization.

A high-level block diagram representing the PIA network is given below:

Page 28 of 189


3.3.1 Local Area Network (LAN)

The PIA LAN is centered at the Computer Centre building situated next to PIA Head

Office, in the vicinity of Jinnah International Airport. It is based on a fiber- optic

backbone and serves different locations as follows:

3.3.2 Wide Area Network (WAN)

PIA also supports major WAN connectivity linking all its regional and local offices to

PIA Computer Centre. The WAN setup is being done in two phases as follows:

Page 29 of 189


SECTION B

INSTRUCTIONS TO BIDDERS (ITB)

Page 30 of 189


B1. Instructions for Bid Submission

1 Introduction /Scope of Bid

The Bidders are invited to submit a detailed Technical Proposal and an item wise

Financial/Commercial proposal for Products and Services required as per the

requirements detailed in the bidding documents.

The assignment may be implemented in accordance with sequence as defined in

section A (A3) in the RFP or in parallel as per critical path identified by Bidder and

agreed by PIAC. The performance of the Bidder under each set of tasks must be to

PIAC’s satisfaction1 . In each case Bidder shall complete task satisfactorily before

initiating next sequential task.

The Bidders must familiarize themselves with local conditions and take them into

account in preparing their proposals. PIAC will provide the inputs specified in the RFP

and reasonably assist the Bidder in obtaining administrative licenses and permits

needed to carry out the project, and make available relevant project data and reports.

However, procurement of licenses, permits etc. shall not be PIAC’s responsibility.

By submitting a Proposal, the Contractor agrees to be legally bound by the terms and

conditions set out in this RFP. The Proposal will be considered as a binding offer from

the Contractor subject to acceptance by PIA.

1.1 Eligible Contractors

Original Solution Providers /authorized implementation partners / joint ventures are

eligible to participate in the bid. In case of joint ventures, Lead Contractor to be

specifically defined alongside partners. The Lead contractor would take the entire

responsibility of the submitted bid. Offers received through

brokers/agents/intermediaries shall not be considered.

1.2 Products and Services

i. Phrase “MRO / M&E Solution” is synonymously used as “MRO / M&E Package”

or “MRO / M&E System”, and means that all of the

products/solutions/software/training/licenses/ and related services to be

provided by the selected Bidder under the contract (as per the bidding

documents)

ii. The word “company” used in this section (B) & section (G), means “Pakistan

International Airlines Corporation Limited”

1PIAC will issue a completion certificate for each stage and a final completion certificate on completion of

the project.

Page 31 of 189


1.3 Cost of Bidding

The Bidders shall bear all costs associated with the preparation and submission of

its proposal, and Pakistan International Airline, hereinafter referred to as “PIAC”,

will in no case be responsible or liable for those costs or any of the losses to the

bidder, regardless of the conduct or outcome of the bidding process.

2 The Request for Proposal Document

2.1 Content of RFP Documents

The contents of the RFP Documents are listed below and should be read in

conjunction with any addenda issued in accordance with ITB:

Section A Project Details

Section B Instructions to Bidders

Section C Product Detail (MRO / M&E Package and Add-Ons)

Section D Service Requirements

Section E Product Requirements (Others)

Section F Hardware Requirements

Section G Bidder’s Qualification, Experience& Evaluation

Section H Requirements Compliance Matrix.

Section I Completion and Compliance Checklist.

2.2 Contractors must examine all instructions, forms, terms, specifications and

other information in the RFP Documents. Each Contractor by submitting its

proposal shall be deemed to have satisfied itself as to all the conditions and

circumstances affecting the scope of work and bid amount / contract price.

2.3 Failure to furnish all information required by the RFP Documents or to submit a

Proposal not substantially responsive to the RFP Documents in every respect

will be at the Contractor‘s risk and may result in the rejection of their Proposal

and the Contractor shall not hold PIA liable for such rejection in anyway

whatsoever. PIA reserves the right to verify at its sole discretion any or all

information submitted in response to the RFP Document. Any false information

or misrepresentation or non-disclosure may result in rejection of the entire

Proposal

3 Clarification of RFP Document

PIAC has made every effort to make the RFP Document as clear as possible. However,

in a project of this size and complexity, Bidders may need more clarifications.

Bidders may request for clarification on any of the RFP documents up to seven days

before the proposal submission date. Any request for clarification must be sent in

Page 32 of 189


writing by paper mail, cable, telex, facsimile, or electronic mail to the PIAC’s address

indicated in the RFP. PIAC may respond by cable, telex, facsimile, or electronic mail

to such requests and will send written copies of the response (including an explanation

of the query but without identifying the source of inquiry) to all parties who intend to

submit proposals.

Contact Address


Supply Chain Management (Store Building)

PIA Head Office

Airport, Terminal-1

Karachi 75200

PAKISTAN

Ph: +92-21-99044423


4 Amendment to RFP Documents

4.1 PIA may modify the RFP Documents by issuing addenda, for any reason, and at any time prior to the deadline for submission of Proposals. Any addenda to the RFP Documents shall be considered part of the RFP Document.

4.2 All Contractors will be notified of the addenda in writing by newspapers, email,

letter or facsimile, all such Contractors shall confirm the receipt of such

addenda to PIA and it shall be binding on them.

To allow Contractors reasonable time to take any addenda into account in preparing

their Proposals, PIA may, at its own discretion, extend, as necessary, the deadline

for the submission of proposal.

Page 33 of 189


5 Preparation of Proposals

5.1 Language of Proposals

Proposals and all correspondence and documents relating to the proposals

exchanged by the Bidders and PIAC shall be in English.

5.2 Documents Comprising the Proposal

Bidders will be required to submit separate proposals along with implementation

plan for Complete MRO / M&E Implementation each comprising of following two

proposals.

➢ Technical Proposal (one Original and one Copy “Soft Copy and Hard Copy)

➢ Financial/Commercial Proposal (one Original and one Copy)

a) The relevant completed “Proposal Form” and all Price Schedules as included in

Section B, Subsection B3 – Template Forms, completed and duly signed.

b) Bid security furnished in accordance with ITB Sub-section 8;

c) A full description of the technical solution to the business requirements

described in Sections C – Product Requirements (MRO / M&E Solution & Add-

ons), Section D – Services Requirements and Section E – Product

Requirements (Others).

d) The completed Requirements Compliance Matrix (Section H), Completion

Checklist & Compliance Checklists (Section I, Subsections I1 to I4).

5.3 Technical Proposal

In preparing the Technical Proposal, Bidders are expected to examine the

documents constituting this RFP in detail. Deficiencies in providing the information

requested may result in rejection of a proposal.

While preparing the Technical Proposal, Bidders must give particular attention to

the following:

▪ If a Bidder considers that it does not have all the expertise for the assignment, it

may, subject to PIAC’s prior approval, obtain a full range of expertise by

associating with individual Bidder and/or other Bidders or entities in a joint

venture as appropriate. Bidders may associate with other parties invited for this

assignment (through this RFP or the earlier invitation for Expression of Interest)

only with approval of PIAC.

▪ It is desirable that the majority of the key professional staff proposed by the

Bidder should be its permanent employees or have an extended and stable

working relationship with it.

Page 34 of 189


▪ Proposed professional staff must, at a minimum, have sufficient experience in the required field, preferably working under conditions similar to those prevailing in the country of the assignment.

▪ Alternative professional staff shall not be proposed, and only one curriculum

vitae (CV) may be submitted for each position.

Reports to be issued by the Bidders as part of this assignment must be in English

language.

5.3.1 Information Required

a) Detailed project plan with timeframe for task and sub task.

b) A brief description of the bidder’s organization and an outline of recent

experience on assignments of a similar nature. For each assignment, the

profiles of the staff proposed, duration of the assignment, contract amount,

and bidder’s involvement.

c) Any comments or suggestions on the Terms of Reference and on the data,

a list of products/services, and facilities to be provided by PIAC.

d) A description of the methodology and work plan for implementation of the

project.

e) The list of the proposed staff team by specialty, the tasks that would be

assigned to each staff team member, and their timing.

f) CVs recently signed by the proposed professional staff and the authorized

representative submitting the proposal. The format of CV must be as per

format attached in Section B, subsection B3. Key information should

include number of years working for the firm/entity and degree of

responsibility held in various assignments during the last ten (10) years.

g) Estimates of the total staff input (professional and support staff; staff time)

needed to carry out the project, supported by bar chart diagrams showing

the time proposed for each professional staff team member.

h) A detailed description of the proposed methodology, staffing, and

monitoring of training, if the RFP specifies training as a major component

of the project.

i) Any additional information requested in the RFP.

j) Technical team training, end-user training.

The Technical Proposal shall not include any financial information.

Page 35 of 189


5.4 Financial Proposal

In preparing the Financial Proposal, Bidders are expected to take into account the

requirements and conditions outlined in the RFP documents. The Financial

Proposal should list all costs associated with the project, further broken-down into

per module costs, costs of licenses if any, hardware, software, cost of operating

software, database software or any other software with required number of licenses

for each component of the application, operating system or any other utility

software required, cost of training, post implementation support, cost of warranties

if any etc. If appropriate, these costs should be broken down by activity and, if

appropriate, into foreign and local expenditures. Bidders must quote all prices of

their goods and services in USD only

5.4.1 Proposals must remain valid for 180 days after the submission date. During

this period, the bidder is expected to keep available the professional staff

proposed for the assignment. PIAC will endeavor to complete

discussions/clarifications within this period. However, if necessary, PIAC

may require extension in the said validity period. The proposal submitted by

the bidders shall comprise the following:

5.4.2 The relevant completed “Proposal Form” and all Price Schedules as

included in Section B3.

5.4.3 A full description of the technical solution to the business requirements

described in Sections C – Product Requirements (MRO / M&E Package&

add-ons) and Section D – Services Requirements.

5.4.4 The successful bidder will be required to furnish, on or before the date of the

signing of the contract, a performance guarantee equal to 5% (five percent)

of total value of the contract price/successful bid amount from a reputable

scheduled bank acceptable to PIAC.

The Bidder is required to deposit earnest money equal to 2% of the bid submitted

for MRO / M&E Solution implementation, with the bid at the time of submission of

the bid. The earnest money shall be furnished in the form of a pay order of a

scheduled bank in favor of PIAC. The earnest money will be returned to

unsuccessful bidder for which unsuccessful bidder has to submit a written request.

The earnest money deposited by the successful bidder will be kept as security

deposit until project is completed satisfactorily. No interest will be payable on

earnest money to successful or unsuccessful bidder.

6 Proposed Prices

6.1 The Contractor must provide the prices of the proposed Solution using the

Price Schedule Templates provided in Subsection B3.

Page 36 of 189


6.2 Prices provided on the Price and Recurrent Costs Schedules (as per

Templates) shall be listed individually in the following manner:

6.2.1 Unit and total prices of products offered, inclusive of all taxes and duties paid.



6.2.4 Prices for implementation services.

6.2.5 Prices for training Master Trainers, Power Users and End Users etc. local and

foreign component to be mentioned separately.

6.2.6 Recurrent costs after the expiration of the warranty period on the Recurrent

Costs Form, as follows:

6.2.6.1 The cost of all software updates, recurrent licensing fees, and any

other items needed to operate the MRO / M&E Solution, plus any other

recurrent supply of products specified in the RFP Document

6.2.6.2 The cost of all maintenance and technical support services, and any

other recurrent services specified in the RFP Document, including all

taxes payable by the Bidder thereon.

6.2.6.3 Cost of post implementation support along with number of experts

stationed at PIAC premises.

6.2.7 Totals of Products, Services and Recurrent Costs, on the Proposal Price

Summary Form.

6.2.8 There should be no hidden costs. Any cost not mentioned and to be incurred

later for proper fault free execution of the project is the responsibility of the

Bidder.

6.2.9 All costs are to be quoted in USD and must be fixed.

6.2.10 Payment will be milestone based as per format attached in Section B,

subsection B3. Bidder is required to provide the confirmation if agreed with

payment schedule.

6.3 Contractor‘s separation of price components in accordance with ITB Subsection

6, item 6.2 will be solely for the purpose of facilitating the comparison of

proposals and will not in any way limit PIA‘s right to contract on any of the terms

offered.

Page 37 of 189


6.4 Prices quoted by the Contractor shall be fixed maximum prices during the

Contractor‘s performance of the contract. Proposals submitted with adjustable

price quotations will be rejected and the Contractor shall not hold PIA liable in

anyway whatsoever for such rejection.

7 Documents Establishing Contractor’s Eligibility and Qualifications

The documentary evidence of the Contractor’s qualifications and ability to perform

the contract if its proposal is accepted shall establish to PIAC’s satisfaction:

7.1 That, in the case of a Contractor not doing business in Pakistan, the Contractor

will be able (if awarded the Contract), to carry out the installation,

implementation, support, maintenance, and other service obligations

prescribed in the RFP Documents. Documentary evidence supporting the

aforementioned must be provided;

7.2 That the Contractor and any Sub-contractors have the financial, technical, and

staff capabilities to support the MRO / M&E Solution, and have a successful

performance history, appropriate for their role in fulfilling the contract.

7.3 Each Sub-contractor must sign a Letter of Authorization / Joint Venture

Agreement authorizing the Lead Contractor to act on its behalf. A copy of this

Letter of Authorization / Joint Venture agreement must be submitted along with

the Proposal. The Lead Contractor shall be completely responsible for all

contract services to be performed. The Lead Contractor must demonstrate

that all aspects of this RFP Document have been carefully and completely

considered.

7.4 No substitution of a Sub-contractor shall be allowed during the term of this

contract. Failure of a Sub-contractor to perform as expected shall not relieve

the Lead Contractor of its duties to perform on the whole requirement and the

Lead Contractor shall be liable for any / all loss(es) / damage(s) that PIA may

suffer as a result of failure of a Sub-contractor to perform any / all of its

obligations under this contract.

8 Document Establishing Products, Services Eligibility & Conformity to RFP

8.1 Pursuant to ITB Sub-section 5.2, the Contractor shall furnish, as part of its

Proposal, documents establishing the eligibility and conformity to the RFP

Documents of all products and services that the Contractor proposes to supply

under the contract. This includes all the information/evidences needed to

evaluate the contractor as set forth in section G (Bidder’s Qualifications, Experience

& Evaluation).

Page 38 of 189


8.2 The documentary evidence of conformity of the products and services to the

RFP Documents may be in the form of written descriptions, literature, diagrams,

certifications and client references, including:

8.2.1 A detailed description of the essential technical and performance

characteristics of the products;

8.2.2 An item-by-item commentary on PIAC’s Product and Services Requirements, as detailed in Sections C, D & E, demonstrating the substantial responsiveness of the proposed solution to the specifications provided; and

8.2.3 A confirmation that the Contractor shall accept responsibility for the

successful integration and interoperability of all proposed products and other PIA systems as required by the RFP Documents. (refer Section A, sub-section A5-1)

9 Bid Bond

9.1 Pursuant to ITB Sub-section 9, the Contractor shall furnish, along with its

Financial Proposal, a bid bond for 2% (two percent) of the total amount of the

Products, Services and Support Prices.

9.2 The bid bond is required to protect PIA against the risk of the Contractor’s

conduct that would warrant the security’s forfeiture, as per ITB Sub-section 9,

item 9.7.

9.3 The bid bond shall be denominated in USD, shall be valid for One Hundred

and Eighty (180) days beyond the validity of the Proposal, and shall be in one

of the following forms:

9.3.1 A bank guarantee by a Pakistani Scheduled bank of the Contractor’s

choice, in the form provided in the RFP Documents;

9.3.2 A Pay Order / Demand Draft drawn on a Pakistani Scheduled bank.

9.4 Any Proposal not secured in accordance with ITB Sub-section 9, items 9.1

and 9.3 will be rejected by PIA and the Contractor shall not hold PIA liable in

anyway whatsoever for any such rejection.

9.5 Unsuccessful Contractors’ bid bond will be discharged or returned as

promptly as possible after the expiration of the period of Proposal validity

prescribed by PIA pursuant to ITB Sub-section 10.

Page 39 of 189


9.6 The successful Contractor’s bid bond will be discharged upon the Contractor

signing the contract, pursuant to ITB Sub-section 22, and furnishing the

performance guarantee, pursuant to ITB Sub-section 21.

9.7 The bid bond may be forfeited:

9.7.1 If a Contractor attempts to withdraw its Bid before the date stipulated in

the RFP for the validity of the Bid or any extension in this date agreed

between the Company and the Contractor,

9.7.2 If a Contractor attempts to modify or amend its Bid without the approval

/ consent of the Company before the date stipulated in the RFP for the

validity of the Bid or any extension to this date agreed between the

Company and the Contractor,

9.7.3 The Contractor shall not hold the Company liable in anyway

whatsoever for the amount so forfeited by the Company.

10 Period of Validity of Proposals

Proposals shall remain valid for at least 180 days from the date of Proposal submission

or any extension thereof, prescribed by PIAC. A Proposal valid for a shorter period

shall be rejected by PIAC.

11 Tender Proceedings

For sake of clarity, the PPRA (Public Procurement Regulatory Authority of Pakistan) guidelines for Single stage – two envelope procedure, which are as follow, shall be followed.

11.1 The bid shall comprise a single package containing two separate envelopes. One envelope shall contain the financial proposal while the other one shall contain the technical proposal;

11.2 The envelopes shall be marked as “FINANCIAL PROPOSAL” and

“TECHNICAL PROPOSAL” in bold and legible letters to avoid confusion; 11.3 Initially, only the envelope marked “TECHNICAL PROPOSAL” shall be

opened; 11.4 The envelope marked as “FINANCIAL PROPOSAL” shall be retained in the

custody of PIA without being opened; 11.5 PIA shall evaluate the Technical Proposal in a manner prescribed in the RFP

documents, without reference to the price(s) and reject any proposal which does not conform to the specified requirements;

Page 40 of 189


11.6 During the Technical evaluation, no amendments in the technical proposal

shall be permitted; 11.7 The financial proposals of bids shall be opened publicly at a time, date and

venue announced and communicated to the bidders in advance; 11.8 After the evaluation and approval of the technical proposal(s), PIA shall at a

time within the bid validity period, publicly open the financial proposals of the technically accepted bids only. The financial proposal of bids found technically non-responsive shall be returned un-opened to the respective bidders; and

11.9 The bid found to be the lowest evaluated (as per prescribed criteria) shall be

accepted.

12 Submission of Proposals

12.1 The Bidder is required to submit an original and one copy of each of its

Technical and Commercial Proposals clearly mark each “ORIGINAL BID” or

“COPY OF BID”, as appropriate. In the event of any discrepancy between

them, the original shall govern.

12.2 The Technical and Commercial Proposals shall be typed or written in indelible

ink and shall be signed by a person or persons duly authorized to bind the

Bidder to the contract

12.3 Bidders are required to submit their offer in sealed envelopes either in person

or through courier. Each offer should be clearly marked as “Bid for MRO / M&E

solution” at top of the envelope.

12.4 The Technical and Financial Proposals shall be submitted in separately sealed

envelopes, each marked “Technical Proposal” and “Financial Proposal”

accordingly, and bearing the name and complete return address of the Bidder,

be addressed to:


Supply Chain Department (Store Building)

PIA Head Office

Airport, Terminal-1

Karachi 75200

PAKISTAN

Ph: +92-21-99044423


Page 41 of 189


13 Deadline for Submission of Proposals

13.1 Proposals must be received by PIAC at the address and by the time

specified in the RFP Document covering letter. Proposals received after

this deadline will be rejected and returned to the Bidder unopened.

13.2 PIAC may, at its discretion, extend this deadline for the submission of

Proposals, in which case all rights and obligations of PIAC and Bidders

previously subject to the deadline will thereafter be subject to the deadline

as extended.

13.3 PIAC reserves the right to reject any or all proposals or divide the business

in more than one bidder or not to implement the MRO / M&E solution.

14 Opening of Proposals by PIA

14.1. PIA will open all Technical Proposals at a place and time to be advised in

the covering letter by PIA. Contractors or their authorized representatives may attend the opening, and those who are present shall sign a register evidencing their attendance.

14.2. No Proposal shall be rejected at the time of Proposal opening, except for late Proposals, which shall be returned unopened to the Contractor.

14.3. The Commercial Proposals of Contractors will be opened subsequently and evaluated. Contractors will be informed of the place and time by PIA.

15 Clarification of Proposals

15.1. During evaluation of Proposals, PIA may, at its discretion, ask the Contractor for a clarification of its Proposal. The request for clarification and the response shall be in writing, and no change in the prices or substance of the Proposal shall be sought, offered, or permitted during evaluation of the Proposal.

15.2. PIA may request the Contractor to arrange site visits for its reference sites.

15.3. PIA may also request the Contractor to give “proof of concept” by developing prototypes of specific scenarios identified by PIA.

16 PIA’s Right to accept any Proposal and to reject any or All Proposals

16.1. PIA reserves the right (without limitation to any other right whatsoever) to accept or reject any Proposal, or to annul the bidding process and reject all

Page 42 of 189


Proposals at any time prior to contract award without incurring any liability to the affected Contractor or Contractors.

16.2. PIA also reserves the right (without limitation to any other right whatsoever) to award the consolidated contract in its entirety to a single Contractor or to award it in parts to more than one Contractor without incurring any liability to the affected Contractor or Contractors.

17 Evaluation &Finalization of Selection.

17.1. After receipt of proposals from the Contractors, PIA will evaluate and study the submitted proposals. PIA does not bind itself to award the contract to the lowest or to any Contractor but will take into consideration all relevant facts and aspects. Finalization of the Contract between the successful Contractor and PIA will be held in the presence of members of PIA’s Project team and Steering committee at PIA Head Office. The aim is to reach agreement on all points and sign a contract.

17.2. Having selected the successful Contractor on the basis of, among other

things, an evaluation of the total solution offered, proposed methodology (work plan), verifiable successful implementations, and proposed key professional staff, PIA expects to finalize a contract on the basis of the products and available expertise named in the proposal. Before contract finalization, PIA will require assurances that products and experts will be actually available. PIA will not consider substitutions during contract finalization unless both parties agree that undue delay in the selection process makes such substitution unavoidable or that such changes are critical to meet the objectives of the assignment.

17.3. The finalization of the contract with the successful Contractor will conclude

with a review of the agreed draft, to be signed by PIA and the Contractor, ensuring successful delivery and completion of the project. PIA and the successful Contractor will initial the agreed draft of the contract. If this process fails, PIA may invite the next Contractor for the award of the assignment. In this regard, Contractors should submit draft copies of their proposed contracts and Service Level Agreements along with their Technical Proposals.

18 Confidentiality

18.1 Information relating to evaluation of proposals and recommendations concerning awards will not be disclosed to the Bidder or to other persons not officially concerned with the process. The Bidder shall maintain complete confidentiality of its proposal and shall not disclose the proposal or any terms thereof to any unrelated person or any third party. The Bidder shall also keep confidential all its discussions and negotiations with PIAC.

Page 43 of 189


18.2 For the purpose of this RFP all Bidders receiving or responding to this RFP

are considered potential contractors and have been identified throughout the

RFP accordingly.

19 Bidder’s Profile

In assessing a potential contractor’s ability to provide the MRO / M&E System

Renewal Program solution to PIAC, PIAC is seeking details of the Bidders’

structure including:

19.1 The core activities of the business; 19.2 The products and/or services provided; and 19.3 The future Plans of the bidder.

20 Legal Binding

By submitting a Proposal, the Bidder agrees to be legally bound by the terms and

conditions set out in this RFP. The Proposal will be considered as a binding offer

from the supplier capable of acceptance by PIAC. If during the course of any

discussions or negotiations PIAC and the Bidder agrees to vary any terms or the

Proposal, the Proposal will be deemed to be amended to the extent of the agreed

variation and PIAC may accept the Proposal as deemed amended.

21 Performance Guarantee

21.1. Within five (5) working days of the receipt of notification of award of the

Contract from PIA, the successful Contractor shall furnish a Performance Guarantee for 5% (five percent) of Contract value in accordance with the conditions of Contract, using the Performance Security Form provided in the RFP document.

21.2. In case joint venture is successful in the bidding process, the Lead Member of such joint venture will be responsible to PIA for performance of obligations under the agreement as principal obligator.

22 Signing of Contract

22.1 Within four (04) working days of receipt of the Performance Guarantee in

accordance with ITB Sub-section 21, PIA will send the successful Contractor the Contract Form provided in the RFP documents, incorporating all agreements between the parties.

22.2 Within four (04) working days of receipt of the Contract Form, the successful Contractor shall sign and date the contract and return it to PIA.

Page 44 of 189


22.3 By mutual agreement in writing, the contract signature date may be postponed by up to fifteen (15) days.

23 Contacting PIA

Any effort by the Contractor to unethically influence PIA in the process of evaluating Proposals and in decisions concerning award of the contract will result in the rejection of the Contractor’s Proposal.

The Contractors submitting proposals should attach a declaration that:

23.1 They will not obtain or induce the procurement of the contract or any right,

interest, privilege, or other obligation or benefit related to the contract from PIA or the Government of Pakistan, or any subdivision or agency thereof, through any corrupt business practice.

23.2 They will not give or agree to give and shall not give or agree to give to

anyone within or outside Pakistan either directly or indirectly through any person or organization, including affiliates, agents, associates, brokers, consultants, directors, promoters, shareholders, sponsors or subsidiaries, any commission, gratification, bribe, finder’s fee or kickback, whether described as consultation fee or otherwise, with the object of obtaining or inducing pursuant to the contract or any right, interest, privilege or other obligation or benefit related to the contract in whatsoever form.

23.3 They have made and will make full disclosure of all contracts and

arrangements with all persons / organizations in respect of or related to the proposed contract with PIA and have not taken any action or will not take any action to circumvent the above declaration, representation or warranty.

23.4 They agree to pay compensation to PIA in an amount equivalent to the direct

losses to PIA, which would include the sum of any commission, gratification, bribe, finder’s fee or kickback that would otherwise have been given to PIA in the form of a concession, given by the parties submitting proposals for the purpose of corruptly obtaining or including the procurement of the contract or any right, interest or other obligation or benefit related to this contract in whatsoever form from the parties submitting proposals, if it shall ultimately be determined by a final judicial decision that the party submitting proposals has so obtained or induced the procurement of the contract, or any right, interest, privilege or other obligation or benefit related to such contract.

P

age 45

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

B2

SU

MM

AR

Y O

F R

EQ

UIR

EM

EN

TS

This

schedu

le lis

ts a

ll majo

r com

ponents

of th

e M

RO

/ M&

E S

olu

tion

to b

e p

rocure

d th

rou

gh th

is R

equest fo

r Pro

posal.

Furth

er d

eta

ils a

nd e

xa

ct s

pecific

atio

ns fo

r each ite

m a

re in

clu

ded in

the S

ectio

ns C

, D a

nd E

.

Item

Typ

e

Descrip

tion

P

roje

ct

Site

(s)

MR

O / M

&E

P

ackage

Applic

atio

n s

oftw

are

module

s to

meet th

e A

pplic

atio

ns re

qu

irem

ents

as p

er d

eta

ils in

Sectio

n C

. A

lso, a

ny A

dd-o

n re

qu

ired fo

r MR

O / M

&E

solu

tion, if a

ny

Head O

ffice

Oth

er

Locatio

ns

3rd P

arty

S

oftw

are

A

s re

quire

d b

y th

e p

rop

osed M

RO

/ M&

E P

ackage a

nd A

dd-o

n A

pp

lica

tions

Head O

ffice

DB

MS

A

s re

quire

d b

y th

e p

rop

osed M

RO

/ M&

E P

ackage a

nd A

dd-o

n A

pp

lica

tions

Head O

ffice

Hard

ware

Recom

mended c

onfig

ura

tion o

f hard

ware

and

opera

ting s

yste

m s

oftw

are

for th

e P

roductio

n

Enviro

nm

ent w

ill be p

rovid

ed b

y th

e C

ontra

cto

r and it s

hall n

ot b

e b

indin

g o

n P

IA to

pro

cure

th

is fro

m th

e C

ontra

cto

r. In

terim

Applic

atio

n / D

ata

Serv

er(s

) inclu

din

g O

pera

ting S

yste

ms a

s re

quire

d b

y th

e p

rop

osed

M

RO

/ M&

E S

olu

tion fo

r Tra

inin

g, D

evelo

pm

ent, T

estin

g a

nd Q

uality

Assura

nce

Enviro

nm

ents

will b

e p

rovid

ed b

y th

e C

ontra

cto

r at its

ow

n c

ost

Head O

ffice

Oth

ers

A

pplic

atio

n D

evelo

pm

ent T

ools

, Query

and R

eport G

enera

ting T

ools

, Syste

m A

dm

inis

tratio

n

Tools

, Opera

ting S

yste

ms, S

yste

ms M

anagem

ent T

ools

, etc

. H

ead O

ffice

Insta

llatio

n /

Imple

menta

tion

Serv

ices

Insta

llatio

n, c

onfig

ura

tion a

nd im

ple

menta

tion o

f Hard

ware

an

d O

pera

ting S

yste

m, M

RO

/ M&

E

Sta

ndard

Softw

are

, Add

-on A

pplic

atio

ns, 3

rd Party

Applic

atio

ns.

Head O

ffice

Oth

er

Locatio

ns

Tra

inin

g

End U

ser,

Po

wer

Use

r and M

ana

gem

ent

train

ing fo

r M

RO

/

M&

E,

Add-o

n and 3

rd P

arty

Applic

atio

ns, T

echnic

al tra

inin

g fo

r De

velo

pers

and A

dm

inis

trato

rs o

n A

pplic

atio

n D

evelo

pm

ent

Tools

, Reportin

g T

ools

, DB

MS

, DB

A to

ols

, OS

, Syste

m M

anag

em

ent T

ools

, etc

.

Head O

ffice

Oth

er

Locatio

ns

Data

Mig

ratio

n

Develo

pm

ent o

f Stra

tegy&

Pla

n fo

r mig

ratio

n o

f data

from

legacy s

yste

ms a

nd m

anual re

cord

s.

Head O

ffice

Recurre

nt

Serv

ices

Post-Im

ple

menta

tion s

upport fo

r thre

e y

ears

(afte

r Warra

nty

Perio

d) fo

r MR

O / M

&E

Package,

Add-o

n a

pplic

atio

ns, H

ard

ware

and 3

rd Party

So

ftware

Main

tenance a

nd

Support

All L

ocatio

ns

Page 46 of 189


B3 TEMPLATE FORMS

Notes for Contractors on the Template Forms

1. The Contractor shall complete and submit with its Proposal the Proposal

Form and the required Price Schedules and in accordance with the

requirements included in Section B, Subsection B3.

2. The Contractor should provide the Bid Bond as per the form included in this

Subsection.

3. The Performance Guarantee form should not be completed by the Contractor

at the time of their Proposal preparation. Only the successful Contractor will

be required to provide Performance Guarantee as per the form included in

Section B. PIA, however reserves the right, in case of failure on part of the

Contractor to provide the aforesaid Performance Guarantee in accordance to

the instructions as laid down in Instruction to Bidders (ITB) Section B1, sub-

section 20, within the specified time, to forfeit the bid security furnished by the

Contractor.

Page 47 of 189


Proposal Form

To:


Procurement and Logistics Building

PIA Head Office

Airport Terminal-1

Karachi 75200

PAKISTAN

Dear Sir:

Having examined the Request for Proposal Documents including Addenda Nos. [insert

numbers, if issued and applicable], the receipt of which is hereby duly acknowledged, we,

the undersigned, offer to produce, deliver, install, implement, support and maintain the

MRO / M&E Solution in full conformity with the said RFP Documents.

We undertake, if our Proposal is accepted, to implement the MRO / M&E Solution in

accordance with the Project milestones agreed with PIA.

We certify that a bid bond for 2% (two percent) of the total amount of the proposal is

submitted along with Financial Proposal.

If our Proposal is accepted, we will provide a Performance Guarantee in the form and in the

amounts, and within the times stipulated in the Request for Proposal Documents.

We agree to abide by this Proposal for a period of 180 days from the date fixed for

Proposal submission, or any extended date, and it shall remain binding upon us and may

be accepted at any time before the expiration of that period. Until a formal Contract is

prepared and executed, this Proposal, together with your written acceptance thereof and

your notification of award, shall constitute a binding Contract between us.

We understand that you are not bound to accept the lowest or any Proposal you may

receive.

Dated this ________________ day of ________________ 20______.

_______________________________________________________

[Signature] [In the capacity of]

Duly authorized to sign Proposal for and on behalf of _____________

Page 48 of 189


Bidding Organization Profile

[Provide a brief (not more than five pages) description of the background and organization of your firm/entity and each sub-contractor for this assignment.]

Page 49 of 189


Bidder’s Experience

[Using the format below, provide information on each assignment for which your firm, and each associate for this assignment, was legally contracted either individually as a corporate entity or as one of the major companies within an association, for carrying out services similar to the ones requested under this

assignment. Attach details on separate sheet if necessary.]

Assignment name:

Approx. value of the contract (in current USD):

Country/State/Province: Location within country:

Duration of assignment (months):

Name of Client:

Total No of staff-months of the assignment: (If applicable)

Address:

Approx. value of the services provided by your firm under the contract (in current USD):

Start date (month/year): Completion date (month/year):

No of professional staff-months provided by Sub-Contractor:

Name of Sub-Contractor, if any:

Name of senior professional staff of your firm involved and functions performed (indicate most significant profiles such as Project Director/Coordinator, Team Leader):

Narrative description of Project:

Description of actual services provided by your staff within the assignment:

Page 50 of 189


Description of Approach, Methodology &

Project Plan for the Project

[In order to ensure timely completion of this project, the consultant/service provider should submit a

methodology and detailed Project Plan including the estimated completion timeline of each area/sub area

of the scope]

Page 51 of 189


Team Composition and Task Assignments

[Using the format below, provide information regarding the nominated project team for this assignment

based on proposed methodology and work plan. Depending upon skill sets, experience and technology

certifications as mentioned in CV and subject to the submission of documentary evidences]

Professional Staff / Nominated Project Team

Name of Staff Position Assigned Area/Task Assigned

in this Project Skill Sets and Technology

Certification Name(s)

Page 52 of 189


Curriculum Vitae (CV) for Professional Staff

[CVs should be submitted for Nominated Project Team/Professional Staff only]

1. Proposed Position:

2. Name of Firm [Insert name of firm proposing the staff]:

3. Name of Staff [Insert full name]:

4. Date of Birth: Nationality:

5. Education [Indicate college/university and other specialized education of staff member, giving

names of institutions, degrees obtained, and dates when obtained]:

6. Technology Certification(s) Achieved [Provide name of all the technology certification achieved

by the staff]

____________________________________________________________________________________

_

7. Other Trainings [Indicate significant training since, education under 5, were obtained]:

8. Countries of Work Experience: [List countries where staff has worked in the last ten years]:

9. Languages [For each language indicate proficiency: good, fair, or poor in speaking, reading, and

writing]:

10. Employment Record [Starting with present position, list in reverse order every employment held

by staff member since graduation, giving for each employment (see format here below): dates of

employment, name of employing organization, positions held.]:

From [Year]: To [Year]:

Employer:

Positions held:

11. Detailed Tasks Assigned

Page 53 of 189


[List all tasks to be performed under this assignment]

12. Work Undertaken that Best Illustrates Capability to Handle the Tasks Assigned

[Among the assignments in which the staff has been involved, indicate the following information for

those assignments that best illustrate staff capability to handle the tasks listed under point 11.]

Name of assignment or project:

Year:

Location:

Client:

Main project features:

Positions held:

Activities performed:

13. Certification:

I, the undersigned, certify that to the best of my knowledge and belief, this CV correctly describes myself,

my qualifications, and my experience. I understand that any willful misstatement described herein may

lead to my disqualification or dismissal, if engaged.

Date:

[Signature of staff member or authorized representative of the staff] Day/Month/Year

Full name of authorized representative:

Pag

e 5

4 o

f 189

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Pro

du

cts

Pric

e S

ch

edule

Nam

e o

f Contra

cto

r

Page _

__ o

f ____

Item

N

o.

Pro

duct D

escrip

tion

Contra

cto

r P

roposal

Refe

rence

Pro

duct

Pro

ducer

Partn

er o

r Sub-

contra

cto

r R

esponsib

le fo

r S

upply

an

d

Insta

llatio

n

Quantity

Unit

Pric

e2

(US

D)

Tota

l Pric

e3

(US

D)

(1)

(2)

(3

) (4

) (5

) (6

) (7

) = (5

) x (6

)

MR

O / M

&E

Packag

e

&A

dd

-on

A

pp

licatio

ns

Subto

tal

DB

MS

Subto

tal

3rd P

arty

So

ftware

Subto

tal

Hard

ware

: Subto

tal

Clo

ud

Serv

ices

: S

ubto

tal

Oth

er P

rod

ucts

: Subto

tal

TO

TA

LS

A

dditio

nal M

RO

/ M&

E

Lic

ensin

g C

ost P

er U

ser4

Sig

natu

re o

f Contra

cto

r

-----------------------------------------------------

2Pric

es in

clu

de a

ll taxes p

ayable

by th

e C

ontra

cto

r there

on.

3In c

ase o

f dis

cre

pan

cy b

etw

een u

nit p

rice a

nd to

tal, th

e u

nit p

rice s

hall p

revail. S

imila

rly, s

ubto

tals

shall p

revail o

ver to

tals

. 4 P

rice fo

r Each A

dditio

nal M

RO

/ M&

E U

ser s

hould

be

pro

vid

ed s

epara

tely

Page 5

5 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Serv

ices P

rice S

ch

ed

ule

(Prio

r to M

ain

ten

an

ce)

Nam

e o

f Contra

cto

r

Page _

__ o

f ____

Sig

natu

re o

f Contra

cto

r

_________

____

____

____

___

___

___

5S

erv

ice

pric

es in

clu

de a

ll taxe

s p

aya

ble

by th

e C

on

tracto

r the

reo

n.

6In

case o

f dis

cre

pancy b

etw

een u

nit p

rice a

nd to

tal, th

e u

nit p

rice s

hall p

revail. S

imila

rly, s

ubto

tals

shall p

revail o

ver to

tals

.

Item

N

o.

Serv

ice D

escrip

tion

Contra

cto

r P

roposal

Refe

rence

Partn

er o

r Sub-

contra

cto

r R

esponsib

le fo

r Serv

ice

D

eliv

ery

Quantity

U

nit P

rice

5 (U

SD

) T

ota

l Pric

e6

(US

D)

(1)

(2)

(3

) (4

) (5

) (6

) = (4

) x (5

)

Imp

lem

en

tatio

n

• M

RO

/ M&

E

Package

• A

dd

-on A

pplic

atio

ns

• 3

rd Party

Softw

are

S

ubto

tal

Tra

inin

g

• M

aste

r Tra

iners

•

End

-users

•

Technic

al

• A

pps D

ev T

ool

• R

eportin

g T

ool

• D

BA

Tool

• D

BM

S

• O

pera

ting S

yste

m

• S

ys A

dm

in / M

gm

t. •

Oth

ers

S

ubto

tal

Data

Mig

ratio

n

D

ocu

me

nta

tion

Oth

er

T

OT

AL

S

Page 5

6 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Recu

rren

t Co

sts

Sch

ed

ule

(Pric

es d

urin

g th

e m

ain

tenance p

erio

d fo

r first th

ree y

ears

)

Nam

e o

f Contra

cto

r

Page _

__ o

f ____

Sig

natu

re o

f Contra

cto

r

________

___

____

____

___

___

____

_

7The a

nnual c

ost s

hould

indic

ate

the to

tal c

osts

for th

e y

ear in

clu

siv

e o

f all ta

xes.

Ma

xim

um

com

pounded c

osts

per a

nnum

afte

r exp

iratio

n o

f the

warra

nty

perio

d (in

US

D)7

Ye

ar 1

Y

ear 2

Y

ear 3

T

ota

l Recurre

nt C

osts

Main

ten

an

ce F

ee:

MR

O / M

&E

Package

Add-o

n A

pplic

atio

n

3rd P

arty

Softw

are

DB

MS

Su

b-to

tal

Recu

rren

t So

ftware

Lic

en

sin

g

Fees:

MR

O / M

&E

Package

Add-o

n A

pplic

atio

n

3rd P

arty

Softw

are

DB

MS

Su

b-to

tal

Hard

ware

main

ten

an

ce c

osts

C

lou

d S

erv

ices

co

sts

O

ther re

cu

rren

t co

sts

T

OT

AL

S

Page 5

7 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Pro

po

sal P

rice S

um

mary

Fo

rm

Nam

e o

f Contra

cto

r

P

age _

__ o

f ____

Pro

ducts

Pric

e T

ota

l S

erv

ices P

rice T

ota

l R

ecurre

nt C

osts

Tota

l T

ota

l P

roposal

Pric

e:

Am

ount in

US

D

Sig

natu

re o

f Contra

cto

r

Page 5

8 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Pro

po

sed

Paym

en

t Pla

n

Team

Mo

biliz

atio

n

10

%

Pro

ject C

on

trol B

oo

k

5%

Gap

An

aly

sis

10

%

So

lutio

n D

esig

n

10

%

Syste

m C

on

figu

ratio

n

10

%

Data

Mig

ratio

n

10

%

User A

ccep

tan

ce T

est

15

%

Go

Liv

e P

rod

uctio

n

15

%

Po

st G

o L

ive

15

%

Page 5

9 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Bid

Bo

nd

Fo

rm

BA

NK

GU

AR

AN

TE

E N

O._

_____________

DA

TE

D: _

___________________________

AM

OU

NT

: _________________________

EX

PIR

Y: _

_________________________

Pakis

tan In

tern

atio

nal A

irlines C

orp

ora

tion L

imite

d

Kara

chi A

irport

Kara

chi

BID

BO

ND

AS

PE

R T

EN

DE

R N

O. _

____________

FO

R _

___________

WH

ER

EA

S

_________________________________________________

(here

inafte

r calle

d

“the

Contra

cto

r”) has

subm

itted

to

PA

KIS

TA

N

INT

ER

NA

TIO

NA

L

AIR

LIN

ES

(h

ere

inafte

r calle

d

“the

Com

pany”)

a

bid

date

d

___

day

of

____________ y

ear _

____, fo

r the e

xecutio

n o

f the a

bo

ve w

ork

.

AN

D W

HE

RE

AS

it

is pro

vid

ed by th

is bid

th

at

the C

ontra

cto

r shall

furn

ish th

e C

om

pany w

ith security

by w

ay of

an

unq

ualifie

d b

ond o

r guara

nte

e fo

r the d

ue fu

lfillment o

f certa

in m

atte

rs re

latin

g to

this

Bid

.

AN

D

WH

ER

EA

S

________________________

_________________________

have

at

the

req

uest

of

the

Contra

cto

r

agre

ed to

giv

e s

uch s

ecurity

.

NO

W T

HE

RE

FO

RE

WE

____________________________________________ o

f ________________________________

________________________________________________

_

_______________________________________

___underta

ke,

subje

ct

to

the

follo

win

g

term

s,

to

pay

to

the

Com

pany

unconditio

nally

and irre

vocably

on its

first w

ritten d

em

and s

uch s

um

s a

s m

ay b

e c

laim

ed b

y it in

writin

g u

pto

a m

axim

um

of

US

D _

____________ a

s re

cord

ed o

n th

e R

eq

uest fo

r Pro

posal.

1.

The C

om

pany m

ay c

laim

paym

ent h

ere

under if e

ither:

Page 6

0 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

1.1

Befo

re th

e d

ate

stip

ula

ted in

the R

eq

uest fo

r Pro

posal fo

r the v

alid

ity o

f the B

id o

r any e

xte

nsio

n to

this

date

agre

ed b

etw

een th

e C

om

pany a

nd th

e C

ontra

cto

r, the C

ontra

cto

r atte

mpts

to w

ithdra

w, m

odify

, or a

mend h

is

bid

; or

1.2

The C

om

pany has ag

reed w

ith th

e C

ontra

cto

r th

at

a C

ontra

ct

will

be execute

d,

but

the C

ontra

cto

r fa

ils to

execute

the fo

rmal C

ontra

ct D

ocum

ent w

hen re

queste

d to

do s

o b

y th

e C

om

pany; o

r

1.3

At th

e tim

e o

f ente

ring in

to a

Contra

ct w

ith th

e C

om

pany to

underta

ke a

nd c

om

ple

te th

e w

ork

, the C

ontra

cto

r

fails

to p

rovid

e th

e B

onds a

nd G

ua

rante

es re

quire

d b

y s

uch C

ontra

ct.

2.

Paym

ent s

hall b

e m

ade h

ere

under o

n th

e C

om

pany’s

first w

ritten d

em

and to

us s

tatin

g th

at o

ne o

r more

of th

e a

bove e

vents

has o

ccurre

d w

ithout a

ny re

fere

nce to

the c

ontra

cto

r; and w

ithout fu

rther c

onditio

n o

r substa

ntia

tion a

nd w

ithout th

e n

ecessity

of a

ny p

roceedin

gs w

hate

ver, w

heth

er ju

dic

ial o

r oth

erw

ise b

ein

g in

stitu

ted b

y th

e C

om

pany.

3.

The B

ond s

hall re

main

in fu

ll forc

e a

nd e

ffect u

ntil th

e d

ate

when th

e C

ontra

cto

r shall h

ave e

xecute

d th

e fo

rmal C

ontra

ct

Docum

ent a

nd p

rovid

ed th

e n

ecessary

Bonds a

nd G

uara

nte

es th

ere

under o

r upon th

e w

ritten re

jectio

n b

y th

e C

om

pany o

f the

Contra

cto

r’s B

id, w

hic

hever is

earlie

r, at w

hic

h tim

e th

e B

ond s

hall a

uto

matic

ally

expire

and b

e o

f no fu

rther e

ffect.

IN W

ITN

ES

S W

HE

RE

OF

this

Bond h

as b

een d

uly

sig

ned a

nd s

eale

d o

n th

e _

____ d

ay o

f ________________ y

ear

______.

For a

nd o

n b

ehalf o

f

__________________________________

_______________

___________________

______________

______

Offic

er

Manag

er

Witn

esses:

1

. _________________ 2

. __________________

Page 6

1 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Fo

rm o

f Co

ntra

ct A

gre

em

en

t T

HIS

A

GR

EE

ME

NT

is

m

ade

the

_____

day

of

_______

___

year

____

_

betw

een

Pakis

tan

Inte

rnatio

na

l A

irline

s

(here

inafte

r calle

d “P

IA”) o

f the o

ne p

art a

nd [n

am

e o

f Contra

cto

r] of [c

ity a

nd c

ountry

of C

ontra

cto

r] (here

inafte

r calle

d

“the C

ontra

cto

r”) of th

e o

ther p

art:

WH

ER

EA

S P

IA in

vite

d P

roposals

fo

r certa

in pro

ducts

an

d ancilla

ry serv

ices,

viz

., M

RO

/

M&

E S

olu

tion an

d has

accepte

d a

Pro

posal b

y th

e C

ontra

cto

r for th

e s

upply

of th

ose p

roducts

and s

erv

ices in

the s

um

of [c

ontra

ct p

rice in

word

s a

nd fig

ure

s] (h

ere

inafte

r calle

d “th

e C

ontra

ct P

rice”).

NO

W T

HIS

AG

RE

EM

EN

T W

ITN

ES

SE

TH

as fo

llow

s:

1.

In th

is A

gre

em

ent w

ord

s a

nd e

xpre

ssio

ns s

ha

ll have th

e s

am

e m

eanin

gs a

s a

re re

spectiv

ely

assig

ned to

them

in th

e

Conditio

ns o

f Contra

ct re

ferre

d to

.

2.

The fo

llow

ing d

ocum

ents

shall b

e d

eem

ed to

form

and b

e re

ad a

nd c

on

stru

ed a

s p

art o

f this

Agre

em

ent, v

iz.:

(a) In

stru

ctio

ns to

Co

ntra

cto

rs;

(b)

Sum

mary

of R

equire

ments

;

(c) P

roduct a

nd S

erv

ices R

equire

ments

;

(d)

Genera

l Instru

ctio

ns a

nd C

onditio

ns o

f Contra

ct;

(e) S

pecia

l Term

s a

nd C

onditio

ns o

f Contra

ct;

(f) C

ontra

cto

r’s P

roposa

l.

3.

In c

onsid

era

tion o

f the p

aym

ents

to b

e m

ade b

y P

IA to

the C

ontra

cto

r as h

ere

inafte

r mentio

ned, th

e C

ontra

cto

r here

by

cove

nants

with

PIA

to p

rovid

e th

e p

roducts

an

d s

erv

ices a

nd to

rem

edy d

efe

cts

there

in in

confo

rmity

in a

ll respects

with

the p

rovis

ions o

f the a

gre

em

ent.

4.

PIA

here

by c

oven

ants

to p

ay th

e C

ontra

cto

r in c

onsid

era

tion o

f the p

rovis

ion o

f the p

roducts

and s

erv

ices a

nd th

e

rem

edyin

g o

f defe

cts

there

in, th

e C

ontra

ct P

rice o

r such o

ther s

um

as m

ay b

ecom

e p

ayab

le u

nder th

e p

rovis

ions o

f the

Contra

ct a

t the tim

es a

nd in

the m

anner p

rescrib

ed b

y th

e C

ontra

ct.

5.

Unle

ss e

xpre

ssly

sta

ted

here

in, w

here

ver a

ny p

erio

d o

r perio

ds o

f time a

re s

pecifie

d, th

e p

artie

s h

ere

to a

gre

e th

at tim

e

shall b

e th

e e

sse

nce o

f the C

ontra

ct.

Page 6

2 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

6.

Unle

ss e

xpre

ssly

sta

ted h

ere

in, th

e fa

ilure

of o

ne p

arty

to e

xerc

ise a

ny o

ptio

n, rig

ht o

r rem

edy u

nder th

e C

ontra

ct o

r to

dem

and c

om

plia

nce o

f an

y o

blig

atio

n o

f the o

ther p

arty

, shall n

ot c

onstitu

te a

waiv

er o

f any s

uch o

ptio

n, rig

ht o

r rem

ed

y

or th

e p

erfo

rmance th

ere

of.

7.

Each o

f the rig

hts

and o

blig

atio

ns c

onta

ined in

this

Contra

ct s

hall b

e d

eem

ed to

be d

istin

ct a

nd s

evera

ble

so th

at if o

ne

such rig

hts

an

d o

blig

atio

ns s

hall b

e d

ecla

red o

r becom

e ille

gal, v

oid

or u

nenfo

rceable

, then

the re

main

ing rig

hts

and

oblig

atio

ns s

ha

ll (unle

ss th

e e

ffect is

to fru

stra

te th

e fu

ndam

enta

l basis

of th

is C

ontra

ct) c

ontin

ue in

full fo

rce a

nd e

ffect.

8.

The C

ontra

cto

r shall n

ot a

ssig

n a

ny o

f its d

utie

s / o

blig

atio

ns u

nder th

is c

ontra

ct to

any th

ird p

arty

.

9.

The p

artie

s to

the C

ontra

ct s

hall n

ot b

e lia

ble

for a

ny lo

ss, c

laim

s o

r dem

ands o

f any n

atu

re w

hats

oe

ver a

nd s

ha

ll not b

e

deem

ed in

bre

ach o

f this

Contra

ct b

ecause o

f an

y d

ela

y o

r failu

re in

observ

ing o

r perfo

rmin

g a

ny o

f the c

onditio

ns o

r

pro

vis

ions h

ere

of if s

uch d

ela

y o

r failu

re is

caused b

y o

r aris

es o

ut o

f any c

ircum

sta

nces w

hats

oe

ver, b

eyon

d th

e

affe

cte

d party

’s co

ntro

l, in

clu

din

g (b

ut

with

out

limitin

g th

e gen

era

lity of th

e fo

regoin

g),

decla

red or

undecla

red w

ar,

sabota

ge, b

lockad

e, re

vo

lutio

n, p

olic

e a

ctio

n, rio

ts o

r dis

ord

er, e

mbarg

oes o

r trad

e re

stric

tion

s o

f any s

ort, g

overn

ment

or q

uasi-g

overn

ment a

ctio

n, a

cts

of G

od, fire

, flood, e

arth

qu

akes, e

xplo

sio

n, a

ccid

ent, ra

dia

tion, s

trike, lo

ckouts

or o

ther

Labo

ur d

ispute

s o

r dis

aste

rs.

10

. T

he C

om

pany s

hall h

ave th

e rig

ht to

term

inate

the C

ontra

ct:

• If th

e C

ontra

cto

r, in th

e ju

dgm

ent o

f the c

om

pan

y, is

or h

as b

een e

ngag

ed in

corru

pt o

r fraudu

lent p

ractic

es in

com

petin

g fo

r or e

xecutin

g th

e C

ontra

ct

• If th

e C

ontra

cto

r com

mits

a b

reach o

f any o

f the te

rms a

nd c

onditio

ns o

f this

Contra

ct

In a

ny c

ase th

e C

om

pany te

rmin

ate

s th

e c

ontra

ct o

n a

ny o

f the a

fore

said

reasons, th

e C

ontra

cto

r shall b

e lia

ble

for a

ll

dire

ct lo

sses, d

am

ages a

nd c

harg

es in

curre

d b

y th

e C

om

pany, in

rela

tion to

the te

rmin

atio

n o

f this

contra

ct.

11

. A

ll dis

pute

s o

r an

y d

iffere

nce o

r questio

n w

hic

h m

ay a

rise b

etw

een th

e p

artie

s h

ere

to o

r an

y p

ers

on c

laim

ing th

ere

of,

touchin

g o

r aris

ing o

ut o

r in re

spect o

f this

Contra

ct o

r the s

ubje

ct m

atte

r there

of s

hall b

e re

ferre

d to

the a

rbitra

tion

in

accord

ance w

ith th

e A

rbitra

tion A

ct 1

940, e

ach p

arty

shall a

ppo

int its

ow

n A

rbitra

tor a

nd th

e d

ecis

ions in

such a

rbitra

tion

pro

ceed

ings s

hall b

e fin

al a

nd b

indin

g o

n b

oth

the p

artie

s. T

he p

artie

s s

ubm

it to th

e ju

risdic

tion o

f the c

ourts

of K

ara

chi,

PA

KIS

TA

N.

Page 6

3 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

IN

WIT

NE

SS

, wh

ere

of th

e p

artie

s h

ere

to h

ave

caused th

is A

gre

em

ent to

be e

xecute

d o

n th

e d

ay a

nd

ye

ar firs

t above w

ritten.

Sig

ned, s

eale

d, a

nd d

eliv

ere

d b

y th

e

said

[na

me o

f repre

senta

tive] (fo

r PIA

)

in th

e p

resence o

f [nam

e o

f witn

ess]

Sig

ned, s

eale

d, a

nd d

eliv

ere

d b

y th

e

said

[na

me o

f repre

senta

tive] (fo

r the C

ontra

cto

r)

in th

e p

resence o

f [nam

e o

f witn

ess]

Page 6

4 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Pe

rform

an

ce

Gu

ara

nte

e F

orm

BA

NK

GU

AR

AN

TE

E N

O._

______

____

___

DA

TE

D:

____

____

___

___

____

_____

____

_

AM

OU

NT

:

____

____

___

___

____

_____

__

_

EX

PIR

Y: _

____

___

___

____

____

___

___

__

Pakis

tan In

tern

atio

na

l Airlin

es C

orp

ora

tion L

imite

d

Kara

chi A

irport

Kara

chi

Dear S

ir,

PE

RF

OR

MA

NC

E G

UA

RA

NT

EE

DE

SC

RIP

TIO

N O

F W

OR

K _

____

____

___

___

_____

____

___

___

____

_____

____

Where

as,

we

unders

tand

that

yo

u

ha

ve

pla

ced

a

Work

C

ontra

ct

No.

_______

___

___

___

___

___

____

date

d

____

____

___

___

____

with

____

___

___

____

____

____

_

(The

Contra

cto

r) fo

r th

e

above

mentio

ned

work

and

that

in

accord

ance w

ith th

e te

rms o

f the c

ontra

ct, th

e C

ontra

cto

r is re

quire

d to

furn

ish a

Bank G

uara

nte

e in

respect o

f its o

blig

atio

ns

under th

e s

aid

contra

ct fo

r an a

mount e

qual to

5%

(five p

erc

ent) o

f the to

tal c

ontra

ct v

alu

e v

iz (a

mount o

f contra

ct in

word

s

and fig

ure

s).

No

w,

there

fore

, in

con

sid

era

tion of

the abo

ve,

we,

(Nam

e and ad

dre

ss of

Bank)

here

by G

UA

RA

NT

EE

irre

voca

bly

and

uncond

ition

ally

the d

ue p

aym

ent to

you u

pon d

em

and o

f first w

ritten s

uch s

um

or s

um

s n

ot e

xcee

din

g (a

mou

nt o

f gu

ara

nte

e

in w

ord

s a

nd fig

ure

s) w

ithout w

hats

oever rig

ht o

f obje

ctio

n in

the e

ven

t that th

e c

ontra

cto

r fails

to p

erfo

rm o

r fulfill a

ny o

f the

term

s a

nd c

onditio

ns o

f the c

ontra

ct a

t the tim

e o

r durin

g th

e p

erio

d s

pecifie

d th

ere

fore

in th

e c

ontra

ct, p

rovid

ed th

at a

ny

dem

and h

ere

under is

rece

ived in

writin

g a

t this

offic

e w

ithin

the v

alid

ity o

f this

guara

nte

e a

ccom

panie

d b

y y

our w

ritten

decla

ratio

n to

us th

at th

e C

ontra

cto

r has fa

iled to

com

ply

with

the te

rms o

f the c

ontra

ct, a

nd s

uch d

ecla

ratio

n s

hall b

e

Page 6

5 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

accepte

d b

y u

s a

s c

onclu

siv

e p

roof th

at th

e a

mount c

laim

ed is

due to

you, a

nd w

e s

hall fo

rthw

ith p

ay y

ou th

e e

ntire

am

ount

cla

imed.

Our lia

bility

un

der th

is g

uara

nte

e s

hall n

ot b

e a

ffecte

d b

y a

ny d

ispute

or d

iffere

nce b

etw

ee

n y

ou

and th

e C

ontra

cto

r or b

y a

ny

forb

eara

nce o

r indulg

en

ce g

rante

d b

y y

ou to

the C

ontra

cto

r or b

y a

ny o

ther s

ecurity

held

by y

ou fro

m th

e C

ontra

cto

r rela

ting

to th

e a

bove

-mentio

ned

Contra

ct o

r any v

aria

tion in

the c

ontra

ct o

r any o

ther m

atte

r or th

ing w

hic

h m

ight o

therw

ise a

ffect o

ur lia

bility

here

und

er.

We fu

rther g

uara

nte

e th

at n

o c

hange o

r additio

n to

or o

ther m

odific

atio

n o

f the te

rms o

f the C

ontra

ct s

hall in

an

yw

ay re

lease

us fro

m a

ny lia

bility

und

er th

is G

uara

nte

e a

nd w

e h

ere

by w

aiv

e n

otic

e o

f any s

uch c

han

ge, a

dditio

n o

r modific

atio

n.

This

Guara

nte

e w

ill rem

ain

valid

until ........................................... a

nd a

ny c

laim

s h

ere

under m

ust b

e re

ceiv

ed b

y th

at d

ate

,

afte

r whic

h th

is g

uara

nte

e w

ill becom

e n

ull a

nd v

oid

, and m

ust b

e re

turn

ed to

us fo

r cancella

tion.

This

guara

nte

e s

ha

ll be c

onstru

ed in

accord

ance w

ith th

e la

ws o

f Pakis

tan.

For a

nd o

n b

eha

lf of

____

____

___

___

____

_____

____

___

___

____

_____

____

___

____

____

___

___

____

_

____

____

___

___

____

__

Offic

er

M

an

ager

Witn

esses:

1. _

_____

___

____

___

_ 2

. ________

____

___

___

Page 6

6 o

f 18

9

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

Co

ns

ortiu

m R

es

po

nsib

ility F

orm

N

am

e o

f Firm

8

Fo

rm o

f B

usin

ess

9 R

ole

in P

roje

ct10

Resp

on

sib

ilities

11

Pro

du

ct o

r S

erv

ice

12 to

be

Pro

vid

ed

Jo

int V

en

ture

A

gre

em

en

t13

Refe

ren

ce a

nd

Date

Lead C

ontra

cto

r

For e

ach p

artn

er lis

t, the s

taff m

em

bers

wh

o w

ill be a

part o

f the p

roje

ct, th

eir p

roposed ro

les a

nd th

e m

inim

um

com

mitte

d

man-d

ays fo

r each p

ers

on.

____

____

___

___

____

_____

____

___

___

____

_____

____

Sig

natu

re a

nd

Sta

mp

of A

uth

oriz

ed

Lead

Co

ntra

cto

r

8 E

nte

r the

na

me o

f ea

ch

of th

e C

onso

rtium

/ Jo

int V

en

ture

/ Su

b-C

on

tracte

d firm

s, s

tartin

g w

ith th

e L

ea

d C

on

tracto

r 9

Sta

te w

heth

er In

div

idual, S

ole

Pro

prie

tor, L

imite

d L

iability

Com

pan

y, P

artn

ers

hip

, Corp

ora

tion, e

tc.

10 S

tate

the ro

le o

f the F

irm o

n th

e P

roje

ct i.e

. whe

ther L

ead C

ontra

cto

r, Pro

ject M

an

ager, S

oftw

are

Su

pplie

r, Softw

are

Develo

pe

r, Tra

iner, e

tc.

11 C

learly

list a

ll the k

ey re

sponsib

ilities th

e F

irm w

ould

be

und

erta

kin

g o

n th

e P

roje

ct

12 In

clu

de a

time s

chedule

for p

rovis

ion o

f pro

ducts

and

serv

ices o

f each p

artn

er

13 C

opy(s

) of A

gre

em

ent(s

) to b

e a

ttached

Page 67 of 189


B4. Format and Contents of Proposal

1. General Proposal Requirements

1.1 Proposals should be prepared simply and provide a straightforward, concise

description of the Bidder’s capabilities to satisfy the requirements of this RFP.

1.2 Bidders must follow all formats and address all portions of the RFP set forth herein

providing all information requested. Bidders may retype or duplicate any portion of

this RFP for use in responding to the RFP, provided that the proposal clearly

addresses all of PIAC's information requirements.

1.3 Bidders must respond to every subsection under the Technical Proposal and Cost

Proposal sections. Bidders must label each response to RFP requirements with the

section and subsection numbers or Proposal Reference IDs associated with the

subject requirement in this RFP.

1.4 Proposals must not contain extraneous information. All information presented in a

Proposal must be relevant in response to a requirement of this RFP, must be

clearly labeled, and, if not incorporated into the body of the Proposal itself, must be

referenced to and from the appropriate place, within the body of the Proposal.

1.5 Proposals shall be prepared on standard A4 size paper. Foldouts containing charts,

spreadsheets, and oversize exhibits are permissible. Proposal pages must be

numbered and responses must be identified by the related RFP section number.

1.6 Bidders shall divide their responses to this RFP into a Technical Proposal and a

Financial Proposal. Financial Proposal and pricing information should not be

included in the Technical Proposal. Inclusion of Price Proposal or pricing in the

Technical Proposal shall make the proposal non-responsive.

2. Required Format of the Proposal

Each Contractor can submit only one Proposal. Bidders shall prepare their Bids

using the following structure and form.

2.1 Executive Summary

The Bidder’s response concerning its ability to satisfy the qualification, eligibility,

business and technical requirements as stated in the RFP Document. The Bidder

should summarize the proposed technical and service solution and qualitatively

describe its advantages in the Executive Summary.

2.2 Bidder’s Qualification and Experience

The Bidder should provide information regarding his eligibility, qualification and

relevant experience to perform the requirements under Section G, sub-section G1–

“Bidder’s Qualification and Experience” of this RFP.

Page 68 of 189


2.3 MRO / M&E Package

Complete details should be provided of the MRO / M&E Package that is being

proposed as part of the solution. The MRO / M&E Package’s general functional

description and capabilities, with particular reference is defined in Section C –

Product Requirements (MRO / M&E Package& add-ons). The MRO / M&E Package

should have all integrated modules and should seamlessly interface with PIAC’s

existing internal and external software with an overview of integration and data

transfer mechanisms. The security and manageability features should also be

highlighted. The Bidder should elaborate on the extent and efforts for customization

required to satisfy the functional requirements. Bidder should provide contingency

and backup plans/procedures with guaranteed Service Level Agreements.

Licensing cost for M&EIT System users should be provided as follows:

• 350 - 500 MRO / M&E users

• 501 - 750MRO / M&E users

• 751 - 1000MRO / M&E users Unit cost for each MRO / M&E user

• If enterprise licensing option is available, please specify

• Optionally tail based / revenue based licensing model

In case of concurrent users License may be reduce accordingly.

Contractor must also specify an “Escrow” arrangement for the availability of source

code necessary to support the proposed solution in case the Contractor or the

principal vendors cease to exist, discontinue this line of business or are

incapacitated in any way to support the proposed solution.

2.4 Database Management System (DBMS)

Complete details of the DBMS are to be provided, including features and

capabilities, adherence to industry standards, portability and openness, with

reference.

Features and capabilities of the Database Administration Tools that are proposed

should be provided.

2.5 Query and Report Generator Tools

Complete description of the tools that are being provided with MRO / M&E Package

standard functionality for End-User ad-hoc query and report generation, including

capabilities for ease-of-use and learning.

2.6 Implementation Strategy

The Bidder should provide details of the implementation strategy to be adopted, and

include a component-wise high-level plan. Details should be provided of the project

Page 69 of 189


organization that will be maintained. The Project progress reporting mechanism is to

be highlighted. Details of how the resources identified will be utilized during the

various phases of the Project should be described. The quality assurance process to

be followed for products and services, as well as responsibilities, should be

described. Implementation tasks requirements are detailed in Sub Section D1.

Detailed time schedule shall be provided highlighting main milestones and activities

in detail with overall time span. Bidders must clearly specify the facilities required by

their consultants during implementation.

2.7 Interim Server(s)

A complete description of the hardware configuration and performance expectations

of the proposed Interim Server should be provided. The Contractor should also

describe the contingency arrangements that will be in effect for the period that the

Interim Server(s) is required, as well as maintenance responsibilities. The Site

Specifications for installation of the Server(s) must be provided to enable PIA to cater

for the requirements.

2.8 Training to Users and Management

Details of Training to be conducted by the successful Bidder should be provided,

with description of type, content, duration and location of courses for each of the

identified personnel levels, with reference to Sub Section D - Services

Requirements. Also describe the training material to be provided on completion of

the course as well as certification/examination method to be followed. Following

table indicates the approximate number of users that would require training

2.9 Data Migration

All details of data conversion strategy and process have to be defined, in accordance with details outlined in Section D, sub-section-D3.Acquiring of any third-party industry solution by the contractor for data migration should be described, and

USER GROUPS EXPECTED ROLES NUMBER

Senior Management (DCE and above)

➢ Report / MIS review

➢ Transaction review and approval

➢ Limited transaction entry / edit

80

Power / Key Users (IT, Others) ➢ System parameterization and configuration Master trainers

50

End Users ➢ Transaction entry / edit

➢ Transaction approvals

➢ Report / MIS / Document viewer

800

Technical Users (IT Department) ➢ Technical Support 25

Page 70 of 189


licensing cost of such solution should be part of ‘Migration’ cost as specified in Section-B4, Form Services Price Schedule (Prior to Maintenance). PIA may decide at its own discretion, not to migrate the legacy data at all, or limit the functions/time-frame, and shall declare it in writing as part of contract.

2.10 3rd Party Software Interfaces

Contractor will be responsible to ensure that required 3rd party software, operating



interfaces, etc. are all made available, documented, designed, implemented and

operational to meet PIA’s requirements in the proposed MRO / M&E solution. These

should be clearly spelt out in the Technical Proposal and corresponding pricing

shown in the Price Proposal.

2.11 Documentation

Details of documentation have to be provided for MRO / M&E and other

Applications. It should describe a summary of contents, media on which provided,

and the number of hard and soft copies. The Bidder should address the needs of

End user as well as technical (operations, support and development).

2.12 Post-Implementation Warranty / Support

Details of post-implementation support during and after warranty period that will be

provided after the expiry of the warranty should be provided for each required

component with reference to Section D - Services Requirements. The type of

support, coverage, location from which support will be provided, should be

described, as well as the level of expertise that will be employed for support. Also

describe the escalation process that is to be followed, and the service levels. A

description of the handling of various categories of problems and response times

should be provided along with the cost.


Details of the proposed technology architecture under which the MRO / M&E

solution will be implemented should be provided, consistent with modern n-tiered

client/server and distributed computing design and details provided in Section C –

Product Requirements (MRO / M&E Package and Add-Ons).

2.14 Recommendations for Hardware Configuration and System Management Tools

The Bidder should provide its recommendations for the platform configuration for

server hardware to run the MRO / M&E Package and other applications. The

proposed MRO / M&E Package and DBMS shall be platform independent so that

shall give PIAC liberty for choosing any appropriate platform in the future.

Page 71 of 189


Bidder has to propose complete hardware solution and minimum network

infrastructure.

PIAC reserves the right to purchase hardware/operating software from the

successful Bidder or any other vendor of its choice.

2.15 Add-on Applications

Where the suite of MRO / M&E modules does not meet all the functional

requirements of PIA, and the Contractor proposes to custom-build application(s) as

Add-ons to the MR&E IT to fulfill the requirements, details of the application

development methodology, development platform and tools, and extent of

development complexity are to be provided. Their capability to integrate seamlessly

with the core MRO / M&E Solution and other proposed external software utilities

and modules should be described, with an overview of integration and data transfer

mechanisms. The ownership rights of the Add-on applications will rest with PIA,

including all Intellectual Property Rights. The Contractor‘s (or Consortium Partner‘s)

experience of developing and implementing such Custom-Built applications must be

highlighted.

2.16 Requirements from PIA: The Contractor must specify in detail the facilities to be

provided by PIA for effective implementation. The Technical Proposal must

clearly mention the responsibilities of PIA and the Contractor during different phases

of the project.

2.17 Comments / Suggestions (Optional): The Contractor should provide any comments

or suggestions on the Terms of Reference

2.18 List of all deliverables during the projects.

Page 72 of 189


SECTION C

PRODUCT DETAIL (MRO / M&E PACKAGE & ADD-ONS)

Page 73 of 189


C1 OBJECTIVES

This section describes the functional requirements that the MRO / M&E

Solution is required to meet.

Requirement are sub-divided into two sub-sections C2 & C3.

Sub-section C2 covers all the functional areas of PIA Engineering & Maintenance

department, while functionality requirements are based upon as-is processes /

workflows / practices or activates, which are currently handled through various

mean; i.e.;

▪ PAMMIS (PIA Aircraft Maintenance Management Information System);

or

▪ by way of using Microsoft Access/Excel; or

▪ by using home-grown applications; or

▪ by using all paper-based documentations & records, manually tracked

functions, with little or no system support.

Sub-Section C3 describes general requirements of MRO/M&E Solution mainly

addressing add-ons, data/information formats, trending technologies & other

product enhancing features.

PIA intends to introduce the best of the breed IT functionality modules into its

Maintenance & Engineering, therefore it is required that wherever applicable, the

“best industry practices, processes & templates” to be introduced / suggested to

meet or exceed the functional requirements outlined in following sub-sections

(C2 & C3).

Page 74 of 189


C2 FUNCTIONAL REQUIREMENTS

1.0 Required Engineering Functionality

1.1 MPD Management

▪ Import / upload of Maintenance Planning Document (MPD) as delivered by the

aircraft OEM in digital format, both initial issue and subsequent revisions.

▪ For non-customized MPD delivery, a filter according the PIAC effectivity shall

generate customized MPD variant/version.

▪ Capability to generate the difference report between two consecutive revisions of the

MPD for the purpose of PCAA approval.

▪ Customization of the MPD as per peculiar PIAC requirements.

▪ Notification to the key users upon upload of new/revised or customized MPD.

▪ Define MEL and update according to fleet configuration.

1.2 Reliability Management

▪ Reliability and Performance analysis of A/C System, Engine & Components, on the

basis of the defects & rectification data arising of unscheduled maintenance, on

aircraft, engine and components.

▪ The No Fault Found (NFF) analysis / reporting aircraft system/chapter-wise

▪ MTBUR analysis of the aircraft components. The system should suggest MPD

adjustment accordingly.

▪ Engine, APU trend / performance monitoring, through engine condition monitoring&

oil consumption.

▪ Support for CofM & CofA renewal process.

▪ Monitor aircraft configuration for ETOPS, RVSM compliance

▪ Flight incidents & Pilot Reports data classification upon entry into the system

▪ The aircraft/ fleet utilization to be stored into the system through an interface.

1.3 Document Management

▪ An automated upload/update of OEM Manuals with

The system shall ensure an airworthy update and revision management of all OEM documents used for aircraft maintenance and engineering. But also, airframe structure drawing to be up-loaded via internet access.

▪ Upload and register SB’s

All Service Bulletins (SB’s) and Airworthiness Directives (AD’s) to be registered in

the system

▪ Revise aircraft & aircraft component manuals

The revision management process shall ensure, the revisions are applied at the

central library but also, that all revised documents receive all end user.

Page 75 of 189


▪ Technical Library Function

All aircraft & aircraft components manuals should be made available in a catalogued

manner in the library. The library should be connected to the OEMs sites at back

end for continued up-t-date manual contents of the manuals. User sections should

have access to the updated OEM manuals/documents as per their work center

requirements, defined in the user section capability list. There should be a

notification to the end user whenever a revised manual is updated. Technical

documents to be made available on desktop PC as well as android, apple devices.

▪ Maintain Internal PIAC Manuals.

PIAC own manuals to be maintained, approved and revised. The system shall

support this process.

1.4 Task Card Management

▪ Upload OEM Task Cards (TC)

PIAC is widely using the Task Cards provided by the OEM. A functionality to be provided to upload and revise master Task Cards. The system shall have functionality to store and manage those document types for further use.

▪ Create/Update/ modify TC

Beside pre-defined TC’s there must be a functionality to write, maintain and revise PIAC own TC’s. For structural damages and major repairs, creation and approval of TC to be supported.

▪ Inclusion of relevant procedures from AMM

Task cards should be enhanced with more detailed instructions, text and graphical elements of the embedding relevant content from OEM manuals with reference. Any change in the OEM manual should automatically update the task card to that extent, with revised manual reference.

▪ Release Master TC for service.

Once the master TC is finally edited and/ or revised. This TC to be get approval by a

second authority. This could be supported by a workflow solution. When the approval

is granted, the TC to be released for using in the production, replacing the old

version. When the master TC is released for production, The TC content is reduced

to the concerned tail sign, the order number is added to the TC and the TC attached

to a WP. The TC if required on colored paper with bar code, tail sign text and

graphic. Also, the required material to be on the TC and will create the BoM by

turning the master TC into production.

1.5 Modification Process

❖ Evaluate & approve AD, SB, SIL Evaluation of Airworthiness Directives from regulatory bodies like FAA, EASA & OEM Service Bulletins, Service Information Letters & similar literature for applicability to PIA fleet or installed components.

Page 76 of 189


❖ Create Engineering Order The AD/SB, if evaluated applicable to PIA fleet/components to be converted to a change order with specific actions defined along with material and Mh consumption required. Reference to the relevant maintenance data / instruction to be provided for implementation.

❖ Status Fleet Modification Such modification if implemented on aircraft, the aircraft technical record as well as master configuration record to be updated as applicable.

❖ Status Engine/ Component Modification The modification performed on Engine / aircraft components shall translate into appropriate modification status of Engine / aircraft component, with interchangeability (one-way, two-way) appropriately inserted into fleet master configuration data.

❖ Planning & staggering Fleet Modifications Optimized modification plan to be suggested keeping into view the target time (for time barred modifications), available maintenance slots, QPA, spare float, and modification kit availability/lead times. A close loop monitoring through charts to be provided.

❖ List of performed SB’s

Modification status report of the aircraft, engine or components, with modifications performed in a particular time period should be supported.

❖ Configuration control.

Configuration control of the aircraft or engine to be ensured, with part number/serial

number applicability of sub component / assemblies to be validated upon installation

on aircraft or engines. All applicable ADs & mandatory SBs pending for

incorporation, to be highlighted in terms of open change orders for fleet/tail, Engine

or components with appropriate in time alerts mechanism (email, dashboard etc.) to

key stake holders, specifically the engineering and quality assurance divisions.

Page 77 of 189


2.0 Required functionality for Aircraft Phase-in/-Out

The functionality is more importantly required whenever an aircraft is inducted in PIA

through purchase or lease and later phased-out through sale or lease-return.

Technical record is especially important for speedy lease return.

2.1 Aircraft master data

▪ Create aircraft/ engine master data when a new aircraft to be introduced, the Aircraft/ Engine master data to be created.

▪ Create aircraft/ engine master structure & locations

When a new aircraft type to be introduced in the fleet a new structure of this aircraft or variant to be defined. Based on this fleet structure, the aircraft/ engine master structure and location to be defined. The technical locations shall consist of ATA chapters and Zonal information in a hierarchical structure in assays and sub assay.

2.2 Initial data entry

▪ Initial provisioning, upload Recommended Spare Parts List (RSPL)

For the induction of a new aircraft type the recommended spare parts list to be uploaded. An editing functionality shall allow producing versions of this RSPL file. Based on the final agreed parts list, the procurement process to be initiated.

▪ Upload and maintain readiness log

Also, the readiness log to be uploaded to complete the as is configuration.

▪ Upload A/C, engine, component history

The aircraft, engine and component history to be updated.

▪ Upload MPD, MEL

In case of a new aircraft type, the respective MPD and the Minimum Equipment List

(MEL) to be updated and customized according to the PIAC needs.

▪ Upload Tech-Log, MEL status, Open defects

The actual aircraft status concerning technical logbook, MEL related items and

deferred defects to be uploaded into the system.

▪ Upload modification status

The modification status to be uploaded.

▪ Maintain status/ letter checks performed

The due date and the history of the letter checks performed to be updated.

▪ Enter flown flight hours, block hours, landings cycles, days.

The flown flight hours, clock hours, cycles and days to be updated for the aircraft,

engine and leach Line Replaceable Unit (LRU).

Page 78 of 189


2.3 Aircraft phase out

▪ Create Readiness Log

By phasing out an aircraft, a readiness log to be provided. But also, concerned stock

to be reviewed for surplus.

▪ Create Mod Status

A report to be created of the entire aircraft/ engine modification status

▪ Create Maintenance Status

A report to be created of the current maintenance status and the entire maintenance

history.

▪ Create Tech-Log, MEL status, Deferred Defects

A report to be created concerning the actual open items, such as Technical Logbook

entries, MEL related items and deferred defects.

2.4 Engine Change

▪ Remove & extract complete data set

By engine removal, all engine related data to be removed from the aircraft data set. In case of foreign repair, a report to be created and transferred to the vendor, with all concerned engine information.

▪ Upload complete data set

Engine overhaul, repair and modifications concerned data to be uploaded to the system. At engine installation, all concerned data to be linked with the concerned aircraft.

Page 79 of 189


3.0 Required Functionality for Line Maintenance

3.1 Line Maintenance Planning

▪ Long/ medium-term planning (summer/winter/hajj)

Based on the PIAC flight schedule and the PIAC maintenance program (Preamble)

in the long term planning a first schedule of the letter checks (A Check and below)

are done. Together with the expected non-routine work, the needed component

changes and the modifications, to ground time and the needed man hours are

defined.

In the medium term planning each ground time will be adjusted, the bill of work will be finalized and the bill of material defined. The total load will be mapped against the available capacity.

▪ Short-term planning

The deferred defects will be translated to a Bill of Work (BoW). All needed manpower, tools, spares and documents are prepared and assigned to the planned job.

▪ Work load/ capacity planning

The expected workload will be balanced against the available capacity. Further actions to be arranged such as additional capacity or postpone of work packages. Also, flexible shift pattern to be arranged by the system.

▪ Hangar/ A/C visit plan

As a result of the long/ medium term planning, the hangar visit plan is defined. It

represents the needed hangar slots of all PIAC & client letter checks.

▪ Assign Work Package to Work Center/ Shift/ individual staff

The defined work packages to be assigned to a particular work center and shift. In case some work packages cold not completed in a shift, it will be rescheduled by production planning and again assigned to a work center and shift. The major criteria are a priority/ alert list showing the latest due date of a job and also the aircraft availability.

▪ Flight Coverage Planning

▪ For flights, where a Ground Engineer to be attended, the flight coverage planning shall be possible. An optimal flight coverage roster shall be possible for all flights scheduled in a calendar month, taking care of aircraft scheduled, and fly-to station capability.

▪ Dispatch spares, tools, documentation to line station The spares, defined at the Bill of Material (BoM) is already blocked by a

reservation functionality. Also, the needed tools. When Production planning assigns a work package to a work center/ shift, the due date and the location is defined. Production Planning (PP) will also create a transportation order for providing the needed spares and tools at the needed location. When the work packages are performed a dispatch, order will return the tools to the tolls store and location, the replaced components to be dispatched to the salvage store.

▪ Provision of line stations

The provision of line stations with staff, tools, document and spare kit to be planned

and renewed.

Page 80 of 189


3.2 Scheduled Maintenance

▪ Bill of Work (BoW)

The BoW is a list of work packages (WP) to be performed in Line and Base maintenance. Each WP consist of a number of job cards (JC). Each WP has a unique identification number.

▪ Bill of Material (BoM)

The BoM defines the needed routine material (Rotables and consumables) for performing the WP. This list is a master file attached with the BoW master file. Needed routine material can be part of the master JC and the BoM to be extracted of it. Same with the needed tools and equipment.

▪ Needed Tools and Equipment

The needed tools and equipment, such as remedies, stairs, GSE to be planned by PP and dispatched to the WC. The list of required tools and equipment is part of the WP.

▪ Execute Work Package and Task Cards

Planned TC and WP to be performed are stored in the system as master documents. They consist of all needed field such as a unique ID, A/C type and effectivity, ATA chapter and Zone the needed Mh and qualification. When WP and TC are transformed from planning stage and turned into operation, the tail sign, the due date and a unique order number is added. A bare code is printed at the JC representing the order number. A cover sheet representing the WP and showing all JC within the WP.

▪ Schedule Major component change (MIC)

PP will create out of a forecast of hard times and regular inspections. Out of this list, the needed tasks for the coming shift are to be defined. The needed JC are selected and will be part of the WP.

▪ Release A/C to service

After performing the planned maintenance services, the A/C will be release to service. This is noted in the system. Any limitations such as remaining life due to MEL items is also noted and are the base for planning new maintenance activities.

▪ Shift hand over

The shift hand over to be supported by providing a list of open items.


▪ Record defects and corrective action.

The defect description and a number of describing filed including tail sign, ATA chapter and location, to be entered. The functionality shall also indicate repetitive defects. When the repair strategy is already defined during the investigation, it is noted in the corrective action field but also as a deferred defect. When the corrective action is completed, the open case will be closed. The defect notification to be used for further fleet analysis and for the fleet Reliability Report.

▪ Trace deferred defects

Tracing functionality shall locate deferred defects for further actions. An open defect

notification will also create a Maintenance Repair Order.

▪ Indicate MEL items

The system shall display the MEL list. An attribute shall declare the deferred defect as a MEL item and define the remaining life, if appropriate. In case of MEL item for each fight a report to be produced for pilot briefing. The MEL item to be traced on the alert list for high priority maintenance actions.

Page 81 of 189



▪ Update A/C, component records

➢ When and component change is performed, the respective S/N will be posted in the System. The replaced S/N (U/S part) will keep the accumulated counters. The new serviceable unit located in the A/C will accumulate counters to its remaining life. With the component change, the A/C will get an update of the as is configuration.

➢ In case of a modification (performing AD or SB) the new mod status of this A/C is noted. Subsequent changes in the system concerning MPD and TC are initiated. Also, the mod campaign will get notice of accomplishment of this A/C.

By accomplishing the WP, the related A/C counters are set to zero. When the A/C

starts again operation, all A/C counters and the subsequent Engine/ APU/ Component

counters will continue to collect the operational counts. The rescheduling of the next

maintenance activities will start.

▪ Report performed tasks

The performed WP’s are reported as complete, when the WP cover page is clocked-out by bar code scanning. The WP will be deleted from the WP backlog and transferred to the performed tasks. All dirty finger prints are archived by using the WP ID as the leading discriminator.

▪ Archive task cards

After performing the TC, the documents are archived for legal purposes for a

minimum of two year or for tracing A/C, Component history back-to-birth.

Page 82 of 189


4.0 Required Functionality for Cabin Maintenance


▪ Define/ update a maintenance program for CM &A/C cleaning. A regular schedule to be defined for cabin maintenance items and aircraft exterior, interior & deep cleaning.

▪ Define Instruction cards for CM

Instruction card to be defined for cabin maintenance.

▪ Plan CM according the maintenance program

According to the defined maintenance program, the CM work packages are planned

and scheduled.

▪ Plan capacity according to work load

According to the maintenance schedule, the capacity to be assigned.

4.2 Customer Feedback

▪ Interface to customer complaint system

An interface to be created between the system and the PIAC customer feedback

system. All Cabin related items to be transferred.

▪ Corrective action feedback

The corrective actions to be recorded and reported back to the customer feedback

system.

▪ Statistics according customer feedback

Statistics are generated concerning customer feedback and cabin maintenance

activities.


▪ Record defects from CBL or inspection and report corrective action; see also Line

Maintenance (LM) defect management

▪ Trace deferred defects same as LM

▪ Indicate MEL items Same as LM

Page 83 of 189


5.0 Required Functionality for Base Maintenance

5.1 Base Maintenance Planning

▪ Long/ medium-term check planning Base Maintenance Events

In the long term planning a forecast is given by the system for letter check due date and ground time based on standards parameter. This forecast in used for ground time staggering, budget planning and hangar capacity planning. In the medium planning the bill of work to be defined, the bill of material, together with planning adjustments, load and capacity planning. The routine and non-routine work packages are defined. The required tools are defined.

▪ Work Package Management

The standards Work Packages consist of several Job Cards are compiled and edited according to production planning and work optimization criteria. JC to be linked to WP’s and WP to be liked to a project plan.

▪ Hangar/ A/C visit plan; refer Line Maintenance para (3.1)

▪ Work Load Planning see Line Maintenance (3.1)

▪ Job Card creation/ update/ revise see Aircraft Engineering

▪ Event project planning with flow charts and mile stones

The project plan shall be a graphical representation of WP’ along a time line. By meeting the external time criteria, the Production Planner shall have the possibility shifting the WP’s along the time line to match with the available capacity. Also, an automated planning using capacity and load planning shall be possible.

▪ Forward/ Backward event planning (incl. Gantt-Chart).

Various planning scenarios to be possible such as forwards planning by using a

fixed start date and backward planning by using a fixed end date.

▪ Progress monitoring, monitor costs

By using shop floor data collection and the JC completion note, the work progress to be monitored. With the shop floor data collection, the consumed man hours to be collected. Also, consumed parted and exchanged LRU’s to be posted to the Work Order.

▪ Monitor consumed Man hour (Mh) & spares

The consumed spared and respective costs, the repair abroad costs and the

consumed man hour to be monitored on daily basis to control the costs.

5.2 Base Maintenance Operation

▪ Interface deferred defects from LM

The deferred defects to be transferred to the base maintenance event at the time of

aircraft roll in. The deferred defect to be transferred into a Repair Order.

▪ Shop floor data collection.

All Job Cards to be submitted will be assigned to an Order Number. By using a bare code beginning and end of the work to be done is registered. Also, when a component change is due, the in and out Serial Number (S/N) to be notified and subsequent processes to be triggered. But also queries at the Material Master and available stock to be done.

▪ Entering snags, planning rectification.

When visual inspections and system checks are required by the WP, upcoming discrepancies to be notified. Attributes to be added concerning the location, the nature of defect and the causing document (e.g. CPCP). A repair order to be generated with some production planning attributes such as expected man hours,

Page 84 of 189


needed spares and tools. The closure of the defect notification to be recognized by the system. Some observations to be notified and transferred to Engineering work place, such as CPCP.

▪ Shift hand over

A functionality to support shift handover in case the open WP or JC could not

completed within the current shift.

▪ Capacity Planning

Functionality offered to balance workload and available capacity.

▪ Close loop repair

Parts replaced for A/C and returned from shops after repair to be traced and

planned in a close loop parts management.


▪ Transfer defect to LM

When the aircraft roll out after the base maintenance is due, the open items are to

be transferred to line maintenance and kept as Repair Orders.

▪ Update A/C configuration & counters

Modifications, and component changes reflects changes in the aircraft configuration. Configuration update shall be most preferable done automatically by posting a component change. Manual update to be provided as well.

▪ Archive documents

All major activities are recorded as database transactions. But also, the used and stamped documents (dirty finger prints) to be archived according to the legal requirements. A logic link with the respective data base entry leads to a powerful knowledge base.

▪ Post check analysis

Analysis functions to be provided to allow reviewing and analyze performed checks. Also, the recorded Mh to be available for updating the standard Mh per TC.

Page 85 of 189


6.0 Required Functionality for Component Overhaul Shops


a) Medium-term capacity planning/ Shop visit forecast

Based on the shop visit history, and also on removal forecast for scheduled and unscheduled removals, the shop workload to be predicted. The Shop budget and needed capacity to be defined from this data. The system should support annual man-hour plan revised in real time at quarterly intervals.

b) Work Priority Management

Based upon component backlog, aircraft demand, stock level, scheduled component

expected arising & available manpower, system shall suggest a priority maintenance

list.

c) Capacity/ workload planning

Based on the work orders in the shop the workload and capacity planning to be

performed with standards parameters.

d) Monitor costs, monitor consumed Mh & spares.

Dynamic view of man hours & material consumption during the course of a

component maintenance and a report of Mh. & material consumed and cost of

production.

e) LRU repair status

Notwithstanding there is an in-house repair or a repair abroad request was generated, the actual repair status and a forecast concerning the serviceability is given by the system.

f) Planning for consumables.

System should support planning for consumables required during scheduled &

unscheduled maintenance, based upon HTCL, consumption history, average TAT, etc.

g) LRU Status / Location review

At any time, the current status and location of an LRU all serial numbers, a single serial number with installation/removal location and work-order history, its fleet applicability, alternate part numbers, shall be reportable by the system. Component hold up for consumables to carry status of consumables’ procurement phase.

6.2 Component Maintenance Workflow

➢ Work order / Input registration

➢ Work package / Bill of work compilation.

➢ Job issuance at shop production floor.

➢ Maintenance execution

➢ Defect notification & repair procedure.

➢ Work package data entry into system.

➢ Post consumables to repair order.

➢ Component release tag printing / sign-off.

➢ Shop-out / closure of work-order.

➢ Update LRU status & counters.

Page 86 of 189


6.3 Shop Support functions a) Process Flow for Contracted Maintenance / Repair Abroad

Contracted maintenance repair orders process flow with;

▪ Visibility of status of serial number/part numbers under such

maintenance.

▪ Processing/evaluation/approval of contracted maintenance repair

estimates/invoices/warranties as part of Repair Abroad work flow.

b) Scrap Process The scrap process to be supported by the system. The LRU to be deleted from the

system, re-order request to Rotables section & notification to ERP for assets

valuation adjustment.

c) Components requiring consumable During components’ maintenance, consumables are required such as spares, sub-

assemblies and other material.

▪ System should support request generation for consumables to stock rooms. I

▪ If the consumables are NIL in stock, then relevant purchase requisition should be

possible.

▪ The shop manager should be able to analyze the procurement & usage history and

make adjustments to quantity required.

▪ Reporting capability for all such components holdup during consumables’

procurement phase. Filters to be used for critical / AOG components as per demand /

priority.

d) Third Party Customer Component Maintenance

▪ Third party work order Loading at shop floor

▪ Customer approval for cost estimates.

▪ Closure of customer work-order and intimation to Business division.

▪ Handing over of customer components to the originator.

e) Shop Capability Management& Control

Component Capability List (CCL) management ensuring all required pre-

requisites;

▪ Shop Test-Equipment/Tools, alternate Test-Equipment/Tools approval &

registration.

▪ Ensure availability of all applicable material / tools as per CCL.

▪ Ensure Tool/Test Equipment has valid calibration/service life during use.

▪ Work order generation for shop to be restricted for non-CCL components.

▪ Ensure up-to-date maintenance data / OEM manuals for work-orders under

maintenance.

▪ Updated certifying staff list with all pre-requisite courses/training validity

check.

f) Fractional Work Order Process

Page 87 of 189


Inter-shop fractional work to be facilitated, where main work order is being

processed in allocated shop while for fractional work components is temporarily

moved to other shop, and returned upon job completion.

g) Tool store functions

▪ Shop tools management including calibration control

▪ Consumable Material/Chemicals storage in specified quantity with shelf life

control

▪ Tools, equipment Repair/Calibration processing (in-house / abroad)

▪ Issuance of tools on permanent and temporary basis and ensure their timely calibration.

▪ Issuance of consumable material with reference of work order. ▪ Keep an up-to-date inventory of all variety tools/equipment used in respective

shops

6.4 Component Engineering a) Up-to-date OEM Component Maintenance Manuals & documents

System should support that all maintenance manuals are updated and as per

latest revision.

b) SBs, ADs Component modification process

Workflow for component modification process to be supported by the system.

• Evaluation of modification

• Planning for modification, with generation of staggered plan for all applicable LRUs.

• The Mod kits to be ordered / planned.

• Removal request generation from aircraft / stock room for shop as per plan.

• Modification Sheet generation as part of work package.

• After modification, the interchangeability to be updated. Also, the aircraft master parts list/configuration to be updated.

c) Archive Technical Records

All maintenance records to be archived, for audit requirements.

a) Defect notification.

LRU defects to be described in a defect notification. The data are used for the component reliability report and as knowledge base for future maintenance.

d) Component reliability report.

Thee component reliability to be monitored based upon component removals, shop

findings and NFF. The same to be reported / projected as and when required filtered

for a date interval, ATA chapter, shop group, or a single component.

e) System should support the work instruction card to be created, updated and

revised.

f) Alternate Tools / Material Approval

System should maintain record of approved alternate tools / material with a cross-

reference list.

Page 88 of 189


6.5 Work flow for Repair &Modification shop Repair and modification of Mechanical components of airframe, engine, APU, L/G involves multi stage work package. System should support work flow involving following machine shop stages;

• Machining / grinding

• Welding, brazing

• Heat treatment

• Precision measuring

• Metallographic inspection / Hardness testing

• Surface treatment

• Bench fitting

• Plating / plasma / paint.

6.6 Workshop Equipment Maintenance

a) Fixed equipment Maintenance Shop

• Maintenance all the fixed installation of Power Plant, L/G & components overhaul shops’ mechanical machines, Test Rigs, workshop equipment, O/H cranes, compressors, cylinder chargers and other rotary equipment.

• Keep record of complete inventory of the workshop equipment and maintain the maintenance history for each type of equipment in the database.

b) Tool / Test Equipment Local Fabrication ❖ Fabricate/ repair various kinds of special tools/ fixture/equipment as suggested

by manufacturer through drawings manuals and samples. ❖ Approval by Technical Services Engineering and issuance of the compliance

certificate and recording into the system

Page 89 of 189


7.0 Required Functionality Concerning Quality Assurance

7.1 Quality Assurance (Audit) ▪ Define Yearly Audit Plan and define audit program/assigning teams for individual

audits. ▪ Preparing checklist for the specific area of audit, recording of Non-Compliances,

after execution of audit, for different levels (Level I, II, III) and time limit for corrective action. Follow up of NCRs till such time corrective actions are accepted and verified.

▪ Defining and conducting audits of Line Stations and Technical Handling Agents. Recording of Non-Compliances and their corrective actions.

▪ Audit Reports including Compliances and Non-Compliances for all audits (Base Station/Line Stations/Technical Handling Agents)

▪ Conducting and follow up of un-scheduled Audits whenever asked by Management / Regulatory Authority.

▪ Evaluation of potential Vendors and recommendation. Record of all vendors approved by Chief Engineer (QA).

▪ Assessment of CCL cases submitted for approval of Chief Engineer (QA). ▪ Assessment of Certifying Staff posted at Base and at different Line Stations and

record of Company Authorizations issued with expiry monitoring.

7.2 Quality Assurance (Maintenance) ▪ Selecting flights for different destinations and scheduling / assigning teams for ramp

inspections. Recording of Findings / Observations for different categories (1, 2, 3), corrective actions submitted by the concerned section and follow up till such time the findings are closed.

▪ Scheduling / assigning teams for spot checks of different areas of Engineering & Maintenance. Recording of Findings/Observations, corrective actions and follow up till such time findings are closed.

▪ Unscheduled Ramp Inspections and Spot Checks when ever asked by Management or Regulatory Authority.

7.3 Human Factor / SMS ▪ Reporting of SMS/HSE/Human factor related issues. ▪ Analysis, Risk assessment and their mitigation actions follow up of reported issues. ▪ Risk assessment of findings raised during internal audit.

7.4 Examination ▪ Record of submitted applications for PCAA licenses and Company Approvals.

Scrutiny and status of submitted applications. ▪ Conducting of Company Approval Exams by extracting questions from Question

Data Bank (QDB) and issue approval certificate to successful candidates. ▪ Record of Technical Qualifications (Licenses and Company Approvals) of PIA

Engineering & Maintenance Personnel.

7.5 Chief Engineer Secretariat ▪ Approval of vendors and their Quality Monitoring. Blacklisting or removal from list of

approved vendors as a result of quality monitoring. ▪ Record of Concessions / Limited Authorization issued by PCAA and issuing LA

termination report after concession / limited authorization expiry. ▪ Liaison with different sections of PIA and Regulatory Authority regarding incidents /

delays and their investigations. ▪ Liaison with PCAA for renewal of Licenses. (Application Acceptance / Scrutiny /

Submission to PCAA & Follow up)

Page 90 of 189


8.0 Maintenance Operations Support Center Procurement and logistics functions of PIA Engineering are performed on Oracle ERP. There should be 2-way interface / data-exchange capability necessary for functions defined here under.

8.1 Material Planning& Management

▪ Upload Readiness Log

As a major source for the aircraft configuration the Readiness Log to be uploaded. The functionality supports a comfortable automated upload / semiautomatic upload of data notwithstanding is the first A/C of a fleet or a subsequent one.

▪ Upload and maintain initial provisioning data

The initial provisioning to be supported by uploading the RSPL file notwithstanding it is the first A/C of a fleet or a subsequent one. A comfortable editing functionality shall support material planner by modifying the recommended and to actual Part Number (P/N) and quantity.

▪ Maintain Aircraft structure/ location

The aircraft master structure and location to be defined. This to be done by

uploading the readiness Log, and/ or by editing the master structure.

▪ Maintain Material Master Data

The material master parts list to be uploaded and edited. Also, the interchangeability

and the PIAC internal master P/N to be defined.

▪ Plan consumable based on planning parameters & past consumption

Beside the initial provisioning the subsequent material consumption of consumables and repairable to be planned. Functionality shall support this process by providing statistical data concerning past consumptions, calculations based on planning parameters but also an event forecast and the respective routine materials. Calculations concerning the reliability of on condition components and failure rates to be provided.

▪ Material provision for planned maintenance.

Based on the PIAC fleet maintenance forecast for letter checks, material planner shall get all needed information for planning provision of planned and unplanned material. Also, the derived from the standard BoM for letter checks budgeting information to be derived for financial planning for future checks.

▪ Monitor consumption and stock level

Material planner also need information on stock consumption in a given time frame. Based on this and on procurement parameters the reorder level to be optimized and populated to the inventory system maintaining in ERP.

▪ Material request.

Consumables and demanded to requested by the users to be requested by the system. The request shall have several levels of urgencies and the expected delivery date. When a material request s handled automatically the service level and the material budget to be updated.

Page 91 of 189


8.2 Rotables Control (LRU)

▪ Plan LRU float

The LRU float to be optimized, based on the net requirements for the fleet, the needed Turn Around Time (TAT) for overhaul and the logistic times. The needed information such as MTBUR to be provided for the float calculation.

Control lifetime

The system shall monitor the life time of LRU’s and Life Limited Parts (LLP’s) no matter if it is a hard time item or to be monitored on condition. If an assay is replaced from the aircraft, all subsequent sub-assay’s to be also removed automatically.

▪ Component history

The complete component history to be tracked and traceable in the system.

Working papers to be attached to this information in an electronic format.

▪ Component tracking

The actual location to be traced in the system whether it installed in the aircraft,

dispatched, at store or in a repair cycle.

▪ Shelf life / Environmental Conditions for storage

Some component may have a shelf life. Those components to be monitored. A report

will inform about reaching the end of a shelf life. Environmental conditions for storage

to be part of component master data.

8.3 Loan/ Borrowing

▪ Administrate loan of parts/ equipment / tools

When PIAC loan parts/ equipment and tools to other airlines, the loan and the return of

the goods to be monitored by the system.

▪ Administrate borrowing of parts/ equipment / tools

Also, when PIAC will borrow parts/ equipment / tools from other airlines. The borrowing and return of the goods to be monitored. The system shall also display LRU’s installed in the aircraft on loan basis.

▪ Support component pooling concept

In case of a component pooling concept. The system shall support exchange parts

based on a pooling contract.

8.4 Component exchange program

Support for component exchange program / Component support program. ❖ Contracts management for CEP/CSP. ❖ Work flow for entire CSP loop, starting from;

• components’ removal from aircraft,

• request generation to CSP vendor for provision of replacement part,

• dispatch of removed component to the CSP vendor,

• tracking of replacement part till arrival in PIA stock

• tracking of removed part till it reaches designated location, with early alerts to avoid late penalty.

❖ Component out/in history

In case part to be handled on an exchange program, the component history shall go with the component to the supplier. The exchanged part to be returned shall come with its documentation. The information deleted from the system and transferred to the supplier and received from the supplier and uploaded to the system in an electronic format.

Page 92 of 189


❖ Keeping track of NFF and generate appropriate alerts if the numbers tend to exceed the allowed limit.

❖ Reporting capability for components send to CSP in a given time frame with all serial numbers removal data (defect, aircraft, etc.

8.5 Contracted Maintenance

Aircraft Components are sent for repair to contracted repair stations outside PIA, where there is no in-house capability exist, or there doesn’t exist any parts exchange (CSP) or pooling arrangement. Support for such contracted maintenance should exist in the system thru an interface with ERP. System should generate a work order to track and coordinate such maintenance. ▪ The status of the component, expected return into the stock / system based

estimated through defined TAT keeping in view of the standard process parameters.

▪ Repair reports integration to the component history record upon return.

▪ Provision to update the respective system parameters & work order closure when a

component is scrap is approved on repair agency site or an offer for serial number

exchanged is approved from management.

▪ System shall maintain Permanent repair abroad list (PRA) for components sent on

contracted maintenance on routine basis, with all contract parameters defined such as

repair cost (power by the hour, flat rate, etc.), repair facility address, certification

warranty etc.

8.6 Warranty management

System should support Warranty management. Generally following broad

categories of warranty events occur in PIA.

i. Repair Warranty

▪ Components returned from contracted maintenance in stock room with valid

warranty should be offered on priority for aircraft demand.

▪ If a component is removed from aircraft and is still under warranty, the

relevant sections to be immediately notified for speedy process of return

dispatch to the repair agency.

▪ Last repair report should be readily available to correlate last repair area/parts

with current defect.

ii. Purchase Warranty

▪ Purchased Component with valid warranty should be issued on priority.

▪ If the component is removed from aircraft and is still under purchase

warranty, the relevant sections to be immediately notified for speedy process

of return dispatch to the repair agency.

iii. Induction Warranty

The warranty by virtue of new fleet/aircraft induction provided by the aircraft

manufacturer and applicable for 3-5 years typically. Individual serial numbers

warranty expiry shall vary in accordance with part of readiness log of a

particular MSN of aircraft.

❖ A warranty expiry field as part of component record should be maintained as long as the component is under warranty. For all 3 classes of warranty, an FOC work order to be generated automatically with water mark on the work order

Page 93 of 189


9.0 Required Functionality for Engineering Business Development

9.1 Client Contract

a) Define Client Master Agreement

The Client General Agreement with all general terms to be stored in the system.

This agreement is the client master document for the client maintenance order. b) Define Client Maintenance Order

The Client Maintenance Order defines the actual terms for the actual client order.

The terms could be a fixed price order, based on time and material, a flat rate or on

condition. The actual operation and the cost data collection to be mapped with the

client orders and the respective terms. c) Client Contact Details data base

A client data base shall contain all needed client master data, but also the client

history including performed order but also lost proposals in a bidding process.

9.2 Order Management

a) Define Client Order System according to the contract terms

A client order system according to the contract terms to be defined. The client order covering all relevant sub order to be defined. The sub order is defined related to the various order types such as routine and non-routine maintenance, modifications, defect rectifications, subcontracting, engineering services and others. According to production needs, those orders may have suborders. All orders are linked together. Collected data such as Mh and consumed materials shall be displayed on each level in the hierarchical order system.

b) Monitor Client Order progress

The progress of the client order to be monitored displaying the order start date and the expected completion date. This to be done also for all sub-orders. Also, the consumed Mh and materials to be displayed, as well as the subcontract orders.

c) Monitor Mh & parts costs

The Mh & consumed parts to be monitored for client orders. This functionality shall

ensure and monitor profitability of the client order.

d) Monitor Repair abroad costs and progress

Especially for client orders but also for the PIAC operation the Repair Abroad Orders to be monitored concerning progress and completion date but also concerning the accumulated costs.

e) Order progress information accessible by the Client

The client shall have the capability to access via web PIAC production system and

monitor the progress of his orders

9.3 Proposal Management

a) Define master proposal.

Proposal Masters are defined and used as text modules for an actual proposal to be

submitted. The modules represent the scope of services of PIAC Engineering b) Store customized proposal

According to the client needs and the PIAC Engineering capability a proposal has to be designed. The proposal to be stored in the system, the proposal status to be monitored: such as pre-proposal, submitted, in negotiation, agreed. Also, no longer

Page 94 of 189


valid proposal to be kept to follow the client history. The calculation scheme also to be attached to the proposal

c) Monitor proposal success rate

Some functionality is needed to monitor the hit rate in the sales process.

d) Capability List

A capability list based on fleet, engines and part numbers and the respective activity type to be stored in the system. This is to be displayed to the market, but also used to calculate the scope of service and the costs for subcontracting.

9.4 Profitability Analysis

a) Calculate client order profitability

The client proposal is calculated with a particular profitability perception. This is to be monitored during performing the client order. Finally, after completion of the client order, the profitability of this order to be calculated.

b) Calculate complete client profitability

By maintaining the client relationship, further contracts to be performed by PIAC

Engineering. A profitability analysis along with the client history to performed.

c) Profitability analysis by region & products

PIAC Engineering Sales and Marketing needs further information for strategic and tactic decisions. For that reasons contract volume and profitability analysis to be performed by region and offered products. Also, an analysis concerning the target budget and actual performed volume per region and product to be monitored.

Page 95 of 189


10.Required Functionality concerning Power Plant Overhaul Power Plant overhaul has the facility to maintenance / repair / overhaul for Engines, APUs

& Landing Gears of various types. Functionality description outlined here in sub-section 10

to be considered applicable all of the three.

10.1 Production Planning

▪ Long-term planning Engine/ APU/ Component shop visits

Based on the LLP, hard time, on condition, engine removals, Engine Health monitoring data, on above information, shop visit to be planned and the first scope of work to be defined.

▪ Production/ capacity planning

The planned work load and the available human resource capacity to be balanced.

▪ Forward/ Backward event planning (incl. projection thru Gantt-Chart)

The engine/ landing gear shop visit to be planned on a project chart to show the duration of subsequent steps in a Gantt-Chart. A forward and backward planning to be provided. By getting real time data and feedback by production the chart shall be updated.

▪ The Bill of Work (BoW) and subsequently the Bill of Material (BoM) to be

defined on several steps according to the several inspections performed. Also, a full

integration between BoM and the subsequent material planning processes are

essential. Available parts locked others to be procured.

▪ Engine/ module disassemble management

For engine disassembly, the as is hierarchical parts list with part number, serial number and mod status to be provided. This list to be provided at the disassembly table to check the as is parts list and mark those parts to be removed from the engine. The parts to be removed, a removal tag to be generated by the system

▪ Engine/ module/ component build-up control

By building-up the engine a new hierarchical parts list to be defined by using disassembly parts list as a master. The new parts to be installed also to be notified in the parts list. A final check to be done by mirroring the new parts list against the former one and check modification status and the compatibility of parts.

▪ Other related functions performed in the shop

• Man-Power Planning in engine Overhaul shop section.

• Plan the Overhaul of engines/APUs and testing in-accordance with approved schedule maintained by TSE and manufacturer maintenance manuals.

• Plan the overhaul/ repair of engines/APU’s and engines components, not covered in PIA Engineering capability, at a third-party facility, in coordination with Repair abroad section.

• Components’ scrap process workflow.

• Inter shop engines /APU’s / parts movement tracking.

• Processing of vendors’ repair estimates/invoices/warranty claim.

• Maintaining history of LLPs.

• While estimating engine repair completion time, TAT of items sent to for third-party repair should be considered thru integration with related system/module.

Page 96 of 189


10.2 Engineering Functions related to Engine/APU/LG

▪ Modification status dashboard

The engine/ APU/ landing gear/ component modification status review for all serial numbers available in the system, including a hierarchical modification status view of the installed subassemblies.

▪ Modification management

Provision for complete modification cycle, starting from modification planning, scheduling, execution (in-house or from third-party), release and update of relevant system parameters.

▪ Update Engine/APU/ LRU counters & status

System should provide the capability for complex assembly management where counters (Fh/Fc/Days) of main as well as sub-assembly(s) are updated in parallel, whether on aircraft or in shop. The sub-assembly counters to be taken separately upon removal from the main unit (Engine/APU/LG). For any new subassembly installed, this becomes part of the complex assembly and respective counter are update along with main unit.

▪ Update Engine/ APU/ LG modification history

Any repair or modification to be added to the unit life record, with attachments as required.

▪ Update serialized components

The master parts list and the as-is parts list including LLP’s to be maintained, kept

and updated.

▪ Archiving performed work and all related documents.

All working documents and certificates to be archived and linked with the related

unit. The LLP’s and related component history to be updated. The record should be

easily printable reviewable for audit purposes.

▪ Create/ update/ revise Shop Work Sheet

System should provide capability for creation /update of work/task-sheets to be created, which are part of work package. All created work/task sheets should be maintained in a catalogue.

▪ Shop finding reports Defects and discrepancies identified by inspection to be entered in the system. The defect notification shall use a thesaurus, in order to allow statistical analysis. In case of parts the leading discriminator shall be the part number, in other cases the ATA chapter. The defect notification to be used for the reliability management, but shall also trigger the repair or scrap process.

▪ Updated OEM manuals

System should support the availability of updated Engine/APU/LG & Component

manuals thru Documentation management function.

10.3 Engine Health Monitoring

The system should either indigenously support the Engine Health Monitoring or

through an interfaced third-party application.

The EHM should be based upon industry best practices.

10.4 Shop/ Work Place Control

▪ Work center performance monitoring

Page 97 of 189


Production planning shall monitor work load and performance at each work center. The backlog to be displayed, as well as open time slots.

▪ Backlog priority management at Work Center

A priority management to be available for the work order backlog. Especially the

priorities between close loop parts and repair for stock to be well balanced.

▪ Mh and Machine hour recording

For each work order, the man hours and machine hours to be recorded by using

base code: clock-in and clock-out

▪ Tracking & tracing parts in the shop

Using the clock-in and clock-out information, parts to be traced and tracked in the

workshop by acknowledge arrival & departure of the part at the work center (WC).

▪ Multi stage component routing

In case a unit to be overhauled consists of several assays and sub assays, a multi stage routing and component tracking to be available. The system shall provide support to define time limits for each work order to optimize the turnaround time of the complete unit.

10.4.1 Engine/APU Maintenance/Overhaul Work Flow. System should provide process flow for Engine / APU shop functions;

• Disassembly, cleaning, inspection assembly of engines.

• Static and dynamic balancing of rotating group.

• Maintenance support like BSI, inspections, parts replacement. ▪ Video imaging and recording on large gas turbine engines as and when applicable. ▪ Fan blades replacement. ▪ Overhaul, buildup of APUs.

10.4.2 Engine/APU Test &QEC Build up section Work Flow. ▪ Test & troubleshooting of engines /APU’s. ▪ Troubleshooting, Trim Balancing, Preservation of engines and component

replacement related to b/up of engines. ▪ Support workflow for engine buildup. ▪ Support workflow for incoming and outgoing inspections and identify shortages for

completion engine / APU build up.

10.4.3 Landing Gear Shop Work Flow. Support workflow for landing gear maintenance, of various types.

▪ Material Planning for hard-time components. ▪ Subassembly removals including harnesses for shop test/repair. ▪ Assembly completion including L/G harness installation.

• Testing & Release.

10.5 Budgeting & Financial Control (through integration with ERP)

▪ Budget planning for Engine/ APU/ Component OH

Based on the fleet plan, the engine/ APU/LG& installed component removal rate; the number of shop visits to be defined. Based on these key figures, the needed material & Mh recourses for in-house repair and the expected budget for subcontracting repair abroad to be calculated.

▪ Repair/ overhaul cost control

The repair/ modification of each engine/ APU component to be monitored by posting the spares / subcontracting costs and the consumed Mh on the Repair/ overhaul order.

Page 98 of 189


11. Required Functionality for Tools Managements, & Standards Lab

11.1 Tools Master Data

a) Define tools, GSE and figures locations & quantity

All tools GSE and other units to be registered with location and quantity

b) Define tools master data.

The master data to be maintained

c) Functionality for reservation, in-use, available tools

A requisition functionality to be in place with availability status and to block the required tool for a period.

d) Transportation order for tools

A dispatch order to be defined for transport the tools

e) Statistics concerning utilization

Statistical function for concerning usage of tools.

f) Maintenance planning of tools & repair

Maintenance plan for fools and repairs. Also, a repair order to be submitted.

11.2 Calibration of tools

a) Register tools

All tools to be calibrated to be registered in the system, with ownership specified.

b) Schedule tools calibration

a) A scheduling functionality to be available for calibration purposes. Optimal

planning with staggering of Cal required equipment visits to Standards Lab. The forecast for calibration is given to concerned department by providing a report.

c) Report compliance

A calibration report is given and the calibration results are notified. The serviceable or unserviceable status of the tools is marked. This status will have an impact to the tools reservation system.

11.3 Standards Lab Functions PIA maintains an Electrical & a mechanical Standard Lab. Both operates in a similar fashion, and supports calibration services for electrical/electronic & mechanical equipment calibration.

MRO / M&E system should support following work flow; b) Tools/equipment work order generation as received from tools store. c) Calibration check/adjustment/repair performed and recording the results in

the system. d) Issuance of Calibration sticker / certificate with next due date. e) Intimation to respective tool store for receiving of the calibrated

tool/equipment. f) Where local Cal/repair capability not exist, sending the tool/equipment for

contracted maintenance g) Capability for Tracking of Cal/Repair cycle at Standards Lab by the concerned

tools store / user section.

Page 99 of 189


C3 General Requirements of the MRO / M&E System

1. Ability for Integration with ERP &Interfacing with Sabre, IBM Lotus Notes

➢ Oracle ERP system controls all major PIAC resources. A smooth integration between the Oracle ERP, and MRO / M&E system is required. The following areas for integration are highlighted:

Financial Accounting, Financial Control, Budgeting, Purchasing, Logistic, HR, Training & Qualifications.

➢ Sabre Products AirFlite, AirCentre & Sabre AirVision applications are used in Flight planning &scheduling. An interface to MRO / M&E Solution is required at minimum; Following areas for interfacing are specifically highlighted; Schedule/Slot/Fleet management, Flight Plan/Movement manager

➢ AIMS ➢ Any other Application

2. MIS & Reporting

▪ Key Performance Indicators (KPI) to be reported for all major sections in PIAC

Engineering on regular basis. The KPI to be defined by PIAC.

▪ The PIAC Engineering Management shall get regular reports concerning the regular and un-regular operation.

3. The System will control the day-by-day work

▪ All work packages, tasks and business activities will be initiated and controlled by

the system.

▪ Subsequently all Labels, Orders and Certificates are printed by the System.

4. Drill down option and flexible reporting

a) From the top to the bottom it must be possible to generate more details if required.

From the individual A/C to a BoW, to the individual WP, to the JC and finally to the

details of each JC must be possible.

b) Beside a number of regular used reports, a flexible report generator shall prepare

reports on occasional basis.

c) Tracing of information

Within the system, it should be possible to trace information along a logical path. It

should be possible to see a component removal order, follow the PIAC intern

dispatch order of the part, see the request for proposal, the repair order, the customs

Page 100 of 189


clearance, the QA reports, the invoice, the invoice verification process, the final

payment posting etc.

d) Dashboard for Management / Planning & Maintenance Operation Center

A Dashboard for showing on PC and scalable to large screen regarding status of the entire fleet whether on ground or in air. Inflight defects reporting to be supported through ACARS or other industry tools, while on ground current maintenance activity (planned / required) as highlighted trough Tech log, MIC, deferred defects, unscheduled events etc. should be displayed. Option to select a single station, bay, fleet or aircraft, or grouping of more than one should be possible.

5. Flexibility

a) Organizational changes shall be easily addressed in the System by re-configuration.

b) In case of outsourcing of parts of the production units (e.g. Base Maintenance,

Engine OH), the system shall be able to be customized accordingly.

6. Advanced MRO / M&E Concepts

a) System Should support e-Tech-Log (incl. Cabin Log), with tablet / mobile solutions

both online and offline (with seamless synchronization upon network availability)

b) Airplane / Engine Health monitoring,

c) Analytics Tools for predictive & prescriptive troubleshooting of defects. Future

upgradability for IoT solutions.

d) RFID, Smart card, barcode based emerging trends.

e) Solution provided by bidders must be compatible / available on all mobile/cell

phone, tablets &iPad.

7. Required Interfaces of the new MRO / M&E System

a) The Aircraft log data (Fh, Cycles, Landings) shall be entered at one location at PIAC. -

Or automated upload of the SITA telex. This shall be done within PIAC operations. The

MRO / M&E System shall have an interface for a real-time data upload. ACARS shall

be used where possible.

b) The Aircraft Rotation Plan shall be available online for PIAC-Engineering. LM

Production Planning shall actively use the displayed ground time for the medium and

Page 101 of 189


short term maintenance task planning. The Aircraft rotation plan will show interactively

the planned A/C assignments to routes and the slots maintenance events.

c) The Commercial Flight Schedule shall be online available for long and medium-term

planning. PIAC Engineering will request online slots for letter checks (A, B, C, D).

d) PIAC Operations will monitor operational performance and A/C dispatch reliability. An

online interface will provide the data for PIAC Engineering

e) PIAC Finance is responsible for the Financial Budget and Financial Accounting. The

data are shared with PIAC Engineering on online basis for performance monitoring and

planning purposes. This would require an interface with Oracle ERP.

f) Automated upload /availability of all up-to-date (current revision) OEM manuals, such

as AMM, IPC, SRM, EMM, TSM and others using the S1000D standards.

g) The Service Bulletins (SBs), ADs, etc. shall be auto up-loaded from OEM website.

h) Material Master Data shall be up-loaded using the AMTOSS and SPEC 2000 data

standards.

i) Upload of Vendor capability list, price list, availability status and others, for contracted

maintenance.

j) Electronic exchange of agreements, purchase order, delivery/ repair status, invoice,

payments. Supported formats shall be XML, SPEC2000 and others. An international

B2B communication platform to be interfaced for exchanging procurement and repair

status information.

k) The new System shall support a WEB Portal to provide major information and data for

production to an Intranet Web Portal. It is the target, to avoid time consuming and

outdated paper based distribution of information.

l) The system to be ready for RFID applications to be integrated. Also, the PIAC

employee ID card to be read for employee acknowledgement, specifically to monitor

job/task Mh. consumption.

m) Working papers such as Job Cards and parts tags to be printed with barcode. Bar

code readers to be integrated for man hour recording and parts tracking.

Page 102 of 189


SECTION D

SERVICES REQUIREMENTS

Page 103 of 189


D1. Implementation

1. As part of its proposal, the Bidder must submit an Implementation Strategy and Plan

which caters for the following, to be performed by the Bidder: -




any other required Utilities, on the Interim Server/s.



any other required Utilities, on the Permanent Servers.

1.4 Implementation of Database security features

1.5 Development of Business Requirement Document for each functional area,

which maps the business process for the parameterization of MRO / M&E

Package. This document should be based on PIAC’s reengineered business

processes that would be made available to the Contractor. PIA will review

and approve this document within ten working days of submission before

Contractor can start work on parameterization / configuration of the MRO /

M&E.

1.6 Development of business case scenarios for testing MRO / M&E Package.

1.7 Parameterization of supplied Software i.e. the configuration of application

software via selection of in-built values, setting up of tables, etc. to meet the

business requirements.

1.8 Software modifications, where required, to supplied Application software and

development of extensions and/or modules to meet the business

requirements.





1.10 Integration with PIAC’s other applications such as Oracle ERP, Sabre

applications, AIMS, PIAC website, etc.







1.14 Design and implementation of Online and Batch job operational procedures

until implementation is successfully completed at all locations.

1.15 Bidder will provide regular progress reports of the project pinpoint

obstacles/short comings if experienced well in time.

Page 104 of 189


1.16 Quality Assurance for Bidder related activities.

1.17 Any other tasks required in successful delivery of the supplied products and

services.

2. The Contractor must utilize airline industry specific rapid implementation templates

to ensure quick implementation. Details of such templates should be submitted with

the Technical Proposal.

3. A detailed comprehensive project plan is to be prepared by Contractor and

submitted as a part of the proposal. The plan shall be mutually approved and

incorporated as part of contract and reviewed at regular intervals.

4. The Contractor must submit a detailed project organization structure identifying, by

name, the specific individuals who would be assigned different tasks of this project.

4.1 The Contractor must assign a full-time Project Manager to manage this Project.

This person must be from the list of Lead Consultants submitted by the

Contractor in response to the EOI. He / she must have the experience of

implementing the proposed MRO / M&E SOLUTION in at least two airlines.

His/her detailed CV including experience of managing MRO / M&E IT and other

Projects, MRO / M&E IT Package Certification, if any, the number of MRO / M&E

projects managed and the number of years on each project, etc. must be

submitted along with the Proposal.

4.2 A personnel roster containing detailed responsibilities of Contractor staff who

shall be assigned by the Contractor to perform duties or services under the

contract should also be provided. The roster should include estimated number

of hours to be worked on the project for each person broken down in different

phases of the project; it should also clearly identify the start and end dates for

each phase. These staff members should be from the list of implementers

provided in response to the EOI.

4.3 If additional members are assigned to the project, their detailed CVs should be

submitted as part of the proposal. PIA recognizes that occasional substitution of

Contractor staff may be necessary after an apparent bid winner is determined

and during the project. Staff proposed as substitutes must have qualifications

equivalent to or better than those being replaced and must be approved by PIA.

5. The Contractor must provide, by phase, the proposed number of personnel to be

based on-site at PIAC’s premises. Space and other logistical requirements to be

provided by PIAC to the Bidder’s Implementation Team should be specified.

6. The Contractor’s implementation plan must take into consideration the business

priority areas and applications.

Page 105 of 189


7. The Contractor will develop a system turnover plan which indicates the conditional

criteria required to fully turn over the daily operation of the system to PIA technical

staff. At a minimum, the turnover plan must include the state of readiness required

for system turnover and all required documentation.

8. System Performance: During system installation, the Bidder will evaluate

performance factors including, but not limited to, transaction volumes, response

times, CPU utilization, and input/output activity. The Bidder will be responsible for

tuning the application to meet acceptable response times.

9. The Contractor must submit a detailed Testing Methodology. The Bidder may

perform Unit, Integration, and Systems Tests off-site; however, the official Systems

Test and all User Acceptance Tests must be performed on-site using PIAC’s testing

environment.

10. Capacity Evaluation: The Contractor will conduct a Capacity Test that will include stress

and volume testing. Capacity testing shall include a stress test that includes simulation

of at least 30% of the system workload and volume tests that test the database activity

against at least 30% of the data volume. The Contractor will document, the conclusions

resulting from the test.

11. Project Management and Reporting: The Bidder is required to maintain a project

plan covering its components of the project and each individual phase. The plan

shall include project organization, work break down structures, schedules, critical

path determination, and other features required to track and manage this project.

12. Project Quality Management: In its proposal, the Contractor must describe its

approach for assuring the quality of its components on this project. The proposal

must demonstrate an understanding of the Contractor’s ultimate responsibility for

quality and define a comprehensive set of reasonable and effective practices for

fulfilling that responsibility. Contractor must also specify whether third party audit /

quality assurance visits will be undertaken and who will bear the cost of these visits.

13. Acceptance Testing: PIAC’s M&E Team will conduct a rigorous acceptance test of the

system. PIA user staff and information system specialists will exercise all system

functional aspects using appropriate test data (use cases developed from real-time PIA

engineering & maintenance operations) to assure that the system meets defined

business and technical performance requirements. During this test, PIAC’s MRO / M&E

Team will identify required modifications and document them through the problem

resolution or change management processes (described below) as appropriate. The

Contractor shall modify the system as required and provide new versions of modified

components to PIA for testing. PIA will notify the Contractor in writing when it

determines that the system is acceptable.

Page 106 of 189


14. Problem Resolution: The Contractor and PIAC’s MRO / M&E Team will cooperate to

resolve system problems found during acceptance testing and production use,

including the warranty period. PIA will prioritize and report problems in a written

format. The Contractor shall track these problems to closure and report their status.

The Contractor shall evaluate each reported problem, estimate the time needed to

resolve the problem, identify potential impacts on the system and the project, and

report to PIA. If PIA decides to proceed, the Contractor shall resolve the problem

according to its assigned priority.

15. Change Management: PIAC’s MRO / M&E Team and Contractor will cooperate in

managing changes to previously agreed upon system functional capabilities. PIAC’s

contractor will identify potential functional changes and propose these to the

Contractor in writing. The Contractor shall evaluate each proposal, identify potential

impacts on the system and the project timeline, and report to PIA. If PIA decides to

proceed, it will prioritize the change and authorize the Contractor in writing to

perform the work. The Contractor shall track the status of in progress change orders

and report to PIA upon request. However, cost escalation will not be allowed under

any circumstances.

16. Configuration Management: The Contractor shall manage version releases of all

contract deliverables and certain other critical documents as determined by PIA.

This process shall assure that the status of all deliverables is known, that only

approved versions are released for production use, that prior released versions can

be recreated, and that changes are made to released deliverables only when

authorized by PIA. The final release of each controlled deliverable must reside in a

library (preferably computer based) under PIA control.

17. The contractor will ensure that the MRO / M&E solution is in compliance with

regularity requirements of PIA’s Organization approval under Pakistan Civil Aviation

Authority’s ANO-145. PIA Quality Assurance will apply to Pakistan Civil Aviation for

compliance verification audit. The contractor will be required to cooperate with the

PCAA audit team, by providing functionality demonstrations and reports as required.

Any non-compliance shall be addressed by the contractor in liaison with PIA QA & IT

Team, till compliance is verified.

D2. Training

1. Training is required in two main areas: (a) Technical Support Staff, and (b) Systems

Users. Technical Support Staff will comprise of System Operators, System

Administrators, Database Administrators and Developers. Systems Users will

comprise the staff from different functional areas of Engineering & Maintenance, at

all stations. Three levels of Systems Users are currently identified as: Key Users

(responsible for system parameterization in the future), End Users and Senior

Management (who are expected to be provided System Overview). It must be

classroom based training.

Page 107 of 189


2. As part of the proposal, the Contractor must describe in detail its approach to

meeting the training requirements for each audience. The description must include

methods proposed to deliver both training and documentation. The Contractor

should describe the general content of all training materials, training courses, and

documentation proposed.

3. The Contractor will be required to develop a Training Strategy to ensure that all

identified Systems Users and Technical Support Staff is thoroughly trained in the use

and support of the system. Training for Key Users must be imparted early in the

implementation stage, preferably in the first month, to enable them to actively

participate in the parameterization process

4. The Training Strategy should include a training solution to support the training of

users throughout PIA Engineering & Maintenance covering all functionalities and

Add-on applications. The Contractor will be required to develop formalized

classroom training sessions, to be delivered by their staff, for each of the user groups

identified to ensure that the trainees become familiar with all the system features of

the implemented applications. In addition, where required, for technical staff,

informal training should also be included.

5. For PIA technical staff, the Training Strategy should include a plan to train the

required staff in the Development and Administration tools supplied, and provide

them the knowledge to efficiently operate, use and maintain the system independent

of Contractor assistance. Technical training materials must be comprehensive and

detailed.

6. The Training Strategy will address, at a minimum, the following:

a) Description of the Course, the Course outline, specifications of the number and

appropriateness of staff who will attend, probable dates for classes, etc.

b) Proposed content of all training materials.

c) Description of proposed software / tools (these may include training aids,

manuals, on-line references, quick reference guides or templates, or computer

based training), and their use during the training.

d) Details of the physical locations to be used for training.

e) Training evaluation methodology

f) The names, qualification and ―Formal Training‖ experience in man-months, of

the instructors for each training course.

7. The Contractor is required to provide materials for training users in central and

remote locations. The User Staff training materials must cover, at a minimum, the

following topics:

a) Systems Overview

• systems benefits;

• data inputs, outputs, and reports produced;

• major systems business functions;

Page 108 of 189


• Users‘ Manual contents and usage;

b) Systems Usage

• entering data and data validation;

• data correction and user help features;

• menu and system function traversal;

• problem recovery;

• report contents, report generation / suppression;

• search and inquiry features;

• record update procedures;

c) Systems Operation

• job recovery;

• job scheduling;

• job cycles (daily, monthly, quarterly, annual, and special);

• special forms usage;

8. The Contractor must provide material for training Technical Staff such as database

administrators, system administrators, operators, and developers. This material

must cover all aspects of systems design, operation, and maintenance including, at a

minimum, the following topics:

• application and database design and architecture;

• application structure and module / sub-module / program / subroutine

relationships;

• application start-up / shut-down procedures;

• application back-up, recovery, and restart procedures;

• data dictionary structure and maintenance procedures;

• database logical and physical organization, and maintenance procedures;

• application security features;

• audit and testing procedures;

• system data entry; checking, correction, and validation procedures;

• user help procedures and features;

• system troubleshooting and system tuning procedures and features;

• system administration functions management;

• setting and changing system password and user ID security features;

• system interface processing;

• on-line and batch processing procedures;

• unique processing procedures;

• report generation procedures;

• Menu structures, chaining, and system command mode operations.

9. PIA requires the training material on CDs. All training material provided by the

Contractor will be reproduced and used as needed by PIA.

Page 109 of 189


10. Cost of Foreign Training, if proposed, should be included in the Contractor‘s

Commercial Proposal and include all expenses related to travel, accommodation,

tuition fees and other incidentals.

D3. Data Migration

1. PIA currently uses internally developed application named ‘PAMMIS’ (PIA Aircraft

Maintenance Management Information System). The underlying database is

IBMDB2 format.

2. The application is used to perform functions such as Engineering, Tech-Log, LRU

Management, Tools & Calibration, Fleet Performance, Work package & Check

Planning, Readiness Log, Shop functions with Operator Mh, AD/SB records, and

certain other minor functions of the entire PIA fleet.

3. The Bidder should include, as a part of its proposal, a Data Migration Strategy which

includes description of its general approach to the data migration process for

configuration, seed, history &cutover data.

4. The Data Migration Strategy must address, at a minimum, the following:

a) Migration process (automated or manual, verification procedures)

b) Migration schedule / time frame

c) Migration preparation task outline

d) The resources that will be required.

e) Any training requirements

f) The programming effort that will be undertaken OR acquiring of third-party

industry solution/application, should also be described.

5. The Successful bidder would be required to prepare a Detailed Migration Plan, which

must address the following:

a) Identify data elements to be migrated.

b) Identify any special forms and procedures

c) Identify any control procedures and evaluation criteria.

d) Identify, with the assistance of the PIAC, the personnel needed to participate

in the migration of the data.

e) Plan any interim file maintenance requirements.

f) Develop migration programs (This includes specifications, program coding,

test plans, and complete testing)/acquire third-party industry solutions.

g) Present migration plan, procedures & program to PIAC for approval.

6. PIAC expects the Bidder to perform the following tasks: -

Study the existing application and databases and;

a) Ensure smooth transition without compromising routine operations and

without any downtime.

Page 110 of 189


b) Design and develop/acquire a solution including intermediate utility (if any) to

migrate the data from existing databases to the new databases, ensuring data

cleansing and integrity.

c) Demonstrate and test this data migration on sample test data from existing

live applications.

d) Develop and document all operational and technical areas for above solution

D4. Documentation

1. As part of its Technical Proposal, the Contractor must describe the level and types

of documentation that will be delivered. This documentation must cover each level of

operation, for example: user, security administrator, database administrator,

operator, developer, etc.

2. Two complete hardcopy sets of documentations for all Bidder supplied components

for this Project must be furnished, in addition to softcopies on CDs.

3. The Manuals should feature clear organization of content, easy to understand

language, useful graphic presentations, and a thorough index and glossary. These

will under the following categories:

• Detailed process manuals

• User manuals

• Operational manuals

4. These manuals must address the view of the system required by business unit staff

(end users). It must contain sufficient information to enable the user to

independently operate the system, troubleshoot simple problems, and correct

problems. The manual must be able to serve as a reference guide and a teaching

aid. It must cover all facets of system functions and operations, including:

• Complete instructions for the users, completely explaining the use of each

system function;

• System usage scenarios, based on real world examples drawn from the day-

today workloads of typical users, that fully describe and explain the salient

features and operation of the system;

• How input data are stored and related between system records;

• How to generate/suppress standard and ad hoc reports;

• Normal report distribution;

• Prioritization processing, system determined priorities, and user override

procedures;

• System log-on, log-off, and security features;

• Error messages and error correction procedures;

• Help features and usage;

• System troubleshooting;

• Mandatory data fields and default data values;

• Traversing system menus;

Page 111 of 189


• Screen layouts and contents;

• Inquiry functions

5. In conjunction with the Users’ Manual, Quick Reference cards will be produced by

the contractor, which will be an immediate aid to the user and quickly describe

operations.

6. The Technical Manuals must address the view of the system required by

developers, administrators and other technical personnel. It should provide an

understanding of the application; database design and file structures; relationships

between programs, security; troubleshooting; special constraints; and other

operational guidelines.

7. Copies of all licenses, warranties, maintenance agreements and similar materials for

all Bidder delivered components of the project must be furnished separately.

8. Contractor must submit sample copies of all documents that it will prepare / deliver

to PIA during the course of this project.

D5. Warranty and Maintenance Support

1. The Bidder will provide warranty services for a period of at least one year for

software and a minimum of three years for hardware by ensuring that the system in

every way meets the specifications stated in this RFP. The warranty begins upon

PIAC’s written final acceptance of the system14. All warranty support services,

whether on- or off-site, are to be rendered free-of-charge to PIAC; the Bidder shall

be responsible for any travel costs associated with warranty support services. The

warranty to be also given for the underlying DBMS.

2. Separate and apart from the warranty support services, the Bidder shall provide

support (“Maintenance”) services for Applications, and DBMS beginning upon the

end of the warranty services and extend upto three (3) year thereafter.

3. The Bidder must describe in detail in the Technical Proposal its User and Technical

Support Plan for the warranty and maintenance periods, covering the resources,

timing and procedures that will be available to provide this support. The plan must

include identifications of procedures for on-site and off-site maintenance during

normal hours of operation, for:

• On-site fault diagnostic techniques;

• Remote or tele-diagnostic fault diagnostic techniques;

• Average time to arrive on-site;

• Mean time to fix major system components; •Fault escalation procedures;

• Maintenance of error logs.

4. The Bidder must specify the various categories of problems it will support and

describe the severity levels of problems. The escalation process must assure

Page 112 of 189


appropriate management contacts can be made in the event that the support

response is not effective. PIAC would like to sign a Service Level Agreement (SLA)

(that would include penalties for non-performance or poor delivery) for maintenance

support with the Contractor.

5. Details of the establishment of an effective “Hot Line Telephone and Support Desk”

service should be provided. Internet enabled support, if available, should be

highlighted.

6. PIAC may require the Contractor to develop additional customized reports, screens,

workflows, etc. during the maintenance and support period. Contractor must specify

in its Technical Proposal a solution to accommodate PIAC’s requirement. The Price

Proposal must contain the pricing mechanism for additional development /

customization.

7. The Bidder should provide a list of clients for which MRO / M&E Package

Maintenance Support is, or has been provided during the past three years. Details of

the modules supported should be included.

____________________________________________________________________

14Acceptance

The MRO / M&E Solution shall be deemed accepted upon the successful completion of Acceptance Testing of all supplied applications and modules, conducted in accordance with PIA's Acceptance Criteria which will test the desired functionality and interoperability of Contractor supplied applications and modules.

D6. Version and Upgrades

1. Contractor must ensure that training material / software / process documents are

duly licensed for the purpose of implementation and use by PIAC of the MRO / M&E.

These are to be of latest version and Contractor must ensure up-gradation of all

modules / material / process documents during the warranty period and as part of

after-warranty maintenance support.

2. During the implementation and subsequent rollout Contractor would be responsible

to arrange and provide free version upgrades of all components under its

responsibility. Contractor must ensure that at the time of handing over the solution to

PIAC all components are of the latest release and that the total solution is certified

by the Contractor for completeness.

3. All updates. Additional features, version and upgrades will be part of the cost and

PIAC will not pay any such cost for the change, within warranty period.

Page 113 of 189


D7. Information Needs of the management and Application Requirements

PIAC requires management information systems that support its decision makers by

fulfilling their daily information needs and also assisting them in creating different

scenarios and providing what-if analysis.

The CEO, CTO and other key senior management personnel are responsible for managing the day-to-day operations of PIAC with respect to Engineering & Maintenance. Their information needs pertain to monitoring, controlling and directing the operational and financial management activities of Engineering & Maintenance particularly; ▪ Close and thorough monitoring of on ongoing & planned maintenance events,

projects& their associated cost. ▪ Safety & regularity Audit compliance status, plans & associated costs if any.

The information should be available as desired, and may require interfacing with PIA internal systems. The format of information shall aim at comprehension, analysis & decision making.

D8. System Security

System must be secure enough to handle the internal and external threats. SSL

security and firewall must be integral part of the proposed solution.

Page 114 of 189


SECTION E

PRODUCT REQUIREMENTS (OTHERS)

Page 115 of 189


E1 DBMS and Database Administration Tools

The Contractor is required to supply the latest version of DBMS that effectively supports

the proposed MRO / M&E Package. To this extent certification of MRO / M&E

manufacturer that the particular version of the DBMS is supported by the MRO / M&E

should be provided.

1 Database schema definition, management, query and reporting facilities must be

provided.

2 Historical transactions must be maintained by the DBMS. Facilities for reviewing

transactions, multiple transaction roll back and transaction log reporting are required.

3 Database update facilities must include features such as the use of working copies and

status reporting on query and update operations.

4 The system must provide locking mechanisms for update and delete operations.

5 The system must maintain concurrent control mechanisms to ensure the correctness of

transactions and to detect and resolve deadlocks on the network.

6 The system must support authorization lists and groups for create, read, update and

delete.

7 The provision of on-line facilities to manage transactions and overall on-line system

performance is desirable.

8 The system must provide users and applications with distribution independence.

Users do not need to know where database objects are located.

9 The system must operate in a distributed environment where different nodes of the

network run at different functional levels.

10 The system must have the ability to automatically recover and restore the database

fully to the last consistent state after a media or system or database failure.

11 The ability to notify users as to what transactions were being processed but not written

to the database during a crash is highly desirable.

12 The system should have archive logs and checkpoint facilities and the capability to roll

back / undo to any one checkpoint.

13 The system must continue to be available to users during any backup process or

alteration of the database schema’s and definitions.

14 The system must support one-to-one, one-to-many and many-to-one relationships.

Page 116 of 189


15 The system must be capable of working in a multi-tier environment, and provide the

appropriate tools for partitioning the location of the processing. All tuning must be

independent to the user.

16 All information in the database must be represented as values in the table.

17 Null value support (as opposed to empty character strings, blank characters or zero)

must be available for all data types.

18 Database recovery must be made in minimum acceptable downtime. Acceptable

downtime is to be negotiated and agreed upon

19 DBMS should have a support for ELT

20 DBMS should have support for SAN storage and cluster environment

21 Load balancing and failover must be supported to minimize down time

22 DBMS should support DR sites and automatic standby configurations. It must be

capable of operating in the DR environment and support synchronous as well as

asynchronous data replication at remote DR site

23 DBMS should be capable of supporting large amounts of data in terra bytes

24 DBMS should have support for transmission of data from other new systems as well as

exiting legacy systems

25 It should support libraries to enable backup on tape and disk drives

26 It should have support for new firewalls and n-tier network architecture.

27 It should have support for Analytics, OLAP, OLTP and DSS systems

For effective monitoring and management of the database, the Contractor is required to

provide, as part of its solution, Database Administration Tools that will help database

administrators in database monitoring, storage analysis, capacity planning and

performance monitoring and including trend analysis, size estimation and table creation.

E2 Application Development Tools

All application development and maintenance will be carried out on the centrally located

development server. The Contractor will be required to propose and supply application

development tools, consistent with the proposed MRO / M&E Package. It is expected that

the proposed solution comes with a built-in 4GL development environment tool set.

Page 117 of 189


E3 Query and Report Generator Tools

The Contractor must provide complete query and report generator functionality, preferably

within the provided system. The report generator functionality must include a scheduling or

production process for routine reporting.

The report generator functionality must be robust and oriented to the skills of "average"

desktop systems users and should support SQL. Formatting and statistical capabilities

such as averaging, multi-level sub-totaling, percent change comparisons, standard

mathematical operations and financial calculations is required. Generated reports must be

able to be saved in several output formats, at a minimum: Data Analytics, web-services,

APIs, XML MS Word, MS Excel, Text, PDF, HTML and XML.

The Contractor must describe its query and report generator systems in detail in the

Technical Proposal.

E4 Interim Servers and Operating System

1. PIA intends to purchase, the Server hardware and Operating System software required

for the MRO / M&E Application and Database.

2. PIAC’s purchase of the required Server Hardware and Operating System software will

depend on the selected Contractor’s recommended architecture in accordance with

details provided in Section E – Subsection E4.

3. However, in order to avoid any delay in meeting the Project completion milestone, and

to cater for the lead time required by PIA in the procurement process, the Contractor is

required, as part of its proposal to provide, without any cost to PIA, an Interim Server

and Operating System Software, as follows:

3.1 The Server, (or Servers) will be installed by the Contractor at PIAC’s Computer

Centre.

3.2 The Server(s) will be used for the purpose of configuration of the MRO / M&E

Package, development of Add-on applications, training of staff, and testing the

system.

3.3 All necessary hardware components such as CD-ROM drives, tape drives (for

back up purposes), etc. should also be provided on an interim basis.

3.4 Software components, such as DBMS, Development tools, 3rd party

Software, etc. provided by the selected Contractor will be initially used on the

Interim Server.

4. It is anticipated that the Server(s) will be required for a period of approximately six to

nine months from the date of supply of Server Hardware, Operating System Software

and MRO / M&E Package Software.

5. Subsequent to PIA purchasing and installing the required Permanent Server Hardware

and Operating System software, the Contractor will be required to re-install all MRO /

Page 118 of 189


M&E, Add-on applications, DBMS, database administration tools, application

development tools, query / report generating tools, 3rd party software, etc. on the

Permanent Server(s).

6. The details of the proposed Interim Server(s) hardware Configuration and Operating

System software are to be provided by the Contractor in its proposal.

7. The configuration of these machines should be capable to support the number of users

as specified by the Contractor in its plan.

8. In its proposal, the Contractor will provide site specification requirements for the

installation and operation of the Interim Server(s). It will be the responsibility of PIA to

cater to the prescribed site specifications.

9. PIA - at the end of implementation and rollout - may at its discretion, decide to purchase

the interim servers provided by the Contractor. In this regard, the Contractor should, as

part of its Price Proposal, separately mention the cost at which it would offer these

machines for sale to PIA. However, this cost component should not be added to the

total bid price, nor should it be used to calculate the bid bond amount.

E5 3rd. Party Software

1. In order to effectively manage and run the complete solution some other 3rd party

software and application programming interfaces (APIs) may also be required to

integrate various applications and execute and monitor the complete solution.

2. Contractor will be responsible to ensure that all required 3rd party software, operating



interfaces, etc. are made available, documented, designed, implemented and

operational to meet PIAC’s requirements in the proposed MRO / M&E solution.

3. It is the responsibility of the Contractor to offer PIA a complete solution in all respects –

delays or costs arising out of any shortcoming will have to be borne by the Contractor.

Page 119 of 189


SECTION F

HARDWARE REQUIREMENTS

Page 120 of 189


F1 HARDWARE

The Contractor must evaluate and prepare an appropriate configuration to run the

proposed MRO / M&E solution. PIA is looking for a high-availability solution including

servers, clustering design, and disaster recovery recommendations besides maintenance /

repair options needed for the associated infrastructure.

1 Contractor should submit details of the proposed configuration, including layout

diagram detailing model designation(s), memory size, number of CPUs, type of drives

with capacity and counts.

2 The offered solution should comply with the Open Systems Architecture and latest

technology trends.

3 The solution should be scalable, both horizontally and vertically.

4 The hardware should be sized keeping in view the operational requirements of the

MRO / M&E and associated applications.

5 The hardware should be fully capable of hosting the MRO / M&E certified database.

6 The hardware must allow each partition of the MRO / M&E environment to be isolated

in such a way that a software fault in one partition will not have an impact on another

partition.

7 All software required for clustering of servers and implementation of DRP should be

included in the solution.

8 The solution should be fully supported by the Contractor for not less than ten years

from the date of supply. It should remain capable of being supported, upgraded and

extended by the Contractor during this period.

9 The solution provided should be accompanied with complete documentation, operating

manuals, system diagrams, startup and recovery procedures and all other information

required for proper and efficient operation.

10 Contractor should provide all technical material and verifiable benchmarks related to

the proposed solution. The hardware should be certified by the MRO / M&E principal

vendor for the operation of the MRO / M&E and be reasonably expected to be certified

for future versions of the MRO / M&E during the expected life of the hardware.

11 Contractor should provide information on warranties on the equipment and any options

regarding warranty extension. Principal’s assurance is required for parts availability

after expiry of warranty period.

12 The Contractor must provide a thorough and contemporary 3rd party testing software

for acceptance and load testing. The testing should be done according to system

equipment specifications as well as generally accepted practices.

Page 121 of 189


13 All test results should be completely documented by the Contractor. Complete test

documentation including results of the 3rd party load / stress testing software should be

provided to PIA.

14 Based on PIAC’s high availability requirements, failover design should be based on

protecting single point of failure.

15 For high availability on the application layer, the solution should implement log on load

balancing between the application servers. It should not need any form of reallocation

of resources between servers. The application environment should be sized and

designed such that upon failure of an application server (based on single point of

failure), minimum degradation of performance is experienced.

16 A Disaster Recovery (DR) design should be provided which provides a seamless, pragmatic DR process. It should integrate within the overall design of the MRO / M&E landscape.

17 The DR process should be simple to execute. A step-by-step process and procedure

is required to minimize the potential for human error in a time of crisis and disaster.

Additionally, the DR design must be easily tested with minimal impact on day-today

operations.

Page 122 of 189


SECTION G

BIDDER’S QUALIFICATION, EXPERIENCE

&

EVALUATION

Page 123 of 189


G1. Bidder’s Qualifications and Experience

Technical Proposals shall provide the following information (referencing the subsections in

sequence) to evidence the Bidder’s qualifications to deliver the services sought under this

RFP:

1 A brief, descriptive statement indicating the Bidder’s qualifications and solution to deliver

the supply and services sought under this RFP. This should cover at least the following

topics:

a) MRO / M&E solution providers should have verifiable Airline / Aviation references

for proposed solution of their MRO / M&E Package. Minimum two complete

verifiable MRO / M&E references are to be provided

b) Reference based on individual modules shall not be considered towards MRO /

M&E reference.

c) Experience with the relevant target platform(s) and architectural components.

2 A brief description of the Bidder’s background and organizational history including:

1.1. Years in business;

1.2. Location of offices and local Infrastructure;

1.3. Form of business (i.e., individual, sole proprietor, corporation, partnership, joint

venture, Limited Liability Company, etc.).

3 A personnel roster and resumes of key people who shall be assigned by the Bidder to

perform duties or services under the contract. The resumes shall detail each

individual’s title, education, current position with the Bidder, MRO / M&E Package

Certification and employment history. Bidders must include a brief commentary on

each individual’s experience and suitability related to the services to be performed. The

lead consultants must have sufficient airline experience and completed at least one

MRO / M&E implementation cycles. The top consultant/ project manager must have

sufficient airline experience and completed at least two implementation cycles. Top and

lead consultant to be assigned for the complete project duration and must be full time

onside at the project location in Karachi. Also, the other team members must have

sufficient airline background and functional knowledge accepted by PIAC.

4 Where applicable, a letter from its Principal or Supplier, as the case may be, that it is

authorized to represent, acts as agent, and/or provide the products or services required

under this RFP.

5 A statement as to whether there is any pending litigation against the Bidder; and if such

litigation exists, attach an opinion of counsel as to whether the pending litigation will

impair the Bidder’s performance in a contract under this RFP.

6 Documentation of financial responsibility, financial stability, and sufficient financial

resources to provide the scope of services (and any related equipment) to PIAC in the

volume projected and within the time frames required; said documentation shall

include:

Page 124 of 189


• A description of the Bidder organization’s size, longevity, client base;

• A statement as to whether, in the last ten (10) years, the Bidder has filed (or had

filed against it) any bankruptcy or insolvency proceeding, whether voluntary or

involuntary, or undergone the appointment of a receiver, trustee, or assignee for

the benefit of creditors; and if so, an explanation providing relevant details; and

• Other pertinent financial information by which PIAC may reasonably formulate an

opinion about the relative stability and financial strength of the Bidder. This

information must include the most recent audited financial statement.

• Last 5 years’ earnings in IT Projects.

7 The Proposal should provide the following details of each MRO / M&E client in tabular

form.

• Client Name and Address

• Nature of Assignment

• MRO / M&E Package and list of modules implemented

• Date of Assignment Completion

• Nature of Client’s Business

• Type of Service provided

• Contact Person’s Name and Contact details.

Page 125 of 189


G2 Evaluation

1.0 Evaluation of Bidders

Evaluation process of the bidders involve Technical Evaluation as well as Financial

evaluation. The evaluation is based on data submitted by the bidder and which should

be substantiated with verifiable evidence. PIA may ask the vendors to demonstrate its

functional capability through presentation, with real-time functionality scenario, use case

or scripted simulation.

2.0 Criteria for Technical and Commercial Evaluation of M&E Solution & Contractor

Mandatory Requirements

Sr. No

Attributes Requirements

01 Off-the shelf solution of International Repute Literature/ brochure / catalogue of Product, user manual and technical documents

02 Details of litigation/sub-judice cases (if any) Certificate/ Letter

03 Income tax (NTN), Sales Tax Registration Certificate Provide certificates

04 Web enabled application Compulsory

05 Provision of on line bugs tracking / reporting system Compulsory

06 Search record Functionality Provide efficient Search functionality in all modules

07 Reports Capability to generate multiple reports as per requirement of different modules

08 Upgrades Provide software enhancements, updates & patches in the package. (with no hidden charges)

09 Audited Financial Statements for preceding 3 years Audited financial statements

10 Undertaking of no outstanding claims against PIA Appropriate undertaking

11 Integration with Oracle ERP, and interfacing with Sabre applications, AIMS (Section A5-1).

Compulsory

3.0 Weightage of Technical & Commercial Evaluation

Technical Bid: 70% Commercial Bid: 30%

Technical bids with scores of 70 points and above will be considered responsive and will be

considered for further commercial evaluation.

1- Technical Bid Score: Marks obtained by Firm / 100 * 70 = _______________

2- Commercial Bid Score: M/B * W = _______________

M → Minimum Bid B → The bid W → Weight (30)

Total Score = Technical Bid Score + Commercial Bid Score

_______________________________________________________________________

Note: PIA reserve the right to reject the proposal if any of the above mentioned requirements are not fulfilled.

Page 126 of 189


4.0 Technical Evaluation Performa

A – Business Profile

Sr. No.

Attributes Max

Score

Score Distrib-ution

Requirements

1 Authorized Product dealer/ Partner

4

4 Principal MRO / M&E IT vendor directly participating

3 OEM / Principal provide confirmation about the successful implementation of proposed solution in writing.

1 Authorized dealer/ partner participating

2 Financial Strength 4

4 More than or equal to USD 1 million turnover with MRO / M&E IT services revenue being 80%

3 USD 0.75 to 0.99 million turnover with MRO / M&E IT services revenue being 80% or more

2 USD 0.50 to 0.74 million turnover with MRO / M&E IT services revenue being at least 80% or more

3 Company established (No. of years) as of 30-June-2017.

4

4 15 or more years

3 10 years or more

2 05 years or more

4 Country Presence 3

3 Principal MRO / M&E IT vendor has office in Pakistan

2 Principal MRO / M&E IT vendor has authorized dealer/partner in Pakistan

1 Presence in Region

Total 15

Sections Max Score

Score Obtained

A. Business Profile 15

B. Experience 15

C. Product details 40

D. Composition of team assigned

16

E. Training 04

F. Compliance 10

Total 100

Page 127 of 189


B – Experience

Sr. No.

Attributes Max

Score

Score Distrib-ution

Requirements

5

Successful Full-scale implementations of MRO / M&E IT solution in last 5 years in airlines of PIA size - 30 aircraft.

10

10 More than 5such Implementations



6

Number of reference able Full-scale Implementations of MRO / M&E IT solution In last 5 years

5

5 10 or more Implementations

3 5-9 Implementations

2-4 Implementations

Total 15

C – Product details

Sr. No.

Attributes Max

Score

Score Distrib-ution

Requirements

7 Compliance of Product with Functional Requirements of RFP

30

30 90%-100% compliance (all modules)



5 70-79 % flexibility.

8 Warranty with Free Maintenance & Operational Support after complete implementation.

10

10 Free for more 3 years or more

5 Free for up to 2 years

3 Free for up to 1 year

Total 40

Page 128 of 189


D – Composition of Team Assigned to Implement MRO / M&E Solution

Sr. No.

Attributes Max

Score

Score Distrib-ution

Requirements

9 Project Manager (PM) experience of MRO / M&E implementation (in airlines of PIA size - 34 aircraft)

4

4 3 or more such MRO / M&E implementations as Project Manager and PMP Certification



10 Project Functional Lead (at least 2 resources)

4

4 10 or more years of Solution Delivery Experience



11 Project Size Team 4




12 Experience Level and Relevance of Proposed Team

4

4 High (each resource has at least 5 years of experience) and combined team experience is more than 200 person-years)

3 Moderate (each resource has at least 3 years of experience) and combined team experience is more than 150 person years)



Total 16

Page 129 of 189


E – Training

Sr. No.

Attributes Max

Score

Score Distrib-ution

Requirements

13 Contractor Training Team size made available for training

4 5 Class Room Based Training

1 Online Training

Total 4

F – Compliance

Sr. No.

Attributes Max

Score

Score Distrib-ution

Requirements

14 Extent of Compliance with PIA‘s Suggested Timelines and Payment Terms

10

10 Fully Compliant (both timelines and payment terms)

5 Significantly Compliant (payment terms only)

3 Partially Compliant (timelines only)

Total 10

Page 130 of 189


SECTION H

REQUIREMENTS COMPLIANCE MATRIX

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

31

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H1

G

LO

BA

L R

EQ

UIR

EM

EN

TS

– G

EN

ER

AL

Deta

iled b

elo

w a

re th

e g

lob

al re

quire

ments

applic

ab

le fo

r the e

ntire

solu

tion. C

ontra

cto

rs m

ust p

rovid

e th

eir re

spon

ses in

the “

Resp

on

se” c

olu

mn a

nd p

rovid

e a

dd

itiona

l info

rmatio

n / c

larific

atio

n in

the “

Rem

ark

s” c

olu

mn.

Vendor re

spo

nse m

ust b

e re

stric

ted to

:

Sr. N

o.

Resp

on

se

Rem

ark

s

1.

S

= S

tandard

featu

re a

vaila

ble

M

odule

/ sta

ndard

featu

re o

f the p

roposed s

olu

tion

2.

E

= E

nhancem

ent th

rough A

dd

-on / 3

rd party

utility

D

escrip

tion o

f Add

-on / U

tility a

nd th

e tim

e re

quire

d to

config

ure

/ develo

p / im

ple

ment it.

In s

uch c

ases C

ontra

cto

r has to

ensure

that a

ppro

pria

te c

osts

have b

een in

corp

ora

ted in

th

e C

om

merc

ial P

roposal

3.

N

= N

o / C

annot b

e p

rovid

ed

Nil

In c

ase th

e C

ontra

cto

r does n

ot p

rovid

e a

resp

onse, it w

ill be c

onsid

ere

d a

s “

N”.

The C

ontra

cto

r should

pro

vid

e th

e re

spo

nse b

y fillin

g u

p th

e c

olu

mns "

Resp

on

se" a

nd "

Rem

ark

s" o

nly

. Any c

ha

nges,

such a

s a

dditio

n, d

ele

tion, o

r modific

atio

n o

f row

conte

nts

in th

e R

FP

docum

ent, w

ill be c

onsid

ere

d a

s a

n in

va

lid re

sponse

to th

e R

FP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

32

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - G

EN

ER

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

1

Co

mm

on

Ch

ara

cte

ristic

s

1.1

Com

mon c

hara

cte

ristic

s a

re s

hare

d b

y a

ll are

as o

f the M

RO

/ M&

E S

olu

tion

2

In

teg

ratio

n

2.1

Softw

are

supports

m

odern

“b

est

busin

ess pra

ctic

es”,

with

data

lo

cate

d in

one

in

tegra

ted s

yste

m s

hare

d a

cro

ss a

ll org

aniz

atio

nal u

nits

. Inte

gra

tion w

ith O

racle

E

RP

&

in

terfa

cin

g w

ith S

abre

applic

atio

ns,

& A

IMS

is

pro

vid

ed as part

of

the

offe

red s

olu

tion.

2.2

It w

ill als

o

be

inte

gra

ted

with

fu

ture

m

odule

s

usin

g

the

sam

e

develo

pm

ent

language / p

latfo

rm

3

C

on

figu

ratio

n

3.1

Softw

are

w

ill re

quire

m

inim

um

softw

are

m

odific

atio

n

to

meet

its

busin

ess

require

ments

. It

will

allo

w fo

r easy config

ura

tion to

m

eet

those re

quire

ments

w

ithout c

hangin

g s

oftw

are

code o

r requirin

g A

dd

-ons

4

T

ech

no

log

y In

terfa

ces

4.1

The B

idder s

hould

pro

vid

e s

tandard

applic

atio

n p

rogra

mm

ing in

terfa

ces, to

ols

and

meth

odolo

gie

s

that

allo

w

futu

re

rele

ases

to

accom

modate

in

terfa

ces

with

out

repro

gra

mm

ing.

4.2

A

sta

ndard

appro

ach

to

inte

rfaces

is

availa

ble

to

avoid

m

ultip

le,

uniq

ue

appro

aches fo

r diffe

rent s

yste

ms

4.3

The B

idder w

ill have to

ensure

, at its

ow

n c

ost, a

vaila

bility

of A

PIs

for b

oth

its

pro

posed syste

m as w

ell

as syste

m ru

nnin

g in

P

IAC

. T

he softw

are

should

be

capable

to

in

tegra

te

with

applic

atio

ns

alre

ady

runnin

g

in

PIA

C

thro

ugh

Web

-serv

ices, A

pplic

atio

n P

rogra

mm

ing (A

PIs

), or th

rough d

ata

exports

in a

secure

and

effic

ient m

anner.

4.4

B

idder m

ust e

nsure

to p

rovid

e X

ML

-based A

PIs

where

ver th

ese a

re re

quire

d.

5

U

ser In

terfa

ce

5.1

The s

yste

m w

ill have a

com

mon lo

ok a

nd fe

el a

cro

ss a

ll applic

atio

ns

5.2

Scre

en la

belin

g w

ill be a

vaila

ble

in E

nglis

h

5.3

Onlin

e h

elp

will b

e a

vaila

ble

for a

ll applic

atio

ns a

nd w

ill allo

w fo

r custo

miz

atio

n

5.4

The s

yste

m w

ill be a

ccessib

le u

sin

g s

tandard

pers

onal c

om

pute

r thro

ugh b

row

ser

5.5

Syste

m w

ill allo

w o

penin

g m

ultip

le s

essio

ns

5.6

Syste

m w

ill allo

w fo

r sw

itchin

g b

etw

een d

iffere

nt p

rogra

ms w

ithout firs

t havin

g to

exit fro

m th

e s

yste

m.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

33

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - G

EN

ER

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

5.7

Syste

m w

ill allo

w d

efin

ing n

avig

atio

nal m

enus th

at c

an b

e c

reate

d b

y e

nd

-users

accord

ing to

their jo

b re

quire

ments

5.8

Busin

ess ru

les w

ill be in

corp

ora

ted in

to th

e s

yste

m s

uch th

at th

e ru

les a

re a

pplie

d

at th

e tim

e in

form

atio

n is

ente

red in

to th

e s

yste

m

5.9

The

syste

m

will

have

valid

atio

n

routin

es

/ para

mete

rs

to

identify

erro

rs,

inconsis

tencie

s o

r additio

nal re

quire

ments

at th

e tim

e d

ata

is e

nte

red

6

S

ecu

rity &

Au

tho

rizatio

n

6.1

The syste

m supports

m

ultip

le le

vels

of

security

w

hile

pro

vid

ing

sin

gle

sig

n-o

n

facility

to th

e u

sers

6.2

Indiv

idual fie

lds w

ill be p

rote

cte

d fro

m u

nauth

oriz

ed a

ccess

6.3

Access to

certa

in fu

nctio

ns a

nd d

ata

will b

e p

rote

cte

d u

ntil th

ey a

re a

ppro

ved b

y

PIA

C’s

concern

ed p

olic

y m

akers

6.4

Applic

atio

n s

ecurity

will b

e in

tegra

ted w

ith d

ata

base s

ecurity

. Data

files / ta

ble

s

will o

nly

be a

ccessed th

rough th

e M

RO

/ M&

E; d

irect a

ccess th

rough d

iffere

nt

query

languages w

ill not b

e p

ossib

le

6.5

Tem

pla

tes o

r gro

up fu

nctio

ns w

ill be p

rovid

ed to

facilita

te m

ain

tenance

6.6

Changes

in

assig

nm

ent

(em

plo

yee

transfe

rs)

or

term

inatio

n

/ re

tirem

ent

will

auto

matic

ally

trigger a

revie

w o

f the e

mplo

yee’s

security

priv

ileges

6.7

Com

pre

hensiv

e lo

gs o

f transactio

ns a

nd s

ecurity

incid

ents

will b

e m

ain

tain

ed fo

r auditin

g p

urp

oses. S

yste

m w

ill be c

apable

to m

ain

tain

audit tra

ils a

nd lo

gs

6.8

Syste

m

will

pro

vid

e

auth

oriz

atio

n,

auth

entic

atio

n,

inte

grity

and

non

-repudia

tion

fa

cilitie

s fo

r critic

al tra

nsactio

ns

6.9

Passw

ord

length

and a

ccepta

ble

chara

cte

r com

bin

atio

n a

s p

er in

dustry

sta

ndard

s

are

supporte

d

6.1

0

S

yste

m w

ill allo

w settin

g up of

passw

ord

change fre

quency and th

e num

ber

of

pre

vio

us p

assw

ord

s th

at c

ould

not b

e re

peate

d

6.1

1

S

yste

m w

ill forc

e u

sers

to c

hange th

eir p

assw

ord

s a

fter p

re-d

efin

ed in

terv

als

6.1

2

S

yste

m w

ill allo

w s

ecure

rem

ote

login

and w

ill support d

igita

l sig

natu

re a

nd tim

e

sta

mp, e

tc.

7

R

ep

ortin

g / In

qu

iry

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

34

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - G

EN

ER

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

7.1

The s

yste

m w

ill inclu

de c

om

pre

hensiv

e in

quiry

/ reportin

g to

ols

that a

llow

for e

asy

access to

auth

oriz

ed d

ata

7.2

“Drill d

ow

n” c

apability

to e

xam

ine d

eta

ils w

ill be a

vaila

ble

7.3

It will a

lso b

e p

ossib

le to

cre

ate

reports

that re

flect s

tatu

s a

s o

f a s

pecifie

d p

oin

t in

time

7.4

Sta

ndard

reports

will b

e in

clu

ded to

serv

e a

s m

odels

for c

usto

miz

ed re

portin

g a

nd

to p

rovid

e fo

r basic

functio

nal re

ports

7.5

Report w

izard

s o

r sim

ilar te

chniq

ues w

ill be a

vaila

ble

to g

uid

e u

sers

thro

ugh re

port

cre

atio

n

7.6

The

syste

m

will

be

such

that

reportin

g

activ

ities

do

not

com

pro

mis

e

responsiv

eness o

f the in

tera

ctiv

e s

yste

m

7.7

Reports

w

ill be

form

atte

d

to

prin

t on

local

PC

and

LA

N

atta

ched

prin

ters

, centra

lized h

igh-s

peed p

rinte

rs a

s w

ell a

s o

ver in

tern

et a

nd in

tranet

7.8

It will b

e p

ossib

le to

deliv

er fix

ed re

ports

to u

sers

on a

pre

-dete

rmin

ed s

chedule

to

be re

vie

we

d o

nlin

e, to

be re

tain

ed o

nlin

e o

r to b

e p

rinte

d a

t the u

ser’s

dis

cre

tion

7.9

Syste

m w

ill be able

to

deliv

er

the re

ports

usin

g its

ow

n m

essagin

g /

work

flow

engin

e a

s w

ell a

s P

IAC

’s e

mail s

yste

m, L

otu

s N

ote

s

7.1

0

T

he s

yste

m w

ill be a

ble

to d

em

onstra

te u

sefu

l dem

ogra

phic

and fo

recastin

g

capabilitie

s

7.1

1

T

he s

yste

m w

ill support te

xt-b

ased, p

ara

mete

rized a

nd w

ild-c

ard

searc

hes

7.1

2

S

yste

m w

ill pro

vid

e u

sers

the a

bility

to d

evelo

p a

d h

oc re

ports

at th

eir d

iscre

tion

7.1

3

T

he s

yste

m w

ill inclu

de a

data

dic

tionary

or s

imila

r pro

vis

ion to

allo

w n

on

-technic

al

users

to id

entify

the a

ppro

pria

te d

ata

ele

ments

for in

clu

sio

n in

their re

ports

8

D

ata

An

aly

tic T

oo

ls

8.1

PIA

desire

s d

ecis

ion s

upport to

ols

and in

form

atio

n b

ases th

at a

re fu

lly in

tegra

ted

with

the s

yste

m to

facilita

te s

trate

gic

pla

nnin

g, ta

ctic

al o

pera

tions a

nd o

rganiz

atio

n

wid

e a

naly

sis

– th

ese w

ill be a

vaila

ble

8.2

The s

yste

m w

ill support th

e e

asy m

ovem

ent o

f data

to c

om

mon p

ackaged P

C-

based a

pplic

atio

ns s

uch a

s M

icro

soft O

ffice

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

35

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - G

EN

ER

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

8.3

The s

yste

m w

ill be c

apable

of p

roducin

g “

wh

at if”

scenario

s to

support d

ecis

ion-

makin

g

9

C

om

mu

nic

atio

n

9.1

The s

yste

m w

ill foste

r info

rmatio

n s

harin

g a

t all le

vels

of th

e o

rganiz

atio

n. F

or

exam

ple

, polic

y d

irectiv

es a

nd g

oals

will b

e in

corp

ora

ted in

to th

e b

udget p

lannin

g

pro

cess;

departm

ents

w

ill be

able

to

share

purc

hasin

g

inte

ntio

ns

and

specific

atio

ns

and “b

est b

usin

ess p

ractic

es” w

ill be re

adily

availa

ble

for c

onsulta

tion

9.2

The s

yste

m w

ill pro

vid

e a

sin

gle

pla

ce fo

r users

to q

uic

kly

access in

form

atio

n a

nd

update

s o

n o

rganiz

atio

nal n

ew

s a

nd p

olic

ies

10

F

lexib

ility

10.1

The

syste

m

will

be

easily

re

config

ure

d

to

respond

to

changes

in

busin

ess

pra

ctic

es, p

olic

y d

irectiv

es, o

rganiz

atio

n s

tructu

re, s

tatu

tes a

nd re

gula

tions

10.2

Fle

xib

ility w

ill exte

nd b

oth

to e

nte

rpris

e-w

ide a

s w

ell a

s in

dustry

specific

pra

ctic

es

11

S

yste

m A

vaila

bility

11.1

Overa

ll it will b

e a

hig

hly

availa

ble

solu

tion

11.2

The s

yste

m w

ill be a

vaila

ble

for a

ccess b

y a

uth

oriz

ed p

ers

onnel fro

m a

nyw

here

at

any tim

e o

f the d

ay o

r nig

ht (2

4 x

7 a

vaila

bility

)

11.3

The s

yste

m w

ill be e

qually

usable

from

rem

ote

locatio

ns a

s fro

m th

e H

ead O

ffice

11.4

Web-b

ased a

ccess w

ill be s

upporte

d

12

T

ran

sactio

n T

imin

g

12.1

The s

yste

m w

ill support re

al tim

e o

pera

tions. C

hanges to

data

or th

e s

tatu

s o

f pro

cesses w

ill be im

media

tely

availa

ble

in th

e s

yste

m

12.2

Syste

m opera

tions w

ill not

constra

in th

e busin

ess pro

cesses supporte

d by th

e

syste

m

12.3

The s

yste

m w

ill support e

ffectiv

e d

atin

g fo

r transactio

ns, in

clu

din

g b

oth

futu

re a

nd

retro

activ

e c

hanges. T

he a

uth

ority

for s

uch tra

nsactio

ns w

ill be in

clu

ded in

the

security

capabilitie

s o

f the s

yste

m

12.4

The a

ssig

nm

ent o

f a re

troactiv

e d

ate

will g

enera

te th

e c

hanges re

quire

d to

brin

g

the s

yste

m u

p to

the c

urre

nt d

ate

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

36

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

G

LO

BA

L R

EQ

UIR

EM

EN

TS

- GE

NE

RA

L

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

13

O

nlin

e D

ocu

men

tatio

n a

nd

Tra

inin

g

13.1

The s

yste

m w

ill inclu

de c

usto

miz

able

onlin

e d

ocum

enta

tion a

nd tra

inin

g m

ate

rials

such a

s c

onte

xt-s

pecific

help

, searc

h c

apability

, busin

ess p

rocess d

ocum

enta

tion

and p

rocess m

aps

13.2

Conte

xt s

ensitiv

e h

elp

will in

clu

de:

13.2

.1

M

enu o

ptio

ns

13.2

.2

T

abs

13.2

.3

D

ata

entry

field

s

13.2

.4

B

utto

ns

13.2

.5

Ic

ons

14

S

tora

ge / R

eco

rd R

etrie

val

14.1

Record

colle

ctio

n and re

tentio

n is

an im

porta

nt

org

aniz

atio

nal

require

ment.

The

ability

to e

asily

arc

hiv

e, re

tain

and a

ccess re

cord

s is

require

d

14.2

Record

s re

tentio

n p

rocedure

s w

ill allo

w in

form

atio

n to

be s

tore

d in

a w

ay th

at c

an

be a

ccessib

le in

defin

itely

15

S

yste

m S

ecu

rity

15.1

Syste

m p

rovid

ed is

secure

and m

eets

all s

tandard

security

require

ments

i.e.

Identific

atio

n, A

uth

entic

atio

n, A

uth

oriz

atio

n a

nd In

tegrity

15.2

Syste

m a

llow

s im

ple

menta

tion o

f industry

sta

ndard

security

polic

ies a

nd is

capable

to

evolv

e to

meet s

ecurity

challe

nges

15.3

Deta

ils o

f the p

roposed s

ecurity

tools

is p

rovid

ed

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

37

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H2

G

LO

BA

L R

EQ

UIR

EM

EN

TS

– T

EC

HN

ICA

L

Deta

iled b

elo

w a

re th

e te

chnic

al re

quire

ments

applic

able

for th

e e

ntire

solu

tion. C

ontra

cto

rs m

ust p

rovid

e th

eir re

sponses

in th

e “

Resp

on

se” c

olu

mn a

nd p

rovid

e a

dditio

nal in

form

atio

n / c

larific

atio

n in

the “

Rem

ark

s” c

olu

mn.

Vendor re

spo

nse m

ust b

e re

stric

ted to

:

Sr. N

o.

Resp

on

se

Rem

ark

s

1.

S

= S

tandard

featu

re a

vaila

ble

M

odule

/ sta

ndard

featu

re o

f the p

roposed s

olu

tion

2.

E

= E

nhancem

ent th

rough A

dd

-on / 3

rd party

utility

D

escrip

tion o

f Add

-on / U

tility a

nd th

e tim

e re

quire

d to

config

ure

/ develo

p / im

ple

ment it.

In s

uch c

ases C

ontra

cto

r has to

ensure

that a

ppro

pria

te c

osts

have b

een in

corp

ora

ted in

th

e C

om

merc

ial P

roposal

3.

N

= N

o / C

annot b

e p

rovid

ed

Nil

In c

ase th

e C

ontra

cto

r does n

ot p

rovid

e a

resp

onse, it w

ill be c

onsid

ere

d a

s “

N”.

The C

ontra

cto

r should

pro

vid

e th

e re

spo

nse b

y fillin

g u

p th

e c

olu

mns "

Resp

on

se" a

nd "

Rem

ark

s" o

nly

. Any c

ha

nges,

such a

s a

dditio

n, d

ele

tion, o

r modific

atio

n o

f row

conte

nts

in th

e R

FP

docum

ent, w

ill be c

onsid

ere

d a

s a

n in

va

lid re

sponse

to th

e R

FP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

38

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

1

N

ew

Tech

no

log

y

1.1

The s

yste

m is

desig

ned in

such a

wa

y th

at it e

asily

allo

ws th

e in

corp

ora

tion o

f new

te

chnolo

gie

s, a

s th

ey b

ecom

e a

vaila

ble

2

M

ultip

le E

nviro

nm

en

ts

2.1

The s

yste

m s

upports

multip

le e

nviro

nm

ents

. These e

nviro

nm

ents

are

suffic

iently

is

ola

ted fro

m e

ach o

ther s

o th

at o

pera

tions in

one e

nviro

nm

ent

does n

ot a

ffect

those o

f anoth

er. T

he e

nviro

nm

ents

are

as fo

llow

s:

2.1

.1

P

roductio

n –

all p

roductio

n p

rocessin

g w

ill be p

erfo

rmed in

this

enviro

nm

ent

2.1

.2

D

evelo

pm

ent –

all d

evelo

pm

ent a

ctiv

ities in

clu

din

g u

nit a

nd s

yste

m te

stin

g w

ill be

conducte

d in

this

enviro

nm

ent

2.1

.3

Q

uality

Contro

l / Test –

afte

r all d

evelo

pm

ent, u

nit a

nd s

yste

m te

stin

g h

as b

een

com

ple

ted, th

is e

nviro

nm

ent w

ill be u

sed fo

r User A

ccepta

nce T

estin

g b

efo

re th

e

syste

m is

accepte

d in

to p

roductio

n

2.1

.4

T

rain

ing –

for a

ll in-h

ouse im

ple

menta

tion a

nd p

ost im

ple

menta

tion tra

inin

g

activ

ities

3

S

yste

m P

erfo

rman

ce

3.1

The s

yste

m is

responsiv

e a

nd a

vaila

ble

; it supports

rapid

fail-o

ver o

r redeplo

ym

ent

in th

e e

vent o

f pro

ble

ms o

r pla

nned m

ain

tenance. N

inety

-nin

e p

erc

ent o

f all fa

il-over e

vents

will ta

ke p

lace in

less th

an fiv

e m

inute

s

3.2

Any v

olu

me (b

atc

h) p

rocessin

g w

ill not in

terfe

re w

ith o

nlin

e re

sponsiv

eness o

r availa

bility

3.3

Syste

m a

vaila

bility

figure

s o

f the p

roposed s

olu

tion a

re p

rovid

ed. In

case v

ario

us

com

ponents

have d

iffere

nt v

alu

es, th

ese a

re s

pecific

ally

mentio

ned.

4

A

rch

ive a

nd

Pu

rge

4.1

The s

yste

m s

upports

perio

dic

arc

hiv

al a

nd p

urg

ing o

f unused o

r obsole

te

info

rmatio

n

4.2

Arc

hiv

ed in

form

atio

n is

availa

ble

fo

r his

toric

al

reportin

g in

such a m

anner

that

querie

s

can

be

perfo

rmed

on

arc

hiv

ed

data

usin

g

auto

mate

d

data

re

trieval

functio

ns

4.3

A c

om

ple

te d

ata

arc

hiv

al p

lan is

pro

vid

ed

5

R

eco

very

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

39

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

5.1

The syste

m auto

matic

ally

re

covers

to

th

e la

st

com

ple

te prio

r tra

nsactio

n in

th

e

event o

f a fa

ilure

5.2

The s

yste

m c

learly

indic

ate

s to

the u

ser th

at a

transactio

n fa

iled a

nd th

at it m

ust b

e

re-e

nte

red. R

ecovery

occurs

with

out o

pera

tor in

terv

entio

n

5.3

Contin

gency

and

backup

recovery

pro

cedure

s

with

guara

nte

ed

Serv

ice

Level

Agre

em

ents

(SLA

s) h

ave b

een p

rovid

ed

6

B

acku

p / R

eco

very

an

d R

eo

rgan

izatio

n

6.1

The s

yste

m p

rovid

es fo

r the u

natte

nded d

aily

backup o

f all in

form

atio

n a

nd d

ata

to

a m

edia

that c

an b

e s

tore

d o

ffsite

for d

isaste

r recovery

purp

oses

6.2

Syste

m s

upports

diffe

rent ty

pes o

f backups s

uch a

s:

6.2

.1

F

ull b

ackup

6.2

.2

In

cre

menta

l backup

6.2

.3

O

nlin

e b

ackup

6.2

.4

O

ffline b

ackup

6.3

Backups d

o n

ot p

revent th

e s

yste

m fro

m b

ein

g a

vaila

ble

at a

ll times a

nd d

o n

ot

dis

rupt s

yste

m o

pera

tions

6.4

There

is n

o p

erfo

rmance d

egra

datio

n d

urin

g d

ata

backup

6.5

Data

base re

org

aniz

atio

ns d

o n

ot s

ignific

antly

impair s

yste

m a

vaila

bility

6.6

The c

alc

ula

tion o

f time ta

ken to

backup d

ata

with

respect to

data

siz

e in

cre

ase h

as

been p

rovid

ed.

7

P

rint M

an

ag

em

en

t

7.1

The syste

m pro

vid

es a m

eth

od fo

r m

anagin

g th

e prin

t enviro

nm

ent

for

report

dis

tributio

n s

o th

at re

ports

are

dire

cte

d to

the a

ppro

pria

te p

rint fa

cility

. It cate

rs to

both

hig

h s

peed c

entra

lized p

rintin

g fa

cilitie

s a

s w

ell a

s lo

cal L

AN

-based p

rintin

g

facilitie

s th

at w

ill be e

mplo

yed in

additio

n to

prin

ting o

ver in

tern

et / in

tranet

8

F

allb

ack S

olu

tion

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

40

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

8.1

Syste

m

Should

support

functio

nality

, if

syste

m

or

parts

of

the

syste

m

is

not

opera

tive, a

manual o

r sem

i-manual fa

llback s

olu

tion to

be d

evelo

ped, to

contin

ue

the M

RO

/

M&

E opera

tion.

Afte

r re

sta

rt of

the syste

m.

It m

ust

be possib

le to

update

the s

yste

m a

ccord

ingly

.

9

A

bility

for s

yste

m a

nd

licen

se u

pd

ate

s

9.1

Pro

vid

ed M

RO

/ M&

E P

ackage’s

custo

miz

atio

n o

r modific

atio

n s

hall b

e re

ady fo

r any fu

ture

update

s. T

his

guara

nte

e s

hall a

lso b

e g

iven fo

r any u

nderly

ing s

oftw

are

such a

s D

BM

S, O

pera

ting S

yste

m, N

etw

ork

Managem

ent a

nd o

ther to

ols

.

10

T

ech

no

log

y A

rch

itectu

re

10.1

Recom

mendatio

ns o

f the te

chnolo

gy a

rchite

ctu

re u

nder w

hic

h th

e p

roposed M

RO

/ M

&E

Package w

ill opera

te a

re p

rovid

ed, w

ith th

e fo

llow

ing fe

atu

res p

refe

rence:

10.1

.1

N

-tiere

d

Clie

nt/S

erv

er

arc

hite

ctu

re

incorp

ora

ting

thin

pre

senta

tion

-logic

-clie

nt

com

munic

atin

g w

ith c

lient-n

eutra

l, serv

er-b

ased a

pplic

atio

ns, c

om

munic

atin

g w

ith

the d

ata

base

10.1

.2

T

hin

clie

nt, fo

r rem

ote

users

10.1

.3

A

pplic

atio

ns d

istrib

ute

d a

t serv

ers

locate

d a

t Head O

ffice

10.1

.4

C

entra

lized d

ata

base, lo

cate

d a

t Head O

ffice

10.2

Able

to s

upport d

iffere

nt n

etw

ork

based s

erv

ices / p

roto

cols

such a

s:

10.2

.1

T

CP

/IP

10.2

.2

D

HC

P

10.2

.3

W

INS

10.2

.4

D

NS

10.2

.5

N

etB

EU

I

10.2

.6

LD

AP

10.2

.7

F

TP

10.2

.8

D

LC

10.3

Syste

m is

able

to s

upport o

pen s

pecific

atio

ns fo

r AP

Is / m

iddle

ware

applic

atio

ns

such a

s:

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

41

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

10.3

.1

C

OM

/ DC

OM

10.3

.2

C

OR

BA

10.3

.3

R

MI

10.3

.4

A

LE

10.3

.5

M

Q S

erie

s L

ink

10.3

.6

O

LE

/ CO

M2

10.3

.7

O

DB

C

10.4

It is a

ble

to in

tegra

te w

ith In

tern

et te

chnolo

gie

s s

uch a

s:

10.4

.1

H

TT

P

10.4

.2

X

ML

10.5

Scala

ble

arc

hite

ctu

re is

supporte

d, s

uch a

s:

10.5

.1

S

MP

10.5

.2

M

PP

10.5

.3

C

luste

ring

10.6

While

desig

nin

g th

e te

chnolo

gy a

rchite

ctu

re, th

e fo

llow

ing a

re k

ept u

nder

consid

era

tion:

10.6

.1

S

olu

tion is

scala

ble

with

com

ple

te p

latfo

rm in

dependence w

ithout ty

ing d

ow

n P

IA

to a

sin

gle

pla

tform

10.6

.2

S

olu

tion is

effo

rtlessly

porta

ble

from

one s

yste

m to

anoth

er

10.6

.3

It

pro

vid

es

support

for

diffe

rent

flavors

of

UN

IX;

how

eve

r, it

is

a

tota

lly

inte

ropera

ble

solu

tion

10.6

.4

T

here

is o

pen s

ourc

e s

upport. In

this

conte

xt, th

e c

urre

nt s

cenario

vis

-à-v

is th

e

solu

tion o

ffere

d a

nd th

e fu

ture

roadm

ap a

re p

rovid

ed

10.6

.5

O

ptim

izatio

n o

f licensin

g c

osts

for th

e p

latfo

rm s

oftw

are

10.6

.6

P

IAC

’s exis

ting Local

and W

ide A

rea N

etw

ork

, and m

inim

izatio

n of

Wid

e A

rea

Netw

ork

band

wid

th re

quire

ments

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

42

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

10.6

.7

S

implic

ity o

f Syste

m A

dm

inis

tratio

n a

nd O

pera

tions

10.6

.8

E

ase o

f busin

ess c

ontin

uity

pla

nnin

g a

nd e

xecutio

n

11

S

erv

er H

ard

ware

11.1

The re

com

mended config

ura

tion cate

rs fo

r th

e exis

ting lo

ad as w

ell

as annual

volu

me g

row

th o

f 10

-15%

for th

e n

ext fiv

e y

ears

11.2

The config

ura

tion is

capable

of

reta

inin

g data

fo

r at

least

ele

ven years

(th

at

is,

curre

nt y

ear p

lus te

n y

ears

’ his

toric

al re

cord

)

11.3

The s

olu

tion is

redundant, re

liable

and c

onsis

tently

availa

ble

to a

llow

unin

terru

ptib

le

24x7 o

pera

tions

11.4

The p

roductio

n s

erv

er c

onfig

ura

tion in

clu

des re

dundant (R

AID

5) d

ata

sto

rage a

nd

multip

le p

rocessors

and c

ate

rs fo

r com

patib

ility w

ith P

IA’s

exis

ting L

AN

/ WA

N

enviro

nm

ent

11.5

The

are

as

of

perfo

rmance

and

scala

bility

, re

liability

and

fault

tole

rance

while

re

com

mendin

g S

erv

er c

onfig

ura

tions h

ave b

een ta

ken in

to c

onsid

era

tion

11.6

Perfo

rmance

guara

nte

es

of

the

solu

tion

under

diffe

rent

scenario

s

such

as

concurre

nt

users

durin

g norm

al

work

ing,

durin

g data

backup,

durin

g overlo

ad,

durin

g p

artia

l syste

m fa

ilure

, etc

. have b

een p

rovid

ed

12

S

yste

m a

nd

Netw

ork

Man

ag

em

en

t To

ols

12.1

Suita

ble

S

yste

ms and N

etw

ork

M

anagem

ent

Tools

have been re

com

mended.

These to

ols

will e

nsure

pro

per p

lannin

g, c

onfig

ura

tion, a

nd p

roble

m h

andlin

g o

f IT

resourc

es a

nd s

upport s

uch ta

sks a

s:

12.1

.1

defin

ing, re

solv

ing, a

nd m

anagin

g p

roble

ms

12.1

.2

opera

ting n

etw

ork

s a

nd m

ulti-v

endor s

yste

ms

12.1

.3

dis

tributin

g a

nd m

anagin

g s

oftw

are

and d

ata

12.1

.4

contro

lling o

pera

tions

12.1

.5

pla

nnin

g a

nd m

anagin

g p

erfo

rmance

12.1

.6

adm

inis

terin

g s

ecurity

12.1

.7

m

ain

tain

ing a

sset in

form

atio

n

12.1

.8

pla

nnin

g fo

r the fu

ture

capacity

of s

yste

ms

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

43

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

13

Data

Su

pp

ort

13.1

T

he s

olu

tion w

ill support m

ultip

le d

ata

types –

text, im

age, v

oic

e, e

tc.

13.2

T

he s

yste

m w

ill support d

ata

uplo

ad to

and d

ow

nlo

ad fro

m d

iffere

nt s

yste

ms in

m

ultip

le fo

rmats

13.3

B

esid

es s

imple

uplo

ad / d

ow

nlo

ad

facility

it will a

lso c

om

munic

ate

and s

upport d

ata

in

terc

hange w

ith m

obile

devic

es s

uch a

s:

13.3

.1

cellu

lar p

hones

13.3

.2

handheld

term

inals

13.3

.3

PD

As, e

tc.

13.4

S

yste

m w

ill support o

ther d

evic

es s

uch a

s:

13.4

.1

Scanners

13.4

.2

barc

ode re

aders

13.4

.3

bio

metric

devic

es

13.4

.4

card

readers

13.4

.5

RF

ID d

evic

es, e

tc.

13.5

S

upport fo

r importa

nt m

essagin

g / d

ata

form

ats

/ sta

ndard

s w

ill inclu

de, a

s a

m

inim

um

:

13.5

.1

Airc

raft C

om

munic

atio

n A

ddre

ssin

g a

nd R

eportin

g S

yste

m (A

CA

RS

)

13.5

.2

SIT

AT

EX

13.5

.3

AS

CII

13.5

.4 S

MS

13.5

.5 X

ML

13.5

.6 S

pec 2

010

13.5

.7 S

1000D

13.5

.8 M

S-O

ffice

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

44

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S –

TE

CH

NIC

AL

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

13.5

.9 Lotu

s N

ote

s, e

tc.

14

Syste

m S

ecu

rity

14.1

T

he s

yste

m s

upports

auth

entic

atio

n m

eth

ods th

at w

ill assure

that o

nly

auth

oriz

ed

users

are

able

to a

ccess p

rote

cte

d d

ata

and tra

nsactio

ns

14.2

T

hese in

clu

de s

upport fo

r:

14.2

.1

dig

ital s

ignatu

res

14.2

.2

PK

I infra

stru

ctu

re

15

Web

-en

ab

lem

en

t

15.1

T

he p

roposed s

yste

m is

Inte

rnet re

ady a

nd a

llow

s w

eb

-enable

d a

ccess to

users

fro

m a

nyw

here

acro

ss th

e w

orld

thro

ugh a

web p

orta

l

15.2

T

he s

yste

m is

com

plia

nt w

ith th

e S

erv

ice O

riente

d A

rchite

ctu

re (S

OA

)

16

W

ork

flow

16.1

The

pro

posed

syste

m

will

pro

vid

e

Work

flow

fu

nctio

nality

to

users

by

whic

h

info

rmatio

n a

nd re

quests

could

be a

uto

matic

ally

route

d to

the c

oncern

ed le

vels

for

appro

val

17

O

thers

17.1

Som

e o

ther re

quire

ments

inclu

de:

17.1

.1

S

upportin

g m

ulti-c

urre

ncy

17.1

.2

S

upportin

g u

ser d

efa

ults

17.1

.3

S

upportin

g u

ser d

efin

ed s

cre

ens

17.1

.4

S

upportin

g m

ultip

le d

ate

form

ats

17.1

.5

S

upportin

g u

ser d

efin

ed fie

lds

17.1

.6

S

chedulin

g o

f jobs fo

r unatte

nded o

pera

tions

17.1

.7

M

ain

tain

ing e

ffectiv

e d

ate

s o

f maste

r file d

ata

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

45

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H3

G

LO

BA

L R

EQ

UIR

EM

EN

TS

– O

TH

ER

S

Deta

iled b

elo

w a

re o

the

r glo

bal re

qu

irem

ents

applic

able

for th

e e

ntire

solu

tion. C

ontra

cto

rs m

ust p

rovid

e th

eir re

spo

nses in

the “

Resp

on

se” c

olu

mn a

nd p

rovid

e a

dd

itiona

l info

rmatio

n / c

larific

atio

n in

the “

Rem

ark

s” c

olu

mn.

Vendor re

spo

nse m

ust b

e re

stric

ted to

:

Sr. N

o.

Resp

on

se

Rem

ark

s

1.

S

= S

tandard

featu

re a

vaila

ble

M

odule

/ sta

ndard

featu

re o

f the p

roposed s

olu

tion

2.

E

= E

nhancem

ent th

rough A

dd

-on / 3

rd party

utility

D

escrip

tion o

f Add

-on / U

tility a

nd th

e tim

e re

quire

d to

config

ure

/ develo

p / im

ple

ment it.

In s

uch c

ases C

ontra

cto

r has to

ensure

that a

ppro

pria

te c

osts

have b

een in

corp

ora

ted in

th

e C

om

merc

ial P

roposal

3.

N

= N

o / C

annot b

e p

rovid

ed

Nil

In c

ase th

e C

ontra

cto

r does n

ot p

rovid

e a

resp

onse, it w

ill be c

onsid

ere

d a

s “

N”.

The C

ontra

cto

r should

pro

vid

e th

e re

spo

nse b

y fillin

g u

p th

e c

olu

mns "

Resp

on

se" a

nd "

Rem

ark

s" o

nly

. Any c

ha

nges,

such a

s a

dditio

n, d

ele

tion, o

r modific

atio

n o

f row

conte

nts

in th

e R

FP

docum

ent, w

ill be c

onsid

ere

d a

s a

n in

va

lid re

sponse

to th

e R

FP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

46

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - O

TH

ER

S

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

1

D

BM

S A

ND

DA

TA

BA

SE

AD

MIN

IST

AT

ION

TO

OL

S

1.1

Data

base s

chem

a d

efin

ition, m

anagem

ent, q

uery

and re

portin

g fa

cilitie

s p

rovid

ed

1.2

His

toric

al tra

nsactio

ns w

ill be m

ain

tain

ed b

y th

e D

BM

S. F

acilitie

s fo

r revie

win

g

transactio

ns,

multip

le

transactio

n

roll

back

and

transactio

n

log

reportin

g

are

availa

ble

1.3

Data

base u

pdate

facilitie

s in

clu

de fe

atu

res s

uch a

s th

e u

se o

f work

ing c

opie

s a

nd

sta

tus re

portin

g o

n q

uery

and u

pdate

opera

tions.

1.4

The s

yste

m p

rovid

es lo

ckin

g m

echanis

ms fo

r update

and d

ele

tes o

pera

tions.

1.5

The s

yste

m m

ain

tain

s c

oncurre

nt c

ontro

l mechanis

ms to

ensure

the c

orre

ctn

ess o

f tra

nsactio

ns a

nd to

dete

ct a

nd re

solv

e d

eadlo

cks o

n th

e n

etw

ork

.

1.6

The s

yste

m s

upports

auth

oriz

atio

n lis

ts a

nd g

roups fo

r cre

ate

, read, u

pdate

and

dele

te

1.7

There

is a

pro

vis

ion o

f on

-line fa

cilitie

s to

manage tra

nsactio

ns a

nd o

vera

ll on

-line

syste

m p

erfo

rmance.

1.8

The s

yste

m p

rovid

es u

sers

and a

pplic

atio

ns w

ith d

istrib

utio

n in

dependence. U

sers

do n

ot n

eed to

know

whe

re d

ata

base o

bje

cts

are

locate

d.

1.9

The syste

m opera

tes in

a dis

tribute

d enviro

nm

ent

where

diffe

rent

nodes of th

e

netw

ork

run a

t diffe

rent fu

nctio

nal le

vels

.

1.1

0

T

he s

yste

m h

as th

e a

bility

to a

uto

matic

ally

recover a

nd re

sto

re th

e d

ata

base fu

lly

to th

e la

st c

onsis

tent s

tate

afte

r a m

edia

failu

re.

1.1

1

T

he a

bility

to n

otify

users

as to

what tra

nsactio

ns w

ere

bein

g p

rocessed b

ut n

ot

writte

n to

the d

ata

base d

urin

g a

cra

sh is

availa

ble

.

1.1

2

T

he s

yste

m h

as c

heckpoin

t facilitie

s a

nd th

e c

apability

to ro

ll back / u

ndo to

any

one c

heckpoin

t.

1.1

3

T

he s

yste

m w

ill contin

ue to

be a

vaila

ble

to u

sers

durin

g a

ny b

ackup p

rocess o

r alte

ratio

n o

f the d

ata

base s

chem

a’s

and d

efin

itions.

1.1

4

T

he s

yste

m w

ill support o

ne

-to-o

ne, o

ne-to

-many a

nd m

any-to

-one re

latio

nship

s.

1.1

5

T

he s

yste

m is

capable

of w

ork

ing in

a m

ulti-tie

r enviro

nm

ent, a

nd p

rovid

es th

e

appro

pria

te to

ols

for p

artitio

nin

g th

e lo

catio

n o

f the p

rocessin

g. A

ll tunin

g w

ill be

independent to

the u

ser.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

47

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - O

TH

ER

S

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

1.1

6

A

ll info

rmatio

n in

the d

ata

base is

repre

sente

d a

s v

alu

es in

the ta

ble

.

1.1

7

N

ull

valu

e support

(as opposed to

em

pty

chara

cte

r strin

gs,

bla

nk chara

cte

rs or

zero

) is a

vaila

ble

for a

ll data

types.

1.1

8

D

ata

base re

covery

will b

e m

ade in

min

imum

accepta

ble

dow

ntim

e. A

ccepta

ble

dow

ntim

e w

ill be n

egotia

ted a

nd a

gre

ed u

pon

1.1

9

D

BM

S h

as a

support fo

r ELT

1.2

0

D

BM

S h

as s

upport fo

r SA

N s

tora

ge a

nd c

luste

r enviro

nm

ent

1.2

1

Load b

ala

ncin

g a

nd fa

ilover a

re s

upporte

d to

min

imiz

e d

ow

n tim

e

1.2

2

D

BM

S w

ill support

DR

site

s and auto

matic

sta

ndby config

ura

tions.

It

will

be

capable

of o

pera

ting in

the D

R e

nviro

nm

ent a

nd s

upport s

ynchro

nous a

s w

ell a

s

asynchro

nous d

ata

replic

atio

n a

t rem

ote

DR

site

1.2

3

D

BM

S w

ill support la

rge a

mounts

of d

ata

in te

rra b

yte

s

1.2

4

D

BM

S w

ill have s

upport fo

r transm

issio

n o

f data

from

oth

er n

ew

syste

ms a

s w

ell

as e

xitin

g le

gacy s

yste

ms

1.2

5

It w

ill support lib

rarie

s to

enable

backup o

n ta

pe a

nd d

isk d

rives

1.2

6

It h

as s

upport n

ew

firew

alls

and n

-tier n

etw

ork

arc

hite

ctu

re

1.2

7

It w

ill support O

LA

P, O

LT

P a

nd D

SS

syste

ms

2

A

PP

LIC

AT

ION

DE

VE

LO

PM

EN

T T

OO

LS

2.1

The p

roposed s

olu

tion h

as a

built-in

4G

L d

evelo

pm

ent e

nviro

nm

ent to

ol s

et

3

Q

UE

RY

AN

D R

EP

OR

T G

EN

ER

AT

OR

TO

OL

S

3.1

The re

port g

enera

tor fu

nctio

nality

inclu

des a

schedulin

g o

r pro

ductio

n p

rocess fo

r ro

utin

e re

portin

g

3.2

The re

port g

enera

tor fu

nctio

nality

supports

Stru

ctu

red Q

uery

Language (S

QL)

3.3

It als

o

supports

in

dustry

sta

ndard

re

port

genera

tors

such

as

Cry

sta

l R

eports

, B

usin

ess O

bje

cts

, etc

.

3.4

Report g

enera

tor h

as fo

rmattin

g a

nd s

tatis

tical c

apabilitie

s s

uch a

s:

3.4

.1

A

vera

gin

g

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

48

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

GL

OB

AL

RE

QU

IRE

ME

NT

S - O

TH

ER

S

Sr. N

o.

Req

uire

men

t R

esp

on

se

(S / E

/ N)

Rem

ark

s

3.4

.2

M

ulti-le

vel s

ub-to

talin

g

3.4

.3

P

erc

ent c

hange c

om

paris

ons

3.4

.4

S

tandard

math

em

atic

al o

pera

tions

3.4

.5

F

inancia

l calc

ula

tions

3.5

Genera

ted re

ports

are

able

to b

e s

aved in

severa

l outp

ut fo

rmats

, such a

s:

3.5

.1

M

S W

ord

3.5

.2

M

S E

xcel

3.5

.3

T

ext

3.5

.4

P

DF

3.5

.5

H

TM

L

3.5

.6

X

ML

4

IN

TE

RIM

SE

RV

ER

S

4.1

Specific

atio

ns a

re p

rovid

ed fo

r inte

rim s

erv

ers

that w

ill be u

sed fo

r MR

O / M

&E

config

ura

tion, a

dd

-on s

oftw

are

develo

pm

ent, u

ser tra

inin

g, e

tc.

4.2

All n

ecessary

hard

ware

com

ponents

are

als

o p

rovid

ed

4.3

The c

onfig

ura

tion o

f these m

achin

es w

ill support th

e n

um

ber o

f users

as s

pecifie

d

in th

e p

lan.

5

3

RD P

AR

TY

SO

FT

WA

RE

5.1

All

require

d

3rd

party

softw

are

, opera

ting

syste

ms,

syste

m

managem

ent

and

monito

ring to

ols

, backup and re

covery

softw

are

, data

base adm

inis

tratio

n to

ols

, dis

aste

r re

covery

and busin

ess contin

uity

to

ols

, A

PIs

/

inte

rfaces,

etc

. w

ill be

made availa

ble

, docum

ente

d,

desig

ned,

imple

mente

d and opera

tional

to m

eet

PIA

C’s

require

ments

in th

e p

roposed M

RO

/ M&

E s

olu

tion.

5.2

A com

ple

te solu

tion in

all

respects

has been offe

red to

P

IA – dela

ys or

costs

aris

ing o

ut o

f any s

hortc

om

ing w

ill be b

orn

e b

y th

e C

ontra

cto

r.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

49

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H4

FU

NC

TIO

NA

L R

EQ

UIR

EM

EN

TS

– M

RO

/ M&

E S

OL

UT

ION

Deta

iled b

elo

w a

re th

e te

chnic

al re

quire

ments

applic

able

for th

e e

ntire

solu

tion. C

ontra

cto

rs m

ust p

rovid

e th

eir re

sponses

in th

e “

Resp

on

se” c

olu

mn a

nd p

rovid

e a

dditio

nal in

form

atio

n / c

larific

atio

n in

the “

Rem

ark

s” c

olu

mn.

Vendor re

spo

nse m

ust b

e re

stric

ted to

:

Ve

nd

or

Sc

ore

. R

es

po

nse

R

em

ark

s

4

S =

Sta

nda

rd fe

atu

re a

va

ilable

M

od

ule

/ sta

nd

ard

featu

re o

f the

pro

po

sed

so

lutio

n

3

E =

En

han

cem

ent

Th

e re

qu

ired

fun

ctio

na

lity c

an

be

de

ve

lop

ed

by th

e b

uild

-in 4

GL

or th

e re

po

rt ge

ne

rato

r. Futu

re re

lea

se

s

of th

e p

rovid

ed

syste

m a

re n

ot a

ffecte

d.

2

A =

En

han

cem

ent th

rou

gh A

dd

-on

/ 3rd

pa

rty u

tility

De

scrip

tion

of A

dd

-on

/ Utility

an

d th

e tim

e re

quire

d to

co

nfig

ure

/ de

ve

lop

/ imp

lem

en

t it. In s

uch

ca

se

s

Co

ntra

cto

r ha

s to

ensu

re th

at a

pp

rop

riate

costs

ha

ve

be

en in

co

rpo

rate

d in

the C

om

me

rcia

l Pro

posa

l

0

N =

No

/ Ca

nn

ot b

e p

rovid

ed

N

il

In c

ase th

e C

ontra

cto

r does n

ot p

rovid

e a

resp

onse, it w

ill be c

onsid

ere

d a

s “

N”.

The C

ontra

cto

r should

pro

vid

e th

e re

spo

nse b

y fillin

g u

p th

e c

olu

mns "

Resp

on

se" a

nd "

Rem

ark

s" o

nly

. Any c

ha

nges,

such a

s a

dditio

n, d

ele

tion, o

r modific

atio

n o

f row

conte

nts

in th

e R

FP

docum

ent, w

ill be c

onsid

ere

d a

s a

n in

va

lid re

sponse

to th

e R

FP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

50

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

1.0

F

un

ctio

nal R

eq

uire

men

t co

ncern

ing

Airc

raft E

ng

ineerin

g

Resp

on

se

S/E

/A/N

Rem

ark

1.1

M

PD

Pro

ces

s

❖

Read n

ew

MP

D v

ers

ion

/ auto

mate

d u

plo

ad

❖

Custo

miz

atio

n F

ilter fo

r non-c

usto

miz

ed d

eliv

ery

of M

PD

❖

D

iffere

nce re

port fo

r pre

-& p

ot-re

vis

ion o

f MP

D

❖

MP

D c

usto

miz

atio

n to

genera

te M

ain

tenance P

rog

ram

for fle

et-

wis

e/ta

il num

ber-w

ise

.

❖

Rele

ase c

usto

miz

ed/re

vis

ed M

PD

(OM

P)

to s

erv

ice, a

nd n

otify

the k

ey u

sers

. ❖

D

efin

e M

EL.

1.2

R

elia

bility

Man

ag

em

en

t ❖

R

elia

bility

Re

port, A

/C, C

hapte

r, Engin

e,

Com

ponent

❖

Dis

patc

h R

elia

bility

❖

N

FF

Reports

❖

M

TB

UR

Repla

cem

ents

❖

E

ngin

e, A

PU

perfo

rmance

monito

ring

❖

Mon

itor C

ofM

, CofA

rene

wal &

reportin

g

❖

Mon

itor E

TO

PS

, RV

SM

com

plia

nce

❖

Flig

ht in

cid

ents

, Pilo

t Reports

❖

F

leet u

tilizatio

n re

ports

.

1.3

D

ocu

men

t Man

ag

em

en

t ❖

U

plo

ad O

EM

Ma

nuals

& e

nsure

contin

ue

d u

pdate

d re

vis

ion

sta

tus.

❖

Uplo

ad a

nd re

gis

ter S

B’s

, AD

’s

❖

Revis

e a

ircra

ft manuals

❖

T

echnic

al

Lib

rary

fu

nctio

ns

with

e

-dis

tributio

n

of

docum

ents

❖

M

ain

tain

PIA

Inte

rnal M

anua

ls

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

51

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

1.4

T

ask C

ard

Man

ag

em

en

t ❖

U

plo

ad O

EM

TC

❖

C

reate

/Update

/ modify

TC

❖

In

clu

sio

n / h

yperlin

kin

g o

f rele

vant m

ain

tenance

pro

cedure

/re

fere

nce fro

m A

MM

. ❖

R

ele

ase M

aste

r TC

for s

erv

ice

1.5

M

od

ificatio

n P

rocess

❖

Evalu

ate

& a

ppro

ve S

B, A

D

❖

Cre

ate

Engin

eerin

g O

rder

❖

Sta

tus F

leet M

odific

atio

n

❖

Sta

tus E

ngin

e/ C

om

ponent M

od

ificatio

n

❖

Pla

nnin

g &

sta

ggerin

g F

leet M

odific

atio

ns

❖

Lis

t of p

erfo

rmed S

B’s

❖

C

onfig

ura

tion c

ontro

l

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

52

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

2.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Airc

raft In

du

ctio

n a

nd

Ph

ase o

ut

R

esp

on

se

S/E

/A/N

Rem

ark

2.1

A

ircra

ft maste

r data

❖

C

reate

airc

raft/ e

ngin

e m

aste

r data

❖

C

reate

airc

raft/ e

ngin

e m

aste

r stru

ctu

re &

locatio

ns

2.2

In

itial d

ata

en

try

❖

Initia

l pro

vis

ionin

g, u

plo

ad R

SP

L

❖

Uplo

ad a

nd m

ain

tain

readin

ess lo

g

❖

Uplo

ad A

/C, e

ngin

e, c

om

ponent h

isto

ry

❖

Uplo

ad M

PD

, ME

L

❖

Uplo

ad T

ech-L

og, M

EL s

tatu

s, O

pen

defe

cts

❖

U

plo

ad m

odific

atio

n s

tatu

s

❖

Main

tain

sta

tus/ le

tter c

hecks p

erfo

rmed

❖

Ente

r flow

n flig

ht h

ours

, blo

ck h

ours

, landin

gs c

ycle

s, d

ays

2.3

A

ircra

ft ph

ase o

ut

❖

Cre

ate

Read

iness L

og

❖

Cre

ate

Mo

d S

tatu

s

❖

Cre

ate

Ma

inte

nance S

tatu

s

❖

Cre

ate

Tech-L

og, M

EL s

tatu

s, D

efe

rred D

efe

cts

2.4

E

ng

ine C

han

ge

❖

De-lin

k th

e d

ata

set o

f rem

oved E

ngin

e fro

m th

e a

ircra

ft curre

nt d

ata

and c

reate

report.

❖

Uplo

ad c

om

ple

te d

ata

set o

f the in

sta

lled E

ngin

e a

nd lin

k

it to th

e c

oncern

ed a

ircra

ft data

set.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

53

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

3.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Lin

e M

ain

ten

an

ce

R

esp

on

se

S/E

/A/N

Rem

ark

3.1

L

ine M

ain

ten

an

ce P

lan

nin

g

❖

Long/ m

ediu

m-te

rm p

lannin

g (s

um

mer/w

inte

r/hajj)

❖

Short-te

rm p

lannin

g

❖

Work

load/ c

apacity

pla

nnin

g

❖

Hangar/ A

/C v

isit p

lan

❖

Assig

n W

ork

Package to

Work

Cente

r/ Shift/ in

div

idu

al s

taff

❖

Dis

patc

h s

pare

s, to

ols

, docum

enta

tion to

line s

tatio

n

❖

Pro

vis

ion o

f line s

tatio

ns

❖

Pla

n fo

r Flig

ht C

overa

ge.

3.2

S

ch

ed

ule

d M

ain

ten

an

ce

❖

Bill o

f Work

(BO

W)

❖

Bill o

f Mate

rial (B

OM

)

❖

Neede

d T

ools

and E

qu

ipm

ent

❖

Execute

Work

Package a

nd T

ask C

ard

s

❖

Schedule

Majo

r com

ponent c

hang

e (M

IC)

❖

Rele

ase A

/C to

serv

ice

❖

Shift h

and o

ver

3.3

U

nsch

ed

ule

d M

ain

ten

an

ce

❖

Record

defe

cts

and c

orre

ctiv

e a

ctio

n

❖

Tra

ckin

g o

f defe

rred d

efe

cts

❖

Indic

ate

ME

L ite

ms

3.4

P

ost M

ain

ten

an

ce P

rocess

❖

Update

A/C

, com

ponent re

cord

s

❖

Report p

erfo

rmed ta

sks

❖

Arc

hiv

e T

ask c

ard

s

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

54

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

4.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Cab

in M

ain

ten

an

ce

R

esp

on

se S/E

/A/N

Rem

ark

4.1

M

ain

ten

an

ce P

lan

nin

g

❖

Defin

e/ u

pdate

a m

ain

tenance p

rogra

m fo

r CM

, but a

lso fo

r A/C

exte

rior c

lean

ing.

❖

Defin

e In

stru

ctio

n c

ard

s fo

r CM

❖

Pla

n C

M w

ork

accord

ing th

e m

ain

tenance p

rog

ram

❖

Pla

n c

apacity

accord

ing

to w

ork

load

/main

tenance s

chedule

4.2

C

usto

mer F

eed

back

❖

Inte

rface to

custo

mer c

om

pla

int s

yste

m

❖

Do c

orre

ctiv

e a

ctio

n

❖

Sta

tistic

s a

ccord

ing c

usto

mer fe

edback

4.3

U

nsch

ed

ule

d M

ain

ten

an

ce

❖

Record

defe

cts

from

CB

L o

r inspectio

n a

nd re

port

❖

Tra

ce d

efe

rred d

efe

cts

❖

Indic

ate

ME

L ite

ms

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

55

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

5.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Base M

ain

ten

an

ce

R

esp

on

se S

/E/A

/N

Rem

ark

5.1

B

ase M

ain

ten

an

ce P

lan

nin

g

❖

Long/ m

ediu

m-te

rm c

heck p

lannin

g B

ase M

ain

tenance E

ve

nts

❖

Work

Package M

an

age

ment

❖

Job C

ard

cre

atio

n/ u

pda

te/ re

vis

e

❖

Hangar/ A

/C v

isit p

lan

❖

Work

Load P

lannin

g

❖

Event p

roje

ct p

lann

ing w

ith flo

w c

harts

and m

ile s

tones

❖

Forw

ard

/ Backw

ard

eve

nt p

lannin

g (in

cl. G

antt-C

hart)

❖

Pro

gre

ss m

onito

ring, m

onito

r costs

thru

dashbo

ard

s

❖

Mon

itor c

onsum

ed M

h &

spare

s

5.2

B

ase M

ain

ten

an

ce O

pera

tion

❖

Inte

rface d

efe

rred d

efe

cts

from

LM

❖

Shop flo

or d

ata

colle

ctio

n

❖

Ente

ring s

nags, p

lannin

g re

ctific

atio

n

❖

Shift h

and o

ver

❖

Capacity

Pla

nnin

g

❖

Clo

se lo

op re

pair / v

isib

ility o

f fractio

nal w

ork

offlo

ade

d to

oth

er

shops.

5.3

P

ost M

ain

ten

an

ce P

rocess

❖

Tra

nsfe

r defe

ct to

LM

❖

Update

A/C

config

ura

tion &

counte

rs

❖

Arc

hiv

e d

ocum

ents

❖

Post-C

heck a

naly

sis

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

56

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

6.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Co

mp

on

en

t Overh

au

l

Resp

on

se

S/E

/A/N

Rem

ark

6.1

M

ain

ten

an

ce

Pla

nn

ing

❖

Med

ium

-term

capacity

pla

nnin

g/ S

hop v

isit fo

recast

❖

Main

tena

nce b

acklo

g, p

riority

managem

ent b

ased o

n

airc

raft d

em

and, m

anpow

er a

nd s

tock le

vel

❖

Capacity

/ work

loa

d p

lan

nin

g

❖

Mon

itor c

osts

, monito

r consum

ed M

h &

spare

s

❖

Pla

nnin

g fo

r consum

able

s

❖

LR

U S

tatu

s &

Locatio

n re

vie

w.

6.2

C

om

po

ne

nt M

ain

ten

an

ce

Wo

rk F

low

❖

Work

ord

er / S

hop

-In re

gis

tratio

n

❖

Wok p

ackage c

om

pila

tion

❖

Job Is

suance a

t pro

ductio

n flo

or. (c

lock-in

)

❖

Main

tena

nce E

xecutio

n / p

rogre

ssiv

e s

tatu

s

❖

Defe

ct n

otific

atio

n &

repair

pro

cedure

.

❖

Work

package e

ntry

into

syste

m

❖

Postin

g o

f Mate

rial c

onsum

ed to

work

ord

er

❖

Com

ponent re

lease ta

g

❖

Shop o

ut / c

losure

of w

ork

ord

er C

lock &

clo

ck-o

ut

6.3

S

ho

p S

up

po

rt Fu

nc

tion

s

❖

Pro

cess F

low

for C

ontra

cte

d M

ain

tena

nce.

❖

Com

ponent S

cra

p P

rocess

❖

Com

ponents

requirin

g C

onsum

able

s

❖

Third

-Party

custo

mer c

om

ponents

handlin

g

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

57

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

❖

Shop C

ap

ability

managem

ent &

contro

l

❖

Fra

ctio

nal W

ork

Ord

er p

rocess

❖

Tool S

tore

functio

ns

6.4

C

om

po

ne

nt E

ng

ine

erin

g

❖

Up-to

-date

com

ponent m

ain

tenance m

anuals

. ❖

S

Bs, A

Ds; C

om

ponent m

odific

atio

n p

rocess

❖

Arc

hiv

e te

chnic

al re

cord

s

❖

Defe

ct n

otific

atio

n

❖

Com

ponent re

liability

report

❖

Work

Instru

ctio

n C

ard

cre

atio

n/ u

pd

ate

/ revis

e.

❖

Alte

rnate

Tools

/Mate

rial a

ppro

val

6.5

W

ork

flow

for R

ep

air &

Mo

dific

atio

n s

ho

p

With

pro

gre

ssiv

e m

ove

me

nt o

f wo

rk p

iece

s to

are

as lik

e

Mach

inin

g/ g

rind

ing, W

eld

ing, b

razin

g, H

eat tre

atm

ent, P

recis

ion

measurin

g, M

eta

llogra

phic

inspectio

n / H

ard

ness te

stin

g, S

urfa

ce

treatm

ent, B

ench fittin

g, P

latin

g / p

lasm

a / p

ain

t. Etc

.

6.7

W

ork

sh

op

Eq

uip

me

nt M

ain

ten

an

ce

❖

F

ixe

d e

qu

ipm

ent M

ain

ten

an

ce

Sh

op

❖

T

oo

l / Te

st E

qu

ipm

ent L

oca

l Fab

rica

tion &

app

rova

ls.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

58

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

7.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Co

mp

on

en

t Overh

au

l

Resp

on

se

S/E

/A/N

Rem

ark

7.1

Q

ua

lity A

ss

ura

nc

e (A

ud

it)

❖

De

fine

Au

dit P

lan

/Pro

gra

m

❖

Pre

pa

ring C

he

cklis

t, Re

co

rdin

g a

nd

Fo

llow

up

of N

on

-

Co

mp

lian

ce

s

❖

Co

nd

uct a

nd

Fo

llow

Up

of L

ine S

tatio

n a

nd

Te

ch

nic

al H

an

dlin

g

Age

nts

Au

dit

❖

Un

sch

edu

led

Au

dits

❖

Au

dit R

ep

orts

❖

Eva

lua

tion

an

d R

eco

rd o

f Ap

pro

ve

d V

end

ors

❖

Asse

ssm

en

t of C

ase

s s

ub

mitte

d fo

r Com

pa

ny C

ap

ab

ility L

ist

Ad

ditio

n / E

nha

ncem

en

t

❖

Asse

ssm

en

t and

Re

cord

of C

om

pa

ny A

uth

oriz

atio

ns / L

imite

d

Au

tho

riza

tion

s

7.2

Q

ua

lity A

ss

ura

nc

e (M

ain

ten

an

ce

)

❖

Ra

mp

Inspe

ctio

n o

n flig

hts

rea

dy fo

r de

pa

rture

❖

Sp

ot C

he

cks o

f diffe

ren

t se

ctio

n o

f PIA

En

gin

ee

ring &

Ma

inte

na

nce

❖

Un

sch

edu

led

Ra

mp

Insp

ectio

ns / S

po

t Ch

ecks

7.3

H

um

an

Fa

cto

r / SM

S

❖

SM

S / H

um

an

Fa

cto

r / HS

E re

late

d re

po

rting, a

na

lysis

,

reco

mm

en

datio

ns a

nd im

ple

me

nta

tion

inclu

din

g a

na

lysis

of

Inte

rna

l Aud

it find

ings.

HS

E/S

MS

Ac

tivity

Ha

za

rd &

Ris

k M

an

ag

em

en

t

❖

Su

ppo

rt for H

SE

/SM

S H

aza

rd/R

isk a

ctiv

ity re

gis

tratio

n a

nd

mitig

atio

n c

on

trols

man

age

me

nt.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

59

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

7.4

E

xa

min

atio

n

❖

Scru

tiny o

f rece

ive

d A

pp

lica

tion

s a

nd

Re

co

rd o

f Qu

alific

atio

ns

(Lic

en

se

s a

nd C

om

pan

y A

pp

rova

ls)

❖

Co

nd

uctin

g c

om

pa

ny a

pp

rova

ls e

xa

ms e

xtra

ctin

g p

ap

ers

from

Qu

estio

n D

ata

Ba

nk (Q

DB

)

7.5

C

hie

f En

gin

ee

r Sec

reta

riat

❖

Issu

an

ce

of C

ertific

atio

n A

uth

oriz

atio

n / L

ist o

f Ce

rtifyin

g S

taff

❖

Ap

pro

va

l of v

en

do

rs, th

eir Q

ua

lity M

on

itorin

g a

nd a

ctio

ns a

s a

resu

lt of m

on

itorin

g

❖

Re

co

rd o

f Lim

ited

Au

tho

riza

tion

s is

su

ed

from

Re

gu

lato

ry

Au

tho

rity

❖

Incid

en

ts / D

ela

ys (R

ep

ortin

g to

PC

AA

, inve

stig

atio

ns)

❖

Re

co

rd o

f Lic

en

se

s (F

or S

cru

tiny a

nd R

ene

wa

l from

PC

AA

)

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

60

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

8.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Mate

rial M

an

ag

em

en

t

Resp

on

se

S/E

/A/N

Rem

ark

8.1

M

ate

rial P

lan

nin

g

❖

Uplo

ad re

adin

ess lo

g

❖

Uplo

ad a

nd m

ain

tain

initia

l pro

vis

ionin

g d

ata

❖

Main

tain

Airc

raft s

tructu

re/ lo

catio

n

❖

Main

tain

Mate

rial M

aste

r data

❖

Pla

n c

onsum

able

based

on p

lann

ing p

ara

mete

rs &

past

consum

ptio

n

❖

Mate

rial p

rovis

ion fo

r pla

nne

d m

ain

tenance

❖

Mon

itor c

onsum

ptio

n a

nd s

tock le

vel

❖

Mate

rial re

qu

est fu

nctio

ns

8.2

R

ota

ble

s C

on

trol (L

RU

)

❖

Pla

n L

RU

float

❖

Contro

l lifetim

e

❖

Com

ponent h

isto

ry

❖

Com

ponent tra

ckin

g

❖

Shelf life

/ Enviro

nm

enta

l Cond

itions d

ata

8.3

L

oan

/ Bo

rrow

ing

❖

Adm

inis

ter lo

an o

f parts

/ equip

ment / to

ols

❖

Adm

inis

ter b

orro

win

g o

f parts

/ equip

ment / to

ols

❖

Handle

parts

on e

xchan

ge b

asis

❖

Support c

om

ponent p

oo

ling c

oncept

8.4

C

om

po

ne

nt e

xc

ha

ng

e p

rog

ram

❖

Contra

cts

managem

ent fo

r CE

P/C

SP

.

❖

Work

flow

for e

ntire

CS

P lo

op, w

ith tra

ckin

g a

bility

.

❖

Com

ponent o

ut/in

his

tory

❖

NF

F T

rackin

g

❖

Reportin

g c

apab

ility fo

r com

ponents

in C

SP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

61

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

8.5

C

on

trac

ted

Ma

inte

nan

ce

/ Re

pa

ir Ab

roa

d

❖

The s

tatu

s o

f the c

om

ponent, &

expecte

d re

turn

time.

❖

Repair re

ports

inte

gra

tion to

the c

om

ponent h

isto

ry re

cord

❖

Syste

m update

fo

r scra

p at

repair

ag

ency site

or

repla

cem

ent

com

ponent o

ffer.

❖

Syste

m s

hall m

ain

tain

Perm

anent re

pair a

bro

ad lis

t (PR

A).

8.6

W

arra

nty

man

ag

em

en

t su

pp

ort

❖

Rep

air W

arra

nty

❖

Pu

rch

ase W

arra

nty

❖

Ind

uctio

n W

arra

nty

as p

art o

f airc

raft re

ad

iness lo

g.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

62

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

9.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Bu

sin

ess D

eve

lop

men

t

Resp

on

se

S/E

/A/N

Rem

ark

9.1

C

lien

t Co

ntra

ct

❖

Defin

e C

lient M

aste

r

Agre

em

ent

❖

Defin

e C

lient M

ain

ten

an

ce

Ord

er

❖

Clie

nt C

onta

ct D

eta

ils d

ata

base

9.2

O

rder M

an

ag

em

en

t

❖

Defin

e C

lient O

rder S

yste

m a

ccord

ing to

the c

ontra

ct te

rms

❖

Mon

itor c

lient O

rder P

rogre

ss

❖

Mon

itor M

h &

parts

costs

❖

Mon

itor R

epa

ir abro

ad c

osts

and p

rogre

ss

❖

Ord

er p

rogre

ss in

form

atio

n a

ccessib

le b

y th

e C

lient

9.3

P

rop

osal M

an

ag

em

en

t

❖

Defin

e m

aste

r pro

posal

❖

Sto

re c

usto

miz

ed p

ropo

sal

❖

Mon

itor p

roposal s

ucce

ss

rate

❖

Capab

ility lis

t

9.4

P

rofita

bility

An

aly

sis

(thru

ER

P In

terfa

ce

)

❖

Calc

ula

te c

lient o

rder p

rofita

bility

❖

Calc

ula

te c

om

ple

te c

lient p

rofita

bility

❖

pro

fitability

an

aly

sis

by re

gio

n &

pro

ducts

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

63

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

10.0

F

un

ctio

nal R

eq

uire

men

ts fo

r Po

wer P

lan

t Overh

au

l

Resp

on

se

S/E

/A/N

Rem

ark

10.1

P

rod

uctio

n P

lan

nin

g

❖

Long-te

rm p

lannin

g E

ng

ine/ A

PU

/ Com

ponent s

hop

vis

its

❖

Pro

ductio

n/ c

apacity

pla

nnin

g

❖

Forw

ard

/ Backw

ard

eve

nt p

lannin

g (in

cl. p

roje

ctio

n th

ru G

antt-

Chart)

❖

Cre

ate

/ update

BoW

& B

oM

❖

Engin

e/ m

odule

dis

asse

mble

managem

ent

❖

Engin

e/ m

odule

/ com

ponent b

uild

-up c

ontro

l

❖

Com

ponent S

cra

p p

rocess

❖

Fra

ctio

nal W

ork

(inte

r-shop) p

rocess

❖

Contra

cte

d m

ain

tenance / re

pair a

bro

ad w

ork

flow

❖

Ma

inta

inin

g L

LP

’s h

isto

ry

10.2

E

ng

ine E

ng

ineerin

g

❖

Mod

ificatio

n s

tatu

s d

ashboard

❖

Mod

ificatio

n m

anagem

ent

❖

Update

Engin

e/A

PU

/ LR

U c

ounte

rs &

sta

tus

❖

Update

Engin

e/ A

PU

/ LG

modific

atio

n s

tatu

s.

❖

Cre

ate

/ update

/ revis

e S

hop W

ork

Sheet

❖

Shop F

indin

g R

ep

orts

❖

Update

seria

lize

d c

om

ponents

❖

Arc

hiv

ing o

f technic

al re

cord

s.

❖

Update

/ revis

e O

EM

manuals

10.3

E

ng

ine H

ealth

Mo

nito

ring

❖

In

dig

en

ous s

upp

ort fo

r EH

M.

Or S

upport fo

r EH

M th

rough th

ird-p

arty

inte

rfaced a

pplic

atio

n.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

64

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

10.4

S

ho

p/ W

ork

Pla

ce C

on

trol

❖

Work

cente

r monito

ring

❖

Backlo

g p

riority

managem

ent a

t Work

Cente

r

❖

Mh a

nd M

achin

e h

our re

cord

ing

❖

Tra

ckin

g &

tracin

g p

arts

in th

e s

hop

❖

Engin

e/m

odule

teard

ow

n m

anagem

ent

❖

Multi

sta

ge

com

ponent

routin

g

❖

En

gin

e/A

PU

/LG

main

ten

an

ce W

ork

flow

.

❖

En

gin

e

/ A

PU

T

est

&

QE

C

Bu

ildu

p

sectio

n

wo

rkflo

w.

❖

Lan

din

g G

ear S

ho

p W

ork

flow

.

10.5

B

ud

getin

g &

Fin

an

cia

l Co

ntro

l (thru

ER

P in

terfa

ce)

❖

Budget p

lannin

g fo

r Engin

e/ A

PU

/ Landin

g

Gear

❖

Repair/ o

verh

aul c

ost

contro

l

❖

Mon

itor p

erfo

rmance

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

65

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

11.0

F

un

ctio

nal R

eq

uire

men

ts fo

r To

ols

an

d E

qu

ipm

en

t& S

tan

dard

L

ab

Resp

on

se

S/E

/A/N

Rem

ark

11.1

T

oo

ls M

aste

r data

❖

Defin

e to

ols

, GS

E a

nd fig

ure

s lo

catio

ns &

quantity

❖

Defin

e to

ols

maste

r data

❖

Functio

nality

for re

serv

atio

n, in

-use,

availa

ble

❖

Tra

nsporta

tion o

rder fo

r tools

❖

Sta

tistic

s c

oncern

ing u

tilizatio

n

❖

Main

tena

nce p

lannin

g o

f tools

& re

pair

11.2

C

alib

ratio

n o

f too

ls

❖

Regis

ter to

ols

❖

Schedule

tools

calib

ratio

n

❖

Report c

alib

ratio

n c

om

plia

nce

11.3

S

tan

da

rd L

ab

s F

un

ctio

ns

❖

Too

ls / e

qu

ipm

en

t wo

rk o

rde

r

❖

Ca

libra

tion

ch

eck/a

dju

stm

en

t with

refe

ren

ce

to s

tan

da

rds

❖

Ca

libra

tion

stic

ke

r/ce

rtificate

s

❖

Intim

atio

n to

ow

ne

r tool s

tore

❖

Su

b-c

on

tractin

g fo

r no

-ca

pab

ility ite

ms

❖

Equ

ipm

en

t un

de

r Ca

l trackin

g b

y u

se

r se

ctio

n.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

66

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

C3-1

G

en

era

l Fu

nctio

nal R

eq

uire

men

ts o

f the M

RO

/ M&

E S

yste

m

R

esp

on

se

S/E

/A/N

Rem

ark

1

Ab

ility fo

r Inte

gra

tion

with

ER

P &

inte

rfacin

g w

ith o

ther

Ap

plic

atio

ns

❖

Ora

cle

ER

P s

yste

m c

ontro

ls a

ll majo

r PIA

resourc

es. A

sm

ooth

in

tegra

tion b

etw

ee

n th

e E

RP

, exis

ting a

pplic

atio

n ru

nnin

g in

P

IAC

and th

e M

RO

/ M&

E s

yste

m is

require

d.

➢

T

he fo

llow

ing a

reas fo

r inte

gra

tion a

re h

ighlig

hte

d:

Fin

ancia

l Accountin

g, F

inancia

l Contro

l, Budg

etin

g,

Purc

hasin

g, L

og

istic

, HR

, Tra

inin

g &

Q

ualific

atio

ns/C

ertific

atio

ns

❖

Sab

re A

irCentre

&

S

abre

A

irVis

ion ap

plic

atio

ns are

used in

F

light

pla

nn

ing

&sche

dulin

g.

An

inte

rface

to

MR

O

/ M

&E

S

olu

tion is

req

uire

d a

t min

imum

. ➢

The fo

llow

ing a

reas fo

r inte

rfacin

g a

re s

pecific

ally

hig

hlig

hte

d;

Schedule

/Slo

t/Fle

et

managem

ent,

Flig

ht

Pla

n/M

ovem

ent

manager, A

CA

RS

managem

ent.

2

MIS

& R

ep

ortin

g

❖

Key P

erfo

rmance In

dic

ato

rs to

be re

porte

d fo

r all m

ajo

r sectio

ns in

PIA

Engin

ee

ring o

n re

gu

lar b

asis

. The K

PI to

be

defin

ed b

y P

IA.

❖

The P

IA E

ngin

eerin

g M

anag

em

ent s

hall g

et re

gula

r rep

orts

concern

ing th

e re

gula

r and u

n-re

gula

r opera

tion.

3

Th

e S

yste

m w

ill co

ntro

l the d

ay-b

y-d

ay w

ork

❖

A

ll work

packages, ta

sks a

nd b

usin

ess a

ctiv

ities w

ill be in

itiate

d

and c

ontro

lled b

y th

e s

yste

m.

❖

Subsequ

ently

all L

abels

, Ord

ers

and C

ertific

ate

s a

re p

rinte

d b

y

the S

yste

m.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

67

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

4

Drill d

ow

n o

ptio

n a

nd

flexib

le re

po

rting

❖

F

rom

the to

p to

the b

otto

m it m

ust b

e p

ossib

le to

genera

te

reports

with

more

deta

ils if re

quire

d.

❖

Besid

e re

gu

lar u

sed re

ports

, a fle

xib

le re

port g

enera

tor fo

r occasio

nal u

se.

❖

Tra

cin

g o

f info

rmatio

n a

long a

logic

al p

ath

. ❖

D

ashbo

ard

for m

anagem

ent / p

lanners

for liv

e s

tatu

s o

f fleet

and m

ain

tenance in

pro

gre

ss &

oth

er re

late

d in

form

atio

n.

5

Fle

xib

ility

c) O

rganiz

atio

nal c

han

ges s

hall b

e e

asily

addre

ssed in

the

Syste

m b

y re

-config

ura

tion.

d)

In c

ase o

f outs

ourc

ing p

arts

of th

e p

roductio

n (e

.g. B

ase

Main

tena

nce, E

ngin

e O

H), th

e s

yste

m s

hall b

e a

ble

to b

e

custo

miz

ed a

ccord

ingly

.

6

Ad

va

nc

ed

MR

O / M

&E

Co

nc

ep

ts

❖ S

upport e

-Tech-L

og / w

-Cabin

-Log

❖

Airp

lan

e / E

ngin

e H

ea

lth m

onito

ring,

❖

Analy

tics

Tools

fo

r pre

dic

tive

&

pre

scrip

tive

defe

ct

managem

ent/ tro

uble

sh

ootin

g

❖

Futu

re u

pgra

da

bility

for Io

T s

olu

tions.

❖

RF

ID

❖

Sm

art c

ard

❖

B

arc

ode b

ase

d

❖

Oth

er e

merg

ing tre

nds in

avia

tion (d

escrib

e in

Rem

ark

s

colu

mn)

❖

Support fo

r mobile

technolo

gy in

clu

din

g c

ell p

hones, ta

ble

ts &

iP

ads.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

68

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

7

Req

uire

d In

terfa

ces o

f the n

ew

MR

O / M

&E

Sys

tem

❖

The A

ircra

ft log d

ata

(Fh, C

ycle

s) e

ntry

at o

ne

locatio

n in

PIA

. T

he M

RO

/ M&

E S

yste

m s

hall h

ave a

n in

terfa

ce fo

r a re

al-tim

e

data

uplo

ad. A

CA

RS

shall b

e u

se

d w

here

possib

le.

❖

The A

ircra

ft Rota

tion P

lan s

hall b

e a

va

ilable

on

line fo

r Pla

nnin

g

sectio

ns o

f PIA

Engin

eerin

g, s

ho

win

g in

tera

ctiv

ely

the p

lan

ned

A

/C a

ssig

nm

ents

to ro

ute

s a

nd th

e s

lots

main

tenance e

ve

nts

.

❖

The C

om

merc

ial F

light S

chedule

shall b

e o

nlin

e a

vaila

ble

for

long a

nd m

ediu

m-te

rm p

lan

nin

g.

❖

PIA

Opera

tions w

ill monito

r opera

tional p

erfo

rmance a

nd A

/C

dis

patc

h re

liability

. An o

nlin

e in

terfa

ce w

ill pro

vid

e th

e d

ata

for

PIA

Engin

eerin

g.

❖

P

IA

Fin

ance

is

responsib

le

for

the

Fin

ancia

l B

udget

and

Fin

ancia

l A

ccountin

g.

The

data

are

share

d

with

P

IA

Engin

eerin

g o

n o

nlin

e b

asis

for p

erfo

rmance m

onito

ring a

nd

pla

nnin

g p

urp

oses.

❖

Auto

mate

d u

plo

ad o

f all O

EM

manuals

, such a

s A

MM

, IPC

, S

RM

, EM

M, T

SM

and o

thers

usin

g th

e S

1000

D s

tandard

s

❖

Auto

matic

uplo

ad o

f SB

’s, A

D’s

,

❖

Mate

rial M

aste

r data

shall b

e u

p-lo

aded u

sin

g th

e A

MT

OS

S

and S

PE

C200

0 d

ata

sta

ndard

s

❖

Uplo

ad o

f Vendor c

apability

list, p

rice lis

t, availa

bility

sta

tus a

nd

oth

ers

(ER

P)

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

69

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

❖

E

lectro

nic

exch

ange o

f agre

em

ents

, purc

hase o

rder, d

eliv

ery

/ re

pair

sta

tus,

invoic

e,

pa

ym

ents

. S

upporte

d fo

rmats

shall

be

ED

I, X

ML,

SP

EC

2000

and

oth

ers

. A

n

inte

rnatio

na

l B

2B

com

munic

atio

n

pla

tform

to

be

inte

rfaced

for

exchangin

g

pro

cure

ment a

nd re

pair s

tatu

s in

form

atio

n.

❖

The n

ew

Syste

m s

hall s

upport a

WE

B P

orta

l to p

rovid

e m

ajo

r in

form

atio

n a

nd d

ata

for p

roductio

n. It is

the ta

rget, to

avoid

tim

e

consum

ing

and

outd

ate

d

paper

base

d

dis

tributio

n

of

info

rmatio

n.

❖

The s

yste

m to

be re

ady fo

r RF

ID a

pplic

atio

ns to

be in

tegra

ted.

Als

o,

the P

IAC

em

plo

ye

e ID

card

to

be re

ad fo

r em

plo

yee

ackno

wle

dgem

ent.

❖

T

he w

ork

ing p

apers

such a

s J

ob C

ard

s a

nd p

arts

tags to

be

prin

ted w

ith b

arc

ode. B

ar c

ode re

aders

to b

e in

tegra

ted fo

r m

an h

our re

cord

ing a

nd

parts

trackin

g.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

70

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H5

S

ER

VIC

ES

RE

QU

IRE

ME

NT

S

Deta

iled b

elo

w a

re th

e s

erv

ices re

quire

ments

. Contra

cto

rs m

ust p

rovid

e th

eir re

sponses in

the “

Resp

on

se” c

olu

mn a

nd

pro

vid

e a

dditio

nal in

form

atio

n / c

larific

atio

n in

the “

Rem

ark

s” c

olu

mn.

Vendor re

spo

nse m

ust b

e re

stric

ted to

:

Sr. N

o.

Resp

on

se

Rem

ark

s

1.

Y

= Y

es

Deta

ils o

f how

the s

erv

ices w

ould

be p

rovid

ed

2.

N

= N

o / C

annot b

e p

rovid

ed

Nil

In c

ase th

e C

ontra

cto

r does n

ot p

rovid

e a

resp

onse, it w

ill be c

onsid

ere

d a

s “

N”.

The C

ontra

cto

r should

pro

vid

e th

e re

spo

nse b

y fillin

g u

p th

e c

olu

mns "

Resp

on

se" a

nd "

Rem

ark

s" o

nly

. Any c

ha

nges,

such a

s a

dditio

n, d

ele

tion, o

r modific

atio

n o

f row

conte

nts

in th

e R

FP

docum

ent, w

ill be c

onsid

ere

d a

s a

n in

va

lid re

sponse

to th

e R

FP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

71

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

SE

RV

ICE

S R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

1

IM

PL

EM

EN

TA

TIO

N

1.1

An Im

ple

menta

tion S

trate

gy h

as b

een s

ubm

itted th

at c

overs

:

1.1

.1

In

sta

llatio

n o

f the In

terim

Serv

er(s

) inclu

din

g th

e O

pera

ting S

yste

m.

1.1

.2

In

sta

llatio

n o

f all s

upplie

d A

pplic

atio

n s

oftw

are

, D

BM

S s

oftw

are

, Develo

pm

ent /

Query

and R

eport W

riter / D

ata

base A

dm

inis

tratio

n T

ools

and a

ny o

ther re

quire

d

Utilitie

s, o

n th

e In

terim

Serv

er(s

).

1.1

.3

In

sta

llatio

n o

f all s

upplie

d A

pplic

atio

n s

oftw

are

, D

BM

S s

oftw

are

, Develo

pm

ent /

Query

and R

eport W

riter / D

ata

base A

dm

inis

tratio

n T

ools

and a

ny o

ther re

quire

d

Utilitie

s, o

n th

e P

erm

anent S

erv

ers

.

1.1

.4

Im

ple

menta

tion o

f Data

base s

ecurity

featu

res

1.1

.5

Develo

pm

ent o

f Busin

ess R

equire

ment D

ocum

ent fo

r each fu

nctio

nal a

rea w

hic

h

maps th

e b

usin

ess p

rocess fo

r the p

ara

mete

rizatio

n / c

onfig

ura

tion o

f MR

O / M

&E

P

ackage.

T

his

docum

ent

will

be

based

on

PIA

C’s

re

engin

eere

d

busin

ess

pro

cesses p

rovid

ed b

y P

IA.

1.1

.6

D

evelo

pm

ent o

f busin

ess c

ase s

cenario

s

1.1

.7

P

ara

mete

rizatio

n o

f supplie

d S

oftw

are

i.e. th

e c

onfig

ura

tion o

f applic

atio

n s

oftw

are

via

sele

ctio

n of

in-b

uilt

valu

es,

settin

g up of

table

s,

etc

. to

m

eet

the busin

ess

require

ments

.

1.1

.8

S

oftw

are

m

odific

atio

ns,

where

re

quire

d,

to

supplie

d

Applic

atio

n

softw

are

and

develo

pm

ent o

f exte

nsio

ns a

nd / o

r module

s to

meet th

e b

usin

ess re

quire

ments

.

1.1

.9

In

tegra

tion

with

P

IAC

’s

oth

er

applic

atio

ns

such

as

Ora

cle

E

RP

, S

abre

applic

atio

ns, A

IMS

, PIA

website

, etc

.

1.1

.10

D

esig

n a

nd d

evelo

pm

ent o

f custo

miz

ed re

ports

, scre

ens, w

ork

flow

s, e

tc. T

here

is

no u

pper lim

it to th

e c

usto

miz

atio

n th

at w

ill be u

nderta

ken

1.1

.11

D

esig

n, d

evelo

pm

ent a

nd in

itial s

et u

p o

f data

bases.

1.1

.12

T

estin

g S

trate

gy. U

nit, In

tegra

tion a

nd S

yste

m te

stin

g p

rior to

User A

ccepta

nce

testin

g.

1.1

.13

D

ata

mig

ratio

n activ

ities.

These in

clu

de pre

para

tion of

data

mig

ratio

n s

trate

gy,

and u

nderta

kin

g d

ata

mig

ratio

n a

ctiv

ities a

s p

er s

ectio

n D

, sub

-sec: 3

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

72

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

SE

RV

ICE

S R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

1.1

.14

D

esig

n a

nd im

ple

menta

tion o

f Onlin

e a

nd B

atc

h jo

b o

pera

tional p

rocedure

s u

ntil

imple

menta

tion is

successfu

lly c

om

ple

ted a

t all lo

catio

ns.

1.1

.15

P

rogre

ss re

portin

g o

n C

ontra

cto

r rela

ted a

ctiv

ities.

1.1

.16

Q

uality

Assura

nce fo

r Contra

cto

r rela

ted a

ctiv

ities.

1.1

.17

A

ny

oth

er

tasks

require

d

in

successfu

l deliv

ery

of

the

supplie

d

pro

ducts

and

serv

ices.

1.2

Airlin

e in

dustry

specific

rapid

imple

menta

tion te

mpla

tes w

ill be u

tilized to

ensure

quic

k im

ple

menta

tion. D

eta

ils o

f such te

mpla

tes a

re s

ubm

itted w

ith th

e T

echnic

al

Pro

posal

1.3

A d

eta

iled c

om

pre

hensiv

e p

roje

ct p

lan is

pre

pare

d a

nd s

ubm

itted a

s a

part o

f the

pro

posal.

1.4

A d

eta

iled p

roje

ct o

rganiz

atio

n s

tructu

re h

as b

een s

ubm

itted:

1.4

.1

Id

entify

ing th

e s

pecific

indiv

iduals

who w

ould

be a

ssig

ned d

iffere

nt ta

sks o

f this

pro

ject.

1.4

.2

Assig

n a

full-tim

e P

roje

ct M

anager to

manage th

is P

roje

ct. T

his

pers

on m

ust b

e

from

the lis

t of L

ead C

onsulta

nts

subm

itted b

y th

e C

ontra

cto

r in re

sponse to

the

EO

I. He / s

he m

ust h

ave th

e e

xperie

nce o

f imple

mentin

g th

e p

roposed M

RO

/

M&

E S

OLU

TIO

N in

at le

ast tw

o a

irlines. H

is/h

er d

eta

iled C

V in

clu

din

g e

xperie

nce

of

managin

g

MR

O

/ M

&E

IT

and

oth

er

Pro

jects

, M

RO

/

M&

E

IT

Package

Certific

atio

n, if a

ny, th

e n

um

ber o

f MR

O / M

&E

pro

jects

managed a

nd th

e n

um

ber

of y

ears

on e

ach p

roje

ct, e

tc. m

ust b

e s

ubm

itted a

long w

ith th

e P

roposal.

1.4

.3

Conta

inin

g a pers

onnel

roste

r conta

inin

g deta

iled re

sponsib

ilities of

Contra

cto

r sta

ff assig

ned

to

perfo

rm

dutie

s

or

serv

ices.

T

he

roste

r in

clu

des

estim

ate

d

num

ber o

f hours

to b

e w

ork

ed o

n th

e p

roje

ct fo

r each p

ers

on b

roken d

ow

n in

diffe

rent p

hases o

f the

pro

ject c

learly

identify

ing th

e s

tart a

nd e

nd d

ate

s fo

r each

phase.

T

hese

sta

ff m

em

bers

are

fro

m

the

list

of

imple

mente

rs

pro

vid

ed

in

response to

the E

OI.

1.4

.4

S

ubstitu

tes to

the n

om

inate

d s

taff w

ill have q

ualific

atio

ns e

quiv

ale

nt to

or b

ette

r th

an th

ose w

ho w

ill be re

pla

ced.

1.5

The C

ontra

cto

r must p

rovid

e, b

y p

hase, th

e p

roposed n

um

ber o

f pers

onnel to

be

based o

n-s

ite a

t PIA

C’s

pre

mis

es, a

nd s

pace a

nd o

ther lo

gis

tical re

quire

ments

to

be p

rovid

ed b

y P

IA d

urin

g Im

ple

menta

tion

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

73

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

SE

RV

ICE

S R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

1.6

T

he C

ontra

cto

r’s im

ple

menta

tion p

lan ta

kin

g due consid

era

tion to

th

e busin

ess

prio

rity a

reas a

nd a

pplic

atio

ns.

1.7

A s

yste

m tu

rnover p

lan w

ill be d

evelo

ped th

at w

ill indic

ate

the c

onditio

nal c

riteria

re

quire

d to

fully

turn

over th

e d

aily

opera

tion o

f the s

yste

m to

PIA

technic

al s

taff.

At a

min

imum

, the tu

rnover p

lan w

ill inclu

de th

e s

tate

of re

adin

ess re

quire

d fo

r syste

m tu

rnover a

nd a

ll require

d d

ocum

enta

tion.

1.8

Durin

g

syste

m

insta

llatio

n,

the

Contra

cto

r w

ill evalu

ate

perfo

rmance

facto

rs

inclu

din

g, b

ut n

ot lim

ited to

, transactio

n v

olu

mes, re

sponse tim

es, C

PU

utiliz

atio

n,

and in

put / o

utp

ut a

ctiv

ity. T

he C

ontra

cto

r is re

sponsib

le fo

r tunin

g th

e a

pplic

atio

n

to m

eet a

ccepta

ble

response tim

es.

1.9

The C

ontra

cto

r m

ust

subm

it a deta

iled T

estin

g M

eth

odolo

gy.

The B

idder

may

perfo

rm

Unit,

Inte

gra

tion,

and

Syste

ms

Tests

off-s

ite;

how

eve

r, th

e

offic

ial

Syste

ms T

est a

nd a

ll User A

ccepta

nce T

ests

must b

e p

erfo

rmed o

n-s

ite u

sin

g

PIA

C’s

testin

g e

nviro

nm

ent.

1.1

0

The C

ontra

cto

r will c

onduct a

Capacity

Test th

at w

ill inclu

de s

tress a

nd v

olu

me

testin

g. C

apacity

testin

g s

hall in

clu

de a

stre

ss te

st th

at in

clu

des s

imula

tion o

f at

least 3

0%

of th

e s

yste

m w

ork

load a

nd v

olu

me te

sts

that te

st th

e d

ata

base a

ctiv

ity

again

st

at

least

30%

of

the data

volu

me.

T

he C

ontra

cto

r w

ill docum

ent,

the

conclu

sio

ns re

sultin

g fro

m th

e te

st

1.1

1

The C

ontra

cto

r will p

repare

and s

ubm

it weekly

pro

gre

ss re

ports

to P

IA o

n e

ach

com

ponent o

f the P

roje

ct u

nder w

hic

h it is

responsib

le

1.1

2

Pro

ject

Quality

M

anagem

ent:

In its

pro

posal,

the C

ontra

cto

r must

describ

e its

appro

ach fo

r assurin

g th

e q

uality

of its

com

ponents

on th

is p

roje

ct. T

he p

roposal

must d

em

onstra

te a

n u

nders

tandin

g o

f the C

ontra

cto

r’s u

ltimate

responsib

ility fo

r quality

and d

efin

e a

com

pre

hensiv

e s

et o

f reasonable

and e

ffectiv

e p

ractic

es fo

r fu

lfilling th

at re

sponsib

ility.

1.1

3

Accepta

nce T

estin

g: P

IAC

’s M

&E

Team

will c

onduct a

rigoro

us a

ccepta

nce te

st

of th

e s

yste

m. P

IA u

ser s

taff a

nd in

form

atio

n s

yste

m s

pecia

lists

will e

xerc

ise a

ll

syste

m fu

nctio

nal a

spects

usin

g a

ppro

pria

te te

st d

ata

(use c

ases d

evelo

ped fro

m

real-tim

e P

IA e

ngin

eerin

g &

main

tenance o

pera

tions) to

assure

that th

e s

yste

m

meets

defin

ed busin

ess and te

chnic

al

perfo

rmance re

quire

ments

. D

urin

g th

is

test, P

IAC

’s M

RO

/ M&

E T

eam

will id

entify

require

d m

odific

atio

ns a

nd d

ocum

ent

them

th

rough

the

pro

ble

m

resolu

tion

or

change

managem

ent

pro

cesses

(describ

ed belo

w)

as appro

pria

te.

T

he C

ontra

cto

r shall

modify

th

e syste

m as

require

d a

nd p

rovid

e n

ew

vers

ions o

f modifie

d c

om

ponents

to P

IA fo

r testin

g. P

IA

will

notify

th

e

Contra

cto

r in

w

riting

when

it dete

rmin

es

that

the

syste

m

is

accepta

ble

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

74

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

1.1

4

Pro

ble

m R

esolu

tion: T

he C

ontra

cto

r and P

IAC

’s M

RO

/ M&

E T

eam

will c

oopera

te

to re

solv

e s

yste

m p

roble

ms fo

und d

urin

g a

ccepta

nce te

stin

g a

nd p

roductio

n u

se,

inclu

din

g th

e w

arra

nty

perio

d. P

IA w

ill prio

ritize a

nd re

port p

roble

ms in

a w

ritten

form

at.

T

he C

ontra

cto

r shall

track th

ese pro

ble

ms to

clo

sure

and re

port

their

sta

tus. T

he C

ontra

cto

r shall e

valu

ate

each re

porte

d p

roble

m, e

stim

ate

the tim

e

needed to

resolv

e th

e p

roble

m, id

entify

pote

ntia

l impacts

on th

e s

yste

m a

nd th

e

pro

ject, a

nd re

port to

PIA

. If PIA

decid

es to

pro

ceed, th

e C

ontra

cto

r shall re

solv

e

the p

roble

m a

ccord

ing to

its a

ssig

ned p

riority

1.1

5

Change M

anagem

ent: P

IAC

’s M

RO

/ M&

E T

eam

and C

ontra

cto

r will c

oopera

te in

managin

g

changes

to

pre

vio

usly

agre

ed

upon

syste

m

functio

nal

capabilitie

s.

PIA

C’s

MR

O / M

&E

Team

will id

entify

pote

ntia

l functio

nal c

hanges a

nd p

ropose

these to

the C

ontra

cto

r in w

riting. T

he C

ontra

cto

r shall e

valu

ate

each p

roposal,

identify

pote

ntia

l impacts

on th

e s

yste

m a

nd th

e p

roje

ct tim

elin

e, a

nd re

port to

PIA

. If

PIA

decid

es to

pro

ceed,

it w

ill prio

ritize th

e c

hange and auth

oriz

e th

e

Contra

cto

r in w

riting to

perfo

rm th

e w

ork

. The C

ontra

cto

r shall tra

ck th

e s

tatu

s o

f

in

pro

gre

ss

change

ord

ers

and

report

to

PIA

upon

request.

H

ow

ever,

cost

escala

tion w

ill not b

e a

llow

ed u

nd

er a

ny c

ircum

sta

nces.

1.1

6

Config

ura

tion M

anagem

ent: T

he C

ontra

cto

r will m

anage v

ers

ion re

leases o

f all

contra

ct d

eliv

era

ble

s a

nd c

erta

in o

ther c

ritical d

ocum

ents

as d

ete

rmin

ed b

y P

IA.

1.1

7

Ensure

re

gula

tory

com

plia

nce

with

P

CA

A

AN

O-1

45.

The

contra

cto

r w

ill be

require

d

to

coopera

te

with

th

e

PC

AA

audit

team

, by

pro

vid

ing

functio

nality

dem

onstra

tions a

nd re

ports

as re

quire

d. A

ny n

on

-com

plia

nce s

hall b

e a

ddre

ssed

by th

e c

ontra

cto

r till com

plia

nce is

verifie

d.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

75

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

SE

RV

ICE

S R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

2

T

RA

ININ

G

2.1

Tra

inin

g S

trate

gy h

as b

een s

ubm

itted a

s p

art o

f the T

echnic

al P

roposal

2.2

It describ

es in

deta

il the a

ppro

ach to

meetin

g th

e tra

inin

g re

quire

ments

for e

ach

type o

f audie

nce

2.3

The g

enera

l conte

nt o

f all tra

inin

g m

ate

rials

, train

ing c

ours

es, a

nd d

ocum

enta

tion

pro

posed h

as b

een d

escrib

ed in

the T

echnic

al P

roposal

2.4

Pro

vis

ion o

f Tra

inin

g M

ate

rial fo

r Technic

al s

upport s

taff &

syste

m u

sers

3

D

AT

A M

IGR

AT

ION

3.1

A d

escrip

tion o

f the g

enera

l appro

ach to

the d

ata

mig

ratio

n p

rocess (m

anual a

nd

auto

mate

d) fo

r his

toric

al, s

eed, a

nd c

uto

ver d

ata

has b

een p

rovid

ed.

3.2

Mig

ratio

n a

ppro

ach / s

trate

gy a

ddre

sses th

e fo

llow

ing:

3.2

.1 M

igra

tion p

rocess (a

uto

mate

d o

r manual, v

erific

atio

n p

rocedure

s)

3.2

.2 M

igra

tion s

chedule

3.2

.3

M

igra

tion p

repara

tion ta

sk o

utlin

e

3.2

.4

Resourc

e re

quire

ments

3.2

.5

Tra

inin

g R

equire

ments

3.2

.6

Pro

gra

mm

ing e

ffort/u

se th

ird-p

arty

applic

atio

n

3.3

Expecta

tions fro

m B

idders

:

3.3

.1

If s

uccessfu

l will p

repare

a d

eta

iled p

lan fo

r data

mig

ratio

n. (S

ectio

n: D

, D3

-5)

3.3

.2

W

ill ensure

sm

ooth

transitio

n w

ithout s

yste

m d

ow

ntim

e.

3.3

.3

W

ill desig

n / a

cquire

rele

vant p

rogra

m/s

oftw

are

to e

nsure

data

cle

ansin

g/in

tegrity

3.3

.4

D

em

onstra

te &

test d

ata

thru

sam

ple

s ta

ken fro

m liv

e s

yste

m.

3.3

.5 D

evelo

p &

docum

ent a

ll opera

tional a

reas o

f the a

bove s

olu

tion

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

76

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

SE

RV

ICE

S R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

4

D

OC

UM

EN

TA

TIO

N

4.1

Contra

cto

r will p

rovid

e u

ser m

anuals

that w

ill cover a

s a

min

imum

the fo

llow

ing:

4.1

.1

C

om

ple

te in

stru

ctio

ns fo

r the u

sers

, com

ple

tely

expla

inin

g th

e u

se o

f each s

yste

m

functio

n;

4.1

.2

S

yste

m u

sage s

cenario

s, b

ased o

n re

al w

orld

exam

ple

s d

raw

n fro

m th

e d

ay-to

-day w

ork

loads o

f typic

al u

sers

, that fu

lly d

escrib

e a

nd e

xpla

in th

e s

alie

nt fe

atu

res

and o

pera

tion o

f the s

yste

m;

4.1

.3

H

ow

input d

ata

are

sto

red a

nd re

late

d b

etw

een s

yste

m re

cord

s;

4.1

.4

H

ow

to g

enera

te / s

uppre

ss s

tandard

and a

d h

oc re

ports

;

4.1

.5

N

orm

al re

port d

istrib

utio

n;

4.1

.6

P

rioritiz

atio

n p

rocessin

g, s

yste

m d

ete

rmin

ed p

rioritie

s, a

nd u

ser o

verrid

e

pro

cedure

s;

4.1

.7

S

yste

m lo

g-o

n, lo

g-o

ff, and s

ecurity

featu

res;

4.1

.8

E

rror m

essages a

nd e

rror c

orre

ctio

n p

rocedure

s;

4.1

.9

H

elp

featu

res a

nd u

sage;

4.1

.10

S

yste

m tro

uble

shootin

g;

4.1

.11

M

andato

ry d

ata

field

s a

nd d

efa

ult d

ata

valu

es;

4.1

.12

T

ravers

ing s

yste

m m

enus;

4.1

.13

S

cre

en la

youts

and c

onte

nts

;

4.1

.14

In

quiry

functio

ns

4.2

Contra

cto

r will p

rovid

e te

chnic

al m

anuals

that w

ill cover a

s a

min

imum

the

follo

win

g:

4.2

.1

A

ddre

sses th

e v

iew

of th

e s

yste

m re

quire

d b

y d

evelo

pers

, adm

inis

trato

rs a

nd o

ther

technic

al p

ers

onnel.

4.2

.2

P

rovid

es a

n u

nders

tandin

g o

f the a

pplic

atio

n; d

ata

base d

esig

n a

nd file

stru

ctu

res;

rela

tionship

s b

etw

een p

rogra

ms, s

ecurity

; trouble

shootin

g; s

pecia

l constra

ints

; and

oth

er o

pera

tional g

uid

elin

es

4.3

Contra

cto

r has s

ubm

itted s

am

ple

copie

s o

f all p

roposed d

ocum

ents

that it w

ill pre

pare

/ deliv

er to

PIA

durin

g th

e c

ours

e o

f this

pro

ject.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

77

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

SE

RV

ICE

S R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

5

W

AR

RA

NT

Y A

ND

MA

INT

EN

AN

CE

SU

PP

OR

T

5.1

Contra

cto

r will p

rovid

e w

arra

nty

serv

ices fo

r a p

erio

d o

f thre

e y

ears

by e

nsurin

g

that th

e s

yste

m in

every

way m

eets

the s

pecific

atio

ns s

tate

d in

this

RF

P

5.2

Separa

te

and

apart

from

th

e

warra

nty

support

serv

ices,

the

Contra

cto

r shall

pro

vid

e s

upport (“M

ain

tenance”) s

erv

ices fo

r Applic

atio

ns, a

nd D

BM

S b

egin

nin

g

upon th

e e

nd o

f the w

arra

nty

serv

ices a

nd e

xte

nded u

p to

thre

e (3

) year th

ere

afte

r

5.3

Contra

cto

r has p

rovid

ed its

User a

nd T

echnic

al S

upport P

lan d

eta

iling th

e

follo

win

g:

5.3

.1

O

n-s

ite fa

ult d

iagnostic

techniq

ues;

5.3

.2

R

em

ote

or te

le-d

iagnostic

fault d

iagnosin

g te

chniq

ues;

5.3

.3

A

vera

ge tim

e to

arriv

e o

n-s

ite;

5.3

.4

M

ean tim

e to

fix m

ajo

r syste

m c

om

ponents

;

5.3

.5

F

ault e

scala

tion p

rocedure

s;

5.3

.6

M

ain

tenance o

f erro

r logs.

5.4

Contra

cto

r will e

sta

blis

h H

otlin

e a

nd H

elp

desk s

upport

5.5

Contra

cto

r has s

pecifie

d a

solu

tion to

accom

modate

PIA

’s re

quire

ment o

f additio

nal

custo

miz

ed re

ports

durin

g th

e m

ain

tenance a

nd s

upport p

erio

d.

6

V

ER

SIO

NS

AN

D U

PG

RA

DE

S

6.1

Contra

cto

r has a

ssure

d th

at tra

inin

g m

ate

rial / s

oftw

are

/ pro

cess d

ocum

ents

will

be d

uly

licensed fo

r the p

urp

ose o

f imple

menta

tion a

nd u

se b

y P

IA fo

r the E

RP

. T

hese w

ill be of

late

st

vers

ion and C

ontra

cto

r w

ill ensure

up

-gra

datio

n of

all

module

s / m

ate

rial / p

rocess d

ocum

ents

durin

g th

e w

arra

nty

perio

d a

nd a

s p

art o

f afte

r-warra

nty

main

tenance s

upport.

6.2

Durin

g th

e im

ple

menta

tion a

nd s

ubsequent ro

llout C

ontra

cto

r will b

e re

sponsib

le

to

arra

nge

and

pro

vid

e

free

vers

ion

upgra

des

of

all

com

ponents

under

its

responsib

ility. C

ontra

cto

r will e

nsure

that a

t the tim

e o

f handin

g o

ver th

e s

olu

tion

to P

IA all

com

pon

ents

are

of

the la

test

rele

ase and th

at

the to

tal

solu

tion is

certifie

d b

y th

e C

ontra

cto

r for c

om

ple

teness.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

78

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H6

H

AR

DW

AR

E R

EQ

UIR

EM

EN

TS

D

eta

iled b

elo

w a

re th

e h

ard

ware

require

ments

. Contra

cto

rs m

ust p

rovid

e th

eir re

sponses in

the “

Resp

on

se” c

olu

mn a

nd

pro

vid

e a

dditio

nal in

form

atio

n / c

larific

atio

n in

the “

Rem

ark

s” c

olu

mn.

Vendor re

spo

nse m

ust b

e re

stric

ted to

:

Sr. N

o.

Resp

on

se

Rem

ark

s

1.

Y

= Y

es

Deta

ils o

f how

the h

ard

ware

require

ments

will b

e fu

lfilled

2.

N

= N

o / C

annot b

e p

rovid

ed

Nil

In c

ase th

e C

ontra

cto

r does n

ot p

rovid

e a

resp

onse, it w

ill be c

onsid

ere

d a

s “

N”.

The C

ontra

cto

r should

pro

vid

e th

e re

spo

nse b

y fillin

g u

p th

e c

olu

mns "

Resp

on

se" a

nd "

Rem

ark

s" o

nly

. Any c

ha

nges,

such a

s a

dditio

n, d

ele

tion, o

r modific

atio

n o

f row

conte

nts

in th

e R

FP

docum

ent, w

ill be c

onsid

ere

d a

s a

n in

va

lid re

sponse

to th

e R

FP

.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

79

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

HA

RD

WA

RE

RE

QU

IRE

ME

NT

S

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

1

H

AR

DW

AR

E

1.1

Contra

cto

r has s

ubm

itted deta

ils of

the pro

posed c

onfig

ura

tion, in

clu

din

g la

yout

dia

gra

m d

eta

iling m

odel d

esig

natio

n(s

), mem

ory

siz

e, n

um

ber o

f CP

Us, ty

pe o

f driv

es w

ith c

apacity

and c

ounts

.

1.2

The

offe

red

solu

tion

com

plie

s

with

th

e

Open

Syste

ms

Arc

hite

ctu

re

and

late

st

technolo

gy tre

nds.

1.3

The s

olu

tion is

scala

ble

, both

horiz

onta

lly a

nd v

ertic

ally

.

1.4

The h

ard

ware

is s

ized k

eepin

g in

vie

w th

e o

pera

tional re

quire

ments

of th

e M

RO

/ M

&E

and a

ssocia

ted a

pplic

atio

ns.

1.5

The h

ard

ware

is fu

lly c

apable

of h

ostin

g th

e M

RO

/ M&

E c

ertifie

d d

ata

base.

1.6

The h

ard

ware

allo

ws e

ach p

artitio

n o

f the M

RO

/ M&

E e

nviro

nm

ent to

be is

ola

ted in

such a

way th

at a

softw

are

fault in

one p

artitio

n w

ill not h

ave a

n im

pact o

n a

noth

er

partitio

n.

1.7

All s

oftw

are

require

d fo

r clu

ste

ring o

f serv

ers

and im

ple

menta

tion o

f DR

P is

in

clu

ded in

the s

olu

tion.

1.8

The s

olu

tion w

ill be fu

lly s

upporte

d b

y th

e C

ontra

cto

r for n

ot le

ss th

an te

n y

ears

fro

m th

e d

ate

of s

upply

. It will re

main

capable

of b

ein

g s

upporte

d, u

pgra

ded a

nd

exte

nded b

y th

e C

ontra

cto

r durin

g th

is p

erio

d.

1.9

The

solu

tion

pro

vid

ed

will

be

accom

panie

d

with

com

ple

te

docum

enta

tion,

opera

ting m

anuals

, syste

m dia

gra

ms,

sta

rtup and re

covery

pro

cedure

s and all

oth

er in

form

atio

n re

quire

d fo

r pro

per a

nd e

fficie

nt o

pera

tion.

1.1

0

Contra

cto

r will p

rovid

e a

ll technic

al m

ate

rial a

nd v

erifia

ble

benchm

ark

s re

late

d to

th

e p

roposed s

olu

tion. T

he h

ard

ware

is b

y th

e M

RO

/ M&

E p

rincip

al v

endor fo

r the

opera

tion o

f the M

RO

/ M&

E a

nd is

reasonably

expecte

d to

be c

ertifie

d fo

r futu

re

vers

ions o

f the M

RO

/ M&

E d

urin

g th

e e

xpecte

d life

of th

e h

ard

ware

.

1.1

1

C

ontra

cto

r has pro

vid

ed in

form

atio

n on w

arra

ntie

s on th

e equip

ment

and any

optio

ns re

gard

ing w

arra

nty

exte

nsio

n. P

rincip

al’s

assura

nce fo

r parts

availa

bility

afte

r expiry

of w

arra

nty

perio

d is

als

o p

rovid

ed.

1.1

2

T

he

Contra

cto

r has

to

pro

vid

e

thoro

ugh

and

conte

mpora

ry

3rd

party

te

stin

g

softw

are

for a

ccepta

nce a

nd lo

ad te

stin

g. T

he te

stin

g w

ill be d

one a

ccord

ing to

syste

m e

quip

ment s

pecific

atio

ns a

s w

ell a

s g

enera

lly a

ccepte

d p

ractic

es.

Sectio

n H

– R

equire

ments

Com

plia

nce M

atrix

Page 1

80

of 1

89

MR

O /

M&

E P

ro

je

ct

R

equ

est for P

rop

osal

H

AR

DW

AR

E R

EQ

UIR

EM

EN

TS

Sr. N

o.

Req

uire

men

t R

esp

on

se

(Y / N

) R

em

ark

s

1.1

3

A

ll test re

sults

will b

e c

om

ple

tely

docum

ente

d b

y th

e C

ontra

cto

r. Com

ple

te te

st

docum

enta

tion in

clu

din

g re

sults

of th

e 3

rd p

arty

load / s

tress te

stin

g s

oftw

are

will

be p

rovid

ed to

PIA

.

1.1

4

B

ased

on

PIA

C’s

hig

h

availa

bility

re

quire

ments

, fa

ilover

desig

n

is

based

on

pro

tectin

g s

ingle

poin

t of fa

ilure

.

1.1

5

For h

igh a

vaila

bility

on th

e a

pplic

atio

n la

yer, th

e s

olu

tion w

ill imple

ment lo

g o

n

load b

ala

ncin

g b

etw

een th

e a

pplic

atio

n s

erv

ers

. It does n

ot n

eed a

ny fo

rm o

f re

allo

catio

n o

f resourc

es b

etw

een

serv

ers

. The a

pplic

atio

n e

nviro

nm

ent is

siz

ed

and desig

ned such th

at

upon fa

ilure

of

an applic

atio

n serv

er

(based on sin

gle

poin

t of fa

ilure

), min

imum

degra

datio

n o

f perfo

rmance w

ill be e

xperie

nced.

1.1

6

A

Dis

aste

r Recovery

(DR

) desig

n is

pro

vid

ed w

hic

h p

rovid

es a

seam

less, p

ragm

atic

D

R p

rocess. It in

tegra

tes w

ithin

the o

vera

ll desig

n o

f the M

RO

/ M&

E la

ndscape.

1.1

7

The D

R p

rocess is

sim

ple

to e

xecute

. A s

tep

-by-s

tep p

rocess a

nd p

rocedure

is

pro

vid

ed to

min

imiz

e th

e p

ote

ntia

l for h

um

an e

rror in

a tim

e o

f cris

is a

nd d

isaste

r. A

dditio

nally

, the D

R d

esig

n c

an b

e e

asily

teste

d w

ith m

inim

al im

pact o

n d

ay-to

-day o

pera

tions.



SECTION I

COMPLETION AND COMPLIANCE CHECKLIST



I1 PROPOSAL COMPLETION CHECKLIST

RFP Reference

Requirement Description Yes / No Section

Sub section Item

B B3 Completed All Forms

a) Proposal Form b) Biding Organization & Experience c) Bidders Experience d) Description of Approach, Methodology & Project plan e) Team composition & task assignment f) CV of professional staff

g) Products Price Schedule h) Services Prices Schedule i) Recurrent Cost Schedule j) Proposal Price Summary k) Bid Bond l) Form of Contract Agreement m) Performance Guarantee n) Consortium Responsibility (if applicable)

B1 7.2.3 Declaration of accepting responsibility for the successful integration and interoperability of all proposed products and other PIA systems as required by the RFP documents (reference Section A5-1)

B1 8 Bid Bond

B1 4.2 Original plus One hardcopy of Technical and Commercial Proposals

B1 4.2A Softcopy of Technical Proposal

B1 11.4 Technical and Commercial Proposals provided separately, clearly marked and sealed, as required

B4 Proposal in Format, as specified in Section B3 – Format and Contents of Proposal

B1 22.1, 22.2

Declaration of not inducing or influencing the bidding / evaluation process

D D1 3 Comprehensive Project Plan

4 Project Organization Structure and Personnel Roster

E E1 DBMS And Database Administration Tools

F F1 Hardware specifications and design layout

G G1 Bidder’s Qualifications and Experience

H Requirements Compliance Matrix

I Completion and Compliance Checklist



I2 PRODUCTS AND SERVICES




E E1 DATABASE MANAGEMENT SYSTEM AND DATABASE ADMINISTRATION TOOLS

E2 APPLICATION DEVELOPMENT TOOLS

E3 QUERY AND REPORT GENERATION TOOLS

E4 INTERIM SERVERS

3 The Contractor is required, as part of its proposal to provide an Interim Server and Operating System Software.

4

It is anticipated that the Server(s) will be required for a period of approximately six to nine months from the date of supply of Server Hardware, Operating System Software and MRO / M&E Package Software.

5 The Contractor will be required to re-install all MRO / M&E, 3rd Party, Custom-built software, DBMS, Database, Development tools, etc. on the Permanent Server(s).

6 The details of the proposed Interim Server(s) hardware Configuration and Operating System software are to be provided by the Contractor in its proposal.

7 The configuration of machines should be capable to support the number of users as specified by the Contractor in its plan.

8 In its proposal, the Contractor will provide site specification requirements for the installation and operation of the Interim Server(s).

9

PIA - at the end of implementation and rollout - may at its discretion, decide to purchase the interim servers provided by the Contractor. In this regard, the Contractor should, as part of its Price Proposal, separately mention the cost at which it would offer these machines for sale to PIA. However, this cost component should not be added to the total bid price, nor should it be used to calculate the bid bond amount.

E5 3RD PARTY SOFTWARE

2

Contractor will be responsible to ensure that all required 3rd party software, operating systems, system management and monitoring tools, backup and recovery software, database administration tools, disaster recovery and business continuity tools, APIs / interfaces, etc. are made available, documented, designed, implemented and operational to meet PIA’s requirements in the proposed MRO / M&E solution.

3 It is the responsibility of the Contractor to offer PIA a complete solution in all respects – delays or costs arising out of any shortcoming will have to be borne by the Contractor.

D D1 IMPLEMENTATION


1.2 Installation of all supplied Application software, DBMS software, Development / Query and Report Writer / Database Administration Tools and any other required Utilities, on the Interim Server(s).

1.3 Installation of all supplied Application software, DBMS software, Development / Query and Report Writer / Database Administration Tools and any other required Utilities, on the Permanent Server(s).

1.4 Implementation of Database security features.

1.5

Development of Business Requirement Document for each functional area which maps the business process for the parameterization / configuration of MRO / M&E Package. This should be based on PIA’s reengineered business processes that would be made available to the Contractor.

1.6 Development of business case scenarios

1.7 Parameterization of supplied Software i.e. the configuration of application software via selection of in-built values, setting up of tables, etc. to meet the business requirements.






1.8 Software modifications, where required, to supplied Application software and development of extensions and / or modules to meet the business requirements.

1.9 Design, development and initial setup of databases.

1.10 Integration with PIA’s other applications such as Oracle ERP, Sabre applications, IBM Lotus Notes, AIMS, Aero-Exchange, PIA website, etc.

1.11

Design and development of customized reports, screens, workflows, etc. PIA will try to maximize the use of standard reports, screens and workflows available in the proposed solution; however, the Contractor cannot set an upper limit to the number of customization that it will undertake.



1.14 Design and implementation of online and batch job operational activities until implementation is successfully completed at all locations.

1.15 Progress reporting on Contractor related activities.

1.16 Quality Assurance for Contractor related activities.

1.17 Any other tasks required in successful delivery of the supplied products and services.

2 Contractor must utilize airline industry specific rapid implementation templates to ensure quick implementation. Details of such templates should be submitted with the Technical Proposal.

3

A detailed comprehensive business plan is to be prepared by Contractor and submitted as a part of project. The business plan shall be mutually approved and incorporated as part of contract and reviewed at regular intervals.

4

The Contractor must submit a detailed project organization structure identifying, by name, the specific individuals who would be assigned different tasks of the project.

The Contractor must assign a full-time Project Manager to manage this Project. This person must be from the list of Lead Consultants submitted by the Contractor in response to the EOI. He / she must have the experience of implementing the proposed MRO / M&E in at least two airlines. His / her detailed CV including experience of managing MRO / M&E and other projects; MRO / M&E certification, if any; number of MRO / M&E projects managed; number of years on each project; etc. must be submitted along with the Technical Proposal.

A personnel roster containing detailed responsibilities of Contractor staff should also be provided. It should include the estimated number of hours to be worked on the project for each person broken down in different phases of the project; it should also clearly identify the start and end dates for each phase. These staff members should be from the list of implementers provided in response to the EOI. Detailed CVs of additional members should be provided.

5 The Contractor may perform Unit, Integration, and Systems Tests offsite; however, the official Systems Test and all User Acceptance Tests must be performed on-site using PIAC’s testing environment.

6 The Contractor must provide, by phase, the proposed number of personnel to be based on-site at PIAC’s premises, and space and other requirements to be provided by PIA during Implementation.

7

The Contractor will develop a system turnover plan which indicates the conditional criteria required to fully turn over the daily operation of the system to PIA technical staff. At a minimum, the turnover plan must include the state of readiness required for system turnover and all required documentation.

8 The Contractor’s implementation plan must take into consideration the business priority areas and applications.






9

System Performance: During system installation the Contractor will evaluate performance factors including, but not limited to, transaction volumes, response times, CPU utilization, and input / output activity. The Contractor will be responsible for tuning the application to meet acceptable response times.

10 Capacity Evaluation: The Contractor will conduct a Capacity Test will include stress and volume testing.

11

Project Management and Reporting: The Contractor is required to maintain a project plan covering its components of the project and each individual phase. The Contractor will be required to prepare and submit weekly progress reports to PIA on each component of the Project under which it is responsible.

12

Project Quality Management: In its proposal, the Contractor must describe its approach for assuring the quality of its components on this project. Contractor must also specify whether third party audit / quality assurance visits will be undertaken and who will bear the cost of these visits.

13

Acceptance Testing: PIA will conduct a rigorous acceptance test of the system. During this test, PIA will identify required modifications and document them through the problem resolution or change management processes (described below) as appropriate. The Contractor shall modify the system as required and provide new versions of modified components to PIA for testing. PIA will notify the Contractor in writing when it determines that the system is acceptable.

14

Problem Resolution: The Contractor and PIA will cooperate to resolve system problems found during acceptance testing and production use, including the warranty period. PIA will prioritize and report problems in a written format. The Contractor shall track these problems to closure and report their status upon request.

15

Change Management: PIA and Contractor will cooperate in managing changes to previously agreed upon system functional capabilities. PIA may identify potential functional changes; however, cost escalation will not be allowed under any circumstances.

16 Configuration Management: The Contractor shall manage version releases of all contract deliverables and certain other critical documents as determined by PIA.

17

The Bidder must assign a full-time Project Manager to manage this Project. His/her detailed CV including experience of managing MRO and other Projects, MRO Package Certification, if any, the number of MRO projects managed and the number of years on each project, etc. must be submitted along with the Proposal.

D2 TRAINING

2

As a part of the proposal, the Contractor must describe in detail its approach to meeting the training requirements for each audience. The description must include methods proposed to deliver both training and documentation. The Contractor should describe the general content of all training materials, training courses, and documentation proposed.

3

The Training Strategy should include a training solution to support the training of end users throughout PIA in the functionality of the various MRO and Add-on applications components.

The Contractor is required to develop materials for training users in central and remote offices.

The Contractor must provide material for training Technical Staff such as database administrators, system administrators, operators, and developers.

4 Cost of Foreign Training, if proposed, should be included in the Contractor’s Financial Proposal and include all expenses related to travel, accommodation, tuition fees and other incidentals.






D3 DATA MIGRATION

4 The Conversion Strategy must address, at a minimum, items a) to f)

5 Undertake to submit data Migration Plan, as per Section: D, D3-5

6 Ensure smooth transition, data cleansing & integrity, document all areas.

D4 DOCUMENTATION

1

As part of its Technical Proposal, the Contractor must describe the level and types of documentation that will be delivered. This documentation must cover each level of operation, for example: user, security administrator, database administrator, operator, developer, etc.

2 Two complete hardcopy sets of documentations for all Contractor supplied components for this Project must be furnished, in addition to softcopies.

3 The manuals should feature clear organization of content, easy to understand language, useful graphic presentations, and a thorough index and glossary.

4

These manuals must address the view of the system required by business unit staff (end users). It must contain sufficient information to enable the user to independently operate the system, troubleshoot simple problems, and correct problems.

5 In conjunction with the Users’ Manual, Quick Reference cards will be produced by the contractor, which will be an immediate aid to the user and quickly describe operations.

6

The Technical Manuals must address the view of the system required by developers, administrators and other technical personnel. It should provide an understanding of the application; data base design and file structures; relationships between programs, security; troubleshooting; special constraints; and other operational guidelines.

7 Copies of all licenses, warranties, maintenance agreements and similar materials for all Contractor delivered components of the project must be furnished separately.

8 Contractor must submit sample copies of all documents that it will prepare / deliver to PIA during the course of this project.

D5 WARRANTY AND MAINTENANCE SUPPORT

1

The Contractor will provide warranty services for a period of at least one year for software and a minimum of three years for hardware. The warranty will begin on PIA’s written final acceptance of the system. All warranty support services are to be rendered free of charge to PIA. Contractor will be responsible for all related costs during this period.

2

Separate and apart from the warranty support services, the Contractor shall provide Maintenance services for Applications, and DBMS beginning upon the end of the warranty services and extended upto three (3) years thereafter.

3

The Contractor must describe in detail in the Technical Proposal its User and Technical Support Plan for the warranty and maintenance periods, covering the resources, timing and procedures that will be available to provide this support.

4 The Contractor must specify the various categories of problems it will support and describe the severity levels of problems.

5 Details of the establishment of an effective “Hot Line Telephone and Support Desk” service should be provided.

6

PIA may require the Contractor to develop additional customized reports, screens, workflows, etc. during the maintenance and support period. Contractor must specify in its Technical Proposal a solution to accommodate PIA’s requirement. The Price Proposal must contain the pricing mechanism for additional report development / customization.

7

The Contractor must provide a list of clients in Pakistan and abroad for which MRO / M&E Maintenance Support is, or has been provided during the past three years. Details of modules supported should be included.



RFP Reference



Sub section Item

D6 VERSION AND UPGRADES

1

Contractor must ensure that training material / software / process documents are duly licensed for the purpose of implementation and use by PIA of the MRO / M&E. These are to be of latest version and Contractor must ensure up-gradation of all modules / material / process documents during the warranty period and as part of after-warranty maintenance support.

2

During the implementation and subsequent rollout Contractor would be responsible to arrange and provide free version upgrades of all components under its responsibility. Contractor must ensure that at the time of handing over the solution to PIA all components are of the latest release and that the total solution is certified by the Contractor for completeness.

F HARDWARE

1

The Contractor must evaluate and prepare an appropriate configuration to run the proposed MRO / M&E solution. PIA is looking for a high-availability solution including servers, clustering design, and disaster recovery recommendations besides maintenance / repair options needed for the associated infrastructure.

The response must address all items 1) to 17)



I3 BUSINESS INFORMATION AND APPLICATION NEEDS

RFP Reference



Sub section Item

D D7 Information Requirements of the management.

C / H4 Functional Information Requirements

1.0 Functional Requirement concerning Aircraft Engineering

2.0 Functional Requirements for Aircraft Induction and Phase out

3.0 Functional Requirements for Line Maintenance

4.0 Functional Requirements for Cabin Maintenance

5.0 Functional Requirements for Base Maintenance

6.0 Functional Requirements for Component Overhaul

7.0 Functional Requirements for Quality Assurance

8.0 Functional Requirements for Maintenance Operation Support Center

9.0 Functional Requirements for Business Development

10.0 Functional Requirements for Power Plant Overhaul

11.0 Functional Requirements for Tools and Equipment& Standards Labs

12.0 General Functional Requirements of the MRO / M&E System



I4 MRO / M&E PACKAGE REQUIREMENTS



& Page Section Sub section

Item

A A4 1. OVERVIEW OF SOLUTION REQUIREMENTS

A A4 2 GENERAL REQUIREMENTS

2.1 Common Characteristics

2.2 Integration

2.3 Configuration

2.4 Technology Interfaces

2.5 User Interface

2.6 Security & Authorization

2.7 Reporting / Enquiry

2.8 Data Analytic Tools

2.9 Communication

2.10 Flexibility

2.11 System Availability

2.12 Transaction Timing

2.13 Online Documentation and Training

2.14 Storage / Record Retrieval

2.15 System Security

A A4 3. TECHNOLOGY REQUIREMENTS

3.1 New Technology

3.2 Multiple Environments

3.3 System Performance

3.4 Archive and Purge

3.5 Recovery

3.6 Backup and Reorganization

3.7 Print Management

3.8 Fallback Solution

3.9 Ability for system and license updates


3.11 Server Hardware

3.12 System and Network Management Tools

3.13 Data Support

3.14 Authentication for accessing protected data & transactions

3.15 Web-enablement

3.16 Workflow

3.17 Others

Date post:	26-Mar-2018
Category:	Documents
Upload:	trinhthuan
View:	216 times
Download:	1 times