12.02.2015 Views

Concept RFP For Smart School Management System

Concept RFP For Smart School Management System

Concept RFP For Smart School Management System

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong><br />

<strong>School</strong> <strong>Management</strong><br />

<strong>System</strong><br />

Wednesday, July 23, 1997


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

Copyright © 1997 Government of Malaysia.<br />

In the event that there exists any discrepancy between an electronic version of this document (or a<br />

document printed or distributed using an electronic version as a source) and the official printed<br />

hardcopy distributed by the Government (See Section 1.4.4 Obtaining a Printed Copy of The<br />

C<strong>RFP</strong>s and Related Documents), or officially distributed addenda or corrections, then the<br />

information in the official printed hardcopy, addenda or corrections shall prevail.<br />

i


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

<strong>Concept</strong> Request <strong>For</strong> Proposal (C<strong>RFP</strong>) <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> (SSMS).................. 1<br />

1 Overview of the MSC and the <strong>Smart</strong> <strong>School</strong> Project................................................................ 1<br />

1.1 MSC Flagship Applications ............................................................................................... 1<br />

1.2 <strong>Smart</strong> <strong>School</strong> Project Objectives and Approach ............................................................... 2<br />

1.3 The <strong>Smart</strong> <strong>School</strong> Pilot Effort............................................................................................. 2<br />

1.3.1 Objectives........................................................................................................................... 2<br />

1.3.2 Background information of pilots .................................................................................... 3<br />

1.3.3 Scope of the Pilot Projects ................................................................................................. 3<br />

1.4 <strong>Concept</strong> Requests for Proposals ........................................................................................ 3<br />

1.4.1 Overview............................................................................................................................ 3<br />

1.4.2 Documents to be read with this C<strong>RFP</strong> ............................................................................. 4<br />

1.4.3 The <strong>Smart</strong> <strong>School</strong> C<strong>RFP</strong>s................................................................................................... 4<br />

1.4.4 Obtaining a Printed Copy of The C<strong>RFP</strong>s and Related Documents ................................ 5<br />

1.4.5 C<strong>RFP</strong> Process and Timeline .............................................................................................. 6<br />

First stage: Individual Proposal Development..................................................................... 6<br />

Second Stage: Total Integrated Solution Development ....................................................... 6<br />

Abbreviated Timeline ............................................................................................................ 7<br />

2 Introduction to the <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> (SSMS) C<strong>RFP</strong>................................... 8<br />

2.1 Background......................................................................................................................... 8<br />

2.2 Objective.............................................................................................................................. 9<br />

2.3 The Roles of the <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> (SSMS) .........................................10<br />

2.4 Functions of the SSMS.......................................................................................................11<br />

3 Functional Requirements..........................................................................................................12<br />

3.1 <strong>School</strong> Governance............................................................................................................12<br />

3.2 Student Affairs <strong>Management</strong>............................................................................................13<br />

3.3 Educational Resources <strong>Management</strong> ...............................................................................14<br />

3.4 External Resources <strong>Management</strong> .....................................................................................15<br />

3.5 Financial <strong>Management</strong>......................................................................................................16<br />

3.6 Facilities <strong>Management</strong> ......................................................................................................17<br />

3.7 Human Resources <strong>Management</strong>.......................................................................................17<br />

3.8 Security <strong>Management</strong>........................................................................................................18<br />

3.9 Technology <strong>Management</strong>..................................................................................................19<br />

3.10 Hostel <strong>Management</strong> ..........................................................................................................19<br />

3.11 Summary of communications requirements....................................................................19<br />

4 Technical Requirements............................................................................................................22<br />

4.1 Application Architecture ..................................................................................................22<br />

4.2 Application Framework....................................................................................................23<br />

4.3 Standards Compliance ......................................................................................................25<br />

4.4 Integration Requirements .................................................................................................26<br />

4.5 Security Considerations ....................................................................................................26<br />

4.6 Platform Support...............................................................................................................27<br />

4.7 <strong>System</strong> Sizing and Capacity Planning..............................................................................27<br />

4.8 Multiple Language Support..............................................................................................28<br />

4.9 Risk Assessment Statement ..............................................................................................28<br />

4.10 Technical Service Level .....................................................................................................29<br />

5 Implementation Requirements.................................................................................................30<br />

5.1 Project <strong>Management</strong> Methodology ..................................................................................30<br />

5.2 Project Team Structure......................................................................................................30<br />

5.3 Risk <strong>Management</strong> Plan .....................................................................................................31<br />

5.4 Quality <strong>Management</strong>.........................................................................................................31<br />

5.5 Change <strong>Management</strong> Plan................................................................................................31<br />

ii


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

5.6 Training Plan .....................................................................................................................31<br />

5.7 Acceptance Testing Plan ...................................................................................................31<br />

5.8 Technology Transfer Plan .................................................................................................31<br />

5.9 Implementation Strategies ................................................................................................32<br />

6 Training Programs ....................................................................................................................33<br />

6.1 Overview............................................................................................................................33<br />

6.2 Training strategy ...............................................................................................................33<br />

6.3 Training Facilities ..............................................................................................................33<br />

6.4 Training schedule ..............................................................................................................34<br />

6.5 Training venue...................................................................................................................34<br />

6.6 Training Modules ..............................................................................................................34<br />

6.6.1 Training Design ................................................................................................................34<br />

6.6.2 Resources and References ................................................................................................34<br />

6.6.3 Time of Delivery...............................................................................................................34<br />

6.6.4 Training Curriculum ........................................................................................................34<br />

6.6.5 <strong>For</strong>mat of Training Modules............................................................................................34<br />

6.7 Monitoring and Evaluation...............................................................................................35<br />

6.8 Follow –up programme ....................................................................................................35<br />

7 Maintenance and Support Services..........................................................................................36<br />

7.1 Overview............................................................................................................................36<br />

7.2 Organisational ...................................................................................................................36<br />

7.3 Coverage ............................................................................................................................37<br />

7.4 Services...............................................................................................................................37<br />

7.4.1 Remedial Maintenance Service........................................................................................37<br />

7.4.2 Preventive Maintenance Service......................................................................................37<br />

7.4.3 Solution Support and Maintenance.................................................................................37<br />

7.4.4 Miscellaneous ...................................................................................................................38<br />

8 Performance Requirements ......................................................................................................39<br />

9 External Linkages......................................................................................................................40<br />

9.1 External Databases ............................................................................................................40<br />

10 Financial Requirements ........................................................................................................41<br />

10.1 Business Model Requirements..........................................................................................41<br />

10.2 Business Model..................................................................................................................41<br />

10.2.1 Government ....................................................................................................................41<br />

10.2.2 Responding Organisation ..............................................................................................42<br />

10.2.3 Users................................................................................................................................42<br />

Financial modelling assumptions ........................................................................................43<br />

10.2.4 Quantities required.........................................................................................................43<br />

10.2.5 Financial constraints.......................................................................................................43<br />

11 Capabilities of the Responding Organisation......................................................................44<br />

11.1 Project <strong>Management</strong> Capabilities.....................................................................................44<br />

11.1.1 Project <strong>Management</strong> Methodology ...............................................................................44<br />

11.1.2 Project <strong>Management</strong> Experience ...................................................................................44<br />

11.2 Training Capabilities.........................................................................................................44<br />

11.3 Support Capabilities..........................................................................................................44<br />

11.4 Financial Capabilities ........................................................................................................44<br />

11.5 Technical Capabilities .......................................................................................................45<br />

11.5.1 Technical leadership.......................................................................................................45<br />

11.5.2 Relevant reference sites..................................................................................................45<br />

11.5.3 Other unique capabilities as applicable ........................................................................45<br />

12 Instructions to Responding Organisations ..........................................................................46<br />

12.1 Communication .................................................................................................................46<br />

iii


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

12.1.1 Responding Organisations’ Briefing .............................................................................46<br />

12.2 Submission of Proposal.....................................................................................................46<br />

12.2.1 Time and Date.................................................................................................................46<br />

12.2.2 Mode of Delivery and Address .....................................................................................47<br />

12.2.3 Marking...........................................................................................................................47<br />

12.2.4 Number of Copies and Separation of Sections of Proposals........................................47<br />

12.2.5 Deposit ............................................................................................................................47<br />

12.2.6 Receipt of Proposal.........................................................................................................48<br />

12.2.7 Amendments...................................................................................................................48<br />

12.2.8 Validity of the Proposal..................................................................................................48<br />

12.2.9 Advertisement ................................................................................................................48<br />

12.2.10 Short-list ........................................................................................................................48<br />

12.2.11 Letter of Intent ..............................................................................................................48<br />

12.2.12 Performance Bond ........................................................................................................48<br />

12.2.13 Letter of Understanding...............................................................................................49<br />

12.2.14 Language.......................................................................................................................49<br />

12.2.15 Currency........................................................................................................................49<br />

12.2.16 Contents ........................................................................................................................49<br />

12.3 Proposal Process................................................................................................................49<br />

12.3.1 Communication during the First Stage .........................................................................49<br />

12.3.2 First Stage: Proposal Development ...............................................................................49<br />

12.3.3 First Stage Evaluation of Proposals and Short-Listing.................................................50<br />

12.3.4 Second Stage: Integrated Solution Development .........................................................50<br />

12.3.5 Second-Stage Evaluation and Shortlisting ....................................................................52<br />

12.3.6 Multi-track negotiations.................................................................................................52<br />

12.3.7 Final Selection .................................................................................................................52<br />

12.3.8 Implementation...............................................................................................................52<br />

12.4 Process Timeline................................................................................................................52<br />

12.5 Mandatory Requirements and Evaluation Criteria.........................................................53<br />

12.5.1 Mandatory Requirements ..............................................................................................53<br />

Evaluation Criteria................................................................................................................53<br />

Responding to specific evaluation criteria...........................................................................54<br />

12.6 Rights of the Government.................................................................................................55<br />

12.6.1 Amendments...................................................................................................................55<br />

12.6.2 Acceptance of Proposals.................................................................................................55<br />

12.6.3 Cost of Proposal..............................................................................................................55<br />

12.6.4 Responding Organisation’s Responsibilities ................................................................55<br />

12.6.5 Non-liability....................................................................................................................56<br />

12.6.6 Confidential Information ...............................................................................................56<br />

12.6.7 Failure of Negotiation ....................................................................................................56<br />

12.6.8 Discrepancy of Document..............................................................................................56<br />

12.6.9 Withholding Tax.............................................................................................................56<br />

12.6.10 Governing Law .............................................................................................................56<br />

Appendix 1 - Responding Organisation’s Undertaking <strong>For</strong>m ......................................................57<br />

Appendix 2 - Bank Guarantee Deposit <strong>For</strong>m..................................................................................58<br />

Appendix 3 - Quantum of Deposit for Responding Organisations...............................................60<br />

1. <strong>For</strong> International Companies....................................................................................................60<br />

2. <strong>For</strong> local companies not registered with the Ministry of Finance, Malaysia.........................60<br />

3. <strong>For</strong> companies registered with the Ministry of Finance, Malaysia........................................60<br />

Appendix 4 - Bank Guarantee <strong>For</strong>m for Performance Bond..........................................................61<br />

Appendix 5 - Glossary......................................................................................................................64<br />

iv


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

Table 1: Summary of Information in <strong>School</strong> Governance and its Operational Functions ...............13<br />

Table 2: Summary of Information for Student Affairs <strong>Management</strong> and Its Operational Functions.<br />

........................................................................................................................................................14<br />

Table 3: Summary of Information on Educational Resource and its Operational Functions ..........15<br />

Table 4: Summary of Information on External Resource and its Operational Functions ................16<br />

Table 5: Summary of Information on <strong>School</strong> Finance Functions.......................................................17<br />

Table 6: Summary of Information on <strong>School</strong> Facilities <strong>System</strong>’s Functions .....................................17<br />

Table 7: Summary of Information on Human Resource <strong>System</strong>’s Functions...................................18<br />

Table 8: Summary of Information on <strong>School</strong> Security <strong>System</strong>’s Functions ......................................19<br />

Figure 1: Three-Tier Application Architecture ...................................................................................23<br />

Figure 2: <strong>Smart</strong> <strong>School</strong> Application Framework ................................................................................24<br />

Figure 3: Funding model between Ministry of Education, Responding Organisations, Users and<br />

Stakeholders..................................................................................................................................44<br />

Figure 4: How short-listed Responding Organisations will form an unbound consortium............53<br />

v


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

<strong>Concept</strong> Request <strong>For</strong> Proposal (C<strong>RFP</strong>)<br />

<strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> (SSMS)<br />

1 Overview of the MSC and the <strong>Smart</strong> <strong>School</strong> Project<br />

Malaysia’s Multimedia Super Corridor (MSC) aims to revolutionise how the world does<br />

business. Located at the hub of Asia’s fastest growing markets, the MSC shall unlock<br />

multimedia’s full potential by integrating ground breaking cyberlaws and outstanding<br />

information infrastructure in an attractive physical environment. The MSC shall be a<br />

regional launch site for companies developing or using leading multimedia technology,<br />

allowing these innovators to harness Malaysia’s unique competitive advantages that arise<br />

from its multicultural links, committed leadership, and proven track record in developing<br />

products and services for regional and global markets.<br />

The MSC is a gift from the Malaysian Government to technology developers and users<br />

seeking to expand their Asian presence, to Malaysians wanting their country to prosper, and<br />

to neighbouring countries aspiring to partner with a technology hub. The MSC is a 15-by-<br />

50-kilometre zone extending south from Malaysia’s present national capital and business<br />

hub, Kuala Lumpur. The nation is devoting this massive corridor to creating the perfect<br />

environment for companies wanting to create, distribute and employ multimedia products<br />

and services.<br />

The MSC shall bring together the following four key elements<br />

• Best possible physical infrastructure, including Kuala Lumpur City Centre, a new<br />

world class airport and integrated logistics hub, rapid rail links to Kuala Lumpur, a<br />

smart highway, and two intelligent garden cities.<br />

• New laws, policies, and practices designed to enable and encourage electronic<br />

commerce, facilitate the development of multimedia applications, and position Malaysia<br />

as the regional leader in intellectual property protection.<br />

• High capacity global telecommunications infrastructure built on MSC’s 2. 5-gigabitto-10-gigabit<br />

digital optical fibre backbone and using Asynchronous Transfer Mode<br />

(ATM) switches to provide fibre to the building. This network shall have a 5-gigabit<br />

international gateway with direct links to the US, Europe, and Japan, as well as the other<br />

nations in Southeast Asia.<br />

• The Multimedia Development Corporation (MDC) – A one-stop Shop created to<br />

manage and market the MSC. The MDC’s mission is to create the best environment in<br />

the world for private sector companies to pursue multimedia and to facilitate their<br />

investment in the MSC. The MDC is a high powered ‘one-stop super shop’ wholly<br />

focused on ensuring the success of the MSC and the companies operating in it.<br />

1.1 MSC Flagship Applications<br />

To speed the MSC’s evolution, the Malaysian Government has targeted seven<br />

multimedia applications for rapid development. These flagship applications<br />

are Electronic Government, Telemedicine, <strong>Smart</strong> <strong>School</strong>s, Multipurpose Card,<br />

R&D Clusters, Worldwide Manufacturing Webs, and Borderless Marketing<br />

Centres.<br />

The objective of these flagship applications is to attract a critical mass of worldclass<br />

companies to develop leading edge applications, products, and services<br />

1


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

in the MSC. Specifically, the flagship applications aim to increase the<br />

productivity and competitiveness of Malaysia and also create a global test bed<br />

for innovative solutions.<br />

The flagships shall improve Malaysia’s productivity and competitiveness by<br />

increasing the efficiency and effectiveness of technology transfer and creating<br />

an environment that nurtures highly competitive webs of Malaysian and<br />

international small and medium enterprises. The flagships shall also increase<br />

foreign direct investment into high technology and shall accelerate the<br />

development of a robust services sector.<br />

The flagship applications also aim at creating a global test bed for innovation<br />

by allowing consortia to pioneer new applications of multimedia in the public<br />

and private sectors. The flagships shall also build platforms for ongoing<br />

innovation and create standards that allow growing reverse investment from<br />

MSC consortia. The flagship shall create the opportunity for the MSC to<br />

develop a strong reputation for commercial R&D and shall also strengthen<br />

Malaysia’s skill base in multimedia R&D.<br />

1.2 <strong>Smart</strong> <strong>School</strong> Project Objectives and Approach<br />

<strong>Smart</strong> <strong>School</strong>s, one of the flagships of the MSC, has been identified as a critical<br />

enabler to transform radically, the Malaysian school system. The objectives of<br />

implementing these <strong>Smart</strong> <strong>School</strong>s, which are based on Malaysia’s National<br />

Philosophy of Education, are to<br />

• produce a thinking and technology-literate workforce<br />

• democratise education<br />

• increase participation of stakeholders<br />

• provide all-round development of the individual including (intellectual,<br />

physical, emotional and spiritual)<br />

• provide opportunities to enhance individual strengths and abilities<br />

The basis for a Malaysian <strong>Smart</strong> <strong>School</strong> is provided in the The Malaysian<br />

<strong>Smart</strong> <strong>School</strong>: A <strong>Concept</strong>ual Blueprint that has been drafted by a joint<br />

