Development and Support Clause Samples

Development and Support. DHS reported early in the development of the Pinnacle Plan that public sector resources were strained due to the growing number of children in ▇▇▇▇▇▇ care. To develop and support more ▇▇▇▇▇▇ homes, DHS implemented a set of short-term strategies while it developed a longer-term reconceptualization of its business model for recruiting, assessing, supporting and certifying ▇▇▇▇▇▇ homes. In 2012 and continuing through 2013, DHS approved staff overtime, hired temporary staff, ▇▇▇▇▇▇▇ retirees and contracted with vendors to complete ▇▇▇▇▇▇ care home studies. Additionally, DHS increased the availability of ▇▇▇▇▇▇ parent pre-service trainings in order to increase convenience and options for families. As articulated in its Pinnacle Plan, DHS’ chief longer-term strategy involved the privatization of non-▇▇▇ ▇▇▇▇▇▇ home development and support. DHS planned to continue to manage the pool of public agency ▇▇▇▇▇▇ homes that it had already developed and to utilize those homes for children’s placements. Moving forward, DHS articulated that private agencies would develop and support new ▇▇▇▇▇▇ homes after contracts were awarded, creating a bifurcated ▇▇▇▇▇▇ care system that would require close coordination between DHS and private agencies. In order to select the private agencies authorized to undertake this work with ▇▇▇▇▇▇ homes, DHS committed in its Pinnacle Plan to administer a contract bidding process through the issuance of a Request for Proposals (RFP) with the bidding process to be completed by September 30, 2012. However, DHS did not post the RFP on the state’s Central Purchasing website until October 29, 2012 with a proposal deadline of December 3, 2012, two months late. Throughout the RFP process, bidders expressed concerns to DHS leadership regarding what they believed to be a lack of bidder input concerning RFP outcomes, unrealistic performance metrics and fiscal penalties for agencies if certain performance targets were missed. One hundred twenty proposals were submitted in response to the RFP and DHS selected ten agencies to provide ▇▇▇▇▇▇ care services in 26 of its 29 child welfare districts. On April 12, 2013, DHS leadership cancelled the ten contracts, believing its longer-term goals identified in the Pinnacle Plan would be compromised by the awards. In its notice of cancellation to the contracted agencies, DHS explained that its original RFP language was too prescriptive and worked against provider creativity, flexibility and capability. DHS further obser...

Development and Support. 3.4.1 The Contractor shall participate in the implementation and development of NAVAIR sponsored initiatives for continuous improvements such as Airspeed, Theory of Constraints, Six Sigma and Reliability-Centered Maintenance. 3.4.2 The Contractor shall support the NATOPS program for assigned aircraft T/M/S. Submit NATOPS change recommendations as necessary. Support NATOPS Model Manager with technical information and recommendations regarding aircraft or system characteristics. Support and attend NATOPS conference when directed by NTWL/ NTWP Squadron Commanding Officer. Provide ground, simulator, and in-flight training to Fleet Units as aircraft and systems transition from development to Operational Test (OT) and/or Initial Operational Capability (IOC). 3.4.3 The Contractor shall support HAZREP and Mishap Investigations. Provide technical, aeronautical, and human factors insights to Aviation Mishap Boards. Support NAVAIR Aeromechanics Safety Investigation Support Team (ASIST) efforts with analysis of mishap data and through piloted simulations of mishap sequence of events.

Development and Support. Developer shall not incorporate or combine any Open Source Technology into or with any Update or Deliverable without first obtaining Cisco’s prior written approval. Developer shall strictly adhere to the following procedure with regard to Open Source Technology, Updates, and Deliverables (a) Developer shall submit a request to Cisco which shall contain: (i) engineering data in support of the request, (ii) detailed explanation of how the Open Source Technology will interact with any Cisco Property or proprietary technology of Cisco or any third party incorporated in the Update or Deliverable or any component thereof or which directly interfaces with the Update or Deliverable, (iii) a copy of the license governing the use and distribution of the Open Source Technology, and (iv) detailed analysis of whether the use of the Open Source Technology would, (A) create obligations, or purports to create obligations, for Cisco or Developer with respect to any Update or Deliverable or proprietary technology of Cisco or Developer, or (B) grant, or purports to grant, to any third party any rights or immunities under Cisco Property or Licensed Property or proprietary technology (collectively, “Contamination”). At Cisco’s request, Developer shall cooperate with Cisco in order to determine if incorporation of any Open Source Technology would result or has resulted in any Contamination. (b) Within thirty (30) days after receiving such request, Cisco shall respond by: (i) approving the request, (ii) disapproving the request, or (iii) extending the deadline for the approval or disapproval period for an additional ten (10) business days. If Cisco disapproves the request, then any timelines in the Statement of Work associated with completion of the applicable Deliverable will be extended as necessary to allow Developer to find an alternative or work-around for the Open Source Technology contained in such request and, if applicable, to resubmit the request to Cisco in accordance with this Section 2.12.2. (c) Developer shall list all approved Open Source Technology incorporated into or combined with the Deliverable in the applicable Statement of Work(s) or engineering change request before Cisco approves such Statement of Work(s) or engineering change request.

Development and Support. ▇▇▇▇▇▇ shall design and develop an Integration Module together with supporting user documentation for each platform, operating system, or computing environment supported by ▇▇▇▇▇▇ for LoadMaster® dispatch software ("Deliverables") in accordance with the timetable set forth in Schedule 1 attached hereto and incorporated herein.

Development and Support. To the extent reasonable and practical, Genesis shall use reasonable efforts to maintain, support and enhance the Genesis Product and The Genesis Server as is necessary to effect the purposes and objectives of this Agreement. Genesis will maintain and support the Licensees to no less an extent than that which it provides maintenance and support to its other customers.

