irrigation management system development and piloting of …5.6 ui/ux 16 5.7 language support 16 5.8...

)For

Development and Piloting of WMO-Registration & Irrigation Management System

Prepared BytA, Dhaka- 1000

Supported ByAccess to Information (a2i) Program, Prime Minister's office

Terms of Reference (TOR) for WMO-RIMS

Table of ContentsTABLE OF CONTENTS 2

1. BACKGROUND 3

2. REvIEW OF EXISTING SERVICES 4

2.1 About the Organization 42.2 EXisting Services (As-Is) 42.3 Problems and Challenges 5

3. PROPOSED E-SERVICE (To-BE) 5

3.1 e-Service Objectives 53.2 e-Service Scope 5

4. E-SERVICE FUNCTIONAL REQUIREMENTS 6

4.1 Solution Architecture 64.2 e-Service Functions and Features 74.3 Users and User Roles 104.4 Security and Privacy Requirements 114.5 Integration Requirements 114.6 Hosting Requirements 12

E-SERVICE NON-FUNCTIONAL REQUIREMENTS 12

5.1 Application .Compliance Requirements 125.2 Sizing, Performance and Scalability Requirements 135.3 Business Continuity 145.4 Interoperability and Data Exchange 155.5 System Audit 155.6 UI/UX 165.7 Language Support 165.8 Accessibility 165.9 Coding Conventions 165.10 Documentation : 175.11 Tools and Technologies to be used 175.12 Quality Attributes and Assurance 185.13 Copyright 19

6. SCOPE OF WORK 19

6.1 Development and Implementation Methodology 196.2 System Requirement Analysis 196.3 System Design ~ 206.4 Development 216.5 Integration , 216.6 Testing 216.7 Hosting 226.8 User Acceptance Test (UAT) 226.9 Management and Migration of Legacy Data 226.10 Deployment and Implementation 236.11 Training and Knowledge Transfer 236.12 Maintenance and Support Service 246.13 Duration of the Project and Work Station 246.14 Work Distribution and Team Composition 256.15 Expected Deliverables 27

7. CONCLUSION 28

5.

The vendor has to provide with an on-line end to end solutions for the 'WMO Registration andIrrigation Management System' of BWDB', starting from planning and survey and ends 287.1 Clients Responsibilities 287.2 Consultants Responsibilities 28

Prepared by BWDB, Supported by a2i, PMO (TOR-Template V:2.2) Page: 2


1. Background

Bangladesh is a rapidly growing and developing country of south-Asia where 160million people lives within only about 147.5 thousand sq. km area. So, water resourcemanagement for flood management & food production to ensure our national foodsecurity is one of the basic mandates of Bangladesh Water Development people'sparticipation, and delivering government services to the farmer and enhance Board(BWDB). To ensure the effective implementation of BWDB's development projects,regarding irrigation management system: peoples' participation and deliveringgovernment services to the farmer and increase administrative and financialaccountability of GoB organization E-service delivery system may be a promisingtool. Digitization of public & private services has been accepted as one of the bestinnovation and development tool all over the world. Digital Bangladesh by 2021 is the'Charter for Change'. It is a long term vision that takes ICT as the prime tool to makethe services of the government easily accessible to citizens. Since its inception in2009 the government has been working relentlessly through numerous innovativeinitiate water sectors' developments with a sharp focus to ensure delivery of suchservices to those who are the least served. The initiatives include transformation ofmanual service delivery systems to e-service design, development andimplementation.

The government of Bangladesh has recently initiated Annual Performance Agreement

(APA) under Government Performance Monitoring System (GPMS) and a record of

understanding between a minister representing the peoples' mandate and the secretary

of a ministry or division responsible for implementing the mandate. Among the

mandatory activities of APA every Departments has to choose and transform one

manual service into an e-service by June 2017. With a view to develop institutional

capacity through designing and developing a comprehensive work plan for

implementing the selected service to an e-service a2i came forward to create a

resource pool and help them make a TOR with service features. In this context one of

the services ofBWDB, that is, "WMO (Water Management Organization) registration

and Irrigation Management System" has been selected to innovate an e-service system

t><&> ~ ~~Prepared by BiVDB, Supported by a2i, PMO (TOR-Template V:2.2) Page: 3

Terms of Reference (TOR) for WMO-RlMS

So initiative taken by Ministry:

The initiatives taken by the Bangladesh Water Development Board, Ministry of Water

Resource are as follows

(i) Online Flood Forecasting and Early Warning System

(ii) Online Recruitment Management System

(iii) Online Attendance management System

(iv) Auto Real Time Data Acquisition System (ARTDAS)

(v) Geographic Information System(GIS) Based Digital Land Information System

(Pilot Phase)

Current thinking of BWDB towards this e-service:

BWDB is trying to improve this slow, tiresome and less accountable manual systemof delivering the irrigation service, poor recovery of irrigation service charge byinnovation of online service system. The a2i Program of PMO has taken initiative toselect this service to design and guide so that it can be the one selected services to betransformed into e-service under AP A 2017-18.

2. Review of Existing Services

2.1 About the OrganizationBangladesh is a rapidly growing and developing country of south-Asia where 160million people lives within only about 147.5 thousand sq. km area. So, water resourcemanagement for flood management & food production to ensure our national foodsecurity is one of the basic mandates of Bangladesh Water Development people'sparticipation, and delivering government services to the farmer and enhance Board(BWDB).

2.2 Existing Services (As-Is)The current manual process of WMO registration and irrigation service delivery of

BWDB is primarily provided towards the farmers. The services include Formation of

different committees, arrangement of election, registration of WMO, providing

irrigation etc. Theses services has been identified with too many physical

visits(about 18 times), excessive costs involvement(about 70000 BDT) and additional

time(About 18 Days). Moreover, the quality of the service fails to satisfy the service

recipient. The lack of transparency and accountability culminates to their sufferings.