industry – Ministry of Education task force, basing itself on an original policy<br />

document (<strong>Smart</strong> <strong>School</strong>s in Malaysia: A Quantum Leap) prepared by the<br />

Ministry of Education. This team also prepared a document, The Malaysian<br />

<strong>Smart</strong> <strong>School</strong> Implementation Plan to guide the conversion of existing schools<br />

into <strong>Smart</strong> <strong>School</strong>s in two stages. In the first stage, 90 schools in 1999 shall be<br />

converted into <strong>Smart</strong> <strong>School</strong>s. The second stage is to convert the estimated<br />

10,000 primary and secondary schools by 2010.<br />

1.3 The <strong>Smart</strong> <strong>School</strong> Pilot Effort<br />

1.3.1 Objectives<br />

These pilots, implemented in the 90 pioneer schools, shall allow for<br />

testing, evaluation, improvement and further fine-tuning to be made to<br />

the solutions proposed. Since the pioneer schools are made up of different<br />

kinds of schools, the pilots shall also be tested according to the suitability<br />

of their solutions to different schools. The pilots shall also be an<br />

2


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

opportunity to evaluate the extent, to which vendors are able to meet<br />

deadlines, fulfil predetermined performance levels and generally,<br />

demonstrate their implementation capabilities.<br />

1.3.2 Background information of pilots<br />

The 90 pioneer schools, among which the pilots are to be implemented<br />

comprise six different categories of schools:<br />

• 9 new schools – 5 primary and 4 secondary – four in the Sri Bintang<br />

Complex, two in the Batu Permai Complex and three in Putra Jaya;<br />

• 36 residential secondary schools;<br />

• 14 Munshi Network schools, currently piloting electronic resource<br />

centres;<br />

• 14 state secondary schools;<br />

• 14 state primary schools;<br />

• 3 remote schools without direct electricity supply, comprising 2<br />

primary schools and 1 secondary school.<br />

The implementation shall involve allocating schools according to<br />

predetermined levels of technology, ranging from a preliminary level to<br />

the highest level. At the highest level, schools are equipped with a high<br />

ratio of computers to teachers and schoolchildren, and full multimedia<br />

laboratories such as labs, audio-visual equipment and Local Area<br />

Network (LAN) and Wide Area Network (WAN) networks.<br />

Full details of these schools including location, staff and student strength,<br />

the existing levels of computerisation and other information are listed in<br />

The Malaysian <strong>Smart</strong> <strong>School</strong> Implementation Plan.<br />

1.3.3 Scope of the Pilot Projects<br />

The pilot efforts shall be in line with the different levels of technology that<br />

have been allocated to the schools. <strong>For</strong> any given level, the applications in<br />

the pilots shall be implemented to the maximum extent allowed by the<br />

level of technology assigned. Details of the levels of technology are<br />

described in The Malaysian <strong>Smart</strong> <strong>School</strong> Implementation Plan.<br />

Each Responding Organisation is expected to detail their deliverables as<br />

well as their performance criteria to be used to evaluate their<br />

implementation.<br />

1.4 <strong>Concept</strong> Requests for Proposals<br />

1.4.1 Overview<br />

The <strong>Concept</strong> Request for Proposals (C<strong>RFP</strong>) outlines the high-level<br />

functional requirements expected in each Responding Organisation’s<br />

proposal. The C<strong>RFP</strong> does not explicitly specify platforms, but prescribes a<br />

framework built around broadly detailed standards and policies. It gives<br />

the Responding Organisation the flexibility to innovate, creating the best<br />

solutions to deliver these benefits. Specifically, the C<strong>RFP</strong> details:<br />

3


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• Solution Requirements:<br />

Functional, operational, technical, financial and implementation.<br />

• Required capabilities of Responding Organisation:<br />

Organisational, financial and technical.<br />

• Instructions for Responding Organisations:<br />

Proposal procedures and high-level evaluation criteria.<br />

1.4.2 Documents to be read with this C<strong>RFP</strong><br />

This C<strong>RFP</strong> shall be read in conjunction with the following documents, in<br />

order to get a full picture of the <strong>Smart</strong> <strong>School</strong> project.<br />

• The Malaysian <strong>Smart</strong> <strong>School</strong>: A <strong>Concept</strong>ual Blueprint.<br />

This document provides the conceptual overview of the whole <strong>Smart</strong><br />

<strong>School</strong> project.<br />

• The Malaysian <strong>Smart</strong> <strong>School</strong> Implementation Plan.<br />

This document presents the roadmap for creating Malaysian <strong>Smart</strong><br />

<strong>School</strong>s.<br />

• <strong>Smart</strong> <strong>School</strong> Information Technology Policy and Standards.<br />

The primary audience for this document is intended to be Malaysian<br />

Government Agencies and Multimedia Development Corporation<br />

personnel responsible for making decisions about information<br />

technology, and those organizations desiring to provide systems for<br />

the Malaysian Government that conform to this set of policies.<br />

• The other C<strong>RFP</strong>s for the <strong>Smart</strong> <strong>School</strong> pilots<br />

As the C<strong>RFP</strong>s describe a tight integration between their various<br />

described components, familiarity with the requirements of the other<br />

C<strong>RFP</strong>s will be an advantage in producing an integrable solution<br />

1.4.3 The <strong>Smart</strong> <strong>School</strong> C<strong>RFP</strong>s<br />

The <strong>Smart</strong> <strong>School</strong> Project is built on five C<strong>RFP</strong>s that invite organisations<br />

to offer solutions on one or more of the following areas:<br />

• The <strong>Smart</strong> <strong>School</strong> Teaching-Learning Materials<br />

This C<strong>RFP</strong> for Teaching-Learning (T-L) Materials focuses on four<br />

subjects (Bahasa Melayu, English, Mathematics and Science) that shall<br />

be used in classrooms in conjunction with the pedagogical practices<br />

outlined in The Malaysian <strong>Smart</strong> <strong>School</strong> <strong>Concept</strong>ual Blueprint. These<br />

materials, with built-in assessment, shall promote learning in a<br />

manner that is best suited to the student’s individual learning pace<br />

and style. The C<strong>RFP</strong> shall also outline requests for training modules<br />

and a master-trainer training program.<br />

• The <strong>Smart</strong> <strong>School</strong> Assessment <strong>System</strong><br />

The C<strong>RFP</strong> for the <strong>Smart</strong> <strong>School</strong> Assessment <strong>System</strong> addresses the<br />

<strong>Smart</strong> <strong>School</strong>’s assessment packages and the Life-Time Database<br />

(LTDB), which shall assess and record students’ academic progress<br />

and performance. The C<strong>RFP</strong> also outlines requests for the training<br />

and certification of assessors.<br />

4


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• The <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> (SSMS)<br />

The C<strong>RFP</strong> for the <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> outlines the need<br />

for automating school’s administrative processes. This system shall<br />

have many linkages with the other sections of the <strong>Smart</strong> <strong>School</strong>,<br />

especially Teaching-Learning and Assessment systems, as well as<br />

with external Ministry of Education databases. The C<strong>RFP</strong> shall also<br />

outline requests for training modules, as well as the training of a<br />

group of management trainers.<br />

• The <strong>Smart</strong> <strong>School</strong> Technology Infrastructure<br />

The C<strong>RFP</strong> for the <strong>Smart</strong> <strong>School</strong> Technology Infrastructure addresses<br />

the hardware and LAN that shall be used by 79 of the <strong>Smart</strong> <strong>School</strong>s<br />

(the technology infrastructure of the nine new schools and two of the<br />

residential secondary schools is beyond the scope of this C<strong>RFP</strong>). This<br />

shall be used to support the Teaching-Learning, <strong>Management</strong> and<br />

Assessment system applications. The systems shall conform to<br />

specified standards to ensure interoperability.<br />

• The <strong>Smart</strong> <strong>School</strong>s <strong>System</strong>s Integration<br />

The C<strong>RFP</strong> for <strong>System</strong>s Integration focuses on the <strong>System</strong> Integrator’s<br />

(SI’s) responsibilities for design and implementation of the overall<br />

<strong>Smart</strong> <strong>School</strong>s system. The SI shall ensure the detailed design,<br />

installation, testing and acceptance of each of the <strong>Smart</strong> <strong>School</strong> subapplications<br />

(Teaching-Learning, <strong>School</strong> <strong>Management</strong> system,<br />

Assessment system and Hardware / Infrastructure). The SI is also<br />

responsible for the network management and the user assistance<br />

services. The C<strong>RFP</strong> also outlines the need for training for system and<br />

network administrators, as well as an overall training strategy and<br />

logistics for teachers and principals. The SI shall design and be<br />

responsible for the management of the WAN architecture.<br />

Although there are five separate C<strong>RFP</strong>s, Responding Organisations are<br />

welcome to submit proposals that cover the requirements of more than<br />

one C<strong>RFP</strong>. The two-stage process for selection is outlined in Section 1.4.5,<br />

and described in more detail in the chapter titled “Instructions to<br />

Responding Organisations”.<br />

1.4.4 Obtaining a Printed Copy of The C<strong>RFP</strong>s and Related Documents<br />

A hardcopy of all the C<strong>RFP</strong>s with the related documents shall be<br />

purchased from the<br />

SMART SCHOOL C<strong>RFP</strong> SECRETARIAT<br />

Educational Technology Division<br />

Ministry of Education<br />

Pesiaran Bukit Kiara<br />

50604 Kuala Lumpur<br />

Malaysia<br />

They may be obtained in person during office hours, from 26 July 1997<br />

until 30 September 1997. C<strong>RFP</strong>s shall not be sold after this period. The<br />

office hours are as follows:<br />

Monday-Thursday 0800 – 1245, 1400 – 1615<br />

Friday 0800 – 1215, 1445 – 1615<br />

5


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

Saturday 0800 – 1245<br />

The C<strong>RFP</strong>s may be purchased upon payment of a non-refundable fee.<br />

Payment shall be in the form of Bank draft in favour of the Chief<br />

Accountant, Ministry of Education, Malaysia.<br />

The documents are packaged into two sets:<br />

1. The Malaysian <strong>Smart</strong> <strong>School</strong>: A <strong>Concept</strong>ual Blueprint, the Malaysian<br />

<strong>Smart</strong> <strong>School</strong> Implementation Plan, the <strong>Smart</strong> <strong>School</strong> Information<br />

Technology Policy and Standards document and all five of the C<strong>RFP</strong>s,<br />

2. The curriculum documents for the relevant subjects, which are<br />

necessary for any Responding Organisation interested in responding<br />

to the C<strong>RFP</strong> for the <strong>Smart</strong> <strong>School</strong>s Teaching-Learning Materials and<br />

the document, <strong>Smart</strong> Assessment: An Introduction, which may be<br />

useful for those responding to the C<strong>RFP</strong> for <strong>Smart</strong> <strong>School</strong>s<br />

Assessment <strong>System</strong>.<br />

1.4.5 C<strong>RFP</strong> Process and Timeline<br />

The C<strong>RFP</strong> process for the <strong>Smart</strong> <strong>School</strong>s project has two stages. The first<br />

stage qualifies individual organisations for participation in the second<br />

stage, in which they shall join in an "unbound consortium" that shall<br />

provide a comprehensive, integrated response to the requirements of all<br />

five <strong>Smart</strong> <strong>School</strong> C<strong>RFP</strong>s. In this way, the C<strong>RFP</strong> process aims to foster the<br />

development of webs of collaborating companies, which shall further the<br />

growth of the MSC. In addition, the inclusion of Malaysian companies in<br />

these unbound consortia offers one avenue for the transfer of technology<br />

to and development of skills in Malaysian enterprises, though there are<br />

other, additional ways for the unbound consortia to fulfil this obligation.<br />

The chapter titled “Instructions to Responding Organisations” contains a<br />

detailed account of the C<strong>RFP</strong> process.<br />

First stage: Individual Proposal Development<br />

The first stage consists of organisations responding with a proposal for a<br />

product or service for a particular C<strong>RFP</strong>. However, they should be aware<br />

that the C<strong>RFP</strong>s represent requests for proposals that shall be eventually<br />

integrated into a total integrated solution system. Hence, they shall be<br />

prepared to state a proposal that incorporates their vision of how their<br />

particular product or service will fit into the overall solution. In particular<br />

they shall address issues of how they plan to develop, deploy, distribute,<br />

support and provide access to the service or product.<br />

The Government shall then evaluate and short-list the proposals to<br />

identify the Responding Organisations capable of participation in the<br />

second round.<br />

Second Stage: Total Integrated Solution Development<br />

The short-listed organisations shall then work with each other in<br />

unbound consortia, in order to produce a complete integrated solution.<br />

There are several conditions as to the make-up of these unbound<br />

6


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

consortia that are outlined in the chapter “Instructions to Responding<br />

Organisations”.<br />

.<br />

Abbreviated Timeline<br />

• 30 September 1997: The deadline by which the Responding<br />

Organisations shall submit their proposals.<br />

• 1 December 1997: Short-listed Responding Organisations for the<br />

integrated proposal round are announced.<br />

• December to March 1998: Short-listed Responding Organisations<br />

form unbound consortia and prepare integrated proposals.<br />

• 31 March 1998: Deadline by which the unbound consortia shall<br />

submit their integrated proposals.<br />

• 1 July 1998: Second round selection is completed. The successful<br />

proposal and the winning unbound consortium shall be announced.<br />

The Government shall sign a contract with all the Responding<br />

Organisations that comprise the winning unbound consortium or<br />

with a legally bound consortium that comprise all the Responding<br />

Organisation of the winning unbound consortium. The terms and<br />

conditions of the contract shall be agreed upon between the<br />

Government and all the Responding Organisations that comprise the<br />

said legally bound consortium as the case may be.<br />

7


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

2 Introduction to the <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> (SSMS) C<strong>RFP</strong><br />

2.1 Background<br />

The primary objective for the SSMS is to support teaching and learning<br />

functions within schools by managing resources and processes more efficiently<br />

and effectively. This includes linkages and functionality required to support<br />

school processes that relate to external entities such as:<br />

• District Education Offices<br />

• State Education Departments<br />

• Ministry of Education (MoE)<br />

• Relevant Government agencies<br />

• Parents<br />

• The community<br />

• Relevant NGOs, suppliers, etc<br />

Each of the activities under the <strong>Smart</strong> <strong>School</strong>s management functions can be<br />

categorised into one of nine broad areas. These nine areas, however, are<br />

classified as such because of the major emphasis of their functions. They are<br />

not necessarily mutually exclusive as a number of them may share some<br />

common databases, providing for the necessity for integration across them.<br />

The nine functional areas are briefly described as follows:<br />

<strong>School</strong> Governance: This part of the school management function deals with<br />

school policies and regulations. It ensures efficient communication between<br />

relevant agencies and stake holders, and makes decisions on curriculum<br />

management to fit the school's local environment and to tailor it according to<br />

students' needs.<br />

Student Affairs: The Student Affairs component of the <strong>Smart</strong> <strong>School</strong>s<br />

management system deals with all the issues that relate to students' teachinglearning<br />

and welfare needs. It maintains a comprehensive database of student<br />

records.<br />

Educational Resources: This component manages a teaching-learning resource<br />

database that is quick and easily accessed by students and teachers. It<br />

provides schools with relevant and appropriate teaching-learning materials in<br />

a timely manner.<br />

External Resource: The External Resource component maintains a<br />

comprehensive database on available external resources that are relevant and<br />

applicable to the teaching-learning scenarios in schools. It should also provide<br />

and manage resources to enable "virtual visits".<br />

Finance: This component of the <strong>Smart</strong> <strong>School</strong>s management system handles<br />

the fiscal management portion. It consists of a comprehensive educational<br />

accounting system with direct interface to the District Education Office and the<br />

State Education Department.<br />

Facilities: This component of the <strong>Smart</strong> <strong>School</strong>s management system<br />

maintains and manages the utilisation of the school's facilities. It contains<br />

8


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

comprehensive records of inventories and is capable of tracking the movement<br />

of removable assets.<br />

Human Resource: This component comprises a comprehensive Human<br />

Resource <strong>Management</strong> <strong>System</strong> which tracks the individual staff member's<br />

development programmes. It manages the staff development programme of<br />

the school to ensure balanced opportunities for all staff members to attend or<br />

participate at seminars, conferences and workshops for professional<br />

development. It also manages staff's promotions and transfers.<br />

Security: A system is required to ensure human safety as well as physical<br />

safety of the school. Measures required include the need for proper<br />

identification or authorisation for access into school or access into certain<br />

databases of the school communication systems.<br />

Technology: This component of the <strong>Smart</strong> <strong>School</strong>s management system<br />

manages the technology components of the school and includes IT hardware<br />

and IT resource management, network management and technology designs<br />

upgrading.<br />

2.2 Objective<br />

The objective of this C<strong>RFP</strong> is to invite proposals from Responding<br />

Organisations for the following:<br />

The supplying, integrating, installing, testing, commissioning, training and<br />

post-acceptance maintenance and support services for an integrated <strong>Smart</strong><br />

<strong>School</strong>s <strong>Management</strong> <strong>System</strong> (SSMS).<br />

Each proposal, from either an individual Responding Organisation or a<br />

Consortium of Responding Organisations, shall include:<br />

