Analyze Phase Sample Clauses

Analyze Phase. [***] 6.2.2.1 Design Hand-off Requirements Document & Checklist reviewed with Customer and minimum dataset identified for Analyze Phase 6.2.2.2 Availability of [***] including all [***]. 6.2.2.3 Availability of preliminary [***] covering all modes
Sample 1Sample 2
AutoNDA by SimpleDocs
Analyze Phase. Based on the information collected during the Engage Phase, Mercatus will analyze and document the detailed business requirements of Customer. Once the entire current process has been mapped, Mercatus will identify gaps and overlap within roles or business units and define how Mercatus will fit into and facilitate Customer’s applicable processes using the Platform. This includes definitions and recommendations around: o Data, Document and Entity Management workflows o Commitment Tracking o Reporting and Analytics Dashboards requirements o User roles and access privileges o 3rd party software integration requirements, such as existing monitoring or accounting solutions (if applicable) • This process will be defined within a “Functional Requirements Document” (FRD) delivered by Mercatus, which will be reviewed with the assigned Customer Project Sponsor, then presented to Customer’s Executive Team. This document will be approved in writing prior to the start of the Build Phase to ensure that Customer has complete clarity on what will be implemented, how it will be implemented, and timeline for implementation.
Sample 1Sample 2
Analyze Phase. 17. Medidata will provide the following Edge methodology design specification templates in the Medidata formats to Customer: • eCRF specification template • Data validation specification template • Standard output data transfer plan –or- • Custom output data transfer plan specification template (if in scope) • Custom report requirements specification template (if in scope) • Integration specification template including Rave import requirements (if in scope) 18. Medidata will be responsible for completing the Medidata Edge specification templates provided for the study. 19. Customer and Medidata will sign-off on the Medidata Edge specifications prior to starting the study Build phase. 00. Training sessions are out of scope under this Statement of Work No. 2, as all sites are identical to the Neodisc US study and will have already have been trained as part of the Neodisc US study implementation. 21. Medidata will be responsible for configuring the following components of the Rave application: • eCRFs (copied from Neodisc US) • System edit checks (copied from Neodisc US) • Standard edit checks (copied from Neodisc US) • Custom edit checks and custom functions (copied from Neodisc US) • Standard reports • Standard outputs (copied from Neodisc US) • Creating user accounts and sites for purposes of development and UAT • Study specific configuration (roles) (copied from Neodisc US) 22. Medidata will perform quality control activities on all aforementioned components. 23. Medidata will activate the pre-configured standard reports provided with the license of the Rave application. 24. Medidata will provide standard outputs for up to one SAS dataset for each unique eCRF. It is assumed that 80 – 90% of the data will be a one-to-one mapping from the eCRF to the SAS data format. Final datasets will be delivered in SAS format. Additional custom output files and transformations can be requested. Additional custom outputs are out-of-scope under this Statement of Work No. 2. 25. Medidata will provide data transfers via a secure FTP site or other secure transfer mechanism at the following frequencies: • 1 test transfer • Twice-weekly transfers, beginning 1 month following Study Start in SAS format • 1 final transfer in SAS format • Additional files and on-demand transfers are out-of-scope • SAS datasets will be provided on a twice-weekly basis, with additional datasets requested and provided on demand 26. Local Labs and associated reference are out of scope under this State...
Sample 1
Analyze Phase. 16. Medidata will provide the following Edge methodology design specification templates in the Medidata formats to Customer: • eCRF specification template • Data validation specification template • Standard output data transfer plan –or- • Custom output data transfer plan specification template (if in scope) • Custom report requirements specification template (if in scope) • Integration specification template including Rave import requirements (if in scope) 17. Medidata will be responsible for completing the Medidata Edge specification templates provided for the study. 18. Customer and Medidata will sign-off on the Medidata Edge specifications prior to starting the study build phase. Build Xxxxx 00. Medidata will be responsible for configuring the following components of the Rave application: • eCRFs • System edit checks • Standard edit checks • Custom edit checks and custom functions • Standard reports • Standard outputs • Creating user accounts and sites for purposes of development and UAT • Study specific configuration (roles) 20. Medidata will perform quality control activities on all aforementioned components. 21. Medidata will activate the pre-configured standard reports provided with the license of the Rave application. 22. Medidata will provide standard outputs for up to one SAS dataset for each unique eCRF. It is assumed that 80 – 90% of the data will be a one-to-one mapping from the eCRF to the SAS data format. Final datasets will be delivered in SAS format. Additional custom output files and transformations can be requested. Additional custom outputs are out-of-scope under this Statement of Work No. 3. 23. Medidata will provide data transfers via a secure FTP site or other secure transfer mechanism at the following frequencies: • 1 test transfer • Twice-weekly transfers, beginning 1 month following Study Start in SAS format • 1 final transfer in SAS format • Additional files and on-demand transfers are out-of-scope • SAS datasets will be provided on a twice-weekly basis, with additional datasets requested and provided on demand 24. Local Labs and associated reference are out of scope under this Statement of Work No. 3. 25. This study will use a Radiographic lab facility. The data will be entered into the eCRF via data entry screens by lab personnel. Automated system integration is outside the scope of this Statement of Work No. 3. The eCRF will provide file attachment capability to allow lab personnel to attach digitized x-ray image files for ea...
Sample 1
Analyze Phase. Requirements gathering session. A requirements-gathering session will be held with Subscriber to ensure that all requirements are understood.  Requirements document. A document that describes in detail all of the requirements associated with the workflow. Subscriber representative will be required to sign off on the requirements document before proceeding to the following steps.  Application configuration.  Ambra Study Uploader. The Ambra Study Uploader will be installed on on-site computers as needed. Please note that the Subscriber will provide the hardware on which the Ambra Study Uploader will be installed.  Web Upload Tool. The Ambra Web Uploader will be integrated into the Subscriber’s website for ad hoc uploading as needed.  Ambra Gateway installation. The Ambra Gateway will be installed on site as needed. Please note that Subscriber will provide the hardware on which the Gateway will be installed.  Alpha review. Initial review with Subscriber in xxxx://xxxxxx.xxxxxxxxxxx.xxx to familiarize Subscriber’s representatives with the Ambra Applications and workflow in preparation for user acceptance testing.  Training material for end users. Ambra will provide training materials in the form of standard Ambra Documentation and up to one hour of edits as requested by Subscriber.  User acceptance testing. Subscriber is responsible for all elements of user acceptance testing including test case writing and test case execution. Company will answer any questions as needed.
Sample 1
Analyze Phase. 16. Medidata will provide the following Edge methodology design specification templates in the Medidata formats to Customer: • eCRF specification template • Data validation specification template • Standard output data transfer plan –or- • Custom output data transfer plan specification template (if in scope) • Custom report requirements specification template (if in scope) • Integration specification template including Rave import requirements (if in scope) 17. Medidata will be responsible for completing the Medidata Edge specification templates provided for the study. 18. Customer and Medidata will sign-off on the Medidata Edge specifications prior to starting the study build phase.
Sample 1
Analyze Phase. Silver Spring Responsibilities. Silver Spring will perform each of the following tasks:
Sample 1
AutoNDA by SimpleDocs

