Related Use Case Requirements Sample Clauses

Related Use Case Requirements. Certain Use Cases may require Participant to enter into other Use Cases. These Use Cases are interdependent to fully support each Use Case. Each Exhibit will set forth any such requirements. Organizations participating in any Exhibit will need to also participate in the Common Key Service Use Case and the Active Care Relationship Service Use Case unless an Exhibit specifically excludes participation in the CKS or the ACRS Use Cases.
AutoNDA by SimpleDocs
Related Use Case Requirements. Certain Use Cases may require PO to enter into other Use Cases. These Use Cases are interdependent to fully support each Use Case. Each Exhibit will set forth any such requirements. Organizations participating in any Exhibit will need to also participate in the Common Key Service Use Case and the Active Care Relationship Service Use Case unless an Exhibit specifically excludes participation in the CKS or the ACRS Use Cases.
Related Use Case Requirements. In addition to the Use Cases required under the MUCA, PO must enter into the following Use Cases: [include additional Use Case participation requirements].
Related Use Case Requirements. No related Use Case requirements.
Related Use Case Requirements. 4.4.1. Organizations contributing data for this Use Case are required to onboard to the following Use Cases: Active Care Relationship Service, Common Key Service and Health Directory. 5. Service Interruptions. No service interruption variations. 6. Responsibilities of the Parties.

Related to Related Use Case Requirements

  • License Requirements The Hotel’s alcoholic beverage license requires that the Hotel shall: (i) request proper identification (photo ID) of any person of questionable age and refuse alcoholic beverage service if the person is either under age or proper identification cannot be produced, and (ii) refuse alcoholic beverage service to any person who, in the Hotel’s judgment, appears to be intoxicated; and (iii) instruct its personnel to avoid encouraging patrons to consume alcoholic beverages (commonly referred to as “over-pouring”).

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • Project Requirements 1. Project must conform to regulations under 24 CFR Part 92, commonly known as the HOME Regulations.

  • Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.

  • Service Requirements Grantee shall:

  • Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.

  • Vehicle Requirements The following shall be considered minimum Vehicle requirements. The Authorized User shall include supplemental required specifications for Vehicles specified in a Mini-Bid. Unless otherwise indicated, all items specified which are listed on the OEM Pricelist as standard or optional equipment shall be factory installed and operative. Vehicles delivered to an Authorized User in a condition considered to be below retail customer acceptance levels will not be accepted. Items which determine this acceptance level shall include, but not be limited to, the general appearance of the interior and exterior of the vehicle for completeness and quality of workmanship, lubrication and fluid levels, with any leaks corrected, mechanical operation of the vehicle and all electrical components operational. Product specified to be furnished and installed which is not available through the OEM shall conform to the standards known to that particular industry, both product and installation.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!