BETA PHASE Sample Clauses

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 [*] [*] 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 [*] 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.
Sample 1
AutoNDA by SimpleDocs
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.
Sample 1
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
Sample 1
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.
Sample 1
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
Sample 1
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...
Sample 1
BETA PHASE. During the Beta Phase, reviews will be exploratory only.
Sample 1
AutoNDA by SimpleDocs

Related to BETA PHASE

  • Construction Phase Part 1 –

  • Initial Development Plan Not later than the Effective Date, Licensee shall have provided Merck with an initial Development plan for the Licensed Product in the Field in the Territory, which shall be incorporated as part of this Agreement as Attachment 3.02(a) (as may be amended in accordance with this Agreement, the “Development Plan”). **CERTAIN INFORMATION IN THIS EXHIBIT HAS BEEN OMITTED AND WILL BE FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION PURSUANT TO A CONFIDENTIAL TREATMENT REQUEST.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

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

  • Commissioning Commissioning tests of the Interconnection Customer's installed equipment shall be performed pursuant to applicable codes and standards. If the Interconnection Customer is not proceeding under Section 2.3.2, the Utility must be given at least ten (10) Business Days written notice, or as otherwise mutually agreed to by the Parties, of the tests and may be present to witness the commissioning tests.

  • Development Work The Support Standards do not include development work either (i) on software not licensed from CentralSquare or (ii) development work for enhancements or features that are outside the documented functionality of the Solutions, except such work as may be specifically purchased and outlined in Exhibit 1. CentralSquare retains all Intellectual Property Rights in development work performed and Customer may request consulting and development work from CentralSquare as a separate billable service.

  • Information Systems Acquisition Development and Maintenance Security of System Files. To protect City Information Processing Systems and system files containing information, Service Provider will ensure that access to source code is restricted to authorized users whose specific job function necessitates such access.

  • Development Program A. Development activities to be undertaken (Please break activities into subunits with the date of completion of major milestones)

  • Development Efforts 4.2.1 Hana shall use Commercially Reasonable Efforts to Develop each Product in the Territory (including carrying out its responsibilities under the Development Plan) to:

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.

Time is Money Join Law Insider Premium to draft better contracts faster.