RBDMS State Projects: Development Process

GWPC provides support to interested states throughout the RBDMS development and implementation process.  This includes talking with interested states, providing software demonstrations, conducting a project needs assessment and defining technical and IT support needs.  GWPC will then help to customize the selected RBDMS products on a cost-share basis to cover implementation and customization efforts. The RBDMS code base is freely available to governmental agencies that sign a software license agreement. 

Step 1: Initial Interest

An interested state reaches out to the GWPC Technical Director. GWPC staff will connect with state staff to discuss RBDMS product options and identify specific state needs.

GWPC Technical Director
Paul Jehn

Step 2: Needs Assessment

RBDMS TeamBecause each state has different statutes and regulations that drive systems requirements, new projects begin with a comprehensive needs assessment, fit gap analysis, and requirements gathering.  All RBDMS products are configurable and customizable, allowing states to add on additional features as needed based on budget, preferences, and programmatic needs. The needs assessment is used for development of future work plans and as a means to confirm with the state that GWPC has adequately modeled the state’s requirements.

Step 2.1: Team Identification

  • GWPC holds a project call to determine the state’s big picture needs/priorities and creates a Needs Assessment Team. This team includes a GWPC Project Coordinator who will be a resource to the state and actively involved in management of the project.
  • Needs Assessment Team develops an agenda for a 2-3 day onsite meeting with state agency staff.

Step 2.2: Onsite Meeting

  • The onsite meeting consists of a general kick-off meeting with senior state officials followed by meetings focused on the state’s priority issues. These are generally held with agency staff who have specific subject matter expertise (e.g. compliance/permitting staff, field inspectors, UIC staff).

Step 2.3: Documentation

  • The Needs Assessment Team composes a draft report and forwards to the state project lead for concurrence and modification.
  • The final needs assessment is approved and delivered to the state.

Step 3: Work Plan

Work plan(s) and software requirements are developed based on priority and budget and sent to the state project lead for approval.  Project requirements are compared to current RBDMS functionality and a gap analysis is performed.  Proposals for enhancements to current RBDMS functionality are brought to the Steering Committee for approval and the Technical Committee to ensure compliance with RBDMS standards.

Step 4: Development

Upon approval of the work plan and software requirements, GWPC and the state choose a contractor to complete necessary customizations.  This is usually done through an RFP.  All RBDMS code is shared in a central repository upon which customizations are built.  GWPC and state agency staff work closely with the contractor throughout the process to ensure the desired functionality is delivered.

Step 5: Implementation

Upon completion of the project, GPWC  will provide initial support.  Biannual training sessions teach state staff how to support and maintain their system.  Some helpdesk support is provided for minor ongoing issues.  Technical assistance from the software development contractor is often recommended through a maintenance and operations agreement between the state and GWPC, which should be considered during development of the work plan.