3 Section 3

Department of Schools, Ministry of Education
Project Title : The Supply, Delivery, Installation, Testing, Commissioning and

Maintenance of Schools Network Infrastructure for Government Primary, Secondary
and Religious Schools Ministry of Education, Brunei Darussalam (Phase I, II & III)
Project Ref : MOE/EGOV/DS/001-9/2004
TABLE OF CONTENTS
COMPOSITION OF TENDER.........................................................................................................2
SCHEDULE 1 – INFORMATION SUMMARY......................................................................................4
SCHEDULE 2 – SUB-CONTRACTS ................................................................................................5
SCHEDULE 3 – COMPANY’S BACKGROUND ..................................................................................6
SCHEDULE 4 – COMPANY’S TRACK RECORD...............................................................................7
SCHEDULE 5 – CONTRACTOR’S EMPLOYEES AND THEIR DUTIES..................................................16
SCHEDULE 6 – SOFTWARE.......................................................................................................24
SCHEDULE 7 – HARDWARE FACILITIES......................................................................................28
SCHEDULE 8 – SPECIFICATION..................................................................................................31
...........................................................................................................................................34
SCHEDULE 9 – PERFORMANCE CRITERIA..................................................................................34
SCHEDULE 10 – TECHNICAL PROPOSAL AND SYSTEM CONFIGURATION..........................................36
SCHEDULE 11 – PROPOSED APPROACH AND METHODOLOGY........................................................39
SCHEDULE 12 – IMPLEMENTATION PLAN...................................................................................45
SCHEDULE 13 – IMPLEMENTATION AND RELATED SERVICES.........................................................48
SCHEDULE 14 – INSTALLATION TESTS.......................................................................................53
SCHEDULE 15 – ACCEPTANCE TESTS.........................................................................................53
SCHEDULE 16 – DOCUMENTATION AND DELIVERABLES................................................................53
SCHEDULE 17 – TRAINING PLAN..............................................................................................57
SCHEDULE 18 – STATEMENT OF COMPLIANCE............................................................................64
SCHEDULE 19 – PRICE SUMMARY............................................................................................65
SCHEDULE 20 – TERMS OF PAYMENT........................................................................................67
Section 3 – Requirements Page 1

of 67
SECTION 3
REQUIREMENTS
COMPOSITION OF TENDER
The composition of the Technical Proposal, Price Proposal and Tenderer Information shall
be as follows:
(a) Information to be included in Price Proposal and Technical Proposal:
“Requirement Schedule”:
Requirement
Technical Proposal Price Proposal
Schedules
Schedule 1 All
Schedule 2 All
Schedule 3 All
Schedule 4 All
Schedule 5 All
Schedule 6 All except Table 6.1(a) Table 6.1(a)
Schedule 7 All except Table 7.1(a) Table 7.1(a)
Schedule 8 All
Schedule 9 All
Schedule 10 All
Schedule 11 All
Schedule 12 All
Schedule 13 All except Table 13.2 Table 13.2
Schedule 14 All
Schedule 15 All
Schedule 16 All

of 67
Requirement
Technical Proposal Price Proposal
Schedules
Schedule 17 All
Schedule 18 All
Schedule 19 All
Schedule 20 All

of 67
SCHEDULE 1 – INFORMATION SUMMARY
1.1 Tenderers shall provide in this Schedule the following information:
(a) Management summary
(b) List of all the companies (including Contractor and sub-contractor(s), if

any) involved in the provision of the services and items specified in this
tender, and the responsibility of each company
(c) Company profile (including Contractor and sub-contractor(s), if any)
(d) Years of experience (as of the Tender Closing Date) and skills of the
Contractor and sub-contractor(s) in:
• Developing and implementing IT projects; and
• Providing operations and maintenance services
(e) Description of the salient features and flexibility of the Hardware Facilities
and Software proposed, including:
• Overview
• Architecture
• Configuration
• Interoperability
(f) Status and support policy of each major product (e.g. how long each
product has been available in the market, the manufacturer, commitment
in terms of life cycle and in the case of software, the current version
number and the number of versions released in the last 24 months with
information summary for the proposed version)
(g) Other information which is considered relevant

of 67
SCHEDULE 2 – SUB-CONTRACTS
2.1 Tenderers shall complete Table 2.1 with information about all the companies
involved in the provision of the services and items specified in this tender. This
shall include details about the Contractor and each sub-contractor involved, as
well as their respective responsibilities.
2.2 Tenderers shall also indicate in Table 2.1 any alliance relationship established
with each sub-contractor. An alliance is defined as a formal and binding business
relationship between the allied parties.
Table 2.1 Responsibility Table

Alliance Relationship between
Contractor and Sub-contractor(s)
Alliance
Exists? Date
Company Name Responsibility (Y/N) Establishe Alliance
Description d Description
Contractor
Not Not Not Applicable

Applicable Applicable
Sub-contractor(s)

of 67
SCHEDULE 3 – COMPANY’S BACKGROUND
3.1 Each of the companies involved in this tender, including Contractor and sub-
contractor(s) (if any), shall provide its company profile including company
strengths, organisation structure and management background.

of 67
SCHEDULE 4 – COMPANY’S TRACK RECORD
4.1 Company Contribution
4.1.1 Tenderers shall complete Table 4.1, with information about the
contribution percentages of different companies (which can be the
Contractor, sub-contractor(s), or other manufacturer(s)) in the provision of
the following project services or items:
(a) Project Management Services

Tenderers shall list the company(ies) responsible for
the provision of Project Management Services.
Contribution percentage of each company shall be
provided based on the relevant number of mandays,
service price or cost, over total mandays, service
price or cost for Project Management Services.
(b) Implementation and Related Services

Tenderers shall list the company(ies) responsible for
the provision of Implementation and Related
Services. Contribution percentage of each company
shall be provided based on the relevant number of
mandays, service price or cost, over total mandays,
service price or cost for Implementation and Related
Services.
(c) Application Software

Tenderers shall list the manufacturer/developer(s) of
all the proposed application software item(s).
Contribution percentage of each
manufacturer/developer shall be provided based on
the relevant application software price/cost over total
application software price/cost.
(d) Database Software

all the proposed database software item(s).
Contribution percentage of each
the relevant database software price/cost over total
database software price/cost.
(e) Hardware and Operating System

all the proposed hardware and operating system
item(s). Contribution percentage of each

of 67
the relevant hardware or software price/cost over

total hardware and operating system price/cost.
4.1.2 The sum of contribution percentages across

different companies on a particular project service or
item must give a total of 100%.
Table 4.1 Contribution of Companies (in %)
Project Services or Items
ServicesOperations and Maintenance

ServicesImplementation and Related
Hardware and Operating System

Project Management Services
Application Software
Database Software
Ref.
No. Company Name
Contractor
Sub-contractors
Other Companies/ Manufacturers

(if not Contractor and sub-
of 67
contractors)
Total: 100% 100% 100% 100% 100% 100%

