The file's text, extracted by GovTribe without its formatting.
Instructions and Score Summary OSH Patient Biometric Monitoring Solution Requirements Scoring Matrix
| Worksheet Completion Instructions | |
| Proposer shall complete and submit an electronic version of this Requirements matrix to demonstrate how the proposed solution addresses the requirements. Please follow these instructions to complete the scoring matrix. | |
| 1 | ENTER Proposer's Name in cell B12 of this Instructions Tab. |
| 2 | INDICATE proposed solution type (e.g., SaaS, PaaS, IaaS, or On-Premise) in cell O12 of this Instructions Tab. |
| 3 | This workbook is arranged in three worksheets or Category Tabs: |
- Instructions and Score Summary (this tab)
- Functional Requirements
- Non-Functional Requirements 4 Proposer responses are recorded in columns E ("Response") and F ("Comments") in the Functional and Non-functional tabs. Only selections made in Column E will be scored.
For each Requirement line item in the Business and Technical tabs, Proposer:
a. SELECT ONE of the five Response Options from the drop down menu in Column E "Response." The codes in the drop-down list correspond to the codes described in the Code Table below, AND
b. IF Proposer desires, THEN ENTER brief comments in the corresponding Column F cell to support, explain, or clarify the code selected in Column E.
| The comments should succinctly describe how the proposed Solution will implement the requirement line item, especially where the required functionality DOES NOT "Currently Exist" in the general release version of the proposed Solution at the time of Offer submission. In any explanation provided, Proposer must describe how the proposed Solution addresses the required functionality, whether it requires custom code, and where custom code may be required. The explanation may also provide configuration alternatives or functionality to be developed. | | |
| 5 | ENSURE to provide a response and comments for each requirement line item. | Total number of requirements across the Category Tabs: | 62 |
| Proposers Name: | | | | | Indicate if this is a Saas, PaaS, IaaS or On-Premise System: | | | | | |
| Objective Score | | | | | | | | | | |
| Summary: | | Total Points | 0 | 0.0% | Must Have Requirements that are "S" standard functions | | 0 | 0.0% | Must Have Requirements in "B" Base Code or On Roadmap | 0 | 0.0% |
| | | | out of | | | | out of | | | out of |
| | | | 880 | | | | 56 | | | 56 |
| Requirements Category Tab Column | Explanation of Column | Code Table | | | |
| Column A | Requirement ID | Points | Response Code | Condition | Description |
| Column B | Requirement Area | 5 | S | Standard Function | The functionality described by the requirement currently exists in the proposed Solution with no additional configuration or cost. |
| Column C | Priority Rating (as determined by the Agency) | 4 | B | Base Code Configurable or On Roadmap | The functionality described in the requirement is: |
- Available in the proposed Solution by configuration of existing base code, OR
- On Solution Provider's product roadmap for general availability release within one year of RFP Release (ensure to include expected date of general availability)
| Column D | Requirement Description | 3 | C | Customization Required | The functionality would require modification to the Solution's underlying source code as part of the initial implementation and the functionality is not included on Solution's product roadmap. |
| Column E | Response Code (See table to right) | 2 | I | Third-Party Integration Required | The functionality is provided through the use of a separate software package(s). If third-party software is necessary to provide the functionality, please describe in Column F. |
| Column F | Proposer Comments | 0 | O | Cannot Fulfill Requirement | Proposed Solution does not provide the functionality and is not on product roadmap for release within one year of RFP Release. Proposer may provide alternative functional solutions in Proposer's Comments in Column F. |
| Column G | Auto Calculated Response Points | | | | |
| Column H | Auto Calculated Points | | | | |
| Column I | Maximum Points | | | | |
Functional Requirements
| Functional Requirements | | | | |
| Req # | Area | Priority | Requirement | Response |
(Please select from
| drop-down menu) | Comments | Auto Calculated Response Selection Points | Auto Calculated Points |
| (Response x Priority Rating) | Maximum Points | | |
(Priority Rating x Max Points)
| FR1 | Weapons Detection | | | |
| FR1.01 | Concealed Weapons | Must - 3 | Automatically detect concealed weapons on individuals and inside bags (e.g. backpacks, purses, briefcases). | 15 |
| FR1.02 | Weapon Types | Must - 3 | Detect firearms, knives, and Improvised Explosive Devices (IEDs) with metallic components. | 15 |
| FR1.03 | Benign Items | Must - 3 | Operate effectively without removal of benign items (e.g. phones, wallets). | 15 |
| FR1.04 | Mass Casualty | Must - 3 | Automatically detect mass casualty weapons. | 15 |
| FR1.05 | Natural Screening | Must - 3 | Allow screening naturally, without stopping or turning. | 15 |
| FR1.06 | Lane Configurations | Must - 3 | Support single and dual-lane configurations. | 15 |
| FR1.07 | Full Body Detection | Must - 3 | Perform full body detection on personnel up to 6'2" in height. | 15 |
| FR1.08 | Adjustable Sensitivity | Must - 3 | Have an adjustable sensitivity across at least 5 levels. | 15 |
| FR1.09 | Permission-Based App | Must - 3 | Be operable via a permission-based application. | 15 |
| FR1.10 | One Second Detection | Must - 3 | Detect and alert to threats within 1 second. | 15 |
| FR1.11 | Fused Sensing | Should - 2 | Utilize millimeter-wave sensing technologies, fused with video analytics. | 10 |
| FR1.12 | Video Integration | Could - 1 | Integrate with existing video management systems (VMS) for enhanced situational awareness. | 5 |
| FR1.13 | Video Cameras | Must - 3 | Have forward and aft facing situational cameras. | 15 |
| FR2 | Data Display / User Interface | | | |
| FR2.01 | Sensor Alerting | Must - 3 | Provide visual and audible alerts from the sensing apparatus. | 15 |
| FR2.02 | Tablet Alerting | Must - 3 | Provide a visual indication on tablet devices to guide secondary screening area(s) of focus (e.g. highlight areas of concern on a generic model of the human body). | 15 |
| FR2.03 | Individual Specificity | Must - 3 | Provide an indication on tablet devices of which individuals were detected to guide secondary of the correct individual. | 15 |
| FR2.04 | Flag All Alerts | Must - 3 | Provide a visual indication for each detected threat simultaneously. | 15 |
| FR2.05 | Self Help | Must - 3 | Provide help modules for self-guided training and troubleshooting assistance. | 15 |
| FR2.06 | Tablet Dashboards | Must - 3 | Provide a tablet dashboard on each setup to view throughput and detection metrics and review logs. | 15 |
| FR2.07 | Screening Data Capture | Must - 3 | Provide a means for staff to record results of secondary screening, to enable evaluation of detection performance. | 15 |
| FR3 | Software Functionality | | | |
| FR3.01 | Remote Updates | Must - 3 | Support remote updates of application and scanner software. | 15 |
| FR3.02 | ML Detection | Must - 3 | Use machine-learning based threat detection methods. | 15 |
| FR3.03 | ML Detection Updates | Must - 3 | Support daily updates of machine-learning weapons detection models to allow for continuous improvement of threat detection. | 15 |
| FR3.04 | Cloud Management | Must - 3 | Provide a cloud-based management interface for all detection setups, including health checks and GPS location for mobile systems. | 15 |
| FR3.05 | Automated Reporting | Must - 3 | Provide automated reporting and dashboard functionality to monitor system performance (e.g. alert rates, trends, error logs). | 15 |
| FR3.06 | Remote Configuration | Must - 3 | Support remote configuration and updates of setups via a web interface. | 15 |
| FR3.07 | Notifications | Must - 3 | Provide a means to alert key personnel via email and/or SMS notifications. | 15 |
| FR4 | Data | | | |
| FR4.02 | Secure Data | Must - 3 | Provide secure transmission and storage of data and alerts. | 15 |
| FR4.03 | Role-Based Administration | | Provide role-based access control for application operation and system administration. | |
| 26 | "Must" Requirements | 0 | Must have Requirements as "S" Standard Function | 0 | 405 |
| 1 | "Should" Requirements | 0 | Must have Requirements in "B" Base Code or already on roadmap | Response Total Pts | Tab Max Total Pts |
| 1 | "Could" Requirements | | | | |
| 28 | Requirements Total on this worksheet | | | | |
Non-functional Requirements
| Non-Functional Requirements | | | | |
| Req # | Area | Priority | Requirement | Response |
(Please select from
| drop-down menu) | Comments | Auto Calculated Response Selection Points | Auto Calculated Points |
| (Response x Priority Rating) | Maximum Points | | |
(Priority Rating x Max Points)
| NFR1 | Availability | | | |
| NFR1.01 | Technical Support | Must - 3 | Provide 24/7/365 technical support with remote diagnosis capability. | 15 |
| NFR1.02 | On-Site Support | Must - 3 | Provide on-site support within 24 hours for hardware failures. | 15 |
| NFR1.03 | Downtime Plans | Must - 3 | Provide well-defined downtime response plans for continuous operational capability. | 15 |
| NFR2 | Data Management | | | |
| NFR2.01 | Data Accessibility | Must - 3 | The Solution must allow for and support the process to receive or send real-time or nightly data feeds to ensure Agency can aggregate data with other State data for analytical reporting purposes. | 15 |
| NFR2.02 | Data Migrations Process | Must - 3 | The Solutions data retrieval processes must utilize secure, encrypted communications methods. | 15 |
| NFR3 | Data Security | | | |
| NFR3.01 | Role Access Controls | Must - 3 | The Solution must implement Role-Based Access Control, to allow for precise control over access to real-time and historical data. | 15 |
| NFR4 | Power & Data Systems Interfaces | | | |
| NFR4.01 | Power Interface | Must - 3 | Operate on a 100-240VAC @ 50 or 60Hz circuit, with no more than 1000W of power. | 15 |
| NFR4.02 | Wifi Interface | Must - 3 | Operate independently of the facility's Local Area Network, to only require internet access via a secured guest wifi network. | 15 |
| NFR4.03 | System Integrations | Should - 2 | Support integration with access control, visitor management, and video monitoring systems. | 10 |
| NFR5 | Performance | | | |
| NFR5.01 | Walking Speed | Must - 3 | Allow personnel to walk at least 0.5 m/s through detection apparatus. | 15 |
| NFR5.02 | Simultaneous Screening | Must - 3 | Be capable of screening more than one individual simultaneously. | 15 |
| NFR5.03 | Throughput | Must - 3 | Have a demonstrated capacity of screening at least 2,000 individuals per hour. | 15 |
| NFR5.04 | Non-Daily Calibration | Should - 2 | Operate without daily calibration (e.g. only require weekly reboots). | 10 |
| NFR6 | Reliability & Environment | | | |
| NFR6.01 | Operational History | Must - 3 | Have a proven and robust operational history with use in high traffic screening areas (e.g. hospitals, athletic facilities, transporation venues). | 15 |
| NFR6.02 | Storage Temperature | Should - 2 | Be capable of being stored across a temperature range of –40°C to +70°C. | 10 |
| NFR6.03 | Operational Temperature | Must - 3 | Be capable of operation across a temperature range of –20°C to +40°C in full sun, up to +55°C in shade. | 15 |
| NFR6.04 | Humidity | Must - 3 | Be capable of operating in up to 100% relative humidty, condensing. | 15 |
| NFR6.05 | Dust and Water Ingress | Must - 3 | Be IP54 rated for dust and water ingress. | 15 |
| NFR6.06 | Wind Conditions | Must - 3 | Operate in wind conditions up to 20 mph. | 15 |
| NFR6.07 | Indoor and Outdoor | Must - 3 | Be fully operational in indoor and outdoor spaces, with reasonably anticipated usage patterns. | |
| NFR7 | Accessibility | | | |
| NFR7.01 | Dimensions - Single Lane | Must - 3 | Fit within 80 inches of width, 42 inches of depth, and no more than 75 inches of height. | 15 |
| NFR7.02 | Dimensions - Dual Lane | Must - 3 | Fit within 140 inches of width, 42 inches of depth, and no more than 75 inches of height. | 15 |
| NFR7.03 | ADA Compliance | Must - 3 | Support ADA compliant lane widths. | 15 |
| NFR7.04 | Fixed Spacing | Must - 3 | Support fixed spacing of detecting towers. | 15 |
| NFR7.05 | Mobile Sensors | Must - 3 | Be mobile and relocatable by OSH personnel. | 15 |
| NFR7.06 | Mobile Sensors - Setup | Must - 3 | Support a readily repeatable setup and alignment process. | 15 |
| NFR7.07 | Mobile Sensors - Securing | Must - 3 | Have a means provided to retain and secure the sensors to the ground or floor. | 15 |
| NFR8 | Usability | | | |
| NFR8.01 | Standard Look/ Feel/ Branding | Should - 2 | The Solution should include the ability to allow for agency branding labels (logo) on sensor apparatuses and web interfaces. | 10 |
| NFR8.02 | Americans with Disability Act Compliance | Must - 3 | The Solution must meet federal accessibility standards (508 Standards and Section 255 Guidelines for Information and Communication Technology -- WCAG 2.2. | 15 |
| NFR8.03 | Web-based design/functionality | Must - 3 | The Solution must support mobile users as well as desktop/laptop users with responsive web design. | 15 |
| NFR8.04 | Member Communication | Must - 3 | The Solution must comply with the HHS guideline to display information in plain language. | |
Note: See the Department of Health and Human Services web guideline in reference doc.
| https://www.hhs.gov/web/building-and-managing-websites/web-requests/write-in-plain-language/index.html | | | | | 15 | |
| NFR8.05 | DHS SAFETY Act | Must - 3 | Comply with the DHS SAFETY Act designation or certification. | | 15 |
| NFR8.06 | Electrical Appliance Safety | Must - 3 | Comply with UL 61010-1, with certification by a Nationally Recognized Testing Laboratory. | | 15 |
| NFR8.07 | Radiating Device Safety | Must - 3 | Comply with IEEE C95.1-2019 for Safe Exposure to Electromagnetic Fields, with test data from an accredited lab. | | 15 |
| 30 | "Must" Requirements | 0 | Must have Requirements as "S" Standard Function | 0 | 475 |
| 4 | "Should" Requirements | 0 | Must have Requirements in "B" Base Code or already on roadmap | Response Total Pts | Tab Max Total Pts |
| 0 | "Could" Requirements | | | | |
| 34 | Requirements Total on this worksheet | | | | |