Related to Analyze Phase

  • Development Phase contractual phase initiated with the approval of ANP for the Development Plan and which is extended during the Production Phase while investments in xxxxx, equipment, and facilities for the Production of Oil and Gas according to the Best Practices of the Oil Industry are required.

  • Production Phase contract period in which the Development and the Production are to be performed.

  • Design Development Phase INDICATE IN STATEMENT OF WORK “NOT APPLICABLE” IF SECTION IS NOT APPLICABLE 1.1.6.1. The ARCHITECT/ENGINEER shall prepare from the approved Schematic Design Studies, the Design Development Documents consisting of drawings (including at least architectural, landscaping, civil, structural, mechanical and electrical plans, building sections; and finish schedule), outline specifications following the Construction Specification Institute "CSI" Format and other necessary documents to fix and describe the size and character of the entire Project as to its site, structural, mechanical, and electrical systems, materials and other such essentials as may be appropriate, for and until approved by the State. 1.1.6.2. The ARCHITECT/ENGINEER shall conduct meetings with the State, Efficiency Vermont, and relevant members of the design team, to review the Design Development Documents for the purposes of furthering the energy efficiency objectives of the Project. 1.1.6.3. The ARCHITECT/ENGINEER shall prepare for the State a revised accounting of how the Project is responding to LEED criteria. 1.1.6.4. The ARCHITECT/ENGINEER shall submit to the State a revised Statement of Probable Construction Cost based thereon for and until approved by the State.

  • Design Phase All Basic Services set forth in the Agreement with the exception of Interdisciplinary Document Coordination Review, conducting a Card Trick session, Value-Engineering services, Estimating services. • All Basic Services set forth in the Agreement. • All Basic Services set forth in the Agreement. • All Basic Services set forth in the Agreement.

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Construction Phase Part 1 –

  • PHASE is a distinct portion of the Work to be provided under this Agreement, as specified in the Statement Of Work.

  • Construction Phase Fee Contractor’s Construction Phase Fee is the maximum amount payable to Contractor for any cost or profit expectation incurred in the performance of the Work that is not specifically identified as being eligible for reimbursement by Owner elsewhere in this Agreement. References in the UGSC to Contractor’s “overhead” and “profit” mean Contractor’s Construction Phase Fee. The Construction Phase Fee includes, but is not limited to, the following items: 9.1 All profit, profit expectations and costs associated with profit sharing plans such as personnel bonuses, incentives, and rewards; company stock options; or any other like expenses of Contractor.

  • Tests and Preclinical and Clinical Trials The preclinical studies and clinical trials conducted by or, to the Company’s knowledge, on behalf of the Company, that are described in the Registration Statement, the Pricing Disclosure Package and the Prospectus, as applicable, and are intended to be submitted to the U.S. Food and Drug Administration (the “FDA”) or other comparable government entities, were and, if still ongoing, are being conducted in all material respects in accordance with experimental protocols, procedures and controls pursuant to accepted professional scientific standards and all Authorizations and Applicable Laws, including, without limitation, current Good Clinical Practices and Good Laboratory Practices and any applicable rules and regulations of the jurisdiction in which such trials and studies are being conducted; the descriptions of the results of such studies and trials contained in the Registration Statement, the Pricing Disclosure Package and the Prospectus are, to the Company’s knowledge, accurate and complete in all material respects and fairly present the data derived from such studies and trials; except to the extent disclosed in the Registration Statement, the Pricing Disclosure Package and the Prospectus, the Company is not aware of any studies or trials, the results of which the Company believes reasonably call into question the study or trial results described or referred to in the Registration Statement, the Pricing Disclosure Package and the Prospectus when viewed in the context in which such results are described and the clinical stage of development; and, except to the extent disclosed in the Registration Statement, the Pricing Disclosure Package or the Prospectus, the Company has not received any written notices or written correspondence from the FDA or any governmental entity requiring the termination or suspension of any preclinical studies or clinical trials conducted by or on behalf of the Company, other than ordinary course communications with respect to modifications in connection with the design and implementation of such trials, copies of which communications have been made available to you.

  • Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!