Production Environment Setup. Contractor is responsible for establishing the production environment. After testing has been completed, the SOMA Platform will be migrated to the production environment. During the setup the County will being final acceptance testing of the SOMA Dispatch, SOMA Mobile and SOMA Hub systems. The acceptance criteria is split by application and will be fully developed during Discovery. The acceptance test process shall include three phases: the acceptance testing period, the reliability test period and the final acceptance per the County’s requirements. The level of system reliability is inversely related to the error levels described below. ● Total System Failure (S1) ─ Critical system errors, which are defined as, Loss of Data, Corruption of Data, or Loss of Productive Use of the System. In the event this type of error occurs, the County will immediately notify Contractor and the thirty (30) day Reliability period will be cancelled. Contractor personnel shall promptly resolve the problem at no additional cost and a new thirty
Production Environment Setup. Contractor is responsible for establishing the production environment. After testing has been completed, the SOMA Jail will be migrated to the production environment. During the setup the County will begin final acceptance testing of the Jail Management System. The acceptance criteria is split by application and will be fully developed during Discovery. The acceptance test process shall include three phases: the acceptance testing period, the reliability test period and the final acceptance per the County's requirements. The level of system reliability is inversely related to the error levels described below. ● Total System Failure (S1) ─ Critical system errors, which are defined as, Loss of Data, Corruption of Data, or Loss of Productive Use of the System. In the event this type of error occurs, the County will immediately notify Contractor and the thirty (30) day Reliability period will be cancelled. Contractor personnel shall promptly resolve the problem at no additional cost and a new thirty (30) day Reliability Period will begin. Once the system operates for 30 consecutive days without an Error Level 1, the thirty (30) day Reliability test will be completed. ● Critical Failure (S2) ─ Critical errors exist when the primary purpose of the JMS software is compromised, and productive use of the system is significantly impacted. A procedural workaround is either not immediately or readily available or has been proposed and has been found to be unacceptable by the County. In the event this type of error occurs, the County will immediately notify the suspended. The Contractor’s personnel shall promptly resolve the problem at no additional cost to the County, and the thirty (30) day Reliability period will re-commence at the point where it was suspended. ● Non-Critical Failure (S3) ─ Non-critical errors which are defined as incomplete operation of system where a procedural workaround is readily and immediately available, and productive use of the system is not significantly impacted on software or operations. In the event this type of error occurs, the County will immediately notify the Contractor, but the thirty (30) day Reliability period will continue. Contractor shall resolve the problem during the thirty (30) day Reliability period. ● Inconvenience (S4) ─ Cosmetic errors which are defined as configuration issues that can be corrected by the County, data integrity issues that must be addressed by the County, Help File documentation errors, or enhancements...
