develop spad operator based licensing system

DEVELOP SPAD OPERATOR BASED LICENSING SYSTEM PROJECT

Priority Description

MANDATORY Indicates that the requirement must be made available.Non-availability or non-compliance of this requirement is a demerit.

OPTIONAL Indicates that the requirement is required but SPAD has the right to exercise the option to include or exclude it from the final agreement.Non-availability or non-compliance of such requirement shall not unduly demerit the Tenderer.

APPENDIX T-3: FUNCTIONAL SPECIFICATION

No Functional Requirements Priority Vendor ResponseCompliance Remarks (Must be entered to explain

extent of compliance)Full Partial NoneA. GENERAL

A.1. The purpose of this Tender is to Design, Supply, Deliver, Install, Develop, Customize, Integrate, Test, Train And Maintenance For SPAD Operator Based Licensing System Project.

MANDATORY

A.2. It is tenderer responsibility to ensure that the proposal is complete and accurate and to provide adequate documentary evidence such as published technical literature or brochures to substantiate claims made in this compliance table.

MANDATORY

A.3. Tenderers to provide descriptive answer to each of the questions. Answer such as ‘COMPLY/YES/NO/OK/NOTED/SAME/EQUIVALENT/COMPATIBLE/CAN’ are not sufficient

MANDATORY

SPAD CONFIDENTIAL PAGE 1 OF 34

DEVELOP SPAD OPERATOR BASED LICENSING SYSTEM PROJECTNo Functional Requirements Priority Vendor Response

Compliance Remarks (Must be entered to explain extent of compliance)Full Partial None

and not acceptable and may result in disqualification of the entire proposal.

A.4. Proposed solutions shall include all required components for full functionality and operations of the solution components as specified in this document, such as (but not limited to) hardware, software and services.

MANDATORY

A.5. The scope of this implementation exercise shall cover SPAD Central Region Office and SPAD HQ.

MANDATORY

A.6. The proposed Solution MUST have a user friendly and well integrated web based user interface to facilitate efficient access to designated functionalities.

MANDATORY

A.7. The proposed Solution MUST have the ability to be accessed via a web browser and mobile browser (ie: Internet Explorer, Firefox, Google Chrome & Safari).

MANDATORY

A.8. The Solution must be built on a web-based architecture accessible through a thin client.

MANDATORY

A.9. The proposed Solution MUST be able to be viewed and print via major web browser such as:i) IEii) Safariiii) Chromeiv) Firefoxv) Mobile Browser

MANDATORY




A.10. The proposed Solution should be able to provide tool tips / help to guide user.

MANDATORY

A.11. The proposed Solution MUST have the ability of the application minimum number of users as listed below and with expected growth of user for 10 – 20 % from total user:

i) HQ Office – est 50 staffii) Enforcement – est 200 staffiii) Central Region Office – est 300

staffiv) Northern, Eastern, Southern

Region Office – est 80 staff per region office

v) State Office – est 20 staff per office

vi) UTC Office – est 5 staff per officevii) External user (Public, Operator,

Applicant and etc.

MANDATORY

A.12. The Solution should have a scalable operation and technology infrastructure that can change with expanding business requirements.

MANDATORY

A.13. The Solution should have the capability of executing multiple scheduled actions simultaneously.

MANDATORY

A.14. The solution is flexible for changes in process/ workflow based on policy/circular amendment if necessary.

MANDATORY




A.15. The solution has the capability to create parameter for policies based on each Operator License class.

MANDATORY

A.16. The solution has the ability to automatically prompt the user on the historical record of a particular operator or vehicle for cross checking in relevant modules.

MANDATORY

A.17. Auto generate of correspondence for internal & external stakeholder. Content of correspondence can be easily customized and support multiple language, operator, categorization and etc.

MANDATORY

A.18. The solution must be able to provide the history of all transaction of data updated in the system.

MANDATORY

A.19. The Solution must maintain the same ‘look & feel’ across its entire site.

MANDATORY

A.20. The proposed solution must be easily maintainable and upgradeable.

MANDATORY

A.21. Changes made to any record will be logged in the audit trail. Please provide the details this can be captured in the audit log.

MANDATORY

A.22. Ability to provide the initiation of the workflow by the designated user. These workflows can be automated for scheduled or recurring activities.

MANDATORY

A.23. Ability to do search across module via keywords, wildcards.

MANDATORY




A.24. The design of the infrastructure must implement High Availability (HA) and Disaster Recovery (DR).

MANDATORY

A.25. The solution must have a dynamic reporting capability to generate ad-hoc report and data manipulation by various stakeholders.

MANDATORY

A.26. The solution must integrate with SPAD corporate email and able to provide notification alert to respected recipients via email.

MANDATORY

A.27. The proposed hardware shall include reusing and upgrading the existing infrastructure. The Tenderer also can propose additional hardware if deemed necessary.

MANDATORY

B. LICENSING MODULEB.1. The Solution must be able to cater for the

following licensing process for Road, Rail, Terminal and Tourism operator as below:

a) Receiving of applicationsb) Evaluation of applicationc) Approval of Applicationsd) Appeale) Issuance of Licensef) Issuance of driver cardg) Collectionsh) Impose / amend License Conditions