4.2 Program Management Experiences
4.2.1 Tenderers shall complete Table 4.2, with details of all the IT projects in the
recent 5 years as of the Tender Closing Date, that the Contractor was
responsible for overall programme management of the Implementation
and Related Services.
Table 4.2 Program Management Experiences
Name and Address Name and Version of Location where

Of Customer Main Application, System was
Brief Description implemented

of 67
4.3 Project Partnership Experiences
4.3.1 Tenderers shall complete Table 4.3, with details of all the IT projects in the
recent 5 years as of the Tender Closing Date, that:
(a) The Contractor has partnered with any of the proposed sub-
contractor(s) in this tender, in providing any of the following project
services or items for the listed projects:
(i) Implementation and Related Services
(ii) Operations and Maintenance Services
(iii) Application Software The types of partnership shall include:
• Partnership between Contractor and sub-contractor within the

same project in providing different services or items as listed
above.
• Partnership between the Contractor and sub-contractor within

the same project in providing the same service or item as listed
above.
(b) The Contractor itself was responsible for any two or more project
services or items mentioned above for the listed projects, although
without partnership with the proposed sub-contractor(s) in this tender.
4.3.2 Tenderers shall indicate the roles of the Contractor and sub-contractor(s)
for the listed projects in Table 4.3, by providing the companies’ reference
numbers as specified in Table 4.1.
4.3.3 Tenderers shall enter ‘N/A’ (not applicable) for the project service(s) or
item(s) in the listed project(s), that were responsible by parties other than
the Contractor or sub-contractor(s) in this tender.
Table 4.3 Project Partnership Experiences

Companies Responsible for
Maintenance Services
Implementation and
Related Services
Operations and
Project
Name & Address Completi
of Customer Project Description on Date
Section 3 – Requirements Page

10 of 67
4.4 Company Track Records
4.4.1 Tenderers shall provide a list of relevant track records in the tables as
listed below, for the companies that are named in Table 4.1.
Table 4.4 -- Project Management Services
Table 4.5 -- Implementation and Related Services
Table 4.6 -- Application Software
Table 4.7 -- Hardware and Operating System
4.4.2 Tenderers shall complete Tables 4.4 to 4.7 with track records as follows:
(a) The track records must be for with similar functions to the system
being tendered.
(b) The track records must be within recent 5 years as of the Tender
Closing Date.
(c) The company must have performed a similar role as in this tender
for the listed projects.
4.4.3 Tenderers shall indicate in Tables 4.4 to 4.7, the track records/ projects
that can be used as reference sites. Three (3) reference sites must be
provided for each company under a particular project service or item.
4.4.4 Tenderers shall assign a project reference number to the track records
provided. The same project reference number must be used if the same
project is referred to by different companies, or under different project
services or items.
4.4.5 General guidelines for completing Tables 4.4 to 4.7:
Column Heading Descriptions

Customer Type • Tenderers shall indicate whether the customer is a
Government or Quasi Government organisation.
• Please put a ‘Y’ under the appropriate category and
leave blank if the customer is neither a Government
nor a Quasi Government.
• A Quasi Government is defined as an organisation
which (1) is managed and controlled by Government;
or (2) has at least 50% shares being held by
Government.

11 of 67
Column Heading Descriptions

Project Scale • Tenderers shall indicate the scale of the project:
 Table 4.4 - in terms of total contract value (the
contract value of the overall project), and total
number of mandays.
 Table 4.5 – in terms of contract value of the
implementation project, and the total
implementation mandays.
 Table 4.6 – in terms of total/ annual contract value
of the service, and the number of users
supported.
Reference Site • Please mark a ‘Y’ for the projects/ track records that
can be used as reference sites.
• Tenderers shall provide at least three (3) reference
sites for each company under a particular project
service or item.
Project Reference • Please assign a project reference number for each
Number project/ track record.
• Tenderers shall note that the same project reference
number must be used if the same project is referred
to by different companies, or under different project
services or items.

12 of 67
Project Title : The Supply, Delivery, Installation, Testing, Commissioning and Maintenance of Schools Network Infrastructure for
Government Primary, Secondary and Religious Schools Ministry of Education, Brunei Darussalam (Phase I, II, & III)
Table 4.4 Company Track Records (Project Management Services)

Company Name
Customer Location
Project Project Timeframe
Type Scale
Where Total No. Project
Quasi Name and Version of Main System was of Project Completion Referenc Referenc
Name of Govt Govt. Application, Brief implemented Man-days Start Date Date e Site e
Customer . Description Number
Table 4.5 Company Track Records (Implementation and Related Services)

Company Name
Customer Project
Type Location Scale Project Timeframe
where No. of Project
Quasi Name and Version of Main System was Project Completio Referenc Referenc
Name of Govt Govt. Application, Brief implemented Man-days Start Date n Date e Site e
Customer . Description Number
Section 3 - Requirements Page 13 of

67
Table 4.6 Company Track Records (Application Software)

Company Name
Customer
Type
Quas Project
Name and Version of Main Number
Govt i Location where System Referenc
Name of Customer Application, Brief of Reference Site
. Govt was implemented e
Description Users
. Number
Table 4.7 Company Track Records (Hardware and Operating System)

Company Name
Customer
Type
Q Name and Version of Main Project
Location Number
uasi Application and Hardware/ Referenc
Name of Customer Govt. where System was of Reference Site
Govt Operating System, e
implemented Users
. Brief Description Number

67
Department of Information and Communications Technology, Ministry of Education
Maintenance of Departmental Network Infrastructure in Ministry of
Education, Brunei Darussalam
Project Ref. : MOE/EGOV/ICT/001-5/2004
4.5 Reference Sites
4.5.1 For each project/ track record that is indicated as a reference site in Tables
4.4 to 4.7, Tenderers shall provide contact details in Table 4.10 below.
Table 4.10 Reference Site Contact Details

Relevant Project Services or
Items
ServicesOperations and Maintenance
Hardware and Operating System

Project Management Services
Implementation and Related
Database Software
Contact
Services
Project Number,
Referenc Company Fax
Contact
e Name and Number
Person Title
Number Address and E-mail
Address
4.5.2 The Ministry of Education shall treat all the information submitted under
this schedule in strict confidence.
4.5.3 The Ministry of Education reserves the right to contact the reference sites
for tender assessment purposes.
4.5.4 Tenderers may also be requested to make arrangements for the Ministry
of Education Representative to visit the reference sites. If such site visits
are required to be conducted overseas, Tenderers shall render all
assistance in arranging the site visits but the Ministry of Education shall
bear the costs of transportation, subsistence and accommodation for the
Ministry’s Representative for such visits.
Section 3 – Requirements Page 15 of