• An integrated management software covering the nine areas of the<br />

management function, namely, Financial, Student Affairs, Educational<br />

Resource, External Resource, Human Resource, Facilities, <strong>School</strong><br />

Governance, Security, and Technology for the first phase of 90 <strong>Smart</strong><br />

<strong>School</strong>s to be implemented beginning January 1999;<br />

• Training Programme for <strong>Management</strong> Trainers (Training Programme).<br />

The Responding Organisation shall prepare and implement a training<br />

programme to train <strong>Management</strong> Trainers. These <strong>Management</strong> Trainers<br />

shall train other Trainers. <strong>Management</strong> Trainers and Trainers will then be<br />

responsible for the training of school administration teams comprising<br />

principals of secondary schools, headmasters of primary schools, senior<br />

assistants and clerks as well as Ministry of Education officers from district,<br />

state and federal levels.<br />

• Training Modules. The Responding Organisation shall prepare Training<br />

modules related to the SSMS for <strong>Management</strong> Trainers to use in the<br />

Training Programme.<br />

Response:<br />

• The Responding Organisation shall submit a single proposal for all 3<br />

components.<br />

• Since all administrative aspects of the <strong>Smart</strong> <strong>School</strong>s are covered by the<br />

SSMS, the applications and systems specified in other <strong>Smart</strong> <strong>School</strong><br />

9


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

C<strong>RFP</strong>s will need to be integrated with the SSMS. Consequently, the<br />

Responding Organisation awarded the contract to implement the SSMS<br />

shall be required to integrate all the <strong>Smart</strong> <strong>School</strong> systems and<br />

applications.<br />

• The Responding Organisation is encouraged to submit innovative<br />

proposals for systems that can be deployed in phases for various,<br />

possibly differing, technology platforms commensurate with the<br />

different levels of technology that will be deployed in Malaysia’s<br />

schools. These technology requirements, together with the levels of<br />

technology to be deployed in the schools, are described in the document,<br />

The Malaysian <strong>Smart</strong> <strong>School</strong> Implementation Plan.<br />

2.3 The Roles of the <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> (SSMS)<br />

In addition to supporting the management functions of the <strong>Smart</strong> <strong>School</strong>, the<br />

SSMS must also integrate the following systems that are to be specified in the<br />

other C<strong>RFP</strong>s:<br />

• Teaching-Learning Materials<br />

• Assessment<br />

• IT Security management<br />

• Network and <strong>System</strong> management<br />

• User Support/Helpdesk<br />

The SSMS will help integrate the different functions outlined in the other four<br />

<strong>Smart</strong> <strong>School</strong> C<strong>RFP</strong>s by:<br />

• acting as a common user front-end for access to all applications<br />

• consolidating database information across multiple applications<br />

• allowing access between certain applications and other, possibly external,<br />

databases and applications<br />

• allowing access to existing databases within the various divisions in the<br />

Ministry of Education, thus requiring these databases to be integrated with<br />

the SSMS that will be developed.<br />

By integrating these different systems and applications, the SSMS should<br />

reduce time and effort spent by teaching staff on non-teaching tasks and<br />

provide timely access to relevant information, which will help more<br />

stakeholders participate in, and improve, Malaysia’s educational decisionmaking<br />

processes.<br />

The Responding Organisation shall propose optimal integration methods and<br />

ensure:<br />

• Alignment of all applications and systems around a common framework of<br />

access, deployment, distribution, security, management and support<br />

• Minimisation of the number of disparate systems and platforms to be<br />

installed, managed and supported<br />

• Consolidation of information in the interest of reducing unnecessary<br />

information redundancy<br />

10


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• Integration of databases where necessary<br />

• The access requirements of disparate constituencies encompassing the<br />

Ministry of Education, other government agencies, students and their<br />

parents, the community, corporations and other organisations are met.<br />

2.4 Functions of the SSMS<br />

As mentioned in paragraph 2.1, the functions of the SSMS can be categorised<br />

into 9 areas. Each of these areas does not necessarily need a system of its own,<br />

as there are many links between systems.<br />

Residential and semi-residential schools have an additional function of hostel<br />

management.<br />

These functional areas are described in the The Malaysian <strong>Smart</strong> <strong>School</strong>: A<br />

<strong>Concept</strong>ual Blueprint, with the requirements for the SSMS being detailed in the<br />

following section.<br />

11


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

3 Functional Requirements<br />

This section describes the function of SSMS. The requirements are organised below into 10<br />

sub-sections that correspond to the 9 functional areas listed in the previous section and an<br />

additional Hostel <strong>Management</strong> function for residential schools. This categorisation does not<br />

imply or mandate that 10 separate sub-systems are to be provided in the SSMS. The<br />

Responding Organisation shall propose an integrated SSMS that, at a minimum<br />

• Meets the functional requirements stated in this C<strong>RFP</strong><br />

• Organises access to all applications and services in a manner consistent with the<br />

category or role of the user.<br />

3.1 <strong>School</strong> Governance<br />

<strong>School</strong> Governance is a function that is primarily concerned with the day-today<br />

governance of school-wide policies and operations.<br />

The <strong>School</strong> Governance part of the <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Software<br />

shall<br />

• receive and send messages from and to the divisions of the Ministry of<br />

Education, the State Education Departments, District Education Offices<br />

and parents or the community at large.<br />

• enable the recording of the daily attendance of students, teachers and all<br />

other staff members. This component shall therefore be linked to “Student<br />

Affairs”, “External Resource”, and the “Human Resource” components.<br />

• allow the recording and analysing of students’ achievement measures for<br />

all school-based assessment. Plots and groups the growth curves and<br />

calculates the necessary basic summary statistics of the measures at regular<br />

intervals.<br />

• allow storage of students’ co-curricular activities records that are accessible<br />

by the principal, teachers, students and students' own parents, but<br />

protected from others unless given permission to access.<br />

• enable the preparation of teachers’ timetables, given all the necessary<br />

variables such as total number of periods per week for teachers concerned,<br />

the subject(s) taught by each teacher, teachers’ names, whether teaching<br />

periods should be consecutive or otherwise, total number of teachers<br />

available for a given subject, etc.<br />

• make messaging services available to all in school, for communication<br />

between the principal, teachers, students, office staff members, as well as<br />

members of the community.<br />

• enable transfer and exchange of teaching-learning and reference materials<br />

as well as allowing consultations and the sharing of expertise (outsourcing<br />

of expertise) amongst teachers across the country.<br />

• allow access to centrally located government materials such as the<br />

Government General Orders and Government Financial Orders as well as<br />

all other government circulars to the principal, teachers and other office<br />

staff members only.<br />

12


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• provide a channel of communication between school and the community<br />

as well as relevant higher authorities in the planning and implementation<br />

of school projects such as fund raisers and sports.<br />

• enable the school administrators to classify materials and restrict access to<br />

materials according to the type of user and materials.<br />

Information<br />

Operational Functions<br />

1 • Reports on subject panel • Record, dissemination and retrieval<br />

discussions and minutes of<br />

meetings<br />

2. • Teacher and class time tables<br />

including relief time tables<br />

• Construction, record, dissemination and<br />

retrieval<br />

3. • Teaching and non–teaching tasks<br />

performed by staff<br />

• Record, retrieval and analysis for summary<br />

data on workload<br />

4. • Government General Orders • Retrieval and dissemination.<br />

• Ministry of Education Circulars<br />

5. • Students’ assessment records • Record, retrieval, analysis and reporting.<br />

6. • Co–curricular activities – • Record, retrieval, analysis and reporting.<br />

Participation and assessment<br />

7. • Curriculum <strong>Management</strong> • <strong>System</strong> that is able to monitor the<br />

implementation of the school curriculum.<br />

Table 1: Summary of Information in <strong>School</strong> Governance and its Operational Functions<br />

3.2 Student Affairs <strong>Management</strong><br />

The Student Affairs component is concerned with the management of student<br />

information and all other items pertaining to student matters. This solution<br />

shall enable<br />

• input and retrieval of data on:<br />

− student’s profile which include personal particulars (historical and<br />

current) as well as performance records that can be adapted for usage<br />

in assessment records,<br />

− parents’ or guardians’ relevant personal records for usage in scholarship<br />

awards, book loan etc.<br />

• reporting and analysing of student data which include assessment scores<br />

• projection of student performance.<br />

• compilation of feedback on student's performance by various parties.<br />

• input, retrieval, analysis and reporting of data on students, categorised by<br />

age, sex, race, religion, socio-economic status, and other classifiers.<br />

• transfer of data on student profiles between schools district and state<br />

education offices and the various divisions of the Education Ministry, as<br />

may be required when students move.<br />

13


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• provide information on facilities used by students and teachers such as the<br />

borrowing of science equipment, books under the text book loan scheme,<br />

books from the school library, scholarships and grants, and the use of<br />

hostel rooms (for fully and semi-residential schools).<br />

• recording of attendance and participation details on students’ curricular<br />

and co-curricular activities,<br />

• recording and retrieval of confidential information on students’ discipline,<br />

academic performance, health and insurance, and counsellor’s reports as<br />

well as the follow-up and follow through actions by the school.<br />

• on-site and off-site registration of students with the school .<br />

Information Operational Function<br />

1. • Student biodata e.g. health profiles • Record and retrieval<br />

2. • On-going assessment records and • Record retrieval, and reporting<br />

teacher reports on individual students<br />

3. • Student family background • Record and retrieval<br />

4. • Student attendance in school. • Record and retrieval<br />

5. • Participation in co-curricular activities at<br />

various levels e.g. debates, sports and<br />

games at district, state, national and<br />

International levels.<br />

6. • Confidential reports on student’s overall<br />

discipline and academic performance<br />

7. • Counsellor’s confidential report on<br />

students<br />

8. • Rooming system – records on hostel<br />

boarders (Residential schools)<br />

9. • Analysis of students’ scores and<br />

measures by some basic variables such<br />

as sex, age, socio-economic status, etc.<br />

• Record, retrieval, analysis and<br />

reporting<br />

• Restricted record and retrieval,<br />

analysis and reporting<br />

• Restricted record and retrieval,<br />

analysis and reporting<br />

• Record and retrieval<br />

• Record, retrieval, analysis and<br />

reporting<br />

• Automated file transfer between<br />

schools, education offices and<br />

divisions of the Education Ministry<br />

Table 2: Summary of Information for Student Affairs <strong>Management</strong> and Its Operational Functions.<br />

Note: Report formats include formats for school testimonials, students’<br />

performance reports, and students’ profiles.<br />

3.3 Educational Resources <strong>Management</strong><br />

The Educational Resources <strong>Management</strong> component deals with managing the<br />

usage of resources for teaching-learning delivery. The “Educational Resource”<br />

portion of the SSMS shall<br />

• enable the input and retrieval of teaching-learning materials<br />

14


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• enable the input and retrieval of personal data of available resource<br />

persons.<br />

• maintain an inventory of all the schools’ property and records of borrowals<br />

and returns. These records shall be accessible to teachers and other staff<br />

members of the school,<br />

• consist of an automated library management system to manage borrowals<br />

and returns of library and other educational resource materials, interlibrary<br />

loans, generation of reminders for overdue materials and the<br />

monitoring of fines and payments for overdue materials returned.<br />

Information<br />

Operational Function<br />

1. Detailed inventory of all teaching and audio visual –<br />

aids. e.g. OHP’s, T.V, VCR, science equipment,<br />

software, teaching-learning materials, and analysis<br />

of usage of all these equipment and materials<br />

2. Electronic library management system :<br />

• Cataloguing<br />

• Borrowing and returning of resources from and<br />

to the library<br />

3. Multiple locations in the school for reception of video<br />

demonstrations.<br />

• Coding of equipment,<br />

record, retrieval, tracking<br />

and monitoring<br />

• Automated<br />

• Inter-library loan facilities<br />

and communication<br />

• On-line catalogue from<br />

teachers’ and students’<br />

homes<br />

• Recording, tracking and<br />

issuance of reminders for<br />

late returns<br />

• Protection against theft of<br />

library materials<br />

• Centralised control and<br />

online monitoring of video<br />

shows by IT demonstrator<br />

Table 3: Summary of Information on Educational Resource and its Operational Functions<br />

3.4 External Resources <strong>Management</strong><br />

Information Required<br />

The External Resources component deals with the management of resources<br />

and linkages to constituencies outside the school. The “External Resource”<br />

portion of the SSMS shall enable access to external databases for the retrieval of<br />

real-time and recorded data and the monitoring of the access to external<br />

resources by users.<br />

Operational Function<br />

1. Learning materials from external sources • External linkages to other<br />

agencies such as mass<br />

media, museums, media<br />

centres, and institutions<br />

of higher learning.<br />

2. General and academic materials • External linkages to other<br />

educational resources.<br />

Table 4: Summary of Information on External Resource and its Operational Functions<br />

15


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

3.5 Financial <strong>Management</strong><br />

Operational Function<br />

1. <strong>School</strong> Accounts Maintenance <strong>System</strong>s: audit reports,<br />

debit and credit entries, monthly balances, analysis<br />

of financial items, sub accounts, fees collection,<br />

accounts tracking.<br />

2. Purchasing system: Information on invoices,<br />

authorisation of payments, quotation requests<br />

• Record, retrieval and<br />

dissemination to relevant<br />

agencies and offices, with<br />

restricted access to some.<br />

• Preparation formats,<br />

record, retrieval and<br />

dissemination<br />

3. Salary: payment and receipt • Record, retrieval and<br />

dissemination<br />

4. <strong>School</strong> assets and revenue from usage • Record, tracking, retrieval<br />

and accounting<br />

5. Inventory: maintenance, schedule of usage, prices • Record, scheduling,<br />

retrieval and monitoring<br />

Table 5: Summary of Information on <strong>School</strong> Finance Functions.<br />

The Financial <strong>Management</strong> component handles the fiscal management portion<br />

of the SSMS. The school financial system includes budgeting, reporting,<br />

accounting, procurement, project funding, long term planning, audit and<br />

control. The solution shall:<br />

• generate customised reports periodically as required by various governing<br />

agencies for checking and monitoring purposes. Some such reports are<br />

the monthly balance of statement, bank reconciliation, cash-book entry in<br />

terms of income and expenditure, monthly and annual audit reports.<br />

• interface to Ministry of Education finance accounting system to provide<br />

financial information to district, state and federal levels.<br />

• have a fixed asset system that gathers data and reports on the acquisition,<br />

transfer and use of school funds.<br />

• provide a budget development system with an on-line entry of budget<br />

development information by school, district and state education offices<br />

and the federal authorities.<br />

• easily track, update and review assets leading to efficient and effective<br />

accounting with:<br />

− an account payable system for procurement that uses purchase orders,<br />

and that receives information and invoices to authorise payment to<br />

vendors;<br />

− an ability to generate check transmittal and warrants after check runs<br />

and integrate appropriate payable transactions into the general<br />

accounting system;<br />

• have validation and fund checking capabilities<br />

• shall track cash flows and make on-demand audit and other reports as<br />

required by the district, state and federal authorities.<br />

16


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• have a system to monitor the hostel financial management (for fully and<br />

semi-residential schools) such as finances related to food and<br />

accommodation.<br />

3.6 Facilities <strong>Management</strong><br />

The Facilities <strong>Management</strong> component is involved in maintaining and<br />

managing the utilisation of school facilities. The Facilities <strong>Management</strong><br />

portion of the SSMS shall:<br />

• enable the tracking of usage and maintenance of all forms of school<br />

facilities such as sports facilities, halls and classrooms, hostels, science<br />

equipment and computers. This includes the scheduling of required<br />

maintenance and servicing of equipment<br />

• enable the management of all inventory, fixed assets and facilities with a<br />

built-in reporting system<br />

• enable the scheduling of the usage of facilities by staff, students and other<br />

authorised parties.<br />

Information<br />

Operational Function<br />

1. • Inventory of facilities with item specifications • Record, retrieval, tracking and<br />

reporting<br />

2. • Scheduling of usage facilities • Record, retrieval, tracking and<br />

reporting<br />

3. • Budgeting for maintenance • Record, retrieval, tracking and<br />

reporting<br />

Table 6: Summary of Information on <strong>School</strong> Facilities <strong>System</strong>’s Functions<br />

3.7 Human Resources <strong>Management</strong><br />

The Human Resources <strong>Management</strong> component supports the organisation,<br />

planning and implementation of school staff development programmes. The<br />

“Human Resource” portion of the SSMS shall:<br />

• allow the input and retrieval of data on teachers and supporting staff.<br />

• have a combination of a payroll/personnel system. The payroll functions<br />

perform along with the related personnel functions of recruiting,<br />

employment, staffing, certification records, professional development<br />

records, records on discipline and other related matters.<br />

• be able to access a payroll and personnel system that combines payroll<br />

information with records on recruiting, employment, staffing, certification,<br />

professional development, discipline, and other related matters.<br />

• be able to generate monthly and annual reports to district and state<br />

education offices, as well as to relevant divisions of the Ministry of<br />

Education.<br />

• enable the recording and planning of staff development programmes.<br />

17


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• enable the input and retrieval of staff’s personal biodata, records of<br />

service, promotions, achievements, courses attended and health.<br />

• record attendance and participation details on staff members’ curricular<br />

and co-curricular duties.<br />

