Analyze Phase Sample Clauses

The Analyze Phase clause defines the initial stage in a project or contractual engagement where the parties assess requirements, objectives, and potential challenges. During this phase, the involved parties typically gather information, review existing processes, and identify key deliverables or issues that need to be addressed before moving forward. This clause ensures that both sides have a clear understanding of the project's scope and expectations, reducing the risk of misunderstandings and setting a solid foundation for subsequent phases.
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.
View SourceView Similar (2)
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
View SourceView Similar (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. Build ▇▇▇▇▇ ▇▇. 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 unde...
View SourceView Similar (2)
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.
View Source
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 ▇▇▇▇://▇▇▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ 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.
View Source
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 ▇▇▇▇▇ ▇▇. 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...
View Source
Analyze Phase. Silver Spring Responsibilities. Silver Spring will perform each of the following tasks:
View Source

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 ▇▇▇▇▇, 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 1.3.1 Based on the approved Schematic Design Documents, model(s) and any adjustments to the Program of Requirements, BIM Execution Plan or Amount Available for the Construction Contract authorized by the Owner, the Architect/Engineer shall prepare, for approval by the Owner and review by the Construction Manager, Design Development Documents derived from the model(s) in accordance with Owner’s written requirements to further define and finalize the size and character of the Project in accordance with the BIM Execution Plan, “Facility Design Guidelines” and any additional requirements set forth in Article 15. The Architect/Engineer shall review the Design Development documents as they are being modeled at intervals appropriate to the progress of the Project with the Owner and Construction Manager at the Project site or other location specified by Owner in the State of Texas. The Architect/Engineer shall utilize the model(s) to support the review process during Design Development. The Architect/Engineer shall allow the Construction Manager to utilize the information uploaded into Owner’s PMIS to assist the Construction Manager in fulfilling its responsibilities to the Owner. 1.3.2 As a part of Design Development Phase, Architect/Engineer shall accomplish model coordination, aggregation and “clash detection” to remove conflicts in design between systems, structures and components. Architect/Engineer shall utilize Owner’s PMIS to accomplish model coordination and collaborate with Construction Manager in the resolution of critical clashes identified by the Construction Manager. Architect/Engineer shall demonstrate and provide written assurance to Owner that conflicts/collisions between models have been resolved. 1.3.3 The Architect/Engineer shall review the Estimated Construction Cost prepared by the Construction Manager, and shall provide written comments. 1.3.4 Before proceeding into the Construction Document Phase, the Architect/Engineer shall obtain Owner’s written acceptance of the Design Development documents and approval of the mutually established Amount Available for the Construction Contract and schedule. 1.3.5 The Architect/Engineer shall prepare presentation materials including an animation derived from the model(s) as defined in “Facility Design Guidelines” at completion of Design Development and if so requested shall present same to the Board of Regents at a regular meeting where scheduled within the state. 1.3.6 The Architect/Engineer shall prepare preliminary recommended furniture layouts for all spaces where it is deemed important to substantiate the fulfillment of program space requirements, or to coordinate with specific architectural, mechanical and electrical elements. 1.3.7 Architect/Engineer shall assist the Owner, if requested, with seeking approval of the Project by the Texas Higher Education Coordinating Board (THECB). Such assistance shall include (i) the preparation of a listing of the rooms and square footages in the Project, and (ii) the preparation of project cost information, in accordance with THECB Guidelines. This information shall be provided at the completion of the Design Development Phase when requested by the Owner. The listing of rooms and square footages shall then be updated to reflect any changes occurring during construction and provided to the Owner at Substantial Completion. 1.3.8 At the completion of the Design Development Phase, or such other time as Owner may specify to Architect/Engineer, at Owner’s sole option and discretion, Owner will furnish Architect/Engineer with a Guaranteed Maximum Price proposal prepared by Construction Manager based upon the Design Development documents prepared by the Architect/Engineer and approved by the Owner. The Architect/Engineer shall assist the Owner and endeavor to further and advocate the Owner’s interests in Owner’s communications with the Construction Manager in an effort to develop a Guaranteed Maximum Price proposal acceptable to Owner, in Owner’s sole option and discretion. If the Owner does not accept the Construction Manager’s Guaranteed Maximum Price proposal, the Architect/Engineer shall participate with the Owner and Construction Manager in constructability reviews and shall revise the documents as necessary in order to reach an agreement. If the Construction Manager’s Guaranteed Maximum Price proposal exceeds the Schematic Design Phase Estimated Construction Cost prepared by, or otherwise accepted by the Construction Manager due to an increase in the scope of the Project caused by further development of the design documents by the Architect/Engineer to the extent that such could not be reasonably inferred by the Construction Manager from the Schematic Design documents, and Owner directs Architect/Engineer to revise the documents, the Architect/Engineer shall revise the documents at its own expense so that the Guaranteed Maximum Price proposal for constructing the Project shall not exceed the Owner’s Amount Available for the Construction Contract and any previously approved Estimated Construction Costs. If it is determined to be in the Owner’s best interest, instead of requiring the Architect/Engineer to revise the Drawings and Specifications, the Owner reserves the right to accept a Guaranteed Maximum Price proposal that exceeds the stipulated Amount Available for the Construction Contract. The Architect/Engineer shall analyze the final Guaranteed Maximum Price proposal document, together with its supporting assumptions, clarifications, and contingencies, and shall submit a detailed written analysis of the document to the Owner. Such analysis shall include, without limitation, reference to and explanation of any inaccurate or improper assumptions and clarifications. The A/E will not be required to make revisions to the documents at its own expense under the provisions of this paragraph if the Owner’s rejection of the Guaranteed Maximum Price proposal is not due to a failure of the A/E to provide the services otherwise required herein. 1.3.9 After the Guaranteed Maximum Price has been accepted, the Architect/Engineer shall incorporate necessary revisions into the Design Development documents. The A/E will not be required to make revisions to the documents at its own expense under the provisions of this paragraph if the revisions are required as the result of inaccurate assumptions and clarifications made in the development of the Guaranteed Maximum Price proposal that are not due to a failure of the A/E to provide the services otherwise required herein.

  • 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