3. Solutions Write Up

8/3/2019 3. Solutions Write Up

http://slidepdf.com/reader/full/3-solutions-write-up 1/24

Proposal for Lembaga Lebuhraya Malaysia

Computer-Based Learning Sdn Bhd Private and Confidential

1

1. Executive Summary

Computer Based Learning Sdn Bhd (hereinafter referred to as CBL) has great pleasure in submitting this

Technical proposal to Lembaga Lebuhraya Malaysia (hereinafter referred to as LLM).

The proposed supply, analysis, design, development, installation, configuration, testing, commissioning,

migration, provisioning, support and maintenance for LLM is based upon our clear understanding of

LLM's requirements for Highways Asset Quality System (hereinafter referred to as HAQS). The proposal

aims to address the functional fit, technology fit; the ability of a web base application that can be

totally integrated and has future scalability capacities, as well as to ease of maintenance efforts.

CBL will provide a multi-disciplinary team with expertise in each of the areas critical to the success of

LLM project. We have skills in the areas of Rapid Software Development and sound understanding of

large scale business operations in the areas of Financial Accounting software development and

Hospitality Management . Our team have successfully developed and implemented industry standard

applications; such as the home-grown Hotel and Administration System which is marketed under the

brand name HANIS and Hanis Financial Management System.

We are also the software developers of ASSETBase, the world patented (PCT/SG/2006), award winning

accounting simulation and learning tool specially designed for education and training. The software

bridges the gap between classroom learning and accounting industry practice through the

breakthrough simulation technology. Our major client for this software is the Ministry of Education

Malaysia and it is being used in 1365 secondary schools throughout Malaysia. Secondary school

students who have passed their Principles of Accounting SPM paper, and have been formally assessed

on the use of ASSETBase, will be granted exemptions from ACCA’s Paper 1 and Paper 3 CAT syllabus,

Level 1, Level 2 and Level 3 certifications from LCCI as well as CIMA Financial Foundation Payer. The

ASSETBase also had the honour of receiving official awards and recognitions from the academia and

industry alike; among others Gold Medals at the Science, Technology and Innovation Expo for 2 years in

a row (2003 & 2004) organized by the Ministry of Science and Technology and Innovation of Malaysia;

Gold Medals for Research and Invention by Universiti Putra Malaysia (20002 & 2003), Gold Medal at the

International Invention, Innovation, Industrial Design and Technology Exhibition (I.TEX 2002), Gold

Medals at the prestigious Salon International Des Inventions in Geneva, Switzerland (2005) and the

MSC APICTA 2007 award for the Best in Education and Training Category. The local professional

accounting body, MICPA also endorsed the software which further testifies the software credibility.





2

Our wealth of knowledge from the development of our inhouse applications similar which is in nature

to the requirement of LLM HAQS system is a great strength that CBL has to offer not only in

understanding the requirements but also in executing and recommending critical business processes in

the entire value chain of LLM operations.

For the purpose of this project, all development work will be using the existing LLMs application i.e.

running Microsoft Operating Systems, Microsoft Visual Studio 2005 application development tool,

Crystal Report 2008, Fusion Chart 3.0 and Microsoft SQL Database. By using these applications we

would also reuse most of the current invested hardware and software by LLM.

With regards to managing the project, a team of Project Management Office (PMO) shall be established

to manage and oversee the system implementation to ensure that requirement specifications

throughout the system’s implementation life-cycle are met. The team will work hand in hand with

LLM's own Project team to ensure a smooth delivery of HAQS system.

CBL will undertake to deliver the complete Software Development and Implementation of the new

HAQS LLM System in 10 months. We are confident in achieving this timeframe due to our extensive

experience as developers of award winning software applications and the fact that CBL possesses sound

knowledge of the subject matter.

The proposed total solution by CBL uses a combination of tried and tested, hardware and software

development tools, testing tools and Project Management tools. We are therefore confident that the

proposed approach will provide a reliable and efficient system, which will significantly enhance the

delivery and the processing capabilities of LLM’s that matter its mission and vision.





3

Solution write-up

1. Understanding of Requirement

1.1 Present State and IT Infrastructure Environments

1.1.1 Present State

The current application landscape in LLM comprises of systems that were deployed in a

distributed network environment which is being used by LLM to regulate 23 concession companies

through out Malaysia to ensure the quality control of assets are of standards defined by LLM. At the

moment 20 concession companies are running their own distributed database to record Civil and