,

MANDATORY

B.2. The Solution must be able to cater for the MANDATORY




following licensing application for Road, Rail, Terminal and Tourism operator as below:

a) New Applicationb) Renewalc) Variationd) Revocatione) LPSf) Cancellationg) Re-print Documentsh) Appeali) Submission of Incomplete

Supporting Documentsj) Approval for Temporary closure of

train servicek) Approval for Temporary closure of

stationl) Approval for Temporary change of

service frequency / schedulem) Approval for Fare reviewn) Approval for Modification and

upgrading works

B.3. The Solution must be able to cater for the following licensing documents (but not limited to) for Road, Rail, Terminal and Tourism operator as below:

a) Operator Licenseb) Vehicle Permit

MANDATORY




c) Service Permitd) Service Level Requiremente) Lampiran Af) Terminal operator licenseg) Licensed Operator’s Networkh) Service frequency / schedulei) Station locations and facilitiesj) Maintenance location and Facilitiesk) Emergency Response Planl) Condition of Carriagem) Operational Plann) Operational Manualo) Maintenance Planp) Maintenance Manualq) Fare Structurer) Future development planss) Financial reportst) Service Performance reportsu) Training modules

B.4. Operator Management to manage operator information for monitoring and control purpose within the system and cross-checking with other operator for duplicate, zoning, violation, audit report and etc for Road, Rail, Terminal and Tourism operator.

Note:Key information of the Operator, e.g.

MANDATORY




company name, company registration no., address, license class, validity period etc. General and specific terms and conditions for the OL

B.5. Registered Tickets Agents Management to manage registered tickets agents information for registering, revocation, monitoring and control purpose within the system and cross-checking with other operator/tickets agents for duplicate, violation, enforcement, audit report and etc for Road, Rail, Terminal and Tourism Operator.

Note:Key information of the Tickets Agents for e.g. ticket company name, ticket company registration no., address, license class, validity period , etc. General and specific terms and conditions for the OL

MANDATORY

B.6. Vehicle Permit Management to manage vehicle information for monitoring and control purpose within the system and cross-checking with other operator for duplicate, zoning, violation, audit report and etc for Road, Rail, Terminal and Tourism operator.

MANDATORY




Note:Summary of all VPs attached to the OLKey vehicle information, e.g. VP no., vehicle type, registration no., chasis no., vehicle age, expiry date, etc. General and specific terms and conditions of the VP

B.7. Service Permit Management to manage route information for monitoring and control purpose within the system and cross-checking with other operator for zoning, violation, audit report and etc for Road, Rail, Terminal and Tourism operator.

Note:Summary of all permitted routes attached to the OL. General and specific terms and conditions of the SP

MANDATORY

B.8. Service Level Requirement (SLR) Management to manage SLR information for monitoring and control purpose within the system and cross-checking with other operator for zoning, violation, audit report and etc for Road, Rail, Terminal and Tourism operator.

Note:Conditions to be fulfilled by Operator, covering aspects such as safety, customer

MANDATORY




service, reliability and accessibility. KPIs will be added in stages

B.9. Schedule Time Management to manage information for monitoring and control purpose within the system and cross-checking with other operator for zoning, violation, audit report and etc for Road, Rail, Terminal and Tourism operator.

MANDATORY

