Common use of General Clarification Clause in Contracts

General Clarification. Initial Data Load “Data import”, “import workbooks”, and “initial data load” are synonymous terms referring to the initial migration of data from The Customer's existing systems into Questica. Where this initial data load is to be performed by Questica, the data shall be returned to Questica in Excel workbooks. Questica's Project Manager will provide blank workbooks for this purpose as an output of initial discovery meetings. These are adapted from standard templates to use The Customer's terminology and to incorporate all elements of The Customer's chart of accounts, other data entities, and columns within those data entities. Such data provided must be “clean”, consistent, and complete. The Questica PM is not responsible for cleaning data, and will not repeatedly load data in order to repair issues and/or add missing information. The Customer can use the software's user interface or Questica's Excel® export/import feature to further amend and maintain data, or to load data where this is a customer task. For example, where Questica's work to load prior year data may be limited to a specific number of years in order to reduce implementation cost, there is no system limit to the number of prior years that the customer can load using Excel® export/import. Data Model The Questica Budget system is a relational database built on a standard data model. Using the system's user interface, this data model may be enhanced to mirror The Customer's data structures, notably the chart of accounts that is unique to The Customer's institution. While all of the standard tables ('entities') must be retained, the following points are held to be true: • Any of the standard entities may be renamed to match The Customer's terminology; • Out-of-the-box entities may be ignored, or in some cases filled with place-holder data, if not useful; • There is a defined, immutable, relationship between certain entities - for example Costing Centers (Operating) and Projects (Capital) roll up to a single Department, each in turn rolling up to a single Division; • The GL Account/Account Category, Division/Department, Fund Category/Fund, and Asset Category/Asset Type structures must be consistent across all years and across the modules (Operating, Personnel, Capital, Financial Statements, and Performance); • GL Account Categories must be categorized as containing either a revenue or expenditure accounts (accommodation is made for other account types in the Financial Statements module); • Questica Budget enacts data integrity through the use of relational data structures. Data structures which do not follow accepted data principles (for example, re-using GL Accounts/Object Codes to mean different things to different Departments) can typically be accommodated but is not guaranteed and such accommodation can extend the import timeframe; • A list of the standard entities and their relationship is available upon request.

General Clarification. Initial Data Load “Data import”, “import workbooks”, and “initial data load” are synonymous terms referring to the initial migration of data from The Customer's ’s existing systems into QuesticaQuestica Budget. Where this initial data load is to be performed by Questica▇▇▇▇▇▇▇▇, the data shall be returned to Questica in Excel workbooks. Questica's ’s Project Manager will provide blank workbooks for this purpose as an output of initial discovery meetings. These are adapted from standard templates to use The Customer's ’s terminology and to incorporate all elements of The Customer's ’s chart of accounts, other data entities, and columns within those data entities. Such data provided must be “clean”, consistent, and complete. The Questica PM is not responsible for cleaning data, and will not repeatedly load data in order to repair issues and/or add missing information. The Customer can use the software's ’s user interface or Questica's Questica Budget’s Excel® export/import feature to further amend and maintain data, or to load data where this is a customer task. For example, where Questica's ’s work to load prior year data may be limited to a specific number of years in order to reduce implementation cost, there is no system limit to the number of prior years that the customer can load using Excel® export/import. Data Model The Questica Budget system is a relational database built on a standard data model. Using the system's ’s user interface, this data model may be enhanced to mirror The Customer's ’s data structures, notably the chart of accounts that is unique to The Customer's ’s institution. While all of the standard tables ('‘entities'’) must be retained, the following points are held to be true: • Any of the standard entities may be renamed to match The Customer's ’s terminology; • Out-of-the-box entities may be ignored, or in some cases filled with place-holder data, if not useful; • There is a defined, immutable, relationship between certain entities - for example Costing Centers (Operating) and Projects (Capital) roll up to a single Department, each in turn rolling up to a single Division; • The GL Account/Account Category, Division/Department, Fund Category/Fund, and Asset Category/Asset Type structures must be consistent across all years and across the modules (Operating, Personnel, Capital, Financial Statements, and Performance); • GL Account Categories must be categorized as containing either a revenue or expenditure accounts (accommodation is made for other account types in the Financial Statements module); • Questica Budget enacts data integrity through the use of relational data structures. Data structures which do not follow accepted data principles (for example, re-using GL Accounts/Object Codes to mean different things to different Departments) can typically be accommodated but is not guaranteed and such accommodation can extend the import timeframe; • A list of the standard entities and their relationship is available upon request.