On the other hand, government needs a lot of employee to manage the manual process

in different layers of offices, which is time consuming & error prone.

2.3 Problems and Challenges

• Registration process of WMO is taking more time.• Delay in irrigation service and lack sufficient water in dry season.• Difficulties in collecting Service charge.• Due to lack of maintenance of Hydrolic structures(Sluice gate, Pump House

etc.) irrigation serive is hampered gravely.• Irrigation Canals/Dykes are not dredged in time.• Survey, identification and formation of WMO and collection of information

from end farmers• Holding Election and committee formation• Transaction of information from field level (in case of problem)• Training and enable the end farmer to cope with the system

3. Proposed e-Service (To-Be)

3.1 e-Service Objectives

• The main objective is to provide with the best possible irrigation services tothe end farmer so that, the ultimate crop production of the project areaincreases to the highest level. The e-service will ultimately help to improve thesocio economic development of the end people.The e-service will faster the survey and data collection, committee formation,registration process so that, the service delivery will be smooth and efficient.The field level information can be received in shortest possible time so that, itcan be addressed and can be solved in time especially the infrastructure relatedIssues.Develop & implement a user-friendly, interactive, web-based System forWMO Registration & Irrigation Management for BWDB.The system should provide suitable flexible interactive user-friendly tools toallow collation of inputs from PEs and produce standard reports anddisseminate information to stakeholders in a systematic way.

•

•

•

•

3.2 e-Service Scope

• Planning, House hold Survey of detail farmer's information for WMOformation.

• Collection of Project, irrigation area, Hydraulic Structure information.• WMO Adhok and Election Committee formation.• Arrangement of Election for formation ofWMO Executive Committee

through Election• Preparation of by-laws by Executive Committee as per PWMR-2014• Application for WMO's Registration by Executive Committee

Prepared by BPVDB, Supported by a2i, PMO (TOR-Template V:2,2) Page: 5


• Sorting, verification, Validation & sending application to ApprovalAuthority

• Approval ofWMO's Registration & Issues of Certificate• Development of Irrigation Water Distribution and Irrigation Service

charge system• Training Management,• Service Rating• Complain management

4. e-Service Functional Requirements

4.1 Solution Architecture

Solution architecture is expected to define and describe an architecture of the proposed e-Service Solution in the context of the mentioned prevailing service delivery process i.e._lI'JI!lllr_.lli ••llljJjl•• ~I.The solution architecture should assistin the translation of the service to e-Service transformation requirements into a solution.vision, high-level operations and/or lCT application specifications and a portfolio ofimplementation scope. The expected architecture of a solution, where the solution is a e-Service system that should offers a coherent set of functionalities to it's environment. Assuch, it should concerns those properties of a solution that are necessary and should besufficient to meet its essential requirements. The vendor shall propose a comprehensivesolution architecture on WMO-Registration & Irrigation Management System which maycover the following items in their descriptive and diagrammatic presentation

• Goals/Results• Service Recipients• e-Service Operators/User (Service Providers)• e-Service Observers (Service Administration and Performance Monitor)• Database application components:• Entity application component:• Utility component• System federation (Systems to be integrated)• Process application component• Interaction application component• Application• Accessible Points• Networks• Types or Layers of Service Delivery Points• Hosting Site

Prepared by BfY!)!3, Supported by a2i, PMO (TOR-Template V:2.2) Page: 6


4.2 e-Service Functions and Features

Module: Project & WMO (WMG, WMA, WMF) Information Management

Project Profile User will Input Project informationmanagement (name, code, description,

geographical location, cost, timeframe etc.) through web based input PD/SEIXEN Websiteform.User may also import projectinformation through Web ServiceAPI from

2 Project Area Wise User will Input Project Irrigable websiteIrrigation Information area & Net Irrigated area through .)Management through web based input form. PD/SE/XENUser will also import these data

information through Web ServiceAPI from

3 WMO(WMG, WMA, Options to Create/Update/Delete PD/XENIDCE websiteWMF) Database WMO (WMG, WMA, WMF) O/EOManagement member Information

Options for reportGeneration(lndividual/Collective)

Module: WMO Formation & Management

Committee CreationIModificationiDeletion and DCEO/ WebsiteManagement report generation of Farmers

• WMO ad-hoc Committee• WMO General Committee• Election Committee• Executive Committee

2 WMO formation • Fixing & boundary setup WMO(WMG, WMA, WMF).

• Fixing & list of the Number ofWMO DCEO/ Website/appsFarmers• Options to Create WMO

• Farmer Detail Information• Enlistment of House holds

3 Online Polling • Creation of Schedule for electionManagement • Selling and submission nomination

paper through web/mobile app• Shortlist of Nomination Paper• Appeal through web/mobile app• Candidate Finalization DCEO/• Allocation Ballot/Sign ( Protik) Farmers

Mobile Appsand Print Ballot Paper

• Organizing and conductingelection

• Declaration election result andresolution

• Generation

6@J~

'~u, J..v,--

Prepared by BWDB,. Supported by a2i, PMO (TOR-Template V:2.2) Page: 7


4 Auto generated by- • Auto generate Draft by-lawslaws preparation

• Draft by-laws finalization by DCEOIPEC/General Committee through CWM Websitesystem

• Online verification of Draft by-lawaapproval.. . '\Module. Onlme Registration

