EXHIBIT 5-A

 

PM Connect’s Proposal to the

Monterey Peninsula Water Management District (MPWMD) related to the Water Demand Division Database (WDD-DB) Project

 

 

January 14, 2004

 

Overview

 

The Water Demand Division (WDD) of the Monterey Peninsula Water Management District (MPWMD) desires to improve existing business processes through the development of a single database system to handle all areas of the Water Demand Division (WDD).

 

Currently, there are many separate systems, as well as many manual forms which all relate to applications, permits, inspections, and other areas under the management of the WDD. These systems were developed under the DOS and Unix operating systems and do not have a graphical user interface.
 

Incorporating a graphical user interface and integrating these systems into one system will help WDD staff be more efficient and effective in their daily operations.

 

In addition, it is required that the new system be “web enabled”, meaning that areas of the WDDs database that are available to the public will be incorporated into the District’s web site.

 

Proposal

 

PM Connect is a project management consulting company based in Monterey. We’ve been in business since 1985 helping our clients manage technology projects.

 

Since late December 2003, Dan Swaigen from PM Connect has met with Inder-Mohan Osahan and Rob Cline several times (for a total of 16 hours), addressing these areas:

·        Defining the scope of the project

·        Defining the top-level business processes to be addressed

·        Understanding the existing system, both from a user and technical perspective

·        Started to define detailed WDD business processes

 

PM Connect proposes to assist MPWMD with six (6) key areas of the WDD-DB project:

           

  1. Develop and document the business processes and procedures to be supported by the new WDD-DB system.

 

  1.  Develop and document the technical specifications for the WDD-DB project

 

  1. Develop input screens, user interface, forms, and reports to be available in the new system.

 

  1. Assisting the CTO with development of a prototype of the new system.

  2. Develop a Request for Qualifications (RFQ) for a vendor to design, code, and test the WDD-DB project.

  3. Assist with the selection of a vendor to develop the system.

Costs, Resources, and Schedule

 

PM Connect will provide a consultant (Dan Swaigen) at a rate of $125/hour on this project. We have estimated the total cost for this project to be $38,000. Assuming a start date of 2/2/04, the completion of this project (date for selecting the vendor) is estimated to be 6/16/04.

 

Summary level estimates for project hours and costs are as follows:

 

ITEM #

Description

Cost

Hours

Start

Finish

 

 

 

 

 

 

1

Work Process Flow Diagrams

4500.00

36

02/02/04

02/13/04

2

Input Screens

2500.00

20

02/16/04

02/27/04

3

Forms

3750.00

30

02/16/04

02/25/04

4

Reports

6500.00

52

02/25/04

03/17/04

5

Technical Specification and Prototype

15000.00

120

03/17/04

05/07/04

6

Request for Qualification (RFQ) for Outside Vendor

2750.00

22

05/07/04

05/14/04

7

Vendor Selection

3000.00

24

05/07/04

06/16/04

 

 

 

 

 

 

 

Totals

38,000 

304

 

 

 

 

We have attached a detailed project plan which provides more information including detailed tasks associated with each summary area above. The summary areas and associated deliverables are also described in the next section.

Description of Tasks to be Performed

 

Note: Each item will have a final deliverable that must be approved by WDD Management

 

Item #1 - Work Process Flow Diagrams

 

Model the data by meeting with WDD staff and developing detailed Work Process Flow Diagrams for all processes that will be addressed by the WDD-DB. These diagrams will reflect both manual and electronic steps needed to support all WDD processes. Meetings with Rob Cline and Inder Osahan have already started under a preliminary contract will continue as soon as the new contract is approved.

 

Item #2 – Input Screens

 

Develop the input screens (or user interface) for the new system based on the Work Process Flow Diagrams produced as item #1 above. This will include available fields, buttons, drop down menus, and other data entry elements.

Item #3 – Forms

 

Modify existing paper forms to support the needs of the new system. Gather and convert standard documents into electronic forms that can easily integrate with data in the system to prevent manual data entry or multiple data entry. 

 

Item #4 - Reports

 

Develop specific reports based on WDD process and analysis needs. Examples include Permits issued by jurisdiction, date range, water company, parcel number, etc. This will cover any output from the system.

Item #5 - Technical Specification and Assist with Prototype

 

Develop a detailed technical specification using the output of the previous four items.  Assist the CTO in developing a prototype of the working system. The prototype will show the operation of the system and corresponding user interface but will not be a fully functional system. The technical specification and prototype will be the design documents to be used by the ultimate developer of the WDD-DB system.

 

Item #6 - Request for Qualification (RFQ) for Outside Vendor

 

Develop a Request for Qualification (RFQ) for an outside vendor to develop and test the WDD-DB system. This will incorporate all previous items and be submitted to vendors selected by the District.

Item #7 – Vendor Selection

 

Assist the CTO with selecting candidates, reviewing candidate responses and selecting the final vendor. Three (3) weeks are being allocated for candidate vendors to respond to the RFQ.

Terms and Conditions

 

Invoices will be issued on the 1st and 15th of each month during the engagement and are payable Net 15 from receipt of invoice.

 

Payments should be sent to:

 

PM Connect

801 Lighthouse Ave

Suite 201

Monterey, CA 93940

 

This proposal is valid for 60 days from receipt.

 

U:\staff\word\boardpacket\2004\2004boardpacket\20040129\ConsentCalendar\05\item5_exh5a.doc