{"component": "clause", "props": {"groups": [{"snippet": "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.", "samples": [{"hash": "8xipgZIs9yP", "uri": "/contracts/8xipgZIs9yP#functional-requirements", "label": "Master Subscription Agreement", "score": 34.1420631409, "published": true}, {"hash": "5jG92AHu5uu", "uri": "/contracts/5jG92AHu5uu#functional-requirements", "label": "Data Processing Agreement", "score": 33.153049469, "published": true}, {"hash": "daVdFlTc55A", "uri": "/contracts/daVdFlTc55A#functional-requirements", "label": "Wisconsin Student Data Privacy Agreement", "score": 31.5525512695, "published": true}], "snippet_links": [{"key": "security-project", "type": "definition", "offset": [124, 140]}, {"key": "denial-of-service", "type": "clause", "offset": [166, 183]}], "size": 12, "hash": "34b68a43afd5f71aa54a331822769132", "id": 1}, {"snippet": "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.", "samples": [{"hash": "1jRZcL3rMUW", "uri": "/contracts/1jRZcL3rMUW#functional-requirements", "label": "Agreement Concerning the Adoption of Uniform Technical Prescriptions for Wheeled Vehicles", "score": 23.7118415833, "published": true}, {"hash": "k12rWCgNO4c", "uri": "/contracts/k12rWCgNO4c#functional-requirements", "label": "Agreement Concerning the Adoption of Uniform Technical Prescriptions for Wheeled Vehicles", "score": 19.0, "published": true}, {"hash": "gZN6NajwGp9", "uri": "/contracts/gZN6NajwGp9#functional-requirements", "label": "Agreement Concerning the Adoption of Uniform Technical Prescriptions for Wheeled Vehicles", "score": 19.0, "published": true}], "snippet_links": [{"key": "provide-a", "type": "definition", "offset": [91, 100]}, {"key": "luminance-contrast", "type": "definition", "offset": [101, 119]}, {"key": "light-source", "type": "definition", "offset": [212, 224]}], "size": 6, "hash": "9e5746e92965fe7132bcf32ff65f9212", "id": 4}, {"snippet": "The Structure shall perform the following functions:\na) Support all Bus and Instrument equipment through all mission phases, including pre-launch, launch, initialization, normal operations, and EOL disposal.\nb) [**Redacted**]", "samples": [{"hash": "fd3ytLoPm1J", "uri": "/contracts/fd3ytLoPm1J#functional-requirements", "label": "Satellite Purchase Agreement (Digitalglobe Inc)", "score": 20.3908290863, "published": true}, {"hash": "SxxE6ngEbJ", "uri": "/contracts/SxxE6ngEbJ#functional-requirements", "label": "Satellite Purchase Agreement (Digitalglobe Inc)", "score": 19.8432579041, "published": true}, {"hash": "cgsBBJDvGpI", "uri": "/contracts/cgsBBJDvGpI#functional-requirements", "label": "Worldview 3 Satellite Purchase Agreement (Digitalglobe Inc)", "score": 19.1601638794, "published": true}], "snippet_links": [{"key": "normal-operations", "type": "clause", "offset": [171, 188]}], "size": 7, "hash": "62bfa0c220a4e8514ab072f62948467c", "id": 2}, {"snippet": "The Thermal Control subsystem shall autonomously perform the following functions under the Conditions and Operational Scenarios specified below:", "samples": [{"hash": "jCncWHiOOTV", "uri": "/contracts/jCncWHiOOTV#functional-requirements", "label": "Worldview 3 Satellite Purchase Agreement (Digitalglobe Inc)", "score": 23.1601638794, "published": true}, {"hash": "7jKHWUPMKNd", "uri": "/contracts/7jKHWUPMKNd#functional-requirements", "label": "Worldview3 Satellite Purchase Agreement (Digitalglobe, Inc.)", "score": 22.1540050507, "published": true}, {"hash": "4JGN5UIdOtq", "uri": "/contracts/4JGN5UIdOtq#functional-requirements", "label": "Worldview 3 Satellite Purchase Agreement (Digitalglobe Inc)", "score": 21.3299102783, "published": true}], "snippet_links": [{"key": "control-subsystem", "type": "definition", "offset": [12, 29]}, {"key": "the-conditions", "type": "clause", "offset": [87, 101]}, {"key": "operational-scenarios", "type": "clause", "offset": [106, 127]}], "size": 6, "hash": "7a057245f0a24ebb9644e594a9fd0992", "id": 3}, {"snippet": "Each vehicle submitted for approval pursuant to this Regulation shall be equipped with an Electronic Stability Control (ESC) system that:\n6.1. Is capable of applying braking torques individually to all four wheels4 and has a control algorithm that utilizes this capability;\n6.2. Is operational over the full speed range of the vehicle, during all phases of driving including acceleration, coasting, and deceleration (including braking), except:\n6.2.1. When the driver has disabled ESC;\n6.2.2. When the vehicle speed is below 20 km/h;\n6.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.;\n6.2.4. When the vehicle is being driven in reverse.\n6.3. Remains capable of activation even if the antilock braking system or traction control system is also activated.", "samples": [{"hash": "aY6B3knjbNM", "uri": "/contracts/aY6B3knjbNM#functional-requirements", "label": "Agreement Concerning the Adoption of Uniform Technical Prescriptions for Wheeled Vehicles", "score": 35.5623435974, "published": true}, {"hash": "k4RcabooyD1", "uri": "/contracts/k4RcabooyD1#functional-requirements", "label": "Agreement Concerning the Adoption of Uniform Technical Prescriptions for Wheeled Vehicles", "score": 24.6988372803, "published": true}, {"hash": "f2VwPEoeQ3e", "uri": "/contracts/f2VwPEoeQ3e#functional-requirements", "label": "Agreement Concerning the Adoption of Uniform Technical Prescriptions for Wheeled Vehicles", "score": 24.5414104462, "published": true}], "snippet_links": [{"key": "for-approval", "type": "definition", "offset": [23, 35]}, {"key": "pursuant-to", "type": "definition", "offset": [36, 47]}, {"key": "this-regulation", "type": "definition", "offset": [48, 63]}, {"key": "an-electronic", "type": "clause", "offset": [87, 100]}, {"key": "stability-control", "type": "definition", "offset": [101, 118]}, {"key": "capable-of", "type": "definition", "offset": [146, 156]}, {"key": "speed-range", "type": "clause", "offset": [308, 319]}, {"key": "the-vehicle", "type": "clause", "offset": [323, 334]}, {"key": "all-phases", "type": "clause", "offset": [343, 353]}, {"key": "the-driver", "type": "definition", "offset": [457, 467]}, {"key": "vehicle-speed", "type": "definition", "offset": [502, 515]}, {"key": "not-to-exceed", "type": "definition", "offset": [617, 630]}, {"key": "conditions-of", "type": "clause", "offset": [665, 678]}, {"key": "antilock-braking-system", "type": "definition", "offset": [797, 820]}, {"key": "control-system", "type": "definition", "offset": [833, 847]}], "size": 6, "hash": "47a545f5af20ef8df629a1f90ca73158", "id": 5}, {"snippet": "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 facility and location count after the inmate has received a booking number in the system. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-09 The solution shall enable users to create a new booking number for an inmate and the tie it to the OCN number (inmate number). I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-10 The solution shall enable users to enter information from multiple sources/documents such as the Statement of Booking Officer (SOBO), Pre-booking, PCD etc. As mentioned earlier, it is expected that this information will come in through an automated interface that will obtain data real-time and insert it into the inmate record. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-11 The solution shall enable users to search for an inmate record based on multiple criteria such as, but not limited to: name, alias, SSN, and date of birth. N = Not Included 80 ATIMS has all functions available in the base system with the exception of SSN. ATIMS will add this function as an enhancement. AD-12 The solution shall enable users to add a booking number for each incarceration event. These booking numbers must be linked to the OCN number. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-13 The solution shall consolidate inmate information into the original OCN#. A history of corrections must also be maintained. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-14 The solution shall provide users with the ability to search an inmate's prior incarceration information and alerts. The system must prompt users to carry over prior alerts to the new record. It should also provide users with the ability to NOT carry over an alert (such as a medical alert that is no longer relevant) if so desired by OCSD. I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-15 The solution shall provide users with the ability to capture custody booking status including, but not limited to: a. Pre-trial b. Sentenced c. Detainer I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-16 The solution shall provide users with the ability to do a partial or full copy of inmate information from a previous booking. The solution shall maintain all previous booking information (e.g. photos, tattoos, classification, release, etc.) I = Included This is a standard function of the ATIMS Intake and Booking Module. AD-17 The solution shall enable users to record inmate information including, but not limited to: a. Name (Last, Middle, MI, Suffix) b. Name Type (Legal, Committed, Alias, Nickname)", "samples": [{"hash": "6CInNFB2jYu", "uri": "/contracts/6CInNFB2jYu#functional-requirements", "label": "Contract for Integrated Jail Management System", "score": 25.8432579041, "published": true}], "snippet_links": [{"key": "not-included", "type": "clause", "offset": [55, 67]}, {"key": "estimated-hours", "type": "clause", "offset": [68, 83]}, {"key": "the-solution", "type": "definition", "offset": [122, 134]}, {"key": "booking-process", "type": "definition", "offset": [164, 179]}, {"key": "compliance-with-the", "type": "clause", "offset": [183, 202]}, {"key": "policies-and-procedures", "type": "clause", "offset": [208, 231]}, {"key": "state-of-the-art", "type": "clause", "offset": [258, 274]}, {"key": "policy-and-procedures", "type": "definition", "offset": [377, 398]}, {"key": "we-believe", "type": "definition", "offset": [418, 428]}, {"key": "provide-the", "type": "clause", "offset": [575, 586]}, {"key": "authorized-users", "type": "definition", "offset": [602, 618]}, {"key": "to-enter", "type": "definition", "offset": [619, 627]}, {"key": "basic-information", "type": "clause", "offset": [628, 645]}, {"key": "time-of-arrival", "type": "clause", "offset": [667, 682]}, {"key": "medical-information", "type": "definition", "offset": [738, 757]}, {"key": "the-system", "type": "definition", "offset": [759, 769]}, {"key": "electronic-data-exchange", "type": "clause", "offset": [849, 873]}, {"key": "upon-approval", "type": "clause", "offset": [874, 887]}, {"key": "base-system", "type": "definition", "offset": [979, 990]}, {"key": "enable-users", "type": "clause", "offset": [1091, 1103]}, {"key": "the-information", "type": "clause", "offset": [1310, 1325]}, {"key": "an-internal", "type": "clause", "offset": [1435, 1446]}, {"key": "cost-proposal", "type": "definition", "offset": [1547, 1560]}, {"key": "notification-to", "type": "clause", "offset": [1597, 1612]}, {"key": "designated-staff", "type": "definition", "offset": [1629, 1645]}, {"key": "mental-health", "type": "definition", "offset": [1689, 1702]}, {"key": "standard-configuration", "type": "clause", "offset": [1741, 1763]}, {"key": "to-receive", "type": "definition", "offset": [1887, 1897]}, {"key": "ready-to", "type": "clause", "offset": [1986, 1994]}, {"key": "technical-requirements", "type": "definition", "offset": [2045, 2067]}, {"key": "the-booking", "type": "definition", "offset": [2243, 2254]}, {"key": "the-facility", "type": "clause", "offset": [2496, 2508]}, {"key": "a-booking", "type": "definition", "offset": [2558, 2567]}, {"key": "the-tie", "type": "clause", "offset": [2758, 2765]}, {"key": "information-from", "type": "clause", "offset": [2932, 2948]}, {"key": "multiple-sources", "type": "definition", "offset": [2949, 2965]}, {"key": "statement-of", "type": "clause", "offset": [2988, 3000]}, {"key": "booking-officer", "type": "definition", "offset": [3001, 3016]}, {"key": "based-on", "type": "definition", "offset": [3370, 3378]}, {"key": "not-limited", "type": "clause", "offset": [3410, 3421]}, {"key": "date-of-birth", "type": "clause", "offset": [3448, 3461]}, {"key": "with-the-exception-of", "type": "clause", "offset": [3536, 3557]}, {"key": "inmate-information", "type": "clause", "offset": [3877, 3895]}, {"key": "the-original", "type": "definition", "offset": [3901, 3913]}, {"key": "ability-to", "type": "clause", "offset": [4099, 4109]}, {"key": "carry-over", "type": "clause", "offset": [4205, 4215]}, {"key": "medical-alert", "type": "clause", "offset": [4332, 4345]}, {"key": "booking-information", "type": "definition", "offset": [4891, 4910]}, {"key": "to-record", "type": "definition", "offset": [5084, 5093]}], "size": 6, "hash": "f08ec6f8c642d4f526b9a0aba5969610", "id": 6}, {"snippet": "The EPDS shall perform the following functions under the Conditions and Operational Scenarios specified below:", "samples": [{"hash": "jCncWHiOOTV", "uri": "/contracts/jCncWHiOOTV#functional-requirements", "label": "Worldview 3 Satellite Purchase Agreement (Digitalglobe Inc)", "score": 23.1601638794, "published": true}, {"hash": "iV6X73CU4Fs", "uri": "/contracts/iV6X73CU4Fs#functional-requirements", "label": "Worldview 3 Satellite Purchase Agreement (Digitalglobe Inc)", "score": 21.1601638794, "published": true}, {"hash": "fd3ytLoPm1J", "uri": "/contracts/fd3ytLoPm1J#functional-requirements", "label": "Satellite Purchase Agreement (Digitalglobe Inc)", "score": 20.3908290863, "published": true}], "snippet_links": [{"key": "the-conditions", "type": "clause", "offset": [53, 67]}, {"key": "operational-scenarios", "type": "clause", "offset": [72, 93]}], "size": 5, "hash": "f98e1ae78f39918bd4cef02dd201201f", "id": 7}, {"snippet": "3.3.1. Components shall be supplied in the inner and retainer trays for use in the operating room (OR).\n3.3.2. Kit shall be easy to open with gloves on.\n3.3.3. Lead kit shall be supplied ETO sterilized per manufacturing outline LEAD2008-35B.", "samples": [{"hash": "bRjdkFMpNuY", "uri": "/contracts/bRjdkFMpNuY#functional-requirements", "label": "Supply Agreement (Nevro Corp)", "score": 25.7857627869, "published": true}], "snippet_links": [{"key": "operating-room", "type": "clause", "offset": [83, 97]}, {"key": "to-open", "type": "clause", "offset": [129, 136]}], "size": 5, "hash": "2b22c03615495a584478d26036db5184", "id": 8}, {"snippet": "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:", "samples": [{"hash": "5ZrdjZwqlFj", "uri": "/contracts/5ZrdjZwqlFj#functional-requirements", "label": "Contract", "score": 24.1779594421, "published": true}, {"hash": "hdijk0JPVQq", "uri": "/contracts/hdijk0JPVQq#functional-requirements", "label": "Contract", "score": 24.1560573578, "published": true}, {"hash": "bpmbL8ftGnD", "uri": "/contracts/bpmbL8ftGnD#functional-requirements", "label": "Contract", "score": 24.1122512817, "published": true}], "snippet_links": [{"key": "facility-shall", "type": "clause", "offset": [12, 26]}, {"key": "provide-the", "type": "clause", "offset": [84, 95]}, {"key": "and-storage", "type": "clause", "offset": [166, 177]}, {"key": "elemental-mercury", "type": "definition", "offset": [181, 198]}], "size": 4, "hash": "80924b44692f77d3eb9e5b5415c3c28b", "id": 9}, {"snippet": "The EPDS shall perform the following functions under the Conditions and Operational Scenarios specified below:\na) Provide sufficient power to all Spacecraft Bus and Instrument equipment to", "samples": [{"hash": "7jKHWUPMKNd", "uri": "/contracts/7jKHWUPMKNd#functional-requirements", "label": "Worldview3 Satellite Purchase Agreement (Digitalglobe, Inc.)", "score": 22.1540050507, "published": true}, {"hash": "4JGN5UIdOtq", "uri": "/contracts/4JGN5UIdOtq#functional-requirements", "label": "Worldview 3 Satellite Purchase Agreement (Digitalglobe Inc)", "score": 21.3299102783, "published": true}, {"hash": "ajKHZJMjQGS", "uri": "/contracts/ajKHZJMjQGS#functional-requirements", "label": "Worldview 3 Satellite Purchase Agreement (Digitalglobe Inc)", "score": 21.1601638794, "published": true}], "snippet_links": [{"key": "the-conditions", "type": "clause", "offset": [53, 67]}, {"key": "operational-scenarios", "type": "clause", "offset": [72, 93]}, {"key": "spacecraft-bus", "type": "definition", "offset": [146, 160]}], "size": 3, "hash": "260504a0358cd5d53d64b197537e5e16", "id": 10}], "next_curs": "CmASWmoVc35sYXdpbnNpZGVyY29udHJhY3RzcjwLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IiBmdW5jdGlvbmFsLXJlcXVpcmVtZW50cyMwMDAwMDAwYQyiAQJlbhgAIAA=", "clause": {"title": "Functional Requirements", "children": [["", ""], ["functional-requirements", "Functional Requirements"], ["general", "General"], ["worldspace-signal-reception", "WorldSpace Signal Reception"], ["file-format", "File Format"]], "size": 214, "parents": [["requirements", "REQUIREMENTS"], ["application-security", "Application Security"], ["miscellaneous", "Miscellaneous"], ["general", "General"], ["functional-requirements", "Functional Requirements"]], "id": "functional-requirements", "related": [["operational-requirements", "Operational Requirements", "Operational Requirements"], ["additional-requirements", "Additional Requirements", "Additional Requirements"], ["general-requirements", "General Requirements", "General Requirements"], ["federal-requirements", "Federal Requirements", "Federal Requirements"], ["closet-i-urinal-requirements", "Closet I Urinal Requirements", "Closet I Urinal Requirements"]], "related_snippets": [], "updated": "2025-07-24T06:49:05+00:00", "also_ask": ["What are the essential elements that must be included in a functional requirements clause to ensure clarity and enforceability?", "How can parties strategically define or limit functional requirements to manage scope and avoid scope creep?", "What are the most common pitfalls or ambiguities in drafting functional requirements, and how can they be mitigated?", "How do courts typically interpret disputes over functional requirements\u2014what evidence or standards are most persuasive?", "How do functional requirements clauses in this agreement compare to industry standards or similar contracts in other jurisdictions?"], "drafting_tip": "Specify measurable criteria, use clear language, and reference standards to ensure requirements are unambiguous, testable, and enforceable.", "explanation": "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."}, "json": true, "cursor": ""}}