Structure(C&S) assets for pavement, bridge, slope and drainage. The remaining 3 concession companies

are recording in a sparkle system environment.

While the Mechanical and Electrical (M&E) assets for M&E services, lighting, toll, collection system,

tunnel system, traffic control surveillance system are still on manual record keeping processes.

Each of the concession companies are required to prepare periodic and routine asset maintenance

program and these schedules are submitted LLM district offices for verification, monitoring and to

ascertain the schedules effectiveness and timing. The district offices will conduct site inspections based

on the submitted and approved maintenance schedules and a Non Compliance Record (NCR) will be

issued to the concession companies for their further action based on the ratings that are giving in NCR.

The concession companies must comply to the NCR that was issued and to ensure that it is within

guidance of rectification respond time. Subsequently the concession companies are required to submit

corrective or preventive maintenance reports on jobs done based upon the NCR to respective district

LLM offices for further site visits to verify and close the NCR.

If a NCR is not closed or address to, for 3 consecutive times after it’s issuance the regulatory division of

LLM will propose the execution of the maintenance bon by the effected concession company to top

level management of LLM.

1.1.2 Present IT Infrastructure Environment

The Primary Internet Link to LLM HQ is via VPN pipes, with a bandwidth of 2Mbps and LLM branches

are link to the current environment via 1Mbps ADSL IPVPN links. This is due to the current distributed

network architecture and the Servers that were deployed for the current application environment and

the current network design at the Data Centre requires further detail analysis to address LLM’s desire to

enhance its information system delivery to achieve a state which requires less or minimal manual user

intervention, avoid overlapping transaction by different users from the business chain, functionalprocessing, timeliness of business information update, speed of transaction, accurate and quality

information capture and reporting in a highly secured manner.





4

2. Challenges to Be Addressed

LLM is an entity with 4 distric offices and 23 concession companies currently throughout Malaysia.

For the purpose of the tender, our focus will be to ensure the following:-

i. A centralized system accessible via secured and timely existing internet and intranet

environment to record, process, analyze and produce valuable data and reports in relation to highway

asset inventory monitoring for C&S and M&E which would enable LLM to monitor the checking,

auditing, repairing and maintenance works done by entities under it.

ii. High availability system with secure security standards accessible through various channels.

iii. Manage and track the whole business process value chain of Highway Asset Inventory and

Maintenance at LLM, district offices and concession companies with the management of HAQS businessrules and conditions are centrally controlled via System Administration module. The integrated system

must be able to meet the transactional and operational needs of LLM Headquarter, branches and

external users

iv. A management reporting tool that as able to provide operational, statistical and management

reports on the fly from various level of the business chain of the LLM organisation and modules.

As can be seen from above there is no single readymade application that can cater to all the

requirements of the various business levels of LLM HAQS. As such our propose integrated solution

which will be centrally located and the new LLM HAQS System must be able handle the following:

The Table 1-1 below describes the current number of various access points.

No. Application Systems Access

Points

1 LLM Headquarter 1

2 District offices 4

3 Concession company 23

Total 28

Table 1-1

2.1 Addressing Challenges Identified

In addition to meeting the functional requirements of LLM business units, the New HAQS System that

will be implement must have the following characteristics:-

i. Web-based application that is accessible via any operating system

ii. Capable of supporting offline transactions as well as online transactions

iii. Fully integrated between all solutions

iv. Centralised control from HQ

v. Scalable not just in number of users but also in meeting future functional requirements

vi. Easy to manage and maintain





5

Due to the integrated HAQS system activities and locations of the various operations, the challenges

that will arise are as follows:-

i. Data accuracy and consistency

ii. Data timelines

iii. Data control

iv. Data security

v. Deployment and maintenance of solutions

vi. User control and segregation of duties

vii. Process control – in relation to work flow

viii. Accommodating for future growth in business activities and users

ix. Accommodates analysis of data using tools

Our Approach to meet the Requirements

Future Environment Guiding Principles.

The Solution that CBL will be providing for is based on assumptions and consideration of the

uniqueness of the nature of business and operations in LLM. They are centered around the

following principles as outlined in the quotation document. They are to assist in:

To monitor highway asset inventory for C&S and M&E

To monitor and analyze routine and periodic asset maintenance schedule or program

and it’s work flow and tasks must be traceable, reconcilable and done in a secure,

accurate and timeliness manner.

