3.1.2.5 Technical Objective 5 (T-OBJ-5) Database Independence – Description Provide ability for COTS OMS application to be database independent. Rationale The agency wants to determine which database platform to utilize with the COTS OMS to comply with IT direction. Acceptance/Fit The selected solution will be able to function seamlessly with Criteria internal agency’s selected database platform. 3.1.2.6 Technical Objective 6 (T-OBJ-6) Rules Based Configuration – Description Provide the ability to configure jurisdiction-specific data that does not affect core system functionality. Rationale The agency envisions a system that is maintained internally, to allow for workflow and items to be modified quickly based on changing end-user needs. Acceptance/Fit Clearly outlined documentation and training allowing agency Criteria to assume the system configuration tasks upon implementation. 3.1.2.7 Technical Objective 7(T-OBJ-7) Create Reporting Environment – Description Replicate production data to separate environment for the purpose of disaster recovery, reporting, statistical analysis and business intelligence efforts. Rationale As the demand for reports and data analysis continue to increase, the new solution must provide and communicate with a separate environment to reduce the impact on the production system. Acceptance/Fit Separate production and reporting environments. Criteria 3.1.2.8 Technical Objective 8 (T-OBJ-8) Contractor Independence – Description Ensure that NMCD IT staff gains sufficient experience and knowledge to implement the COTS OMS application and to maintain after implementation independently. Rationale The agency wants to reduce or eliminate the reliance upon external contractors to maintain the OMS. Acceptance/Fit Internal staff qualified to maintain and update selected COTS Criteria OMS solution.
3.1.2.5 Technical Objective 5 (T-OBJ-5) – Database Independence Description Provide ability for COTS OMS application to be database independent. Rationale The agency wants to determine which database platform to utilize with the COTS OMS to comply with IT direction. Acceptance/Fit Criteria The selected solution will be able to function seamlessly with internal agency’s selected database platform. 3.1.2.6 Technical Objective 6 (T-OBJ-6) – Rules Based Configuration Description Provide the ability to configure jurisdiction-specific data that does not affect core system functionality. Rationale The agency envisions a system that is maintained internally, to allow for workflow and items to be modified quickly based on changing end-user needs. Acceptance/Fit Criteria Clearly outlined documentation and training allowing agency to assume the system configuration tasks upon implementation. 3.1.2.7 Technical Objective 7(T-OBJ-7) – Create Reporting Environment Description Replicate production data to separate environment for the purpose of disaster recovery, reporting, statistical analysis and business intelligence efforts. Rationale As the demand for reports and data analysis continue to increase, the new solution must provide and communicate with a separate environment to reduce the impact on the production system. Acceptance/Fit Criteria Separate production and reporting environments. 3.1.2.8 Technical Objective 8 (T-OBJ-8) – Contractor Independence Description Ensure that NMCD IT staff gains sufficient experience and knowledge to implement the COTS OMS application and to maintain after implementation independently. Rationale The agency wants to reduce or eliminate the reliance upon external contractors to maintain the OMS. Acceptance/Fit Criteria Internal staff qualified to maintain and update selected COTS OMS solution.
NMCD-OMS%20Project%20Management%20Plan%20Final-R.docx