Operational requirements for Data Exchange Sample Clauses

Operational requirements for Data Exchange. 9.1 The parties undertake to implement and maintain an operational environment to operate data exchange according to the terms and conditions of this NDA- MOU, which includes but is not limited to the following:
AutoNDA by SimpleDocs

Related to Operational requirements for Data Exchange

  • 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.

  • 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.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Additional Requirements for Sleeping Rooms The Contractor shall provide departing Attendees a secured area for storing belongings.

  • Closet/Urinal Requirements 6.1 Employees Closets Urinals 1-5 1 Nil 6-10 1 1 11-20 2 2 21-35 3 4 36-50 4 6 51-75 5 7 76-100 6 8

  • Technical Requirements 2.7.4.1 The NID shall provide an accessible point of interconnection and shall maintain a connection to ground.

  • Additional Requirements from Authorized Users An Authorized User may have distinct requirements that must be met by all individuals employed by or working for the Authorized User. The Contractor’s Staff Members will be expected to comply with these requirements as a condition of the placement.

  • GENERAL OPERATIONAL REQUIREMENTS 12.1 Interference or damage to Distributor's Equipment by Customers: The Trader must, subject to clause 29.1, include in each of its Customer Agreements a requirement that, during the term of the Customer Agreement and until the end of the period ending on the earlier of 6 months after the termination of the Customer Agreement or the date on which a new Customer Agreement is entered into in respect of the relevant ICP, the Customer must not interfere with or damage, and must ensure that its agents and invitees do not interfere with or damage, the Distributor's Equipment without the prior written consent of the Distributor (except to the extent that emergency action has to be taken to protect the health or safety of persons or to prevent damage to property).

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

  • Procedural and Operational Requirements By accepting and using the Financial Assistance awarded under this Agreement and for this Program Element, LPHA agrees to conduct activities in accordance with the following requirements:

Time is Money Join Law Insider Premium to draft better contracts faster.