Related Use Case Requirements Clause Samples

The 'Related Use Case Requirements' clause defines the specific needs or conditions that must be met in connection with particular use cases outlined in an agreement. This clause typically details how certain products, services, or processes should function to support these use cases, and may reference technical specifications, performance standards, or integration points. Its core practical function is to ensure that all parties have a clear understanding of the expectations and deliverables related to each use case, thereby reducing ambiguity and helping to prevent disputes over whether requirements have been fulfilled.
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.
View Source
Related Use Case Requirements. No related Use Case requirements.
View Source
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.
View Source
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].
View Source
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.
View Source

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.

  • Developer Operating Requirements The Developer must comply with the Transmission Owner’s operating instructions and requirements including but not limited to Transmission Owner’s Operation Coordination Agreement, as it may change from time to time. The Developer must comply with all applicable NYISO tariffs and procedures, as amended from time to time. Whether or not the Large Generating Facility is eligible for the Transition Period LVRT Standard set forth in Appendix G will be determined by the Commission. The Large Generating Facility will comply with the Transition Period LVRT Standard pending issuance of an order by the Commission determining the appropriate LVRT standard. For purposes of compliance with Appendix G, the Transmission Owner has determined that the Developer shall maintain the Large Generating Facility in service during a three-phase fault for 7 cycles. Infrastructure security of New York State Transmission System equipment and operations and control hardware and software is essential to ensure day-to-day New York State Transmission System reliability and operational security. The Commission will expect the NYISO, all Transmission Owners, all Developers and all other Market Participants to comply with the recommendations offered by the President’s Critical Infrastructure Protection Board and, eventually, best practice recommendations from the electric reliability authority. All public utilities will be expected to meet basic standards for system infrastructure and operational security, including physical, operational, and cyber-security practices. All personnel working in Transmission Owner’s facilities will require security background checks prior to entering and working in such facilities. New York Independent System Operator, Inc. Attn: Vice President, Operations ▇▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇ Schenectady, NY 12303 Senior Vice President of Transmission New York Power Authority ▇▇▇ ▇▇▇▇ ▇▇. ▇▇▇▇▇ ▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇-▇▇▇▇ Re: Large Generating Facility Dear : On [Date] [Developer] has completed Trial Operation of Unit No. . This letter confirms that [Developer] commenced Commercial Operation of Unit No. at the Large Generating Facility, effective as of [Date plus one day]. Thank you. NYISO: