Assumptions and Dependencies. This section will describe any key assumptions or dependencies upon which the Project was based or is dependent upon for successful completion, or both.
Assumptions and Dependencies. (To be agreed upon and listed)
Assumptions and Dependencies. Client: Supplier:
Assumptions and Dependencies. In order to achieve a successful deployment, Rogers assumes the following;
2.5.7.1 A minimum system requirement of:
2.5.7.1.1 Windows Vista, 7, 8 or later;
2.5.7.1.2 Mac OS X 10.5 or later;
Assumptions and Dependencies. XL will undertake the tasks (if any) expressly assigned to it in the Project Plan and the Responsibilities Matrix. If there is any delay in XL undertaking such tasks, the provisions of clause 13.1(c) shall apply.
Assumptions and Dependencies. Xxxxxx’s ability to perform the services under this SLA is conditional on Licensee cooperating with Nuance and providing Nuance personnel with reasonable access to individuals, data, systems, and Licensee Ecosystem partners as necessary to perform the services. Xxxxxx is not responsible for the performance of Licensee’s or End Customers’ third-party vendors, nor for the actions or inactions of such third parties. Licensee and End Customer agrees to cooperate and ensure the participation of relevant contributors as follows: Licensee will assist with troubleshooting as necessary. Licensee will facilitate interaction with other partners and End Customers in the event those partners or End Customers impact, or are impacted by, the performance of the Hosted Services, including: o Opening a bridge call with all members of the Licensee Ecosystem, as reasonably necessary. o Making back-end systems of Licensee Ecosystem partners available for testing by Nuance. o Ensuring that Nuance receives maintenance notifications five (5) business days prior to any maintenance performed by Licensee’s internal IT, Licensee’s Ecosystem partners, or any other party reasonably expected to impact the performance of the Hosted Services, along with the anticipated effect on the Hosted Services. o Sharing with Nuance any alerts generated by any hardware and/or software which interacts with the Application(s) and Nuance Ecosystem.
Assumptions and Dependencies. 7.1 Any Fee quoted and any timescale provided is conditional upon:
7.1.1 the Customer performing any dependencies set out in the relevant Statement of Work (and otherwise complying with the terms set out in this agreement and the relevant Statement of Work); and
7.1.2 each assumption set out in the relevant Statement of Work proving to be accurate.
7.2 If Robiquity becomes aware that (a) the Customer has failed to comply with the terms set out in this agreement and/or the relevant Statement of Work and/or perform any of its dependencies or other obligations within the required timescales or (b) an assumption is inaccurate (each a Relief Event), and Robiquity reasonably believes that such Relief Event has or is likely to have a material detrimental effect on its ability to comply with its obligations under a Statement of Work, Robiquity shall:
7.2.1 use reasonable endeavours to mitigate the impact of a Relief Event and to avoid any adverse impact on the performance of its obligations, including seeking to avoid or minimise any delay or cost implication; and
7.2.2 if Robiquity does not consider it is reasonably practicable to avoid an impact on the performance of its obligations as a result of the Relief Event, as soon as reasonably practicable notify the Customer of the Relief Event, any steps that Robiquity is taking to mitigate the impact, and the nature of any adverse impact which it nevertheless expects the Relief Event to have (including any delay or cost implication).
7.3 Subject to clause 7.2, if Robiquity fails to comply with any of its obligations under a Statement of Work as a result of a Relief Event then Robiquity:
7.3.1 shall not be in breach of that Statement of Work where and to the extent it shows that such failure was caused by the Relief Event;
7.3.2 shall be granted a reasonable extension of time for performance of its obligations (provided that such delay was notified to the Customer in accordance with clause 7.2.2); and
7.3.3 Robiquity may charge the Customer for any additional fees, costs and expenses that are reasonably incurred as a result of any Relief Event (provided that such cost implication was notified to the Customer in accordance with clause 7.2.2).
Assumptions and Dependencies. (a) IBM shall maintain system code, applications, and database data on EMC DASD which will be co-resident with other Franklin equipment at the Recovery Center and kept up to date by IBM with Franklin's production data center located in Rancho Cordova, CA via a SRDF process to meet the RTO/RPO requirements as specified in the Agreement. However, the EMC DASD and SRDF solution are not in scope of this Amendment and will be handled separately. If, for any reason, Franklin decides not to implement SRDF technology, the mainframe will continue to be kept at a ready state pending any Disaster declaration.
(b) The Amendment 3 Equipment as listed in Attachment 1 is accurate and will be validated prior to shipment by Franklin. Franklin shall reconfirm the accuracy of Attachment 1 during installation by IBM.
Assumptions and Dependencies. All systematic data feeds and positional information will still be available to ResCap in the same format and location it is currently available. • The availability of Broker Dealer personnel to support the processes and procedures to provide information and clarify information continues unchanged from current practices.
Assumptions and Dependencies. Below are a list of assumptions and dependencies related to this engagement. The COUNTY should confirm that the following statements are accurate and valid. Any changes in the below assumptions could affect the scope of work, schedule or budgeted hours of effort:
(a) Work already completed by the CARE staff and its consultants can be leveraged and modified in the creation of an updated Conceptual Plan for this project
(b) The COUNTY assures appropriate participation and contributions of all functions involved (including management and staff from the Clerk-Recorder’s Division, the Assessor’s Division, the Elections Division, and the Information Technology Division)
(c) CARE Management fully supports and places a high priority on this effort
(d) The COUNTY will facilitate access to other COUNTY vendors (e.g., EasyAccess / Xxxxx, Farallon Geographics, FileNet/RS Computer Assoc., etc.), as necessary, to ensure that all relevant input is received and considered
(e) XXXX will have ready access to COUNTY staff, as appropriate (f) XXXX will have access to COUNTY systems, as appropriate