• enable the transfer of personal files from school to other institutions when<br />

staff members are transferred, or retire, or leave the service.<br />

Information Operational Function<br />

1. • Teacher and support staff<br />

profiles<br />

• Analysis for basic statistics on teachers, students,<br />

in terms of background, categories and ability to<br />

• Individual data files<br />

sort according to various variables, and<br />

• Salary records and updates<br />

determination of teacher–student ratio<br />

• Service records and updates • Record and retrieval<br />

• Teaching licence records<br />

• Medical records<br />

• Records of expertise and<br />

professional achievements.<br />

• Staff development records for<br />

each teacher<br />

2. Incorporation of confidential staff<br />

appraisals<br />

3. <strong>System</strong> to determine manpower<br />

needs<br />

4. File transfer between schools and<br />

various divisions of the Ministry<br />

of Education.<br />

• Record, retrieval and reporting, with restricted<br />

access to confidential reports<br />

• Projections on school’s student population and<br />

analysis of future need for staff, based on current<br />

and available previous data, record and retrieval<br />

• Record, retrieval and dissemination<br />

Table 7: Summary of Information on Human Resource <strong>System</strong>’s Functions<br />

3.8 Security <strong>Management</strong><br />

Information<br />

The Security <strong>Management</strong> component helps manage the safety of staff and<br />

students when they are at school, as well as the safety of the school itself.<br />

Requirements for a comprehensive IT security solution are described in the<br />

C<strong>RFP</strong> for <strong>Smart</strong> <strong>School</strong> <strong>System</strong>s Integration. This Security portion of the SSMS<br />

shall consist of a security monitoring system that:<br />

• identifies authorised visitors and detects trespassers;<br />

• signals early warnings against break-ins, fires, leakage of gas and other<br />

poisonous fumes in science laboratories.<br />

• protection against vandalism.<br />

Operational Function<br />

1. Security of school grounds, staff<br />

and students during and after<br />

school hours.<br />

Monitoring of school access points<br />

18


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

Table 8: Summary of Information on <strong>School</strong> Security <strong>System</strong>’s Functions<br />

3.9 Technology <strong>Management</strong><br />

Technology functions of the school can be categorised into the following:<br />

• IT management. The requirements for a comprehensive IT <strong>Management</strong><br />

solution is described in the document C<strong>RFP</strong> for <strong>Smart</strong> <strong>School</strong> <strong>System</strong>s<br />

Integration.<br />

• Non-IT technology management. Descriptions of these components can be<br />

found in the document, C<strong>RFP</strong> for <strong>Smart</strong> <strong>School</strong> Technology Infrastructure.<br />

Responding Organisations are invited to propose solutions that may assist<br />

in the management of these technologies.<br />

3.10 Hostel <strong>Management</strong><br />

This component of school management is applicable only to fully residential or<br />

semi-residential schools. The solution shall:<br />

• enable the input and retrieval of data on hostel fees collection, (income and<br />

expenditure)<br />

• input records of usage of rooms by boarders as well as rental by other<br />

agencies<br />

• input records of student boarders, their welfare e.g., health, and their<br />

activities outside school hours, including records of their days in and out<br />

of school<br />

• record the daily and weekly menus and food supply<br />

• record usage and maintenance of hostel facilities such as dormitories,<br />

dining halls and kitchen facilities<br />

• record inventories of hostel facilities and monitor their movement.<br />

3.11 Summary of communications requirements<br />

The following tables summarise some of the communication requirements for<br />

the 9 functional areas of the SSMS. The tables show participants in the<br />

information exchange between the school administration, staff, students,<br />

parents and the community, district education offices, state education<br />

departments and the various divisions of the Ministry of Education. To reduce<br />

repetition, communications, which involve a two-way exchange, are only listed<br />

once.<br />

The following abbreviations are used in the tables:<br />

GOV --<br />

<strong>School</strong> Governance<br />

SA -- Student Affairs <strong>Management</strong><br />

EDU -- Educational Resource <strong>Management</strong><br />

EXT -- External Resource <strong>Management</strong><br />

FIN -- Financial <strong>Management</strong><br />

FAC -- Facilities <strong>Management</strong><br />

19


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

HR -- Human Resources <strong>Management</strong><br />

SEC -- Security <strong>Management</strong><br />

TEC -- Technology <strong>Management</strong><br />

<strong>School</strong>-wide broadcast of information From To<br />

GOV<br />

SA<br />

EDU<br />

EXT<br />

FIN<br />

FAC<br />

HR<br />

SEC<br />

TEC<br />

• Information on school policy Admin Teachers &<br />

Students<br />

• General Orders and government circulars<br />

(accept restricted ones)<br />

• Teaching and non-teaching tasks schedule Admin Teachers &<br />

Students<br />

• Analysis of students' academic achievement Admin Teachers &<br />

according to class, grades and levels<br />

Students<br />

• Resources available for teaching and Admin Teachers &<br />

learning<br />

Students<br />

• Training, seminars and workshops for<br />

teachers and supporting staff<br />

• Announcements and events Admin Entire<br />

<strong>School</strong><br />

ü ü ü ü ü ü ü ü ü<br />

Admin Teachers ü ü ü ü ü ü<br />

ü ü ü ü ü ü ü<br />

ü<br />

ü<br />

ü ü ü ü ü<br />

Admin Teachers ü ü ü ü ü<br />

ü ü ü ü ü ü ü ü ü<br />

Common information exchange between<br />

parents, community and school From To<br />

administration.<br />

• <strong>School</strong>’s academic and co-curricular Admin Parents &<br />

achievements<br />

Public<br />

• <strong>School</strong> and hostel facilities Admin Parents &<br />

Public<br />

• Funds and scholarship Admin Parents &<br />

Public<br />

• Book loan scheme Admin Parents &<br />

Public<br />

• Opportunities for career development. Admin Parents &<br />

Public<br />

• Parent-Teachers Association activities Teachers Parents &<br />

Public<br />

• <strong>School</strong>-based and external assessment types Admin Parents &<br />

and schedules<br />

Public<br />

• Curriculum content Teachers Parents &<br />

Public<br />

• Assignments Teachers Teachers,<br />

Parents &<br />

Public<br />

• Co-curricular activities in school Teachers Parents &<br />

Public<br />

• Public security measures Admin Parents &<br />

Public<br />

• Resources available for teaching and<br />

learning<br />

• Training, seminars and workshops for<br />

teachers and supporting staff<br />

• Educational resources for fieldwork that<br />

can be utilised in Teaching and learning<br />

• Feedback from parents and<br />

Community on management of school<br />

Teachers<br />

Admin<br />

<strong>School</strong><br />

staff<br />

Parents<br />

& Public<br />

Teachers,<br />

Parents &<br />

Public<br />

Teachers,<br />

Parents &<br />

Public<br />

Parents &<br />

Public<br />

GOV<br />

SA<br />

EDU<br />

EXT<br />

FIN<br />

FAC<br />

HR<br />

SEC<br />

ü ü ü<br />

ü ü ü ü ü<br />

ü ü ü ü<br />

ü ü ü ü<br />

ü ü ü<br />

ü ü ü ü ü<br />

TEC<br />

ü ü ü ü<br />

ü<br />

ü<br />

ü ü ü<br />

ü ü ü<br />

ü ü ü ü ü<br />

ü ü ü<br />

ü ü ü<br />

ü ü ü ü<br />

Admin ü ü ü ü<br />

20


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

(such as changes in internal school policy)<br />

Information which requires<br />

secure, privileged access<br />

From<br />

To<br />

GOV<br />

SA<br />

EDU<br />

EXT<br />

FIN<br />

FAC<br />

HR<br />

SEC<br />

TEC<br />

• Individual students’ profiles Admin Parents, MoE, State<br />

Edu.Dept, & District<br />

Edu. Office<br />

• Discipline reports Admin Parents, MoE, State<br />

Edu.Dept, & District<br />

Edu. Office<br />

• Records and reports on students<br />

discipline outside schooling<br />

hours<br />

Admin<br />

Parents,&<br />

Community and<br />

public safety<br />

organisations (e.g<br />

police, Welfare Dept)<br />

• Counselling reports Admin Parents,&<br />

Community and<br />

public safety<br />

organisations (e.g<br />

police, Welfare Dept)<br />

• Individual academic and cocurricular<br />

progress reports<br />

Admin<br />

Parents, MoE, State<br />

Edu.Dept, & District<br />

Edu. Office<br />

• Financial information Admin MoE, State Edu.Dept,<br />

& District Edu. Office<br />

ü ü ü<br />

ü ü ü<br />

ü ü ü<br />

ü ü ü<br />

ü ü ü<br />

ü ü ü<br />

Information exchange between<br />

individuals and groups<br />

From<br />

To<br />

GOV<br />

SA<br />

EDU<br />

EXT<br />

FIN<br />

FAC<br />

HR<br />

SEC<br />

TEC<br />

• Lesson plan strategy Teachers Teachers<br />

within a<br />

school and<br />

other<br />

schools<br />

• <strong>School</strong>-based research <strong>School</strong><br />

staff and<br />

students<br />

• Exchange programs <strong>School</strong><br />

staff and<br />

students<br />

<strong>School</strong><br />

staff and<br />

students<br />

from other<br />

schools<br />

<strong>School</strong><br />

staff and<br />

students<br />

from other<br />

schools<br />

ü ü ü<br />

ü ü<br />

ü ü ü<br />

21


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

4 Technical Requirements<br />

This section describes technical requirements that are common across all C<strong>RFP</strong>s, as well as<br />

specific requirements that are particular to this C<strong>RFP</strong>.<br />

4.1 Application Architecture<br />

All applications to be deployed in the <strong>Smart</strong> <strong>School</strong>s shall use an n-tiered<br />

application architecture. Figure 1 shows the minimum three tiers which any<br />

application shall split into. These three tiers are:<br />

• User-Interface<br />

• Application services<br />

• Data and database services<br />

Specific applications shall then consolidate or distribute services as required<br />

when performing particular optimisations. These requirements shall likely<br />

evolve over time as additional applications are introduced, or the loads on a<br />

particular server increase. <strong>For</strong> example, application and database services for a<br />

particular application may initially be deployed on the same platform, with<br />

database services migrating to another server later for performance and<br />

consolidation reasons.<br />

This modular architecture provides a flexible, extensible and open basis for<br />

deploying applications, enabling introduction or substitution of individual<br />

components. Modular architectures require standard interfaces and protocols<br />

APPLICATION ARCHITECTURE<br />

New<br />

Applications<br />

Application<br />

Client<br />

+<br />

UI<br />

Teaching<br />

Learning<br />

Materials<br />

<strong>School</strong><br />

<strong>Management</strong><br />

Central<br />

Assessment<br />

Databases<br />

Client P.O.A.<br />

Device<br />

Application Services<br />

<strong>School</strong><br />

Data Repositories<br />

Figure 1: Three-Tier Application Architecture<br />

22


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

to ensure interoperability between application tiers. Some of these standards are<br />

described in the document, <strong>Smart</strong> <strong>School</strong> Information Technology Policy and<br />

Standards. Section 4.3 describes general standards compliance requirements that apply<br />

across all C<strong>RFP</strong>s.<br />

Responses:<br />

• Responding Organisations shall acknowledge requirements for an n-tiered<br />

Application Architecture.<br />

• Responding Organisations shall state how their proposed solutions comply<br />

with the prescribed application architecture.<br />

4.2 Application Framework<br />

While the previous section describes the preferred three-tier application architecture,<br />

this section describes a framework for organising the applications needed by the <strong>Smart</strong><br />

<strong>School</strong>s. Figure 2 shows the desired <strong>Smart</strong> <strong>School</strong> Application Framework.<br />

All applications shall adhere to the <strong>Smart</strong> <strong>School</strong> Application Framework, which has<br />

the following features:<br />

• A Common User Front End, which provides a standard means for<br />

USER<br />

ACCESS<br />

Common User Front End<br />

APPS<br />

Assessment<br />

<strong>School</strong> <strong>Management</strong><br />

<strong>System</strong><br />

Teaching-Learning<br />

Materials<br />

DATA<br />

Data<br />

bases<br />

Databases<br />

Data<br />

bases<br />

Figure 3: <strong>Smart</strong> <strong>School</strong> Application Framework<br />

23


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

accessing all <strong>Smart</strong> <strong>School</strong> applications.<br />

• Various applications, which are specified in the C<strong>RFP</strong>s for Teaching-<br />

Learning Materials, Assessment, <strong>System</strong>s Integration and <strong>Smart</strong> <strong>School</strong><br />

<strong>Management</strong> <strong>System</strong>.<br />

• Separate databases: In some cases, applications may use several databases.<br />

However, at times a centralised, consolidated database may be more<br />

appropriate. Examples include student personal data and persistent data<br />

that exceed the lifetime of individual applications. In these instances, the<br />

application shall support integration with external databases. Equally, an<br />

application shall also support and facilitate access by other applications to<br />

its own databases.<br />

The application framework needs to have the following features:<br />

• Portability: The ability of application systems to operate on various<br />

platforms regardless of manufacturer or operating system.<br />

• Flexibility: The capability to take advantage of new technologies and<br />

resources, and be implemented in changing environments. Flexibility<br />

contributes to lower overall costs by allowing procurement of software and<br />

hardware from multiple sources.<br />

• Interoperability: The ability to work together on a network, connect with,<br />

and share data and processes with computers and applications from other<br />

vendors.<br />

• Scalability: The capability for application systems to migrate as a client or<br />

server to machines of greater or lesser power, depending upon<br />

requirements, with little or no change to the underlying components.<br />

• Usability: The ease of use of applications systems to enhance and support,<br />

rather than limit or restrict, school processes. Human interfaces need to be<br />

intuitive and consistent with other application systems in the environment,<br />

and within themselves in both purpose and use.<br />

• Manageability: The applications, hardware and software shall be<br />

manageable and easy to operate.<br />

Responses:<br />

• Responding Organisations shall acknowledge requirements specified in<br />

this section.<br />

• Responding Organisations shall describe in detail their proposed<br />

application framework and the extent to which it meets or exceeds the<br />

specified requirements.<br />

• Responding Organisations shall describe their approaches to providing<br />

a common user front end<br />

• <strong>For</strong> the First Stage, Responding Organisations shall describe features of<br />

their solutions that support the requirements for portability, flexibility,<br />

interoperability, scalability, usability and manageability.<br />

• <strong>For</strong> the Second Stage, the Unbound Consortium shall describe the extent<br />

to which all <strong>Smart</strong> <strong>School</strong> applications shall be accessed from the<br />

common user front end.<br />

24


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

4.3 Standards Compliance<br />

An open standards-based technology architecture is strongly preferred, and<br />

although Responding Organisations may refer to the technology standards and<br />

guidelines specified in the document, <strong>Smart</strong> <strong>School</strong> Information Technology Policy<br />

and Standards, the following principles shall serve as the basis for the use of<br />

mechanisms or standards to be utilised in solutions proposed:<br />

• Open, barrier free, flexible, architecturally neutral technologies that are<br />

accessible and available to all<br />

• Availability of solutions conformant with the standard, from multiple<br />

vendor sources, in multiple implementations, across multiple<br />

heterogeneous platforms.<br />

• Standards that are non-proprietary and do not lock a solution to only one<br />

hardware platform or operating system<br />

“Open systems” refers to products and technologies that have been designed<br />

and implemented according to open interfaces. Interfaces are considered open<br />

if their specifications are readily and non-discriminatorily available to all<br />

suppliers, service providers, and users, and are revised only with timely notice<br />

and public process.<br />

Responses:<br />

• Responding Organisations shall acknowledge requirements for the<br />

standards compliance and conformance as specified in this C<strong>RFP</strong> and<br />

the <strong>Smart</strong> <strong>School</strong> Information Technology Policy and Standards<br />

document.<br />

• Responding Organisations shall state the standards they propose to use<br />

for the following areas specified in the <strong>Smart</strong> <strong>School</strong> Information<br />

Technology Policy and Standards document, as they apply:<br />

♦<br />

♦<br />

♦<br />

♦<br />

♦<br />

♦<br />

♦<br />

♦<br />

Devices<br />

User services<br />

Logic services<br />

Data services<br />

Communication<br />

Inter-process communication<br />

Application development<br />

<strong>System</strong>s management<br />

• Responding Organisations shall also list the standards they propose to<br />

use for the areas specified in the document, <strong>Smart</strong> <strong>School</strong> Information<br />

Technology Policy and Standards and this C<strong>RFP</strong>.<br />

• Responding Organisations shall state if and how elements of their<br />

proposed solutions comply with the Open <strong>System</strong>s requirements<br />

specified above, and, if not, justify why they have not seen the need to<br />

comply.<br />

25


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

4.4 Integration Requirements<br />

Responding Organisations shall describe in detail all the access and integration<br />

mechanisms supported by the proposed solutions. The mechanisms described<br />

shall address the possible implementation scenarios of centralised or<br />

distributed service tiers. Where multiple options are available for a particular<br />

mechanism, Responding Organisations shall indicate the recommended and<br />

preferred option, and justify that choice.<br />

Responding Organisations shall also address the following areas in their<br />

statement of the applicable standards that each mechanism is based upon:<br />

• The interconnection of hardware platforms (computers, network devices,<br />

audio-visual equipment).<br />

