Rationale The current legacy system and the operating system needed to modify the application source code is past end-of-life and support. Acceptance/Fit 100% retirement of PowerBuilder CMIS, java-based OMP and any Criteria other ancillary systems. 3.1.2.2 Technical Objective 2(T-OBJ-2) Streamline Development Platform – Description Collapse development and maintenance overhead due to multiple, disparate systems. Rationale Streamline development resources currently working on multiple platforms and programming languages by utilizing one pre-defined development platform included in the COTS OMS. Acceptance/Fit Ability to have development staff address other Criteria business/programmatic needs due to the reduced development overhead with a COTS OMS. 3.1.2.3 Technical Objective 3 (T-OBJ-3) Mobility – Description Provide the technical components and platform to application mobility. Rationale Due to the need for officers to conduct offender reporting at the offender’s home or workplace, it is paramount to provide the ability for officers to document supervision contact details while in the field using mobile technology rather than having to enter data once they return to the office. Acceptance/Fit Robust solution that will easily integrate both with technology that Criteria the officers currently have, such as smart phones, as well as other devices, such as tablets, etc. 3.1.2.4 Technical Objective 4 (T-OBJ-4) Data Sharing – Description Provide the technical architecture to allow near real-time sharing of application data. Rationale The COTS OMS solution will have the ability to provide common web services to reduce the administrative overhead currently required to data. Acceptance/Fit Industry-standard services that conform to national standards such Criteria as NIEM and GRA and maintain CJIS compliance.
Rationale The current legacy system and the operating system needed to modify the application source code is past end-of-life and Acceptance/Fit Criteria 100% retirement of PowerBuilder CMIS, java-based OMP and any other ancillary systems. 3.1.2.2 Technical Objective 2(T-OBJ-2) – Streamline Development Platform Description Collapse development and maintenance overhead due to multiple, disparate systems. Rationale Streamline development resources currently working on multiple platforms and programming languages by utilizing one pre-defined development platform included in the COTS OMS. Acceptance/Fit Criteria Ability to have development staff address other business/programmatic needs due to the reduced development overhead with a COTS OMS. 3.1.2.3 Technical Objective 3 (T-OBJ-3) – Mobility Description Provide the technical components and platform to application mobility. Rationale Due to the need for officers to conduct offender reporting at the offender’s home or workplace, it is paramount to provide the ability for officers to document supervision contact details while in the field using mobile technology rather than having to enter data once they return to the office. Acceptance/Fit Criteria Robust solution that will easily integrate both with technology that the officers currently have, such as smart phones, as well as other devices, such as tablets, etc. 3.1.2.4 Technical Objective 4 (T-OBJ-4) – Data Sharing Description Provide the technical architecture to allow near real-time sharing of application data. Rationale The COTS OMS solution will have the ability to provide common web services to reduce the administrative overhead currently required to data. Acceptance/Fit Criteria Industry-standard services that conform to national standards such as NIEM and GRA and maintain CJIS compliance. support.
NMCD-OMS%20Project%20Management%20Plan%20Final-R.docx