Annex_I_Checklist__Aug_30_2016.docx

DOCX document 149 KB Posted

Attached to
Interview Recording Management System and Portable Interview Recording System Federal contract opportunity
Solicitation number
RFQ0010143
Issued by
Department of Justice Federal Bureau of Investigation Headquarters Division

About this file

Electronic Annex 1

View the file

Other files for this federal contract opportunity

Other files attached to Interview Recording Management System and Portable Interview Recording System, newest first.
File Type Posted
SF_30_RFQ_0010143_A0003.pdf PDF
Amendment_2_and_SOW.pdf PDF
Amendment_1 _SOW_QA_Annex_1.pdf PDF
IRMS_Matrix.docx DOCX document
Combined_RFQ_0010143_Interview_Room.pdf PDF
SOW_and_Annex.pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

SOW Annex I – Technical Specifications

(U) The purpose of this Annex is to describe the functions and features of an Interview Recording Management System (IRMS). The requirements for the Interview Recording Management System are presented in table format below. Mandatory requirements (utilizing “shall” in the description) are listed for each category. In addition, capabilities desired by the Government are also listed (using “should” in the description). Any proposed system must comply with the set of mandatory requirements.

Requirements noted as “Mandatory Enhancements—(ME)” must be available within 120 days after award. The ME shall be available for all systems and solutions. If any of the ME are currently available in your solution, provide that information in your technical proposal. If they are not currently available and you can provide them within 120 days after award, provide that information in your technical proposal. If the ME are not currently available and you CAN NOT provide them, provide that information in your technical proposal.

(U) The requirements and desired capabilities are numbered sequentially for reference.

(U) The FBI requires an IRMS to support fixed-location recording and a portable interview recording system (PIRS) to support mobile and portable uses. The fixed-location IRMS will be permanently installed in rooms at the Field Office level and below. The portable PIRS will provide a video/audio recording system to agents via a portable device and will be capable of exporting interviews for use by other FBI systems.

IRMS must capture, record, store, catalog, preserve, secure, share (as permitted), monitor (live), and view (playback) interactions between interviewers and interviewees providing high quality audio and video with customized metadata. The IRMS must ensure evidence integrity across all elements of the system, as evidence integrity is a cornerstone requirement of the FBI and is essential to mission success when criminal prosecutions require accurate, original recordings for introduction into court proceedings. The IRMS will support export of interview recordings and associated metadata for ingest into a larger enterprise evidence collection capability. The IRMS will support export of interviews for creation of portable media for evidence.

(U) Overall system functional capability requirements and desired functional capability requirements are set forth in Table I.1:

(U) The requirements stated in Table I.1, are based on the nominal IRMS configuration specified in Figure I.1. The functionality of the system is described in terms of this configuration; however, Offerors may propose alternative configurations that achieve the same functionality. For example, an alternate configuration may utilize a system that uses one workstation per interview room rather than a server in the control room.

(U) In Figure I.1 the shaded elements, unless otherwise noted, are to be contractor supplied equipment. Items with no shading are government furnished equipment.

UNCLASSIFIED

IRMS SOW Annex IPage 3
UPDATED 8/30/2016UNCLASSIFIED

Figure I.1. Notional IRMS Architecture

Table I.1. IRMS Technical Requirements

Interview Recording Management System and Portable Interview Recording System

Class
Requirement Number
Mandatory/

Optional/ Mandatory Enhance-ment

Architecture
Feature
Requirement Descriptions
Solution Component
COTS/

GOTS/

Opensource Implementation (Out Of Box:

Customization:

Development)

Cross Reference for Tech Volume
Solution Additional Functionality

IRMS

U
1.0.10
M

System Activation and Activity Notification

U
1.0.10.1
ME

Shall have a wall mounted device outside of each individual interview room that can initiate recording in that room.

U
1.0.10.2
M

Shall support initiation of recording remotely from the control room.

U
1.0.10.3
ME

Shall include two recording status notification lights to provide notification that the system is (or is not) recording & properly functioning for recording interview video, audio, and metadata.

U
1.0.10.3.1
ME

Shall include one recording status notification light on an exterior wall/ceiling of the interview room entrance doorway to notify of interview in progress.

U
1.0.10.3.2
ME

Shall include one recording status notification light on the interior of the interview room within sight of the interviewer. Desired: Indicator should not be readily visible to subject.

