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.
General Requirements The Contractor hereby agrees:
Special Requirements Additional terms and conditions of this Agreement, if any, which are made a part hereof are set forth in the “Special Requirements” attached hereto as Exhibit “B” and incorporated herein by this reference. In the event of a conflict between the provisions of Exhibit “B” and any other provisions of this Agreement, the provisions of Exhibit “B” shall govern.
Operational Requirements 4 At-Sea Monitors are deployed, in accordance with coverage rates developed by 5 NMFS and as assigned through the Pre-Trip Notification System (PTNS), to 6 vessels. Due to availability of funding, changes in the fishery management, 7 such as emergency closures, court ordered closures, weather, and unforeseen 8 events must remain flexible. Additional funding for sea days may be added to 9 the contract within the scope and maximum allowable sea days. 10 The following items define the operational services to be provided by the 11 contractor under this contract.
Personnel Requirements a. The CONTRACTOR shall secure, at the CONTRACTOR'S own expense, all personnel required to perform this Contract. b. The CONTRACTOR shall ensure that the CONTRACTOR'S employees or agents are experienced and fully qualified to engage in the activities and perform the services required under this Contract, and that all applicable licensing and operating requirements imposed or required under federal, state, or county law, and all applicable accreditation and other standards of quality generally accepted in the field of the activities of such employees and agents are complied with and satisfied.
Procedural and Operational Requirements By accepting and using the Financial Assistance awarded under this Agreement and for this Program Element, LPHA agrees to conduct the following activities in accordance with the indicated procedural and operational requirements: a. LPHA must operate its Communicable Disease program in accordance with the Requirements and Standards for the Control of Communicable Disease set forth in ORS Chapters 431, 432, 433 and 437 and OAR Chapter 333, Divisions 12, 17, 18, 19 and 24, as such statutes and rules may be amended from time to time. b. LPHA must use all reasonable means to investigate in a timely manner all reports of Reportable Diseases, infections, or conditions. To identify possible sources of infection and to carry out appropriate control measures, the LPHA Administrator shall investigate each report following procedures outlined in OHA’s Investigative Guidelines or other procedures approved by OHA. OHA may provide assistance in these investigations, in accordance with OAR 333-019-0000. Investigative guidelines are available at: xxxx://xxx.xxxxxx.xxx/oha/PH/DiseasesConditions/CommunicableDisease/ReportingCommuni cableDisease/ReportingGuidelines/Pages/index.aspx c. As part of its Communicable Disease control program, LPHA must, within its service area, investigate the Outbreaks of Communicable Diseases, institute appropriate Communicable Disease control measures, and submit required information in a timely manner regarding the Outbreak to OHA in Orpheus (or Opera for COVID-19 Cases and XXXXX for COVID-19 contacts) as prescribed in OHA CD Investigative Guidelines available at: d. LPHA must establish and maintain a single telephone number whereby physicians, hospitals, other health care providers, OHA and the public can report Communicable Diseases and Outbreaks to LPHA 24 hours a day, 365 days a year. LPHA may employ an answering service or 911 system, but the ten-digit number must be available to callers from outside the local emergency dispatch area, and LPHA must respond to and investigate reported Communicable Diseases and Outbreaks. e. LPHA must attend Communicable Disease 101 and Communicable Disease 303 training. f. LPHA must attend monthly Orpheus user group meetings or monthly Orpheus training webinars.
Financial Requirements A report of monthly and cumulative financial requirements; and
Federal Requirements In the event this Contract is paid in whole or in part from any federal government agency or source, the specific terms, regulations and requirements governing the disbursement of these funds shall be specified herein and become a part of this clause.
Governmental Requirements The Provider warrants and represents that it will comply with all governmental ordinances, laws and regulations.
Technical Requirements 4.5.3.1 Tandem Switching shall have the same capabilities or equivalent capabilities as those described in Telcordia TR-TSY-000540 Issue 2R2, Tandem Supplement, June 1, 1990. The requirements for Tandem Switching include but are not limited to the following: 4.5.3.1.1 Tandem Switching shall provide signaling to establish a tandem connection; 4.5.3.1.2 Tandem Switching will provide screening as jointly agreed to by <<customer_short_name>> and BellSouth; 4.5.3.1.3 Where applicable, Tandem Switching shall provide AIN triggers supporting AIN features where such routing is not available from the originating end office switch, to the extent such Tandem switch has such capability; 4.5.3.1.4 Where applicable, Tandem Switching shall provide access to Toll Free number database; 4.5.3.1.5 Tandem Switching shall provide connectivity to Public Safety Answering Point (PSAP)s where 911 solutions are deployed and the tandem is used for 911; and 4.5.3.1.6 Where appropriate, Tandem Switching shall provide connectivity for the purpose of routing transit traffic to and from other carriers. 4.5.3.2 BellSouth may perform testing and fault isolation on the underlying switch that is providing Tandem Switching. Such testing shall be testing routinely performed by BellSouth. The results and reports of the testing shall be made available to <<customer_short_name>>. 4.5.3.3 BellSouth shall control congestion points and network abnormalities. All traffic will be restricted in a non-discriminatory manner. 4.5.3.4 Tandem Switching shall process originating toll free traffic received from <<customer_short_name>>’s local switch. 4.5.3.5 In support of AIN triggers and features, Tandem Switching shall provide SSP capabilities when these capabilities are not available from the Local Switching Network Element to the extent such Tandem Switch has such capability.