67
Maintenance of Departmental Network Infrastructure in Ministry of
Education, Brunei Darussalam
SCHEDULE 5 – CONTRACTOR’S EMPLOYEES AND THEIR DUTIES
5.1 Project Team Structure
5.1.1 Tenderers shall provide a clear organisation chart to show the project
management structure including the escalation procedures.
5.1.2 Tenderers shall provide a clear organisation chart of the Implementation

Team. Descriptions shall be provided to show how the Implementation
Team address the functional and technical requirements and how to
discharge the Implementation and Related Services stated in Section 2.
5.2 Project Role and Staffing Arrangement
5.2.1 Tenderers shall provide, in Table 5.1, the following information in respect
of each of their project staff designated:-
(a) Name;
(b) Company to which the project staff belongs;
(c) Proposed role in this project;
(d) Terms of Service;
(e) Language (Spoken); and
(f) Deployment of staff for this project, including information about
estimated effort and estimated schedule of work.

67
Table 5.1 Project Role and Staffing Arrangement
Proposed Project Role Terms of Service Schedule of Work

On-site/
Languag Team/ Staff Full- Local off- Start End
Name Company e IC/ Sub-Team Category time/ site/ Date Date
(Spoken Passport Part- Overseas
) No. time

67
and Religious Schools Ministry of Education, Brunei Darussalam (Phase I, II, & III)
5.2.3 Tenderers shall propose and present arrangements on the provision of staff and/
or sub-contractor establishment.
5.3 Previous Experience of Project Staff
5.3.1 Tenderers shall provide in Table 5.2 the following information in respect of
the previous experience of each of their key project staff designated for
the project:
(a) Name;
(b) Academic qualification;
(c) Years of post-qualification IT experience;
(d) Number of relevant project experience; and
(e) Years of experience in relevant subject areas.
5.3.2 Tenderers shall attach with this Schedule the Curriculum Vitae of each
proposed staff for the Project Team. Tenderers are required to cross-
reference to the Curriculum Vitae when completing Tables 5.2 to 5.5.

67
Project Title : The Supply, Delivery, Installation, Testing, Commissioning and Maintenance of Departmental Network Infrastructure in
Ministry of Education, Brunei Darussalam
Table 5.2 Project Staff Profile
Number of Relevant
Project Experience in Years of Experience in
recent 10 Years
(Team Member)Assigned Subject Area

Operations and Maintenance Services
Implementation and Related Services
(Team Leader)Assigned Subject Area
Proposed Application Software

Project Management
No. of Years
of Post-
Academic Qualification
Package
Name Qualification IT Experience No. Xref
1 7

67
Project Title : The Supply, Delivery, Installation, Testing, Commissioning and Maintenance of Departmental Network Infrastructure in
Ministry of Education, Brunei Darussalam
Note: 1) For Functional Specialist, this should be “Number of Years of Post-Qualification Functional Experience”
2) Xref – Cross-reference to the experience provided in Curriculum Vitae

67
Maintenance of Schools Network Infrastructure for Government Primary,
Secondary and Religious Schools Ministry of Education, Brunei Darussalam
(Phase I, II & III)
5.3.3 Tenderers shall submit a list of system implementation projects in Table

5.3 that the proposed Project Manager(s) of this tender has engaged in
with a similar role (as of the Tender Closing Date). Tenderers shall provide
cross-references to the experiences in Curriculum Vitae.
Please indicate whether the proposed Overall Implementation

Methodology, as specified in Schedule 11 – “Proposed Approach And
Methodology”, was adopted in the projects by putting a ‘Y’ under column
“Used Proposed Overall Impl. Methodology” where appropriate.
Table 5.3 List of projects that the proposed Project Manager(s) has engaged in
Brief Scale of Project Period

Project of
Name(s) of Description No. of Time
Proposed Name (e.g. name No. Total Team Engag Used
Project and and nature of Project Memb ed in Proposed
Manager(s) Address of Users Manday ers at the Overall Xref
Impl.
of application s Peak Project
Methodolog
Client ) y

67
(Phase I, II & III)

5.4 that the proposed Functional Specialist(s) of this tender has engaged
in with a similar role (as of the Tender Closing Date). Tenderers shall
provide cross-references to the experiences in Curriculum Vitae.

“Used Proposed Overall Impl. Methodology” where appropriate.
Table 5.4 List of projects that the proposed Functional Specialist(s) has
engaged in
Brief Scale of Project

Project
Name(s) of No. of Used
Description Period of
Proposed Name No. Total Team Propos
(e.g. name Time Engaged in
Functional and of Project Member ed Xref
and nature the
Management Address Users Mandays s at Peak Overall
of Project
Specialist(s) of Client Impl.
application
Method
)
ology

67
(Phase I, II & III)

5.5 that the proposed Team Leader(s) of this tender has engaged in with a
similar role (as of the Tender Closing Date). Tenderers shall provide cross-
references to the experiences in Curriculum Vitae.

“Used Proposed Overall Implementation Methodology” where appropriate.
Table 5.5 List of projects that the proposed Team Leader(s) has engaged in
Brief Project Scale of Project Period of

Description No. of Time
Name(s) of Name (e.g. name No. Total Team Engaged Used
Proposed and and nature of Project Member in the Proposed
Team Address of Users Mandays s at Peak Project Overall Impl. Xref
Leader(s) of Client application) Methodology

67
(Phase I, II & III)
SCHEDULE 6 – SOFTWARE
6.1 Application and Database Software Items
6.1.1 Tenderers shall propose in this part all necessary software items that will
be:
• Licensed to the Ministry of Education
• Supplied and implemented by the Contractor
These must include Application Software and Database Software. Details

of the proposed software items, including product description, version
number and proposed quantity etc., shall be provided.
6.1.2 The quantity of each software item shall be proposed based on a

justifiable basis. Tenderers shall propose the quantity of licences required,
with reference to the volumes and figures stipulated in Annex 2.2 or any
justifiable basis as deemed appropriate.
The licences must be sufficient to support the maximum number of

concurrent users of the System. Sufficient development licences shall
also be included for implementation, maintenance and support of the
System.
6.1.3 Tenderers shall complete Table 6.1(a) and Table 6.1(b) with all the
software items, that will be supplied by the Contractor and licensed to the
Ministry of Education, in performing the functions specified in Section 2
(including all the essential functions and desirable functions that the
Contractor is committed to offer).
6.1.4 Tenderers shall complete Table 6.1(a) and Table 6.1(b) with same contents
(other than cost-related information), ensuring the two tables correspond
with each other.
6.1.5 Tenderers shall:
(a) Enter ‘N/C’ (i.e. no charge) where applicable

(b) Charge annual licence fees and annual maintenance charge
(c) Include all necessary and related components for the installation of
the software

67
Project Title : The Supply, Delivery, Installation, Testing, Commissioning and Maintenance of Schools Network
Infrastructure for Government Primary, Secondary and Religious Schools Ministry of Education, Brunei Darussalam
(Phase I, II & III)
Table 6.1(a) Application and Database Software Items
Year 1 Year 2 Year 3 Year 4 Year 5 Total