To produce Non Compliance Record (NCR). To monitor, check and approved maintenance and repair of assets by the concession

companies.

Speed of transaction and omnipresent access at any time from different locations to

the new HAQS system. All transactions and information flow must be accurate,

secured, and reliable and the data must be treated as single trusted source of

information.

2.2 Future Application Environment

The new HAQS system will be an integrated system. It will be able to meet the

transactional and operational need of the users at the LLM Headquarters, branches and

concession companies. Able to track the whole business process value chain of Highway

Assest Inventory management. A management reporting tool to print statiscal and

management reports. Robust and expandable to meet the business and operational needs

of LLM.

2.3 Future IT Infrastructure Environment (3.1, 3.2)

The new HAQS system must be able to seamlessly accessible from internal, external

Users. The data center has a list of Server, Operating systems and Network security related softwares.

The LLM network and applicaiton is fully equiped with the proposed hardware and software.





6

List of Software exists in future IT infrastructure supplied by CBL

HAQS system 1

Windows Server 2008 R2 6 unit

List of Hardware exists in future IT infrastructure supplied by CBL

New Server –HP Proliant DL 380 Generation 7 (G7) 1 unit

The following diagram illustrates the future IT and Network infrastructure at LLM

Figure 1





7

3. The Solution (3.4)

Development, Testing and documenting of the HAQS LLM Systems, supporting modules and it's access

channels . They are : (Not limited to)

System Administration Module

HAQS Administration Module

Highway Asset Inventory Module

Highway Asset Maintenance Program Module

Highway Asset Maintenance Monitoring Module

Mobile Module

The above development activities are to be carried out in Development environment and beta tested

by our testers before deploying to test environment for users testing and acceptance upon which we

will be publishing to production environment.

The new integrated HAQS LLM HAQS system is to be developed as below:

Future HAQS LLM System Application Architecture Figure 2

Deployment of New Server, Existing servers, networking equipments, storage, backup and security

devices, tools and monitoring equipment at Central Data Centre.

Providing training, materials and reference manuals to relevant New HAQS System users and transfer of

technology to relevant IT users in LLM.





8

Providing Support and maintenance of Software and Hardware after the New HAQS System has gone

live with clearly defined Service Level Agreement.

Providing the Project Management office that administer, monitor and report all the activities of theproject duration.

As with all integrated information systems development and implementation, the above objectives

that have been laid out by LLM are to address the uniqueness of the nature of LLM business and

operations, CBL are also required to take into consideration in our Technical Proposal the following :-

Timeliness of information access and retrieval

Accuracy of information and trusted single source of information

Reconciliation of data between modules

Transaction audit trail

Quality information processing and reporting

Seamless accessibility from the internal and external users Setting of key performance measures for all LLM operational levels

Well trained system users

Well documented user references

To have a centralised focal Data Centre.

To achieve the above objectives besides developing, and implementing the new HAQS LLM System

The characteristics of the solution that would be able address the challenges identified above are dealt

with in the following section.

3.1 Our Activities

Figure 3





9

3.2 Proposed Approach

We propose a three (3) stage approach, consisting of Analysis, development, testing, migration,

deployment and training and transfer of technology.

Workshops will be conducted for 1) kick-off meeting with stakeholders 2) Validate findings and agree on

the requirements 3) workshop for training

Figure 4

3.3 Requirement Study (2 Months) (1.2)

Understanding the Requirement (2 Months)

Team members: Project Management Team, Testing Team, Development Team, Quality Assurance andDocumentation Team and Hardware Technical Team.

Application Requirement and understanding

We will be liaising with LLM to have detailed understanding of the new LLM HAQS system and its

operations.





10

Understanding existing hardware and additional hardware required

We will be studying existing hardware infrastructure, servers and analyze new options. If required.

Existing Network Infrastructure Study

We will be studying existing network infrastructure and equipment and prepare change plan and

upgrade plan. If required.

Understanding requirement Mobile device software

Scoping the mobile device operational usage and defining policies.

Preparing Project Scope

We will be getting endorsement from LLM on the overall project scope and project charter.

User requirement sign off

At the end of this stage the following are the deliverables but not limited to.

- Project Charter

- Project Management Plan

- Integrated project plan and schedule

- Data conversion and Migration Plan

- Software design document

- Database design

- Data dictionary

- Entity Relationship Diagram

- Deployment strategy plan(Development, Test and Production Environment)