B.10. Schedule Fees Management to manage information for monitoring and control purpose within the system and cross-checking with other operator for zoning, violation, audit report and etc for Road, Rail, Terminal and Tourism operator.

MANDATORY

B.11. Designated Depoh (Operator Operating Address) Management to manage operating address information for monitoring and control purpose within the system and cross-checking with other operator for zoning, violation, audit report and etc for Road, Rail, Terminal and Tourism operator.

MANDATORY

B.12. Terminal Management to manage information for monitoring and control purpose within the system.

To provide terminal information management which comprises of terminal categorization, list of bus operators in each

MANDATORY




terminal, list of operator and etc.B.13. To register information and detail of the

operators i.e. applicant, company details inclusive business registration number, financial details, license’s class/category applied for processing and monitoring purposes.

MANDATORY

B.14. To provide information on status of the application at every process level/ stage

MANDATORY

B.15. To provide email-trigger notification for every milestone in the application process for applicants information or feedback via email or printed letter.

MANDATORY

B.16. To be able to issue “Surat Tawaran Kelulusan” (STK) at respective state office.

MANDATORY

B.17. To provide flexibility for submission of application at any SPAD Offices for processing.

MANDATORY

B.18. To provide customizable parameter setting for Operator Licensing Policies for policies based on each OL class for e.g express bus, school bus, stage bus and etc.

MANDATORY

B.19. Performance Monitoring (KPI) for every operator for easy reference in renewal, suspension, revocation or variation applications.

MANDATORY

B.20. The system must be able to provide presentation to Licensing Committee, this

MANDATORY




would enable Licensing Committee to make a decision based on statistic and projection.

B.21. Cross check payment records and register all collections from licensing fee processes and to be linked with Accounts Dept's system for monitoring, control and reporting purposes.

MANDATORY

B.22. To provide ability to roll-back transaction that has been posted.

MANDATORY

B.23. To provide auto-renewal notification for defined range of license and permits to operator via email or printed letter.

MANDATORY

B.24. To provide ability to process application for Tourism Vehicle

MANDATORY

B.25. To provide ability to reprint license and permits after application for lost documents is processed.

MANDATORY

B.26. To provide capability to extend the age limit of vehicle allowed and to capture all details of recommendation, approval, remarks and etc.

MANDATORY

B.27. To provide capability to integrate with other Enforcement Division and Complaint Unit to cross-check on suspension, revocation or under investigation cases and to cross-check on operators' performances based on public complaints.

MANDATORY

B.28. Integration with SPAD revenue collection system / account department to manage

MANDATORY




and monitor collection / transactionOperator management module to manage and monitor operators.

B.29. To provide capability to add new operator category introduced in future for e.g. multi-operator capability

MANDATORY

B.30. To provide capability registering agent under the licensed operator to sell tickets legally for e.g. registering express bus tickets agent.

MANDATORY

C. ENFORCEMENT MODULEC.1. To provide capability to perform

Enforcement process as follows:a) Operation Process

Planning Field Operation Investigation Compound

b) Audit Process

MANDATORY

C.2. To provide capability to register, monitor and track the following enforcement operation (but not limited) :

c) Berkalad) Bersepadue) Harianf) Risikan/Pemantauang) Hippoh) Parasit/Alieni) Tegas

MANDATORY




j) Serkapk) Ulatl) Aduan (from Complaint Module)

C.3. To provide capability to register the following enforcement case (but not limited) :

a) proses I.Pb) kompaunc) amarand) mahkamahe) bekuf) NFAg) TPR (Timbalan Pendakwa Raya)h) Legal (SPAD)i) Train accidentsj) Service Disruptionk) Late/poor emergency rescue planl) Late/poor maintenancem) Late/ poor passenger service

MANDATORY

C.4. To provide capability to register, process, monitor investigation process.

MANDATORY

C.5. To provide capability to check the status of case and to provide the status to other division for cross-checking.

MANDATORY

C.6. To cross check with integration data from PMhS for actual route taken and reconcile against approved route and time table for service permit violation reporting.

MANDATORY




C.7. To provide real-time online enquiry via mobile or tablet via feasible technology to assist enforcers anywhere 24-7 (mobile enforcement).

MANDATORY

C.8. To integrate with other module but not limited to licensing, screening, complaint, legal and etc.

MANDATORY

C.9. A case-based management to facilitate enforcers and legal to keep-track cases