U
1.0.10.3.3
ME

Recording status indicators shall indicate the system, including all components in the interview room, is recording & properly functioning only if all systems are functioning properly as required to record the interview into the IRMS Controller.

U
1.1
M

Cameras

U
1.1.1
O

Should be an IP-camera that provides a minimum 720p 1280 x 720 image resolution with aspect ratio 16:9.

U
1.1.2
O

Should provide additional resolutions, including: 1080p, 1080i, or 720p.

U
1.1.3
O

Solution for concealed interview room should have cameras with a sufficiently small form factor that they are capable of being concealed from view of the interview subject in the interview room.

U
1.1.4
M

Shall have the ability to control camera settings for compression, color, brightness, sharpness, white balance, exposure control, exposure zones, backlight compensation, defogging, electronic image stabilization and text and image overlay from a computer on the same network as the camera.

U
1.1.5
M

Shall provide cameras with variable focal capability.

U
1.1.6
M

Shall have controllable frame rate and bandwidth.

U
1.1.7
M

Shall use Variable Bit Rate (VBR) or Maximum Bit Rate (MBR) H.264.

U
1.1.9
O

Should support 0.04 lux, digital zoom.

U
1.1.10
O

Should support 12 VDC / 24VAC.

U
1.1.11
O

Should support DV Iris Vari-Focal Lens (2.9mm - 10mm F1.2).

U
1.1.12
O

Should support automatic gain control (AGC).

U
1.2
M

Microphones

U
1.2.1
ME

Shall be capable of being concealed in an interview room, such as in a drop ceiling.

U
1.2.2
M

Shall have an audio frequency response of at least 100 Hz through 5 kHz +/- 6dB.

U
1.2.3
M

Shall have WDR – dynamic capture of 70dB (minimum).

U
1.2.4
M

Shall use (directional, half-space microphone) or microphone that fully captures the voices of the people in the interview room.

U
1.2.5
M

Microphone shall be enclosed in a housing.

U
2.0
M
Control Room
U
2.1
M

Recorder(s)

U
2.1.1
M

Shall be able to record two channels of audio with at least 16kHz wide sampling.

U
2.1.2
M

Shall support recording an audio frequency range of at least 100 Hz through 5 kHz, +/- 6dB.

U
2.1.3
M

Shall support recording of a minimum of two High Definition digital cameras feeds per room.

U
2.1.4
M

Shall support minimum recording resolution of 720p at a minimum frame rate of 29.97 unique images per second per camera with no dropped frames.

U
2.1.5
M

Shall have the capability of displaying separate synchronized video and audio streams from each of the system cameras simultaneously.

U
2.1.6
ME

Shall provide features to mark an event during recording or during playback of recorded video, add notes to that event, and to skip to that marked event during playback.

U
2.1.6.1
ME

Shall provide a feature to mark an event (on video being recorded) in response to a signal from a button or remote control used by an interviewer in the interview room.

U
2.1.6.2
ME

Shall provide feature for an authorized viewer monitoring an interview being recorded to mark an event and enter comments for that mark on the recorded video from the monitoring console.

U
2.1.6.3
ME

Shall provide a feature for an authorized reviewer to mark an event on the recorded video during playback of the video.

U
2.1.6.4
ME

Shall have the capability for an authorized viewer to add notes with a timestamp to the video being recorded during the interview.

U
2.1.6.5
ME

Shall have the capability for an authorized reviewer to add notes during playback at any marked events of the video.

U
2.1.7
M

Shall support synchronization with an official FBI trusted time source using Coordinated Universal Time (UTC).

U
2.1.8
M

Shall be able to associate any recorded frame in the video with the time that frame was recorded, and display that time on playback.

U
2.1.9
M

Shall provide the ability to remotely view and control recording of the video via computer(s) on the same network as the IRMS system.

U
3.0
M
Software
U
3.1
M

User Interface

U
3.1.1
M

Shall have a user interface that provides an onscreen time/date overlay on the video recordings.

U
3.1.2
ME

Shall have a user interface that allows display of additional configurable metadata field(s) [such as case id, room #, interviewer, …]

U
3.1.3
M

Shall have a user interface that is compliant with Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. Sect. 794(d)).

U
3.1.4
M

Shall have a user interface that allows a viewer to select which camera's video is to be displayed on the viewing console.

U
3.1.5
O

Should have the capability for a user to skip directly to marked events in the video and find specific metadata associated with that marked event.