- Network design diagram

- Data center layout and proposal

- Disaster recovery center layout and proposal *if required

- Prototype of the HAQS system

- Configured Servers

3.4 LLM System Development environment (New server and Existing tools will be used)

We will be getting endorsement from LLM after justifying our proposed usage of the new server which

we have done after taking into consideration the data volume, number users accessing and future

scalability of the server. This development environment will be visible to LLM HAQS project team and

development team only. The passwords will be provided to the developers only to connect to the

development environment.

LLM test & training environment (Identifying the Old servers from Current LLM infrastructure)

We will be getting endorsement from LLM after justifying our proposed usage of old LLM servers. If

required.





11

The HAQS system will must be tested in the following browsers (Not limited to)

Internet Explorer 6 or Higher

Mozilla Firefox version 2 and higher Opera Version 9 and higher

Safari version 4 and higher

Google Chrome

LLM production environment

We will be getting endorsement from LLM after justifying our proposed usage of the application server,

database server, Device interfaces, Communication interfaces, 3rd

party system integrations, Firewall,

load balancer, Network Storage, Backup devices and Monitoring tools which we have done after taking

into consideration the data volume, number of users accessing and future scalability.

Development

We will be getting endorsement from LLM after finalizing the scope of the application, database and

various activities performed during the development process and movement of developed codes and

user interfaces to LLM test environment

Training

We will be getting endorsement from LLM after finalizing the training schedule and training plan,

location and total computers required and number of users to be trained for each module.

Deployment

We will be getting endorsement from LLM after finalizing the deployment strategies

and deployment planning. Preparation of data migration Strategy, Preparation of data migration

accuracy confirmation to LLM

Data Migration (6.0)

We will be able to migrate the data from all existing systems with 100% accuracy. This accuracy is

depends on the accuracy of the existing data in all the system (at HQ, Branches and Concession

companies).

We will prepare migration script which will export the data to Microsoft excel format for LLM

verification purposes. Once LLM approves the accuracy of the Data , then we will be able to export the

data from excel format to new HAQS system into testing database.

The migrated data will then be copied to Testing database for LLM verification purposes. Upon receipt

of the confirmation from LLM about the accuracy of the data, we will copy the final data to production

database.

The detailed migration plan will be provided upon the complete study of the existing data structure at

all sub systems at LLM.





12

3.5 Setting up LLM test environment (3.3)

Team members: Project Management Team, Testing Team, Development Team, Quality Assurance and

Documentation Team and Hardware Technical Team.

- Configuring LLM Old servers (1 Application server and 1 Database server) and

computers to be able to test the user interface, logics, functionality and reports provided by

the development and testing team during the development process. Which includes

Upgrading the Servers, Enabling the LLM test servers will be accessible by the Development

team.

- Configuring Applications

The following diagram illustrates the LLM test environment.

Setting up Development environment

- Configuring New Development servers(1 Application and 1 Development server) at

development site which includes

Delivery of Hardware at development site

Installation of Hardware

Installing Development tools in development pcs. The development tools are

o Visual Studio. 2005

o Crystal Reports 2008

o Fusion Chart Version 3

o MS SQL

o Windows Server 2008

o Macromedia Dreamweaver CS4

After this state, the LLM test environment and Development environment will be ready.

3.6 Software Development Life Cycle (SDLC) and Software Testing Life Cycle (STLC) (8.1,8.2)

Hardware Preparation, Manual Documentation, System write-up (4 to 8

thMonth)

Based on the Project charter and scope, developers will precede with development activities at

development site.

Concurrently, Hardware team is preparing production environment, setting up of data center and

network infrastructure.

And the Documentation team is preparing the following documents (but not limited to) for all new LLM

HAQS Modules.

- User Manual

- Operations Manual

- System Manual

- Technical Manual





13

CBL will adopt ‘V’ Model for software development life cycle (SDLC) and software testing life cycle

(STLC).

Testing can involve some or all of the following factors. (Not limited to)

- Business requirements

- Functional design requirements

- Technical design requirements

- Regulatory requirements

- Programmer Code

- Systems administration standards and restrictions

- LLM Corporate standards

- Professional or trade association best practices

-

Hardware Configuration- Cultural issues and language differences

The following figure illustrates the ‘V’ model approach for SDLC and STLC.

Figure 5





14

V-Model of testing incorporates testing into the entire software development life cycle. In the above

