statement of work solicitation · web viewthe survey intends to replace the current oracle and...

NOTICE

This opportunity is being released to DBITS Contractors pre-qualified as a result of Open Market RFP #0A1147** and MBE RFP #0A1139**.

ONLY Contractors pre-qualified in the Application Development and Maintenance Transition Planning Category are eligible to submit proposal responses AND to submit inquiries. The State does not intend to respond to inquiries or to accept proposals submitted by organizations not pre-qualified in this Technology Category.

An alphabetical listing of Contractors pre-qualified to participate in this opportunity follows:

Accenture Mapsys Systems & Solutions **CDO Technologies Inc.Advocate Consulting Group MAXIMUS Human Services, Inc. Cluster Software, Inc

Advocate Solutions LLC McGladrey LLPCompTech Computer Technologies, Inc.

Ardent Technologies MGT of America, Inc. Digitek Software, Inc.CapGemini America Navigator Management Partners LLC Diversified Systems, Inc.CapTech Ventures Peerless Technologies Evanhoe & Associates IncCardinal Solutions Group Persistent Systems Flairsoft, LtdCareworks Tech Planet Technologies Halcyon Solutions, Inc.CDI Corp Prelude System Logic Soft, Inc.Centric Consulting LLC Quantrum LLC Optimum Technology, inc.CGI Technologies and Solutions, Inc. Quick Solutions Proteam Solutions, Inc

CMA Consulting Services R. Dorsey & CompanySophisticated Systems, Inc.

Computer Aid, Inc. Sense Corp Srisys, Inc.

Crowe Horwath LLP Sondhi SolutionsStellar Innovations & Solutions Inc.

Data Transfer Solutions System Soft Technologies Strategic Systems, Inc.Data-Core Systems, Inc. Systems Technology Group, Inc. TMH SolutionsenfoTech TCC Software Solutions UNICON International Inc.Halcyon Team Ray Technologies, LLC Vana Solutions LLCHMB, Inc. TEK Systems Ventech Solutions, Inc.

IBM TeranomicVertex Computer Systems Inc.**

IIT Contacts The Greentree GroupInfojini Truven Health AnalyticsInformation Control Company Unicon International. Inc.JMT Technology Group VertexKunz, Leigh & Associates Windsor SolutionsLochbridge XLN Systems

O h i o D e p a r t m e n t o f N a t u r a l R e s o u r c e s , D i v i s i o n o f G e o l o g i c a l S u r v e y D B I T S S O W S o l i c i t a t i o n – D B D N R - 2 0 - 0 3 - 0 0 1 1

Statement of Work Solicitation

State of OhioOhio Department of Administrative

Services on behalf of the Ohio Department of Natural Resources, Division of

Geological SurveyOhio Water Well Log Database Migration

and Web Application Development

DBITS Solicitation ID No. Solicitation Release Date

DBDNR-20-03-001 February 19, 2020

Section 1: Purpose

The purpose of this Project Statement of Work (SOW) is to provide the Ohio Department of Natural Resources, Division of Geological Survey (Survey) with information technology services in the Application Development and Maintenance Transition Planning Category. A qualified Contractor, herein after referred to as the “Contractor”, must furnish the necessary personnel, equipment, material and/or services and otherwise do all things necessary for, or incidental, to the performance of work set forth in Section 3, Scope of Work. Table of Contents

Section 1: PurposeSection 2: Background InformationSection 3: Scope of WorkSection 4: Deliverables ManagementSection 5: SOW Response Submission RequirementsSection 6: SOW Evaluation CriteriaSection 7: SOW Solicitation ScheduleSection 8: Inquiry ProcessSection 9: Submission Instructions and Location

Supplements: Supplement 1 – Attachments A through ISupplement 2 – State IT Policy, Standard and Service RequirementsSupplement 3 – State Information Security and Privacy Requirements, State Data Handling Requirements

TimelineSOW Solicitation Release to Pre-Qualified Contractors: February 19, 2020Inquiry Period Begins: February 19, 2020Inquiry Period Ends: March 11, 2020 at 8:00 AMProposal Response Due Date: March 25, 2020 at 1:00 PM

All times Columbus Ohio local time

2 O h i o D e p a r t m e n t o f N a t u r a l R e s o u r c e s , D i v i s i o n o f G e o l o g i c a l S u r v e y D B I T S S O W S o l i c i t a t i o n – D B D N R - 2 0 - 0 3 - 0 0 1

Section 2: Background Information

2.1 Agency Information

Agency Name Ohio Department of Natural Resources, Division of Geological Survey

Contact Craig Nelson, Hydrogeologist (Project Manager); Paul Spahr, Geology Program Manager (Project Manager)

Contact E-Mail [email protected]; [email protected]

Bill to Address 2045 Morse Rd., Bldg. C-1, Columbus OH 43229

2.2 Project Information

Project Name Ohio Water Well Log Database Migration and Web Application Development

Project Background & Objective

The Survey is contracting the redesign, data migration and development of web applications for its Water Well Log database, which has become outdated and somewhat cumbersome to use since its most recent system upgrade in the late 1990s. The Survey intends to replace the current Oracle and Access/Oracle database with an Enterprise SQL Server ESRI Geodatabase. In addition to migrating the existing data to a new system, a new web application is needed to provide updated functionality for viewing, searching, entering, and processing the database’s records. The new systems (database and application) must provide all the functionality of the current system, as well as include additional features and processes that are not currently available, such reviewable records submission queues and Geographic Information Systems (GIS)-integrated data searches and records editing. The new system will include an InnovateOhio Platform (IOP)-compliant login/user schema with varying permission levels and in-app administration modules for Survey staff to administer data entry, data processing, and public records submissions.

Expected Project Duration

Estimated duration of this project is less than 270 days, or earlier based upon agreement with the parties. The Contractor may present a timeline based on their experience in this type of project and the expected deliverables defined by Survey.

The selected Contractor will be notified by the Survey when the project period will begin. The estimated start period for the project is early February 2020. The Survey expects that the Contractor will separately invoice the Survey for deliverables accepted in fiscal year 2020 (July 1, 2019-June 30, 2020), and, if necessary, fiscal year 2021 (July 1, 2020-June 30, 2021).

2.3 Proposed Project Schedule and Milestones

Estimated Date Task

April 20, 2020 Project Start

Within 10 days of Award

Kickoff meeting to discuss project task schedule and deliverables


Meetings to discuss project plan, schedule, and project requirements/validation

Within 50 days of Completion of detailed database redesigns, migration plans, and web applications requirements documents


mailto:[email protected]

mailto:[email protected]

Award


Completion of wireframes and software architecture diagrams


Delivery of redesigned database builds with data migration completed


Delivery of completed web applications

Within 210 days of Award Completion of systems testing

Within 240 days of Award Completion of user acceptance testing

Within 270 Days of Award

Production deployment

Finalization of documentation

For 120 days after production deployment

Technical support period

2.4 Contractor’s Work Effort Requirement

The Contractor is expected to perform most of the work using its own employees. The Contractor must submit a request, in writing, with ample notice, for approval prior to the use of any subcontractors. The Contractor is expected to supply, at minimum, 50% of the work for this project.

Section 3: Scope of Work

3.1 In Scope Requirements

The Ohio Water Well Log Database (WWLD)

[Note:] To avoid confusion with the project Contractor, “Driller” is used in place of “Contractor” for the WWLD description and mockups. For the final design, Drillers should be classified and labeled as “Contractors”

[Attachment Notation:] (see Attachments W[1], X[3a], Y[2-1a], Z) =See Supplement 1, Attachment W, section 1 AND Attachment X, label 3a AND Attachment Y, section 1, label 1a AND Attachment Z

