Job description
Name CIMOR Critical Support DMH--CIMOR- Agency, State Department of Mental Health (DMH), MO Location Jefferson City, MO Contract Duration // – // Release Date // SOW Provide maintenance and support for the Customer Information Management Outcomes and Reporting (CIMOR) application and related interfaces.
Includes enhancements to CIMOR and small applications integrated with it, issue resolution for critical and major problems, coding, peer reviews, unit testing, documentation, and reporting in Azure DevOps.
Contractors will be required to complete annual Department of Mental Health (DMH) required online training and attest to understanding and will comply with DMH's requirements.
All services must be provided in the United States.
Offshore services shall not be used to perform the services outlined herein.
Vendor resource(s) may be exchanged under the SOW without modifications of the SOW upon agreement of the SOW Vendor and the State.
The State reserves the right to review resumes and accept/reject proposed resource(s).
Security & Confidentiality – All materials (including code, tools, documentation and data) provided pursuant to the SOW shall be deemed confidential.
Vendor resource(s) must comply with agency and ITSD security policies, agency and ITSD required trainings, and/or required security specifications that describe: (i) required security capabilities, (ii) required design and development processes, (iii) required test and evaluation procedures, and (iv) required documentation.
The SOW Vendor resource(s) must report to the ITSD Project or Resource Manager or designee, who will provide resource(s) with sufficient knowledge to perform the work.
Vendor resource(s) are expected to conduct themselves in a professional manner and dress in a professional manner.
Submittal Requirement Vendor must submit: completed SOW Word doc with vendor sections filled, signed signature section, Deliverable Payment Milestones table, Contracting Resource(s) Price Calculations table, separate PDF response including project overview, experience, resources, methodology, Exhibits A-D, and resumes.
≤ pages (excluding resumes), pt font+, no embedded files, links, or videos Evaluation Criteria
Total points + bonus points :
∙ Cost – pts
∙ Technical Proposal – pts:
– Approach & Methodology – pts
– Personnel Qualifications & Biographies – pts
– Company History & Experience – pts
Bonus: MBE/WBE – pts, Blind/Sheltered Workshop – pts, MO SDVBE – pts References One () past performance case study required in
Exhibit C, with client name, contact person, phone, email, and project details Resumes required?
Yes — for all proposed resource(s) (Exhibit B) Rate card required No — firm-fixed pricing per deliverable; vendor to provide Contracting Resource(s) Price Calculations” table for internal breakdown Any specific requirement ∙ All services must be performed within the United States (no offshore)
∙ Vendor resources must complete DMH required online training
∙ Resumes subject to State review and approval
∙ No out-of-state travel required
∙ Security and confidentiality per ITSD policy Hardcopy/Email/portal submission Email Link Via Email
Attachment -
Scope, Requirements, Deliverables and Invoicing General Requirements Contractors will be required to complete annual Department of Mental Health (DMH) required online training and attest to understanding and will comply with DMH's requirements.
All services must be provided in the United States.
Offshore services shall not be used to perform the services outlined herein.
Vendor resource(s) may be exchanged under the SOW without modifications of the SOW upon agreement of the SOW Vendor and the State.
The State reserves the right to review resumes and accept/reject proposed resource(s).
Security & Confidentiality – All materials (including code, tools, documentation and data) provided pursuant to the SOW shall be deemed confidential.
Vendor resource(s) must comply with agency and ITSD security policies, agency and ITSD required trainings, and/or required security specifications that describe: (i) required security capabilities, (ii) required design and development processes, (iii) required test and evaluation procedures, and (iv) required documentation.
The SOW Vendor resource(s) must report to the ITSD Project or Resource Manager or designee, who will provide resource(s) with sufficient knowledge to perform the work.
Vendor resource(s) are expected to conduct themselves in a professional manner and dress in a professional manner.
The SOW Vendor must provide resumes for all of the SOW Vendor's resource(s) being assigned to the project for the review and acceptance by the State.
The SOW Vendor's resource(s) assigned to the project are subject to the approval or rejection by the State.
If there would be a need to replace the resource(s) by the SOW Vendor, any subsequent proposed resource(s) may be interviewed by the State prior to acceptance.
The Vendor's resource(s) schedule and location for on-site or off-site work must be agreed upon by the SOW Vendor's Project Manager, ITSD Project/Resource Manager and the Customer Product Owner.
If the vendor resource(s) is to work on-site, the hours are Monday – Friday, – central time, excluding state holidays.
No out-of-state travel is required on the part of the State or the SOW Vendor resource(s) for completion of this project.
Vendor Minimum Experience Requirements The SOW Vendor must meet or exceed the following minimum experience requirements at the time of the SOW response submission and for the duration of the SOW: Leadership Team: + years' experience maintaining a customer information management in a Mental Healthcare setting.
Vendor Resource(s) Experience Requirements The SOW Vendor shall include the following team members/resource(s) to administer and perform the contract requirements: Working Team: + years' experience maintaining a customer information management in a Mental Healthcare setting.
+ years' experience with Visual Studio + years' development experience with C, CSS, HTML, Bootstrap, jQuery and SQL Server as backend.
+ years' combined development experience within Visual Studio Team Services (VSTS) and Azure Dev Ops (ADO) + years' development experience with .net Framework where of those total years are utilizing + years' experience in fine tuning and enhancing the performance of SQL jobs.
Experience with State of Missouri CIMOR system preferred.
Performance Requirements The ITSD DMH Project Manager in coordination with ITSD DMH management will authorize all issue/problem work to be performed.
Assignments are made to the consultant by the Project Manager using Azure DevOps (ADO).
The vendor resource(s) is required to maintain updates in ADO daily indicating the status, hours used, and hours remaining within day of the error being corrected and implemented in production.
Each deliverable/problem report assigned under this SOW will require a description of the problem, the resolution to the problem, and the time/cost associated to resolving the issue.
The vendor resource(s) will report to the ITSD DMH Project Manager and will provide contract staff with sufficient knowledge and skill to resolve CIMOR production problems that are classified as either Critical” or Major” using the definitions below.
Every work order will be prioritized by the CIMOR Project Manager.
Critical Problems: Software errors that require an immediate resolution because they render an application inoperable, prevent all useful work from being done, disable major functions of the application, significantly impact functions of the business, have no workaround, and/or impact the health or welfare of one or more clients.
Work will commence within minutes of assignment and must be resolved within hours No non-critical work will be addressed by the assignee until the critical issue is resolved.
Major problems: software errors that require prompt resolution, significantly impact major areas of the application, have a workaround available, impact the client's eligibility or ability to receive benefits, or result from data integrity problems.
Work will commence within hours of assignment At a minimum, % of major problems assigned must be resolved within five () business days.
Of those that exceed the five () business day turnaround, a minimum of % must be resolved within ten () business days.
All remaining new major problem reports must be resolved within twenty () business days.
If there is a determination that an open issue/problem requires more work to be performed in the timeline as defined for Critical and/or Major issues in this SOW, then an estimate time for completion will be provided to the ITSD DMH and CIMOR Project Manager.
The ITSD DMH Client Services Manager may authorize the work be completed or the original issue/problem ticket to be closed and the issue/problem will be addressed outside of this SOW.
The vendor resource(s) must abide by ITSD-DMH development workflow which includes problem analysis, coding, peer review, unit testing and documentation.
Templates for the issue/problem documentation is required in this SOW and will be provided by state staff.
The vendor resource(s) will be working alongside existing development and QA staff and must coordinate their coding activity.
The DEV and TEST environment is shared by - developers plus - quality specialists.
ADO information for all tasks, user stories, or bugs should be updated as required in other documentation.
Deliverables LIST OF DELIVERABLES (Requirements and Criteria that must be met) DELIVERABLE APPROVAL ACCEPTANCE (Describe approval acceptance conditions that must be met) Monthly report listing of ADO work Items (User Story, Task, or Bug) by developer, work item ID and resolution with hours worked for each item during the reporting month.
Project Deliverable Acceptance Form approved by the ITSD Application Development Manager.
Reporting Requirements The ITSD Project Deliverable Acceptance Form (PDAF) must be used for deliverable acceptance.
Items may require a deliverable review meeting wherein the SOW Vendor walks through the deliverable with the ITSD and agency staff, followed by revisions as required, and finally, with a request for approval and associated payment per the SOW.
Technical Environment Requirements State owned Microsoft ADO shall be used to record, track and resolve issues, bugs and defects.
The SOW Vendor must have all necessary licenses and laptop/equipment to provide IT services in conjunction with the award of this SOW.
SOW Vendor shall purchase/supply and maintain the latest version of the required licenses (per developer) for all development tools for the duration of the project, unless specifically indicated by the SOW.
The required software licenses are: Visual Studio C CSS HTL Bootstrap jQuery SQL Server Azure Dev Ops (ADO) .net Framework State's Obligations The State, ITSD, will establish an Active Directory or Alt account for each contractor and VDI-RDP (or other) to access resources as necessary.
The State, ITSD, will provide a VPN connection as necessary.
The State, ITSD, will provide a physical location for contractor as necessary.
The State will make every effort to have the appropriate State staff available to the Vendor personnel on a timely basis.
The State will make every effort to make necessary project and system documentation available on a timely basis.
The State will perform timely review and approval of deliverables.
State Data State Data Location: All data associated with the solution/service shall only be hosted and stored within the United States.
Ownership: The State's electronic data or information submitted by the state or its authorized users with authorized access to the solution/service shall be considered State Data” for ownership purposes of the contract, as the State serves as either the owner or curator of the data submitted in the solution/service.
State Data” shall include: (a) the State's data collected, used, processed, stored, or generated as the result of the Services; (b) personally identifiable information ( PII”) collected, used, processed, stored, or generated as the result of the services, including, without limitation, any information that identifies an individual, such as an individual's social security number or other government-issued identification number, date of birth, address, telephone number, biometric data, mother's maiden name, email address, credit card information, or an individual's name in combination with any other of the elements listed herein; and (c) protected health information ( PHI”) as that term is defined under the Privacy Rule, Code of Federal Regulations (CFR) § State data is and shall remain the sole and exclusive property of the State and all right, title, and interest in the same is reserved by the State.
State Data” stored in the software and services being provided as a result of the contract shall also be known and treated by the SOW Vendor as confidential information in accordance with the contract, applicable SOW Vendor's documentation, and applicable law.
SOW Vendor Use of State Data: The SOW Vendor shall: (a) keep and maintain state data in strict confidence, using such degree of care as is appropriate and consistent with its obligations as further described in the contract and applicable law to avoid unauthorized access, use, disclosure, or loss; (b) use and disclose state data solely and exclusively for the purpose of providing the services, such use and disclosure being in accordance with the contract, any applicable Statement of Work, and applicable law; (c) not use, sell, rent, transfer, distribute, or otherwise disclose or make available state data for SOW Vendor's own purposes or for the benefit of anyone other than the State without the State's prior written consent; and, (d) not provide state data to any third party without the express written permission of the state.
the purpose of providing the services” as referenced above includes the right of the SOW Vendor to use state data to prevent or address service or technical problems, and verify service improvements, in accordance with the contract and the solution's documentation, or in accordance with the State's instructions.
Incremental Extraction of State Data: The SOW Vendor shall provide the State with the ability to conduct an incremental extraction of the State's data ( new and changed data) from the solution on a nightly basis to update the data available in the State Data Warehouse.
The incremental extraction of state data must be available without additional charges, conditions, or contingencies regarding the state's right to extract the data beyond the terms outlined in the SOW Vendor's cloud services agreement, and in the format mutually agreed to by the parties.
The incremental data extractions will allow the State to maintain an updated copy of the State's data for the duration of the contract.
End of Contract Extraction of State Data: At the end of the contract, the State shall have the right to extract its data from the solution for an additional sixty () calendar days from the date of contract expiration.
The end of contract extraction of state data must be at no additional cost, conditions, or contingencies regarding the state's right to extract the data notwithstanding the terms outlined in the SOW Vendor's services agreement, and in the format that was mutually agreed to by the parties.
If a term greater than calendar days is required by the State to complete the state data extraction, the SOW Vendor agrees to work with the State to define the additional term and fees for the additional time.
Extraction of State Data Process Validation: The SOW Vendor must allow the State to perform routine validation of the extraction of the State's data.
The routine validation occurs to ensure the State's data will accurately transfer as prescribed to the State's designated extraction location and accommodates the volume of data transferred.
The SOW Vendor shall assist the State by providing documentation and tools to allow the state to accurately process the extractions of the State's data for the State's continued use.
Backup and Recovery of State Data: Unless otherwise described in the contract, as a part of the services, the SOW Vendor shall maintain a backup of state data and perform an orderly and timely recovery of such data in the event that the production services may be interrupted in accordance with the disaster recovery and business continuity plans.
Return of State-owned Data: The SOW Vendor shall return state-owned data to the State of Missouri in a format mutually agreed to by the State and SOW Vendor and with a key or crosswalk to the information, where applicable, at no additional cost to the State.
The State shall have the right to test the data extract provided by the SOW Vendor at a frequency determined by the State.
Invoicing and Payment Requirements Statement of Work Invoicing: The SOW Vendor shall follow the outlined PDAF process listed in attachments for deliverable acceptance, then upon deliverable approval, will submit their invoice to the ITSD Project or Resource Manager and Administrative Assistant.
All travel-related expenses must be included within the firm, fixed deliverable price.
Payment Holdback Firm, fixed priced per deliverable to fulfill the SOW project, which shall include a % holdback per deliverable for any project for which the total firm, fixed price for all deliverables is $, or greater.
Unless otherwise authorized by the Division of Purchasing, projects with a total firm, fixed price of $, or greater for all deliverables shall have ten percent (%) holdback of each deliverable held back by the agency, which shall be paid to the SOW Vendor upon final acceptance by the state agency of the entire SOW project completion and receipt by the state agency of an accurate invoice for the final deliverable.
The SOW Vendor shall understand and agree that the payment holdback provisions described herein shall not be construed as a penalty.
The SOW Vendor shall understand and agree forfeiture of Payment Holdback shall result when: The SOW Vendor fails to fulfill the mandatory requirements of the SOW resulting in a deliverable being considered non-compliant with the SOW requirements and the SOW Vendor fails to correct and resolve the issue within ten () business days or other timeframe as agreed to in writing by the State; or The SOW Vendor fails to provide the state agency with an accurate invoice for all successfully completed and accepted deliverables for the SOW project within forty-five () days after State acceptance of the deliverables.
The SOW Vendor shall understand and agree return of Payment Holdback shall result: If the SOW project is canceled by the State due to reasons not attributable to the fault of the SOW Vendor prior to completion of the project, all payment holdback amounts retained by the State for completed and accepted SOW deliverables for that particular SOW project shall be paid to the SOW Vendor; or If the SOW project is completed and accepted by the State and the SOW Vendor has invoiced for the project in accordance with the provisions and requirements of the contract.
Required Skill Profession
Computer Occupations
