Exhibit_B_IDS_Hardware_Specifications_REV1.xlsx
XLSX spreadsheet 31 KB Posted
- Attached to
- IDS Technical Refresh
- Solicitation number
- N0017818R4017
About this file
This document contains technical specifications for an Identity Dominance System (IDS) hardware device. The specifications include over one hundred requirements across various categories such as physical size, computing platform, screen, biometric sensors, environmental ruggedness, and reliability. Key requirements include support for Android 7 or newer, a minimum 4-core 2.45GHz processor, 4GB RAM, fingerprint and iris sensors meeting certain standards, drop and vibration resistance per MIL-STD-810G, and a targeted operational availability of 97% or higher. The related federal contract opportunity notice seeks proposals to update and support IDS technology through its lifecycle via a single-award IDIQ vehicle with cost-plus-fixed-fee and firm-fixed-price contract line items. The solicitation is expected to be issued on August 14, 2018 by the Naval Surface Warfare Center Dahlgren Division.
Specifications
View the file
Other files
| File | Type | Posted |
|---|---|---|
| N0017818R4017_REV2.pdf | ||
| J1_DO1_SOW_Rev2.pdf | ||
| J2_ACTION_SHEET_DO_0001_REV1.pdf | ||
| N0017818R4017_REV1.pdf | ||
| J1_DO1_SOW_Rev1.pdf | ||
| J3_DO_1_CDRLs.pdf | ||
| ExhibitA_IDIQ_CDRL.pdf | ||
| J6_StaffingMatrix.xlsx | XLSX spreadsheet | |
| IDS_RFP.pdf | ||
| J2_ACTION_SHEET_DO_0001.pdf | ||
| J5_SUPPORTING_COST_DATA.pdf | ||
| Exhibit_B_IDS_Hardware_Specifications.xlsx | XLSX spreadsheet | |
| J1_DO1-S.PDF | ||
| J4_COSTS.XLS | XLS spreadsheet |
Show all 14
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| Category | Number | Reqt Name | Reqt Description | Rationale |
| Physical Size | PH.01 | Device Hardware - Weight | The hardware device shall weigh less than 5 lbs. The device weight includes the hardware device plus any batteries needed for its operation; it does not include the case the device is stored in. | |
| Physical Size | PH.02 | Device Hardware - Weight [O] | The hardware device shall weigh less than 2 lbs. The device weight includes the hardware device plus any batteries needed for its operation; it does not include the case the device is stored in. | |
| Physical Size | PH.03 | Device Hardware - Volume | The hardware device shall have a maximum volume of 170 cubic inches in its storage configuration. Volume should be measured as the product of the greatest of each length, width, and height. | The device should be able to be carried outside of its storage container in a carrying pouch or pocket. |
| Physical Size | PH.04 | Device Hardware - Dimension | The hardware device maximum measurement in any one dimension shall be less than 12 inches. | The device should be able to be carried outside of its storage container in a carrying pouch or pocket. |
| Cyber Security | CS.01 | BIOS | The hardware device shall comply with NIST SP 800-147 Basic Input/Output System (BIOS) Protection Guidelines and SP 800-155 BIOS Integrity Measurement Guidelines. | Design needs to adhere to DoD CIO Memo NII001001 8 Sept 2011 "Implementation of BIOS Protection Guidelines". |
| Cyber Security | CS.02 | Public Key Infrastructure | The hardware device shall support the implementation Federal Information Processing Standard (FIPS) 201-2 compliant credentials including derived credentials as described in NIST Special Publication 800-157. | Design needs to adhere to DoD CIO Memorandums: DoD Interim Guidance for Implementing Derived Public Key Infrastructure (PKI) Credentials on Unclassified Commercial Mobile Devices 20150506 and DoD Interim Guidance on the Use of DoD Personal Identity Verification Derived Public Key Infrastructure Credentials on Unclassified Commercial Mobile Devices 20140924 |
| Cyber Security | CS.03 | Cryptography | The hardware device shall securely store and generate approved FIPS 140-1 and 140-2 cryptographic keys and modules. | Android supports whole disk and file folder encryption, secure boot modes, trusted execution, etc. and with hardware support for the encryption it is much faster and more secure than software based solutions. These modules also support SLL, HTTPS, and other end-to-end communications encryption schemes. |
| Cyber Security | CS.04 | Data at Rest | The hardware device shall support the storage and transfer of digital information with password protection and encryption using FIPS140-2 approved encryption. | See DoD CIO Memorandum Encryption of Sensitive Unclassified Data at Rest on Mobile Computing Devices and Removable Storage Media 20070703. The entire hardware device and any related storage media must be encrypted and protected. |
| Computing Platform | CP.01 | Operating System Support | The hardware device shall support Android 7 (API 25) or newer. | |
| Computing Platform | CP.02 | GPU OpenGL | The hardware device shall utilize a Graphics Processing Unit (GPU) that supports OpenGL ES 3.2 or newer | |
| Computing Platform | CP.03 | Built in Tests | The hardware device components shall support communicating diagnostic and status information. | The system software will require a method for communicating with the sensors and internal components to determine what is connected and functional and what is non-operable. This information can then be provided to the system operators. |
| Computing Platform | CP.04 | Permanent Storage (Solid-State) | The hardware device permanent storage shall be solid-state. | |
| Computing Platform | CP.05 | Permanent Storage Type | The hardware device permanent storage shall be a minimum of Universal Flash Storage (UFS 2.0) or equivalent. The device's internal storage will be considered equivalent to UFS 2.0 if it meets or exceeds the performance of other UFS 2.0 storage devices. | |
| Computing Platform | CP.06 | Permanent Storage - Minimum Size | The device shall have a minimum of 64GB of permanent storage. Permanent storage is the storage inherent to the primary computing platform. | |
| Computing Platform | CP.07 | Semi-Permanent Storage | Non-specialized tools shall be required to access the semi-permanent storage. | The semi-permanent storage is meant to provide a cost effective means of replacing the storage once it fails. It is not intended to be removed frequently. |
| Computing Platform | CP.08 | Semi-Permanent Storage - Minimum Size | The device shall have a minimum of 64GB of semi-permanent storage. Semi-permanent storage is storage that is integrated into the hardware device, but can be replaced separately. | The semi-permanent storage is meant to provide a cost effective means of replacing the storage once it fails. It is not intended to be removed frequently. |
| Computing Platform | CP.09 | Semi-Permanent Storage Read Speed | The semi-permanent storage shall have a sequential read speed of 160 MB/s or higher. | |
| Computing Platform | CP.10 | Semi-Permanent Storage Write Speed | The semi-permanent storage shall have a sequential write speed of 155 MB/s or higher. | |
| Computing Platform | CP.11 | Removable Storage Port | The hardware device shall transfer data via external media conforming to Secure Digital (SD) standards. | A removable storage port provides a simple and effective means for transferring data onto or off of the device. |
| Computing Platform | CP.12 | RAM Size | The device shall have a minimum of 4GB of Random Access Memory (RAM). | |
| Computing Platform | CP.13 | RAM Type | The device shall utilize DDR4 or LPDDR4 or newer standard. | |
| Computing Platform | CP.14 | RAM Transfer Rate | The device shall utilize RAM that operates at 3200 MT/s or greater. | |
| Computing Platform | CP.15 | CPU Instruction Set | The hardware device shall utilize a Central Processing Unit (CPU) that uses the ARMv8-A architecture or a newer 64 bit ARM architecture. | ARM architecture is currently utilized in listed DoD Approved Products (Mobile). The Trustzone architecture is used extensively for security and secure processing in mobile architectures when using Android Operating System (OS). Expectation is that ARM with Trustzone will continue to be on the DoD APL and will meet Common Criteria Protection Profile for Mobile Devices. |
| Computing Platform | CP.16 | CPU Number of Cores | The hardware device shall have a CPU with a minimum of 4 cores | |
| Computing Platform | CP.17 | CPU Clock Rate | The hardware device shall have a CPU that operates at a minimum of 2.45 GHz. | |
| Computing Platform | CP.18 | CPU Architecture | The hardware device shall have a 64 bit processor architecture. | |
| Computing Platform | CP.19 | USB Communication | The hardware device shall communicate to external devices using serial communications conforming to Universal Serial Bus (USB) standards. | USB connections will provide the flexibility to add peripherals to the system to increase capability as required. |
| Computing Platform | CP.20 | Serial Communication | The hardware device shall communicate via the ANSI/EIA-232/422 standards. This functionality can be provided by a USB dongle. | The device needs to support interfacing with radios that only have ANSI/EIA-232/422 communication capabilities. |
| Computing Platform | CP.21 | Net Ready Wired | The hardware device shall have an internal RJ-45 interface with duplex Institute of Electrical and Electronics Engineers (IEEE) 802.3x compatibility. |
The ability for the device to connect to a network or tactical IP radio (RJ45 port or USB adapter) is critical to support operations mission.
| Computing Platform | CP.22 | NET Ready Cell | The hardware device shall be capable of Global System for Mobile Communications (GSM) and Long Term Evolution (LTE) communications. | GSM and LTE have the largest supporting networks world-wide. |
| Computing Platform | CP.23 | Wireless Standards | The hardware device shall support IEEE 802.11 a, b, g, n, ac wireless protocols. | The protocol in use by the network the system will connected to could vary, so the system should support all common protocols. |
| Computing Platform | CP.24 | Bluetooth Connectivity | The hardware device shall support Bluetooth 4.1 protocol or greater. | |
| Computing Platform | CP.25 | Interface Disable | The hardware device shall provide appropriate enable/disable functions of external communications interfaces. | Operational requirements in Electronic Warfare (EW) environments require the shutdown of wireless communications (airplane mode). External ports that transmit or receive data via serial, parallel and bus interfaces, regardless of I/F type, should require specific operator or OS actions to enable them when in use and disable them when not. All interfaces have a hardware component, that at the BIOS level, can provide for this function at the OS or application level. Disabling external interfaces reduces the likelihood of I/F attack vectors used to gain access to the device. |
| Computing Platform | CP.26 | GPS | The hardware device shall acquire geo-location data from an internal Global Positioning System (GPS). | Rationale: Reduces user workload and |
improves accuracy of mission-related geolocation information.
| Computing Platform | CP.27 | GPS Disable | The hardware device shall support disabling the GPS module. | The GPS device should remain disabled until required to maximize system battery life. |
| Computing Platform | CP.28 | Computing Platform Security | Removal of the computing platform from the hardware device shall require the use of non-specialized tools. | The computing platform needs to be removable and replaceable. However, for device and data security its removal from the hardware device should require the use of standard electronics tools. |
| Screen | SC.01 | Touchscreen - Hardware Integration | The hardware device shall implement a touch sensitive screen. | |
| Screen | SC.02 | Touch Screen Protection | The hardware device shall protect the touch screen from damage when not in use. | When the device is outside of its storage case, but not in use, the touch screen needs to be protected to prevent damage due to impact or abrasion. |
| Screen | SC.03 | Impact Resistant Screen | The hardware device touch screen shall be impact resistant. | |
| Screen | SC.04 | Hardware Device Touch Screen | Hardware device touch screen shall be designed in accordance with MIL-STD-1472G section 5.1.3.1.1 (Use), 5.1.3.1.2 (Luminance transmission), 5.1.3.1.4 (Display Response Time (Latency)), 5.1.3.1.5 (Impact on Visual Display), and 5.1.3.1.8 (Sensitivity). | |
| Screen | SC.05 | Hardware Device Touch Screen Color | The hardware device touch screen shall support 24-bit color. | A 24-bit color screen provides 256 intensity levels (or 8-bits) in each of the three primary colors (R, G, B), allowing for presentation of color imagery and use of color coding to improve legibility/readability of information presented on the screen. |
| Screen | SC.06 | Hardware Device Touch Screen Refresh Rate | The hardware device touch screen shall provide a flicker free display in accordance with MIL-STD-1472G section 5.2.1.1.4 (Preventing flicker of electronic visual displays). | |
| Screen | SC.07 | Hardware Device Touch Screen - Sensitivity Adjustment | The hardware device touch screen shall support adjustable touch sensitivity. | |
| Screen | SC.08 | Touchscreen - Size | The hardware device screen shall be of a minimum size of 5.1" diagonal. | It is important for the device screen to be of a sufficient size for easy operation and visibility and legibility of presented information (e.g. being able to use a virtual, QWERTY keyboard, utilizing touch screen operations, visibility and legibility of information presented on the screen to operator). |
| Screen | SC.09 | Hardware Device Touch Screen - Pixel Density | The hardware device touch screen shall have a minimum pixel density of 300 Pixels per inch (PPI). | The screen pixel density must allow for legibility/readability of information presented on the screen. |
| Screen | SC.10 | Hardware Device Touch Screen Luminance Adjustability | The hardware device touch screen shall support adjustable luminance control. | Hardware device touch screen luminance must be adjustable with a large enough range to allow the operator to adjust the display's luminance or brightness for better legibility/readability under various lighting conditions. MIL-STD-1472G in section 5.2.1.3.1 specifically states: "Luminance range of a display. The display luminance adjustability (highest to lowest) range shall be not less than 50:1." |
| Screen | SC.11 | Touchscreen - Data Entry Aid | The hardware device shall implement a physical data entry aid for directly interacting with the touch screen. | A physical data entry aid such as a stylus (or a part similar in size and operation to a stylus) must be available to the operator. The data entry aid will be especially useful to the operator when wearing standard issue gloves, which are not touch sensitive. |
| Screen | SC.12 | Touchscreen - Data Entry Aid Tethering | The physical data entry aid for the touch screen shall be tethered to the hardware device to avoid loss of the aid. | |
| Screen | SC.13 | Touch Screen Data Entry Aid Gloved Usage | The physical data entry aid for the touch screen shall be usable by the operator while wearing standard issue gloves. | Standard issue gloves are not touch sensitive, hence the gloved operator must be able to use the data entry aid to interact with the touch screen. |
| Screen | SC.14 | Hardware Input Methods - Alternate Devices | The hardware device shall have methods of input other than the touch screen. | In the event that the touch screen cannot be used as the main mode of data entry (due to screen damage or system movement or vibration), an external keyboard, for example, must be available to the operator for data entry to allow mission continuation and completion. This could also be accomplished through an integrated cursor control or onboard mouse. Furthermore, MIL-STD-1472G, under the section titled "Touch-screen controls for displays" (5.1.3.1 & 5.1.3.1.1) states: "A touch-screen shall not be the sole input means if system movement or vibration degrades user performance below the level required for mission accomplishment". |
| HSI | HS.01 | Haptic Confirmation | The hardware device shall support haptic feedback to the operator. The haptic feedback level must be such that it is felt by the operator while wearing standard issue gloves. | |
| HSI | HS.02 | Haptic Confirmation - Vibration Intensity Adjustment | The hardware device's haptic feedback intensity shall be adjustable. | The intensity of the haptic feedback must be software adjustable to allow for custom operator settings. |
| HSI | HS.03 | Haptic Confirmation - Vibration Duration Adjustment | The hardware device's haptic feedback duration shall be adjustable. | The intensity of the haptic feedback must be software adjustable to allow for custom operator settings. |
| HSI | HS.04 | Aural Confirmation | The hardware device shall include a speaker to support aural feedback to the operator. | |
| HSI | HS.05 | Aural Confirmation - Volume Adjustability | The hardware device's aural feedback shall be adjustable. | |
| HSI | HS.06 | Hardware Device Mechanical Controls | The hardware device mechanical controls shall be designed in accordance with MIL-STD-1472G. Hardware device mechanical controls include switches, knobs, push buttons, etc., but not the touch screen. | |
| HSI | HS.07 | Hardware Device Mechanical Controls - Gloved Usage | The hardware device mechanical controls shall be usable by the operator while wearing standard issue gloves. Hardware device mechanical controls include switches, knobs, push buttons, etc., but not the touch screen. |
HSI HS.08 Design Simplicity - Hardware Device Powering The hardware device shall be powered on by a single operator action.
| To improve ease of use, the design of the hardware device needs to include the provision for a single button (or something analogous to a single button) to bring the device to an operational state. | ||||
| HSI | HS.09 | Startup Time | The hardware device shall boot up in less than 1.0 minutes. Boot up is defined as the time from pressing the power button until when the user login screen is reached. | The hardware device shall meet this requirement with the installed Android operating system. This supports a system requirement to setup operations in 5 minutes. |
| HSI | HS.10 | Design Simplicity - Hardware Device Shut Down | The hardware device shall provide the operator with the functionality to perform a physical hard shut down of the device. |
| To improve ease of use, the design of the hardware device must include a physical means to allow the operator to perform a hard shutdown of the device. | ||||
| HSI | HS.11 | Design Simplicity - Hardware Device Shut Down Design | The physical hard shut down functionality of the hardware device shall be designed to minimize inadvertent device shut down. | |
| The physical hard shut down of the device shall not be achieved by a single operator action to avoid unintentional shut down by the operator. | ||||
| HSI | HS.12 | Hardware Device - Cable Labels | Each cable associated with the hardware device operation shall be labeled in clear and legible English so that the operator knows that it belongs with the hardware device and its function and connection point. | The cables associated with the hardware device operation shall be clearly labeled to minimize operator errors. |
| HSI | HS.13 | HW - Prevent Entanglements | The hardware device shall be designed to prevent entanglement to personnel in accordance with MIL-STD-1472G section 5.8.6.2.5.d. | |
| HSI | HS.14 | HW - Prevent Injury | The hardware device shall be designed to minimize projections to prevent injury to personnel in accordance with MIL-STD-1472G section 5.8.6.2.5.e. | |
| Power | PW.01 | Rechargeable Battery Power | The hardware device shall be able to operate on rechargeable battery power. | |
| Power | PW.02 | Battery Safety | The hardware device shall comply with the battery safety policies in NAVSEA Technical Manual S9310-AQ-SAF-010 and NAVSEAINST 9310.1C. | The hardware device must adhere to the safety policies in NAVSEA Technical Manual S9310-AQ-SAF-010 and NAVSEAINST 9310.1C if lithium batteries are requried to meet specifications. |
| Power | PW.03 | Battery Operating Time | The hardware device shall be capable of operating from rechargeable battery power continuously for a minimum of 6.0 hours at 40 °F +/- 3.6 °F. | The system requires the ability to continuously conduct standard enrollment operations for 6 hours on a fully charged battery. The operational length can be met with the use of a single hot-swap battery change. This assumes one complete biometric enrollment, fingerprints, irises, and mugshots, every 15 minutes. |
| Power | PW.04 | Battery Hot-Swap | The hardware device shall provide the ability to perform hot-swap battery changes without connecting to the external power supply. This swap should be possible without the use of tools. | Battery changes should be possible mid-enrollment without powering off the hardware device and without the risk of data loss. |
| Power | PW.05 | Device Hardware - Operation During Charge | The hardware device shall be able to simultaneously charge the battery while communicating with external devices (via USB). | The device must allow for as many USB ports as necessary to charge the battery while at the same time perform any operation that may require the device to connect via USB to another device, such as a CD/DVD player used to transfer collected information from the device. |
| Power | PW.06 | Powering External Devices | When operating on battery power, the hardware device shall be capable of powering external devices while communicating with them using serial communications conforming to USB standards. | Supports data transfer via USB media devices including CD/DVD-ROM drives, flash drives, and hard drives. Reduces overall kit size and increases portability by eliminating need for additional power connections. |
| Power | PW.07 | Device Hardware - Charge | The hardware device shall remain fully functional while being charged. | Completion of the mission must not be hindered by the hardware device's power life while the hardware device is being charged. |
| Power | PW.08 | UL Power Supply Standards | The hardware device power supply shall be Underwriters Laboratory (UL) Listed, meeting the standards set forth in the UL 60950-1 standard for power supplies of information technology equipment. | The power supply must be suitable for safe usage by the operator and be capable of certification to bring aboard a ship. |
| Power | PW.09 | Power Supply Input Voltage | The hardware device power supply shall support an input voltage range of 110-125 VAC. | |
| Facial Collection/Camera | FC.01 | Facial Image Capture | The hardware device color camera shall digitally capture facial images (mugshots). | |
| Facial Collection/Camera | FC.02 | Camera Auto-Focus | The hardware device color camera shall provide auto-focus capability. | Rationale: The user should be able to capture mugshots at a variety of distances without having to manually adjust the focus of the camera. |
| Facial Collection/Camera | FC.03 | Camera Lighting Conditions | The hardware device color camera shall support digital capture of images in all expected ambient lighting conditions. | Expected ambient lighting conditions range from direct sunlight to complete darkness. |
| Facial Collection/Camera | FC.04 | Biometric Image Capture Direct Sunlight | The hardware device shall capture quality digital images in direct sunlight. The captured images need to be sufficient quality to support accurate matching. | |
| Facial Collection/Camera | FC.05 | Camera Illumination Automatic | The hardware device color camera shall support automatic illumination in low light conditions. | |
| Facial Collection/Camera | FC.06 | Camera Illumination Manual | The hardware device color camera shall support operator controlled illumination during digital capture of images. | |
| Facial Collection/Camera | FC.07 | Eye Safety (Visible) | The hardware device's visible illumination shall be Class 1 in accordance with International Electrotechnical Commission (IEC) 825-1 and IEC 60825-1. | The visible illumination used during facial image collection (i.e., the flash) should not pose a safety hazard. |
| Facial Collection/Camera | FC.08 | Facial Image Capture Range | The hardware device shall support digital capture of facial images at a minimum range of 3.0 feet. | |
| Facial Collection/Camera | FC.09 | Facial Image Capture Standards | The hardware device color camera shall support digital capture of facial image in accordance with the quality standards documented in the Department of Defense (DoD) Electronic Biometric Transmission Specification (EBTS) v4.0. | |
| Facial Collection/Camera | FC.10 | Camera Sensor Response Time | The hardware device color camera shall support the digital capture of an image in less than 2.0 seconds. The response time is measured from the time the camera is activated to the time the image is provided to the software. | Images must be captured in a timely manner to meet overall mission timing requirements and to ensure that blurring doesn’t occur from movement within the image. |
| Facial Collection/Camera | FC.11 | Camera - Placement (Facial Image Capture) | The color camera shall be placed to allow the operator to capture the facial image while viewing the user interface at the same time. | |
| Facial Collection/Camera | FC.12 | Facial Camera Protection | The hardware device shall protect the color camera from protection when not in use. | When the device is outside of its storage case, but not in use, the color camera needs to be protected to prevent damage due to impact or abrasion. |
| Facial Collection/Camera | FC.13 | Camera Resolution | The hardware device color camera shall capture pictures with a minimum resolution of 8 Megapixels (MP). | This sensor resolution supports the implementation of Optical Character Recognition (OCR) on captured imagery, such as the Machine Readable Zone (MRZ) on passports. |
| Fingerprint Collection/Sensor | FP.01 | Fingerprint Capture | The hardware device shall include a fingerprint sensor that meets, at a minimum, Fingerprint Acquisition Profile (FAP) 45. | |
| Fingerprint Collection/Sensor | FP.02 | Flat Fingerprint Capture | The hardware device shall digitally capture flat fingerprints. | |
| Fingerprint Collection/Sensor | FP.03 | Rolled Fingerprint Capture | The hardware device shall digitally capture single rolled fingerprints. | |
| Fingerprint Collection/Sensor | FP.04 | Four-Finger Slap Fingerprints Capture [O] | The hardware device shall digitally capture four finger slap fingerprints. | The 10-print card requires the four flat fingerprints as one image. The preference is to create this from one image rather than stitching from multiple images. |
| Fingerprint Collection/Sensor | FP.05 | Fingerprint Capture Standards | The hardware device shall digitally capture fingerprint images at the quality standards governed by the DoD EBTS v4.0. | |
| Fingerprint Collection/Sensor | FP.06 | Flat Fingerprint Capture Speed | The hardware device shall digitally capture single flat fingerprints in less than 2.0 seconds. The response time is from when the finger is physically placed on the platen until the image is provided to the software. | |
| Fingerprint Collection/Sensor | FP.07 | Rolled Fingerprint Capture Speed | The hardware device shall digitally capture single rolled fingerprints in less than 2.0 seconds. The response time is from when the finger is physically placed on the platen until the image is provided to the software. | |
| Fingerprint Collection/Sensor | FP.08 | Two-Finger Slap Fingerprints Capture Speed | The hardware device shall digitally capture two-finger slap fingerprints in less than 2.0 seconds. The response time is from when the finger is physically placed on the platen until the image is provided to the software. | |
| Fingerprint Collection/Sensor | FP.09 | Multi-Finger Slap Fingerprints Capture Speed [applicable only if FP.04 is met] | The hardware device shall digitally capture four-finger slap fingerprints in less than 2.0 seconds. The response time is from when the finger is physically placed on the platen until the image is provided to the software. | |
| Fingerprint Collection/Sensor | FP.10 | Maximum Safe Current (DC) | The hardware device shall limit the Direct Current (DC) current passing through the subject's finger to a maximum of 15 mA when collecting fingerprints. | According to MIL-STD-1472G, 5.7.9.1.1, Table XXXIII, this is the limit before the current affects human reflexes. The intent is to minimize subject discomfort during fingerprint collection if the fingerprint sensor requires the use of current flow through the finger to achieve functionality. |
| Fingerprint Collection/Sensor | FP.11 | Maximum Safe Current (AC) | The hardware device shall limit the Alternating Current (AC) current passing through the subject's to a maximum of 4 mA when collecting fingerprints. | According to MIL-STD-1472G, 5.7.9.1.1, Table XXXIII, this is the limit before the current affects human reflexes. The intent is to minimize subject discomfort during fingerprint collection if the fingerprint sensor requires the use of current flow through the finger to achieve functionality. |
| Fingerprint Collection/Sensor | FP.12 | Fingerprint Sensor - Placement (Required Fingerprints) | The placement of the fingerprint sensor shall support the ability of the operator to collect the required fingerprints. | The hardware device components, to include biometric sensors, should not interfere with the collection of any biometric modality; placement should not impede the collection of biometrics. Placement is defined as the physical location of the biometric sensor on the hardware device in relation to all other hardware components (i.e. screen, other sensors, keyboard, buttons, etc...). This requirement does not preclude the ability to use multiple sensors to collect rolled and flat fingerprints. However, sensor placement must not prevent the ability of the device from capturing both types of fingerprints. |
| Fingerprint Collection/Sensor | FP.13 | Fingerprint Sensor - Placement (Cooperative Subjects) | The hardware device design shall permit the operator to obtain rolled and flat fingerprints while keeping device stationary and maneuvering the subject's fingers. | This is normal, expected operations for biometrics collection equipment. It is included as related to the requirement Fingerprint Sensor - Placement (Uncooperative Subjects) as the device must support both approaches. |
| Fingerprint Collection/Sensor | FP.14 | Fingerprint Sensor - Placement (Uncooperative Subjects) | The hardware device design shall permit the operator to obtain required fingerprints while keeping the subject's fingers stationary and maneuvering the device when necessary. | The device will be utilized in areas where individuals encountered may not be cooperative and the need for situational awareness must be supported by equipment used in biometric collection. |
There will be a need to fingerprint uncooperative subjects who may have their hands secured (such as with handcuffs), which will dictate the ergonomics, or efficiency, of the fingerprint capture.
| Fingerprint Collection/Sensor | FP.15 | Fingerprint Sensor - Placement (Location) | The fingerprint capture sensor shall be placed such that the operator can view the fingerprint platen and user interface at the same time. | |
| Device hardware should support the collection of a biometric so that the operator can simultaneously view the physical collection of the biometric along with the virtual, or software GUI image, being collected of that biometric. | ||||
| Iris Collection/Sensor | FP.16 | Fingerprint Sensor Protection | The hardware device shall protect the fingerprint sensor from damage when not in use. | When the device is outside of its storage case, but not in use, the fingerprint sensor needs to be protected to prevent damage due to impact or abrasion. |
| Iris Collection/Sensor | IR.01 | Iris Camera Resolution | The hardware device shall be able to capture iris images with a resolution of 640x480. | The hardware device to provide an image that can be stored in the Iris Storage Format (ISF) 2 format. |
| Iris Collection/Sensor | IR.2 | Iris Camera Color (Grayscale) | The hardware device shall capture iris images in grayscale with a minimum of 8 bits per pixel. | |
| Iris Collection/Sensor | IR.3 | Iris Acquisition Profile | The hardware device shall capture iris images at a minimum Iris Acquisition Profile (IAP) of IAP 20. | |
| Iris Collection/Sensor | IR.4 | Simultaneous Iris Image Capture[O] | The hardware device shall be able to capture digital images of the left and right irises simultaneously. | In order to capture both irises at the same time, there needs to be multiple iris sensors, or one sensor capable of imaging both irises at the same time. For mobile applications, both images should be captured simultaneously or quasi-simultaneously. This reduces the possibility of mislabeling of the individual images (right or left). It also allows for more accurate estimation of the roll angle and potentially higher accuracy and comparison speed. (ANSI/NIST-ITL 1-2011: UPDATE 2015) |
| Iris Collection/Sensor | IR.5 | Iris Capture Distance | The hardware device shall capture iris images at a minimum distance of 100 mm. | In order to be considered acceptable as non-intrusive and to avoid excessive geometric distortion, the minimum distance between the mobile iris capture device’s lens and the subject’s eye must be at least 100 millimeters. (ANSI/NIST-ITL 1-2011: UPDATE 2015) |
| Iris Collection/Sensor | IR.6 | Iris Image Capture Stabilization [O] | The hardware device shall provide image stabilization features during iris image capture. | |
| Iris Collection/Sensor | IR.7 | Iris Image Vertical Margins | The hardware device shall capture iris images with minimum vertical margins of 20% the radius of the iris. | In order to provide an acceptable level of usability and ease of alignment, the camera must allow for some variability in the position of the iris center relative to the camera. This is consistent with the ISO/IEC 19794-6, ISO/IEC 29794-6 and ANSI/NIST-ITL 1-2011: UPDATE 2015 standards concerning image margin requirements and is required to support storage in the ISF 2 format. |
| Iris Collection/Sensor | IR.8 | Iris Image Horizontal Margins | The hardware device shall capture iris images with minimum horizontal margins of 60% the radius of the iris. | In order to provide an acceptable level of usability and ease of alignment, the camera must allow for some variability in the position of the iris center relative to the camera. This is consistent with the ISO/IEC 19794-6, ISO/IEC 29794-6 and ANSI/NIST-ITL 1-2011: UPDATE 2015 standards concerning image margin requirements and is required to support storage in the ISF 2 format. |
| Iris Collection/Sensor | IR.9 | Iris Capture Illumination | The hardware device shall be able to illuminate a subject's irises during iris image capture. | |
| Iris Collection/Sensor | IR.10 | NIR Illumination (700-900 nm) | The hardware device's iris illumination wavelengths shall have a minimum of 90% of energy within the 700-900 nm band. | This is the standard spectral band used for iris capture and matching as put forth in ANSI/NIST-ITL 1-2011: UPDATE 2015. |
| Iris Collection/Sensor | IR.11 | NIR Illumination (800-900 nm) | The hardware device's iris illumination wavelengths shall have a minimum of 35% of energy within the 800-900 nm band. | This is the standard spectral band used for iris capture and matching as put forth in ANSI/NIST-ITL 1-2011: UPDATE 2015. |
| Iris Collection/Sensor | IR.12 | Eye Safety (NIR) | The hardware device's Near Infrared (NIR) illumination shall be Class 1 in accordance with IEC 825-1 and IEC 60825-1. | The NIR illumination used during iris image collection should not pose a safety hazard. |
| Iris Collection/Sensor | IR.13 | NIR Camera | The hardware device shall digitally capture images with wavelengths in the 700-900 nm range. | This is the standard spectral band used for iris capture and matching as put forth in ANSI/NIST-ITL 1-2011: UPDATE 2015. |
| Iris Collection/Sensor | IR.14 | Iris Camera Response Time | The hardware device iris camera shall digitally capture an individual iris image in less than 2.0 seconds. The response time is measured from the time the iris camera is activated to the time the image is provided to the software. | Images must be captured in a timely manner to meet overall mission timing requirements. |
| Iris Collection/Sensor | IR.15 | Iris Sensor - Placement | The iris camera shall be placed to allow the operator to capture the iris image while viewing the user interface at the same time. | |
| Iris Collection/Sensor | IR.16 | Iris Sensor - Capture Aid | The hardware device shall shade the subject's eyes from ambient lighting during iris capture. | The device needs to be designed so that during an iris capture, ambient lighting is limited, preventing a poor quality iris image capture due to the subject squinting from the lighting in the environment. |
| Iris Collection/Sensor | IR.17 | Iris Capture Alignment Aid | The hardware device shall have a mechanical alignment aid that ensures the subject's iris is within the iris sensor's depth of field during iris capture. | In order to meet overall mission timing and quality requirements, it is necessary to be able to quickly and properly position the device to ensure the subject's iris(es) is in focus and ready for capture. |
| Iris Collection/Sensor | IR.18 | Iris Sensor Protection | The hardware device shall protect the iris sensor from damage when not in use. | When the device is outside of its storage case, but not in use, the iris sensor needs to be protected to prevent damage due to impact or abrasion. |
| Voice Collection/Microphone | VC.01 | Microphone [O] | The hardware device shall be able to record audio. Recorded audio must be in the range of human hearing and the microphone integration should ensure that the recorded audio is clear and not muffled. | The audio will be used for voice recognition (voice clips from the subject) for future matching. |
| Voice Collection/Microphone | VC.02 | Microphone Signal to Noise Ratio [O] | The hardware device shall record audio with a minimum of 10 dB signal to noise ratio. | |
| Voice Collection/Microphone | VC.03 | Audio Bit Depth [O] | The hardware device shall record audio at a minimum of 16 bits of information per sample. | This is a minimum requirement for voice recognition. |
| Voice Collection/Microphone | VC.04 | Audio Sample Rate [O] | The hardware device shall record audio at a minimum sampling rate of 16kHz | To achieve voice recognition, a sampling rate of 16kHz or higher is needed. |
| Environmental/ Ruggedness | EV.01 | System Ruggedness (Transit Drop) | The hardware device shall be capable of withstanding transit drop without operational or materiel degradation in accordance with MIL-STD-810G CN1, Method 516.7. | |
| Environmental/ Ruggedness | EV.02 | System Ruggedness (General Vibrations) | The hardware device shall be capable of withstanding general vibrations with respect to composite wheeled vehicle profile specified in accordance with MIL-STD-810G CN1, Method 514.7, Procedure 1. | |
| Environmental/ Ruggedness | EV.03 | System Ruggedness (Loose Cargo) | The hardware device shall be capable of withstanding loose cargo vibrations without operational or materiel degradation with respect to composite wheeled vehicle profile specified in accordance with MIL-STD-810G CN1, Method 514.7, Procedure 2. | |
| Environmental/ Ruggedness | EV.04 | System Water Resistance (Immersion) | The hardware device shall be waterproof in accordance with MIL-STD-810G CN1, Method 512.6. | |
| Environmental/ Ruggedness | EV.05 | System Buoyancy in Packaging | The hardware device shall be positively buoyant in seawater while in transport packaging. | |
| Environmental/ Ruggedness | EV.06 | System Water Resistance (Rain) | The hardware device shall be capable of withstanding rain without operational or materiel degradation in accordance with MIL-STD-810G CN1, Method 506.6. | |
| Environmental/ Ruggedness | EV.07 | Operating Humidity | The hardware device shall operate in 5% to 100% relative humidity in accordance to MIL-STD-810G CN1, Method 507.6. | |
| Environmental/ Ruggedness | EV.08 | Fluid Contamination | The hardware device shall maintain integrity after exposure to isopropyl alcohol without operational or materiel degradation in accordance with MIL-STD-810G CN1, Method 504.2. | |
| Environmental/ Ruggedness | EV.09 | Materiel Exposure to Salt-Water Spray/Fog | The system shall, with scheduled maintenance, be able to withstand exposure to salt-water spray/fog without operational or materiel degradation in accordance with MIL-STD-810G CN1, Method 509.6. | |
| Environmental/ Ruggedness | EV.10 | Materiel Exposure to Extreme Dust | The hardware device shall, with scheduled maintenance, be able to withstand exposure to extremely dusty/windswept environments without operational or materiel degradation, in accordance with MIL-STD-810G CN1, Method 510.6, Procedure 1 - Blowing Dust. | |
| Environmental/ Ruggedness | EV.11 | Materiel Exposure to Extreme Sand | The hardware device shall, with scheduled maintenance, be able to withstand exposure to extremely dusty/windswept environments without operational or materiel degradation, in accordance with MIL-STD-810G CN1, Method 510.6, and Procedure II - Blowing Sand. | |
| Environmental/ Ruggedness | EV.12 | Operating Temperatures | The hardware device shall be capable of operating from Cold (40° Fahrenheit [F]) to Hot (120°F) in accordance to MIL-STD-810G CN1, Method 502.6 and Method 501.6. | |
| Environmental/ Ruggedness | EV.13 | Operating Temperatures [O] | The hardware device shall be capable of operating from Cold (-5°F) to Hot (130°F) in accordance to MIL-STD-810G CN1, Method 502.6 and Method 501.6. | |
| Environmental/ Ruggedness | EV.14 | Storage Temperatures | The hardware device shall be capable of being stored in the temperature range of Basic Cold (-28°F) to Hot (160°F) in accordance with the MIL-STD-810G CN1, Method 502.6 and Method 501.6. | |
| Environmental/ Ruggedness | EV.15 | Materiel Exposure to Low Pressure | The hardware device shall be able to withstand exposure to low pressure during transit in accordance with MIL-STD-810G CN1, Method 500.6, Procedure 1. | |
| Environmental/ Ruggedness | EV.16 | Materiel Exposure to Ultraviolet Radiation | The hardware device shall, with scheduled maintenance, be able to withstand exposure to solar ultraviolet radiation without operational or materiel degradation in accordance with MIL-STD-810G CN1, Method 505.6. | |
| Environmental/ Ruggedness | EV.17 | Electromagnetic Environment | The hardware device shall be compatible with and operate in the electromagnetic environment in accordance with Military Standard (MIL-STD) 461G/464C. | |
| Environmental/ Ruggedness | EV.18 | Electromagnetic Environment Degradability | The hardware device shall maintain 100% operational functionality despite exposure to electromagnetic environmental effects, including high intensity radio frequency transmissions in accordance with MIL-STD- 461G/464C. | |
| Environmental/ Ruggedness | EV.19 | Electromagnetic (EM) Environment, Conducted Emissions (Power Leads) | The hardware device shall maintain operation despite exposure to Electromagnetic (EM) conducted emissions effects on power lines from 30 Hertz (Hz)-10 Megahertz (MHz) in accordance with MIL-STD-461G. | |
| Environmental/ Ruggedness | EV.20 | EM Environment, Conducted Susceptibility (Power Leads) | The hardware device shall maintain operation despite exposure to EM conducted susceptibility effects on power lines from 30 Hz-150 Kilohertz (kHz) in accordance with MIL-STD-461G. | |
| Environmental/ Ruggedness | EV.21 | EM Environment, Conducted Susceptibility (Transients) | The hardware device shall maintain operation despite exposure to EM conducted susceptibility transient effects on power leads in accordance with MIL-STD-461G. | |
| Environmental/ Ruggedness | EV.22 | EM Environment, Conducted Susceptibility (Bulk Cable Injection) | The hardware device shall maintain operation despite exposure to EM conducted susceptibility effects on bulk cable injection from 10 kHz-200 MHz in accordance with MIL-STD-461G. | |
| Environmental/ Ruggedness | EV.23 | EM Environment, Conducted Susceptibility (Damped Sinusoidal Transients) | The hardware device shall maintain operation despite exposure to EM conducted susceptibility effects via damped sinusoidal transients on cables and power leads from 10 kHz-100 MHz in accordance with MIL-STD-461G. | |
| Environmental/ Ruggedness | EV.24 | EM Environment, Radiated Emissions (Magnetic Field) | The hardware device shall maintain operation despite exposure to magnetic radiated emissions effects from 30 Hz-100 kHz in accordance with MIL-STD-461G. | |
| Environmental/ Ruggedness | EV.25 | EM Environment, Radiated Emissions (Electric Field) | The hardware device shall maintain operation despite exposure to electric radiated emissions effects from 10 kHz-18 Gigahertz (GHz) in accordance with MIL-STD-461G. | |
| Environmental/ Ruggedness | EV.26 | EM Environment, Radiated Susceptibility (Magnetic Field) - 30 Hz-100 kHz | The hardware device shall maintain operation despite exposure to magnetic radiated susceptibility effects from 30 Hz-100 kHz in accordance with MIL-STD-461G. | |
| Environmental/ Ruggedness | EV.27 | EM Environment, Radiated Susceptibility (Electric Field) - 2 MHz-40 GHz | The hardware device shall maintain operation despite exposure to electric radiated susceptibility effects from 2 MHz-40 GHz in accordance with MIL-STD-461G. | |
| Environmental/ Ruggedness | EV.28 | Electrostatic Charge Control | The hardware device shall comply with Electrostatic charge control designated in MIL-STD-464C section 5.8. | Voltages associated with static charging and energy released during discharges are potentially hazardous to personnel, fuel vapors, ordnance, and electronics. |
| Environmental/ Ruggedness | EV.29 | Hazards of Electromagnetic Radiation to Ordnance (HERO) Factors | Development of the hardware device shall follow Hazards of Electromagnetic Radiation to Ordnance (HERO) requirements in accordance with MIL-STD-464. | |
| Reliability | RL.01 | Operational Availability | The hardware device shall achieve an Operational Availability of 0.97 or greater, assuming a Mean Logistics Delay Time (MLDT) of 40 hours. | For this hardware device Ao shall be calculated using the following: |
Ao = Mean Time Between Maintenance (MTBM)/(MTBM+Mean Maintenance Time (MMT)+Mean Logistics Delay Time (MLDT))
MTBM represents the average time between all maintenance actions, both corrective and preventive. All preventive actions should be defined.
MMT represents item maintainability taking into account both preventive and corrective maintenance.
Reliability RL.02 Operational Availability [O] The hardware device shall achieve an Operational Availability of 0.99 or greater, assuming a Mean Logistics Delay Time (MLDT) of 40 hours. For this hardware device Ao shall be calculated using the following:
Ao = Mean Time Between Maintenance (MTBM)/(MTBM+Mean Maintenance Time (MMT)+Mean Logistics Delay Time (MLDT))
MTBM represents the average time between all maintenance actions, both corrective and preventive. All preventive actions should be defined.
MMT represents item maintainability taking into account both preventive and corrective maintenance.
| Reliability | RL.03 | Major Component Replacement | The device shall be designed such that each integrated major component is able to be removed and replaced separately from the remainder of the system. | This requirement is necessary in order to facilitate removal and replacement at the component level. This makes a two level maintenance concept with Operational level (O-level) and In Service Engineering Agent (ISEA-level) repairs possible in accordance with a Provisioning Parts List (PPL). The PPL will include all the parts that can be removed and replaced at the O-Level and the ISEA level. Examples are a battery at the O-Level and sensors or the computing platform in a hand-held hardware device at the ISEA level. More details are available in the SOW. |
| Notes: [O] in the Requirement name Column indicates that the Requirement is an Objective. Objective requirements will be considered in evaluations but they are significantly less important than cost. |
Exhibit B Identity Dominance System Hardware Specifications
Page &P of &N Unclassified / For Official Use Only
File details come from the government source that posted it. Updated .