U
3.1.6
ME

Shall have a secure client user interface that allows multiple users to monitor live interviews, including all audio, video, and internally generated metadata.

U
3.1.7
ME

Shall have a secure client user interface that allows multiple users to review recorded interviews, including all audio, video, and internally generated metadata.

U
3.1.8
ME

Shall have a secure client user interface that enables multiple users to view live interviews, and to mark events and enter metadata (including case notes).

U
3.1.9
ME

Shall have a secure client user interface that enables multiple users to view recorded interviews, and to mark events and enter metadata (including case notes).

3.1.10
M

Shall have a secure client user interface that supports Automatic Gain Control and Noise Reduction for clear audio playback.

U
3.1.11
M

Shall support administration of the IRMS system.

U
3.1.11.1
M

Shall support separate profiles for administrator access (system management) and end-user functions.

U
3.1.11.2
O

Should implement administrative functions to grant user privileges, change user privileges (such as administrative rights and data access rights), and revoke user privileges when using Active Directory for user authorization and data access.

U
3.1.11.3
M

Shall implement administrative functions to grant user privileges, change user privileges (such as administrative rights and data access rights), and revoke user privileges when Active Directory is not used for user authorization and data access.

U
3.1.11.4
M

The application shall provide a means for a systems administrator to grant a user the authority to create removable media copies, and prevent any user without this authority from creating removable media.

U
3.1.12
ME

Shall support basic viewing operations--as specified in the following sub-requirements--via a secure thin client interface (such as a web browser) that does not require installation of special software on the remote viewing computer.

U
3.1.12.1
ME

Shall support multiple users simultaneously monitoring live interviews including all audio, video, and pre-populated metadata, via a thin client interface.

U
3.1.12.2
ME

Shall support multiple users simultaneously viewing recorded interviews including all audio, video, and metadata, via a thin client interface.

U
3.1.12.3
O

Thin client should be compatible with Microsoft Internet Explorer and Firefox browsers.

U
3.1.12.4
O

Should support user viewing of live interviews allowing for marking and metadata entry via a thin client interface.

U
3.1.12.5
O

Should support multiple users viewing recorded interviews and allowing for marking and metadata entry via a thin client interface.

U
3.1.12.6
O

Should display an onscreen time/date overlay on the video recordings, for viewing via a thin client interface.

U
3.1.12.7
O