MANDATORY

C.10. To provide audit capability for operator license and vehicle permits, service permits and service level requirement audit.

MANDATORY

D. DRIVER CARD MODULED.1. To register information and detail of the

applicant for road and rail driver for monitoring purposes.

MANDATORY

D.2. To record and process the driver card application, list of vehicle allowed to drive, license class and category, applicant and expiry date, number & type of applications, status of application.

MANDATORY

D.3. To provide capability to record driver records as follows (but not limited):

a) Training records;b) last issuance of driver’s certificate;c) last date medical examination;d) employment records;e) past driving mileage experience;

MANDATORY




f) offences and criminal records;D.4. To provide capability to read applicant

personal data from MyKad and capture information into system.

MANDATORY

D.5. To scan and record the applicant photo for application processing.

MANDATORY

D.6. To provide capability to add category of other railway critical personnel for registration purpose such as operation traffic controller; station master; track/wayside workers; etc.

MANDATORY

D.7. To provide capability to alert and print summary of expired critical personnel / train driver cards according to type of license.

MANDATORY

D.8. To register information and detail of the applicant for road and rail driver for monitoring purposes.

MANDATORY

E. ENQUIRY MODULEE.1. The proposed Solution should support

parameterized selection criteria for inquiry list function

MANDATORY

E.2. To provide information on status of the application for every process level/stage

MANDATORY

E.3. The proposed Solution shall have a built-in search capability for multiple searching or filtering of license, operator, vehicle, route, time-table, fees, depoh, offences, application type and etc within the system.

MANDATORY




E.4. The search engine shall be able to facilitate automated indexing of data for faster search results.The search engine shall support collaborative taxonomy which automatically generate business taxonomy and categorize results into common sense groupings by source or topic.

MANDATORY

F. ADMINISTRATION MODULEF.1. The Solution must maintain the same ‘look

& feel’ across its entire site.MANDATORY

F.2. Access rights to module based on user roles and types.

MANDATORY

F.3. Self-service password management to facilitate user to reset and change password.

MANDATORY

G. PAYMENT MODULEG.1. To register all collections from licensing fee

processes and to be linked with Finance Department system for monitoring and controlling purposes.

MANDATORY

G.2. System must be able to differentiate collection by various category that is useful for us whenever it is required in future, i.e. statistic purposes, reporting or investigation, category that shall be provided but not limited to the following:a) operator category ie road, rail, terminal and tourism

MANDATORY




a) license category i.e.; expresses bus, school bus, taxi, excursion bus and etc.b) process category i.e.; new application, renewal, license printing & etcc) region category i.e.; by state, by region & etc.d) company category i.e.; Bhd, Sdn Bhd, JV, Malaysia-based foreign entity, etc

The above requirement will ease the process of identifying collection fees, for reporting & statistic purposes. The systematic of the collection book keeping will ensure all the audit trail can be simply identified, should be any miscalculation of dispute.

G.3. Integration with 3rd party online payment system but not limited to FPX, online banking, meps and etc.

MANDATORY

G.4. To issue out digital & printed receipt with serial number to replace the current buku resit for all payment transaction. Digital receipt will be part of audit module.

MANDATORY

G.5. To register all collections from licensing fee processes and to be linked with Finance Department system for monitoring and controlling purposes.

MANDATORY

G.6. System must be able to differentiate collection by various category that is useful

MANDATORY




for us whenever it is required in future, i.e. statistic purposes, reporting or investigation, category that shall be provided but not limited to the following:a) operator category ie road, rail, terminal and tourisma) license category i.e.; expresses bus, school bus, taxi, excursion bus and etc.b) process category i.e.; new application, renewal, license printing & etcc) region category i.e.; by state, by region & etc.d) company category i.e.; Bhd, Sdn Bhd, JV, Malaysia-based foreign entity, etc

The above requirement will ease the process of identifying collection fees, for reporting & statistic purposes. The systematic of the collection book keeping will ensure all the audit trail can be simply identified, should be any miscalculation of dispute.

H. SCREENING MODULEH.1. The system must be able to provide

workflow for data entry and presentation to Licensing Committee. Refer to Appendix 9 - RPT Application Processing Flow document for workflow system information.

MANDATORY

H.2. To cross-check on suspension, revocation or MANDATORY




