PROTOTYPE PHASE Sample Clauses
The PROTOTYPE PHASE clause defines the initial stage of a project where a preliminary version or model of the product or service is developed and tested. During this phase, the parties typically collaborate to create, evaluate, and refine the prototype, often setting specific criteria for success and timelines for completion. This clause ensures that both parties have a clear understanding of expectations and deliverables before moving to full-scale production, thereby reducing the risk of misunderstandings and costly errors later in the project.
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.
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.
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.
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.
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.
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...