Should allow the user to configure the system to display additional metadata field(s) [such as case id, room #, interviewer, …], when viewed via a thin client interface.

U
3.1.12.8
ME

Shall have a user interface that allows a viewer to select which camera's video is to be displayed on the thin client.

U
3.1.12.9
O

Should support minimization of network bandwidth used to stream video to users using the thin client over a limited bandwidth network connection.

U
3.1.12.10
O

Should have the capability for a user using the thin client interface to skip directly to marked events in the video or find specific metadata associated with that marked event.

U
3.2
M

Processing

U
3.2.1
M

Shall store an evidence copy of the interview recording on IRMS storage.

U
3.2.2
ME

Shall store a working copy of the interview recording on IRMS storage.

U
3.2.3
ME

Shall allow no modifications to the file with the original evidence copy of interview video and audio--any editing to interview video shall saved as a separate and distinct working copy from the evidence file.

U
3.2.4
ME

Shall use a 256 – bit or greater FIPS 140-2 approved hash algorithm to generate a hash value stored with the original video/audio data to be used for authenticating that the video data has been unmodified.

U
3.2.5
M

Shall have a digital asset audit and tracking system.

U
3.2.6
M

Shall record video, audio, and metadata in a standard (container) format and codec. Acceptable standards are: (video) MP4, AVI, MKV, WMV, MJPEG, H.264, H.265, and (audio) WAV.

U
3.2.7
ME

Shall allow input and storage of case notes entered by an authorized user during an interview.

U
3.2.8
O

Should have the ability to accept a trigger from an external device to mark locations within recordings of user-defined events.

U
3.2.9
M

Shall support the ability to instantly review earlier video segments during live recording--without interrupting the recording--to enter case notes or highlight an interviewee's particular action/comment.

U
3.2.10
M

Shall support recording of video at a minimum frame rate of 30 unique images per second per camera with no dropped frames.

U
3.2.11
ME

Shall provide application programming interfaces, service programming interfaces, and/or software development kits to support integration with other systems.

U
3.2.12
ME

Shall have the capability to store or copy interview data in a standard video and audio file format to IRMS storage.

U
3.2.13
O

Should combine the video streams, audio stream and any metadata into one progressive scan format digital video file.

U
3.2.14
M

Shall synchronize video streams, audio stream and any metadata to an accuracy of 33ms throughout the duration of the recording

U
3.2.15
ME

Shall have the capability for Video and Audio redaction (both live and recorded)—to include imported files, to obscure faces or other visible objects, and mask audio that is not intended to be recorded.

U
3.2.15.1
ME

Shall allow the user to define a segment of the recording where the playback will be redacted.

U
3.2.15.2
ME

Shall blackout and skip redacted segments without altering the original audio/video.

U
3.3
M

Audio Input

U
3.3.1
M

Shall provide a minimum of 16-bit PCM audio, and a minimum 16kHz wide sampling, producing an uncompressed linear pulse-code modulation .wav file

U
3.3.2
M

Shall have the capability of recording an audio frequency range of at least 100 Hz through 5 kHz +/- 6dB.

U
3.4
M

Metadata

U
3.4.1
ME

Shall have the ability to create metadata to mark specific events during the recorded interview.

U
3.4.2
ME

Shall have the ability to tag, associate, sort, and retrieve recorded evidence utilizing metadata.

U
3.4.3
ME

Shall place a digital tag/marker indicating placement of case notes.

U
3.4.4
ME

Shall have ability to search, display, and modify metadata, as required.

U
3.4.5
ME

Shall have the ability to pre-populate metadata fields such as room/location.

U
3.4.6
ME

Shall provide the ability to pre-populate metadata tags to mark events such as start of Miranda, Confession.

U
3.4.7
O

Should have the ability to accept metadata from other sources, such as Active Directory/LDAP for username, or GPS for location.

U
3.5
M

Data Export

U
3.5.1
ME

Shall export audio separately/independently from video in the WAV format.

U
3.5.1.1
O

Should export audio separately/independently from video in additional formats, such as mp3, AIFF, PCM, or AAC.

U
3.5.2
ME

Shall export video separately/independently from audio using a standard format and codec, such as MP4, AVI, MKV, MOV, MJPEG, H.264, or H.265.

U
3.5.3
ME

Shall have the capability to export selected recordings and portions of recordings to removable media.

U
3.5.3.1
O

Should have the capability to export selected recordings or portions of recordings to a DVD.

U
3.5.4
O

Should not require trans-coding of the original digital format to export data to removable media and/or storage associated with an enterprise solution.

U
3.5.5
O

Should be able to split a recording across multiple removable media in order to provide recording beyond the length of removable media.

U
3.5.6
O

Should have the ability to generate multiple removable media, each with its own unique labeling.

U
3.5.7
O

Should have the ability to verify the authenticity of a generated removable media recording.

U
3.5.8
ME

Shall support export of video and audio recordings with metadata in a standard video and audio format and codec, such as MP4, AVI, MKV, MOV, MJPEG, H.264, H.265,WAV, and AAC.

U
3.5.9
ME

Shall support export of video and audio recordings without case notes and manual markings in a standard video format and codec, such as MP4, AVI, MKV, MOV, MJPEG, H.264, H.265, WAV, and AAC.

U
3.5.10
O

Should be capable of exporting case notes and/or metadata with video and audio data.

U
3.5.11
O

Should be capable of exporting case notes and/or metadata without video and audio data.

U
3.6
M

Data Import

U
3.6.1
O

Should support import of video with audio and metadata in a standard (container) format and codec. Acceptable standards are: (video) MP4, AVI, MKV, WMV, MJPEG, H.264, H.265, and (audio) WAV, AAC.

U
3.6.1.1
O

Should support import of video with audio and metadata in multiple standard (container) formats and codecs. Acceptable standards are: (video) MP4, AVI, MKV, WMV, MJPEG, H.264, H.265, and (audio) WAV, AAC.

U
4.0
M
Hardware
U
4.0.1
M

Shall be capable of using commercially available cameras, microphones, servers, and data storage devices.

U
4.0.2
M

Shall be local server-based with a network accessible system.

U
4.0.3
M

Shall provide the ability to ingest, manage, and process interviews simultaneously from multiple interview rooms.

U
4.0.4
M

Shall have a minimum local storage capacity of 12 hours of interview room data per day for 30 days.

U
4.0.5
M

The system shall be designed to provide failover and/or redundancy or other features to minimize the chance for recording failure.

U
4.0.6
M

Shall operate on standard 120VAC power and be resistant to power fluctuations.

U
4.0.7
O

Backend server should fit in a standard server rack.

U
4.1
M

Network Interface

U
4.1.1
M

Shall support IPv4 and IPv6.

U
4.1.2
M

Shall support connectivity to the local network at the installation site.

U
4.1.2.1
O

Should support Fast EN-100Base-FX.

U
4.1.2.2
O

Should provide media converters (devices to convert Ethernet to fiber) to extend hardware over the local network, if native support for connection to the local network does not exist.

4.2

Monitors

U
4.2.1
M

Shall support a minimum 1024x768 resolution, or greater,

U
4.2.2
M

Shall support 400:1 contrast ratio, or greater,

U
4.2.3
M

Shall support 16ms response time, or faster,

U
4.2.4
O

Should support 60 frames per second,

U
4.2.5
M

Shall support Stereo sound speakers, PIRS

U
5.0
M

PIRS Functionality

U
5.0.1
O

Should have a built in GPS that will record the location as metadata.

U
5.0.2
M

Shall have one-button recording with a visible indication that recording is in progress.

U
5.0.3
O

Visible recording indicator should be capable of being disabled.

U
5.0.4
M

Shall be capable of receiving two video streams and two separate audio streams (i.e. left and right channel).

U
5.0.5
O

Should be capable of using external cameras and microphones for recording.

U
5.0.6
O

Should only use hardware that is commercially available from multiple sources.

U
5.0.7
ME

Shall have the ability to create metadata to mark specific events during the recorded interview.

U
5.0.8
M

Shall store an evidence copy of the interview recording on PIRS storage.

U
5.0.9
ME

Shall store a working copy of the interview recording on PIRS storage.

U
5.010
ME

Shall allow no modifications to the file with the original evidence copy of interview video and audio--any editing to interview video shall saved as a separate and distinct working copy from the evidence file.

U
5.0.11
ME

Shall use a FIPS 202 compliant hash algorithm to generate a hash value stored with the original video/audio data to be used for authenticating that the video data has been unmodified.

U
5.0.12
M

Shall have a digital asset audit and tracking system.

U
5.0.13
M

Shall record video, audio, and metadata in a standard (container) format and codec. Acceptable standards are: (video) MP4, AVI, MKV, WMV, MJPEG, H.264, H.265, and (audio) WAV.

U
5.0.14
ME

Shall allow input and storage of case notes entered by an authorized user during an interview.

U
5.0.15
M

Shall support recording of video at a minimum frame rate of 30 unique images per second per camera with no dropped frames.

U
5.0.16
ME

Shall provide application programming interfaces, service programming interfaces, and/or software development kits to support integration with other systems.

U
5.0.17
O

Should combine the video streams, audio stream and any metadata into one progressive scan format digital video file.

U
5.0.18
M

Shall synchronize video streams, audio stream and any metadata to an accuracy of 33ms throughout the duration of the recording

U
5.0.19
O

Should have the capability for Video and Audio redaction (for both live and recorded data), to obscure faces or other visible objects, and mask audio that is not intended to be recorded.

U
5.0.19.1
O

Should allow the user to define a segment of the recording where the playback will be redacted.

U
5.0.19.2
O

Should blackout and skip redacted segments without altering the original audio/video.

U
5.0.20
M

Shall have a user interface that provides an onscreen time/date overlay on the video recordings.

U
5.0.21
O

Should have a user interface that allows display of additional configurable metadata field(s) [such as case id, room #, interviewer, …]

U
5.0.22
M

Shall have a user interface that is compliant with Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. Sect. 794(d)).

U
5.0.23
M

Shall have a user interface that allows a viewer to select which camera's video is to be displayed on the viewing console.

U
5.0.24
O

Should have the capability for a user to skip directly to marked events in the video and find specific metadata associated with that marked event.

U
5.0.25
ME

Shall have a secure client user interface that allows the user to monitor live interviews, including all audio, video, and internally generated metadata.

U
5.0.26
ME

Shall have a secure client user interface that allows the user to review recorded interviews, including all audio, video, and internally generated metadata.

U
5.0.27
ME

Shall have a secure client user interface that enables a user to view live interviews, and to mark events and enter metadata (including case notes).

U
5.0.28
ME

Shall have a secure client user interface that enables a user to view recorded interviews, and to mark events and enter metadata (including case notes).

U
5.0.29
M

Shall have a secure client user interface that supports Automatic Gain Control and Noise Reduction for clear audio playback.

U
5.0.30
M

Shall support administration of the PIRS system.

U
5.0.30.1
M

Shall support separate profiles for administrator access (system management) and end-user functions.

U
5.0.30.2
M

Shall implement administrative functions to grant user privileges, change user privileges (such as administrative rights and data access rights), and revoke user privileges and data access.

U
5.1
M

Audio Input

U
5.1.1
M

Shall provide a minimum of 16-bit PCM audio, and a minimum sampling rate of 11.025 kHz, producing an uncompressed linear pulse-code modulation .wav file

U
5.1.2
M

Shall have the capability of recording an audio frequency range of at least 100 Hz through 5 kHz +/- 6dB.

U
5.1.3
M

Metadata

U
5.1.4
ME

Shall have the ability to create metadata to mark specific events during the recorded interview.

U
5.1.5
ME

Shall have the ability to tag, associate, sort, and retrieve recorded evidence utilizing metadata.

U
5.1.6
ME

Shall place a digital tag/marker indicating placement of case notes.

U
5.1.7
ME

Shall have ability to search, display, and modify metadata, as required.

U
5.1.8
ME

Shall have the ability to pre-populate metadata fields such as room/location.

U
5.1.9
ME

Shall provide the ability to pre-populate metadata tags to mark events such as start of Miranda, Confession.

U
5.1.10
O

Should have the ability to accept metadata from other sources, such as GPS for location.

U
5.2
M

Power

U
5.2.1
M

Shall have an internal battery, providing minimum of 250 minutes of recording time.

U
5.2.2
O

Should support the ability to change batteries to increase recording time.

U
5.2.3
M

Shall support alternate power sources operating on 110VAC and 12V DC.

U
5.2.4
M

Shall have the ability to charge the battery while downloading data at a base location.

U
5.2.5
O

Should provide the capability to change the power source during recording without interruption.

U
5.2.6
M

Shall include cables required for use of alternate power sources supported by the system.

U
5.2.6
O

Should have an internal battery for safe shutdown in the event of an unexpected power interruption.

U
5.3
M

Data export

U
5.3.1
ME

Shall export audio separately/independently from video in the WAV format.

U
5.3.2
O

Should export audio separately/independently from video in additional formats, such as mp3, AIFF, PCM, or AAC.

U
5.3.3
ME

Shall export video separately/independently from audio using a standard format and codec, such as MP4, AVI, MKV, MOV, MJPEG, H.264, or H.265.

U
5.3.4
ME

Shall have the capability to export selected recordings and portions of recordings to removable media.

U
5.3.5
O

Should not require trans-coding of the original digital format to export data to removable media and/or storage associated with an enterprise solution.

U
5.3.6
O

Should be able to split a recording across multiple removable media in order to provide recording beyond the length of removable media.

U
5.3.7
O

Should have the ability to generate multiple removable media, each with its own unique labeling.

U
5.3.8
O

Should have the ability to verify the authenticity of a generated removable media recording.

U
5.3.9
ME

Shall support export of video and audio recordings with metadata in a standard video and audio format and codec, such as MP4, AVI, MKV, MOV, MJPEG, H.264, H.265, WAV, and AAC.

U
5.3.10
ME

Shall support export of video and audio recordings without case notes and manual markings in a standard video format and codec, such as MP4, AVI, MKV, MOV, MJPEG, H.264, H.265, WAV, and AAC.

U
5.3.11
O

Should be capable of exporting case notes and/or metadata with video and audio data.

U
5.3.12
O

Should be capable of exporting case notes and/or metadata without video and audio data.

U
5.4
M
Hardware
U
5.4.1
O

The set of PIRS components should be capable of fitting in a case with internal dimensions no larger than 16” x 20” x 8”.

U
5.4.2
M

Camera shall provide a minimum 720p 1280 x 720 image resolution with aspect ratio 16:9.

U
5.4.3
O

Should provide additional resolutions, including: 1080p, 1080i, or 720p.

U
5.4.4
M

Cameras shall have a sufficiently small form factor that they are capable of being concealed from view of the interview subject in a vehicle.

U
5.4.5
M

Shall have the ability to control camera settings for compression, color, brightness, sharpness, white balance, exposure control, exposure zones, backlight compensation, defogging, noise reduction, electronic image stabilization and text and image overlay from a computer on the same network as the camera.

U
5.4.6
O

Should provide cameras with variable focal capability.

U
5.4.7
M

Shall have controllable frame rate and bandwidth.

U
5.4.8
M

Shall use Variable Bit Rate (VBR) or Maximum Bit Rate (MBR) H.264.

U
5.4.9
O

Should support 0.04 lux, digital zoom.

U
5.4.10
M

Shall support 12 VDC and 110 VAC.

U
5.4.11
O

Should support DV Iris Vari-Focal Lens (2.9mm - 10mm F1.2).

U
5.4.12
O

Should support automatic gain control (AGC).

U
5.4.13
O

External microphones should be capable of being concealed in a vehicle.

U
5.4.14
M

Shall have an audio frequency response of at least 100 Hz through 5 kHz +/- 6dB.

U
5.4.15
M

Shall have WDR – dynamic capture of 70dB (minimum).

U
5.4.16
M

Shall use (directional, half-space microphone) or microphone that fully captures the voices of the people.

U
5.4.17
M

Microphone shall be enclosed in a housing.

U
5.4.18
M

Shall have a minimum internal storage capacity sufficient to hold 6 hours of video and audio recording.

U
5.4.19
O

Should have the capability to extend recording to removable storage, such as a USB drive.

Common Requirements for IRMS & PIRS

U
6.0

Security

U
6.1
M

Shall provide, at a minimum, Username/Password protection for access to the live video and camera setup via the network interface.

U
6.2
O

Should have the capability to manage access/authentication using Microsoft Active Directory.

U
6.3
M

Shall support the management of data access by cases and case assignments.

U
6.4
M

Shall allow data access to be granted to individual users or groups of users.

U
6.5
M

Shall maintain comprehensive chain of custody for all interview recordings and associated data.

U
6.6
ME

Shall validate the transfer of data from the server to any removable media (e.g., Blu-ray, DVD, USB) that is authorized for download and is supported by the hardware and operating system on which the system runs.

U
6.7
ME

Shall provide functionality to validate the integrity of the assets stored within the system as unchanged from original recordings.

U
6.8
O

Should allow a user, at the administrator level and/or the authorized user level, to input specific information required for the audit logs and system audit log.

U
6.9
M

Shall log all metadata changes, video recordings, and successful and unsuccessful recording modifications, deletions, and views.

U
6.10
M

Shall have an automated verification for the original data upon completion of the first instance recording.

U
6.10.1
ME

Shall use a FIPS 202 compliant hash algorithm to generate a hash value stored with the original video/audio data to be used for authenticating that the video data has been unmodified.

U
6.11
M

Shall not introduce any visible or audible artifacts into the data.

U
6.12
M

Shall not introduce any non-visible or non-audible artifacts into video or audio data.

U
6.13
M

Shall have built-in encryption support for AES-256-CTR.

U
6.14
M

Shall have built-in encryption support for 1024-bit Diffie-Hellman Key Exchange,

U
6.15
M

Shall have built-in encryption support for SHA-3-HMAC for data transmission,

U
6.16
M

Shall have built-in encryption support for 512-bit RSA key pairs for server identification.

U
6.17
ME

Shall encrypt data at rest and in transit in compliance with FIPS 140-2 Level 1.

U
6.18
M

Shall capture and store audit information.

U
6.18.1
M

Shall provide an audit log that captures user-entered details on specific cases (user name, room, case number, subject's name, names of people in the room).

U
6.18.2
M

Shall provide an audit log that automatically captures details (such as date, room number, start time, stop time, pauses).

U
6.18.3
M

Shall provide an audit log that captures reviewer information (name, time, date, location).

U
6.18.4
M

Shall provide an audit log that captures changes in metadata (change, name, time, date, location).

U
6.18.5
M

Shall provide an audit log of administrative activities of system (name, time, date, system up/down/reboot, system patches, system adds/deletes/changes).

U
6.18.6
M

Shall retain the audit log on-line on the operational system for a period of 90 days.

U
6.18.7
O

Should support the ability to transfer audit log materials to a centralized audit repository.

image1.png

File details come from the government source that posted it. Updated .