I Product/
tem
No. Version Description Manufact Qty License Mainte Licen Maint Licen Maint Licen Mainten Licen Mainte Lice Mainte
No. urer Fee nance se enanc se enanc se ance se nance nce nance
Charge Fee e Fee e Fee Charge Fee Charge Fee Charge
Charg Charg
e e
Sub-total:
Total:
Table 6.1(b) Application and Database Software Items
Item Product/
No. Version No. Description Manufacturer Quantity

67
(Phase I, II & III)

67
(Phase I, II & III)
6.2 Utilities and Other Software Items
6.2.1 Tenderers shall propose in this part all necessary utilities and other
software items that will be provided, utilised, and/or implemented by the
Contractor at Contractor’s own cost, and shall include, but not be limited
to:
• Utilities and other software running on each proposed hardware

facilities (e.g. operating system, firewall, etc.);
• Software for performing Implementation and Related Services, for

example, software items required for developing interfaces,
performing data conversion and migration exercise, and developing
and effecting the interim process during Transitional Operations; and
• Software for performing Operations and Maintenance Services, for

example, help desk software.
Details of the proposed software items, including product description,

version number and proposed quantity etc., shall be provided.
6.2.2 The quantity of each software item shall be proposed based on a

justifiable basis. Tenderers shall propose a sufficient quantity of licences
required, with reference to the volumes and figures stipulated in Section
2, or any justifiable basis as deemed appropriate.
6.2.3 Tenderers shall complete Table 6.2 with all the utilities and other software
items that will be provided by the Contractor, in performing the functions
and services, in accordance with the requirements specified in the Section
2.
Table 6.2 Utilities and Other Software Items
Item Product Name/

No. Version No. Description Manufacturer Quantity

67
(Phase I, II & III)
SCHEDULE 7 – HARDWARE FACILITIES
7.1 Contractor Provided Hardware Facilities
7.1.1 Tenderers shall submit, in Table 7.1, details of the Contractor provided
hardware facilities which are required for the implementation, interface
development, data conversion and migration, interim process
development, network setup, operations and transitional operations and
disaster recovery of the System as specified in Section 2.
7.1.2 Tenderers shall submit, in Schedule 6 – “Software”, the required utilities

and other software running on each proposed hardware facilities item.
7.1.3 Tenderers shall complete Table 7.1(a) and Table 7.1(b) with same contents
(other than cost-related information), ensuring the two tables correspond
with each other.

67
(Phase I, II & III)
Table 7.1(a) Contractor Provided Hardware Facilities

Year 1 Year 2 Year 3 Year 4 Year 5 Total
Item Manufactur Model / Softwar Descriptio Locatio Qty
er e1
n 2
n
No. Part No.Referen Purcha Maintena Purch Mainten Purch Mainten Purch Maintenan Purch Maintena Purch Mainten
ce to se Price nce ase ance ase ance ase ce Charge ase nce ase ance
Table Charge Price Charge Price Charge Price Price Charge Price Charge
6.2
Sub-total:
Total:
Table 7.1(b) Contractor Provided Hardware Facilities
Item Model / Software1
No. Manufacturer Part No. Reference to Description Location2 Qty
Table 6.2
Note :
(1) Tenderers shall list all utilities and other software to be installed on the proposed hardware facilities items in Schedule 6 –
“Software”.
(2) Tenderers shall indicate which Contractor’s locations (e.g. primary data centre, disaster recovery data centre, etc.) the hardware facilities
67
(Phase I, II & III)
to be placed.

67
(Phase I, II & III)
SCHEDULE 8 – SPECIFICATION
8.1 Tenderers shall complete this Schedule by entering all technical information and
particulars including name of product, country of origin, name of
developer/substantial place of manufacturing, address of developer/manufacturer,
system name and version/release number of the proposed hardware facilities,
software and customisation on software which corresponds to the Project
Specification.
8.2 Hardware Facilities Specification
8.2.1 Tenderers shall provide specifications of the proposed hardware facilities

to meet the requirements as specified in Section 2 Specification.
Tenderers shall highlight the following information in the corresponding
specifications:
(a) Servers
• Additional functions and features (e.g. fault event log, built-in

diagnosis tool, automatic function turn on/off, etc.)
• Compatibility with the proposed software
• Number of authorised local support companies and the estimated
total number of local technical support staff members for the
product
• Please also provide the name of these companies
(b) Backup facilities
• The media support

• Maximum uncompressed/compressed capacity
• Backup rate for uncompressed/compressed data
(c) Data Storage
• Maximum data storage capacity

• Maximum throughput
• Fault tolerant support
• Scalability method in response to increased workload

67
(Phase I, II & III)
• Number of authorised local support companies and the estimated

total number of local technical support staff members for the
product

67
(Phase I, II & III)
8.3 Software Specification
8.3.1 Tenderers shall provide specifications of the proposed software to meet

the requirements as specified in the Specification. Tenderers shall
highlight the following information in the corresponding specifications:
(a) Application Software
Please complete Table 8.1 with specifications of all the proposed

application software items.
(b) Database Software
• Functions and features supported (e.g. cluster support, distributed
data support, etc.)
• Maximum data volume supported
(c) Utilities and Other Software

(i) Operating System Software
• Functions and features supported
• Scalability method in response to increased workload
(ii) Other Software

• Functions and features supported
Table 8.1 Application Software Modules
Item Version/Releas Software / Software / Software

No. e Software Module Module Description
Name

67
(Phase I, II & III)
8.4 Custom Programs Specification
8.4.1 Tenderers shall complete Table 8.2, by providing specifications of any

customisations on the application software for the System to meet the
requirements as specified in Section 2.
Table 8.2 Custom Programs Specification
I Softwar Software X-ref to Elaboration New Estimated

tem e/ / requirement of the Progra customisati
No. Softwar Software s in the customisati m (Y/N) on effort
e Module Section 2 to on of the ? (Mandays)
Module Descripti be Software /
Name on supported Software
by Module
customisati
on of the
Software /
Software
Module
SCHEDULE 9 – PERFORMANCE CRITERIA
9.1 Tenderers shall commit that if the Contract is awarded, they shall provide support
the workload under their proposed sizing model with the service levels specified
in the relevant Contract Schedules and Section 2.
9.2 Tenderers shall include all recommended configurations for each resource for the
implementation of the System. The resource should include both Contractor
provided and Ministry of Education provided resources.
9.3 Tenderers shall provide the information of the minimum and recommended
configurations of Ministry of Education provided user workstations for the

67
(Phase I, II & III)
implementation of the System.
9.4 Tenderers shall provide the information of the minimum and recommended
network bandwidths for the Ministry of Education network for the
implementation of the System.