• The transmission of information between two or more applications.<br />

• The retrieval, insertion or update of information from or into an external<br />

data repository or database by any application.<br />

• The sharing of information between two or more applications.<br />

• The invocation of one application by another application in both<br />

centralised and distributed service implementations.<br />

• The communication between different service layers of an n-tier<br />

application.<br />

• The management of network devices and computer platforms.<br />

Responses:<br />

• Responding Organisations shall acknowledge requirements specified in<br />

this section.<br />

• Responding Organisations shall state in detail their responses to all<br />

requirements stated in this section.<br />

4.5 Security Considerations<br />

A comprehensive security strategy is one key element that spans the Ministry<br />

of Education, schools, and all other constituencies requiring system access.<br />

This section outlines broad security requirements that shall be addressed by<br />

Responding Organisations’ proposed solutions.<br />

All proposed applications and systems shall include security features that shall<br />

• Ensure confidentiality of data and communications.<br />

• Build in authorisation levels and controls so only appropriate people and<br />

systems shall access other systems, networks, applications, data, services<br />

and system resources.<br />

• Ensure original data and communications are not compromised, lost or<br />

tampered with.<br />

• Prove data origin from individuals and systems.<br />

• Prevent transaction denial.<br />

26


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• Provide audit trails and log security events, including different types of<br />

access attempts.<br />

The <strong>Smart</strong> <strong>School</strong>s security infrastructure requirements for enterprise-level,<br />

multi-vendor, multi-platform, distributed security are specified in the<br />

document, C<strong>RFP</strong> for <strong>Smart</strong> <strong>School</strong> <strong>System</strong>s Integration.<br />

Responses:<br />

• Responding Organisations shall describe security features of their<br />

solutions that support the requirements specified in this document and<br />

the relevant standards in the document, <strong>Smart</strong> <strong>School</strong> Information<br />

Technology Policy and Standards.<br />

• Responding Organisations shall specify how their solutions integrate<br />

into security infrastructures by:<br />

− Describing in detail the available options to integrate into security<br />

infrastructures for the First Stage of the C<strong>RFP</strong> process.<br />

− Describing in detail the specific options required to integrate all<br />

solutions into the framework of its proposed security architecture<br />

for the Second Stage of the C<strong>RFP</strong> process.<br />

4.6 Platform Support<br />

The Responding Organisation shall describe in detail all the hardware<br />

platforms and operating environments that their proposed solutions run on.<br />

Details to be furnished shall include the specific revisions of each software<br />

component proposed and the corresponding models of hardware platform and<br />

revision of operating system that the said component can operate on.<br />

Responses:<br />

• Responding Organisations shall acknowledge requirements specified in<br />

this section.<br />

• Responding Organisations shall list all proposed software component<br />

revisions together with all the specific hardware platforms and<br />

operating system revisions that support them.<br />

4.7 <strong>System</strong> Sizing and Capacity Planning<br />

To assist Responding Organisations size the equipment and applications<br />

required for the first phase of 90 <strong>Smart</strong> <strong>School</strong>s, information on the school<br />

population and required levels of technology to be deployed in these schools,<br />

are described in the document, The Malaysian <strong>Smart</strong> <strong>School</strong> Implementation Plan.<br />

It is the Responding Organisation’s responsibility to make all examinations<br />

necessary in order to ascertain all factors, inquiries and questions that might<br />

affect the Responding Organisation’s specific proposals. The Responding<br />

Organisation shall ascertain the specific detailed information it requires to<br />

make informed and accurate design, configuration and sizing decisions.<br />

Responding Organisations shall propose strategies to proactively manage the<br />

growth of data repositories and databases, systems and other technology<br />

infrastructure, such as network capacity. Responding Organisations shall<br />

27


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

propose capacity planning mechanisms to meet these growth management<br />

requirements.<br />

Data management and retention issues involve, but are not limited to, the<br />

following areas:<br />

• Teaching-learning materials<br />

• Persistent student related information that shall be retained throughout the<br />

students’ enrolment in a school.<br />

• Students’ portfolio material.<br />

• <strong>School</strong> leavers’ information that may be referred to in later years.<br />

Examples include students requiring transcripts of their school records and<br />

testimonials.<br />

• Staff related information.<br />

• Financial information.<br />

• Communications<br />

Responses:<br />

• In the Second Stage of the C<strong>RFP</strong> process, Unbound Consortium shall<br />

describe in detail the specific system configurations required for all<br />

proposed components, together with the assumptions upon which they<br />

are based.<br />

• In the Second Stage of the C<strong>RFP</strong> process, Unbound Consortium shall<br />

describe in detail the remaining growth capacity of the specific solutions<br />

proposed.<br />

• Responding Organisations shall propose specific growth management<br />

strategies and solutions to meet the immediate and long-term<br />

requirements of the <strong>Smart</strong> <strong>School</strong>s.<br />

4.8 Multiple Language Support<br />

The language support requirements for each application shall be specified in<br />

the relevant C<strong>RFP</strong> document. In general, language support provisions in the<br />

solutions proposed shall address user input and output methods. Examples of<br />

input methods include keyboard and speech-to-text. Examples of output<br />

methods include screen and printer output.<br />

Responses:<br />

• Responding organisations shall state the multiple language support<br />

capabilities of their proposed solutions.<br />

4.9 Risk Assessment Statement<br />

In the Second Stage of the C<strong>RFP</strong> process, Responding Organisations shall<br />

include in their proposals a Risk Assessment Statement that describes the<br />

potential impact on <strong>Smart</strong> <strong>School</strong> operations if a component or system fails.<br />

The Risk Assessment Statement shall describe at least the following:<br />

• Points of potential failure in the system, including hardware and software,<br />

and telecommunications equipment<br />

28


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• Software integration points defining all software interfaces between key<br />

applications, the operating system, programmable hardware, and I/O<br />

(Input/Output) subsystems.<br />

• Which services would become unavailable and who would be impacted<br />

when all known system or subsystem outages occur.<br />

• Which services would become unavailable and who would be impacted by<br />

outages of all known telecommunications systems.<br />

Responses:<br />

• Responding Organisations shall use the following format in supplying a<br />

Risk Assessment Statement:<br />

Components and <strong>System</strong>s in<br />

<strong>Smart</strong> <strong>School</strong><br />

Impact on <strong>Smart</strong> <strong>School</strong><br />

Operations from<br />

Component/<strong>System</strong> Failure<br />

4.10 Technical Service Level<br />

The Technical Service Level requirements are outlined in the document, C<strong>RFP</strong><br />

for <strong>Smart</strong> <strong>School</strong> <strong>System</strong>s Integration. In brief, these requirements include<br />

information about<br />

• Technical specifications of all deliverables<br />

• Communication mechanisms between parties<br />

• Implementation plans, schedules and milestones<br />

• Conditions for service delivery<br />

• Measures of user satisfaction<br />

• Performance milestones<br />

• Process and people management<br />

• Quality, accuracy and reliability measures<br />

• Maintenance plans<br />

• Problem-resolution mechanisms, processes and responses<br />

• Risks and associated credits or penalties<br />

• Resources required (technologies, facilities and people)<br />

Responses:<br />

• Responding Organisations shall provide detailed plans for meeting the<br />

project’s Technical Service Level requirements for the Second Stage of<br />

the C<strong>RFP</strong> evaluation process.<br />

29


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

5 Implementation Requirements<br />

5.1 Project <strong>Management</strong> Methodology<br />

The Responding Organisation shall describe the project management<br />

methodology to be undertaken in the pilot project in order to meet the<br />

schedule as well as the quality requirements of the project. In addition to the<br />

systems design and implementation activities, the project management<br />

methodology shall include the tasks and activities involved in the other areas<br />

of the implementation requirements namely:<br />

• Project Team Structure<br />

• Risk <strong>Management</strong> Plan<br />

• Quality <strong>Management</strong><br />

• Change <strong>Management</strong> Plan<br />

• Training Plan<br />

• Acceptance Testing Plan<br />

• Transfer of Technology Plan<br />

In addition, this section shall also describe the following:<br />

• Implementation Schedule<br />

• Key Milestone Dates<br />

• Key Deliverables<br />

• Workday and Staffing Estimates<br />

Response:<br />

• Responding Organisations shall describe their project management<br />

methodology, including their proposed implementation schedule, use of<br />

resources, milestones and deliverables.<br />

5.2 Project Team Structure<br />

In order to meet the expectations of the pilot project, a sound project<br />

organisation structure shall be established. The Responding Organisation shall<br />

propose the project team structure and the relationships between the various<br />

functions of the structure. Where applicable, the Responding Organisation<br />

shall describe the evolution of project team structure as the project progresses.<br />

In addition, the Responding Organisation shall identify the resources, their<br />

roles and responsibilities and skills needed to execute the activities and tasks<br />

identified. Furthermore, the project organisation shall support the transfer of<br />

technology (See Section 5.8) and change management (See Section 5.5) to be<br />

undertaken in the project.<br />

Response:<br />

• Responding Organisations shall describe their project organisation<br />

structure, including resources, roles and responsibilities.<br />

30


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

5.3 Risk <strong>Management</strong> Plan<br />

The Responding Organisation shall provide a risk management strategy which<br />

shall be used in this pilot project describing the approach for risk identification,<br />

analysis, management and mitigation. Following that, the Responding<br />

Organisation shall demonstrate its understanding of the risks involved by<br />

identifying the risks that constitute a barrier, both potential and real, to the<br />

accomplishment of the <strong>Smart</strong> <strong>School</strong>s or the pilot project goals and objectives.<br />

5.4 Quality <strong>Management</strong><br />

In this section the Responding Organisation is to describe the quality assurance<br />

plan describing the procedures, methodologies and policies that the<br />

organisation shall adopt in order to ensure the quality of the deliverables and<br />

services to be provided in the execution of the pilot project.<br />

5.5 Change <strong>Management</strong> Plan<br />

With the implementation of the pilot project, it is critical that the Responding<br />

Organisation manage the changes the people involved in the operations shall<br />

be experiencing. Of major impact are business processes, technology and<br />

organisation. In this section, the Responding Organisation shall describe the<br />

approach and outcomes that the it shall use to help the end users manage this<br />

critical change effort.<br />

5.6 Training Plan<br />

The success of the pilot project lies not only in the technical and functional<br />

capability, but also in the ability of the user population to effectively use the<br />

system and operate in the new environment. In this section, the Responding<br />

Organisation shall propose a training program that describes the method for<br />

training for the end users. Specific training requirements are detailed in Section<br />

6.<br />

5.7 Acceptance Testing Plan<br />

In this section, the Responding Organisation shall describe the test plan that<br />

will address the various aspects of testing to be implemented in this pilot<br />

project. The test plan shall describe the high level testing strategy for the pilot<br />

project, the approach and to be adopted, the test environment to be set up, the<br />

resources required for the testing as well as the implementation schedule for<br />

the tests.<br />

5.8 Technology Transfer Plan<br />

In this section the Responding Organisation shall describe the technology<br />

transfer program to be implemented in this pilot project. The description of the<br />

approach, process and the methods for ensuring technology is being<br />

transferred to government and local companies (either in the consortium or the<br />

agency itself) during the pilot project shall be described.<br />

The Responding Organisation shall show understanding that the <strong>Smart</strong> <strong>School</strong><br />

project is a long-term one and shall outline their future plans regarding<br />

research, development and technology transfer. Furthermore, bearing in mind<br />

31


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

that the <strong>Smart</strong> <strong>School</strong> project is an MSC flagship application, the Responding<br />

Organisation shall outline any present and planned future involvement with<br />

the MSC, and how they see this involvement with respect to their technology<br />

transfer plan.<br />

The Responding Organisation shall outline how it plans to implement (if<br />

present):<br />

• Details as to how knowledge is to be conveyed,<br />

• The level of co-operation with local companies, universities and<br />

government agencies,<br />

• The level and details of research and development to be undertaken<br />

• Training programs<br />

• Joint development efforts.<br />

5.9 Implementation Strategies<br />

The Responding Organisation shall address how they plan to implement their<br />

solution, given that schools have been designated various levels of technology.<br />

In particular, they shall outline:<br />

• How they plan to stage the implementation to all the schools<br />

• How their solution differs over the different levels of technology<br />

• Implications on existing solutions and processes in a school as a it moves<br />

from one technology level to a higher level<br />

• Their change plan as a school migrates through the different levels of<br />

technology, bearing in mind the rapid change of the technology itself. This<br />

plan shall be linked to their R&D program (if any).<br />

32


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

6 Training Programs<br />

6.1 Overview<br />

Human resource development represents a key element in the implementation<br />

of <strong>Smart</strong> <strong>School</strong>s. A comprehensive training strategy covering both short-term<br />

and long-term measures need to be developed to ensure the continuing<br />

professional growth and development of Principals/Headmasters and the<br />

school administrative staff.<br />

6.2 Training strategy<br />

Training for <strong>Smart</strong> <strong>School</strong> management teams consists of two phases. The<br />

Ministry of Education shall provide the first phase of training which<br />

introduces all school administrators and management teams to the goals and<br />

visions of <strong>Smart</strong> <strong>School</strong>. This training, based on the cascade model, shall be<br />

provided to <strong>Management</strong> Trainers that comprises officers of the National<br />

Institute of Educational <strong>Management</strong> and Leadership (Institut Aminuddin<br />

Baki), and other officers identified by the Ministry. In cascade fashion, highly<br />

skilled <strong>Management</strong> Trainers teach others to train, who in turn train the other<br />

members of the <strong>Smart</strong> <strong>School</strong> administrative teams. This programme focuses<br />

on the training and development of generic skills required of <strong>Smart</strong> <strong>School</strong><br />

Principals and Headmasters, which are:<br />

1. Facilitation Skills<br />

2. Motivational Skills<br />

3. Values Development Skills<br />

4. Correct Usage of Language<br />

5. Critical and Creative Thinking Skills<br />

6. Basic Information Technology Skills<br />

7. Assessment and Evaluation Skills<br />

8. Study Skills<br />

The second phase of training shall be conducted by the successful Responding<br />

Organisation. The focus of this phase is on:<br />

1. Utilisation of Training Modules prepared for the SSMS<br />

2. Development of a Training Programme for fifty (50) <strong>Management</strong> Trainers<br />

which involves training the trainers and supervising them in at least one<br />

session of their training of <strong>Smart</strong> <strong>School</strong> management teams.<br />

6.3 Training Facilities<br />

The Responding Organisation shall ensure that the training facilities are<br />

compatible with and highly similar to the facilities that the school management<br />

team will use in their actual administrative tasks.<br />

33


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

6.4 Training schedule<br />

The Training schedule should meet the requirements of the overall<br />

implementation schedule outlined for <strong>Smart</strong> <strong>School</strong>s in the document, The<br />

Malaysian <strong>Smart</strong> <strong>School</strong> Implementation Plan. The Responding Organisation shall<br />

propose a timeline to train the <strong>Management</strong> Team.<br />

6.5 Training venue<br />

The Responding Organisation shall propose training venues subject to the<br />

approval of the Ministry of Education.<br />

6.6 Training Modules<br />

The Responding Organisations shall submit detailed Training Modules for<br />

inducting and training <strong>Smart</strong> <strong>School</strong> management team into the use of the<br />

SSMS. These Training Modules, which shall be used by the <strong>Management</strong><br />

Trainers, shall possess the following features:<br />

6.6.1 Training Design<br />

The Training Module shall provide clear instructions for use according to<br />

a variety of andragogical strategies and processes. Adequate<br />

commentaries shall be included to ensure that the training design is<br />

comprehensible and user friendly.<br />

6.6.2 Resources and References<br />

The Training Modules shall provide the required and appropriate<br />

resources that can be duplicated in adequate numbers without bringing<br />

upon the Government the need to submit to copyright requirements.<br />

These Modules shall also provide a variety of references and other<br />

materials, including relevant web-sites for the further reference of trainers<br />

and <strong>Smart</strong> <strong>School</strong> management team.<br />

6.6.3 Time of Delivery<br />

The Responding Organisation shall indicate the time of delivery of the<br />

Modules.<br />

6.6.4 Training Curriculum<br />

The Training Modules shall give comprehensive coverage of the utilisation<br />

and management of the SSMS software.<br />

6.6.5 <strong>For</strong>mat of Training Modules<br />

The Training Modules shall encompass guidelines for trainers with<br />

clearly stated objectives, instructional procedures and expected outcomes<br />

in an agreed format that would be comprehensible and user friendly, with<br />

provision for trainer creativity. These modules shall also be accompanied<br />

by commentaries on the management practices and strategies as required<br />

by the SSMS software in meeting the goals of <strong>Smart</strong> <strong>School</strong> <strong>Management</strong>.<br />

34


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

6.7 Monitoring and Evaluation<br />

The Trainer Training Programme shall have an in-built evaluation and<br />

monitoring system to evaluate the trained individual’s understandings and<br />

ability to apply the acquired knowledge and skills, meeting the objectives of<br />

the training program. The Responding Organisation shall also propose a plan<br />

to monitor the implementation of the training programme and to evaluate its<br />

success.<br />

6.8 Follow –up programme<br />

The Responding Organisation shall provide a follow-up staff development<br />

programme, which is responsive to changing needs without unreasonable<br />