diagram of V-Model, the V proceeds down and then up, from left to right depicting the basic sequence

of development and testing activities. The model highlights the existence of different levels of testingand depicts the way each relates to a different development phase.

At the end of the development life cycle, the finalized new LLM HAQS system will be prepared for final

deployment at production environment.

At the end of this stage the following are the deliverables but not limited to.

- HAQS Application User Manuals

- HAQS Operational Manuals(SOP)

- HAQS System Manuals

- Hardware Manuals

-

Source code and inline documentations- Diagnostic manuals

- System architecture

- System design document

- Workflow diagram

- Network diagrams

- Operations Run Book

- HAQS SYSTEM

4.0 System Overview

4.1 General Description of the Overall System Functionality

4.1.1 Development Methodology (1.0,1.1,1.2)

HAQS system will be developed using RAD(Rapid Application Development) software Methodology.

RAD involves the methods like interactive development and software prototyping.

Structured techniques and prototyping are specially used to define user requirements and to design the

final system. The development process starts with the development of preliminary data models and

business process models using structured techniques.

In the next stage requirements are verified using prototyping, eventually to refine the data and process

models. These two stages are repeated iteratively; further development results in a combined business

requirements and technical design statement to be used for constructing final system.

4.1.2 User Requirement Study (2.1 to 2.4 )

We will conduct user requirement study to study user requirements based on individual user groups

and department. The following are the key elements for our requirement study.

To record highway inventory asset by concession company in to the new HAQS system





15

To record periodic maintenance program for C & S and M & E assets

To record asset inspection by concession company

To record information related to monitoring asset inspection by regulatory department and mechanical

and electrical units

To record asset auditing records conducted onsite by the regional office using HAQS mobile module.

To record NCR maintenance information by Concession company.

We will review the data structure of the C & S and M & E highway inventory asset for Yearly

maintenance program.

We will study and consider the data structure for existing system “Sistem Mini Teman(C & S)” andContract Cost Analysis System (CCAS) for M & E.

We will study the inspection checklist form for C & S asset and M & E.

Upon the successful bidder, we will review the existing ICT resources available at LLM and we will

propose the best suitable enhancements needs to be done.

4.1.3 Accessing(4.3.1,5.1,5.2,5.3,3.5,3.6,5.3)

The Proposed solution is an web based application (Portal) runs under IIS web server. It will be

developed in Microsoft Visual Studio.NET 2005 using PHP as the scripting language, Java Script, AJAXTools. Crystal Web reporting Tool 2008, Fusion Chart version 3 for dash boards and SQL server and SQL

manager as the RDBS. We will use the tools existed at LLM for entire development of the HAQS system.

The nature of web based application is, it can be accessible from anywhere and anytime, using

secured SSL and authentication procedures. Based on the assigned access privileges, system will allow

only certain modules and features.

The proposed solution will support industry standard protocols like Digital Certificates, Public

Key Infrastructure, SSL(HTTPS), Transaction Layer Security, VPN.

User login must be based on the password policies and access levels defined by the HAQS

admin users integrated with Active Directory

The following figure will illustrates the application architecture of the HAQS system based on

the locations.

The system will provide the information needed by the users with less than 5 seconds response time.





16

Figure 6

4.1.4 User Interface

The rich layouts and user friendliness of the User interfaces will be maintained throughout the system.

The standardized buttons are provided for common functionalities like “New”, ”Edit”, ”Update”, ”Save”,

”Print”, “Export”, ”Exit” .

User definable mandatory fields are provided. At any time, user may change a specific field as

compulsory field or optional field. On screen field level help system is provided for all user interfaces

throughout the system.

4.1.5 Database Design (4.1.1 to 4.1.3, 2.2.1 to 2.2.6)

We will design the new HAQS database based on the existing data structure after reviewing with the

LLM technical team and we will add new data fields as required for regular assets and asset

management routine for & S and M & E assets.

The HAQS LLM HAQS database will be installed in existing database server cluster at LLM.





17

We will provide the data structure as follows. (Not limited to)

a. Concession company information and User information

b.

C & S periodic asset information like Slope, Drainage, Pavement, bridge etc.c. C & S routine asset information like grass, maintenance, landscaping & Miscellaneous maintenance,

slope cut / embankment maintenance, rest & service area maintenance and environment

management etc..

d. M & E asset information like Building, Tolling System, lighting system, tunnel monitoring system,

traffic control and surveillance system(TCSS) etc..