under investigation cases- To cross-check on operators' performances based on public compaints

H.3. The system is able to set up the evaluation criteria for new and renewal of license.

MANDATORY

H.4. The system is able to set the scoring of the criteria set and automate the evaluation process, the scoring must be able to auto detect and prompt the information.

MANDATORY

H.5. For licensee which has met the license limit (i.e. sole proprietorship/partnership) to automate block features to prevent granting of license in excess of limit set.

MANDATORY

H.6. The system is able to register all member details of partnership information and able to cross-check the members across other operator license ownership, application and etc.

MANDATORY

I. REPORTING MODULEI.1. The proposed solution should provide the

admin users with detailed data and allow creating custom reports. All reports should be exportable to multiple file types and can be scheduled for automatic delivery.

MANDATORY

I.2. Customized Statistical Reports – the solution shall provide and easy and fast report generation on ad-hoc basis.

MANDATORY




I.3. The solution should be capable to support query or ad-hoc report without the need of technical skill (Tenderer to identify the custom report writer tools).

MANDATORY

I.4. The solution shall be simple, user friendly interface and easy-to-use that eases user learning curve.

MANDATORY

I.5. To provide flexible and user friendly reporting parameter.

MANDATORY

I.6. Support flexible and comprehensive reporting and analysis, such as Ad-hoc reporting.

MANDATORY

I.7. Empower Business Users to create ad-hoc report in shortest time (in minutes to hours).

MANDATORY

I.8. Feature report writing functionalities to integrate with proposed database and standard office excel sheet.

MANDATORY

I.9. Easy sharing with authorized users. Allows non-technical business users to create interactive, and real-time dashboards.

MANDATORY

I.10. Ability to display report/statistic on the map. E.g Operator/Bus distribution on map.Online/real time inquiry capability, including drilldown capability from summary level to detailed transaction level for all major reports.

MANDATORY

I.11. Provide standard report for list of Report to identify dormant operators, Report to

MANDATORY




identify errant operators and etc.I.12. Data generated by the reporting tools must

be consumable and manipulate by 3rd party/external party via standard protocol/technology/files.

MANDATORY

J. COMPLAINT MODULEJ.1. The solution must be able to support the

process of Customer Services (complaint, Enquiry, Feedback/Suggestions) as per defined processes.

MANDATORY

J.2. To enable the public to check the status of their complaints. This will ensure that the public would be able to track their complaints and get the latest update on their case status.

MANDATORY

J.3. To categorize the type of vehicles and type of complaints.

MANDATORY

J.4. Ability to automatically prompt the user on the historical record of a particular operator or vehicle.

MANDATORY