67
(Phase I, II & III)
SCHEDULE 10 – TECHNICAL PROPOSAL AND SYSTEM CONFIGURATION
10.1 Tenderers shall provide in this Schedule a technical proposal describing the
proposed architecture and configuration for the First Rollout and Second
Rollout of the System.
10.2 The technical proposal shall cover, but not be limited to, the following items:
(a) Overall Design
 Describe the design philosophy of the proposed System.
 Provide comprehensive system and network diagram(s) showing all

proposed system and network equipment.
 Explain in detail how the System meet or exceed the requirements set
out in the Specifications Section.
 Explain the benefits of adopting the proposed solutions.
 Highlight any limitations or constraints of the System.
 Describe how the major logical components (e.g. workflow, security,

administration, backup/recovery, archiving, log recording/audit trail,
monitoring, contingency plan, disaster recovery, high availability,
availability, interface, etc.) are handled by the system architecture
(e.g. server, database, workstation, network, etc.).
 List all features provided by the System with descriptions of the

functions and operations.
 Describe what maintenance arrangement is required for the System.
(b) Application Software
 Provide a description of the salient features and flexibility of the

proposed application software.
 Describe the functionality of each application module employed for

the System operation.
(c) Database
 Provide a description of the features and flexibility of the proposed

database software.

67
(Phase I, II & III)
 Provide information of the compatibility between the database and

application software.
 Provide the performance and reliability features of the database under

the proposed System set up.
 Describe any value added features such as clustering support,

distributed data store, etc. are applied.
(d) Server
 Describe how the System service accessibility level can be achieved

with the proposed server configurations.
 Provide information on the server scalability in response to the

increased/decreased workload.
(e) Backup
 Describe the backup approach to be implemented with the proposed

backup facilities.
(f) Security
 Describe in detail the security technologies and solutions

implemented.
 Describe in detail the system security arrangement to ensure the

System is well protected from malicious attacks.
 Provide detail information on the system security control such as

granularity of security control, number of authorisation level support,
security technologies employed, variety of security features, etc.
 Explain the digital certificate technology, architecture design and

corresponding implementation.
(g) System Environments
 Describe the set up of the five system environments which include

Production, Development, Testing, Training and Disaster Recovery
Environments.
 Describe, if any, the data exchange, interconnectivity, switch over

arrangements among the five Environments.
(h) Others

67
(Phase I, II & III)
 Tenderers shall also provide other information which is considered

relevant.

67
(Phase I, II & III)
SCHEDULE 11 – PROPOSED APPROACH AND METHODOLOGY
11.1 Tenderers shall give a description on the proposed approach, methodology or

any associated tools adopted for implementation management and control of
this project including but not limited to the following services:
(a) Overall implementation (Paragraph 11.2)
(b) Project management (Paragraph 11.3)
(c) Quality management and assurance (Paragraph 11.4)
(d) System analysis and design (Paragraph 11.5)
(e) Business process re-engineering (Paragraph 11.6)
(f) Interface design and development (with other systems) (Paragraph 11.7)
(g) Interim processes design and development (during transitional

operations) (Paragraph 11.8)
(h) Data conversion and migration (Paragraph 11.9)
(i) Change management (Paragraph 11.10)
(j) Optional (If Required) Operations and Maintenance Services (Paragraph

11.11)
(k) Optional (if Required) Relocation of hardware and Software from

temporary location to the permanent Location (Paragraph 11.12)
11.2 Overall Implementation
11.2.1 Tenderers shall provide detailed information on the overall

methodology and approach to be adopted in implementation and
related services as specified in this tender. This should include, but
not be limited to:
(a) where appropriate, the name of the methodology shall be

indicated. Tenderers shall also provide background descriptions of
the methodology, including the source of the methodology (e.g. is
the methodology defined by an international organisation and is
well adopted in the industry, or is it a knowledge asset of the

67
(Phase I, II & III)
Contractor or any sub-contractor), year of first introduction and

adoption, etc;
(b) the approach, steps and procedures to ensure the integration of

different services; and
(c) an explanation on the linkage between this proposed methodology

and the Implementation Plan.
11.3 Project Management
11.3.1 Tenderers shall describe the detailed methodology and approach to be

adopted in this project for project management. This should include, but
not be limited to:

adoption, extent of use of the methodology on management
system projects in other government or quasi government, etc;
(b) the approach in controlling the project implementation processes;
(c) the approach in project planning, resource estimation and

management;
(d) the reporting and escalation procedures, including the

responsibilities involved;
(e) the methodology in delivering project products in good quality and

performance; and
(f) all associated procedures for the proper management of project

issues, project risks, etc.
11.4 Quality Management and Assurance
11.4.1 Tenderers shall describe the detailed methodology and approach to be

adopted in this project for quality management and assurance. This
should include, but not be limited to:

67
(Phase I, II & III)

adoption, extent of use of the methodology on management
system projects in other government or quasi government, etc;
(b) the approach for version / release control;
(c) the approach for configuration management;
(d) the approach for quality management and assessments;
(e) the acceptance procedures of deliverables such as programs,

database, documentation, etc;
(f) the standards and procedures to be used in the project; and
(g) the quality assurance procedures recommended to ensure the

quality of deliverables.
11.5 System Analysis and Design
11.5.1 Tenderers shall describe the detailed methodology and approach for
system analysis and design (SA&D), including but not limited to:
indicated. Tenderers shall provide background descriptions of the
methodology, including the source of the methodology (e.g. is the
methodology defined by an international organisation and is well
adopted in the industry, or is it a knowledge asset of the Contractor
or any sub-contractor), year of first introduction and adoption,
extent of use of the methodology on management system projects
in other government or quasi government, etc;
(b) the steps, procedures and deliverables associated to system

analysis and design;
(c) the approach in ensuring proper control and management on the

system design; and
(d) the approach in ensuring the alignment and integration between

SA&D and business process re-engineering.
11.6 Business Process Re-engineering

67
(Phase I, II & III)
11.6.1 Tenderers shall describe the detailed methodology and approach in

conducting business process re-engineering, including but not limited to:
(a) the steps, procedures and deliverables associated to business
process re-engineering;
(b) the approach for defining the scope;
(c) the approach for incorporating improvements into processes;
(d) the approach for estimating benefits of the re-engineering

processes;
(e) the approach for implementing the new processes and realising the
benefits; and
(f) the approach for assessing benefits realisation.
11.7 Interface Design and Development (with other systems)
11.7.1 Tenderers shall describe the detailed methodology approach for system
interfaces, including but not limited to:
(a) the approach and methodology in designing, developing and

implementing the System interfaces;
(b) the technology to be employed for the System interfaces; and
(c) the approach and methodology in ensuring the quality and security
of the System interfaces.
11.8 Interim Processes Design and Development (during Transitional

Operations)
ensuring smooth operations during the transitional period between
Release 1 and Release 3. This should include, but not be limited to:
(a) the approach in assessing the scope of interim process

requirements;
(b) the approach in planning, designing and developing interim

processes;
(c) the approach in ensuring readiness for transitional operations

before Release 1; and
(d) the approach in ensuring a smooth changeover from transitional

