PROTOTYPE PHASE Sample Clauses

PROTOTYPE PHASE. After the parties have signed the contract, the prototype phase begins. The purpose is to produce a prototype of the system, with the site skeleton built out and much of the design elements implemented. It is a small, working version of the final system that is ready for adding content to the marketing sites and back office. It may be limited in features, but gives the user an idea of what the final, complete product will be like. At this point, SolutionX and the client determine what, if any, modifications to the scope, budget, and schedule are needed.
Sample 1Sample 2
AutoNDA by SimpleDocs
PROTOTYPE PHASE. The Teams shortlisted in the Idea Phase will be invited to build the functioning prototype based on their shortlisted entry. The functioning prototype shall be built during the Contest Period. - The functioning prototype shall be submitted before 11:55 PM IST on 13th June 2021. - The functioning prototype submitted by a Team shall be referred to as a hack (“hack”). In case of multiple submissions of a hack by any Team, the last hack submitted will be considered as the final submission. - We are not responsible for late or lost submissions. - Organizer or a jury constituted by the Organizer will shortlist winner and runner up from each theme from amongst all Teams shortlisted in the Idea Phase based on Usage of Azure Services, novelty, uniqueness, innovative, sclability, sustainability and practicality of the hack. - ELIGIBLE ENTRY: To be eligible, an entry or a hack must meet the following content / technical requirements: • Your entry or hack must be your own original work; and o For Contests which require a video entry, please note the video must be solely your own work, including but not limited to, the actual filming, editing, graphic design, etc. of the video. • Your entry cannot have been selected as a winner in any other contest; and • You must have obtained all consents, approvals, or licenses required for you to submit your entry; and • To the extent that entry requires the submission of user-generated content such as software, photos, videos, music, artwork, essays, etc., participants of a Team warrant that their entry or hack is their original work, has not been copied from others without permission or apparent rights, and does not violate the privacy, intellectual property rights, or other rights of any other person or entity. You may include Microsoft trademarks, logos, and designs, for which Microsoft grants you a limited license to use for the sole purposes of submitting an entry or hack into this Contest; and • Your entry may NOT contain, as determined by us in our sole and absolute discretion, any content that is obscene or offensive, violent, defamatory, disparaging or illegal, or that promotes alcohol, illegal drugs, tobacco or a particular political agenda, or that communicates messages that may reflect negatively on the goodwill of Microsoft.
Sample 1
PROTOTYPE PHASE. The prototype phase will generally focus on integrating more partner sites into the datalake, consolidate the functionalities that were pioneered in the pilot phase and scale up the performance of the different datalake services. By the end of this phase it should be demonstrated that the datalake ecosystem suits the needs of the ESFRI partner projects, in terms of functionality, performance and usability. The prototype will demonstrate that a cloud-like storage federation, composed of different institutes and different storage providers, can be orchestrated. The aim is to have sizeable storage resources (100TB) from 5 partner institutes in the project leveraging more than three storage technologies. Data injection and distribution through FTS and Rucio should be enabled at the Gigabyte per second scale across sites, targeting a Terabyte per day of net data flow from production to distribution. We should demonstrate the ability to provide at least two different Quality of Service at the orchestrator level and to transition across different Quality of Service layouts. We will provide a token-based AAI infrastructure to be used for general data movement. This implies integrating token support across the main components: the storage systems, the storage orchestrator and the File Transfer Service. The membership database and updating mechanisms for new members will be in place. By the end of the prototype we will provide a common set of monitoring tools offering a high level view of the status ( e.g. storage availability, online files), usage (e.g. number of file and capacity) and activity (e.g. number of data transfers and number of clients accessing data). We will define representative workloads for at least two of the partner projects and integrate them in Hammercloud. Those workloads will be used to assess the impact of latency and bandwidth in remote data access, when compute resources outside the boundary of the datalake are used. We plan to integrate, as a demonstrator, one HPC facility for data processing. Hammercloud will allow us to run these workloads periodically and collect statistics about data access performance. In particular, we intend to measure the impact of network latency with and without the use of xCache and the performance of different QoS classes. Finally, by the end of the prototype we intend to have a first demonstration of event-based data processing. At least one of the storage endpoints would provide file-level information through...
Sample 1
PROTOTYPE PHASE. If BUYER terminates this Agreement for CAUSE --------------- prior to BUYER accepting the Prototype, then SELLER shall refund all sums paid by BUYER to SELLER. If this Agreement is terminated for any other reason prior to accepting the Prototypes, then BUYER shall pay SELLER all charges due at the time of termination together with accrued time, material and equipment charges, if any. Charges associated with a billable event (applicable to both NRE and Engineering Development Charges) shall be due if the work associated with any phase following the previous billable event has been started.
Sample 1
PROTOTYPE PHASE. The Teams shortlisted in the Idea Submission Round will be invited to build the functioning prototype based on their shortlisted Entry. The functioning prototype shall be built during the Contest Period. - The functioning prototype shall be submitted before 20th June 2022. - The functioning prototype submitted by a Team shall be referred to as a Hack (“Hack”). In case of multiple submissions of a Hack by any Team, the last Hack submitted will be considered as the final submission. - We are not responsible for late or lost submissions of a Hack. - The Judges will shortlist winner and runner up from each Theme from amongst all Teams shortlisted in the Idea Submission Round based on usage of Microsoft Azure Services, novelty, uniqueness, innovative, scalability, sustainability and practicality of the Hack.
Sample 1
PROTOTYPE PHASE. In the Prototype Phase, Developer produces and delivers a Proof of Concept - a working "mini-" version of the product delivered online, which includes final functionality, software, reporting, analytics, etc.. The Proof of Concept is a subset of the final product - representing a portion of the final product. The Proof of Concept will be suitable for demonstration purposes, focus testing, and preliminary marketing of the product. The parties acknowledge that the Proof of Concept is used to determine if the design of the product is acceptable and the intended outcome of the product can be realized if development moves forward.
Sample 1

