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. 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. In order to achieve a successful deployment, Rogers assumes the following;
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. Client: • Client will ensure suitably skilled, knowledgeable and experienced people are made available to actively work with the Supplier’s Associates to clarify objectives and priorities during the engagement; • Client will ensure suitably skilled, knowledgeable and experienced people are made available to collaborate with the Supplier’s Associates to resolve any impediments to the progress of the project or deliverables and any other issues that arise in a timely manner; • Client will provide the time reasonably necessary from key stakeholders to answer the Supplier’s queries and sign off on requirements to help the project move forward; • Client will not knowingly withhold any information that may impact the Associates ability to provide the services; • The Client will assign a named Client Representative who will be authorised to accept the deliverables and sign off each Sprint as ‘completed’; • Client is responsible for any regulatory requirements, data protection and privacy policy investigation needed; • Client will ensure timely provision of workspace, wall space and whiteboards suitable for use by the Supplier’s Associates when required; • Client will provide timely access to existing systems, accounts and documentation as may be required by the Supplier’s Associates to enable the provision of the Services; • Client will provide appropriate details and guidance on any governance or security compliance requirements and processes within which the Supplier’s Associates will need to operate; • Client will work with Supplier’s Associates to mitigate any additional RAIDs (Risks, Assumptions, Issues, Dependencies) captured throughout the course of the Works. Supplier: • Supplier will be responsible for the management of its Associate delivery teams in providing the Services and producing the deliverables according to the agreed plan and in line with Sprint review and acceptance processes; • Supplier will assign suitably skilled, knowledgeable and experienced Associates to provide the deliverables and services outlined in this SoW; • Supplier’s Associates will utilise their own equipment and devices in the provision of the Service (save where the Client’s internal security restrictions would prohibit them from doing so). • Supplier’s Associates will actively work with the Client’s personnel to clarify objectives and priorities during the engagement; • Supplier’s Associates will collaborate with the Client’s personnel to resolve any impediments to the prog...
Assumptions and Dependencies. (To be agreed upon and listed)
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:
Assumptions and Dependencies. There are strong dependencies on Work Package 2 to provide updated requirements and specifications with this version of the technical specifications being based on v1.0 of D2.4 Functional Requirements and any further updates will be merged into later iterations of this document. Timely delivery of each iteration requires this specification document to be updated for each iterative release via internal deliverables S2.6 (due Month 14 – May 2013), S2.7 (due Month 20 – November 2013) and S2.8 (due Month 25 – April 2014). The final version of the technical specification will be published as D4.6, also in Month 25 (April 2014). As stated in the Description of Work, the seamless integration of the licensing framework for Europeana into the XXX is a key outcome of the project. A report will be produced by a technical legal expert who will produce an analysis and a set of recommendations for the representation of Europeana licenses in the XXX. The report will be appended to this deliverable when it becomes available. However, we do not expect this to materially change the deliverable. Work Package 4 is dependent on the outputs of Work Packages 3 and 5 to produce its deliverables. Therefore, the following functionality needs to be available for testing in the specified iteration: o Data Selection and Transformation Iteration 1 o Management Overview of status and data publication Iteration 2 o Content re-ingestion from Europeana Iteration 3
Assumptions and Dependencies. The Services are dependent upon the correctness of the Assumptions and satisfaction of the Dependencies. The Client acknowledges that in the event that any of the Assumptions are incorrect or any of the Dependencies are not satisfied, the provision of the affected Services may be delayed and/or prevented and that the time and/or cost to perform those Services may be increased. Thoughtworks shall notify the Client as soon as reasonably practicable after it becomes aware that an Assumption is incorrect or a Dependency is not satisfied, and the Client shall use all reasonable endeavours to remedy the incorrect Assumption and/or satisfy that Dependency (if possible) as soon as possible.
Assumptions and Dependencies. Bioethanol fuel purity will not be measured or analysed continuously during operation. If necessary, such analysis will have to be performed separately e.g. before/during bioethanol fuel tank filling. Fuel purity is assumed to be within the fuel specifications (to be defined).
