Prototype Development Sample Clauses

The Prototype Development clause outlines the obligations and procedures for creating an initial version or model of a product or system before full-scale production or implementation. Typically, it specifies the scope of work, timelines, and performance criteria for the prototype, and may detail the responsibilities of each party regarding design, testing, and feedback. This clause ensures that both parties have a clear understanding of expectations and deliverables during the early stages of a project, reducing the risk of misunderstandings and facilitating smoother project progression.
Prototype Development. CryoTherm shall exclusively bear the costs for all prototype development of the Licensed Products within the Field of Use for the Term of this Agreement.
Prototype Development. Each Participant Company shall work diligently during a 10 week period of the Program (“Program Term”) to develop its Solution into a Prototype. Verizon, in its sole discretion, may extend or shorten the Program Term. Members of the Program Panel and industry professionals will mentor and advise each Participant Company throughout this process. Each Participant Company shall develop its Prototype at an offsite facility of its choosing that is procured and paid for by that Participant Company during the Program Term.
Prototype Development. SUMMARY DESCRIPTION: Receptors will use its best efforts to develop of a prototype sensing system built on the proof-of-principle from Phase I that will sub-type identify the influenza virus, especially H1N1, in a nasal swab or nasal wash sample. DELIVERABLE: LAB-SCALE PROTOTYPE with report, device and demonstration. PHASE II PROJECT PLAN: 1. DEVELOPMENT AND APPLICATION OF HTS SYSTEM (2 months) • Development of magnetic bead, dendrimer, virus system in 384-well format for high-thoughput selection of bead / dendrimer pairs. • Application to HTS to define critical variable parameters. 2. DEVELOPMENT OF DATA GRID TO EVALUATE THE KEY VARIABLES OF CARA, DENDRIMER, VIRUS SUB-TYPE AND MATRIX (4 months) • Application of the HTS to develop the single and multiplexed data. • Database evaluation of CARA and peptide-dendrimer competitor pairs for single and multiplexed sub-type detection. • Selection of candidate single and multiplexed CARA and competitor pairs optimized with respect to the virus sub-type and matrix variables. 3. PROOF-OF-CONCEPT DEMONSTRATION OF THE MULTIPLEXED, SUB-TYPE IDENTIFICATION DEVICE (2 months) • Candidate to lead selection and optimization. • Multiplexed lead integration and point-of-care protocol in matrix (2 months) 4. LAB-SCALE PROTOTYPE (2 months) • Prototype demonstration. • Lab-scale SOP’s PHASE II TIMELINE: March 1, 2010 — December 31, 2010 (10 months) 1. DEVELOPMENT HTS SYSTEM (2 months) MAR-APR 2. DEVELOPMENT OF DATA GRID (4 months) MAY-AUG 3. PROOF-OF-CONCEPT DEMONSTRATION (2 months) SEP-OCT 4. LAB-SCALE PROTOTYPE (2 months) NOV-DEC This RESTRICTED STOCK AGREEMENT (the “Agreement”) is made as of April 22, 2010 (the “Effective Date”) between PositiveID Corporation, a Delaware corporation (the “Company”) and Receptors LLC, a Minnesota limited liability company (“Receptors”).
Prototype Development. We have built a prototype web application that uses the Onassis Ontology and EBTO structure to guide users in identifying legal risks and proactive controls during the negotiation and generation of a contract 8. For a visual overview of the user interface and the user interaction we refer to 9. The prototype contains several web pages with input forms and interaction elements to interactively draft a freelancer contract, based on a text template and contract-specific ques- tions. After the freelancer and the client have answered the contract-specific questions, a legal expert uses those answers to fill in the text in a template con- tract. The expert may add legal risks and possible proactive controls next to a visible predefined set of specified risks. Additional questions can be interac- tively asked to both the client and the freelancer. These questions can be about the (new or predefined) risks, proactive controls, or about initial questions on the contract to which client and freelancer provided conflicting answers, e.g., about the milestones or the payment, or about the need for negotiation/media- tion. Finally, the questions, answers, risks, controls, and legal text are stored as data consisting of semantic subject+predicate+object triples (in Turtle *.ttl for- mat) specified according to the Onassis Ontology and EBTO (or ’model’). We explain the stored data, which help in isolating PCD, in more detail with exam- ples of data actually generated by the prototype in the Results Section in 10.
Prototype Development. CONFIDENTIAL TREATMENT REQUESTED 4
Prototype Development 

Related to Prototype Development

  • Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

  • Design Development An interim step in the design process. Design Development documents consist of plans, elevations, and other drawings and outline specifications. These documents will fix and illustrate the size and character of the entire project in its essentials as to kinds of materials, type of structure, grade elevations, sidewalks, utilities, roads, parking areas, mechanical and electrical systems, and such other work as may be required.

  • Program Development NWESD agrees that priority in the development of new applications services by WSIPC shall be in accordance with the expressed direction of the WSIPC Board of Directors operating under their bylaws.

  • Curriculum Development This includes the analysis and coordination of textual materials; constant review of current literature in the field, some of which are selected for the college library collection, the preparation of selective, descriptive materials such as outlines and syllabi; conferring with other faculty and administration on curricular problems; and, the attendance and participation in inter and intra-college conferences and advisory committees.

  • Supplier Development If the Buyer identifies problems in supplier performance based on supplier monitoring, he shall initiate appropriate improvement measures at the Supplier. Buyer shall pursue the possibilities of continuous improvement of the Supplier. The supplier audit is a form of supplier development; the exchange of information and experience between the Buyer and the Supplier also serves this purpose.