CodeStream Workbench Sample Clauses

CodeStream Workbench. Notwithstanding any provision to the contrary provided herein or elsewhere, Purchaser shall be entitled to notify the Company of its election to exclude from, or to include in, the Purchased Business the items listed under “CodeStream Workbench”in Chapter C of Exhibit 1 (all the assets and liabilities listed in the mentioned paragraph are hereby referred to as “CodeStream Workbench”). Such notice may be submitted by the Purchaser not later than 30 days following the date of the First Closing, after the Company has allowed Purchaser’s representatives to perform a technological, legal, financial and business due diligence check. In the event that Purchaser elects to include CodeStream Workbench in the Purchased Business, it shall be considered as part of the Purchased Business from the date of the First Closing; in the event that Purchaser elects to exclude CodeStream Workbench from the Purchased Business, it shall be considered as excluded business listed under Chapter B of Exhibit 1 effective from the date of the First Closing. Upon the end of the 30 day period, regardless of the Purchaser’s decision to include Codestream Workbench in the Purchased Business or not, the Purchaser shall pay the costs of continuing development, in any event not to exceed £15,000 but not be further responsible for any additional costs or liabities associated with the CodeStream Workbench. If the Purchaser decides to include CodeStream Workbench in the Purchased Business, it shall be responsible for all costs associated with the CodeStream Workbench from the First Closing which will be disclosed to the Purchaser in writing. It is hereby clarified, that in no event is Purchaser obligated to pay any additional consideration regarding the foregoing and regarding Codestream Workbench, regardless of the inclusion or exclusion of CodeStream Workbench. Whether Codestream WorkBench is excluded from, or included in, the Purchased Buisness, by signing this agreement, the Company assign all Intellectual Property in such source code to the Company, and the source code of Codestream WorkBench shall be transferred to BluePhoenix (for no additional consideration). The Company and Indemnifying Shareholders make no warranty nor give any indemnity relating to the Intellectual Property relating to Codestream WorkBench. The Purchaser shall be given the source code, design documents, and all other relevant materials of the software relating to Codestream Workbench.
View Source

Related to CodeStream Workbench

  • Contract Database Metadata Elements Title: Sayville Union Free School District and Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU), Local 424 (2011) Employer Name: Sayville Union Free School District Union: Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU) Local: 424 Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 6131 Unit Size: 55 Number of Pages: 24 For additional research information and assistance, please visit the Research page of the Catherwood website - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/library/research/ For additional information on the ILR School - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/ 55 People TABLE OF CONTENTS ARTICLE Page XXII ANNUAL LEAVE DAYS 14 XXV BREAKS 18 XXVI CIVIL SERVICE LAW ARTICLE SECTION 75 18 XXVIII DURATION 19 XIV EMERGENCY WORK 11 XXI FOUL WEATHER CLOTHING 14 XI GRIEVANCE PROCEDURE 9 XVI HIGHER JOB CLASSIFICATION 12 XVIII HOLIDAYS 13 XV HOLIDAY AND WEEKEND BUILDING CHECKS 12 V INSURANCE 4 X LAYOFF, DISPLACEMENT AND RECALL ORDER 8 VII MANAGEMENT RIGHTS 7 XXVII MISCELLANEOUS 19 XVII NOTICES OF PROMOTIONS 13 XIII OVERTIME 10 II PAYROLL DEDUCTIONS 1 III PERSONNEL FILES 2 XXIV PHYSICAL EXAMINATIONS 18 XXIII RETIREMENT 16 IX STRIKES AND LOCKOUTS 7 XIX VACATIONS 13 XX VISITATION 14 IV WAGES 3 VI WORKERS' COMPENSATION 6 XII WORKWEEK 10 VIII WRITTEN BOARD POLICY 8 APPENDIX A 20 4/20/2016 AGREEMENT made and entered into this day of November 2013 between the SAYVILLE UNION FREE SCHOOL DISTRICT (hereinafter referred to as the “District”) and United Public Service Employees Union, ▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇, ▇▇▇▇▇▇▇▇▇▇, N.Y. 11779 (hereinafter referred to as the “Union”).

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

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

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.