67
(Phase I, II & III)
operations to full operations (that is, after Release 3).
11.9 Data Conversion and Migration
11.9.1 Tenderers shall describe the detailed methodology and approach for data
conversion and migration, including but not limited to:
(a) the approach including data capture procedures and verification

scheme, timetable and initial plan for migration showing all major
activities, tasks, responsible parties, tools and methodology that
shall be used, and the associated deliverables during the data
conversion and migration exercise;
(b) the approach and methodology in ensuring quality and security of

the data conversion and migration exercise; and
(c) the information required from relevant parties in order to meet the
requirements specified in the “Implementation Plan”.
11.10 Change Management
11.10.1 Tenderers shall describe the detailed methodology and approach

for performing change management, including but not limited to:
(a) the steps, procedures and deliverables associated to change

management;
(b) the approach for assessing change management requirements;
(c) the approach in assessing and ensuring change readiness of

different level of users; and
(d) recommended types of change management activities, the

approach in planning and conducting these activities, and any
proven success based on Tenderers’ previous project experiences.
11.11 Optional (If Required) Operations and Maintenance Services
performing operations and maintenance services, including but not
limited to:
(a) the steps, procedures and deliverables associated to operations

and maintenance services;
(b) the approach for operations and maintenance planning, resource

67
(Phase I, II & III)
estimation and management;
(c) the reporting and escalation procedures, including the

responsibilities involved;
(d) the approach and methodology in ensuring quality of the

operations and maintenance services;
(e) all associated procedures for the proper operations and

maintenance of software/hardware related issues, risks etc.
11.12 Optional (If Required) Relocation of hardware and software from

temporary location to permanent location
11.12.1 Tenderers shall describe the detailed methodology and

approach for performing the relocation of hardware and software
from the temporary location to the permanent location, including
but not limited to:
(a) the steps and procedures and deliverables associated to the

relocation of hardware and software from the temporary
location to the permanent location.

67
(Phase I, II & III)
SCHEDULE 12 – IMPLEMENTATION PLAN
12.1 Tenderers shall show the proposed the implementation plan in Table 12.1.
Tenderers shall propose the appropriate activities and deliverables with reference
to Section 2 and shall include any other recommended activities and deliverables
in the table. Tenderers shall provide detailed breakdown on each implementation
service and activity:
(a) For the implementation service about data centre facilities and
management during implementation, Tenderers shall provide detailed
segregation between one-time set-up/ implementation tasks (e.g. set up
system environments), and recurrent management/ support tasks (e.g.
regular backup of data);
(b) Tenderers shall provide for each task, where appropriate, the measurement
metrics (e.g., number of programs) that can be used to objectively track the
progress of specific tasks; and
(c) Tenderers shall indicate the Critical Path and task dependencies.

67
(Phase I, II & III)
Table 12.1 Implementation Plan
Tentative Estimated Effort

Timeframe (Mandays)
(Date)
Others Measurem
Major Activities/ Tasks Start End Contractor Govt. (Pls. ent Deliverables
Specify) Metrics
Total:

67
(Phase I, II & III)
Note: (i) 1 Manday = 8 hours; 1 Man-month = 22.5 Mandays.

67
(Phase I, II & III)
SCHEDULE 13 – IMPLEMENTATION AND RELATED SERVICES
13.1 Implementation and Related Services to be provided by the Contractor
13.1.1 The Contractor shall provide the following Implementation and Related
Services, with details stipulated in Specifications sub-section 14 –
“Implementation and Related Services”.
(a) Project management
(including multi-vendor co-ordination)
(b) System implementation/ integration services
• Business process re-engineering
• System analysis and design
• System installation and installation test
• System configuration
• Customisation and testing services
• Integration of hardware, software and customisations
• Interface with other systems
• Service support at different testing stages
• System software upgrade during implementation
• System performance tuning
• Interim processes development
(c) Disaster Recovery Centre Integration
• Integration to Ministry of Finance EG Centre
• Purchase and locate related Hardware at Ministry of Finance EG

Centre
• Disaster recovery planning and drill

67
(Phase I, II & III)
(d) Infrastructure assessment and implementation
(e) System conversion and rollout services
• Data conversion and migration
• System performance verification
(f) Change management services
• Training plan and development
• Other change management initiatives
(g) Post-implementation review
13.2 Implementation and Related Services Charges – Excluding Data Centre

Facilities and Management during Implementation (if any)
13.2.1 Tenderers shall fill in Table 13.1 for the above-said Implementation and
Related Services of this with information about detailed implementation
tasks and Mandays breakdown by Staff Categories.
13.2.2 Tenderers shall include, in Table 13.1 the effort in the design,
development, testing and implementation of interim processes.
13.2.3 Tenderers shall ensure that the Implementation and Related Services, as
well as the effort specified in this Schedule correspond with the tasks and
effort provided in Contract Schedule 12 – “Implementation Plan”.
13.2.5 Tenderers shall enter ‘N/C’ (i.e. no charge) where applicable.

67
(Phase I, II & III)
Table 13.1 Implementation and Related Services to be provided by the Contractor during Implementation
Estimated Effort (Mandays) Total
Item Description of Others
No. Implementation and Related Services PM DPM FS TL SA A QAS (Pls. Mandays
Specify)
1 Project Management (Including Multi-vendor co-
ordination)
2 System implementation/integration services
2.1 Business process re-engineering
2.2 System analysis and design
2.3 System installation and installation test
2.4 System configuration
2.5 Customisation and testing services
2.6 Integration of hardware, software and
customisations
2.7 Interface with other systems
2.8 Service support at different testing stages
2.9 System software upgrade during implementation
2.10 System performance tuning
2.11 Interim processes development
3 Disaster Recovery Integration Centre
3.1 Integration to Ministry of Finance EG Centre
3.2 Purchase and locate related hardware at MOF EG
Centre services
3.3 Disaster recovery planning and drill
4 Infrastructure assessment and implementation
5 System conversion and rollout services
5.1 Data centre arrangement
5.2 Data conversion and migration
5.3 System performance verification
6 Change management services
6.1 Training plan and development

67
(Phase I, II & III)
6.2 Other change management initiatives

7 Post-implementation review
8 Initial Application Management (Refer Section 2 –
20.1)
Total:
Note: PM – Project Manager; DPM – Deputy Project Manager; FS – Functional Specialist; TL – Team Leader; SA – System Analyst (or
equivalent); A – Analyst/ Programmer (or equivalent); QAS – Quality Assurance Specialist
13.2.6 Tenderers shall fill in Table 13.2 to provide the daily rates for any additional services required for Ongoing
Application Management or other related services as outlined in Specifications sub-section 20.2.2.
Table 13.2 Staff Daily Rate
Staff Category Daily Rate
Project Manager
Deputy Project Manager
Functional Specialist
Team Leader
System Analyst (or

equivalent)
Analyst/programmer (or
equivalent)