On-line Application for WMO registration Application WMO Websiteregistration submission through online (with

Attachment2 Application process To Process(Saving & Validation) DCEOIPEO/ e-filing (Nothi)

Application form for WMO CWM

3 DCEO/PEO/ NotificationCWM

4 DCEO/PEO/ e-filing (Nothi)CWM

5 System

6 Notification for Certificate After Successful registration a WMO ( Farmer) SMSCollection Notification of Registration Certificate

will be sent SMS7 WMO online account, & Executive Committee and WMO ( Farmer) Website/UDC

members information WMO(WMG,WMA,WMF) allMember informationoptions for create/update/delete and

Generation8 Online Certificate Delivery Authorized users can Download WMO ( Farmer) Website/UDC

Management certificate from Digital archive byunion center

Module: Irrigation Water distribution service

1 Digitally Irrigation Digitally manage irrigation XEN/DCEO Digital Irrigationwater distribution data by Prepaid Digital system (DIS)

Meter orSMS2 Mapbase Irrigation GIS Based Mapping of XEN/DCEO/Far DIS/Website

Di 'tal control mer3 LLP Scheme system LLP Scheme control Prepaid XEN/DCEO/Far DIS/Website

D' , Meter mer4 Gravitational Scheme control XEN/DCEO/Far

Scheme mer5 LLP Scheme LLP Scheme Schedule XEN/DCEO/Far DIS/Website

schedule creation/edit/approval from mer

6 Gravitational Gravitational Scheme XEN/DCEO/FarScheme schedule Schedule mer

O~ e> --i.tv.,~'Prepared byBH'DB, Supported by a2i, PMO (TOR-Template V:2.2) Page: 8


management creation/edit/approval fromauthority

7 Irrigation calendar Scheduler for mapping in XEN/DCEO/Far Website/UDC/Smanagement Irrigation calendar by the mer MS

users

Module: Beneficiary Service & Irrigation Management

1 Member profile All Members information DCEO/Farm Website/UDCmanagement (profile) are stored and retrieve er

through database

2 Member/user Show Irrigation information Farmer/user Dashboardirrigation status status (user, WMG, WMA,

WMF, AEO, EO,SDE,DCEO/XEN are higherauthority) through dash board.

3 Online training, Water management, WMO DCEO/Farm Website/ MobileTraining material & management and about crop erschedule training through Online basedManagement (off-line, Video ,UDC)system Training information

4 On-line complain

5 Service rating Provision for both way service Farmer Mobile/ Appsrating regarding Farmersatisfactory level about theservice and managementaccountability through mobileapps/ mobile, service chargecollection and maintenance

Additional Features Requires but not limited to

• The application/system will have different Access Control• The application/system will have User Registration and Management Module

. • The application/system will have Login Management and User TrackingFacility and Privilege Creation, Allocation, Control and Management.

• The system should have complete embedded security measures against thedata hacking/ tampering, data access, and data in transit etc.

• The proposed system will have the facility to generate various reports andquick views such as certificates issued in a specified time period or certificatesissued from a specific office etc.

• The system should have User log book

Prepared by BHlfHI, Supported by a2i, PMO (TOR-Template V:2.2) Page: 9


• The system should have All possible search options and facilities forcertificates.

• Data/report export/print facility in PDF, CSV, XML, Excel, Email.• The system should have Regular/periodical backup and storage facility of

database• The system should have Easy recovery and restoration facility of system files

and database.

Technology

The consultant is expected to maintain consistency in technology standards chosen for thedesign and development of WMO-RlMS to ensure consistency and compatibility withBWDB's existing system. Client's choice will be given preference for selection oftechnology.

BWDB currently has a Linux based system with Oracle Database.

Transfer of Knowledge (Training)

• Training on the functional as well as technical aspects of thesoftwarelApplication developed is an integral component of the Project.

• The front users (From the Recipients and General User, approximately 5000 &180 respectively) shall be trained on the functional aspects and selectedadministrative users (approximately 5) shall be trained on administrative &technical aspects of the system.

• General users shall be trained in Reporting tools. .• The consultant shall develop two separate "Manuals" each for training and

reference purpose for functional as well as technical training.• The technical training program shall expose the trainees on technical know-

how of the system developed in order to equip the trainees for providing firstlevel support and be able to maximize the utilization of the Application.

4.3 Users and User Roles

S1.No User Type Users No. Of users

1 System User System Analyst or lCT Focal Point 05

Higher Authority of theOrganization(DGIADGI 180

2 General user CE/CWM/ ACE/PDIPEO/DCEO/XEN)

DEOIXO 350

3 Service Recipient User WMO(Farmers) 300000

Vendor should submit a comprehensive plan and approach covering different types ofusers and their roles providing accessibility, privacy, confidentiality and transparency basedon the given statics. Also have to mention the user friendliness login system.

Prepared byBH'DJJ, Supported by ali, PMG (TOR-Template V:2.2) Page: 10

Terms of Reference (TOR) for WMO-RlMS~j>smlN~:''''~M:~'''~'....;~;,i3~,-',,"i,'

If the proposed e-Service application needs to integrate and interoperable withgovernment prescribed e-Filing system (a2i e-Filing) then vendor should have design theseamless, smooth and user friendly single login system.

4.4 Security and Privacy Requirements

The vendor should submit an extensive and complete security and privacy plan for this e-Service application considering the following issues

• Project technical scope• Functional and nonfunctional requirements and ultimate objectives• Concerned service provider organization's operational environments and capacity• User roles - Accessibility, Authorization and Accountability• Importance of data management• Technologies to be used for development & run• Hosting• Client and service side• Overall standard application security requirements.

Apart from these, the vendor should keep in account the following considerations also aswell as vendor should provide a checklist based on system and hosting security plan (i.e.fraud, hacking, money laundering etc.) & have to provide the test report of that checklist.

4.5 Integration RequirementsAs a government system or e-Service application, integration with the required and other

prescribed national system is very important and essential. Only by proper integration makinginteroperable, an e-Service application can drive the ultimate citizen benefits with theoptimum use of technology from service to e-Service transformation. Here vendor shouldcome up with an integration plan in their technical proposal considering and understandingthe scope of the e-Service application as per this TOR. The possible integration scopes of thise-Service application are mentioned below as reference for the vendor

S1.No Name of The Name of the Integration Stage PurposeSystem Organization

1 NID Election WMO DB Management Verification &Commission AuthenticationSecretariat

SMS Telecom • Committee Management NotificationOperators • WMO Formation

• Online Poling• Application• Notification for CertificateCollection & BillingInformation

Payment BWDB&A2I Service Charge MembershipGateway Fee, Schedule

Prepared by]}WDB, Supported by a2i, PMO (TOR-Template V:2.2) Page: 11


