Additional Functionality or Systems Sample Clauses

The "Additional Functionality or Systems" clause defines the terms under which extra features or systems, beyond the original scope of an agreement, may be provided. Typically, this clause outlines the process for requesting, approving, and implementing such enhancements, including any associated costs or timelines. For example, if a client requires new software modules or integration with third-party platforms after the initial contract is signed, this clause governs how those requests are handled. Its core practical function is to provide a clear framework for managing and incorporating changes or expansions, thereby preventing misunderstandings and ensuring both parties agree on the scope and terms of additional work.
Additional Functionality or Systems. Populate Table 9 for each upstream EDE Entity that has added functionality or systems to complete the implementation of a primary EDE Entity’s EDE environment (e.g., the approved EDE environment of the primary EDE Entity does not comprise the entire EDE environment for an upstream EDE Entity). Table 9 contains the following fields:  ID: Unique identifier for the row item to track items between Table 8 and Table 9Error! Reference source not found., as applicable.  Primary EDE Entity: Organization Name/System Name  Upstream Entity: Document all known or expected upstream entities and/or system name (if applicable)
View SourceView Similar (3)
Additional Functionality or Systems. Populate Table 9 for each upstream EDE Entity that has added functionality or systems to complete the implementation of a primary EDE Entity’s EDE environment (e.g., the approved EDE environment of the primary EDE Entity does not comprise the entire EDE environment for an upstream EDE Entity). Table 9 contains the following fields: • ID: Unique identifier for the row item to track items between Table 8 and Table 9Error! Reference source not found., as applicable. • Primary EDE Entity: Organization Name/System Name • Upstream Entity: Document all known or expected upstream entities and/or system name (if applicable)
View SourceView Similar (2)
Additional Functionality or Systems. Instructions: During the annual EDE Agreement Renewal submission of the ISA, Primary EDE Entities must document all approved upstream EDE Entity relationships in Table 9. After the annual EDE Agreement Renewal submission, primary EDE Entities must submit a new Table 9 for each new upstream EDE Entity. If you insert a new Table 9, be sure to update the Table Caption field to ensure the correct, sequential table numbering; update the cross-reference fields for the tables; and update the List of Tables in the front matter. If you copy a table, paste it at an insertion point styled as “Normal” and use the following command: Paste/Paste Special/Formatted Text (RTF) where Track Changes is turned off. [Delete this instruction.] Note: A primary EDE Entity adding any EDE Entity relationships must also follow the Change Notification Procedures for Enhanced Direct Enrollment Entity Information Technology Systems process including performing a Security Impact Analysis (SIA), a Business Impact Analysis (BIA), and potentially updating the Privacy Impact Assessment (PIA) based on the analysis of the SIA to determine the impact that changes will have on the Entity’s IT systems. [Delete this instruction.] Table 9 contains the following fields: • ID: Unique identifier for the row item to track items between Table 8 and Table 9, as applicable. • Information System Name: IT system environment name for the EDE Environment Provider. • Upstream EDE Entity Organization Name: Document all known or expected upstream entities and/or system name (if applicable). • NEW: SSO Implementation: If an EDE arrangement will involve SSO, the entity must describe the SSO implementation, including, at a minimum, the following information: which users will use the SSO implementation (i.e., consumers, agents, and brokers) and the process to and entity responsible for conducting identity proofing of consumers, agents, and brokers.
View Source

Related to Additional Functionality or Systems

  • Additional Functions Upon receipt of Proper Instructions, the Custodian shall take all such other actions as specified in such Proper Instructions and as shall be reasonable or necessary with respect to Repurchase Agreement transactions and the Securities and funds transferred and received pursuant to such transactions, including, without limitation, all such actions as shall be prescribed in the event of a default under a Repurchase Agreement.

  • Telemedicine Services This plan covers clinically appropriate telemedicine services when the service is provided via remote access through an on-line service or other interactive audio and video telecommunications system in accordance with R.I. General Law § 27-81-1. Clinically appropriate telemedicine services may be obtained from a network provider, and from our designated telemedicine service provider. When you seek telemedicine services from our designated telemedicine service provider, the amount you pay is listed in the Summary of Medical Benefits. When you receive a covered healthcare service from a network provider via remote access, the amount you pay depends on the covered healthcare service you receive, as indicated in the Summary of Medical Benefits. For information about telemedicine services, our designated telemedicine service provider, and how to access telemedicine services, please visit our website or contact our Customer Service Department.

  • Hosting Services NCR Voyix shall furnish facilities, equipment, computer programs and services, as specified from time to time by NCR Voyix, that NCR Voyix deems necessary for operation and maintenance of the System (collectively, the “Hosting Services”).

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5. 1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

  • Approved Services; Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.