67
(Phase I, II & III)
Quality Assurance
Specialist

67
(Phase I, II & III)
SCHEDULE 14 – INSTALLATION TESTS
14.1 Tenderers are required to state in this Schedule the Installation

Tests to be performed (as specified in Specifications sub-section 15 –
“Delivery and Installation”).
14.2 Tenderers are required to propose the test approach and the test
tools (if any) for conducting the Installation Tests.
SCHEDULE 15 – ACCEPTANCE TESTS

15.1 Tenderers shall state in this Schedule the Acceptance Tests (as specified in
Specifications sub-section 16 – “Acceptance Testing”) to be performed
including System tests, User Acceptance Tests and Performance Tests.
15.2 Tenderers shall propose the test approach and the test tools for conducting
the Acceptance Tests in meeting the workload, performance, and other
requirements of the System, including but not limited to data conversion and
migration, and system interface.
SCHEDULE 16 – DOCUMENTATION AND DELIVERABLES
16.1 General
16.1.1 Tenderers shall propose a complete list of documentation that will be

provided, including all the mandatory documents specified in Section
2. Tenderers are welcome to recommend other types of
documentation or additional documents that are suitable for this
project.
16.2 Software
16.2.1 The Contractor shall produce all necessary documentation for the
Application Software, Database Software and Utilities and Other Software
as proposed in Schedule 6 – “Software”.
Table 16.1 Software Documentation
No. of Copies
Softcopy
Ref. Deliverable (D)/ (Pls specify
No. Description Ref Material ® medium) Hardcopy

67 Page 53 of
67
(Phase I, II & III)
16.3 Hardware Facilities
16.3.1 The Contractor shall produce all necessary documentation for all
Hardware Facilities as specified in Schedule 7 –“Hardware Facilities”
during implementation.
Table 16.2 Hardware Facilities Documentation
No. of Copies
Softcopy
Ref. Deliverable (D)/ (Pls specify
No. Description Ref Material ® medium) Hardcopy

67 Page 54 of
67
(Phase I, II & III)
16.4 Implementation and Related Services
16.4.1 The Contractor shall deliver all relevant materials and documentation for
the provision of Implementation and Related Services (as specified in
Specification Specifications sub-section 13 – “Implementation and Related
Services”) as Project Deliverables. These must include, but not be limited
to the key deliverables specified in Specifications sub-section 19 –
“Documentation and Deliverables”.
Table 16.3 Implementation and Related Services Documentation
No. of Copies
Softcopy
Ref. (Pls specify
No. Description medium) Hardcopy
16.5 Operations and Maintenance (O&M) Services
16.5.1 The Contractor shall deliver all relevant materials and documentation for
the provision of O&M Services (as specified in Specification sub-section 20
– “Operations and Maintenance Services”) as Project Deliverables. These
must include, but not be limited to the key deliverables specified in
Specifications sub-section 19 – “Documentation and Deliverables”.
Table 16.4 Operations and Maintenance Services Documentation
No. of Copies
Softcopy
Ref. (Pls specify
No. Description medium) Hardcopy

67 Page 55 of
67
(Phase I, II & III)
16.6 Others
16.6.1 Tenderers are welcome to recommend other types of documents that are
suitable for this project.
Table 16.5 Other Documentation
No. of Copies
Softcopy
R Deliverable (D)/ (Pls specify
ef. Description Ref Material ® medium) Hardcopy
No.

67 Page 56 of
67
(Phase I, II & III)
SCHEDULE 17 – TRAINING PLAN
17.1 Training Plan and Approach
17.1.1 Tenderers shall describe the training plan and approach, covering all
necessary training courses including touch-base training, end-user
operation training, as well as other proposed training courses. These shall
include, but not be limited to the following:
(a) Overall training methodology and approach, for example, training

recommendations so that end-user operation training can be
effectively rolled out within the planned timeframe
(b) Detailed approach of different courses, for example:

• Types of learning modes (e.g. classroom, presentation, hands-on
computer assisted training)
• Types of delivery aids (e.g. presentation slides)
• Types of course materials
(c) Proposed training approach for new users in the future after rollouts
(e.g. self-learning training materials vs. instructor-led courses)
17.2 Training Resources and Facilities
17.2.1 Tenderers shall describe in this Schedule their training resources and
facilities, including the structure of their local training centres and types of
training offered in these centres.
17.3 Training Courses to be Provided by Contractor
17.3.1 Tenderers shall propose in this Schedule all necessary training courses to
be provided and conducted by the Contractor, which shall include, but not
be limited to:
(a) Touch-base training
The Contractor shall conduct touch-base training for all project team
members and key end users participating in the project.
(b) End-user operation training
The Contractor shall provide end-user operation training for all users.
(c) Others (if any)

67 Page 57 of
67
(Phase I, II & III)
17.3.2 The proposed training schedule shall be in line with the detailed
implementation plan provided in Schedule 13 – “Implementation Plan”.
17.3.3 All the training courses shall be conducted primarily in English with key
support materials and job aids in Malay.
17.3.4 The proposed training fee shall include all charges only for the delivery of
training courses. The effort and cost required in training plan and
development services, for example, development of training plans and
materials, design of training evaluation mechanism, etc., shall be
provided in Schedule 13 – “Implementation and Related Services”.
17.3.5 Tenderers shall complete Table 17.1 and Table 17.2
17.3.6 General Guidelines for completing Table 17.1 and Table 17.2:
Column
Descriptions
Heading
Course Title The title of the course, which shall be clear and self-
explanatory for the <Government’s> understanding. Where
necessary, brief descriptions shall be included.
Format Classroom, self-study, audio/visual, computer assisted,

others (please specify).
Number of The number of sessions that trainees need to attend in order

Sessions per to complete the course.
Course
Total Duration Total number of hours that trainees need to attend in order
(Hours) per to complete the course.
Course
Proposed More than one class shall be proposed for a particular

Number of course if the number of trainees is large and considered not
Classes manageable in one class.
Category of Project team member, end user, others (please specify).

Trainee
Size per Class Number of trainees per class.
Scheduled The proposed date(s) for trainees to attend the sessions.

Date(s) for
each Class
Venue Venue to be provided by the Contractor, or third-party

training centre. Please provide details if the venue is to be
provided by Contractor or by third-party training centre.

67 Page 58 of
67
(Phase I, II & III)
Table 17.1 Mandatory Training Plan and Details
Total
Number Duratio Propose Size Scheduled
of n d Category of per Date(s) for
Sessions (Hours) Number
Course Title Format per per of Trainee Class each Class Venue
Course Course Classes
Touch-base training
End-user operation
training
Others (if any)
Section 3: Requirements Page 59 of

67
(Phase I, II & III)

67
(Phase I, II & III)
Table 17.2 Optional Training Plan and Details
Total
Number Duratio Propose Size Scheduled
of n d Category of per Date(s) for
Sessions (Hours) Number
Course Title Format per per of Trainee Class each Class Venue
Course Course Classes
Touch-base training
End-user operation
training
Others (if any)