e. Information on inspection of periodic and routine asset by concession company.

f. NCR information discovered during the asset auditing conducted by the regional offices as the

inspection checklist forms provided with the tender document.

g. Correction or repairing of NCR information by Concession company.

4.1.6 Integration (5.2.11)

System will provide real time integration with other internal or external applications and can import

data formats in the following manner

1. XLS

2. PDF

4.1.7 Scalability

Vertical Scalability – Adding resource within the same logical unit to increase capacity. An example of

this would be to add CPUs to an existing server or expanding storage by adding hard drive.

We will be considering the expansion of HAQS database structure among multiple storage units. Duringsystem life time, if in case of insufficient storage space, system will allow adding new storage units.

Horizontal Scalability – Adding multiple logical units of resources and making them work as a single

unit.

4.1.8 Integration Monitoring Tool

Should the system detect a failure in communication with the HAQS system with its sub modules. A

temporary buffer file will be provided in the design structure of the overall application in order to re-

synchronize data’s between integrated modules, when the system goes online.





18

4.1.9 System Security Monitoring

The following security protocols will be provided in HAQS system

1. SSL integration

2. 32 bit encryption of passwords

3. All password setting and management rules will be definable using HAQS

administrator

4. User Group management

5. User Access Level management

6. User Privileges management

7. Secured document retrieval authentications

8. Detailed transaction audit trails with date, time, user id, terminal id,

transaction id, module name, location id etc...

9. Unauthorized login attempts tracking and alerting will be provided

10.

Controlling multiple failed login and forcing user to get authentication forHAQS will be provided.

4.1.10 Alerts and Notifications(5.4.8,5.6)

There will be four types of alerts and notifications provided in the system.

System defined alerts

These are the prompts displayed by the system detecting wrong inputs, help messages, field validations

and Data saving / retrieval in process and completion notifications

Process completion alerts

These will be definable by the LLM to indicate certain users, on completion of certain processes. (E.g.

Program Schedule submitted by Concession Company)

Workflow alerts

These are the notifications defined from the workflow management under system administration

module. Workflow setting will enable rerouting of the documents and send notifications to the users

upon receiving the rerouted documents.

Transaction notification alerts

These are emails that will be send to LLM HQ users based on work flow on all the transactions

performed in the HAQS system.





19

4.1.11 Reporting(5.4.6,4.5)

We will provide static reports and also query engine to generate ad-hoc reports as per the userrequirement.

We will ensure all the data in HAQS will be searchable using a minimum of two filter conditions.

We will ensure 5 seconds response time for all screens and outputs from new HAQS system.

We will provide dash boards as per the user requirements.

Reporting tool will be provided with the system to generate ad-hoc reports.

All the related modules and reports will be produced as per the design format attached with the tender

documents Appendix 4, 5 and 6.

4.2 Main Modules in HAQS system(5.8)

Based on our understanding, the proposed solution will have the following main modules.(Not limited

to)

System Administration Module

HAQS Administration Module

Highway Asset Inventory Module

Highway Asset Maintenance Program Module

Highway Asset Maintenance Monitoring ModuleMobile Module

4.2.1 System Administration Module (4.4.1 to 4.4.2, 5.4.9,5.5,5.7)

System Administration module is used by the System Administrators to perform the following functions.

i. Creation of New Users

ii. Creation User Groups

iii. Importing the Users from Active Directory in LLM

iv. Monitoring the Audit Trails

v. Monitoring the Unauthorized login attempts.

vi.

Monitoring the network and modules, whether they are online or goes offline becauseof internet interruption.

vii. Database and application backups and restore

viii. Monitoring the disk space and data sizes.

ix. Moving the historical data to archive.

4.2.2 HAQS Administration Module

HAQS Administration module is used by the LLM HQ users to perform the following functions

Work flow Management





20

Defining Document Re-routing and approval processing Rules

Defining Business Rules

Assigning access privileges to the User group based on the job scope

Assigning access privileges to the individual users based on the users job scope Checking the User audit trail and transaction audit trail

4.2.3 Highway Asset Inventory Module(5.4.3,5.4.4)

The asset inventory module allows the Concession company users to record the C & S and M & E assets

and to track the asset inventory.

An unique id is allocated to each asset. All the assets are attached to a Location/Object.

An unique id is allocated to each location/Object. All the locations/Objects are attached a

Route/Highway.

