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