J.5. To provide information related to company ownership, so relevant information can be checked and extracted (This will enable the call center staff to check the correct vital information (eg. Contact number & person) especially for urgent related cases

MANDATORY

J.6. To enable the public to use self-help in lodging their complaints by linking the

MANDATORY




system with SPAD's corporate websiteJ.7. To provide integration process flow to

enforcement module for further processing of complaint.

MANDATORY

J.8. To migrate/integrate with current complaint system.

MANDATORY

J.9. To integrate with other module but not limited to licensing, screening, enforcement, legal etc.

MANDATORY

J.10. Provide a multi-tier support based on case severity/category

MANDATORY

J.11. Provide a ticketing system to keep-track complaint cases.

MANDATORY

J.12. Provide a statistical report capability. MANDATORYJ.13. To integrate with other government

complaint channelMANDATORY

J.14. To keep a profile of the caller details and history eg. Name/ic/add/contact no./cases for future reference.

MANDATORY

J.15. To integrate with the receiving channels, current telephony module when receiving calls, SMS – CTI (computer telephony integration.

OPTIONAL

K. LEGAL MODULEK.1. To provide for the registration of cases that

are handled and/or forwarded to Prosecution Unit to handle.

MANDATORY




K.2. To provide cross check with integration data from JPJ and PDRM for building up prosecution cases.

MANDATORY

K.3. To provide capability for case status reporting, this status shall be able to be viewed by Enforcement Division, Admin Unit and Licensing unit but only the Prosecutors may access it. There should also a function whereby upon conclusion of a case that status will be automatically be prompt to Enforcement Division, Admin Unit and Licensing units. That information will be beneficial to them in their performance of operation functions for e.g. the Licensing units may use the outcome of a case for revocation and suspension, while admin unit can use the same where there are forfeitures of assets in which, the assets forfeited will transfer to SPAD to be dealt with accordingly according to SOPs and MOF Treasury circulars.

MANDATORY

K.4. The database must be able to be generated into customized reports as need be.

MANDATORY

K.5. Police, JPJ and Puspakom relevant data is required to be prompt/feed into system for legal and licensing unit for the purpose of demerit and merit points, freezing of transaction and suspension and revocation

MANDATORY




of licenseK.6. To have alert/notification via email to

remind any pending cases.MANDATORY

K.7. To integrate with other module but not limited to complaint, enforcement etc.

MANDATORY

K.8. Renewal in licensing module will have visibility on legal court case compound before renewal process.

MANDATORY

K.9. To provide dashboard of list of offences according to multiple parameter that can be customized from drop down list.

MANDATORY

K.10. To have ability to drill down the offences from the dashboard.

MANDATORY

L. ONLINE MODULEL.1. To enable the public & Licensed Operator to

check information directly from website to check their application status, expiry date, enforcement status and etc.

MANDATORY

L.2. To enable information center to get most comfortable, reliable and value for money of taxis or bus express and etc services.

MANDATORY

L.3. To enable grading on operator or vehicle services, public can simply choose which grade of vehicle services they should take. i.e. taxi services or express bus services.Grading will encourage healthy competition amongst services operator.

MANDATORY

L.4. The solution must provide a separate access, MANDATORY




interface and environment for public users (non-SPAD) to access. Non-SPAD may refers but not limited to operators, public citizen etc.

L.5. Ability to provide online enquiry of information submitted.

MANDATORY

M. WEB SERVICE(INTEGRATION)M.1. Have the capability to interface with our

internal systems and external systems.MANDATORY

M.2. To integrate with external agencies such as:i. SSM

ii. JPJiii. Puspakomiv. PDRMv. Immigration

vi. JPNvii. Motour

Note:This will provide the correct source for data and also for immediate action of offense for foreign registered vehicle and foreigner

MANDATORY

M.3. To integrate with internal systems such as:i. CTSSii. DISiii. PMHSiv. SPAD Financial systemv. BRIS (GIS)vi. EDMS




vii. ERPviii. CRM / ISPAAA

Note: The tenderer can propose a better or suitable integration technology if needed.

M.4. To manage central blocking of operator license, permit application that are registered as bankrupt, court case, vehicle offenses and etc.

MANDATORY

M.5. To allow the public to perform certain transactions at Post Office or MyEG online services such as Drivers Card, renewal of vehicle permits, summon payment and etc

MANDATORY

M.6. The solution to be able to integrate with EDMS for easy access of scan documents for e.g. accessing of all scan supporting documents during application process will provide easy and centralized access reference.

MANDATORY

M.7. The integration with EDMS shall have the ability to do document search including but not limited to these file extension:• PDF• DOC and DOCX• XLS and XLSX

MANDATORY

M.8. To scan and record the applicant photo, copy of MyKad, training and medical reports, certificate and police reports. This

MANDATORY




required for future reference and centralized database.

M.9. The solution must be able to integrate with internal collection and accounting system to manage and monitor collection and transaction.

MANDATORY

N. MigrationN.1. To provide migration program & scripts to

migrate existing operator license records to operator license master records.

MANDATORY

N.2. To provide migration program & scripts to migrate existing vehicle records to vehicle master and vehicle permit records.

MANDATORY

N.3. To provide migration program & scripts to export existing routes rote master and route permit associate with vehicle license record as “remark “ for reference (Currently system captured route info in free text format)

MANDATORY

N.4. To provide migration program & scripts to migrate existing operator operating address records to operator operating address master records.

MANDATORY

N.5. To provide migration program & scripts to group existing operators associate with vehicle licenses into operator license record. (to be Operator Based Licensing System)

MANDATORY

N.6. To provide migration program & scripts to migrate driver record.

MANDATORY




N.7. Migration program & script to migrate and enhance the following Modules:

i. Modul Permohonan Baruii. Modul Permohonan Ubahsyarat

Surat Tawaraniii. Modul Permohonan Membaharuiiv. Modul Permohonan Ubahsyaratv. Modul Kemaskini

vi. Modul Pungutan Hasilvii. Modul Penguatkuasaan

viii. Modul Pemanduix. Modul Pertanyaanx. Modul Penyelenggaraan Admin

xi. Modul Pengkuatkuasaanxii. Modul Pengurusan Aduan

MANDATORY

N.8. To create a data migration to transfer current data (vehicle-based permit) to new (operator-based permit) without losing its integrity. The migration plan must include data cleansing process to eliminate any redundant data. The plan must also include restructuring the current database or developing a totally new one. The design must emphasis on scalability, performance, data integrity etc.

MANDATORY

O. MASTER/PROFILE DATAO.1. The Tenderer is expected to provide the

following master data management but not MANDATORY




limited to the following:

O.2. Operator master data, list of operators including the basic information on the company registration number, status, name, contact details, address, financial details, contract details, agreement, local authority approval information, board of directors, audited reports data and etc.

MANDATORY

O.3. Vehicle Mater Data, list of vehicle specification including the basic information on the model, engine capacity, passenger capacity, year make, year register, etc.

MANDATORY

O.4. Route Master Data, list of routes including the basic information on the route, GPS coordinates, bus stop, operating hour, frequency and etc.

MANDATORY

O.5. Schedule Fees Master Data, list of fees table for approved fees including the basic information on the fees, start fees/destination, end fees/destination, scheduled fees, GPS coordinates, bus stop, operating hour, frequency and etc.

MANDATORY

O.6. Schedule Time Master Data, list of time table for approved time table including the basic information on the time, start time/destination, end time/destination,

MANDATORY




scheduled fees, GPS coordinates, bus stop, operating hour, frequency and etc.

O.7. Designated Depoh Master Data, list of operator operating address records for approved operating address(parking vehicle) including the basic information on the address, size, approval permits, GPS coordinates, operating hour, frequency and etc.

MANDATORY

O.8. Driver master data, driver database to all public transportation driver (Bus, Taxi, etc.) information including the name, IC number, operator and etc.

MANDATORY

O.9. Ability to keep track of errant operator, driver, historical information including or any crime associate with the operator/driver.

MANDATORY

O.10. To provide version of changes to all master data above and not limited to the above, for eg change of master data can be updated and historical records can be viewed for each of the changes done.

MANDATORY

P. SECURITY, ACCESS & AUDIT TRAIL

P.1. The solution must be able to secure access through a user group access by menu, field

MANDATORY




level according to job function, department, branches, etc.

P.2. The solution is able to define access type e.g. create, change, delete or read only for different group of users.

MANDATORY

P.3. The solution shall allow a particular user to be associated to more than one access group.

MANDATORY

P.4. The solution must be able to provide audit trails for all maintenance of user ids, sign on attempts, password changed, etc.

MANDATORY

P.5. The solution must support tight session expiration period as to prevent any security breach during sessions left idled (auto logoff features for idle session).

MANDATORY

P.6. The solution is able to disable user id after multiple failed attempts to sign on.

MANDATORY

P.7. The solution must maintain sufficient audit trail and incident logs to track usage information such as user session and failed connection and for trouble shooting purposes.

MANDATORY

P.8. The solution must record user identification, level of authorized access, roles, session IP, session start date/time, session end date/time, etc.

MANDATORY

P.9. Ability to support secure Https User authentication.

MANDATORY




P.10. Solution shall support ‘complexity password’ which is the combination of numeric, alphabet and special characters.

MANDATORY

P.11. The proposed Solution MUST have the audit trail capability features for all transaction executed within the application.

MANDATORY

P.12. The proposed Solution shall be able to provide list of all historical record of previous application process for reference to check the event transaction that have taken place.

MANDATORY

P.13. The proposed Solution shall be able to capture key audit trail information but not limited to the following:i) User ID/Level of authorized accessii) Date/Timeiii) Action takeniv) Descriptionsv) Terminal Id/Session IPvi) Session start date/time, session end date/timevii) Value of change before and after

MANDATORY

P.14. Able to clearly design and segregate internal and external type of access to protect and detect wrong assignment of internal access right to external parties.

MANDATORY

P.15. Able to design screen accessible to group of Users based on the common role defined

MANDATORY




but only able to perform transaction or draw information specific to the User-id.