An unique id is allocated to each Route/Highway. The highway information is recorded by the LLM HQ

users with district office details and concession company details.

Drill-down mechanisms will be provided in the system to zoom into the data of the asset inventories as

shown in the figure below.

Zone ->

LocationAssets

Route /

High way

Scheduling

Corrective

Maintenance

Asset Status

History of

Maintenance

works done

NCR

Produced

Figure 7

TO ILLUSTRATE OUR UNDERSTANDING OF THE REQUIRED HAQS SYSTEM AND HOW

USER FRIENDLY THE SYSTEM SHOULD PROVIDE A DASHBOARD TO MONITOR &

MAKE BUSINESS DECISSIONS.

The following figure will illustrates the asset inventory and tracking for a single Route/Highway

Concession Company. This screen represents both C & S and M & E assets of one Highway. Each

Highway is divided into zones/segments. User will be able to zoom into the segment and monitor the





21

asset inventory , concession company maintenance activities and District office periodic a nd routine

inspection records. The status of activities will be represented in color codes as shown in the above

figure.

The screen shows the details of all the assets within this zone and their status.

CBL proposal [Sample]

Figure 8

The following figure represents a single zone related to one highway/ Concession.

This is the second level screen in asset inventory tracking module.

Screen will show the C & S and M & E assets with their status using Ratings provided in the tender

document.

Yearl Schedule submitted

Yearl Schedule A roved

Yearl Schedule Re ected





22

User will be able to drill down further to get more detailed information about the C & S and M & E

asset inventory monitoring purposes.

4.2.4 Highway Asset Maintenance Program Module(5.4.2.5.4.5,5.4.7)

Concession company will use this module to enter the yearly maintenance schedule for M & E and C &

S assets. Including the resources.

Resource planning is provided in the system. System will guide the concession company to search the

available resources (Engineers/Technicians/ workers etc...) .

Work rerouting features will be provided in the system to reroute the jobs to the alternative resources

with in the same level.

Once the scheduling is completed, Concession Company will submit the schedule to district officers for

checking and monitoring of the programs and also co-ordinate the timings and to ensure the programs

are done properly and on suitable time.

CBL proposal [Sample]

Figure 9





23

Program schedule status will be provided in terms of status (Critical/Partial/Normal). And also the

ratings are provided as follows

Rating A Damages done that block the traffic.And for anything that blocks the traffic and for this type of

problem it has to be solved with in 24 hours.

Rating B Damages that need immediate repairs.

And the time is with in 7 days

Rating C Damages that are recommended for maintenance for the

benefit of the highway users.

Time frame is 1 month.

Rating N Routing preventive maintenance. Time frame cannot be

more than 1 month.

District offices will do inspection based on the approved schedule. And update the program status

Compliant / Non Compliant.

In-case of Non-Complaint, NCR (Non compliance record) will be produced and send to the concession

company.

Concession Company will produce the report (repair and Maintenance report) and submit to the

district office to do site visit and to ensure that they have fully comply with the NCR.

Business rules will be provided to define the total number of consecutive failures of NCR. Based on

these business rules, system will alert the regulatory department to execute the performance bond of

the concession company.

4.2.5 Highway Asset Maintenance Monitoring Module(5.4)

Maintenance Monitoring module will be used by the District offices and also LLM HQ users to monitor

the maintenance schedule performed by the concession companies.

Module allows the users to record auditing schedule for the Periodic and routine assets.

Module allows the Regulatory department users to check the assets maintenance status.

Module allows to monitor correction and action taken by concession company based on NCR

Module allows the district office users, regulatory department and top management to produce the KPI

indicators on the resources / maintenance works done by Concession companies.

Monthly KPI maintenance information will be published on the HAQS portal system.

4.2.6 Mobile Module (Inspection Checklists)





24

The on-site auditing checklists are provided in Mobile Module. District officers will record the audit

data on site using mobile device(Android).

The data will then be stored in the LLM HAQS system database for it can be accessible with HAQS

system by district offices, Regulatory department and Top management.

The communication between the mobile devices to the central database is via wifi/3G/GPRS. Offline

synchronization mechanism will be provided in the system.

5.0 Maintenance (9.1.1 to 9.1.6)

The equipments and services provided will be 12 month warranty after the completion of the project.

6.0 Helpdesk(11.1 to 11.3)

Support will be provided as follows:

Support contact number

Support Skype contact

Support email contact

Documents

3. Solutions Write Up