67
(Phase I, II & III)
17.3.7 Tenderers are to describe the proposed training venue and facilities.

67
(Phase I, II & III)
17.4 Qualifications of Trainers Responsible for the Training Courses
17.4.1 Tenderers shall submit in Table 17.3 the qualifications of the proposed
trainers (with attached curriculum vitae) in conducting the touch-base
training, end-user operation training, and any other training as proposed
by the Tenderers.
Table 17.3 Qualification of the Trainers
Number of Years of
Post- Experien Others

qualificati ce in (Pleas
Academic on Experien system e
N Compan Cours Qualificati experience ce in training specify
ame y e Title on training )

67
(Phase I, II & III)
SCHEDULE 18 – STATEMENT OF COMPLIANCE
18.1 Tenderers shall indicate their compliance by providing a compliance table in

Table 18.1, with clause-by-clause including sub-clause by sub-clause statement
of compliance corresponding to all Sections of Section 2 except sub-section 1 –
“Introduction” and sub-section 2 – “Background”.
Proposal without this compliance table will be considered incomplete and may be
disqualified.
Table 18.1 Statement of Compliance

Sub-section
Section No. Compliance 1
Remarks 2
Note:
1. Please put “Yes” if complied, “No” if not complied.
2. Where appropriate, Tenderers shall specify how the requirement will be
met in the Remarks column.
18.3 Tenderers shall indicate their level of compliance to the detailed functional
requirements by completing the functional requirements checklists provided in
Annex 2.1 – “Functional Requirements”.
Proposal without these completed checklists will be considered incomplete and

may be disqualified.

67
(Phase I, II & III)
SCHEDULE 19 – PRICE SUMMARY
19.1 Tenderers shall provide a summary of the aggregate price for the non-recurrent
cost, quarterly recurrent cost and other price information in Table 19.1.
Tenderers shall ensure the accuracy and consistency with the items proposed in
this tender. This Schedule must be completed in full and the price shall be
consistent with the prices listed in the following Schedules. In case of
discrepancy, this written Schedule document shall prevail.
The charges in Table 19.1 are for the purpose of total price assessment for this
project.
19.2 Items listed in Table 19.1 are guidelines to Tenderers and may not be exhaustive.
Tenderers shall ensure the completeness and accuracy of the information
provided for a total price assessment. Tenderers shall also include in this
schedule the non-recurrent and quarterly recurrent cost of other items.
19.3 Tenderers shall:
(a) Enter ‘N/C’ (i.e. no charge) where applicable.

67
(Phase I, II & III)
Table 19.1 Total Charges for Implementation Phase
Schedule
Descriptions Year 1 Year 2 Year 3 Year 4 Year 5 Total
Reference
Application and Database

Schedule 6
Software
Hardware Facilities Schedule 7
Implementation and Related Schedule 13 and

Services 20
Others (please specify) Not Applicable
TOTAL

67
(Phase I, II & III)
SCHEDULE 20 – TERMS OF PAYMENT
20.1 Mode of Payment
20.1.1 Payment will be made locally and in Brunei Dollars.
20.2 Payment Schedule
20.2.1 Payments shall be made in accordance with the charges set out in Tables
19.1 Schedule 19.
20.2.2 Tenderers should propose a schedule of payments consistent with the

implementation plan proposed in Table 12.1.

67

3 Section 3

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

3 Section 3

Hochgeladen von

Copyright:

Verfügbare Formate

Department of Schools, Ministry of Education

Project Title : The Supply, Delivery, Installation, Testing, Commissioning and

SCHEDULE 1 – INFORMATION SUMMARY......................................................................................4

SCHEDULE 2 – SUB-CONTRACTS ................................................................................................5

SCHEDULE 3 – COMPANY’S BACKGROUND ..................................................................................6

SCHEDULE 4 – COMPANY’S TRACK RECORD...............................................................................7

SCHEDULE 5 – CONTRACTOR’S EMPLOYEES AND THEIR DUTIES..................................................16

SCHEDULE 7 – HARDWARE FACILITIES......................................................................................28

SCHEDULE 9 – PERFORMANCE CRITERIA..................................................................................34

SCHEDULE 10 – TECHNICAL PROPOSAL AND SYSTEM CONFIGURATION..........................................36

SCHEDULE 11 – PROPOSED APPROACH AND METHODOLOGY........................................................39

SCHEDULE 12 – IMPLEMENTATION PLAN...................................................................................45

SCHEDULE 13 – IMPLEMENTATION AND RELATED SERVICES.........................................................48

SCHEDULE 14 – INSTALLATION TESTS.......................................................................................53

SCHEDULE 15 – ACCEPTANCE TESTS.........................................................................................53

SCHEDULE 16 – DOCUMENTATION AND DELIVERABLES................................................................53

SCHEDULE 17 – TRAINING PLAN..............................................................................................57

SCHEDULE 18 – STATEMENT OF COMPLIANCE............................................................................64

SCHEDULE 19 – PRICE SUMMARY............................................................................................65

SCHEDULE 20 – TERMS OF PAYMENT........................................................................................67

Section 3 – Requirements Page 1

Schedule 6 All except Table 6.1(a) Table 6.1(a)

Schedule 7 All except Table 7.1(a) Table 7.1(a)

Schedule 13 All except Table 13.2 Table 13.2

Section 3 – Requirements Page 2

Section 3 – Requirements Page 3

SCHEDULE 1 – INFORMATION SUMMARY

1.1 Tenderers shall provide in this Schedule the following information:

(a) Management summary

(b) List of all the companies (including Contractor and sub-contractor(s), if

(c) Company profile (including Contractor and sub-contractor(s), if any)

(g) Other information which is considered relevant

Section 3 – Requirements Page 4

Table 2.1 Responsibility Table

Not Not Not Applicable

Section 3 – Requirements Page 5

SCHEDULE 3 – COMPANY’S BACKGROUND

Section 3 – Requirements Page 6

SCHEDULE 4 – COMPANY’S TRACK RECORD

4.1 Company Contribution

(a) Project Management Services

(b) Implementation and Related Services

(c) Application Software

(d) Database Software

(e) Hardware and Operating System

Section 3 – Requirements Page 7

the relevant hardware or software price/cost over

4.1.2 The sum of contribution percentages across

Table 4.1 Contribution of Companies (in %)

Project Services or Items

ServicesOperations and Maintenance

Hardware and Operating System

Other Companies/ Manufacturers

Total: 100% 100% 100% 100% 100% 100%

4.2 Program Management Experiences

Name and Address Name and Version of Location where

Section 3 – Requirements Page 9

4.3 Project Partnership Experiences

(i) Implementation and Related Services

(ii) Operations and Maintenance Services

(iii) Application Software The types of partnership shall include:

• Partnership between Contractor and sub-contractor within the

• Partnership between the Contractor and sub-contractor within