demands on the Government, financial or otherwise. The Government<br />

however, shall not be obligated in anyway as a result of acceptance of the<br />

proposed programmed.<br />

35


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

7 Maintenance and Support Services<br />

The Government places strong emphasis on adequate and readily available maintenance<br />

and support services from Responding Organisations to maintain the installed systems and<br />

applications in good working order and state of availability.<br />

These maintenance and support services are deemed by the Government to be essential<br />

services in the delivery of a complete SSMS solution. Hence, Responding Organisations shall<br />

meet these requirements in order to merit favourable consideration of their offers.<br />

7.1 Overview<br />

Responding Organisations shall assist users and administrators of the installed<br />

solutions in exploiting, to the fullest possible extent, the capabilities and<br />

features of the SSMS.<br />

Preference shall be given to Responding Organisations that are able to provide<br />

a high level of maintenance and support services including personnel training,<br />

technical advice as well as assistance in operating and maintaining the systems<br />

and applications effectively and efficiently.<br />

Responding Organisations shall describe in detail their proposed approach to<br />

providing maintenance and support services to all 90 <strong>Smart</strong> <strong>School</strong>s, as well as<br />

all other schools in subsequent implementation phases.<br />

Responding Organisations shall state cost information, for any and all<br />

chargeable services, applications and systems, as they relate to the<br />

requirements of this section, in the financial section of its proposal.<br />

Responding Organisations are also reminded of the helpdesk, user support<br />

and maintenance requirements specified in the document, C<strong>RFP</strong> for <strong>Smart</strong><br />

<strong>School</strong> <strong>System</strong>s Integration. In the Second Stage of the C<strong>RFP</strong> evaluation process,<br />

Responding Organisations shall integrate their individual support and<br />

maintenance mechanisms into this framework.<br />

The Government reserves the right, at its own cost, to nominate a third party to<br />

perform preventive and remedial maintenance, as deemed beneficial to the<br />

Government.<br />

The requirements specified in this document shall constitute minimum<br />

requirements.<br />

7.2 Organisational<br />

Responding Organisations’ proposals shall state the following information:<br />

• Organisational information on their global support structure for this<br />

project.<br />

• Organisational information on their Malaysian-based support structure for<br />

this project.<br />

• The extent of their support and maintenance facilities throughout<br />

Malaysia.<br />

• Their approaches to respond to requests for support, and the<br />

corresponding response times, for the various categories of schools and<br />

problems.<br />

36


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• Their approaches to collaborate with the Government’s support staff to<br />

jointly ensure the applications and systems are in good working order at<br />

all times.<br />

• The number of sufficiently trained, skilled and experienced support and<br />

maintenance personnel to be employed in support of this project, where<br />

they shall be located, and profiles of their expertise and experience.<br />

7.3 Coverage<br />

The Responding Organisation shall state<br />

• The period during which the maintenance and repair services offered will<br />

be valid (the Guarantee Period).<br />

• A list of all services that the Responding Organisations deem to be<br />

important for the optimal support and operation of the SSMS.<br />

• Details of maintenance and support services offered, and any charges (if<br />

present) that come into force, after the expiry of the Guarantee Period.<br />

• Policies regarding the provision of urgently required replacement parts,<br />

software fixes, and personnel having specialist technical expertise, that are<br />

not available in Malaysia.<br />

• Details of any applicable software licensing fees.<br />

• The cost (if present) of replacing items, as part of services rendered, both<br />

during and after the Guarantee Period, and the compensation provided if<br />

the items are unavailable.<br />

• The maximum delay to be encountered by the Government when waiting<br />

for the provision of replacement hardware and software items.<br />

7.4 Services<br />

Responding Organisations shall provide information on their service offerings.<br />

Areas of coverage include the following:<br />

7.4.1 Remedial Maintenance Service<br />

On-call maintenance service to be rendered by the Responding<br />

Organisation at the request of <strong>Smart</strong> <strong>School</strong> to diagnose and correct any<br />

malfunction<br />

7.4.2 Preventive Maintenance Service<br />

Maintenance services other than the above-mentioned required by <strong>Smart</strong><br />

<strong>School</strong> to maintain the systems and applications in good working order.<br />

7.4.3 Solution Support and Maintenance<br />

The Responding Organisation shall describe how they plan to:<br />

• Ensure the continued usability of the SSMS applications as the platform<br />

technologies evolve over time.<br />

• Undertake to improve, update, maintain and provide any new releases.<br />

37


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• Perform revisions on any or all systems and applications supplied to meet<br />

new or changed requirements.<br />

• Provide update materials or update patches for all software supplied, and<br />

assistance on how to utilise them.<br />

• Inform the Government should any errors or malfunctions be detected and<br />

advise the Government how to solve the problems caused by such errors<br />

or malfunctions and/or perform actual corrections or bypasses or<br />

undertake all reasonable steps to remedy all or any errors and<br />

malfunctions in the software.<br />

• Design and run system tests and procedures in order to verify and ensure<br />

that the applications and systems are operating correctly and optimally.<br />

• Provide free maintenance, software upgrades and spare parts during the<br />

Guarantee Period<br />

• Supply spare parts or software fixes for maintenance services as required<br />

by <strong>Smart</strong> <strong>School</strong> within a specified time frame<br />

• Supply complete sets of system and user documentation as the<br />

corresponding systems and applications evolve.<br />

• Provide technical advice with respect to the operation and maintenance,<br />

relocation of the system to new sites and other technical issues.<br />

Response :<br />

7.4.4 Miscellaneous<br />

Responding Organisations shall describe:<br />

• Their approach to keep records of all maintenance and repair, including<br />

the commencement, procedure and completion of all maintenance and<br />

repair work, the details of the faults (if any) and how they plan to clearly<br />

distinguish faults detected during preventative maintenance from those<br />

detected outside those periods.<br />

• The extent to which the records will be available for (on-demand)<br />

inspection by the Government.<br />

• The process utilised to provide a receipt of work done, which may include<br />

the time-period of the work, and how this receipt may be acknowledged<br />

by the Government for purposes of payment and as a measure of service<br />

performance.<br />

• Responding Organisations shall acknowledge requirements stated in this section<br />

• Responding Organisations shall state in detail their responses to all requirements<br />

stated in this section<br />

38


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

8 Performance Requirements<br />

Responding Organisations are expected to develop solutions that innovate and demonstrate<br />

their capability to meet performance requirements. Responding Organisations shall clearly<br />

describe the performance specifications for their proposed solutions bearing in mind the<br />

different categories of users and their multiple modes of access over LAN’s and WAN’s<br />

using various access devices. Interactive applications shall provide acceptable user response<br />

and other processing functions shall complete in acceptable time frames as shall be mutually<br />

agreed upon by the Government and the Responding Organisations. High quality service<br />

performance, and consistency of performance, are expected. Solution performance levels<br />

should be maintained in the face of anticipated growth in the number of users and the<br />

amount of data stored. Responding Organisations shall state any assumptions made for the<br />

solutions proposed in the context of their target <strong>Smart</strong> <strong>School</strong> environments.<br />

Response :<br />

• Responding Organisations shall acknowledge requirements stated in this section<br />

• Responding Organisations shall state in detail their responses to all requirements<br />

stated in this section.<br />

• Responding Organisations shall state the issues, if any, for meeting performance<br />

requirements and propose how they plan to overcome each in detail.<br />

39


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

9 External Linkages<br />

9.1 External Databases<br />

<strong>Smart</strong> <strong>School</strong> management requires communication with various external<br />

entities in the Ministry of Education as well as other government agencies.<br />

Various databases exist within the Ministry of Education, some of which shall<br />

require linkages with the SSMS.<br />

Details about these databases, and their integration requirements, shall be<br />

furnished in Second Stage of the C<strong>RFP</strong> evaluation process. Responding<br />

Organisations are reminded of the integration requirements stated in Section<br />

4.<br />

Response :<br />

• Responding Organisations shall acknowledge requirements stated in<br />

this section<br />

• In the Second Stage, Unbound Consortia shall state in detail their<br />

specific solutions to integrate with specified external databases.<br />

40


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

10 Financial Requirements<br />

This portion of the C<strong>RFP</strong> is designed to allow the Responding Organisation to propose<br />

innovative alternative financing solutions that would benefit both the Government and the<br />

Responding Organisation. These might draw on new approaches to price structuring,<br />

payment schemes and business models. The Ministry of Education is open to the adoption<br />

of value-added services that a Responding Organisation could choose to go into as added<br />

revenue streams, provided that the services support the objectives of the <strong>Smart</strong> <strong>School</strong><br />

project.<br />

10.1 Business Model Requirements<br />

Ensuring the success of the <strong>Smart</strong> <strong>School</strong>s project will require more than<br />

developing quality applications for teaching learning, school management, and<br />

assessment. In fact, delivering the project’s full benefit will require robust<br />

support mechanisms and appropriate business models.<br />

<strong>For</strong> the pilot project to be a success, the business model should meet the<br />

following requirements:<br />

• Low Expenses. The government will incur minimal charges, while the<br />

Responding Organisation is providing the essential services. However,<br />

charges to the users are also expected to be nominal.<br />

• Smooth and Timely rollout. The pilot project implementation plan should<br />

provide for a smooth and timely rollout.<br />

• Equal Access. The solutions should encourage the development of an<br />

environment where relevant information will be made equally accessible to<br />

all appropriate parties.<br />

• High Usage. The solutions should foster high usage and widespread<br />

adoption by the Ministry of Education and other relevant parties.<br />

10.2 Business Model<br />

The traditional business model for service delivery assumes the Government<br />

plays a singular role as sole buyer of services. However, there are additional<br />

roles for Responding Organisations and Stakeholders that would allow market<br />

forces to drive improvements in the delivery of services to the public.<br />

Although in many cases the Responding Organisation shall use the Build-<br />

Operate-Transfer (BOT) mechanism in delivering the solutions, they should<br />

also consider other options, such as Build-Operate-Own (BOO).<br />

Figure 3 provides a conceptual business model to illustrate the funding and<br />

revenue options available to the Responding Organisation. The Responding<br />

Organisation should look into developing their own business model using the<br />

model below only in so far as it is relevant.<br />

10.2.1 Government<br />

In this model, Government is to award an outsourcing contract to a<br />

consortium (or consortia) and pay them substantial fees. Government will<br />

formulate and regulate policies and guidelines for the project and monitor<br />

the success and targeted goals. It will also establish appropriate bodies to<br />

41


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

ensure the effectiveness and quality of the programs and services. All<br />

services commissioned will revert to the Government, subject to the<br />

agreed rights paid for. Hardware installed will depend on the conditions<br />

agreed to in the contract.<br />

10.2.2 Responding Organisation<br />

The successful Responding Organisation, through its lead vendor shall be<br />

responsible for delivering the entire range of services contracted by the<br />

Ministry of Education.<br />

10.2.3 Users<br />

Responding Organisations are also free to propose options where users<br />

pay a nominal fee for services additional to what is usually provided by<br />

the government. Such an option will encourage the service provider to<br />

develop novel and marketable services to increase its revenue. Users shall<br />

generally comprise of:<br />

• Users within schools<br />

• Users within communities.<br />

Funding<br />

Funding<br />

User<br />

Students,<br />

teachers, and<br />

administrators<br />

in <strong>Smart</strong><br />

<strong>School</strong>s and in<br />

the<br />

communities<br />

Service<br />

Responding<br />

organisations /<br />

Consortia /<br />

Consortium<br />

Award outsourcing<br />

contract and<br />

pay fees<br />

Government<br />

(Ministry Of<br />

Education)<br />

Stakeholders<br />

Parents<br />

Companies<br />

Libraries<br />

Corporations<br />

etc<br />

• Pays MOE nominal fees for<br />

<strong>Smart</strong> <strong>School</strong> education<br />

• Pays the vendor for<br />

additional personalised<br />

information and education<br />

services from home<br />

• Pays the consortium for<br />

other additional features and<br />

services developed by<br />

consortium<br />

• Develops the teaching/learning, school<br />

management,and assessment based on<br />

service contract with the MOE<br />

• Augments the education infostructure<br />

and infrastructure with additional<br />

features and services for additional<br />

revenue<br />

• Builds,(design, develop and install),<br />

Operates (administrate, deploy, run, and<br />

maintain),<br />

and Transfers (BOT) to MOE following<br />

completion<br />

• Award<br />

outsourcing<br />

contract and pays<br />

service provider<br />

• Bear moderate<br />

risks<br />

• Play role of<br />

patron to schools<br />

• Community<br />

based<br />

involvement<br />

• Increases their<br />

profile<br />

• Funds upfront investment<br />

• Provides additional education service to<br />

users<br />

• Bears moderate risk<br />

• Motivates creativity<br />

Figure 3: Funding model between Ministry of Education, Responding Organisations, Users and<br />

Stakeholders<br />

42


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

Financial modelling assumptions<br />

The Responding Organisation should provide relevant information on:<br />

• Alternative Pricing Models. The Responding Organisation should<br />

consider alternatives beyond outright purchase (for example, leasing).<br />

The Responding Organisation should also include in the pricing<br />

model options for domestic (within Malaysia) and international<br />

ownership, (outside Malaysia) of intellectual property rights (e.g.,<br />

copyright, publishing, marketing) and the development of derivative<br />

products.<br />

• Costing Model. The Responding Organisation should indicate what<br />

the costing model would be like. <strong>For</strong> example, they should indicate<br />

how much the services will cost (if anything) the government or the<br />

users. Since the Malaysian Government is seeking a minimal capital<br />

outlay, the Responding Organisation should also propose a business<br />

model which provides the net present value of the cash outflow of<br />

government.<br />

• Payback Model. The Responding Organisation should outline the<br />

payback model, i.e. the mechanism and time period for the<br />

Responding Organisation to begin charging for its services.<br />

• Projected Cash Flow.<br />

The Responding Organisation should indicate how they intend to<br />

utilise the cash flow when implementing the pilot project.<br />

10.2.4 Quantities required<br />

Please refer to the section on <strong>Smart</strong> <strong>School</strong> Technology Level Distribution<br />

in The Malaysian <strong>Smart</strong> <strong>School</strong> Implementation Plan.<br />

10.2.5 Financial constraints<br />

The Responding Organisation should do their best to provide a business<br />

model for the pilot project that considers:<br />

• limitation of funds and required skills from the Ministry of Education<br />

in any respective field and discipline.<br />

• that users may be charged nominally for the additional services<br />

provided.<br />

These considerations should ideally be made without compromise to the<br />

quality and quantity of the required services.<br />

43


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

11 Capabilities of the Responding Organisation<br />

The Responding Organisation shall provide the technical and financial capabilities of the<br />

Organisation:<br />

11.1 Project <strong>Management</strong> Capabilities<br />

The Responding Organisation shall be required to provide information in<br />

respect of the following major areas of project management:<br />

11.1.1 Project <strong>Management</strong> Methodology<br />

The Responding Organisation shall describe the background of the<br />

proposed project management methodology which is used to manage<br />

and implement solutions.<br />

11.1.2 Project <strong>Management</strong> Experience<br />

The Responding Organisation shall describe the relevant previous project<br />

management experience, or the relevant previous project management<br />

experience of nominated project managers who shall be involved in the<br />

management and implementation team.<br />

11.2 Training Capabilities<br />

The Responding Organisation shall provide information on its organisation’s<br />

experience on the planning and implementation of training programmes for<br />

both users and technicians.<br />

11.3 Support Capabilities<br />

The Responding Organisation shall describe the level of support provided by<br />

its Organisation. In the response, the Responding Organisation shall address<br />

the following issues:<br />

• Operation hours for the support help desk;<br />

• Problem reporting process;<br />

• Problem escalation process;<br />

• Average problem resolution time;<br />

• Percentage of problems unresolved.<br />

11.4 Financial Capabilities<br />

The Responding Organisation shall describe its financial position. If the<br />

Responding Organisation has traded over the past two years, then the financial<br />

statements shall be included in the response. If the Responding Organisation<br />

is a newly established consortium, then the members of the consortium shall<br />

present their financial statements for the past two years, if their stocks have<br />

been publicly traded over that period.<br />

44


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

Additionally the Responding Organisation shall provide information on any<br />

major projects which have been awarded to its Organisation, if this would be<br />

beneficial in supporting its proposal.<br />

11.5 Technical Capabilities<br />

The Responding Organisation shall provide information on its technical<br />

capabilities, and should include the following:<br />

11.5.1 Technical leadership<br />

Where the Responding Organisation is recognised as a leader in<br />

particular technologies or services, the Responding Organisation shall<br />

describe its area(s) of expertise. Where a consortium exists, all the areas<br />

of technical leadership shall be described in a single consolidated reply.<br />

11.5.2 Relevant reference sites<br />

Relevant reference sites describing the installed solution, scope of the<br />

work, number of project team members and contact information shall be<br />

provided by the Responding Organisation to enable the evaluation of the<br />

experience of the Responding Organisation in completing similar projects.<br />

When an organisation has no experience, but its key members have<br />

suitable experience, then the Responding Organisation shall provide<br />

details of the individual team members’ experience with respect to the<br />

proposed concept solution.<br />

11.5.3 Other unique capabilities as applicable<br />

The Responding Organisation shall provide any additional information<br />

