Functional Requirements Clause Samples
The Functional Requirements clause defines the specific tasks, features, or capabilities that a product, service, or system must deliver. It typically outlines measurable criteria or performance standards that must be met, such as response times, compatibility with certain platforms, or the ability to process a set number of transactions per second. By clearly specifying what is expected, this clause ensures that both parties have a mutual understanding of deliverables, reducing the risk of disputes over whether contractual obligations have been fulfilled.
POPULAR SAMPLE Copied 1 times
Functional Requirements. Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.
Functional Requirements. 6.2.2.2.1. The camera should function well under low sunlight conditions. The camera shall provide a luminance contrast of at least 1:3 under low sun condition in a region outside the part of the image where the light source is reproduced (condition as defined in EN 12368: 8.
Functional Requirements. The Structure shall perform the following functions:
a) Support all Bus and Instrument equipment through all mission phases, including pre-launch, launch, initialization, normal operations, and EOL disposal.
b) [**Redacted**]
Functional Requirements. The Thermal Control subsystem shall autonomously perform the following functions under the Conditions and Operational Scenarios specified below:
Functional Requirements. Each vehicle submitted for approval pursuant to this Regulation shall be equipped with an Electronic Stability Control (ESC) system that:
6.1. Is capable of applying braking torques individually to all four wheels4 and has a control algorithm that utilizes this capability;
6.2. Is operational over the full speed range of the vehicle, during all phases of driving including acceleration, coasting, and deceleration (including braking), except:
6.2.1. When the driver has disabled ESC;
6.2.2. When the vehicle speed is below 20 km/h;
6.2.3. While the initial start-up self-test and plausibility checks are completed, not to exceed two minutes when driven under the conditions of paragraph 9.10.2.;
6.2.4. When the vehicle is being driven in reverse.
6.3. Remains capable of activation even if the antilock braking system or traction control system is also activated.
Functional Requirements. Intake Req # Requirement Text Included, Configurable , not Included Estimated Hours to Customize ATIMS Capabilities AD-01 The solution shall support the intake and booking process in compliance with the OCSD policies and procedures. I = Included ATIMS has a state of the art JMS system that is installed in several California counties. Our intake and booking modules meets the policy and procedures of these agencies. We believe that the ATIMS JMS would also meet the policy and procedure of OCSD but without reviewing them we cannot guarantee this. AD-02 The solution shall provide the capability for authorized users to enter basic information such as the date and time of arrival, agency, name of officer, name(s) of inmates and basic medical information. The system must also provide the capability to ingest information that is sent through an electronic data exchange upon approval from an authorized user. I = Included ATIMS provides all of these functions as part of the base system. If an interface is used to import Prebooking data a cost may be incurred. AD-03 The solution shall enable users to assign a system-generated temporary (pre-booking) number to each inmate. I = Included This is a standard function of the ATIMS Prebooking module. AD-04 The solution shall enable authorized users to send the information identified in AD-02 and AD-03 to the CHS medical system using an automated interface. I = Included ATIMS has an internal interface engine that can accomplish this function. All included interfaces have been quoted in the cost proposal. AD-05 The solution shall trigger a notification to be sent to OCSD-designated staff if an inmate requires immediate medical or mental health attention. C = Configurable This is a standard configuration of the ATIMS event engine and can be configured. AD-06 The solution shall support an interface with the CHS medical system to receive information after Triage activities have been conducted on the inmate and the inmate is ready to be booked. (Interface details are provided in the technical requirements.) C = Configurable This is a standard function of the ATIMS Interface engine. All included interfaces have been quoted in the cost proposal. AD-07 The solution shall populate the booking officers queue with the name(s) of the inmates that have cleared the Triage process and are ready to be booked. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-08 The solution shall enable users to update the ...
Functional Requirements. The EPDS shall perform the following functions under the Conditions and Operational Scenarios specified below:
Functional Requirements. 3.3.1. Components shall be supplied in the inner and retainer trays for use in the operating room (OR).
3.3.2. Kit shall be easy to open with gloves on.
3.3.3. Lead kit shall be supplied ETO sterilized per manufacturing outline LEAD2008-35B.
Functional Requirements. The Storage Facility shall include the following four major capabilities that shall provide the necessary functions for receipt, inspection, and long-term management and storage of elemental mercury:
Functional Requirements. The EPDS shall perform the following functions under the Conditions and Operational Scenarios specified below:
a) Provide sufficient power to all Spacecraft Bus and Instrument equipment to