a. Background Information

The Ohio Water Well Log Database (WWLD) consists of approximately 950,000 records in the form of water well records and well sealing reports. New records are added to the database on a daily basis, with some being filed in paper format and then scanned and others being filed electronically. Records are currently maintained in an Oracle database hosted on an Ohio Department of Administrative Services (DAS) server and administrated by the Ohio Department of Natural Resources, Office of Information Technology (ODNR-OIT). The main WWLD table, WELL_LOG, contains the records for both Well Logs and Sealing Reports, and is linked to 54 related and lookup tables (see Attachment A[1] for current data structure and list of tables). The entire database is approximately four (4) gigabytes (GB) in size. The Survey uses a desktop-based VB.NET application to perform basic database operations, including records modification, records searches, driller management actions, and data entry (for paper records). Survey staff may query, but not modify, the


database through a Microsoft Access Open Database Connectivity (ODBC) connection and make spatial edits via a GIS feature class linked to the Oracle database and synchronized on a recurring basis. ODNR-OIT oversees database administration, GIS/Oracle synchronization, and bulk data modification. The primary end users of the database are drillers and plumbers, who search and submit records; consultants, who search and export records for site assessments and reference purposes; and members of the public, who search for records typically associated with their properties or properties they plan to purchase. On average, approximately 5,000 users access WWLD records each month. Public access to records is via a web application hosted on the ODNR Division of Water Resources website, which includes separate pages for Well Log Filing and Well Log Searches (see: http://water.ohiodnr.gov/search-file-well-logs).

b. Project Objectives

The primary objectives of the project are to:1) Redesign the WWLD data structure;2) Migrate its data to a new DBMS;3) Develop a new web interface and application(s) for three (3) main modules:

- Water Well Search;- Water Well Records Filing; and - Water Well Administration.

4) Transfer the source code and database/application documentation to ODNR-OIT.

c. Required Tasks and Applications

1) Database Redesign

The Survey requires the following items and considerations for the WWLD redesign:

- The new database be built as an Enterprise SQL Server ESRI Geodatabase;- The creation of several new tables, the full list of which will be provided by the Survey (see Attachment A[2]);- The addition, removal, and renaming of fields for specific tables, the full list of which will be provided by the Survey

(see Attachment A[3]);- The creation of relational tables from fields currently existing in un-normalized tables (ex: Gravel Pack), the full list of

which will be provided by the Survey (see Attachment A[2]);- The removal of unused and/or legacy tables, the full list of which will be provided by the Survey (see Attachment

A[3]); and- The establishment of a 2nd page format for Well Log images that are filed electronically, containing the

basic/locational information from the 1st page, an area for multiple screens/gravel packs/grouts not present in current system, an area for Well Log Diagrams (described below), and an area for additional Drilling Log entries. Logs that do not have additional Drilling Log entries or additional screen/gravel pack/grouts will continue to be 1-page images unless the “Include well diagram on report?” checkbox is checked during records filing (see Attachments G[4a], I).

2) Data Migration

The Survey requires that the current WWLD be migrated in its entirety to the newly designed DBMS, with the following considerations:

- The conversion process must follow or consider the steps outlined in Attachment A[3] to preserve the desired data structure and data integrity;

- The migration must account for records submitted during the software development process (i.e. the full project duration); and

- The current database and data structure must be archived when the new system goes live.

3) Web ApplicationsThe Survey requires a new, mobile-friendly web interface and application(s) for three (3) modules:

- Water Well Search;- Water Well Records Filing; and - Water Well Administration.

The three (3) modules should include the features listed below:- All public-facing web pages shall be compliant with the accessibility standards established by the Web Content

Accessibility Guidelines (WCAG) 2.0, Level A and Level AA;


http://water.ohiodnr.gov/search-file-well-logs

- Follow the standards, guidance, and design principles described in the InnovateOhio Platform (IOP) section at the end of the Scope of Work;

- Utilize the .NET Framework and/or JavaScript;- Be contained in a unified web application to be hosted on the ODNR website;- Be accessible through a user-friendly frontpage containing access to the modules themselves, an IOP-compliant

user login interface, and relevant documentation/About sections (the text for which will be provided by the Survey);- Include an IOP-integrated user system that allows users of varying permission levels to log in and access user-level-

locked features (e.g. Driller-level user may submit records, ODNR Staff-level users may submit and edit records, as well as access some of the features in the administration module, Admin-level users may submit records, edit records, and have full access to the administration module) (see Attachments C[1], G[1], H[1]);

- Be designed such that users can easily switch between modules and between Classic and Interactive module versions described below (Attachments C[2], G[2]);

- As part of the IOP-compliant user system, provides a Dashboard page for users, permitting them to file Well Logs and Sealing Reports (either through the Classic or Interactive Records Filing modules), update their DRILLER table information, and view and edit their Submission Queue (described below);

- Allow the public full access to the Interactive Search through the application’s front page, without the requirement to log in; and

- Match the features outlined in the current system for Classic modules (see Attachments B, F) and the application mockups for Interactive modules (see Attachments C, G, H) but the design described in the State of Ohio enterprise digital Style Guide framework for user interface design (see http://ux.ohio.gov).

- The solution must follow either NIST standards for federated identity management, and be capable of consuming OpenId Connect protocol, or Security Access Markup Language (SAML) 2.0 identity assertions, or be capable of consuming HTTP header identity assertions and leveraging it for SSO (Single Sign‐On). HTTP header-based identity assertions integration patterns include, but are not limited to, Trust Association Interceptor and Lightweight Third-Party Authentication.

The Survey requires the following features and considerations (general and by module):

Water Well Search- Has Classic and Interactive Search options, with Classic search replicating the current search system and

Interactive Search including additional features and functionality (see below);- Contains in both Classic and Interactive Search all the features and elements present in the current system, plus

those described below; and- Provides user-friendly tooltips and documentation for every element of the module, the content for which will be

written by the Survey (e.g. “Well Locator Instructions: To locate an unlocated well, please 1) Select …”) (see Attachments C[3a], G[3d]).

Classic Search Module (see Attachment B):o Provides all the functionality of the current system, including a Customized Data Search, an Address

Search, and a County, Township, and Road search (see Attachments B[1b], B[1c], B[1d]) . The current Map-based Search and Area/Radius Area/Polygon Area Search functions will be passed to the Interactive Search described in the Interactive Search Module section;

o Allows users to search for a range of well log numbers or sealing report numbers as is possible in the current desktop system;

o Allows ODNR Staff- and Admin-level users to make edits to records returned as the results of searches; and

