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. 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 development and unit testing of the products will be done online for actual live functionality. ·The Developer shall on own cost use its credentials of its WeChat Developer Account to develop this Project for VAL.
Assumptions and Dependencies. The development and unit testing of the products will be done at Agicent premises. The customer shall be providing Agicent with the credentials of its Apple Developer Account’s and Google Play account (required to creating adhoc and final releases). INTELLECTUAL PROPERTY RIGHTS AND OWNERSHIP All Intellectual Property (including Source Code, Documentation, and Application Package) during the project is owned by the Customer, and will be turned over to the Customer at the conclusion of the project by Agicent and after the fulfillment of all commercial obligations by the Customer. The customer is the sole owner of the developed software with full IPR. TERM OF AGREEMENT This Agreement commences on the date it is executed and shall continue until full performance by both parties, or until earlier terminated by one party under the terms of this Agreement.
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).
Assumptions and Dependencies. The financial information and general ledger activity related to the Broker Dealer will be recorded in the ResCap Peoplesoft general ledger system and transmitted to GMAC outside of the ResCap consolidated financial results; and • The employees providing the services under the SOW will remain employees of ResCap; and • The Broker Dealer employees, who are transferred to GMAC as part of the transaction, will become employees of GMAC, LLC or GMAC UK PLC.
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.