Fee & ServiceChargeCollection

e-Filing A21 Application Process & ApprovalApproval

Digital BWDB Irrigation Water Distribution at DigitalIrrigation LLP scheme IrrigationSystem Water

DistributionServiceChargeCollection

SIMS/SPMMS BWDB Project Profile management ProjectProject Area Wise Irrigation InformationInformation Management Geographical

Mapping

4.6 Hosting Requirements

Bangladesh Government is providing an extensive and standard hosting facility for alltypes of government organization applications and software that is named as National DataCenter under Bangladesh computer council (BCC). It may be mentioned here that the vendordeveloped application will be hosted in BWDB own data center. Therefore, at this stage,vendor is requested to submit a preliminary hosting plan for this e-Service applicationconsidering the issues mentioned below-

• Hosting requirement /environment (hardware, servers, network, security,storage, traffic, firewall, bandwidth etc.)

• Hosting architecture• Data growth and scalability plan• User handling/load balancing mechanism• Licensing issues• Scheduled backup & restore requirements• Disaster recovery requirements• Monitoring tools requirements

5. e-Service Non-Functional Requirements

5.1 Application Compliance Requirements

5.1.1 Web Application

• The application which is a web based solution, has to be hosted in acentralized Web-server

• The application should be developed following Service Oriented

15@ e-: ~L>1Lk'Prepared by BWDB, Supported by a2i, PMO (TOR-Template V:2.2) Page: 12

'I'


Architecture (SOA)

• Application should support MVC framework.

• Considering the operating/client environment at different level of thisapplication, it should be developed in such a way so that it requires lowbandwidth to run.

• The web-based application should support cross browser platforms(popular web-browsers such Mozilla Firefox, Opera, Chrome, InternetExplorer, Safari etc.)

• Should have ability to seamless integration with future module /components / applications

• Application should be lightweight and rich client-side scripting

• UI should be developed based on the analysis of ux.• Any web interface of this application should be fully responsive

5.1.2 Mobile Application Requirements

• The mobile application version of the system should be developed forAndroid and iOS.

• The mobile app should have capability of displaying system notifications

• Functionality for registration options for service recipients

• App should enable compact view of services for service recipients.

• There should be an option to auto synchronization with the centraldatabase with apps local database on the availability of the Internetconnecti vi ty.

5.2 Sizing, Performance and Scalability Requirements

• T~e .syste~ shall be capable of handling online functionalities for a database of at1Ia.IIJJ'~1l1 service recipients and in terms of service provide EllOfficers(General User) and IISystem Users.

• The system processing shall be scalable to support the volume estimates for a periodof 10 years at a 20% annual growth rate.

• The system shall be designed to handle estimated Midium Scale: SOOO simultaneousconnection (online users) when it is ultimately rolled out.

• The vendor must conduct an extensive load testing task taking above factors intoconsideration and submit a load testing results.

Prepared byBIT'DB, Supported bya2i, PMG (TOR-Template V:2.2) Page: 13


• The database architecture should be such that the system IS available to user24x7x365 days a year without any unapproved downtime.

• Page load time, login response-time, on-click load time for the web application shouldbe less than 3 seconds while this is accessed over the intranet.

• Average transaction response time, on-submit response-time, or any other databaseaccess/ search time should be less than 5 seconds when the system solution isaccessed over the intranet.

• Considering the network infrastructure challenges in Bangladesh, the solution mustsupport low bandwidth conditions for the services defined in the functionalrequirements.

• In case of mobile application also, this should support very low bandwidth even in 2Gnetwork provided intemet bandwidth.

• The proposed solution should be highly scalable to accommodate current and futurerequirements within the scope of the scope mentioned in the TOR

• Analyze the requirements whether both horizontal scaling (scale-up) and verticalscaling (scale-up) will be required for this e-Service application or not?

• The e-Service application should be provided with appropriate caching mechanism tohandle very high-traffic scalability

• The vendor may propose here other relevant measures for the e-Service applicationscalability.

5.3 Business Continuity

Business Continuity plan will play a very important role by creating the systems ofprevention and recovery to deal with potential threats and risk of the e-Service operation.Vendor is requested to propose a Business Continuity Plan for this e-Service application.Regarding business continuity you may take in account the followings issues if applicable orsuitable for this e-Service Application

• All standard backup facilities should be supported by the system which can be startedwith disk based backup facility, gradually moving to Storage Area Network (SAN)based backup system.

• Data and the Operating system core component will be separated. A ghost image ofthe Operating system will always be available in case of rebuilding the server. Alldata can be restored in the data drive once the Operating System is restored.

• System can also have an automated Backup mechanism by which users can schedulethe backups and the system will take the backups without manual intervention.

• System must check for the media and generate a report on backup with date time anddetails of backup.

• If a restoration fails for any reason, the system should prompt with proper errormessages and suggest what has to be done to rectify the situation via on-screen, logs,email and text messages.

Prepared by BiVDfJ, Supported by a2i, PMD (TOR-Template V :2.2) Page: 14


• System should maintain an automated recovery system and all versions of backup willbe maintained. At any given point in time, the versions and incremental backupdetails can be retrieved from the system.

• The system may be hosted in virtual servers or containers. A restore of a virtualserver/container is much easier and faster compared to a single host server.

5.4 Interoperability and Data Exchange

The selected vendor must develop this e-Service system following all the standards andprotocols of interoperability, integration and data exchange with other systems. It is expectedthat the system will be based on open architecture and will be fully interoperable with thecurrent and future systems.

The following are the key expectations on interoperability requirements:

1. The system should be designed for interoperability using industry standard protocols.

2. System must expose data by Advanced Message Queuing Protocol and REST via TLS

3. All imported data must undergo data validation to ensure full integrity.

4. Data exchange within the system at different levels via the internet shall be encrypted.

5. The system should have functionality to exchange data with other own systems orexternal institute systems.

6. The system shall have functionality to export/import files based on the standardtemplate defined through web services and/or API

Full API documentation must be provided so that third party integrators can integrate theirsystem with this system.

5.5 System Audit

This e-Service system will maintain an audit trail of any changes or updates made in anyinformation that are considered as vital and should maintain the audit log with informationsuch as

• Log the users who are accessing the system• Log the parts of the application that are being accessed• Log the fields that are being modified• Log the results of these modifications• Log attempted breaches of access• Log attempted breaches of modification rights• Timestamp.

Prepared by.BJVDB. Supported bya2i, PMO (TOR-Template V:2.2) Page: 15


Ensure an audit trail is kept for all transactions and all audit transactions logged are kept onthe trail file or trail database from where system can generate different audit reports as andwhen required.

5.6 UIIUX.

The vendor must propose a UII UX plan containing UI designing method and tools,prototype or Mockup design (if applicable) , UI review method , process for study andanalyze UX , collaboration of basic web and mobile UX issues and expected result andoutcome of UX, fmalizing the UIIUX design. Apart from this, the vendor should consider thefollowing issues as requirement at the time of UIIUX plan.

• The system interfaces should be highly user friendly, easy to navigate and ensure fastloading.

• The UI shall design by using well-established, supported and lightweight UIframework so that it follows widely used industry flow patterns

• UI shall be easily configurable if any changes are needed

• Menu, content and navigation shall be based on the user entitlements, roles andpernussions.

5.7 Language SupportThe e-Service system should support multilingual option i.e. Bangla and English for both

the Web version and Mobile Apps. All the user interfaces will be able to display and inputcontrols can take input both in BangIa and English. System! App users can choose and sethislher preferred language in profile setting for the system interfaces. The system shouldsupport Unicode for the Bangla Language.

5.8 Accessibility

Vendor must develop this e-Service application ensuring access for the citizen (ServiceRecipients) with disabilities in different standard accessible formats. e-Service applicationshould be developed in "universal design" and "assistive technologies". Accepting andfacilitating the use of sign languages, augmentative and alternative inputs and all otheraccessible means, modes and formats for inputs and outputs as per their choice by "ServiceRecipients" with disabilities; All e-service features (Web application or Mobile Application)should be usable with the help of screen reading software by the service recipients withdisability

5.9 Coding ConventionsThe vendor must follow the standard coding styles to produce high-quality code for

further uses of the code in terms of reusability, refactoring, task automation, language factors

Prepared by INVDB, Supported by a2i, PMO (TOR-Template V :2.2) Page: 16


etc. The vendor should submit a standard coding convention approach, which may includedifferent conventions like commenting, indent style, naming etc. following the best codingpractices.

5.10 DocumentationDetail and proper documentation of such rCT based project like e-service application

development and implementation for Government is very vital and essential. Documentationis required for any such project as reference, knowledge transfer, analysis of developmentand implementation history, baseline information for any modification or change, guidanceetc. In this issue, Vender should shows highest-level of professionalism for delivering thestandard documentation approach at each phase of e-Service development andimplementation project. Vendor should include an extensive documentation plan of thisproject in their technical proposal, which may cover the followings

• Documents titles phase or activity wise• Purpose of document• About the format of documents (if possible only index or fields)• Type of expert and skilled resource will be used for documentation• Document priority and dependency• Time requirement for preparation (If applicable)

5.11 Tools and Technologies to be used

Vendor is recommended to choose the appropriate tools and technologies to be used forthe development and . . of the e-Service .. The selected vendor has toconsult with a2i and to finalize the tools,technologies, framework and platform with the approval of same authorities consent.

The main components of the software will be web based application. It should be run inWindows/Linux/OSx operating system at user end and should be compatible to all majorbrowsers such as - Internet Explorer, Firefox, Google Chrome, Opera etc.

The System UI should be compatible with Tab & Smart Phone browsers and in case ofMobile Apps should be support both Android and lOS

Understanding the details scope of this project, vendor is requested to submit acomprehensive plan in their technical proposal following the table format mentioned below

System Requirement

Project Management

Version Control

Prepared by BWD/1, Supported by ali, PMO (TOR-Template V:22) Page: 17


Analysis

System Design

Development (Client end)

Development (Server end)

API/Web services

Apps

Testing

Integration

Hosting & Deployment

Documentation

QA

Helpdesk/Support

Reporting

Communication

5.12 Quality Attributes and Assurance

The Quality attributes and Assurance plan will describe the standards, processes andprocedures in this e-Service application development life cycle which will be used to supportthe consistent delivery of high-quality, professional standard e-Service application andservices provided in the support of an automated environment. The quality assurance processwill be concerned with establishing the authority of the QA function, quality assurancestandards, procedures, policies, and monitoring, and evaluation processes to determinequality in relation to established standards. Quality assurance activities will concentrate onthe prevention of problems through the continuous improvement of processes.

In order to provide high quality products and services, each support team will adhere toprocesses, procedures and standards. Quality Assurance (QA) is a process used to monitorand evaluate the adherence to processes, procedures, and standards to determine potentialproduct and service quality. It will involve reviewing and auditing the products and activitiesto verify that they comply with the applicable procedures and standards, and will assure theappropriate visibility for the results of the reviews and audits.

The vendor is requested to provide an extensive Quality Assurance plan with measurableattributes for each phases of this e-Services development life cycle in their technical proposal.

Prepared by IJWDB, Supported by a2i, PMO (TOR-Template V:2.2) Page: 18


5.13 Copyrightshall be entitled to all proprietary rights

