BETA PHASE Sample Clauses

POPULAR SAMPLE Copied 1 times
BETA PHASE. DMC and MTI shall participate in a joint effort to develop the prototype design into pre-production ODU assemblies for various frequency bands. The key tasks and responsibilities are: [*] BETA PHASE DELIVERABLES [*] 7/8 GHz ODU, built and tested per DMC provided documentation. Configuration and frequency requirements listed in EXHIBIT E. Pricing is as defined in EXHIBIT D. Additional bands will be priced as specifications and drawings are released by DMC. PRODUCTION DELIVERABLES [*] complete and tested 7/8 GHz Out Door Units per DMC documentation. ----------------------- [*] OMITTED PURSUANT TO A CONFIDENTIAL TREATMENT REQUEST. THE MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION. EXHIBIT B: TERMS AND CONDITIONS OF PURCHASE Alpha, payment will be [*] per set price. Beta, payment will be [*] per set price. Production, payment will be [*] per set price.
BETA PHASE. During the Beta Phase, reviews will be exploratory only.
BETA PHASE. The Beta Phase starts upon delivery by SUPPLIER of the Beta version of SUPPLIER's Product and ends with the final acceptance of SUPPLIER's Product by EMC. The Beta Phase will be performed under responsibility of EMC. EMC will provide technical support for EMC software and hardware. SUPPLIER will provide technical support for Product.
BETA PHASE. The Beta Phase starts upon delivery by McDATA of the Beta version of McDATA's Product and ends with the final acceptance of McDATA's Product by EMC. The Beta Phase will be performed under responsibility of EMC. EMC will provide technical support for EMC software and hardware. McDATA will provide technical support for Product.
BETA PHASE. Beta Objectives Validate customer requirements Validate new function in different real-world applications/environments Generate customer success stories and references Review documentation set
BETA PHASE. DMC and REMEC shall participate in a joint effort to develop the prototype design into pre-production ODU assemblies for various frequency bands. The major tasks and responsibilities are: [*] Pricing is as defined in Exhibit D BETA PHASE DELIVERABLES QTY Type and description -------------------------- [*] [*] [*] GHz ODU, Protected, built and tested per DMC PSD [*] [*] [*] GHz ODU, Protected, built and tested per DMC PSD [*] [*] [*] GHz ODU, Protected, built and tested per DMC PSD [*] [*] [*] GHz ODU, Protected, built and tested per DMC PSD [*] [*] [*] GHz ODU, Protected, built and tested per DMC PSD -------------------------------------------------------------------------------- [*] Omitted pursuant to a confidential treatment request. The material has been filed separately with the Securities and Exchange Commission. sf-602617 6 PRODUCTION DELIVERABLES ----------------------- Approximately [*] total complete and tested Out Door Units per DMC documentation and released production order. Product mix will be both protected and unprotected configurations in the [*], [*], [*], [*], or [*] GHz bands and set per purchase order releases. Initial volume build is expected to be for [*] GHz units. STE charges will be amortized over the initial quantity of [*] units as noted in Exhibit D. PRODUCT FORECAST ---------------- It is agreed that DMC will provide REMEC, on a monthly basis, [*] ([*]) day firm purchase release, [*] ([*]) months Product forecasts and [*] ([*]) months rolling forecasts for long lead time items. This section, as appropriate, may be modified in an addendum to reflect specific Product requirements. STE COSTS The anticipated Total STE cost : BAND COST ----------------------------------- [*] GHz $[*] [*] GHz $[*] [*] GHz $[*] [*] GHz $[*] [*] GHz $[*] ------------------------ TOTAL $[*] MATERIAL PROCUREMENT -------------------- REMEC is authorized to purchase materials using standard purchasing practices including, but not limited to, acquisition of material recognizing Economic Order Quantities, ABC buy policy and long lead time component management in order to meet the Purchase Order requirements of DMC. DMC recognizes its financial responsibility and assumes liability for materials covering the [*]-day purchase release for finished product, WIP for the [*] month release, [*] month product forecast and long lead material. This production forecast shall supercede those requirements in Exhibit E. The [*] GHz long lead time item list (Exhibit F) wil...
BETA PHASE. Beta Objectives Validate customer requirements Validate new function in different real-world applications/environments Generate customer success stories and references Review documentation set Validate support process Validate training Validate any escalation process between companies Beta Program Entrance Criteria EMC 1. Internal Sales Order generated 2. EMC agreement on level of function and platform support 3. Signed Beta/ACT/Non-Disclosure Agreement from Customers SUPPLIER 1. Engineering Quality Assurance underway, with all acceptance tests executed. 2. Documented List of Known Defects 3. Draft Install Document 4. Draft User Document 5. Draft Release Notes 6. No Severity 1 defects SUPPLIER deliverables User Guide (DRAFT). Updated Test Report. Updated requirements (Functional Specification) Beta Version of Product, including documentation: Verification Test Suite and Test Reports as described above will be delivered as part of the Beta Version. It will also include Machine Readable Documentation (release notes with build and installation guidelines, online help, end-user documentation - versions from which SUPPLIER's Product are derived, and a description of software specific deviations). The Beta Phase starts upon delivery by SUPPLIER of the Beta Version of software and/or hardware. The Beta Phase will be performed under responsibility of EMC and end upon final acceptance of SUPPLIER's Product by EMC. SUPPLIER will provide technical support and will modify SUPPLIER's Product to resolve any exceptions uncovered during this phase. EMC deliverables Beta Agreements signed by customers. Pass Criteria of Phase Beta Program Exit Criteria as defined by EMC SUPPLIER All Documentation revised with updates Written Known Defect List Beta Site Summary Reports No Sev 1 or Sev 2 Defects(unless exception) - Systems Outage or System Degradation No Data Corruption No Application Failures SUPPLIER start initiation of general availability items above have been delivered and meet the definition of content as given above.

Related to BETA PHASE

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

  • 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.

  • 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.

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Construction Phase Part 1 –