that may assist its response.<br />

45


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

12 Instructions to Responding Organisations<br />

The Government of Malaysia invites proposals to this C<strong>RFP</strong>.<br />

12.1 Communication<br />

Enquiries regarding development of the proposals shall be submitted in<br />

writing by mail, fax or e-mail to:<br />

SMART SCHOOL C<strong>RFP</strong> SECRETARIAT<br />

Educational Technology Division<br />

Ministry of Education<br />

Pesiaran Bukit Kiara<br />

50604 Kuala Lumpur<br />

Malaysia<br />

Fax: +(603) 252 3764<br />

Phone: +(603) 252 3760<br />

E-mail: smartsc@eprd.kpm.my<br />

Website: http://eprd.kpm.my/<br />

Written responses shall be compiled and answered appropriately on the<br />

project website and during the briefing session for Responding Organisations.<br />

No questions, written or verbal, shall be entertained after 1245 hours,<br />

Malaysian Time, 23 August 1997.<br />

12.1.1 Responding Organisations’ Briefing<br />

There shall be a Responding Organisations’ Briefing on 25 August 1997 to<br />

address questions raised by Responding Organisations. Responding<br />

Organisations who wish to participate in this forum shall indicate their<br />

interest to the <strong>Smart</strong> <strong>School</strong> C<strong>RFP</strong> Secretariat no later than two weeks<br />

before the date of the forum, that is by 11 August 1997.<br />

12.2 Submission of Proposal<br />

12.2.1 Time and Date<br />

Proposals shall only be submitted during office hours after 25 September<br />

1997, but not later than 1200 hours Malaysian Time, 30 September 1997.<br />

Proposals submitted after this time shall not be considered.<br />

Office hours are:<br />

Monday-Thursday 0800 – 1245, 1400 – 1615<br />

Friday 0800 – 1215, 1445 – 1615<br />

Saturday 0800 – 1245<br />

46


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

12.2.2 Mode of Delivery and Address<br />

Proposals, together with the Letter of Undertaking as set out in Appendix<br />

1 shall be delivered by hand to:<br />

SMART SCHOOL C<strong>RFP</strong> SECRETARIAT<br />

Educational Technology Division<br />

Ministry of Education<br />

Pesiaran Bukit Kiara<br />

50604 Kuala Lumpur<br />

Malaysia<br />

12.2.3 Marking<br />

Proposals shall be sealed and clearly marked:<br />

“Proposal – <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Pilot”<br />

12.2.4 Number of Copies and Separation of Sections of Proposals<br />

The Responding Organisation shall deliver five copies of each proposal<br />

which shall be physically separated, bound, sealed and labelled as:<br />

• Technical and business proposal<br />

• Financial proposal<br />

(Proposals shall also include a cost-estimate for the overall project<br />

along with detailed cost-estimates for various discrete parts of the<br />

project.)<br />

The Appendices and Attachments may be submitted as a separate section.<br />

12.2.5 Deposit<br />

The Responding Organisation shall submit a deposit together with the<br />

proposal.<br />

The deposit shall be in the form of a Bank Guarantee issued by a bank<br />

operating in Malaysia. The Bank Guarantee shall be in the form as set out<br />

in Appendix 2. The quantum of the deposit is as specified in Appendix 3.<br />

The Bank Guarantee shall remain until 1 January 1999 or until the<br />

Responding Organisation is notified in writing that its proposal is<br />

unsuccessful.<br />

The Deposit shall be forfeited by the Government in the event the<br />

Responding Organisation:<br />

• Revokes its offer prior to being informed of the result of the C<strong>RFP</strong><br />

evaluation<br />

• Fails to honour its obligations under this C<strong>RFP</strong><br />

• Refuses to enter into a contract with the Government on being<br />

informed of the award of contract.<br />

The Government shall not be liable for any interest or any other claim<br />

arising from this deposit.<br />

47


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

12.2.6 Receipt of Proposal<br />

An acknowledgement signed by the authorised representative of the<br />

<strong>Smart</strong> <strong>School</strong> C<strong>RFP</strong> Secretariat shall be evidence of receipt of the<br />

submission of the proposal.<br />

12.2.7 Amendments<br />

No amendment shall be made to the proposal after its submission.<br />

12.2.8 Validity of the Proposal<br />

All proposals and prices shall remain valid for a minimum period of<br />

twelve (12) months from the closing date. However, the Responding<br />

Organisation is encouraged to state a longer period of validity for the<br />

proposal.<br />

12.2.9 Advertisement<br />

No advertisement or press release regarding this proposal shall be<br />

published in any newspaper, magazine or any other form of media,<br />

electronic or otherwise, without prior written approval from the<br />

Government.<br />

12.2.10 Short-list<br />

A Responding Organisation that has been short-listed will be notified in<br />

writing by the Government on or before 1 December 1997.<br />

12.2.11 Letter of Intent<br />

A Responding Organisation that has been short-listed will be notified by<br />

the issue of a Letter of Intent by the Government requiring short-listed<br />

organisations to form Unbound Consortia with other short-listed<br />

organisations and to prepare an integrated proposal.<br />

However, this Letter of Intent is subject to the successful conclusion of the<br />

Unbound Consortium. In the event the short-listed organisations fail to<br />

form the Unbound Consortia, the Government shall not be liable for any<br />

expenses, liabilities, loss, claims, damages or proceedings whatsoever<br />

arising from this Letter of Intent.<br />

12.2.12 Performance Bond<br />

The successful Responding Organisation shall be required to deposit in<br />

the form of a Bank Guarantee a Performance Bond upon the execution of<br />

the contract, a sum equivalent to five percent (5%) of the whole contract<br />

value. This Bank Guarantee shall be issued by a bank operating in<br />

Malaysia and shall be kept valid from the date of issue until eighteen (18)<br />

months after all contractual obligations have been fulfilled. The<br />

Performance Bond shall be forfeited by the Government if the<br />

Responding Organisation breaches any of its obligations under the<br />

contract.<br />

The Bank Guarantee for Performance Bond shall be substantially in the<br />

form as set out in Appendix 4.<br />

48


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

12.2.13 Letter of Understanding<br />

The Responding Organisation shall sign a Letter of Understanding as set<br />

out in Appendix 1.<br />

12.2.14 Language<br />

All proposals including appendices shall be in English; or if not English,<br />

shall include an English translation as an attachment.<br />

12.2.15 Currency<br />

All currency in the proposal shall be quoted in Ringgit Malaysia (RM).<br />

12.2.16 Contents<br />

Proposals shall contain specific and detailed replies to all responses,<br />

requirements, terms and conditions set out in the C<strong>RFP</strong>.<br />

These responses shall be in the order in which the sections and<br />

paragraphs appear in this C<strong>RFP</strong> and make reference the section and<br />

paragraph numbers in this document.<br />

12.3 Proposal Process<br />

The process for submission and evaluation of proposals is designed to foster<br />

development of a web of participating companies. Thus, the process aims to<br />

• Provide adequate time for Responding Organisations to understand<br />

the <strong>Concept</strong> <strong>RFP</strong> processes<br />

• Develop responses that can be evaluated sufficiently to yield a<br />

shortlist of pre-qualified organisations<br />

• Allow Responding Organisations to form Unbound Consortia to<br />

develop comprehensive, innovative and integrated solutions.<br />

12.3.1 Communication during the First Stage<br />

After the issuing of the <strong>Concept</strong> <strong>RFP</strong>, Responding Organisations shall<br />

have the opportunity to submit questions to the <strong>Smart</strong> <strong>School</strong> C<strong>RFP</strong><br />

Secretariat to clarify details relating to the C<strong>RFP</strong> or to gain information<br />

necessary for formulating an attractive proposal. These questions shall be<br />

submitted in written form. No questions shall be entertained after 1245<br />

hours Malaysian Time, 23 August 1997.<br />

Response:<br />

• The Responding Organisations shall submit their queries before<br />

1245 hours Malaysian Time, 23 August 1997.<br />

12.3.2 First Stage: Proposal Development<br />

The Responding Organisation shall prepare its proposal anytime between<br />

the issue of the C<strong>RFP</strong>s and the deadline for the submission of first-stage<br />

proposals (30 September 1997).<br />

The Responding Organisation shall bear in mind that this is a two-stage<br />

process and that it shall form, with other Responding Organisations,<br />

49


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

Unbound Consortia in the second stage to produce a complete,<br />

comprehensive, innovative and integrated solution. Hence, the<br />

Responding Organisation shall also state its vision of how its particular<br />

solution shall fit into an overall solution.<br />

No alterations, amendments or additions to first stage proposals or new<br />

first stage proposals shall be accepted after the deadline.<br />

Response:<br />

• The Responding Organisation shall bear in mind the second stage<br />

of the C<strong>RFP</strong> process when preparing proposals.<br />

• The Responding Organisation shall submit their first-stage<br />

proposal before 1200 hours, Malaysian Time, 30 September 1997.<br />

12.3.3 First Stage Evaluation of Proposals and Short-Listing<br />

The Government will review and evaluate the submitted proposals to<br />

develop a short-list of qualifying organisations. The successful short-listed<br />

candidates shall then form Unbound Consortia and take part in<br />

producing an integrated solution proposal. These comprehensive<br />

proposals by various consortia shall again be evaluated.<br />

The short-listed candidates from the first stage shall be announced on<br />

1 December 1997.<br />

Response:<br />

• Responding Organisations that are confident of being short-listed<br />

shall prepare in advance for the second stage of the C<strong>RFP</strong> process.<br />

12.3.4 Second Stage: Integrated Solution Development<br />

The short-listed candidates shall enter into Unbound Consortia from<br />

among themselves and prepare a comprehensive integrated proposal.<br />

These Unbound Consortia:<br />

• Shall provide a complete integrated solution that responds to all the<br />

requests raised in the five <strong>Smart</strong> <strong>School</strong> C<strong>RFP</strong>s.<br />

• Shall be composed only of companies that have been short-listed in<br />

the first stage of the proposal process and shall include at least four<br />

separate organisations (See Figure 4), of which<br />

• At least two responded to the C<strong>RFP</strong> for Teaching Learning<br />

Materials, each of whom shall be responsible for at least one<br />

entire subject.<br />

• At least two responded to one or more of the four remaining<br />

C<strong>RFP</strong>s (namely, <strong>Management</strong> <strong>System</strong>, Assessment <strong>System</strong>,<br />

Technology Infrastructure and <strong>System</strong>s Integration).<br />

• May contain Responding Organisations that are also part of other<br />

Unbound Consortia, i.e. a Responding Organisation may be a<br />

member of multiple Unbound Consortia.<br />

• May divide responsibilities among their members in ways that do not<br />

strictly follow the C<strong>RFP</strong>(s) for which a Responding Organisation was<br />

short-listed. <strong>For</strong> example, a Responding Organisation that first<br />

50


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

qualified for the <strong>Management</strong> <strong>System</strong> C<strong>RFP</strong>, may in the Unbound<br />

Consortia provide <strong>System</strong>s Integration services.<br />

• Shall organise a single point of contact to interact with the<br />

Government. (This shall probably, but need not necessarily, be the<br />

organisation leading the systems integration.)<br />

• Shall recognise that while they form a single Unbound Consortium,<br />

the Government shall sign a contract with all the Responding<br />

Organisations that comprise the winning Unbound Consortium or<br />

with a legally bound consortium comprising all Responding<br />

Organisations of the winning Unbound Consortium. The Unbound<br />

Consortium shall spell out the division of responsibilities and costing<br />

among its members.<br />

• Shall submit their proposal for the second-stage integrated solution<br />

on or before 1200 hours Malaysian Time, 31 March 1998. No new<br />

second-stage integrated proposals or alterations or additions to<br />

submitted second-stage integrated proposals shall be accepted after<br />

the deadline.<br />

Response:<br />

• Responding Organisations shall bear in mind the conditions set out<br />

in forming their Unbound Consortia.<br />

• The Unbound Consortia shall nominate a single point of contact<br />

with the Government.<br />

• The Unbound Consortia shall respond with a single complete<br />

Teaching-Learning<br />

<strong>System</strong>s<br />

Integration<br />

Technology<br />

Infrastructure<br />

Assessment<br />

<strong>Management</strong><br />

Science<br />

Mathematics<br />

English<br />

Bahasa Melayu<br />

At least<br />

two that<br />

responded<br />

to T-L<br />

An Unbound Consortium<br />

of at least four distinct<br />

organisations that comes<br />

up with a total integrated<br />

solution<br />

At least<br />

two that<br />

responded<br />

to one of<br />

the rest<br />

Figure 4: How short-listed Responding Organisations will form an Unbound Consortium<br />

51


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

integrated proposal, which outlines individual contributions and<br />

costs.<br />

• This second-stage integrated proposal shall be submitted in a<br />

timely manner, before the deadline of 1200 hours Malaysian Time,<br />

31 March 1998.<br />

12.3.5 Second-Stage Evaluation and Shortlisting<br />

The Government will review and evaluate submitted integrated proposals<br />

and develop a short-list of consortia with whom to pursue negotiations.<br />

The successful short-listed candidates for negotiation shall be announced<br />

on 30 April 1998.<br />

Response:<br />

• Confident Unbound Consortia shall prepare for negotiations in<br />

advance.<br />

12.3.6 Multi-track negotiations<br />

The Government will negotiate with the short-listed Unbound Consortia<br />

concurrently to consider terms, scope, capabilities and performance<br />

milestones of the proposed solutions. Confidentiality of proposals shall be<br />

strictly maintained.<br />

12.3.7 Final Selection<br />

The Government shall select the winning Unbound Consortium based<br />

upon the best and final offer.<br />

The successful proposal and the winning Unbound Consortium shall be<br />

announced on or before 1 July 1998. The Government shall sign a contract<br />

with all the Responding Organisations that comprise the winning<br />

Unbound Consortium or with the legally bound consortium that<br />

comprise the Responding Organisations of the winning Unbound<br />

Consortium. The terms and conditions of the contract shall be agreed<br />

upon between the Government and all the Responding Organisations that<br />

comprise the winning Unbound Consortium or the said legally bound<br />

consortium as the case may be.<br />

12.3.8 Implementation<br />

The winning consortium shall demonstrate implementation capabilities<br />

through a proof of concept or initial pilot implementation. The<br />

Government shall regularly review the consortium’s performance against<br />

both their intentions as stated in their proposal and the agreed<br />

performance milestones for the project.<br />

12.4 Process Timeline<br />

• Late July 1997: C<strong>RFP</strong>s are made available.<br />

• Late July-30 September 1997: Responding Organisations prepare<br />

their first stage proposals.<br />

52


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• 12.00 p.m. 30 September 1997: Deadline by which Responding<br />

Organisations shall submit their proposals to be eligible for<br />

membership in any Unbound Consortia.<br />

• October-November 1997: Government evaluates the proposals.<br />

• 1 December 1997: Short-listed Responding Organisations are<br />

announced.<br />

• December 1997 to March 1998: Short-listed Responding<br />

Organisations form Unbound Consortia and prepare integrated<br />

solution proposals.<br />

• 12:00 p.m. 31 March 1998: Deadline by which the Unbound Consortia<br />

shall submit their integrated solution proposals.<br />

• April 1998: Government evaluates the integrated solution proposals.<br />

• 30 April 1998: Short-listed Unbound Consortia are announced.<br />

• May-June 1998: Multi-track negotiations and contract development<br />

occurs.<br />

• 1 July 1998: Second round selection is completed. The successful<br />

proposal and the winning Unbound Consortium shall be announced.<br />

The Government shall sign a contract with all the Responding<br />

Organisations that comprise the winning Unbound Consortium or<br />

with a legally bound consortium that comprise all the Responding<br />

Organisations of the winning Unbound Consortium. The terms and<br />

conditions of the contract shall be agreed upon between the<br />

Government and all the Responding Organisations that comprise the<br />

said legally bound consortium as the case may be.<br />

12.5 Mandatory Requirements and Evaluation Criteria<br />

12.5.1 Mandatory Requirements<br />

Proposals shall comply with the following mandatory requirements:<br />

i. Instructions to Responding Organisations (this chapter); and<br />

ii.<br />

The specific requirements and responses in this C<strong>RFP</strong>.<br />

Proposals that do not comply with these mandatory requirements shall<br />

be excluded from further evaluation<br />

Evaluation Criteria<br />

Proposals that comply with the mandatory requirements stated in section<br />

12.5.1 will then be evaluated against the following evaluation criteria:<br />

• Attractiveness of solution will include the proposed technical<br />

concept, business model, funding options and approach to<br />

implementation.<br />

• Calibre of the Responding Organisations such as its composition,<br />

capabilities, record of experience and the composition of the proposed<br />

implementation team.<br />

53


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• Attractiveness of the model for technology transfer, including the<br />

level of co-operation with local companies, any special initiatives for<br />

technology transfer and joint development efforts.<br />

• Involvement in the MSC. Weightage and priority will be given to<br />

companies which have gained MSC status or would qualify for MSC<br />

status. The level of investment in the MSC will also be considered,<br />

with emphasis on the investment in Research & Development. It is<br />

envisaged that the successful Responding Organisation will apply<br />

and obtain MSC status before a contract is awarded. This<br />

requirement may be waived in the case of Responding Organisations<br />