Development and Support. Category Requirement 3.1 Development Requirements Integrator shall develop and maintain one or more Interfaces that will transfer Data from the Product(s) identified in Exhibit C to the corresponding ▇▇▇▇▇▇ Mae Service(s) identified in the same Exhibit C. The parties may develop separate Exhibits C for various combinations of Products and ▇▇▇▇▇▇ ▇▇▇ Services for which one or more Interfaces are to be developed. Development of the Interface(s) (and, if applicable, the Product) and any modifications, will occur solely at Integrator’s own direction, in accordance with: • the Specifications, • any requirements related to design, features, functions, capability and timetable communicated in writing to Integrator by ▇▇▇▇▇▇ Mae as being required for sound, successful and timely integration of the Product with the Service and • any requirements and processes provided by ▇▇▇▇▇▇ ▇▇▇ to Integrator from time to time. 3.2 Responsibility for Interface Integrator is solely responsible for: • the accuracy, technical sufficiency and functionality of the Interface, • all maintenance and support necessary to maintain the Interface and the Product in continuous working order and at all times fully compatible with the most current version of the ▇▇▇▇▇▇ Mae Service, • resolving all Performance Incidents, and • all costs and expenses associated with the development, operation and maintenance of the Interface and the Product. 3.3 Software Provider IDs Integrator must, prior to releasing the initial version of the Interface and thereafter prior to releasing any new version of the Product or Interface, incorporate into the Interface (or Product) a unique software provider identification number obtained from ▇▇▇▇▇▇ ▇▇▇. Category Requirement This identification number will enable ▇▇▇▇▇▇ Mae to identify transmissions as coming from Integrator. ▇▇▇▇▇▇ ▇▇▇ may change the unique software provider identification number from time to time. 3.4 Codified Findings If Integrator elects to implement CFF Software, the following terms apply: • Integrator develops the CFF Software at its own risk, cost and expense and is solely responsible for the copying, availability and use of Data by and via the CFF Software, as well as all associated liability. • Codified Findings are subject to change at any time. • Upon receipt of any changes to Codified Findings or related Specifications, Integrator will promptly update the CFF Software in order to conform the same to the most recent version of Codified Fin...

Development and Support. 2.4.1 CAMBRIDGE shall use commercially reasonable efforts to cooperate with ONYX, at ONYX’s reasonable expense, on all matters related to ONYX’s efforts to obtain and maintain Regulatory Approval(s) to market and sell Products containing the Material in the different territories to the extent such matters relate directly to the Manufacture of the Material hereunder, including without limitation, complying with applicable provisions of the Quality Agreement. 2.4.2 CAMBRIDGE, under the direction of and with the participation of ONYX, shall develop and validate a commercial Manufacturing process for the Material in accordance with a separate statement of work. Validation shall comply with FDA or any applicable Regulatory Authority [*] = Certain confidential information contained in this document, marked by brackets, has been omitted and filed separately with the Securities and Exchange Commission pursuant to Rule 24b-2 of the Securities Exchange Act of 1934, as amended. guidelines, and shall include three commercial scale Lots in accordance with such separate statement of work. CAMBRIDGE shall provide samples meeting ONYX’s Specifications from at least three different consecutive Lots in accordance with such separate statement of work. 2.4.3 Both Parties agree to work diligently to develop and validate CAMBRIDGE’S commercial Manufacturing process for the Material in accordance with a separate statement of work which when signed by the Parties shall become a part of this Agreement on the agreed-upon timeline as set forth in Exhibit C. 2.4.4 CAMBRIDGE shall provide documentation to ONYX demonstrating approval from FDA to Manufacture the Material, and shall continue to comply with all applicable FDA or any applicable Regulatory Authority regulations.

Development and Support. Server Support - Interface Development - Estimated Development Portion - Production Support - 10 hours per month Provide ordering and buying back foreign currency (cash) and drafts for FCBSC's customers. (- FCBSC branch associates will phone requests into the FCBNC's International Department (- FCBNC's International Department will provide an exact amount being debited from the customer's account during the phone call. (- FCBNC will provide FCBSC's customer a debit advice in the mail for all foreign currency orders. (- FCBNC will provide the currency rate to FCBSC prior to FCBSC purchasing currency from the customer. (- FCBSC will buy back currency from their customer(s) and send the currency to FCBNC's International Department. (- FCBSC will be responsible for crediting their customer's account for the returned currency and debiting their 9040994990 GL. (- FCBSC will provide FCBNC's International Department a copy of the GL ticket noting the customer's name, account number, currency/amount purchased and rate used to purchase currency. (- FCBSC will debit FCBSC customer's account for any fees (drafts only).

Development and Support. (a) ▇▇▇▇ will create and provide to Licensee in HTML format the Pediatric Illustrated Encyclopedia (the "Content Pages"). (b) Each Content Page will have at least one ▇▇▇▇ icon with an appropriate ▇▇▇▇ trademark or ▇▇▇▇ Logo, as specified for appearance and placement according to Exhibit 2. During the Term, Licensee will identify ▇▇▇▇ as the provider of the Pediatric Illustrated Encyclopedia and shall post the ▇▇▇▇ Logo on the home page of the Licensee Web Site, which icon will include a link to the Content Pages. (c) ▇▇▇▇ will provide to Licensee access to the Health Images and Presentations. Licensee may select and use items from the Health Images and Presentations to annotate the content owned by Licensee and provided on the Licensee Web Site ("Licensee Content"). During the Term, Licensee will identify ▇▇▇▇ as the provider of any portion of the Health Images and Presentations used by Licensee in the Licensee Content.