INTEL ARCHITECTURE FOCUS Sample Clauses

INTEL ARCHITECTURE FOCUS. Streamline promises to (i) only implement the portal concept for IA-based computers, (ii) introduce new innovations in non-portal interfaces (browsers) for IA at least as early as for any other platform and (iii) develop * Confidential treatment requested back end technology solutions on IA. All non-portal (browser) features will be readily useable by IA and new features will be optimized for IA or specially adapted to run on IA. The focus described in this Section would last at least through the later of StreamLine's * or * However, Streamline would retain the ability to develop other technology solutions on their own, or with other parties, as Streamline sees fit. Intel may provide input for these efforts. This provision shall not survive termination of the Agreement on account of breach or nonperformance by Intel.
AutoNDA by SimpleDocs

Related to INTEL ARCHITECTURE FOCUS

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

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

  • SCOPE OF ARCHITECT’S BASIC SERVICES 3.1 The Architect’s Basic Services consist of those described in this Article 3 and include usual and customary structural, mechanical, and electrical engineering services. Services not set forth in this Article 3 are Supplemental or Additional Services. § 3.1.1 The Architect shall manage the Architect’s services, research applicable design criteria, attend Project meetings, communicate with members of the Project team, and report progress to the Owner. § 3.1.2 The Architect shall coordinate its services with those services provided by the Owner and the Owner’s consultants. The Architect shall be entitled to rely on, and shall not be responsible for, the accuracy, completeness, and timeliness of, services and information furnished by the Owner and the Owner’s consultants. The Architect shall provide prompt written notice to the Owner if the Architect becomes aware of any error, omission, or inconsistency in such services or information. § 3.1.3 As soon as practicable after the date of this Agreement, the Architect shall submit for the Owner’s approval a schedule for the performance of the Architect’s services. The schedule initially shall include anticipated dates for the commencement of construction and for Substantial Completion of the Work as set forth in the Initial Information. The schedule shall include allowances for periods of time required for the Owner’s review, for the performance of the Owner’s consultants, and for approval of submissions by authorities having jurisdiction over the Project. Once approved by the Owner, time limits established by the schedule shall not, except for reasonable cause, be exceeded by the Architect or Owner. With the Owner’s approval, the Architect shall adjust the schedule, if necessary, as the Project proceeds until the commencement of construction. § 3.1.4 The Architect shall not be responsible for an Owner’s directive or substitution, or for the Owner’s acceptance of non-conforming Work, made or given without the Architect’s written approval. § 3.1.5 The Architect shall contact governmental authorities required to approve the Construction Documents and entities providing utility services to the Project. The Architect shall respond to applicable design requirements imposed by those authorities and entities. § 3.1.6 The Architect shall assist the Owner in connection with the Owner’s responsibility for filing documents required for the approval of governmental authorities having jurisdiction over the Project.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Technology Transfer Subject to the terms of the Development Supply Agreement, as soon as reasonably practicable, but in no event later than the fifth (5th) anniversary of the Effective Date, Alnylam shall initiate a technology transfer to MedCo, or to its Third Party manufacturer(s) of Licensed Product, selected by MedCo and reasonably acceptable to Alnylam, of Alnylam Know-How that is reasonably necessary or useful for the Manufacture of the Licensed Product, and shall make available its personnel on a reasonable basis to consult with MedCo or such Third Party manufacturer(s) with respect thereto, all at MedCo's expense, including the Costs reasonably incurred by Alnylam in connection with such technology transfer activities. MedCo shall reimburse Alnylam such Costs incurred with respect to such Manufacturing technology transfer within [**] days after receipt of an invoice therefor. Alnylam and its Affiliates shall keep complete and accurate records in sufficient detail to enable the payments payable hereunder to be determined. Alnylam shall not be required to perform technology transfer to more than one Third Party manufacturer for each stage of the Licensed Product supply chain (i.e., Bulk Drug Substance, Bulk Drug Product and Finished Product). Promptly after MedCo's written request, Alnylam shall use Commercially Reasonable Efforts to assign to MedCo any manufacturing agreement between Alnylam and a Third Party that is solely related to the manufacture of Licensed Products. Such assignment shall be subject to the terms and conditions of such agreement, including any required consents of such Third Party and MedCo's written agreement to assume all the obligations of Alnylam under such agreement to be undertaken after such assignment, but Alnylam shall remain solely responsible for its obligations under such agreement arising prior to such assignment. Except as provided in the immediately preceding sentence, MedCo shall be solely responsible for contracting with such Third Party manufacturer (and any other Third Party manufacture to whom Alnylam has initiated technology transfer as set forth in this Section 5.3) for the supply of such Licensed Product and Alnylam shall have no obligations under such agreement between MedCo and such Third Party manufacturer. Alnylam shall use Commercially Reasonable Efforts to obtain any such consent in a form reasonably acceptable to MedCo.

  • Project Management Plan Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan and

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