o Replicates as closely as possible the features of the current system (see https://apps.ohiodnr.gov/water/maptechs/wellogs/appNEW/).

Interactive Search Module (see Attachment C):Note: Panes specified below correspond to attached mockups. Final design may deviate from mockup design but should include the features listed below

o Search Pane – Quick Search allows users to search by County, then Township, then Roads (identical to “County

& Twp. Search” in Classic (see Attachment C[3]). Roads made available for selection from the County/Township combination will appear in a side-menu similar to that of the custom search criteria (see Attachment D);

Custom Search allows users to search by Well Log Number or submit custom criteria combinations by entering the criteria in their respective fields and adding them to an automatically populated query (see Attachments C[4], D); and


https://apps/

http://ux.ohio.gov/

The results of searches submitted through both Quick or Custom search automatically appear both in the Interactive Map Pane and the Results Pane (see Attachments C[5], C[6], C[7]).

o Interactive Map Pane – Provides users the ability to search and select wells using an interactive map, independently or in

conjunction with the Search Pane functions; Allows users to toggle various Survey/DNR GIS base map layers on or off (e.g. Aerial

Photography, Digital Elevation, etc.) (see Attachment C[5a]); Allows users to toggle various Survey/DNR GIS feature layers on or off (e.g. roads, drainage

basins, etc.) (see Attachment C[5d]); Allows users to select records by drawing shapes, including rectangles, circles, polygons, and

freehand, as well as buffer their selection shapes by user-defined distances and units (see Attachment C[5b]);

Allows users to draw non-selection shapes and make distance measurements between points or within polygons, which will be included in any exported map (see Attachment C[5b]) Users may also add labels with user-defined text;

Allows users to select a point on the Interactive Map and specify a custom radius to select records within that radius;

Allows users to search by coordinates specified in degrees/minutes/seconds or decimal degrees (see Attachment C[5c]);

Allows users to symbolize the wells based on preset fields (see Attachment C[5e]); Allows users to select a record within the Interactive Map Pane, opening a popup containing the

well’s basic information (fields to be designated by the Survey) and a link to its Well Log Image; and

Includes a specific symbology/labeling for wells that have an associated Sealing Report (ex. SEALED text) and the ability to access that record.

o Results Pane – Displays both Located (having populated LATITUDE and LONGITUDE fields) and Unlocated

Wells. Unlocated Wells will return records that match, for example, the County, Township, and Road specified in the Search Pane or selected in Interactive Map Pane but that do not have populated LATITUDE/LONGITUDE values (see Attachment C[6], C[7]);

Displays Unlocated Wells for shape selections made in the Interactive Map by querying the transportation layer (if active) for county, township, and street names;

Provides capability for sorting and/or filtering results based on multiple, specified criteria, as well as specifying the number of records that appear on each page. (Note: Mockup shows concatenated Address field; results should not be concatenated so users may sort by, for example, ST_NO independent of ST_NAME) (see Attachments C[6a], C[7a]);

For ODNR Staff- and Admin-level users, activates an Edit button on selected records that allows these users to make on-the-fly edits to records returned from a custom data search. Popup window from Edit click will match the Water Well Records Filing module, but show fields in a simplified form, without interactive features; and

Allows users to resize the Results Pane over the Interactive Map Pane so as to provide more viewable space (see Attachment C[6b]).

o Tools Pane – Provides functionality to further filter the results of a custom data search based on simple

statements (e.g. AQUIFER_TYPE = “Sand & Gravel” AND TOTAL_DEPTH >= 20) (see Attachment C[8]);

Allows users to export search results as a .pdf report, Excel/.csv file, or GIS shape file, with a 2,000 record limit (see Attachment C[10]); and

Well Locator feature allows users to select an Unlocated Well record from the Unlocated Wells results and click on a location in the Interactive Map to submit to the Survey for that record a LATITUDE/LONGITUDE for review. Users should be prompted for their Name (required), Email (required), Confidence in Location (required), Phone Number, and Comments on the located well, and their submission should go to a Locator Queue visible to ODNR Staff- and Administrator-level users in the Administration module (see Attachments C[9], E).

Water Well Records Filing- Has Classic and Interactive Records Filing options, with Classic Records Filing replicating the current, desktop-

based data entry system and Interactive Records Filing providing additional features and functionality (see


Interactive Records Filing section below);- In both Classic and Interactive Records Filing, contains all the features and elements present in the current web-

and desktop-based systems, plus those described below;- Includes a validation procedure when records are submitted, which checks for the completion of required fields and

performs additional field/value checks (ex: lowest drilling log formation is same depth as TOTAL_DEPTH), the full list of which to be supplied by the Survey/ODNR-OIT. Upon successful validation and submission, users should be prompted with options to submit another well log, submit a sealing report, or visit the Ohio Department of Health (ODH) website (https://www.odh.ohio.gov/en/odhprograms/eh/water/PWSForms/PWSCForms);

- Establishes a Submission Queue procedure that automatically sends submitted records to a user-linked queue that allows the author of the electronically submitted record to make after-submission edits/corrections during a 10-day period. During this period, the record appears in the database with a DRAFT flag that denotes it as non-final and watermarks the Well Log Image as “DRAFT”. User may then finalize record while it is in queue or, at the end of the 10-day period, the record is automatically submitted as a finalized record with the DRAFT flag and watermark removed. Upon submission of a record, a pop-up briefly explains the system and provides user the opportunity to print a DRAFT version of their record. Users may not immediately finalize their records after submission, effectively bypassing the Queue, but must at least log out and log back in to have the ability to finalize;

- Reminds users when they log in if they have records in the Submission Queue and how many days remain for edits to them;

- Extends the length of time that may pass before a user is automatically logged out of the system to four (4) hours;- Provides user-friendly tooltips and documentation for every aspect of the module, the content for which will be

written by the Survey (e.g. “The Total Depth field represents the depth of the completed well, in feet below land surface.”);

- Allows ODNR Staff- and Admin-level users to “Recreate Image”, a procedure that recreates the Well Log Image for a digitally submitted record that has been modified (this functionality exists for Well Logs but not Sealing Reports in the current desktop app);

- Permits users submitting a Sealing Report to view a list of Well Logs that match the COUNTY, TOWNSHIP, CASING_DIAMETER, and TOTAL_DEPTH (within 5 feet) of that Sealing Report. Users may then select a matching Well Log and import its relevant fields into the Sealing Report, as is possible with the current system using the Well Log number. Popup will prompt drillers to verify the Well Log is correct before the values are imported;

- Provides unique fields and layout for Sealing Report filing different from those of Well Log records. Differences and required fields will be supplied by the Survey. (e.g. WELL_USE field labeled as “Well Use” for Well Logs, to be labeled “Prior Well Use” for Sealing Reports);

- Allow users to generate a unique, sequential Sealing Report number within a range specified by the Survey for paper Sealing Reports that arrive in the unnumbered format;

- Converts fields specified by the Survey into drop-down menus populated by relevant values (e.g. CITY field will become a drop-down list populated by the cities associated with the recorded COUNTY and TOWNSHIP, if available);

- Automatically populates the DRILLER_ID field with the Driller ID associated with the user when a Driller-level user is performing the data entry; and

- Establishes a procedure for converting spatial data entered as degrees/minutes/seconds to the 6-decimal degrees standard used for the LATITUDE and LONGITUDE fields in the database. Once data entry occurs and the record is submitted, the conversion takes place and the LATITUDE and LONGITUDE are stored as 6-decimal degrees (see Attachment G[5a]).

Classic Records Filing Module (see Attachment F):o Provides all the functionality of the current system and matches as closely as possible its layout and designo Removes currently unused fields according to a list to be supplied by the Survey;o Allows access to a miniature version of the Interactive Map feature from the Interactive Records Filing

(described below);o Allows Drillers to add multiple Screens, Gravel Packs, and Grouts through a simple “Add Screen” button

that creates an additional row of screen/gravel pack/grout fields;o Allows the option to display well diagrams (described in the Well Diagram Pane of the Interactive Records

Filing Module); ando Allows users to modify individual fields for each formation added to the Drilling Log without having to

remove the entire formation and re-enter it.

Interactive Records Filing Module (see Attachment G):Note: Panes specified below correspond to attached mockups. Final design may deviate from mockup design but must include the features listed below:

o Interactive Map Pane –


https://www/

Provides users the ability to locate wells through an interactive map by clicking on a button and then a location, which will automatically populate the LATITUDE, LONGITUDE, COUNTY, and TOWNSHIP fields in the Well Information Pane. If users manually enter the LATITUDE and LONGITUDE in the Well Information Pane, the Interactive Map places a pin on the location (see Attachments G[3b], G[5a]). Users may also adjust the exact location by clicking and dragging the location pin;

Allows users to toggle various Survey/DNR GIS base map layers on or off (e.g. Aerial Photography, Digital Elevation, etc.) (see Attachment G[3a]);

Allows users to zoom to a location on the map based on coordinates entered in degrees/minutes/seconds or decimal degrees (see Attachment G[3c]); and

Allows users to toggle various Survey/DNR GIS feature layers on or off (e.g. roads, drainage basins, etc.) (see Attachment G[3d]).

o Well Diagram Pane – Automatically generates a Well Diagram based on the parameters of the Construction Details

(Well Information Pane) and Formations (Drilling Log Pane). Well Diagrams begin at the land surface and visualizes the depth of the formations noted in the drilling log, the borehole diameter and depth, casing diameter and depth, casing thickness, depth and diameter of screen(s), depth of gravel pack(s), and depth of grout(s). Formations will be labeled by formation name and symbolized by a system to be specified by the Survey (see Attachment G[4]); and

Provides the user the option of including the automatically generated well diagram or not on their report, toggleable via a check box (see Attachment G[4a]).

o Well Information Pane – Provides all of the fields and functionality of the current data entry system, with some alterations

noted on Attachments G[5b], G[5c], G[5d], G[5e]. Major alterations include the ability to add multiple Well Tests (in the new system a related table), multiple Screens, multiple Gravel Packs, and multiple Grouts. Users will be able to modify or remove Screens, Gravel Packs, and Grouts exactly like they are able to in the current system for the Borehole / Casing elements; and

Allows users to import the basic information (County, Township, Owner, Address, City, ZIP) from another record (see Attachment G[5f]).

o Drilling Log Pane – Allows users to modify individual fields for each formation added to Drilling Log without having to

remove the entire formation and re-enter it, as is the case in the current system (see Attachment G[6]).

o Submit Pane – Contains buttons to Submit the record, which initiates the previously described validations; save it

for later, which stores a pre-validation temporary file in the system that the user can re-open later to finish; or discard the record, which clears all fields and attachments (see Attachment G[7a]);

Activates an Attach/Replace Well Log Image button for ODNR Staff- and Admin-level users who are filing paper records (see Attachment G[7b]). Well log images will be automatically generated for drillers submitting their record electronically; and

Allows all users to attach associated reports, specifying their type from the ASSOCIATED_REPORT_TYPE table (see Attachment G[7c]).

Water Well Administration- Contains all the features and elements present in the current, desktop-based system, plus those described below;

and- Provides ODNR Staff-level users access to a reduced list of Administration features limited to: Records, Driller

Record Management, Associated Reports, Statistics, Queries, and Reports Editors, as well as the Records Search, Submission Queue, and Locator Queue Panes.

Administration Module (see Attachment H)Note: Panes specified correspond to attached mockups. Final design may deviate from mockup design but must include all of the listed features:

o Administration Pane – Allows administrators to toggle between “Records”, “Users”, “Driller Record Management”,

“Attached Images”, “Associated Reports”, “Database Options”, “Statistics”, “Queries”, and “Reports” in the Editor Pane (see Attachment H[3]); and


Toggling between the above items opens that item in the Editor Pane as well as the Search Pane, if applicable. (e.g.: clicking Driller Record Management switches the Records Search Pane from the default list of well records to the list of drillers and allows users to edit their search selections in the Editor Pane).

o Editor Pane – Permits administrators to make edits and changes to parameters in each of the categories listed

below Records –

o Allows ODNR Staff and Administrators to enter Well Log/Sealing Report numbers or select records from the Records Search and edit that record’s fields, including fields hidden from the Classic/Interactive Search results (e.g. EDITDATE field) (see Attachment H[4]).

Users – o Allows Administrators to add, delete, or modify the details of users (Note: User

login IDs and passwords will be managed by IOP). Driller Record Management –

o Provides ODNR Staff and Administrators access to the DRILLER table (and associated tables, e.g. DRILLER_TYPE) and allows modifications to all fields;

o Allows administrators to search driller by NAME, ID, COUNTY, etc. in the Records Search Pane;

o Allows Administrators to add or delete driller records (not users) from the database; and

o Allows Administrators to access and modify the WELL_LOG_ISSUED table. Attached Images –

o Provides a read-only view of the Well Log and Sealing Report Images directory hosted on ODNR network drive; and

o Allows users to sort by date of upload and produce counts of image submissions by date/period.

Associated Reports – o Provides access to the ASSOCIATED_REPORT and

ASSOCIATED_REPORT_TYPE tables; ando Allows Administrators to add, delete, or modify associated reports, including

add new report types. Statistics –

o Compiles a list of general statistics about the database, including the following (for both Well Logs and Sealing Reports):

# of records; # of records by county; # of records submitted today; # of records submitted in a user-specified date range; # of records submitted in the past year; # of drillers; # and % of records Located total; # and % of records Located by County; # and % of Well Logs with associated Sealing Reports; and Additional statistics to be specified by the Survey.

Queries – o Provides the ability to write and view the results of ad hoc queries.

Reports – o Provides the layout and options for generating custom database reports from

the results of queries or on database statistics.

o Records Search Pane – Provides basic search capabilities resembling the Classic Search custom data search (see

Attachment H[5a]); and Allows Administrators to select records from the search results and edit them directly (see

Attachment H[4], H[5]).

o Submission Queue Pane –

1 0 O h i o D e p a r t m e n t o f N a t u r a l R e s o u r c e s , D i v i s i o n o f G e o l o g i c a l S u r v e y D B I T S S O W S o l i c i t a t i o n – D B D N R - 2 0 - 0 3 - 0 0 1

Lists all records submitted to the Records Filing Submission Queue, including their Well Log/Sealing Report ID, Driller, County, Township, and Date Submitted details (see Attachment H[6]);

Gives Administrators the ability to select, view, edit, and delete records in the Submission Queue [See Attachments H[6a], H[6e]);

Allows Administrators to “accept” a record in the Submission Queue, in effect publishing it, removing its DRAFT tags, and deleting it from the queue (see Attachment H[6d]);

Allows Administrators to hold a record, keeping it in the queue indefinitely (until it is deleted by Driller or accepted/deleted by Administrator) (see Attachment H[6c]); and

Allows Administrators to message Drillers in reference to a record in their Submission Queue, which alerts that user the next time they log on that they have received a message from the administrator and provides access to the message in their Submission Queue. Messaged records are automatically put on hold, but the driller may submit them once they read the message (See Attachment H[6b]).

o Locator Queue Pane – Lists all location modifications submitted through the Well Locator tool in the Interactive Search

module, including their Well Log/Sealing Report ID, County, Township, Latitude, and Longitude, as well as the Contact Name, Email, Phone Number, Comments, and Date Submitted details of who submitted the location (see Attachment H[7]);

Gives Administrators the ability to select, edit, and delete location modification entries in the Locator Queue (see Attachments H[7a], H[7d]);

Allows Administrators to “accept” a location modification entry in the Locator Queue, in effect writing the proposed LATITUDE and LONGITUDE values for that record to the database (see Attachment H[7c]); and

Allows Administrators to contact through email the person who submitted a located record in reference to what they have submitted (see Attachment H[7b]).

4) Knowledge TransferUpon product launch, ODNR-OIT and the Survey require that the source code, development documentation, and administration of the product be transferred to ODNR-OIT for ongoing maintenance and support.

InnovateOhio Platform (IOP) Considerations

The solution must follow either NIST standards for federated identity management, and be capable of consuming OpenId Connect protocol, or Security Access Markup Language (SAML) 2.0 identity assertions, or be capable of consuming HTTP header identity assertions and leveraging it for SSO (Single Sign-On). HTTP header based identity assertions integration patterns include, but are not limited to, Trust Association Interceptor and Lightweight Third Party Authentication.”

The solution must follow either NIST standards for federated identity management, and be capable of consuming Security Access Markup Language (SAML) 2.0 identity assertions, or be capable of consuming HTTP header identity assertions and leveraging it for SSO (Single Sign-On). HTTP header based identity assertions integration patterns include, but are not limited to, Trust Association Interceptor and Lightweight Third Party Authentication.

The solution must be capable of delegating user registration, business entity registration and business user registration to the State’s Enterprise Identity Management (EIDM) system. If the solution has a local user repository, it must offer a published web services based API to allow State’s EIDM system to manage users in its local repository. The solution’s web services based API should include capability to add, modify, remove, suspend and restore users in its local repository.

The solution must support identity assurance levels 3 and 4 based on NIST 800-63-2 standards and be capable of supporting the emerging NIST 800-63-3 standard. The solution must be capable of specifying criteria in the solution that should trigger Identity Proofing and Two Factor Authentication (2FA), so that it can be configured in the State’s Enterprise Identity Management (EIDM) system. The solution should also be capable of consuming Identity Proofing and 2FA services that are offered by State as NIST 800-63 Levels 2 and 3 compliant services.

The solution’s user interfaces should follow State of Ohio enterprise digital Style Guide framework for user interface design. The Style Guide is published at http://ux.ohio.gov

The solution’s User Interface should be capable of integrating with State’s Portal platform based on IBM Digital Experience (DX) product stack.

The solution should have logging that can integrate with the State’s Security Information and Event Management (SIEM) framework, to support report generation and alerting of State Security personnel both directly and via the State’s SIEM framework.

The solution must provide support for a minimum of 256-bit TLS encryption for transport and must be configured to communicate using TLS/ SSL or other appropriate forms of encryption.

The solution must be configurable to transmit transactional data to the State’s Fraud Detection framework, and be

O h i o D e p a r t m e n t o f N a t u r a l R e s o u r c e s , D i v i s i o n o f G e o l o g i c a l S u r v e y D B I T S S O W S o l i c i t a t i o n – D B D N R - 2 0 - 0 3 - 0 0 1 1 1

configurable to accept input from it as part of its transaction workflow. The solution must follow NIST 800-53 control standards for secure access to data and systems.

Out of Scope

Purchase of any software.

3.2 Assumptions and Constraints

Assumptions The Contractor/Subcontractor has successfully completed Oracle and/or SQL Server database designs or migrations for either a State agency and/or a government agency and/or a company of similar size (~50 employees, $4 million annual budget);

The Contractor/Subcontractor has successfully developed web database applications for either a State agency and/or a government agency and/or a company of similar size (~50 employees, $4 million annual budget);

The Contractor/Subcontractor is familiar with and capable of implementing the standards, design principles, and protocols required to make the product fully IOP-compliant;

The Contractor/Subcontractor will work with the Survey and ODNR-OIT to install the developed databases and web applications at the ODNR-OIT’s preferred location;

All documentation of the database migrations and web applications development will be shared with the Survey and ODNR-OIT upon completion of the project;

The Contractor/Subcontractor will provide Application Development and Maintenance Transition Planning; and

The Contractor/Subcontractor will follow the Software Development Life Cycle (SDLC) and include deliverables such as: business requirement specifications, software architecture document, complete code, system test cases, deployment plan, communication plan, risk/issue list and plan, iteration plan, user manual, and closeout.

Constraints The Contractor may need to make small timeline adjustments, as necessary, to compensate for the Survey’s annual Staff Conference, and for cases in which Survey staff (including the Project Manager and/or Project Sponsor) attend out-of-state conferences, during which they will be unavailable. The Survey will provide the Contractor ample notice and work with the Contractor to adjust the schedule, should this be the case;

The Contractor’s travel, developmental software licensing, and other incidental expenses are the responsibility of the Contractor and will not be billed back to the Survey; and

All meetings, requests, responses, and general communication made by the Survey and ODNR-OIT will occur during regular business hours, Monday through Friday. Communication and requests made to the Survey or ODNR-OIT after these hours will be answered the following business day.

3.3 Deliverable Requirements

• Deliverables must be provided on the dates specified by the Survey. Any changes to the delivery date must have prior approval (in writing) by the Survey Project Manager or designee;

• All deliverables must be submitted in a format approved by the Survey’s Project Manager;• All deliverables must have acceptance criteria established and a time period for testing or acceptance;• If the deliverable cannot be provided within the scheduled time frame, the Contractor is required to contact the Survey Project

Manager in writing with a reason for the delay and the proposed revised schedule. The request for a revised schedule must include the impact on related tasks and the overall project;

• A request for a revised schedule must be reviewed and approved by the Survey Project Manager before placed in effect;• The Survey will complete a review of each submitted deliverable in a timely manner;• A kickoff meeting will be held at a location and time selected by the Survey where the Contractor and its staff will be

introduced to the Survey; and• All deliverables must be accepted and approved by the Survey Project Manager and/or Survey Project Sponsor.


3.4 Deliverables – Details for individual Deliverables will be provided to the Contractor after award

DeliverableEstimated Due

Date

Payment Eligible?Yes/No Description and Approval

1. Detailed Project Plan & Schedule

Within 30 days after award Yes

Provide detailed project plan/schedule to complete SOW

Approval from Survey Project Manager and/or Survey Project Sponsor

2. Weekly Status Reports First day of each week by 4:00 PM, starting second week after award

NoProvide weekly report of activities for the current week and plans for the next

3. Detailed Database Redesign and Data Migration Plan

Within 50 days after award

Yes

Provide detailed designs of restructured WWLD and OWN databases and proposed data migration plan


4. Detailed Web Applications Requirements Document


Yes

Provide a detailed requirements document for all modules and web applications to ensure all functionality has been included


5. Detailed Wireframes Within 70 days after award

Yes

Provide detailed mock ups/designs of screens for web applications


6. Software Architecture Diagram Within 70 days after award Yes

Provide a diagram of the architecture of the web applications


7. Built Elements via Bi-weekly Sprints

During bi-weekly sprint reviews, starting day 90

NoDemonstrate developed working code during bi-weekly sprint reviews

8. Redesigned Databases with Data Migration Completed


Yes

Provide test environment access to redesigned WWLD and OWN databases (with data migration completed)



9. Web Applications Within 180 days after award

Yes

Provide test environment builds of WWLD and OWN web applications and frontpages


10. Completion of System Testing Within 210 days after award

Yes

Provide documented results of system testing including bugs and resolutions


11. Completion of User Acceptance Testing


Yes

Provide documented results of UAT testing including bugs and resolutions


12. Deployment Plan Within 240 days after award

No Provide a detailed deployment plan

13. Production Deployment Within 270 days after award Yes

Lead and supervise technical deployment


14. One-hundred and twenty (120) Days of Technical Support after Production Deployment, Including at least Two Quarterly OWN Data Processing Cycle

120 days after Production

DeploymentYes 10%

Holdback

Provide all remaining and updated documentation


3.5 Roles and Responsibilities

Project or Management Activity / Responsibility Description Contractor Survey

Project Schedule and Deliverables X

Coordinating state contacts, stakeholders, and related support X

3.6 Restrictions on Data Location and Work

The Contractor must perform all Work specified in the SOW Solicitation and keep all State data and all work within the United States. The State may reject any SOW Response that proposes to do any work or make State data available outside the United States; and

The Contractor will comply with all state and federal laws regarding equal employment opportunity and fair labor and employment practices, including Ohio Revised Code Section 125.111 and all related Executive Orders.

3.7 Resource Requirements

Survey, ODNR-OIT, and DAS will provide limited access to the servers or testing environment necessary to conduct the work and as needed to complete the project; and


Having either a headquarters or an office in Ohio is a plus but is not a mandatory requirement of this solicitation.

Section 4: Deliverables Management

4.1 Submission/Format

PM Artifact/Project Work Product Submission Format

Project Plan tasks and Gantt chart Via email and within 10 business days of project start

Microsoft Project compatible format or printed copies

All project documents are to be delivered electronically

Via email and as required Microsoft Office compatible format

4.2 Reports and Meetings

The Contractor is required to provide the Survey Project Manager with weekly written progress reports of the project. Reports are due to the Survey Project Manager by 4:00 PM on the first business day of each week throughout the life of the project;

The progress reports shall cover all work performed and completed during the previous week and present the work to be performed during the current week;

The progress report shall identify any problems encountered or still outstanding with an explanation of the cause and resolution of the problem or how the problem will be resolved; and

The Contractor will be responsible for conducting weekly status meetings with the Survey Project Manager. The meetings will be held at a time and place so designated by the Survey Project Manager – unless revised by the Survey Project Manager. The meetings can be in person or online at the discretion of the Survey Project Manager.

4.3 Period of Performance

This project is expected to be completed within 270 days. Performance is based on the delivery and acceptance of each deliverable.

4.4 Performance Expectations

This section sets forth the performance specifications for the Service Level Agreements (SLA) to be established between the Contractor and State. Most individual service levels are linked to “Fee at Risk” due to the State to incent Contractor performance.

The Service Levels contained herein are Service Levels for this SOW Solicitation. Both the State and the Contractor recognize and agree that Service Levels and performance specifications may be added or adjusted by mutual agreement during the term of the Contract as business, organizational objectives and technological changes permit or require.

The Contractor agrees that 10% of the not to exceed fixed price for the SOW will be at risk (“Fee at Risk”). The Fee at Risk will be calculated as follows:

Total Not to Exceed Fixed Price (NTEFP) of the SOW x 10 % = Total Fee at Risk for the SOW

Furthermore, in order to apply the Fee at Risk, the following monthly calculation will be used:

Monthly Fee at Risk =Total Fee at Risk for the SOW

Term of the SOW in months

The Contractor will be assessed for each SLA failure and the “Performance Credit” shall not exceed the monthly Fee at Risk for that period. The Performance Credit is the amount due to the State for the failure of SLAs. For SLAs measured on a monthly basis, the


monthly fee at risk applies and is cumulative.

On a quarterly basis, there will be a “true-up” at which time the total amount of the Performance Credit will be calculated (the “Net Amount”), and such Net Amount may be off set against any fees owed by the State to the Contractor, unless the State requests a payment in the amount of the Performance Credit.

The Contractor will not be liable for any failed SLA caused by circumstances beyond its control, and that could not be avoided or mitigated through the exercise of prudence and ordinary care, provided that the Contractor promptly notifies the State in writing and takes all steps necessary to minimize the effect of such circumstances and resumes its performance of the Services in accordance with the SLAs as soon as reasonably possible.

To further clarify, the Performance Credits available to the State will not constitute the State’s exclusive remedy to resolving issues related to the Contractor’s performance. In addition, if the Contractor fails multiple service levels during a reporting period or demonstrates a pattern of failing a specific service level throughout the SOW, then the Contractor may be required, at the State’s discretion, to implement a State-approved corrective action plan to address the failed performance.

SLAs will commence when the SOW is initiated.

Monthly Service Level Report. On a monthly basis, the Contractor must provide a written report (the “Monthly Service Level Report”) to the State which includes the following information:

Identification and description of each failed SLA caused by circumstances beyond the Contractor’s control and that could not be avoided or mitigated through the exercise of prudence and ordinary care during the applicable month;

the Contractor’s quantitative performance for each SLA;

the amount of any monthly performance credit for each SLA;

the year-to-date total performance credit balance for each SLA and all the SLAs;

upon state request, a “Root-Cause Analysis” and corrective action plan with respect to any SLA where the Individual SLA was failed during the preceding month; and

trend or statistical analysis with respect to each SLA as requested by the State.

The Monthly Service Level Report will be due no later than the fifth (5th) day of the following month.

SLA Name Performance EvaluatedNon-Conformance Remedy

Frequency of Measurement

Delivery Date Service Level The Delivery Date Service Level will measure the percentage of SOW tasks, activities, deliverables, milestones and events assigned specific completion dates in the applicable SOW and/or SOW project plan that are achieved on time. The State and the Contractor will agree to a project plan at the commencement of the SOW and the Contractor will maintain the project plan as agreed to throughout the life of the SOW. The parties may agree to re-baseline the project plan throughout the life of the SOW. Due to the overlapping nature of tasks, activities, deliverables, milestones and events a measurement period of one (1) calendar month will be established to serve as the basis for the measurement window. The Contractor will count all tasks, activities, deliverables, milestones and events to be completed during the measurement

Fee at Risk Monthly


window and their corresponding delivery dates in the applicable SOW and/or SOW project plan. This service level will commence upon SOW initiation and will prevail until SOW completion.

Compliance with delivery date isexpected to be greater than 85%

This SLA is calculated as follows: “% Compliance with delivery dates” equals “(Total dates in period – Total dates missed)” divided by “Total dates in period”

Deliverable Acceptance Service Level

The Deliverable Acceptance Service Level will measure the State’s ability to accept Contractor deliverables based on submitted quality and in keeping with defined and approved content and criteria for Contractor deliverables in accordance with the terms of the Contract and the applicable SOW. The Contractor must provide deliverables to the State in keeping with agreed levels of completeness, content quality, content topic coverage and otherwise achieve the agreed purpose of the deliverable between the State and the Contractor in accordance with the Contract and the applicable SOW. Upon mutual agreement, the service level will be calculated / measured in the period due, not in the period submitted. Consideration will be given to deliverables submitted that span multiple measurement periods. The measurement period is one (1) month. The first measurement period will commence on the first day of the first full calendar month of the Contract, and successive monthly measurement periods will run continuously thereafter until the expiration of the applicable SOW.

Compliance with deliverable acceptance is

expected to be greater than 85%

This SLA is calculated as follows: “% Deliverable Acceptance” equals “# Deliverables accepted during period” divided by “# Deliverables submitted for review/acceptance by the State during the period”

Fee at Risk Monthly


4.5 General Contract Terms and Conditions

All Contract Terms and Conditions follow from the original solicitation which selected the pre-qualified Contractors. A copy of the original solicitation (RFP 0A1147** and RFP 0A1139**) can be found on the details page of this solicitation on the State of Ohio Procurement website. **Contractors pre-qualified by both Contracts must declare which Contract Terms and Conditions are being used.**

4.6 State Staffing Plan

Staff/Stakeholder Name Project Role Percent Allocated

Michael Angle (Division Chief) Project Sponsor As needed

Paul Spahr (Geology Program Manager) Project Manager As needed

Craig Nelson (Hydrogeologist) Project Manager 25% or as needed

OIT Project Manager Project Manager 25% or as needed

Joe Wells (GIMS Database Administrator) Project Manager As needed

James Raab (Geology Program Supervisor) Subject Matter Expert As needed

Section 5: Response Format and Content Requirements

An identifiable tab sheet must precede each section of a Proposal, and each Proposal must follow the format outlined below. All pages, except pre-printed technical inserts, must be sequentially numbered.

Each Proposal must contain the following:

1. Cover Letter;2. Contractor Experience Requirements;3. Subcontractors Documentation (if applicable);4. Assumptions;5. Payment Address;6. Staffing plan, personnel resumes, time commitment, organizational chart;7. Project Plan;8. Project Schedule (WBS using MS Project or compatible);9. Communication Plan;10. Fee Structure including Estimated Work Effort for each Task/Deliverable;11. Acceptance of Supplement 2 – State IT Policy, Standard and Service Requirements;12. Acceptance of Supplement 3 – State Information Security and Privacy Requirements, State Data Handling Requirements;

and13. Rate Card.

Include the following:1. Cover Letter:

a. Must be in the form of a standard business letter;

b. Must be signed by an individual authorized to legally bind the Contractor;

c. Must include a statement regarding the Contractor’s legal structure (e.g. an Ohio corporation), Federal tax identification number, and principal place of business; please list any Ohio locations or branches;

d. Must include a list of the people who prepared the Proposal, including their titles; and

e. Must include the name, address, e-mail, phone number, and fax number of a contact person who has the authority to answer


questions regarding the Proposal.

2. Contractor’s Experience Requirements:a. Each proposal must include a brief executive summary of the services the Contractor proposes to provide and one (1)

representative sample of previously completed projects as it relates to this proposal (e.g. detailed requirements documents, analysis);

b. Each proposal must describe the Contractor’s (and Subcontractor’s, if applicable) experience, capability, and capacity to provide Application Development, Integration and Maintenance Transition Planning. Provide specific detailed information demonstrating experience similar in nature to the type of work described in this SOW for each of the resources identified in Section 5.2; and

c. The Contractor/Subcontractor must demonstrate the following:

The Contractor/Subcontractor must have successfully completed a database design and data migration for agencies or organizations of a similar profile:The Contractor/Subcontractor must have successfully developed data-driven web applications for agencies or organizations of a similar profile;The Contractor/Subcontractor must have experience in GIS applications and spatial data integration;The Contractor/Subcontractor must have experience in Oracle and/or SQL Server database development or administration; andThe Contractor/Subcontractor must have experience in InnovateOhio Platform (IOP) integration.

Contractors must demonstrate that they meet these requirements by including a list of at least three (3) references from current or past customers served in the past 60 months for whom the Contractor performed similar work. The list must contain current contact persons and contact information for those work engagements. Contractors not meeting this requirement to the satisfaction of the Survey may be disqualified,

The proposal must contain a brief summary of each of those work engagements, how they are similar in size, scope, and purpose, to the project described in this SOW solicitation document, and the level of success attained. Additional database redesigns, data migrations, and web application development projects from periods prior to the 60 months are also invited.

3. Subcontractor Documentation (if applicable):

For each proposed subcontractor, the Contractor must attach a letter from the subcontractor, signed by someone authorized to legally bind the subcontractor, with the following included in the letter:

a. The subcontractor’s legal status, federal tax identification number, D-U-N-S number if applicable, and principal place of business address;

b. The name, phone number, fax number, email address, and mailing address of a person who is authorized to legally bind the subcontractor to contractual obligations;

c. A description of the work the subcontractor will do and one (1) representative sample of previously completed projects as it relates to this SOW (e.g. detailed requirements document, analysis, statement of work);

d. Must describe the subcontractor’s experience, capability, and capacity to provide Information Technology Assessment, Planning. Provide specific detailed information demonstrating experience similar in nature to the type of work described in this SOW from each of the resources identified in Section 5.2;

e. A commitment to do the work if the Contractor is selected; and

f. A statement that the subcontractor has read and understood the RFP and will comply with the requirements of the RFP.

4. Assumptions:


The Contractor must list all assumptions the Contractor made in preparing the Proposal. If any assumption is

unacceptable to the State, the State may at its sole discretion request that the Contractor remove the assumption or

choose to reject the Proposal. No assumptions may be included regarding the outcomes of negotiation, terms and

conditions, or requirements. Assumptions should be provided as part of the Contractor response as a stand-alone

response section that is inclusive of all assumptions with reference(s) to the section(s) of the RFP that the assumption is

applicable to. The Contractor should not include assumptions elsewhere in their response.

5. Payment Address:

The Contractor must provide the address to which the State should send payments under the Contract.

6. Staffing Plan, Personnel Resumes, Time Commitment, Organizational Chart:

Identify Contractor and subcontractor staff and time commitments. Identify hourly rates for personnel, as applicable.

Include Contractor and subcontractor resumes for each resource identified, and an organizational chart for entire team.

Project Team Qualifications:

Provide an outline of the project team and a brief description of their approach to the project. At a minimum the proposal must contain:

a. Proposed Project Manager and team members resume/qualifications demonstrating that the team has the necessary professional experience and background;

b. Three (3) references where the proposed Project Manager has managed a similar project. This must outline how the previous work involved facilitating the development of design requirements, coordinating data migration and/or web application development teams, and overseeing internal and user acceptance testing;

c. Team member(s) with program knowledge specific to each aspect of the project, including: database redesigns, data migrations, web application development, Oracle, SQL Server, GIS, .NET framework and/or Java; and

d. Team member(s) with experience analyzing and developing applications for processes that compile, integrate, and publish data.

Team Member Name Role Contractor or Subcontractor? No. Hours Hourly Rate

7. Project Plan:

Identify and describe the plan to produce effective documents and complete the deliverable requirements. Describe the primary tasks, how long each task will take, and when each task will be completed in order to meet the final deadline.

8. Project Schedule (WBS Using MS Project or Compatible):

Describe the Project Schedule including planning, planned vs. actuals for monitoring performance, including milestones, and time for writing, editing, and revising. Using MS Project or compatible software, create a deliverable-oriented grouping of project elements that organizes and defines the total work scope of the project, with each descending level representing an increasingly detailed definition of the project work.

9. Communication Plan:


Strong listening skills, the ability to ask appropriate questions, and follow-up questions will be required to capture the information necessary to complete the deliverable requirements. Describe the methods to be used to gather and store various types of information and to disseminate the information, updates, and corrections to previously distributed material. Identify to whom the information will flow and what methods will be used for the distribution. Include format, content, level of detail, and conventions to be used. Provide methods for accessing information between scheduled communications.

10. Fee Structure including Estimated Work Effort for each Task/Deliverable:

The State will holdback 10% of each deliverable. This holdback will be released at the end of the successful 120-day technical support period after deployment, as defined by the Survey.

Payment will be scheduled upon approval and acceptance of each applicable Deliverable by the Survey Project Sponsor and Survey Project Manager within the usual payment terms of the State.

Deliverable Name Total Estimated Work Effort (Hours)

Not-to-Exceed Fixed Price for Deliverable

Detailed Project Plan & Schedule $

Weekly Status Reports N/A

Detailed Database Redesign and Data Migration Plan $

Detailed Web Applications Requirements Document $

Detailed Wireframes $

Software Architecture Diagram $

Built Elements via Bi-weekly Sprints N/A

Redesigned Databases with Data Migrations Completed $

Web Applications $

Completion of System Testing $

Completion of User Acceptance Testing $

Detailed Deployment Plan N/A

Production Deployment $

One hundred and twenty (120) Days of Technical Support after N/A


Production Deployment, Including at least One Quarterly OWN Data Processing Cycle

(10% holdback)

Total Not-To-Exceed Fixed Price for all Deliverables $

11. Acceptance of Supplement 2 – State IT Policy, Standard and Service Requirements

The Contractor must include a fully completed Supplement 2 as part of their proposal. The Contractor must follow the completion instructions contained in the supplement when preparing their response.

12. Acceptance of Supplement 3 – State Information Security and Privacy Requirements, State Data Handling Requirements

The Contractor must include a fully completed Supplement 3 as part of their proposal. The Contractor must follow the completion instructions contained in the supplement when preparing their response.

13. Rate Card

The primary purpose of obtaining a Rate Card is to establish baseline hourly rates in the event that change orders are necessary. The DBITS contract is not intended to be used for hourly based time and materials work. (NOTE – Section 5.6 collects rate information for named resources) Contractors must submit a Rate Card that includes hourly rates for all services the Contractor offers, including but not limited to those listed in Section 5. Enter the Rate Card information in this section.

Resource Title Hourly Rate

$

$

Section 6: SOW Evaluation Criteria

Mandatory Requirement:

Mandatory Weight Does Not Meet

Partially Meets

Meets Exceeds

The Contractor/Subcontractor must have completed a database migration on at least three (3) projects within the past sixty (60) months. N/A REJECT ACCEPT

Scored Requirements:

Requirement Weight Does Not Meet

Partially Meets

Meets Exceeds

Contractor/Subcontractor must demonstrate experience performing both database migrations and database design.

7 0 2 4 6

Contractor/Subcontractor must demonstrate experience developing data- 7 0 2 4 6


driven web applications.

Contractor/Subcontractor must demonstrate experience in GIS applications and spatial data integration.

7 0 2 4 6

Contractor/Subcontractor must demonstrate experience in SQL Server database development or administration.

7 0 2 4 6

Contractor/Subcontractor must demonstrate experience in InnovateOhio Platform (IOP) integration.

7 0 2 4 6

The proposed Staffing Plan must detail the knowledge, skills and subject matter expertise to address staffing requirements (Staffing Plan, Personnel Resumes, Time Commitment, Organizational Chart).

5 0 2 4 6

The proposed Project Plan must detail all aspects of Section 3: Scope of Work.

7 0 2 4 6

The proposed Project Plan must detail project scope, approach, and consideration of timeline to address requirements of Section 5: Project Plan: 8. Project Schedule.

3 0 2 4 6

Price Performance Formula. The evaluation team will rate the Proposals that meet the Mandatory Requirements based on the following criteria and respective weights.

Criteria PercentageTechnical Proposal 70%

Cost Summary 30%

To ensure the scoring ratio is maintained, the State will use the following formulas to adjust the points awarded to each offeror.

The offeror with the highest point total for the Technical Proposal will receive 700 points. The remaining offerors will receive a

percentage of the maximum points available based upon the following formula:

Technical Proposal Points = (Offeror’s Technical Proposal Points/Highest Number of Technical Proposal Points Obtained) x 700

The offeror with the lowest proposed total cost for evaluation purposes will receive 300 points. The remaining offerors will receive a

percentage of the maximum cost points available based upon the following formula:

Cost Summary Points = (Lowest Total Cost for Evaluation Purposes/Offeror’s Total Cost for Evaluation Purposes) x 300

Total Points Score: The total points score is calculated using the following formula:

Total Points = Technical Proposal Points + Cost Summary Points

The State may reject any Proposal if the Contractor takes exception to the terms and conditions of the Contract.

Waiver of Defects

The State has the right to waive any defects in any quotation or in the submission process followed by a Contractor. But the State will only do so if it believes that is in the State's interest and will not cause any material unfairness to other Contractors.

Rejection of Submissions


The State may reject any submissions that is not in the required format, does not address all the requirements of this SOW Solicitation, or that the State believes is excessive in price or otherwise not in its interest to consider or to accept. The State will reject any responses from companies not pre-qualified in the Technology Category associated with this SOW Solicitation. In addition, the State may cancel this SOW Solicitation, reject all the submissions, and seek to do the work through a new SOW Solicitation or other means.

Section 7: SOW Solicitation Calendar of Events

Firm Dates

SOW Solicitation Released to pre-qualified Contractors February 19, 2020

Inquiry Period Begins February 19, 2020

Inquiry Period Ends March 11, 2020 at 8:00 AM

Proposal Response Due Date March 25, 2020 at 1:00 PM

All times Columbus Ohio local time

Anticipated Dates

Estimated Date for Selection of Awarded Contractor April 8, 2020

Estimated Commencement Date of Work April 20, 2020

Section 8: Inquiry Process

Contractors may make inquiries regarding this SOW Solicitation anytime during the inquiry period listed in the Calendar of Events. To make an inquiry, Contractors must use the following process:

Access the State’s Procurement Website at http://procure.ohio.gov/;

From the Navigation Bar on the right, select “Bid Opportunities Search”;

Enter the DBITS Solicitation ID number found on the first page of this SOW Solicitation in the “Document/Bid Number:” box;

Click the “Search” button;

Click on the Document/Bid Number to go to the document information page,

On the document information page, click the “Submit Inquiry” button;

On the document inquiry page, complete the required “Personal Information” section by providing:

o First and last name of the Contractor’s representative who is responsible for the inquiry,

o Name of the Contractor,

o Representative’s business phone number, and

o Representative’s email address;

Type the inquiry in the space provided including:

o A reference to the relevant part of this SOW Solicitation,

o The heading for the provision under question, and

o The page number of the SOW Solicitation where the provision can be found; and

Click the “Submit” button.


A Contractor submitting an inquiry will receive an acknowledgement that the State has received the inquiry as well as an email acknowledging receipt. The Contractor will not receive a personalized response to the question nor notification when the State has answered the question.

Contractors may view inquiries and responses on the State’s Procurement Website by using the same instructions described above and by clicking the “View Q & A” button on the document information page.

The State usually responds to all inquiries within three (3) business days of receipt, excluding weekends and State holidays. But the State will not respond to any inquiries received after 8:00 a.m. on the inquiry end date.

The State does not consider questions asked during the inquiry period through the inquiry process as exceptions to the terms and conditions of this Solicitation.

Section 9: Submission Instructions & Location

Each Contractor must submit THREE (3) complete, sealed and signed copies of its Proposal Response and each submission must be clearly marked “Ohio Water Well Log Database Migration and Web Application Development” on the outside of its package along with Contractor’s name. Pricing should be submitted under separate cover from the technical proposal.

A single electronic copy of the complete Proposal Response must also be submitted with the printed Proposal Responses. Electronic submissions should be on a CD, DVD.

Each proposal must be organized in the same format as described in Section 5. Any material deviation from the format outlined in Section 5 may result in a rejection of the non-conforming proposal. Each proposal must contain an identifiable tab sheet preceding each section of the proposal. Proposal Response should be good for a minimum of 60 days.

The State will not be liable for any costs incurred by any Contractor in responding to this SOW Solicitation, even if the State does not award a contract through this process. The State may decide not to award a contract at the State’s discretion. The State may reject late submissions regardless of the cause for the delay. The State may also reject any submissions that it believes is not in its interest to accept and may decide not to do business with any of the Contractors responding to this SOW Solicitation.

Proposal Responses MUST be submitted to the Survey’s Procurement Representative:Mike AngleOhio Department of Natural Resources, Division of Geological Survey2045 Morse Rd., Bldg. C-1Columbus, OH, 43229

Proprietary information

All Proposal Responses and other material submitted will become the property of the State and may be returned only at the State's option. If an Offeror includes in its Proposal confidential, proprietary, or trade secret information, it must also submit a complete redacted version of its Technical Proposal in accordance with Confidential, Proprietary or Trade Secret Information that follows. Offerors shall only redact (black out) language that is exempt from disclosure pursuant to Ohio Public Records Act. Offerors must also submit an itemized list of each redaction with the corresponding statutory exemption from disclosure. The redacted version must be submitted as an electronic copy in a searchable PDF format. The redacted version, as submitted, will be available for inspection and released in response to public records requests. If a redacted version is not submitted, the original submission of the Proposal will be provided in response to public records requests. Additionally, all Proposal Response submissions will be open to the public after the contract has been awarded.


statement of work solicitation · web viewthe survey intends to replace the current oracle and...

Documents