Functional Requirements. Intake Req # Requirement Text Included, Configurable , not Included Estimated Hours to Customize ATIMS Capabilities AD-01 The solution shall support the intake and booking process in compliance with the OCSD policies and procedures. I = Included ATIMS has a state of the art JMS system that is installed in several California counties. Our intake and booking modules meets the policy and procedures of these agencies. We believe that the ATIMS JMS would also meet the policy and procedure of OCSD but without reviewing them we cannot guarantee this. AD-02 The solution shall provide the capability for authorized users to enter basic information such as the date and time of arrival, agency, name of officer, name(s) of inmates and basic medical information. The system must also provide the capability to ingest information that is sent through an electronic data exchange upon approval from an authorized user. I = Included ATIMS provides all of these functions as part of the base system. If an interface is used to import Prebooking data a cost may be incurred. AD-03 The solution shall enable users to assign a system-generated temporary (pre-booking) number to each inmate. I = Included This is a standard function of the ATIMS Prebooking module. AD-04 The solution shall enable authorized users to send the information identified in AD-02 and AD-03 to the CHS medical system using an automated interface. I = Included ATIMS has an internal interface engine that can accomplish this function. All included interfaces have been quoted in the cost proposal. AD-05 The solution shall trigger a notification to be sent to OCSD-designated staff if an inmate requires immediate medical or mental health attention. C = Configurable This is a standard configuration of the ATIMS event engine and can be configured. AD-06 The solution shall support an interface with the CHS medical system to receive information after Triage activities have been conducted on the inmate and the inmate is ready to be booked. (Interface details are provided in the technical requirements.) C = Configurable This is a standard function of the ATIMS Interface engine. All included interfaces have been quoted in the cost proposal. AD-07 The solution shall populate the booking officers queue with the name(s) of the inmates that have cleared the Triage process and are ready to be booked. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-08 The solution shall enable users to update the facility and location count after the inmate has received a booking number in the system. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-09 The solution shall enable users to create a new booking number for an inmate and the tie it to the OCN number (inmate number). I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-10 The solution shall enable users to enter information from multiple sources/documents such as the Statement of Booking Officer (SOBO), Pre-booking, PCD etc. As mentioned earlier, it is expected that this information will come in through an automated interface that will obtain data real-time and insert it into the inmate record. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-11 The solution shall enable users to search for an inmate record based on multiple criteria such as, but not limited to: name, alias, SSN, and date of birth. N = Not Included 80 ATIMS has all functions available in the base system with the exception of SSN. ATIMS will add this function as an enhancement. AD-12 The solution shall enable users to add a booking number for each incarceration event. These booking numbers must be linked to the OCN number. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-13 The solution shall consolidate inmate information into the original OCN#. A history of corrections must also be maintained. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-14 The solution shall provide users with the ability to search an inmate's prior incarceration information and alerts. The system must prompt users to carry over prior alerts to the new record. It should also provide users with the ability to NOT carry over an alert (such as a medical alert that is no longer relevant) if so desired by OCSD. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-15 The solution shall provide users with the ability to capture custody booking status including, but not limited to: a. Pre-trial b. Sentenced c. Detainer I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-16 The solution shall provide users with the ability to do a partial or full copy of inmate information from a previous booking. The solution shall maintain all previous booking information (e.g. photos, tattoos, classification, release, etc.) I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-17 The solution shall enable users to record inmate information including, but not limited to: a. Name (Last, Middle, MI, Suffix) b. Name Type (Legal, Committed, Alias, Nickname)
Appears in 1 contract
Functional Requirements. Intake Inmate Records Req # Requirement Text Included, Configurable Configurable, not Included (I,C,N) Estimated Hours to Customize ATIMS Capabilities AD-01 IR-01 The solution shall support the intake and booking process documentation of inmate information in compliance with the OCSD policies and procedures. I = Included ATIMS has a state of the art JMS system that is installed in several California counties. Our intake and booking modules records module meets the policy and procedures of these agencies. We believe that the ATIMS JMS would also meet the policy and procedure of OCSD but without reviewing them we cannot guarantee this. AD-02 IR-02 The solution shall enable a user to view a queue of inmates that have cleared the medical triage process. I = Included This is a standard function of the intake and booking modules IR-03 The solution shall provide the capability to support the use of biometric techniques such as fingerprint readers to identify inmates that may have been previously incarcerated at OCSD.B5 I = Included This is a standard function of the intake and booking modules IR-04 The solution shall enable a user to search the database using multiple search parameters to determine if an inmate has been previously incarcerated at OCSD. I = Included This is a standard function of the intake and booking modules IR-05 The solution shall enable the user to attach the information collected during initial entry and the medical triage, as well as other information such as, but not limited to: alerts and demographic information from the most recent booking to create a new booking record. This record must be tied to the inmate's OCN number. The system will also store the Pre Book number that was created during the Initial Entry process at Intake. In addition, the solution must also provide alerts for authorized active booking numbers such as CWP, EMP, SEC, etc. I = Included This is a standard function of the intake and booking modules IR-06 The solution shall support the capability to electronically ingest any additional information that may be received from other data sources to complete the newly created booking record. I = Included This is a standard function of the intake and booking modules IR-07 The solution shall enable the records users to enter basic identify when the records process is completed so workflow may continue to the next process. I = Included This is accomplished as part of the booking wizard process. IR-08 The solution shall provide users with the capability to update the facility and location count once a booking record has been created. This will signify that the inmate is now in OCSD custody. I = Included This is a standard function of the intake and booking modules IR-09 The solution shall provide users with the ability to automatically query an arrestee for wants/warrants as well as other criminal history information such as once the date and time of arrival, agency, name of officer, name(s) of inmates and basic medical informationbooking number has been created. The system must also check local AWSS, OC Probation, CLETS, and NCIC. N = Not Included 640 ATIMS can assume middle ▇▇▇▇ solution similar to that discussed in CL-11 to retrieve the information from. ATIMS will query the system listed and will return the information in the ATIMS JMS for display. IR-10 The solution shall interface with the live scan device to send the required information to the device once the booking process is completed. C = Configurable This is a standard function of the intake and booking modules IR-11 The solution shall enable a user to add or modify inmate information such as, but not limited to: Name, Date of Birth, Booking Status, Arrest time and date, Alias, Medical Status, Court Jurisdiction, Warrant/ Detainer Information Place of birth, citizenship, SSN, phone number, SMT, Address, Next of Kin, Arraignment dates, next court dates, etc. This should be done prior to the assignment of the booking number. Specific fields cannot be changed once a booking number is assigned N = Not Included 16 ATIMS believes the intent of this requirement is to lock down the edit of data by some personnel after the booking is set complete and not necessarily the creation of a booking number. Our current infrastructure does not support based on creation of the booking number. However we can modify the existing solution to meet this requirement off of booking complete. The solution would require the use of an edit mode and a new permission right to allow the edit of information after booking complete. Hence certain users can update only during the booking process, while other users, who have the permission right can modify before and after. IR-12 The solution shall provide the capability to ingest information that document the various requests and documents received from other agencies via teletype, fax or other mechanisms. This includes, but is sent through an electronic data exchange upon approval from an authorized user. I = Included ATIMS provides all not limited to: Probation Holds, Parole Holds, Out of these functions as part of the base system. If an interface is used to import Prebooking data a cost may be incurred. AD-03 The solution shall enable users to assign a systemCounty Warrants, Fugitive Warrants, US Marshal Warrants, Orange County Warrants, Revocation Hearings, Flash Incarcerations, Pick-generated temporary (pre-booking) number to each inmateup/Release Notifications, WIS Warrant Notifications, Fugitive Warrants, Immigration Holds, Court Paperwork. I = Included This is a standard function of the ATIMS Prebooking module. AD-04 Records Module IR-13 The solution shall enable authorized users provide the capability to send scan any faxes, teletypes or other paper documents that come in and attach/link to booking number. I = Included This is a standard function of the ATIMS Records Module IR-14 The solution shall provide the capability to electronically ingest any information identified in AD-02 and AD-03 to the CHS medical system using that may be sent through an automated electronic interface. I = Included This is a standard function of the ATIMS has an internal interface engine that can accomplish this function. All included interfaces have been quoted in the cost proposal. AD-05 Records Module IR-15 The solution shall trigger have the capability to send notifications to appropriate staff based on the documents received by the Detail Desk. I = Included This is a standard function of the ATIMS Records Module IR-16 The solution shall enable the Detail Desk to document the proposed pick-up time for inmates after coordination with the specific agency. This action should generate a notification to all appropriate departments requesting preparation of any required documents and information. C = Configurable This is a standard function and configuration of the ATIMS Request module IR-17 The solution shall provide users with the capability to document information received from the court. This information can be received in a paper format or an electronic format. This will include, but not be limited to court orders, sentences, remands, go-backs, and court releases. I = Included This is a standard function of the ATIMS Records Module IR-18 The solution shall automatically calculate an inmate's release date, including multiple release dates, concurrent and consecutive sentences, and the incorporation of good time/work time. The system must also provide the ability to override the calculation and enter a manual date with the reason for the override. I = Included This is a standard function of the ATIMS Records Module IR-19 The solution shall provide the capability for users to enter new court documents. Any notifications that result from these should be sent to OCSDthe appropriate personnel based on OCSD pre-designated staff if an inmate requires immediate medical or mental health attentiondefined business rules. C = Configurable This is a standard configuration of the ATIMS event engine request and can be configurednotification engine. AD-06 ATIMS has allotted 7 days of configuration for this item. IR-20 The solution shall support an interface with provide the CHS medical system ability for the records staff to receive information after Triage activities have been conducted on the inmate and the inmate is ready to be booked. (Interface details are provided in the technical requirements.) C = Configurable This is create a standard function of the ATIMS Interface engine. All included interfaces have been quoted in the cost proposal. AD-07 The solution shall populate the booking officers queue with the name(s) of the new supplemental case or a hold for those inmates that have cleared the Triage process and are ready to be bookedcourt releases. I = Included This is a standard function of the ATIMS Intake and Booking ModuleRecords Module IR-21 The solution shall provide the ability for the records staff to add a hold expiration date. AD-08 The system must automatically bring up a alert for the records staff one day prior to the hold expiration date I = Included This is a standard function of the ATIMS Records Module IR-22 The solution shall provide users with the capability to move an inmate to a pre-release status after the hold expiration date expires. I = Included This is a standard function of the ATIMS Records Module IR-23 The solution shall provide the capability for the records staff to move inmates to a pre-release status. This action should automatically generate notifications that are routed to the appropriate departments. I = Included This is a standard function of the ATIMS Records Module IR-24 The solution shall enable users to update view and/or print the facility list of inmates being housed for other agencies (for example, California Department of Corrections and location count after Rehabilitation, US Marshals Service, US Immigration Customs Enforcement). I = Included This is a standard function of the inmate has received ATIMS Records Module IR-25 The solution shall provide the capability to interface with the courts and other criminal justice entities to send and receive electronic information to include, but not limited to information such as paperless jackets/court orders/court paperwork, etc. I = Included This is a booking number in standard function of the ATIMS Records Module IR-26 The solution shall support the capability to print OCSD Forms either without any data or with data already populated from the system. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-09 Records Module IR-27 The solution shall enable provide users with the capability to re-associate all records for an inmate or detainee under one OCN record. I = Included This is a standard function of the ATIMS Records Module IR-28 The solution shall have the capability to produce .pdf forms that can also support e-signatures. These forms should be attached to the specific booking record. I = Included This is a standard function of the ATIMS Records Module IR-29 The solution shall provide users with the ability to record the "book and release" of a subject. I = Included This is a standard function of the ATIMS Records Module IR-30 The solution shall provide users with the ability to record details of contacts or attempted contacts with outside parties. I = Included This is a standard function of the ATIMS Records Module IR-31 The solution shall provide users with the ability to record, review, and edit inmate court hearing information, including bail information. I = Included This is a standard function of the ATIMS Records Module IR-32 The solution shall provide the ability for users to record chronological notes to identify the actions taken on extradition cases within/outside Orange County. I = Included This is a standard function of the ATIMS Records Module IR-33 The solution shall provide users with the ability to create a new failure to self-surrender letter and/or a "no-show" letter. I = Included This is a standard function of the ATIMS Records Module IR-34 The solution shall provide users with the ability to add chronological notes to an inmate's booking number record. I = Included This is a standard function of the ATIMS Records Module IR-35 The solution shall provide users with the ability to add multiple Holds/Detainers and for the entry of a hold/detainer charge(s), hold agency, bail amount, expiration date, and hold disposition. These fields should be user- configurable. The system should not allow for the release of an inmate if the inmate has a hold(s) that does/do not have a releasable disposition. I = Included This is a standard function of the ATIMS Records Module IR-36 The solution shall provide users with the ability to upload and attach the tie it arresting officer's probable cause declaration to the booking record. I = Included This is a standard function of the ATIMS Records Module IR-37 The solution shall provide users with the ability to add new charge(s), warrant(s), and place hold(s), on an inmate record to an existing booking number. I = Included This is a standard function of the ATIMS Records Module IR-38 The solution shall provide users with the capability of sending an electronic notification to or receiving an electronic notification from the probation/PRCS staff if the inmate is on Supervised Release. C = Configurable This configuration is included in the associated interfaces. IR-39 The solution shall provide users with the ability to create a list of subjects who failed to self- surrender as required. I = Included This is a standard function of the ATIMS Records Module IR-40 The solution shall provide users with the ability to create a list of subjects booked during a given time period. I = Included This is a standard function of the ATIMS Records Module IR-41 The solution shall provide users with the ability to maintain booking averages for each arresting agency. I = Included This is a standard function of the ATIMS Records Module IR-42 The solution shall provide a fingerprint card that is printable and available to view on screen. The fingerprint sheet should include inmate name, DOB, race, sex, SSN, OCN number number, booking number, booking date/time, and all current charges to include arresting agency, location of arrest, arrest date/time, arrest type, court case number, arresting officer, arresting agency case number, inmate photo, and a specified area to collect a ink thumb print. I = Included This is a standard function within the entire ATIMS system. It is available as the Inmate Summary with Fingerprint function. IR-43 The solution shall provide users with the ability to enter booking information on special cases (inmate numbercivil commitments, witnesses with no charges and subjects serving out of County sentences). I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-10 Records Module IR-44 The solution shall enable provide users with the ability to record victim information. The system should allow users to enter information from multiple sources/documents such as the Statement flag an inmate record if victim notification is required and provide an alert at time of Booking Officer (SOBO), Pre-booking, PCD etc. As mentioned earlier, it is expected that this information will come in through an automated interface that will obtain data real-time and insert it into the inmate recordrelease if notification has not yet been made. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-11 Records Module IR-45 The solution shall enable provide users to search for an inmate record based on multiple criteria such as, but not limited to: name, alias, SSN, and date of birth. N = Not Included 80 ATIMS has all functions available in the base system with the exception ability to alert classification/special handling of SSN. ATIMS will add this function as an enhancement. AD-12 The solution shall enable users to add a booking number for each incarceration event. These booking numbers must be linked to the OCN numberadditional charges or changes. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-13 Records Module IR-46 The solution shall consolidate inmate provide users with the ability to enter information into on a fugitive hold. i.e. title of charges… I = Included This is a standard function of the original OCN#ATIMS Records Module IR-47 The solution shall provide the capability to enable an authorized User to expunge or modify records by the booking, case or offense. A history of corrections must also be maintainedThe audit trail shall detail who and when the deletion was made. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-14 Records Module IR-48 The solution shall provide users with the ability capability to search an incorporate extensive validation checks to ensure that two separate records are not created for the same inmate's prior incarceration information and alerts. The system must prompt users This will include, but not be limited to carry over prior alerts to the new record. It should also provide users with the ability to NOT carry over an alert (parameters such as a medical alert that is no longer relevant) if so desired by OCSDas: gender, height, weight, overlapping incarcerations, etc. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-15 Records Module IR-49 The solution shall provide users with the ability to capture custody booking status includingrecord charge dispositions as releasable or non-releasable. Non-releasable dispositions must prevent the release of an inmate and provide an over ridable warning message prior to release. N = Not Included 24 ATIMS will add flagging of the charge disposition and a conflict check upon release. Certain reasons for release can be flagged to ignore the non- release flag. This will allow the current system to meet this requirement . IR-50 The solution shall provide users with the ability to add, but not limited to: a. Pre-trial b. Sentenced c. Detainer modify, and delete a final release. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-16 Records Module IR-51 The solution shall provide users with the ability to do a partial or full copy capture the agency name, officer name and badge number of the officer picking up an inmate information from a previous bookingfor transfer to another agency. The solution shall maintain all previous booking information (e.g. photos, tattoos, classification, release, etc.) I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-17 Records Module IR-52 The solution shall provide users with the ability to annotate that a detainer was provided to an outside agency. I = Included This is a standard function of the ATIMS Records Module IR-53 The solution shall provide users with the ability to schedule releases. The system should enable authorized staff to view and/or print a list of all inmates scheduled for release based on user configurable parameters such as release types, predicted sentence expirations or policy decisions. I = Included This is a standard function of the ATIMS Records Module IR-54 The solution shall provide users with the ability to record inmate information includingadd comments/approval/denial of court order. This must include the order type, but not limited to: a. Name (Lastdate received, Middlecase number, MIfree text notes field, Suffix) b. Name Type (Legal, Committed, Alias, Nickname)and approval or denial of the order. I = Included This is a standard function of the ATIMS request engine IR-55 The solution
Appears in 1 contract
Functional Requirements. Intake Housing Req # Requirement Text Included, Configurable Configurable, not Included (I, C, N) Estimated Hours to Customize ATIMS Capabilities AD-01 IH-01 The solution shall support the intake and booking process in compliance provide users with the OCSD policies ability to manage inmate housing based on the Policies and proceduresProcedures of the OCSD. I = Included ATIMS has a state of the art JMS system that is installed in several California counties. Our intake and booking modules housing module meets the policy and procedures of these agencies. We believe that the ATIMS JMS would also meet the policy and procedure of OCSD but without reviewing them we cannot guarantee this. AD-02 The solution shall provide the capability for authorized users to enter basic information such as the date and time of arrival, agency, name of officer, name(s) of inmates and basic medical information. The system must also provide the capability to ingest information that is sent through an electronic data exchange upon approval from an authorized user. I = Included ATIMS provides all of these functions as part of the base system. If an interface is used to import Prebooking data a cost may be incurred. AD-03 IH-02 The solution shall enable authorized OCSD users to assign a system-generated temporary (pre-booking) number to each inmateconfigure and name facilities, housing sectors, location and bunks based on the physical layout. This layout can be modified without the need for programming I = Included This is a standard function of the ATIMS Prebooking Administration module. AD-04 IH-03 The solution shall enable authorized OCSD-users to send the information identified configure specific housing locations and/or bunks as "usable" or "unusable" based on various scenarios. An example of a scenario is where an inmate who has to be kept separate from other inmates is housed in AD-02 and AD-03 a two bunk cell. The 2nd bunk will then need to the CHS medical system using an automated interface. be marked "unusable." I = Included This is called a total separation flag in ATIMS has an internal interface engine that can accomplish this and is available as a standard configuration function. All included interfaces have been quoted in the cost proposal. AD-05 IH-04 The solution shall trigger a notification provide the capability for cells to be sent to OCSD-designated staff if an inmate requires immediate medical or mental health attention. C labelled specifically for "ICE" detainees I = Configurable Included This functionality is a standard configuration currently in development as part of the ATIMS event engine product evolution. This will be available to OCSD at NO COST and can will be configuredaccessible by the use of inmate flags and housing flags. AD-06 IH-05 The solution shall support an interface with allow appropriate users to take a cell offline, change the CHS medical system to receive information after Triage activities have been conducted on custody level, add new areas and beds for Emergency Assignments without the inmate and the inmate is ready to be booked. (Interface details are provided in the technical requirements.) C = Configurable This is a standard function of the ATIMS Interface engine. All included interfaces have been quoted in the cost proposal. AD-07 The solution shall populate the booking officers queue with the name(s) of the inmates that have cleared the Triage process and are ready to be bookedneed for any programming. I = Included This is a standard function of within the ATIMS Intake and Booking ModuleFacility module. AD-08 IH-06 The solution shall enable provide appropriate users with the ability to update view a current snapshot of all the facility and location count after facilities within OCSD. This should display the inmate has received a booking number in the systemof beds available by custody levels, facilities, etc. I = Included This is a standard function within the ATIMS Facility module. IH-07 The solution shall support the ability for a user to assign an inmate to a housing unit. Ideally, a drag and a drop function would be desirable. I = Included All functions mentioned are currently available in the current ATIMS version with the exception of Drag and Drop. That feature will available in future versions of the software (Version 2) IH-08 The solution shall provide the ability to warn staff of situations relating to Keep Separates, medical issues, mental health issues, and Victim/Predator status prior to assigning an inmate to a housing area. I = Included This functionality is currently in development as part of the ATIMS Intake product evolution. This will be available to OCSD at NO COST and Booking Modulewill be accessible by the use of inmate flags and housing flags. AD-09 The Victim/Predator conflict check will be part of the PREA Module enhancement ▇▇-▇▇ ▇▇-▇▇ The solution shall provide the ability for a user to override a warning and to house an inmate in an area with a keep separate. It must record who authorized the move, the date and time the moved was authorized, and the reason for the move. I = Included This is a standard function within the ATIMS Facility module. IH-10 The solution shall show a specific housing unit/bunk as "reserved" once an inmate has been assigned to it. I = Included This is a standard function within the ATIMS Facility module. IH-11 The solution shall automatically schedule a movement for an inmate from his/her current housing location to the new housing location when a housing assignment is entered. N = Not Included 160 ATIMS uses appointments to provide this functionality however based on this requirement and others listed ATIMS believes the best answer for OCSD is to build a movement officer module. ATIMS will build this module based on this requirement. IH-12 The solution shall enable users a user to create display a list of expected returning Weekender inmates and allow the user to assign a new booking number housing location to a Weekender each time the inmate returns to the facility after the initial Admissions process. The system must default to the previous week's list to minimize data entry for users. N = Not Included included in IR-91 IH-13 The solution shall maintain a complete history of every cell an inmate has been assigned to and their cell stay date and time, including cell mates as well as the tie it staff member who entered the housing change, reason and comments. This history is critical to the OCN number medical investigations (inmate numbere.g. an infectious disease situation) or criminal investigations (e.g. witness confirmation). I = Included This is a standard function of within the ATIMS Intake and Booking ModuleFacility module. AD-10 IH-14 The solution shall enable users the housing deputies to enter information from multiple sources/documents such as the Statement of Booking Officer make changes to bunks in a very user friendly manner (SOBOdrag and drop feature is preferred), Pre-booking, PCD etc. As mentioned earlier, it is expected that this information will come in through an automated interface that will obtain data real-time and insert it into the inmate record. I = Included This is a standard function of within the ATIMS Intake and Booking ModuleFacility module. AD-11 IH-15 The solution shall enable users to search keep a history of housing changes for an inmate record based on multiple criteria such asdisplay. The system must track any changes as well as display the reason for and comments regarding the change (e.g. Pod move, but not limited to: nameCell change, alias, SSN, and date of birth. N = Not Included 80 ATIMS has all functions available in the base system with the exception of SSN. ATIMS will add this function as an enhancement. AD-12 The solution shall enable users to add a booking number for each incarceration event. These booking numbers must be linked to the OCN numberD Report #). I = Included This is a standard function of within the ATIMS Intake and Booking ModuleFacility module. AD-13 IH-16 The solution shall consolidate inmate information into ensure that the original OCN#. A history of corrections must also be maintained. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-14 The solution shall provide users housing module interfaces with the ability security module to search an inmate's prior incarceration information view special management status of inmates, including start date and alerts. The system must prompt users to carry over prior alerts to the new record. It should also provide users with the ability to NOT carry over an alert (expected end date, for such as a medical alert that is no longer relevant) if so desired by OCSD. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-15 The solution shall provide users with the ability to capture custody booking status Special Management areas including, but not limited to: a. Pre-trial Administrative Segregation b. Sentenced Protective Custody c. Detainer I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-16 The solution shall provide users with the ability to do a partial or full copy of inmate information from a previous booking. The solution shall maintain all previous booking information (e.g. photos, tattoos, classification, release, etc.) I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-17 The solution shall enable users to record inmate information including, but not limited to: a. Name (Last, Middle, MI, Suffix) b. Name Type (Legal, Committed, Alias, Nickname)Suicide Watch d.
Appears in 1 contract
Functional Requirements. Intake Mail Req # Requirement Text Included, Configurable Configurable, not Included (I, C, N) Estimated Hours to Customize ATIMS Capabilities AD-01 IM-01 The solution shall support the intake processing and booking process documentation of inmate mail in compliance with the OCSD policies and procedures. I = Included ATIMS has a state of the art JMS system that is installed in several California counties. Our intake mail module is currently in development and booking modules meets is designed to meet the policy and procedures of these agencies. We believe that the ATIMS JMS would also meet the policy and procedure of OCSD but without reviewing them we cannot guarantee this. AD-02 The solution shall provide the capability for authorized users to enter basic information such as the date and time of arrival, agency, name of officer, name(s) of inmates and basic medical information. The system must also provide the capability to ingest information that is sent through an electronic data exchange upon approval from an authorized user. I = Included ATIMS provides all of these functions as part of the base system. If an interface is used to import Prebooking data a cost may be incurred. AD-03 IM-02 The solution shall enable users to assign a system-generated temporary (pre-booking) number to each inmate. I = Included This is a standard function authorize the source of the ATIMS Prebooking module. AD-04 The solution shall enable authorized users to send the information identified in AD-02 and AD-03 to the CHS medical system using an automated interface. I = Included ATIMS has an internal interface engine any electronic mail that can accomplish this function. All included interfaces have been quoted in the cost proposal. AD-05 The solution shall trigger a notification to be sent to OCSD-designated staff if an inmate requires immediate medical or mental health attention. C = Configurable This is a standard configuration of the ATIMS event engine and can be configured. AD-06 The solution shall support an interface with the CHS medical system to receive information after Triage activities have been conducted on the inmate and the inmate is ready to be booked. (Interface details are provided in the technical requirements.) C = Configurable This is a standard function of the ATIMS Interface engine. All included interfaces have been quoted in the cost proposal. AD-07 The solution shall populate the booking officers queue with the name(s) of the inmates that have cleared the Triage process and are ready to be booked. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-08 The solution shall enable users to update the facility and location count after the inmate has received a booking number in the system. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-09 The solution shall enable users to create a new booking number for an inmate and the tie it to the OCN number (inmate number). I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-10 The solution shall enable users to enter information from multiple sources/documents such as the Statement of Booking Officer (SOBO), Pre-booking, PCD etc. As mentioned earlier, it is expected that this information will come in through an automated interface that will obtain data real-time and insert it into the inmate record. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-11 The solution shall enable users to search for an inmate record based on multiple criteria such as, but not limited to: name, alias, SSN, and date of birthreceives. N = Not Included 80 ATIMS has all functions available in the base system 160 An Interface is required with the exception of SSNemail Contractor. ATIMS will add ADMIN space for configuration and forward ability and or printed copy. Additionally ATIMS will add the functionality listed to meet this function as an enhancementrequirement. AD-12 The solution shall enable users to add a booking number for each incarceration event. These booking numbers must be linked to the OCN number. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-13 The solution shall consolidate inmate information into the original OCN#. A history of corrections must also be maintained. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-14 IM-03 The solution shall provide users with the ability capability to flag inmates that are on the "mail cover list." N = Not Included 40 ATIMS will add an internal flag against inmate that will show during show during the mail search an inmate's prior incarceration information process to meet this requirement. This enhancement is in addition to IM-02 and alerts. OCSD must select both of these enhancements to achieve this functionality IM-04 The system must prompt solution shall enable users to carry over prior alerts to document the new record. It should also provide users with results of a search of incoming mail for inmates who are on the ability to NOT carry over an alert (such as a medical alert that is no longer relevant) if so desired by OCSDmail cover list. I = Included ATIMS is currently developing a complete mail module for another client that meets this requirement. This will be available to OCSD at NO COST. IM-05 The solution shall enable users to document any contraband found after the search of incoming mail. I = Included ATIMS is currently developing a complete mail module for another client that meets this requirement. This will be available to OCSD at NO COST. IM-06 The solution shall enable the mail staff to record any checks that were received for a specific inmate by mail. I = Included ATIMS is currently developing a complete mail module for another client that meets this requirement. This will be available to OCSD at NO COST. IM-07 The solution shall provide the capability to notify appropriate staff if criminal contraband was discovered in the mail during the initiation of the DR process. C = Configurable ATIMS is currently developing a complete mail module for another client that meets this requirement. This will be available to OCSD at NO COST. IM-08 The solution shall enable users to document the return of non-criminal contraband found in the mail. I = Included ATIMS is currently developing a complete mail module for another client that meets this requirement. This will be available to OCSD at NO COST. IM-09 The solution shall enable users to document names and addresses found on incoming mail. I = Included ATIMS is currently developing a complete mail module for another client that meets this requirement. This will be available to OCSD at NO COST. IM-10 The solution shall enable users to scan an inmate's mail and mail cover and forward a scanned copy, as well as an electronic message, to the requesting law enforcement agency. N = Not Included 120 This functionality will be added to the ATIMS mail module to meet this requirement, IM-11 The solution shall enable users to document any outgoing mail search. N = Not Included 112 The current ATIMS mail module development does not include an out going mail module. To meet this requirement ATIMS will add an outgoing mail module. IM-12 The solution shall allow users to send notifications to the appropriate personnel to start DR proceedings if criminal contraband is found in outgoing mail. C = Configurable ATIMS is currently developing a complete mail module for another client that meets this requirement. This will be available to OCSD at NO COST. IM-13 The solution shall support the capability to keep a list of indigent ICE Detainees so that stamps can be provided to them. The exact amount to be deemed indigent needs to be configurable. C = Configurable ATIMS will configure a new report of this information and will add an indigent threshold in ADMIN to meet this requirement as a configuration at NO COST to OCSD. IM-14 The solution shall provide the capability to scan outgoing mail and document the address details if an inmate is on the Mail Cover list. N = Not Included This is included IM-11 IM-15 The solution shall provide an “alert” function for special handling verifications on specific inmates when they send or receive mail. I = Included ATIMS is currently developing a standard function of complete mail module for another client that meets this requirement. This will be available to OCSD at NO COST. IM-16 The solution shall provide enable users to add comments about individual correspondence (either inbound or outbound mail.) I = Included ATIMS is currently developing a complete mail module for another client that meets this requirement. This will be available to OCSD at NO COST. IM-17 The solution shall provide the capability to digitize all incoming mail to be delivered electronically to inmates. N = Not Included 160 ATIMS will add this functionality to the ATIMS Intake and Booking Modulemail module to meet this requirement. AD-15 OCSD must also chose to do the enhancement for IM-11 as well. IM-18 The solution shall provide users with the ability capability to capture custody booking status including, but not limited to: a. Pre-trial b. Sentenced c. Detainer provide digital readers to inmates for reading correspondence. I = Included This is functionality can be made available via inmate kiosks. ATIMS does not provide inmate tablets. ATIMS can interface with a standard function tablet provider or put our software on the Contractors tablets. Security for these tablets will be the responsibility of the tablet Contractor. IM-19 The system shall allow investigations staff to flag an inmate for an inbound or outgoing mail hold. I = Included ATIMS Intake is currently developing a complete mail module for another client that meets this requirement. This will be available to OCSD at NO COST. IM-20 The system shall track and Booking Modulecatalog mail sent to and received from an inmate, including logging legal and official mail. AD-16 Users must be able to run reports showing mail sent and received by inmates, including the address of the sender for outgoing mail - This is especially important for Legal Mail for ICE detainees. I = Included included in IM-11 IM-21 The solution shall provide allow users with to record the ability to do a partial discovery of contraband found in incoming or full copy of inmate information from a previous bookingoutgoing mail. The solution shall maintain all previous booking information (e.g. photos, tattoos, classification, release, etc.) I = Included ATIMS is currently developing a complete mail module for another client that meets this requirement. This is a standard function of the ATIMS Intake and Booking Modulewill be available to OCSD at NO COST. AD-17 IM-22 The solution shall enable users to record inmate information including, but not limited to: a. Name (Last, Middle, MI, Suffix) b. Name Type (Legal, Committed, Alias, Nickname)the names of inmates subscribing to defined periodicals. I = Included ATIMS is currently developing a complete mail module for another client that meets this requirement. This will be available to OCSD at NO COST.
Appears in 1 contract
Functional Requirements. Intake Classification Req # Requirement Text Included, Configurable Configurable, not Included (I, C, N) Estimated Hours to Customize ATIMS Capabilities AD-01 The solution shall support the intake and booking process in compliance with the OCSD policies and procedures. I = Included ATIMS has a state of the art JMS system that is installed in several California counties. Our intake and booking modules meets the policy and procedures of these agencies. We believe that the ATIMS JMS would also meet the policy and procedure of OCSD but without reviewing them we cannot guarantee this. AD-02 The solution shall provide the capability for authorized users to enter basic information such as the date and time of arrival, agency, name of officer, name(s) of inmates and basic medical information. The system must also provide the capability to ingest information that is sent through an electronic data exchange upon approval from an authorized user. I = Included ATIMS provides all of these functions as part of the base system. If an interface is used to import Prebooking data a cost may be incurred. AD-03 The solution shall enable users to assign a system-generated temporary (pre-booking) number to each inmate. I = Included This is a standard function of the ATIMS Prebooking module. AD-04 The solution shall enable authorized users to send the information identified in AD-02 and AD-03 to the CHS medical system using an automated interface. I = Included ATIMS has an internal interface engine that can accomplish this function. All included interfaces have been quoted in the cost proposal. AD-05 The solution shall trigger a notification to be sent to OCSD-designated staff if an inmate requires immediate medical or mental health attention. C = Configurable This is a standard configuration of the ATIMS event engine and can be configured. AD-06 The solution shall support an interface with the CHS medical system to receive information after Triage activities have been conducted on the inmate and the inmate is ready to be booked. (Interface details are provided in the technical requirements.) C = Configurable This is a standard function of the ATIMS Interface engine. All included interfaces have been quoted in the cost proposal. AD-07 The solution shall populate the booking officers queue with the name(s) of the inmates that have cleared the Triage process and are ready to be booked. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-08 The solution shall enable users to update the facility and location count after the inmate has received a booking number in the system. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-09 The solution shall enable users to create a new booking number for an inmate and the tie it to the OCN number (inmate number). I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-10 The solution shall enable users to enter information from multiple sources/documents such as the Statement of Booking Officer (SOBO), Pre-booking, PCD etc. As mentioned earlier, it is expected that this information will come in through an automated interface that will obtain data real-time and insert it into the inmate record. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-11 The solution shall enable users to search for an inmate record based on multiple criteria such as, but not limited to: name, alias, SSN, and date of birth. N = Not Included 80 ATIMS has all functions available in the base system with the exception of SSN. ATIMS will add this function as an enhancement. AD-12 The solution shall enable users to add a booking number for each incarceration event. These booking numbers must be linked to the OCN number. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-13 The solution shall consolidate inmate information into the original OCN#. A history of corrections must also be maintained. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-14 CL-01 The solution shall provide users with the ability to search identify and appropriately assess an inmate's prior incarceration information inmate in order to provide safe and alerts. The system must prompt users to carry over prior alerts to secure placement within the new record. It should also provide users with the ability to NOT carry over an alert (such as a medical alert that is no longer relevant) if so desired by OCSDfacility. I = Included This is a standard function functionality of the ATIMS Intake and Booking Classification Module. AD-15 CL-02 The solution shall enable a user to generate an electronic list of all inmates waiting for classification review who have been processed through booking and are available for initial classification. I = Included This is standard functionality of the ATIMS Classification Module. CL-03 The solution shall provide the ability for users to identify and assess an inmate with an objective validated tool to ensure an appropriate housing placement choice is made and programmatic mandates within the organization’s jurisdiction are met. OCSD utilizes its own classification instrument. The solution shall be able to I = Included The ATIMS Classification Module uses our agency configurable forms engine to create an electronic form that can be configured to the needs of OCSO. Because this form is built on HTLM and Javascript the functions available within the form are numerous support subjective, objective, as well as an external instrument. CL-04 The solution shall enable authorized external users, such as court staff, to view classification and booking alerts. I = Included This is standard functionality of the ATIMS Classification Module. CL-05 The solution shall provide users with the ability to identify an inmate’s custody status as unsentenced or sentenced. I = Included This is standard functionality of the ATIMS Classification Module. CL-06 The solution shall notify classification users of any changes that could affect the classification of an inmate. C = Configurable This is a standard function available within the Classification module when used in conjunction with the request engine and event triggers. CL-07 The solution shall provide the ability to clearly and quickly identify the custody status of an inmate (i.e. use of color coding in the header, etc.) N = Not Included 16 ATIMS create a custody status in the header where data is displayed. CL-08 The solution shall recommend classification levels based on responses to questions in the classification instrument. I = Included This is standard functionality of the ATIMS Classification Module. CL-09 The solution shall provide the ability for authorized users and supervisory staff to override system-generated classifications as well as capture custody the new classification level, the staff ID making the change, and override reason. I = Included This is standard functionality of the ATIMS Classification Module. CL-10 The solution shall provide Classification personnel with the ability to view current and historical information about an inmate providing a "360 degree view." The information should include, but not be limited to: a. Current charges including highest charge b. Criminal History "Rap Sheet" c. Behavior (disciplinary, other) d. Program participation I = Included This is standard functionality of the ATIMS Classification Module. CL-11 The solution shall enable authorized users to conduct additional queries of external systems to obtain more detailed information for Classification and/or Special Handling. The user should be able to execute these queries from within the proposed solution and have the ability to select one or multiple data sources. These system include but are not limited to: a. ELETE, b. CII c. FBI d. ▇▇▇▇ ▇. EZ Payment System – Inmate funds database (kiosk, online), f. VISION – Criminal and Traffic court database, g. COPLINK – inter-agency law enforcement contact database, h. CALGANGS – interagency state (CA) gang database, i. GTL - Global Telecommunications Link – Jail phone recording database, j. TAGRS – Orange County graffiti tracking/reporting system N = Not Included 320 ATIMS will provide necessary interfaces as specified out in the interface section. Additional queries outside of interfaces will have to be examined on a case by case basis and costed out. ATIMS has included up to 2 months of programming to meet this requirement however this may not be enough and will need to be re-quoted after discussions with OCSD. As an additional option the county may provide a middleware solution to allow ATIMS to query the middleware and return the data. Each system will be a query that will be routed by the middle ▇▇▇▇. CL-12 The solution shall provide the ability to notify the classification user when an inmate has been in OCSD for a specific time period and not been classified, based on the time the inmate arrived in Receiving. I = Included The standard ATIMS work flow places the inmate in to the classification queue at the completion of the booking status including, process. If this is not part of the work process a custom queue can be created for OCSO as well CL-13 The solution shall provide the ability to automatically schedule an inmate for re- classification based rules to include but not limited to: a. Pre-trial determined interval schedule b. Sentenced Disciplinary action c. Program completion d. Court action such as bail change, conviction or additional charges. C = Configurable The system has a base queue available for those who have reached a defined number of days since the last classification based on either housing unit or classification level. Addition of the inmate to the queue based on events is available as a configuration of the event engine. CL-14 The solution shall provide an electronic list of upcoming reclassifications required indicating the reason for the reclassification. These should include, but not be limited to: a. Scheduled b. Disciplinary action c. Program completion d. Bail status e. Parole status f. Detainer status C = Configurable Result of action would be placed in separate queue Included in CL-13 CL-15 The solution shall enable a classification user to reclassify an inmate and record the reclassification result. The system must identify the staff id for the user that has taken this action. I = Included This is a standard function functionality of the ATIMS Intake and Booking Classification Module. AD-16 CL-16 The solution shall provide enable authorized users to override a re-classification. System must capture the staff ID when he/she adjusts the inmate record with the ability to do a partial or full copy of inmate information from a previous bookingnew classification level and override reason. The solution shall maintain all previous booking information (e.g. photos, tattoos, classification, release, etc.) I = Included This is a standard function functionality of the ATIMS Intake and Booking Classification Module. AD-17 The solution shall enable users to record inmate information including, but not limited to: a. Name (Last, Middle, MI, Suffix) b. Name Type (Legal, Committed, Alias, Nickname).
Appears in 1 contract
Functional Requirements. Intake Property Req # Requirement Text Included, Configurable Configurable, not Included (I, C, N) Estimated Hours to Customize ATIMS Capabilities AD-01 The solution shall support the intake and booking process in compliance with the OCSD policies and procedures. I = Included ATIMS has a state of the art JMS system that is installed in several California counties. Our intake and booking modules meets the policy and procedures of these agencies. We believe that the ATIMS JMS would also meet the policy and procedure of OCSD but without reviewing them we cannot guarantee this. AD-02 The solution shall provide the capability for authorized users to enter basic information such as the date and time of arrival, agency, name of officer, name(s) of inmates and basic medical information. The system must also provide the capability to ingest information that is sent through an electronic data exchange upon approval from an authorized user. I = Included ATIMS provides all of these functions as part of the base system. If an interface is used to import Prebooking data a cost may be incurred. AD-03 Capabilities
IP-01 The solution shall enable users to assign a system-generated temporary (pre-booking) number to each inmatethe documentation, storage and disposal of property. I = Included This is a standard function of the ATIMS Prebooking module. AD-04 The solution shall enable authorized users to send the information identified in AD-02 and AD-03 to the CHS medical system using an automated interface. I = Included ATIMS has an internal interface engine that can accomplish this function. All included interfaces have been quoted in the cost proposal. AD-05 The solution shall trigger a notification to be sent to OCSD-designated staff if an inmate requires immediate medical or mental health attention. C = Configurable This is a standard configuration of the ATIMS event engine and can be configured. AD-06 The solution shall support an interface with the CHS medical system to receive information after Triage activities have been conducted on the inmate and the inmate is ready to be booked. (Interface details are provided in the technical requirements.) C = Configurable This is a standard function of the ATIMS Interface engine. All included interfaces have been quoted in the cost proposal. AD-07 The solution shall populate the booking officers queue with the name(s) of the inmates that have cleared the Triage process and are ready to be booked. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-08 property module IP-02 The solution shall enable users to update the facility and location count after the inmate review a queue that shows inmates that have been accepted by OCSD whose property has received a booking number in the systemnot yet been collected. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-09 The solution shall enable users property officer should be able to create a new booking number for select an inmate from this list and the tie it be directed to the OCN number (inmate numberappropriate property screen(s). I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-10 property module IP-03 The solution shall enable users to enter document property collected from an inmate during the booking/ intake process. The information from multiple sources/documents such as collected must include, but not be limited to: a. Item name b. Item quantity c. Item description I = Included This is a standard function of the Statement ATIMS property module IP-04 The solution shall have the capability for users to store photographs of Booking Officer (SOBO), Pre-booking, PCD etcspecific property items if taken by OCSD which may be attached to the specific property item. As mentioned earlier, it I = Included This is expected a future functionality that this information is currently in development and will come be available to OCSD at NO COST IP-05 The solution shall support the ability for a signature pad to be used in through order for an automated interface that will obtain data real-time and insert it into the inmate recordto sign an issued property receipt. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-11 property module IP-06 The solution shall enable users have the ability to search issue a hard copy receipt for any non-cash property that has been taken from an inmate record based on multiple criteria inmate. Property receipt must include data elements such as, but not limited to: inmate's name, aliasbooking number, SSNproperty list/description, and date of birtharresting officer/agency, booking officer, storage location, OCN number, DOB, barcoding, booking date/time, age, race, sex, money balance with receipt number(interface), space to allow for inmate/staff e-signatures. N = Not Included 80 160 ATIMS has all functions most of requested information is available in via our stock forms. This is one of the base few areas of the system with where the exception of SSNoutput is not configurable. ATIMS will add this function as create an enhancement. AD-12 The solution shall enable users enhancement that will convert our current configuration to add a booking number for each incarceration event. These booking numbers must be linked to the OCN number. I = Included This is a standard function of use the ATIMS Intake forms engine for property receipt output. This will allow for a configurable and Booking Module. AD-13 The solution shall consolidate inmate information into the original OCN#. A history of corrections must also be maintained. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-14 The solution shall provide users with the ability to search an inmate's prior incarceration information and alerts. The system must prompt users to carry over prior alerts to the new record. It should also provide users with the ability to NOT carry over an alert (such as a medical alert that is no longer relevant) if so desired by OCSD. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-15 The solution shall provide users with the ability to capture custody booking status including, but not limited to: a. Pre-trial b. Sentenced c. Detainer I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-16 The solution shall provide users with the ability to do a partial or full copy of inmate information from a previous booking. The solution shall maintain all previous booking information (e.g. photos, tattoos, classification, release, etcmodifiable receipt.) I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-17 The solution shall enable users to record inmate information including, but not limited to: a. Name (Last, Middle, MI, Suffix) b. Name Type (Legal, Committed, Alias, Nickname)
Appears in 1 contract