including but not limited to patents, copyrights and trademarks, with regard to many Vendor.

All kinds of source code including code documentation and other approved documents(all versions trail, products, developed applications, documents and all kinds of deliverableswhich bear a direct relation to or is made in consequence of the services provided by thevendor under this scope of this TOR.

At the request of the Bangladesh water Development Board (BWDB) , the vendor shallassist in securing such property rights and transferring them in compliance with therequirement of the applicable law. After the completion of the project such rights will behanded over to the Bangladesh water Development BO<.lTd(B\VDB) s) that will be producedat the time of entire system development and implementation life cycle under the scope ofthis TOR will be owned by Bangladesh water Development Board (B\VDB).

The vendor should properly deliver all the entire approved source codes and otherdeliverables to the Bangladesh water Development Board (BWDB) . The vendor cannotclaim any royalty or authority of any sort in case of replicating the source code or database orany other deliverables under this TOR for any future use that Bangladesh water DevelopmentBoard (BWDB) and the Government of Bangladesh may see fit.

Any studies, documents, reports, graphics or other material prepared by the vendor forthis project under this TOR shall belong to and remain the property of Bangladesh waterDevelopment Board (B\\/D13)

6. Scope of Work

6.1 Development and Implementation Methodology

Development methodology i.e. SDLC plays a very important role to clear the ultimateproject objectives precisely, to stable the project requirements, to monitor the progress withmeasurable deliverables and managing the entire project efficiently. Here the vendor isrequested to propose and submit a best possible suited SDLC approach for this projectconsidering the project scopes, requirements of e-Service, objectives, organizationalenvironmental factors and behavior, project timeline, ultimate deliverables and variousresources to be used.

6.2 System Requirement AnalysisRequirements finalization will be a very important milestone of vendor's proposed

development methodology. It is expected that, the selected vendor will carry out detailedrequirement study and analysis on the each and every scope of e-Service that mentioned inthe TOR. Under this scope of work, the selected vendor has to analyze the detail functions,

Prepared by BiVDB, Supported by a2i, PMD (TOR-Template V :2.2) Page: 19


processes, documents, actors, sites and infrastructure of the relevant prevailing systemprecisely of the concerned organization. At this phase, vendor's ultimate objective will befinalization of the e-Service requirements in details under the scope of TOR and approval ofthe concern organizational authority. Here vendor is requested to propose and submit asystem requirement analysis plan which should cover the scope of work at this phase,relevant activities to be performed, time line, deliverables to be produced, dependencies andresources to be used.

6.3 System DesignAt this phase, the detail functional scope defining and designing as per the standard of

software engineering approach for the proposed e-Service system tasks are being performed.This is very vital and important phase of any SDLC. Considering the ultimate developmentand implementation scope, the proposed system design should be robust, scalable, userfriendly and interoperable enough.

".""".Atthis system-designing phase, vendor may performs following designing related taskand will produce various standard System Designing Documents (SDD):

• Identifying module, components, tasks, I/O and functional features

• Specifying technical and functional requirements

• User Interface design

• Description of UI and requirements

• Preparing the use cases

• Defining Integration and interoperability scope

• Designing system architecture

• Determine process and data flow

• Database design

• API design

• Finalizing tools, technologies and frameworks to be used etc.

Here vendor is requested to cover details system designing plan in their technicalproposal, which may include relevant activities, approaches, methods, documentations anddeliverables.

The consultant firm will discuss with the client to identify the information need to be

Prepared by B iYDB, Supported by a2i, PMD (TOR-Template V :2.2) Page: 20


collected and how the information will be disseminated. The firm will assess all the needs fordeveloping a final design for WMO-RIMS in consultation with the client and will submit apreliminary design(Graphical and Architectural) of WMO-RIMS which will be finalize inafter approval of the client.

6.4 DevelopmentAt this stage, vendor must take prior acceptance or approval from the concerned authority

on tools, technologies and framework that will be used for the development of the e-Serviceapplication. Based on approved SRS and SDD, vendor will prepare a comprehensivedevelopment plan for the e-Service Application which should include a schedule consistingdevelopment item wise start date, test date, review date, completion date etc. At thedevelopment stage, vendor must follow the standard code convention, code leveldocumentations, header of each file, algorithms, interfaces, code compression and APIsshould be supplied with proper description and documentations. All kinds of standard testingtasks that are required to be performed at the development phase, should be mentioned in theplan. Considering the scope mentioned in the TOR for this e-Service application, vendor isrequested to include a preliminary development plan (standard approach) in their technicalproposal.

6.S IntegrationConsidering the above mentioned Integration requirements and scopes for this e-Service application, vendor must includes a phase in their proposed development andimplementation methodology approach. At this stage, the vendor will perform allnecessary tasks regarding integration to make the e-Service application interoperable.

6.6 Testing

The vendor must propose a testing plan for this e-Service application starting fromdevelopment to deployment. This testing plan should cover all the standard suitable testingapproaches for this e-Service application which may include phase wise testing activities liketest scripting, test cases, testing tools, testing process, test log, result and report formats i.e.expected test deliverables based on the application development requirements. The vendorshould submit testing plan which may include standard test approaches. Some are mentionedbelow as examples for reference

• Unit Test• Functional Test• Installation testing• Compatibility testing• Smoke and sanity testing• Regression testing• Stress Testing

Prepared by BWDfJ, Supported by a2i, PMO (TOR-Template V:2.2) Page: 21


• Acceptance testing• Alpha testing• Beta testing• Functional vs non-functional testing• Continuous testing• Destructive testing• Software performance testing• Usability testing• Accessibility testing• Security testing

6.7 HostingVendor should submit primary hosting requirements for this application related to

hardware, servers, network, security, storage, traffic, firewall, bandwidth etc. i.e. completehosting infrastructure that will be requires for their developed application hosting consideringthe . Based on their submitted requirements, regarding hosting 26.

