The file's text, extracted by GovTribe without its formatting.
Appendix H: Data and Infrastructure
Data and Infrastructure Interfaces and Data Exchange Interfaces and Data Exchange includes the activities associated with design and development of constructs to transfer data real time, on demand, and daily bi-directional data from the State’s current internal and external systems to the proposed solution. The State is seeking a vendor with a mature API-based integration framework thereby limiting the number of custom integrations that will need to be developed. The State is contracting a specialist system integrator to support the design and development of the enterprise data integration hub (DIH) that the proposed OMS will be required to integrate with.
Refer to Appendix D: Interface Requirements for an outline of identified State OMS interfaces. The reference table is meant to provide additional detail with anticipated data exchange complexity and transaction volumes.
The following table identifies the general roles and responsibilities with respect to configuration, and testing of Interfaces and Data Exchange, where RACI (Responsible Accountable Consulted Informed) designation(s) are assigned to indicate the roles and responsibilities of each organization in performing and/or completing the activity or task:
Interfaces and Data Exchange Roles and Responsibilities
| Interfaces and Data Exchange Roles and Responsibilities |
| Successful Responder |
| State |
| Output/Outcome |
| 1. Create interface and data exchange specifications from the new system to State target systems and/or DIH for the interfaces and data exchanges listed in Appendix D. |
| R, A |
| R, C |
| Interface & Data Exchange specification document |
| 2. Approve interface and data exchange design specifications. |
| I |
| R, A |
| Documented approval |
| 3. Develop target interfaces and data exchanges according to approved specifications (API specification) |
| R, A |
| - |
| Interface & Data Exchange specification document |
| 4. Produce all necessary “transaction monitoring” capabilities to support the interfaces effort as detailed in the Interface & Data Exchange specification. |
| R, A |
| R, C |
| Documented successful test results |
| 5. Execute all tasks including the setup of the interfaces to State and external systems in compliance with the Interface & Data Exchange specification documents in an iterative process |
| R, A |
| - |
| Documented successful test results |
| 6. Execute the transformations and rules that were used to map the legacy and target environments to include data clean-up tasks in an iterative process |
| R, A |
| - |
| Documented successful test results |
| 7. Create and develop interface and data exchange test plan |
| R, A |
| - |
| Interface & Data Exchange test plan |
| 8. Review and approve interface and data exchange test plan |
| I |
| R, A |
| Documented feedback and approval |
| 9. Create and develop implementation test plan |
| R, A |
| - |
| Interface & Data Exchange test plan |
| 10. Review and approve implementation test plan |
| I |
| R, A |
| Documented feedback and approval |
| 11. Build, test, and validate environments |
| R, A |
| - |
| Documented successful test results |
| 12. Build, test, and validate “sand box” environments |
| R, A |
| - |
| Documented successful test results |
| 13. Test the interfaces, according to the interface and data exchange test plan, to ensure they comply with the interface and data exchange design specifications and data mapping after each iteration |
| R, A |
| - |
| Documented successful test results |
| 14. Test all previously completed system interfaces in accordance with the Interface and Data Exchange test plan after each iteration. Interfaces will comply with business and system technical requirements identified. |
| R, A |
| - |
| Documented successful test results |
| 15. Present reports and results, including capacity and load, after each iteration |
| R, A |
| I |
| Documentation as described |
| 16. Review and approve reports and test results |
| I |
| R, A |
| Testing results report |
| 17. Ensure and verify that the exchanged data is accurate and complete. |
| R, A |
| - |
| Testing results report |
| 18. Update and implement required data sharing agreements and MOUs with external agencies as per approved interface and data exchange design specifications. |
| I |
| R, A |
| Interface & Data Exchange specification document |
Infrastructure and Environment Infrastructure and Environment consists of technical hardware and software environment configurations and specifications (virtual or physical) necessary to operate the OMS solution. The following table identifies the general roles and responsibilities with respect to Infrastructure and Environment, where RACI (Responsible Accountable Consulted Informed) designation(s) are assigned to indicate the roles and responsibilities of each organization in performing and/or completing the activity or task:
| Infrastructure and Environment Roles and Responsibilities |
| Contractor |
| State |
| Output/Outcome |
| 1. Define software requirements for the OMS Infrastructure and Environment |
| R, A |
| - |
| Detailed infrastructure, environment, build and deployment plans and procedures |
| 2. Create, develop, and define the strategy for stand-up of the Infrastructure and Environment |
| R, A |
| - |
| Detailed infrastructure, environment, build and deployment plans and procedures |
| 3. Create, develop, and define the quality control procedures for the build of the OMS infrastructure and environment |
| R, A |
| R, C |
| Detailed infrastructure, environment, build and deployment plans and procedures |
| 4. Create, develop, and define the security measures for the build and deployment of the OMS infrastructure and environment as required by the State |
| R, A |
| R, C |
| Detailed infrastructure, environment, build and deployment plans and procedures |
| 5. Create, develop, and define the testing plans and procedures for the build and deployment stages of the OMS infrastructure and environment |
| R, A |
| C |
| Infrastructure, environment, build and deployment test and validation plan |
| 6. Create and develop the documentation as required for the build of the OMS infrastructure and environment |
| R, A |
| C |
| Detailed infrastructure, environment, build and deployment plans and procedures |
| 7. Report on the status of the infrastructure and environment build and deployment as required |
| R, A |
| I |
| Documented status report |
| 8. Work collaboratively in the creation and configuration of all infrastructure and environments |
| R, A |
| R, C |
| Workshop attendance and minutes |
| 9. Review and approve all plans and procedures |
| - |
| R, A |
| Documented feedback and approval |
| 10. Deploy the production infrastructure and environment |
| R, A |
| C |
| Documented successful test results |
| 11. Conduct quality assurance, security, functional, and technical testing, and correct all unsatisfactory test results |
| R, A |
| R, C |
| Documented successful test results |
| 12. Build, test, and validate infrastructure environments |
| R, A |
| C |
| Documented successful test results |
| 13. Build, test, and validate “sand box” infrastructure environments |
| R, A |
| C |
| Documented successful test results |
| 14. Review and approve test results |
| R, C |
| R, A |
| Documented feedback and approval |
| 15. Set disaster recovery expectations |
| I |
| R, A |
| Documented recovery recommendations |
| 16. Create, develop, and provide disaster recovery plan |
| R, A |
| C |
| Disaster recovery plan |
| 17. Approve disaster recovery plan |
| I |
| R, A |
| Document approval |
| 18. Set business continuity expectations |
| I |
| R, A |
| Documented business continuity expectations |
| 19. Create, develop, and provide business continuity plan |
| R, A |
| C |
| Business continuity plan |
| 20. Approve business continuity plan |
| I |
| R, A |
| Document approval |
| 21. Provide audit access and participate in scheduled or unscheduled audits |
| R, A |
| - |
| Monitoring and incident management plan and procedures |
| 22. Provide automated monitoring and incident notification functionality |
| R, A |
| - |
| Monitoring and incident management plan and procedures |
| 23. Provide automated monitoring and incident notification services |
| R, A |
| - |
| Monitoring and incident management plan and procedures |
| 24. Monitor and validate DOJ, CJIS, NIST, CLETS, security, etc. compliance |
| I |
| R, A |
| Monitoring and incident management plan and procedures |
Integration and User Acceptance Testing Integration and User Acceptance Testing includes the activities associated with a seamless implementation. The following table identifies the general roles and responsibilities with respect to Integration and User Acceptance Testing, where RACI (Responsible Accountable Consulted Informed) designation(s) are assigned to indicate the roles and responsibilities of each organization in performing and/or completing the activity or task:
| Integration and User Acceptance Testing Roles and Responsibilities |
| Contractor |
| State |
| Output/Outcome |
| 1. Create, develop, document, and maintain integration and testing plan that meets requirements and adheres to defined policies. |
| R, A |
| C |
| System Integration and User Acceptance test plan |
| 2. Provide proposed integration and testing plan |
| R, A |
| - |
| System Integration and User Acceptance test plan |
| 3. Review and approve integration and testing plan |
| I |
| R, A |
| Documented approval |
| 4. Create and develop interface test plan for pre-production SIT / UAT |
| R, A |
| C |
| System Integration and User Acceptance test plan |
| 5. Review and approve interface test plan |
| I |
| R, A |
| Documented approval |
| 6. Recommend integration and testing requirements |
| R, A |
| I |
| System Integration and User Acceptance test plan |
| 7. Build, test, and validate environments |
| R, A |
| - |
| Documented successful test results |
| 8. Build, test, and validate “sand box” environments |
| R, A |
| - |
| Documented successful test results |
| 9. Approve integration and testing requirements |
| I |
| R, A |
| Documented approval |
| 10. Manage integration test environment (SIT) |
| R, A |
Status reports
| 11. Manage issue tracking software solution for tracking defects, progress, and proposed resolutions |
| R, A |
| I |
| Risk/Issue Log |
| 12. Maintain software release matrices across development, quality assurance, and production environments and networks |
| R, A |
| I |
| Status reports |
| 13. Conduct integration and security testing for all systems (such as data, equipment, and networks), based on requirements defined in the plan and MN DOC / MNIT policies and procedures |
| R, A |
| R, C |
| Documented successful test results |
| 14. Evaluate all new and upgraded system components for compliance with MN DOC / MNIT security rules, regulations, and procedures |
| R, A |
| R, C |
| Documentation |
| 15. Assess and communicate the overall impact and potential risk to system components prior to implementing changes |
| R, A |
| C |
| System Integration and User Acceptance test plan |
| 16. Create and develop User Acceptance Testing ("UAT") requirements and scripts |
| C, I |
| R, A |
| System Integration and User Acceptance test plan |
| 17. Create and develop UAT plans and scripts per requirements |
| R, A |
| - |
| System Integration and User Acceptance test plan |
| 18. Review and approve UAT plans |
| I |
| R, A |
| Documented feedback & approval |
| 19. Conduct and document UAT results per requirements |
| I |
| R, A |
| Documented successful test results |
| 20. Support UAT testing |
| R, A |
| - |
| Status Reports, attendance, and minutes |
| 21. Review and approve UAT results |
| I |
| R, A |
| Documented feedback & approval |
| 22. Execute interface test plan |
| R, A |
| I |
| Documented test results (verification of execution) |
| 23. Share all test results with successful Responder |
| R, A |
| R, C |
| Status report |
| 24. Identify, remediate, and resolve any problems with the successful Responder’s product, OMS configuration, data conversion, or with the integration or interfacing of their product with those of other third-party Contractors and State. |
| R, A |
| C, I |
| Successful test results |
Data Conversion The selected Responder is expected to convert the DOC’s existing COMS and relevant data to the OMS Solution. A detailed data conversion plan will be required as part of the OMS implementation. The successful Responder will need to convert all records into the new OMS solution. The State must be able to validate successful conversion/migration of their existing OMS data to the new OMS Solution. The successful Responder will provide a final report of the data that successfully converted and the data that could not be converted with appropriate reasons for its failure to convert.
| Document Name | 1 |
| Appendix H | 1 |
image2.png