Job ID: MNSITE-2662 (90090331)
Remote Web Developer/Architect (12+) with requirements gathering, Web forms, role-based security, accessible, comments management and training experience
Location: St Paul MN (Office of Administrative Hearings)
Duration: 12 months
o Web-based interface
o User, password, role management
o Data and screen access controlled through role-based permissions
o Web-based forms for data input
o Reporting features to include ad hoc query
o Database/data storage
o Requirements confirmation/gathering/refinement as part of the projects
o Formal IT project management processes as part of the projects
• Developed one or more systems with the following features:
o Supports similar business processes
o Has configurable features (items/controls that can be modified by an administrative user without the need for additional development)
o Provides information via a data dashboard
o Uses secure coding practices to increase the security of the customized software
o Allows users to import files/data into the database as a means of minimizing data entry for the user.
Description of Project
The Minnesota Department of Information Technology Services (MNIT) partnering with the Office of Administrative Hearings is seeking a vendor partner to work on the design and development of an accessible, easily navigated, web-based portal to collect and publish information and public comments on proposed rules.
At a high level, the object of MNIT and OAH is to increase public participation and engagement in rulemaking for all Minnesotans and across all Minnesota communities. For additional details on the request such as additional background, qualifications, tasks, and evaluation criteria, see the attachments found in the Buyer Attachment section of the Event. This work will be completed in phases. Vendors are asked to respond with cost estimates for all phases, but the initial contract term will only include Phase 1.
The work is expected to be done remotely.
1. Requirements Confirmation Document
a. Requirements have largely been gathered and are represented in the system/functional requirements set forth in this Event.
b. Review the requirements and meet with the OAH to address any questions about the requirements.
c. Restate in a document the requirements in vendor’s own format to confirm a common understanding of the requirements.
1. System Architecture Diagram
a. Provide a document with the system technical architecture.
b. Include firewall port openings required, if relevant.
2. Software Design Document
a. Provide a document that describes the software design.
b. Include overall interface layout and menu system.
c. Include easy to understand descriptions of how the different roles would navigate through the system for typical task(s).
3. Implemented software system that supports the following business requirements
a. Public comment portal that meets business requirements for the collection of electronic public comments on proposed agency rules
i. Portal Homepage – The homepage is the main page of the public comment portal and serves as the table of contents. The homepage includes navigation to the rest of the site, links to content, calls to action, and resources.
ii. Public comment period creation – A web-based form for agency users to enter relevant data about a pending rulemaking comment period. Once the relevant data is entered, a comment period is created and public users can submit comments.
iii. Submission of public comments – A web-based form for public users to submit their comment. Users of the form will include individuals, groups, and organizations, who type their comment directly onto the form and/or attach a various types of files to their comment.
iv. Collection and display of public comments – Once public comments are submitted for a comment period, users can view, sort, and search for submitted comments.
v. Portal search – A search function that allows users to enter keywords and find content on the site. The search will also allow users to filter, sort, and categorize search results.
vi. User accounts and user functionality – Role-based user accounts that allow internal users to log into the public portal and gain access to resources within it.
vii. Portal Reporting and Analytics – Users can create, run, and view a variety of predefined and ad hoc reports.
b. Administrative Functionality
i. Manage user accounts and passwords and role assignment
ii. Manage configurable items
iii. Other Administrative items determined through requirements confirmation
c. A technical administrative guide in word or pdf format.
i. Installation/deployment guide
ii. Database model and data dictionary
d. Administrators manual/guide in word or pdf format.
e. A user guide in word or pdf format.
i. Internal OAH users
ii. External agency users
iii. External public users
f. User training – Train the trainer. OAH staff to receive training from the vendor and then OAH staff will train others as needed.