, will provide detail hosting infrastructure,facility and environment.

6.8 User Acceptance Test (UAT)User Acceptance Test (UAT) is a very vital and essential phase in the e-Service

development lifecycle. At this phase, all types of users must test the developed e-Serviceapplication by themselves and have to provide a details feedback! test report . Based on theUAT report, vendor has to update the application accordingly to ensure user satisfaction bymaking it more user friendly. Here, it is expected that, considering the type of users and theirrole in the e-Service application, the vendor must propose a comprehensive UAT plan in theirtechnical proposal which may cover the followings:

• UAT activities to be perform (planning, designing test cases, selection of testing team,Executing test cases and documenting, Bug fixing, sign-off etc.)

• Types of user wise roles and test items distribution• resource requirement,• activity wise time requirement

• activity wise test case, test results/ deliverables• detail user feedback / test reports

• System update plan

6.9 Management and Migration of Legacy DataUnder the process of service to e-Service transformation, during e-Service activation or

deployment, it may be necessary to move the legacy data of prevailing services. In this case,

Prepared by BWDB, Supported bya2i, PMO (TOR-Template V:2.2) Page: 22

Terms of Reference (TOR) for WMO-RlMS4'\w,;ot:l~~'i<'!fW)_,"'~'

·~....,,~,*,'i~.''';

vendor may require to perform different relevant activities that may include data collection,softcopy conversion, data filter, data cleansing, data verification, data process, data entry,data migration and overall data management. Here, it is expected that, the vendor willpropose their detail data management and data migration plan for this e-Service applicationconsidering the estimation of legacy data mentioned below which will be required to migrateinto the developed application.

The plan may cover amount of data to be migrated, activities to be performed, amount ofresources to be used, required time for different data migration phases for different activities(data collection, hardcopy to softcopy conversion, data entry, data transformation from softcopy, data filtration, data cleaning, data verification) etc.

6.10 Deployment and ImplementationThis is the phase of SDLC , when the consent is being given to "GO LIVE" of the developedsystem after completed all kinds of development integration, testing and hosting. This isvery crucial and sensitive stage for a Government application because at this stage the systembecomes public and expose to access towards all levels of users. The Pilot or full scaleimplementation period starts formally in this stage only ..Vendor is requested to propose theirdeployment and implementation plan covering the major activities to be performed , thedeliverables to be provided etc.

6.11 Training and Knowledge Transfer

• The vendor must propose a detail training plan for the users of the e-serviceapplication.

• The vendor should include necessary training methodology, documentation andtraining materials support in their training plan

• The training materials may include user manual ,administration manual, quickstart tutorial, online help, frequently asked questions

• The training plan must describe the sequencing, time, duration and resourcesinvolved in implementation of each of the consultant's proposed trainingactivities.

• The training plan should contain full course descriptions for all courses that to becarried out for respective users.

• The vendor should develop multimedia training materials for all users. Thesematerials shall be available for viewing and reviewing for all users through a webportal.

• The training instructions should support both English and Bengali language.

Prepared by BI.JiDB, Supported by a2i, PMG (TOR-Template V:2.2) Page: 23


• The training activities should cover the training feedback, evaluation and reportalso.

• The vendor also need to propose their smooth, efficient and effective knowledgetransfer idea and plan here in this technical proposal with the training plan.

6.12 Maintenance and Support ServiceThe selected vendor has to provide a period of 2(Two) years maintenance and support

service. After the development and deployment phase when the implementation period startsthe vendor has to provide maintenance and support service for the 2 (two) years. Here it isexpected that, the vendor must provide a detail maintenance and support service plan in thetechnical proposal, which may include the followings:

• Support service types and mode of services• Service desk functionalities• Configuration management

,._.-. Change management

• Service layers for support• Tools will be used for Support service management• Communication management and modality• Release management• Incident management• Problem management• SLA (Service Level Agreement)• Maintenance and support service related reporting• Support service types• Service Log Management

Apart from the above mentioned issues, if vendor thinks any other issue to be included intheir plan, it would be considered as added value addition.

6.13 Duration of the Project and Work StationThe selected vendor will need to work for the above-mentioned scope as per approved

project management schedule. The selected vendor must complete e-Service applicationdevelopment and deployment i.e. development life cycle as per their proposed developmentmethodology within 1(One) year Including training and testing period excluding themaintenance and support service period ..

Now here in their technical proposal vendor is requested to propose detailed timeframeplan which may include:

• Total duration of the e-Service application development t.e, e-Servicedevelopment

Prepared by BWDf}, Supported by a2i, PMO (TOR-Template V:2.2) Page: 24


• Total duration of the Maintenance and support service at implementation phase

• Proposed SDLC Phase wise and deliverable wise time distribution and duration

• The schedule may cover Activity, Deliverables, Time in Days, Dependencies etc.

• Can be present as table or Gantt chart

6.14 Work Distribution and Team Composition

The vendor is expected to provide work distribution and team composition plan asdeemed suited based on this project requirements and milestones and as per their proposeddevelopment and implementation methodology approach. The interested applicant (Vendor)should provide a team composition plan in their proposal describing the position, roles, tasksto be assigned, expected man-days of involvement, expected deliverables and required skilland expertise.

However, for proper execution of the project i.e. e-Service application the vendor mayinclude at least the following personnel as minimum requirement

(a) Key Personnel's:

Name of The Position No of Qualification expenencePersonnel

Project Manager 1 Masters in CS/CSE/ITI 10years' experience inCE or Master in WRE or Software DevelopmentMBA ( BSc in ManagementCS/CSE/ITIEEE/CE/WRE/B.Sc. Ag)

Sofware Architecht/Sr. 1 BSc in CSE/CS/IT 7 years' working experienceSofrware Engineer with minimum 5 years'experience in related field.

System Administrator 1 BSc in CSE/CS/IT 7 years' working experiencewith minimum 5 years'experience in related field.