that do not fall within the definition of multimedia business.<br />

Responding to specific evaluation criteria<br />

This section requires the Responding Organisation to provide a proposal<br />

on each of the following criteria, which are not explicitly covered in this<br />

C<strong>RFP</strong>.<br />

Calibre of the Responding Organisation<br />

Response:<br />

Proposals shall contain the following:<br />

• Names of all participants in the Responding Organisation (if more<br />

than one) including their scope of involvement;<br />

• Name of lead contractor or joint venture and the relationship<br />

between this entity and the other participants of the Responding<br />

Organisation, if applicable;<br />

• Experience of the Responding Organisation in similar projects,<br />

including references;<br />

• Examples of industry recognition, if any, for the Responding<br />

Organisation in the areas of technological leadership, innovation<br />

and implementation;<br />

• Examples, if any, where the Responding Organisation has worked<br />

together on similar projects with the same participants.<br />

Attractiveness of the model for technology transfer<br />

Response:<br />

Proposals shall set out a plan for achieving the objective of technology<br />

transfer to Malaysia. The description of the approach, process and<br />

methods for ensuring technology is being transferred to local<br />

companies shall be described. This includes participation of Malaysian<br />

companies in the Responding Organisation and plans to raise the<br />

technology skills of Malaysian workers. The Responding Organisation<br />

is required to demonstrate its commitment to the goals and aspirations<br />

of Malaysia and the MSC and outline its plan for knowledge and<br />

technology transfer.<br />

The Responding Organisation shall outline its plan to implement:<br />

• details as to how knowledge is to be conveyed<br />

54


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

• the level of co-operation with local companies, universities and<br />

government agencies<br />

• training programmes<br />

• joint development efforts<br />

Involvement in MSC<br />

Response:<br />

Proposals shall contain the following:<br />

• If the Responding Organisation has:<br />

- obtained MSC status, the Responding Organisation shall show<br />

proof of MSC status;<br />

- applied for MSC status, the Responding Organisation shall show<br />

proof of submission of the MSC status application and attach a<br />

copy of its application form;<br />

- not applied for MSC status yet, the Responding Organisation shall<br />

detail its eligibility for MSC status, with specific reference to the<br />

criteria for MSC status.<br />

- not applied for MSC status, the Responding Organisation shall<br />

provide reasons for not applying for MSC status.<br />

• An outline of the actual or planned involvement of the Responding<br />

Organisation in the MSC, if any.<br />

12.6 Rights of the Government<br />

12.6.1 Amendments<br />

The Government reserves the right to amend or delete any part of this<br />

C<strong>RFP</strong> or any document forming part of this C<strong>RFP</strong> at any time without<br />

prior notice in order to give effect to change in policy or to correct any<br />

error, omission, ambiguity or inconsistency that may arise after the issue<br />

of this C<strong>RFP</strong>.<br />

12.6.2 Acceptance of Proposals<br />

The Government does not bind itself to accept the lowest or any proposal.<br />

12.6.3 Cost of Proposal<br />

The Government shall not be liable for any payment or costs incurred in<br />

the preparation and submission of the proposal in response to the C<strong>RFP</strong>.<br />

All costs and expenses incurred by the Responding Organisation in<br />

providing the proposal shall be borne by the Responding Organisation.<br />

12.6.4 Responding Organisation’s Responsibilities<br />

It is the Responding Organisation’s responsibility to understand the<br />

C<strong>RFP</strong>, including the requirements in this C<strong>RFP</strong> and to make all<br />

55


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

examinations necessary in order to ascertain all factors, enquiries and<br />

questions which might affect the Responding Organisation’s proposal.<br />

12.6.5 Non-liability<br />

Whilst care is taken to ensure that the facts and information contained in<br />

this C<strong>RFP</strong> are correct at the time it is presented, the Government hereby<br />

makes no representation as to the accuracy or adequacy of such facts and<br />

information contained in the C<strong>RFP</strong>. The Government shall not be held<br />

liable for any inaccuracy or inadequacy of such facts and information.<br />

12.6.6 Confidential Information<br />

All information of a confidential nature whether generated in Malaysia or<br />

overseas, shall be subject to Malaysian Laws and Regulations. Without<br />

prejudice to the right of the Government under any law, a breach by the<br />

Responding Organisation may entitle the Government to terminate<br />

dealings with the organisation without prior notice to the Responding<br />

Organisation.<br />

12.6.7 Failure of Negotiation<br />

It shall be agreed and understood that in the event that the negotiation<br />

fails and a contract is not signed, there shall be no cause of action against<br />

the Government howsoever, nor shall it be possible to pursue a cause of<br />

action against the Government for any action howsoever arising.<br />

12.6.8 Discrepancy of Document<br />

In the event that there exists any discrepancy between an electronic<br />

version of this document (or any documents printed or distributed using<br />

an electronic version as a source) and the official printed hardcopy<br />

distributed by the Government, addenda or corrections, then the<br />

information in the official printed hardcopy, addenda or corrections shall<br />

prevail.<br />

12.6.9 Withholding Tax<br />

The Responding Organisation is hereby informed that the Government<br />

shall deduct tax, at the rate prescribed under the withholding tax laws of<br />

Malaysia, from all payments for services rendered by any Responding<br />

Organisation who signs a contract with the Government.<br />

12.6.10 Governing Law<br />

This C<strong>RFP</strong> and any contract executed pursuant to this C<strong>RFP</strong> shall be<br />

governed by and construed in accordance with the laws of Malaysia. The<br />

Government of Malaysia and all Responding Organisations responding to<br />

this C<strong>RFP</strong> and parties to any contract executed pursuant to this C<strong>RFP</strong><br />

shall submit to the exclusive jurisdiction of the Malaysian Courts.<br />

56


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

Appendix 1 - Responding Organisation’s Undertaking <strong>For</strong>m<br />

To:<br />

Secretary General<br />

Ministry of Education<br />

Kuala Lumpur<br />

MALAYSIA<br />

Responding Organisation’s Undertaking<br />

Proposal for <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Pilot<br />

The undersigned (hereinafter called “the Responding Organisation”) hereby offers to<br />

*________________ to the extent which the Government may determine in accepting the C<strong>RFP</strong><br />

and at such time as may be demanded by the Government.<br />

2. The Responding Organisation hereby agrees to the forfeiture of the Deposit (forwarded<br />

together with the proposal) to the Government in the event the Responding Organisation:<br />

a. revokes its offer prior to his being informed of the result of this C<strong>RFP</strong>;<br />

b. fails to honour its obligations under this proposal; or<br />

c. refuses to enter into a contract with the Government on being informed of the award<br />

3. The Responding Organisation further offers to lodge with the Government, if its proposal is<br />

accepted, a sum equivalent to 5% of the Contract value in the form of a Bank Guarantee for<br />

the said sum as security for the due fulfilment of the contract and agrees that the Bank<br />

Guarantee shall be retained by the Government.<br />

4. We enclose herewith the deposit in the form of a Bank Guarantee as follows:<br />

Bank Guarantee No ________________________ Amount:___________________________<br />

Name of Bank _________________________________________________________________<br />

Name of Responding Organisation _________________________________________________<br />

Address _______________________________________________________________________<br />

_______________________________________________________________________<br />

_______________________________________________________________________<br />

Signed by for and on behalf of Responding Organisation_________________________________<br />

Name & Designation _____________________________________________________________<br />

* Responding Organisation is to specify the services/solutions/applications they are offered<br />

57


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

Appendix 2 - Bank Guarantee Deposit <strong>For</strong>m<br />

To:<br />

Secretary General,<br />

Ministry of Education,<br />

Kuala Lumpur,<br />

Malaysia.<br />

Bank Guarantee<br />

Sir,<br />

BANK GUARANTEE<br />

As requested by the Responding Organisation ____________________________________________,<br />

we hereby guarantee that the sum of RM______________ (Ringgit Malaysia<br />

__________________________________) being the amount of Deposit required to be deposited<br />

with the Government of Malaysia in accordance with the conditions of the C<strong>RFP</strong> for<br />

________________________________________ shall become payable by us immediately on receipt<br />

of notices in writing given to us by the Government or its authorised representative.<br />

This Guarantee is effective from the date that the C<strong>RFP</strong> document is submitted by the<br />

Responding Organisation, and shall remain in force until 1 January 1999 or until the Responding<br />

Organisation is notified in writing that its proposal is unsuccessful.<br />

Signed _________________________<br />

<strong>For</strong> and/or behalf<br />

of__________________<br />

Name of Bank___________________<br />

Address________________________<br />

58


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

Bank Guarantee No ________________________ Amount:___________________________<br />

Name of Bank _________________________________________________________________<br />

Name of Responding Organisation _________________________________________________<br />

Address _______________________________________________________________________<br />

_______________________________________________________________________<br />

_______________________________________________________________________<br />

Signed by for and on behalf of Responding Organisation_________________________________<br />

Name & Designation _____________________________________________________________<br />

59


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

Appendix 3 - Quantum of Deposit for Responding Organisations<br />

1. <strong>For</strong> International Companies<br />

Estimated Cost of the C<strong>RFP</strong> solution Amount of Deposit<br />

(i) Not exceeding RM 5 million RM 62, 500.00<br />

(ii)<br />

(iii)<br />

(iv)<br />

More than RM 5 million but<br />

not exceeding RM 10 million<br />

More than RM 10 million<br />

not exceeding RM 20 million<br />

More than RM 20 million but<br />

not exceeding RM 30 million<br />

RM 187,500.00<br />

RM 375,000.00<br />

RM 625,000.00<br />

(v) More than RM 30 million RM 1 million<br />

2. <strong>For</strong> local companies not registered with the Ministry of Finance, Malaysia<br />

These companies are required to submit a deposit of RM 10,000.00<br />

3. <strong>For</strong> companies registered with the Ministry of Finance, Malaysia<br />

All companies registered with the Ministry of Finance are exempted from paying a deposit.<br />

60


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

Appendix 4 - Bank Guarantee <strong>For</strong>m for Performance Bond<br />

Bank Guarantee <strong>For</strong>m for Performance Bond<br />

THIS AGREEMENT is made the ________ day of ____________________ 19__ BETWEEN<br />

_______________________________ (insert name of Bank) of _______________________________<br />

(insert principal address of business of Bank) (hereinafter called the “Guarantor”) of the one Part<br />

and the Government of Malaysia (hereinafter called the “Government”) of the other Part.<br />

WHEREAS<br />

In consideration of the Government allowing _____________________ (hereinafter referred to as<br />

the “Contractor”) to supply and deliver/provide articles/services to the Government<br />

__________________ (hereinafter called the “Articles/Services”) for a contract sum of Ringgit<br />

____________________________ (state the amount in words) (RM __________________), we, the<br />

Guarantor at the request of the Contractor irrevocably undertake a guarantee to the Government<br />

to guarantee the due performance of the Contract in the manner hereinafter appearing.<br />

Now the Guarantor hereby agrees with the Government as follows:<br />

1. On the Government’s first written demand, the Guarantor shall forthwith pay to the<br />

Government the amount specified in such demand notwithstanding any dispute or protest<br />

by the Contractor or Guarantor or by any other third party and without proof or conditions.<br />

Provided always that the total of all demands so made shall not exceed the sum of Ringgit<br />

_________________________ (state the amount in words) (RM____________) and the total<br />

amount recoverable against the Guarantor under this Agreement shall not exceed the said<br />

sum.<br />

2. The Government reserves the right to make any partial demand if it so desires and the total<br />

of all such partial demands so made shall not exceed the sum of<br />

Ringgit________________________ (state the amount in words) (RM______) and the liability<br />

61


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

of the Guarantor to pay the Government the aforesaid shall correspondingly be reduced<br />

proportionately to any payment of partial demand having been made by the Guarantor.<br />

3. The Guarantor shall not be discharged or released from this Guarantee by any arrangement<br />

between the Contractor and the Government with or without the consent of the Guarantor or<br />

by any alteration in the obligation undertaken by the Contractor or by any forbearance,<br />

whether as to payment, time, performance or otherwise.<br />

4. The Guarantee given by the Guarantor is a continuing guarantee. This Agreement shall be<br />

irrevocable and shall initially remain in force and effect until ________________ (referred to<br />

as the “Expiry Date”). The Guarantor shall upon the request of the Government extend this<br />

guarantee for a further period of _____________ (state the period) until ____________ in<br />

which case, the maximum aggregate amount that the Government shall be entitled to shall<br />

not exceed the said um of Ringgit_________________________________ (state the amount in<br />

words) (RM _________________).<br />

5. All obligations and liabilities of the Guarantor under this Agreement shall cease upon the<br />

determination of this Agreement on the date or such extended date as specified in paragraph<br />

4 above as the case may be save to the extent that the Government shall previously have<br />

called upon the Guarantor in writing to pay specified moneys payable under the Contract<br />

then remaining outstanding.<br />

6. ALL CLAIMS, IF ANY, IN RESPECT OF THIS GUARANTEE SHALL BE RECEIVED BY THE<br />

BANK DURING THE VALIDITY PERIOD OF THIS GUARANTEE OR WITHIN FOUR<br />

WEEKS FROM THE EXPIRY DATE OF THIS GUARANTEE WHICHEVER IS THE LATER.<br />

62


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

IN WITNESS WHEREOF the parties hereto have hereunto set their hands the day and year first<br />

abovewritten.<br />

Signed for and on behalf of the said<br />

Guarantor in the presence of<br />

Name:___________________________________<br />

Designation:______________________________<br />

Bank<br />

(Witness)<br />

Name:___________________________________<br />

Designation:_____________________________<br />

Bank<br />

Signed for and on behalf of the said<br />

Government of Malaysia in the presence<br />

of<br />

Name:___________________________________<br />

Designation:______________________________<br />

Department's Chop<br />

(Witness)<br />

Name:___________________________________<br />

Designation:_____________________________<br />

Department’s Chop<br />

63


<strong>Concept</strong> <strong>RFP</strong> <strong>For</strong> <strong>Smart</strong> <strong>School</strong> <strong>Management</strong> <strong>System</strong> Wednesday, July 23, 1997<br />

Appendix 5 - Glossary<br />

First Stage<br />

In the context of these C<strong>RFP</strong>s, this refers to the first stage of evaluation of all<br />

the proposals submitted by Responding Organisations in response to the five<br />

C<strong>RFP</strong>s.<br />

Government<br />

Legally Bound<br />

Consortium<br />

Pilot <strong>School</strong>s<br />

Second Stage<br />

<strong>System</strong>s<br />

Integration<br />

Unbound<br />

Consortia/<br />

Consortium<br />

This shall mean the Government of Malaysia.<br />

A legal entity that comprises only the winning Unbound Consortium.<br />

This term is used interchangeably with the term "pioneer schools". Both<br />

these terms refer to the 90 schools throughout Malaysia that have been<br />

identified for the deployment of the pilot applications described in all five<br />

C<strong>RFP</strong>s issued to develop the Malaysian <strong>Smart</strong> <strong>School</strong> flagship application of<br />

the Multimedia Super Corridor.<br />

In the context of these C<strong>RFP</strong>s, this refers to the second stage of evaluation<br />

where Responding Organisations group together as Unbound Consortia to<br />

propose total integrated solutions for all the five C<strong>RFP</strong>s combined. The<br />

evaluation of these total integrated solutions shall take place at this second<br />

stage.<br />

This refers to the integration of the <strong>Smart</strong> <strong>School</strong>s sub-application systems<br />

for the pilot schools. <strong>System</strong>s integration shall ensure the design, installation,<br />

testing and acceptance of each of the <strong>Smart</strong> <strong>School</strong> sub-applications i.e.<br />

Teaching-Learning Materials, <strong>School</strong> <strong>Management</strong> <strong>System</strong>, Assessment<br />

<strong>System</strong> and Technology Infrastructure. These sub-applications are procured,<br />

installed, integrated, tested so that they shall be operational by the date on<br />

which the systems are commissioned.<br />

This definition of the Unbound Consortium/consortia pertains only to the<br />

specific circumstances of the <strong>Smart</strong> <strong>School</strong> C<strong>RFP</strong> processes. In the interests of<br />

all Responding Organisations providing an integrated solution to all the<br />

<strong>Smart</strong> <strong>School</strong> applications, all Responding Organisations shall first be<br />

evaluated by the Ministry of Education, according to their responses to the<br />

five C<strong>RFP</strong>s issued for the <strong>Smart</strong> <strong>School</strong> applications. All the short-listed<br />

Responding Organisations resulting from this evaluation process, shall then<br />

form Unbound Consortia from among themselves to present to the Ministry<br />

of Education, a total integrated solution encompassing all the requirements<br />

incorporated in all five C<strong>RFP</strong>s. The Ministry of Education shall evaluate<br />

these integrated proposals and select the winning Unbound Consortium.<br />

Each Unbound Consortium shall appoint from among its members a lead<br />

Responding Organisation who shall be responsible for all aspects of<br />

integration among the solution providers. The lead Responding<br />

Organisation may, of its own volition, enter into contracts with each member<br />

of the consortium in order to cover all risks involved in forming such a<br />

consortium. The consortium/consortia arising out of the Ministry of<br />

Education evaluation process, serving the purposes outlined above, shall be<br />

described as an Unbound Consortium.<br />

64

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!