The sequence number of saved transaction that must be used to send information to host computer The status of the transaction The PIN must conform to industry-standard security protocols to: Encrypt in a physically secure device Resist software or hardware tapping, interrogation, tampering and modification of the device Resist diagnostic or maintenance procedures Resist device examination theft Perform PIN translation in a physically secure environment, and store encryption keys so they are not accessible through unauthorized access Utilize Key Exchange Keys (KEK) and PIN Encryption Keys (PEK). The mobile application must be fully compliant with all current and relevant ISO standards to prevent tampering and other unauthorized use. The Contractor must provide written notification within 10 business days to the provider and to ODJFS of the outcome of any investigation arising from a provider dispute or a complaint related to the deployment or use of the mobile application. System Integration Requirements The Contractor must develop and maintain a Detailed Data Interface Document. The Detailed Data Interface Document (DID) must be available in hardcopy and electronic media, in a format approved by ODJFS and must include: Resource requirements that detail time estimates for transaction and batch processes required for production; An identification of system files and processing architecture to support data interfaces; A general narrative of the flow of data interfaces to and from the system; A detailed description and diagram of the interfaces system architecture identifying how components are integrated to meet RFP requirements; A listing and brief description of each file; layouts for all interface files to include, at a minimum, file names, data element names, comprehensive data element dictionary with valid values, record length, record names and types, data validation rules for file data content and related processing to insure data integrity and quality; and Application Programming Interfaces (APIs) used within the application to communicate with ODJFS for data interfaces or with external systems must also be defined. Security controls and protocols used to ensure Confidentiality, Integrity and Availability of the Interfaces (i.e., Encryption, Authentication, etc.). Detailed Data Interface Document.
The sequence number of saved transaction that must be used to send information to host computer The status of the transaction The PIN must conform to industry-standard security protocols to: Encrypt in a physically secure device Resist software or hardware tapping, interrogation, tampering and modification of the device Resist diagnostic or maintenance procedures Resist device examination theft Perform PIN translation in a physically secure environment, and store encryption keys so they are not accessible through unauthorized access Utilize Key Exchange Keys (KEK) and PIN Encryption Keys (PEK). The mobile application must be fully compliant with all current and relevant ISO standards to prevent tampering and other unauthorized use. The Contractor must provide written notification within 10 business days to the provider and to ODJFS of the outcome of any investigation arising from a provider dispute or a complaint related to the deployment or use of the mobile application. System Integration Requirements The Contractor must develop and maintain a Detailed Data Interface Document. The Detailed Data Interface Document (DID) must be available in hardcopy and electronic media, in a format approved by ODJFS and must include: Resource requirements that detail time estimates for transaction and batch processes required for production; An identification of system files and processing architecture to support data interfaces; A general narrative of the flow of data interfaces to and from the system; A detailed description and diagram of the interfaces system architecture identifying how components are integrated to meet RFP requirements; A listing and brief description of each file; layouts for all interface files to include, at a minimum, file names, data element names, comprehensive data element dictionary with valid values, record length, record names and types, data validation rules for file data content and related processing to insure data integrity and quality; and Application Programming Interfaces (APIs) used within the application to communicate with ODJFS for data interfaces or with external systems must also be defined. Security controls and protocols used to ensure Confidentiality, Integrity and Availability of the Interfaces (i.e., Encryption, Authentication, etc.). Detailed Data Interface Document.