System Analyst 1 BSC in CSE/CS/IT/EEE Proposedpersonnelshouldhaveat least 10 years' workingexperiencewithminimum5years' experiencein relatedproject.RelevantCertificationwillbe addedadvantage.

Database Designer 1 BSC in CSE/CS/IT/EEE Proposed personnel shouldhave at least 10 years'working experience withminimum 5 years'experience in related field.

Prepared by mVUIJ, Supported by a2i, PMO (TOR-Template V:2.2) Page: , 25


Sr.DeveloperlProgrammer 1 Minimum Bachelors 05 years' workingin any computer experience in related field.science relateddiscipline

Apps. Developer 1 Minimum Bachelors 3 years of working

in any computer expenence.

science relateddiscipline.

Developer IProgrammer 2 Minimum Bachelors 3 years' working

in any computer experience in related field.

science relateddiscipline.

VX Expert 1 Minimum Bachelors 3years' workingin any computer experience in related field.science relateddiscipline.

Business Analyst 1 BSc in 5 years of workingCS/CSE/IT IEEE/CE/W expenence.RE/Ag)

QA Expert 1 Minimum Bachelors 5 years' experience within any computer minimum 03 years'science related experience in related field.discipline

Interoperability Expert 1 Minimum Bachelors 5years' workingin any computer experience in related fieldscience relateddiscipline.

Trainer 2 BSc in CS/CSE/IT/EEEI at least 5 years' workingCE/WRE/Ag) expenence.

Technical Document Writer 1 Minimum Bachelors 5 years of workingin any computer experience.science relateddiscipline

VI Designer 1 Minimum Bachelors in with at least 5 years'any science discipline working experience

Implementation Project 1 BSc in CS/CSE/ITI 3 year's workingManager (for Piloting CE/Ag) expenence.Phase)

(b) Support Staff:

Jr. Developer 1 Minimum Bachelorsin any com uter

2 years' workingexperience in related field

Name of The Position No of QualificationPersonnel

expenence



science relateddiscipline

TechnicalAssistant 1 Minimum Bachelors 3 years' working. .III any SCIence expenence.discipline

Surveyor 1 Minimum diploma in Not requiredsurvey from anyreputed institute

IT Executive ( for Piloting 2 Diploma c in CS/CSE/IT 5 year's workingPhase) expenence.Data Entry Control 2 Diploma in Computerl 2 years' workingSupervisor (for piloting Bachelor Degree expenence.Phase)Data Entry Operator (for 6 Diploma in Computerl Not requiredpiloting Phase) Bachelor Degree

*Maintenance Support 2 years

Pilot Implementation 2 Place ( Fulgazi, Feni District & Dalia, Nilphamari District)Infrastructure (PC, Server, Laptop, Tab, Mobile, Router, ups, LCD display etc), HROutsource (DEO,DEC,IT Executive and Implementation Project Manager), Sensitization &Training, Advertisement, Operation and Electrical Works &others) .

6.15 Expected Deliverables

Considering the scope of service and scope of work of this project and based on theproposed project development & implementation methodology, the vendor has to submit herea complete list of all types of deliverables will be produced throughout the entire projecttimeline whether those are materials, services, applications, source codes, documents, plans,reports etc. in a table format mentioning the stages, activities and timelines.

Some examples of the deliverables are mentioned here under for your reference.

• Project inception and management report• System requirement specification (SRS)• System design document (SDD)• Complete source code• Detail source code documentation• Test plan with test scripts and testing reports• Technical documentation (system architecture, module integration points, workflow

engine, data dictionary, user manual etc.)• Training plan and reports• Training materials and user manuals• Integration plan and reports

• Audit log• Mobile Application• Web application

6{)J ~~Prepared by BFfDfJ, Supported by a2i, PMO (TOR-Template V:2.2) Page: 27


• UAT Report• Maintenance, agreement & SLA• Maintenance and support log• Hosting requirement specification, plan and report• Implementation plan and report• HR activity plan and report• Progress and review reports

7. Conclusion

The vendor has to provide with an on-line end to end solutions for the'Development and Piloting of WMO-Registration and Irrigation ManagementSystem' ofBWDB', starting from planning and survey and ends

7.1 Clients ResponsibilitiesFacilities provided by the client and access to data and Information: Client will arrangethe following facilities for the consultant:

• Client and field units would provide data, if available and access to the project relatedinformation that may be necessary for the Consultant to carry out its assignment, andfacilitate field visits, access to beneficiaries, consultant.

• BWDB will arrange available data/maps for the project work as identified by theconsultants at the Inception Stage and subsequent project implementation.

• Client will engage technical IT personnel to co-ordinate with consultants III

developing the system,• Client will monitor and recommend as per requirements and. standards of its

organization.

7.2 Consultants Responsibilities• The consultant shall carry out the services as detailed in scope of consulting services

in the best interest of the Client for the successful realization of the project with thereasonable care, skill and diligence with sound technical, administrative and financialpractices and shall be responsible to the Client for the discharge of responsible.

• In performing their duties, the consultant will work under the overall supervision ofICT Cell BWDB. The Team Leader will be responsible to the System Analyst, ICTCell, BWDB for proper and timely execution of all the activities and submission ofthe outputs/reports.

• The technical IT Team of the consultants will co-ordinate and consults with thetechnical IT personnel of the client in developing the system.

~vt~~~'~H'?i.:~\!rt\::Afll.?.";Ff

e( '11'1 »fiR <IT<f'{i<j711·~t~O]1t:'1·"!"'itR 15:411'1 C'lri!3,miT I

~.\5Tf~~~~P9r~<!j"lif.,'it

~fit~, "!t~, Ol<i'ttt.,,~,,"[email protected]

dlr"ft"'l'fi'f+lTb"o-,,-:s.Q~:'<1~17

Prepared by BFVDB, Supported by a2i, PMO (TOR-Template V:2.2) Page: 28