Related to PROTOTYPE PHASE

  • Schematic Design Phase 1.2.1 Based on the mutually agreed upon Program of Requirements, Amount Available for the Construction Contract and the Project Schedule, the Architect/Engineer shall prepare sufficient alternative approaches utilizing BIM for design and construction of the Project to satisfy Owner’s project requirements and shall, at completion of this phase, submit Schematic Design Documents derived from the model in accordance with the BIM Execution Plan, “Facility Design Guidelines” and any additional requirements set forth in Article 15. The Architect/Engineer shall review alternative approaches to design and construction for the Project 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 the Owner within the State of Texas. The Architect/Engineer shall utilize the model(s) to support the review process during Schematic Design. The Architect/Engineer shall provide the Construction Manager with a compact disc containing documents and data files derived from the model to assist the Construction Manager in fulfilling its responsibilities to the Owner. 1.2.2 Architect/Engineer shall provide all services necessary to perform the services of this phase (preparation of model(s), relevant data, decision support model views and Schematic Design Documents) including, without limitation, unless otherwise approved by Owner, the preparation and prompt delivery of all items specified in the BIM Execution Plan and “Facility Design Guidelines”. 1.2.3 Architect/Engineer shall work closely with Owner in preparation of schematic drawings and shall specifically conform to Owner’s requirements regarding aesthetic design issues. 1.2.4 The Architect/Engineer shall review the Estimated Construction Cost prepared by the Construction Manager, and shall provide written comments. 1.2.5 Before proceeding into the Design Development Phase, the Architect/Engineer shall obtain Owner’s written acceptance of the Schematic Design documents and approval of the Architect/Engineer’s preliminary Estimated Construction Cost and schedule. 1.2.6 The Architect/Engineer shall participate in a final review of the Schematic Design Documents and model(s) with the Owner and Construction Manager at the Project site or other location specified by Owner in the State of Texas. Prior to the Owner’s approval of the Schematic Design Documents, the Architect/Engineer shall incorporate such changes as are necessary to satisfy the Owner’s review comments, any of which may be appealed for good cause.

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

  • 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 Review ‌ (a) Where so specified in Schedule A (Scope of Goods and Services) or as otherwise instructed by the City, the Supplier shall submit design-related Documentation for review by the City, and shall not proceed with work on the basis of such design Documentation until the City’s approval of such Documentation has been received in writing. (b) None of: (i) the submission of Documentation to the City by the Supplier; (ii) its examination by or on behalf of the City; or (iii) the making of any comment thereon (including any approval thereof) shall in any way relieve the Supplier of any of its obligations under this Agreement or of its duty to take reasonable steps to ensure the accuracy and correctness of such Documentation, and its suitability to the matter to which it relates.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Preliminary Design Phase 30 percent plans) A. Proceed with Preliminary Design Phase after the completion of the Conceptual phase which includes: Acceptance by Owner of the Conceptual Report and any other Study and Report Phase deliverables; selection by Owner of a recommended solution; issuance by Owner of any instructions for use of Project Strategies, Technologies, and Techniques, or for inclusion of sustainable features in the design, and Indication by Owner of any specific modifications or changes in the scope, extent, character, or design requirements of the Project desired by Owner. 1. Prepare Preliminary Design Phase documents consisting of final design criteria, preliminary drawings, outline specifications, and written descriptions of the Project. 2. Include on plans, property lines, structure locations, ownership names and contact information. 3. In preparing the Preliminary Design Phase documents, use any specific applicable Project Strategies, Technologies, and Techniques authorized by Owner during or following the Study and Conceptual Phase, and include sustainable features, as appropriate, pursuant to Owner’s instructions. 4. Provide necessary field surveys, topographic and utility mapping for Engineer’s design purposes. Comply with the scope of work and procedure for the identification and mapping of existing utilities as defined by Section A1.03 “Utility Requirements” and Section A1.04 “Survey Services” 5. Visit the Site as needed to prepare the Preliminary Design Phase documents. 6. Advise Owner if additional reports, data, information, or services of the types described are necessary and assist Owner in obtaining such reports, data, information, or services. 7. Continue to assist Owner with Project Strategies, Technologies, and Techniques that Owner has chosen to implement. 8. Based on the information contained in the Preliminary Design Phase documents, prepare a revised opinion of probable Construction Cost, and assist Owner in tabulating the various cost categories which comprise Total Project Costs. 9. Obtain and review Owner’s instructions regarding Owner’s procurement of construction services (including instructions regarding advertisements for bids, instructions to bidders, and requests for proposals, as applicable), Owner’s construction contract practices and requirements, insurance and bonding requirements, electronic transmittals during construction, and other information necessary for the finalization of Owner’s bidding-related documents (or requests for proposals or other construction procurement documents), and Construction Contract Documents. Also obtain and review copies of Owner’s design and construction standards, Owner’s standard forms, general conditions, supplementary conditions, text, and related documents or content for Engineer to include in the draft bidding-related documents (or requests for proposals or other construction procurement documents), and in the draft Construction Contract Documents, when applicable. 10. Development communication plan for project: considering the use of door hangers, letters, public meetings, changeable message boards. 11. Furnish 6 review copies of the Preliminary Design Phase documents, opinion of probable Construction Cost, and any other Preliminary Design Phase deliverables to Owner by established due date, and review them with Owner. Owner shall submit to Engineer any comments regarding the furnished items. 12. Revise the Preliminary Design Phase documents, opinion of probable Construction Cost, and any other Preliminary Design Phase deliverables in response to Owner’s comments, as appropriate, and furnish to Owner 6 copies of the revised Preliminary Design Phase documents, revised opinion of probable Construction Cost, and any other deliverables by the specified due date. 13. Engineer’s services under the Preliminary Design Phase will be considered complete on the date when Engineer has delivered to Owner the revised Preliminary Design Phase documents, revised opinion of probable Construction Cost, and any other Preliminary Design Phase deliverables.

  • Preconstruction Phase The Preconstruction Phase shall mean the period commencing on the date of this CM/GC Contract and ending upon commencement of the Construction Phase; provided that if the Owner and CM/GC agree, the Construction Phase may commence before the Preconstruction Phase is completed, in which case both phases shall proceed concurrently, subject to the terms and conditions of the Contract Documents.

  • Flexible Work Schedule A flexible work schedule is any schedule that is not a regular, alternate, 9/80, or 4/10 work schedule and where the employee is not scheduled to work more than 40 hours in the "workweek" as defined in Subsections F. and H., below.

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

  • Improvement Plan A detailed, written plan collaboratively developed between the teacher and evaluator, utilized when a teacher receives an Evaluation Rating of ineffective. The approved form for the Improvement Plan is attached to this agreement as Appendix .

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