Pilot Deployment Sample Clauses

Pilot Deployment. For pilot deployment within WP1 we chose the cruise control system, an automotive system implemented in software which automatically controls the speed of a car. The cruise control system is part of the engine control software which controls actuators of the engine (e.g. injectors, fuel pumps, throttle valve) based on the values of specific sensors (e.g. gas pedal position sensor, air ow sensor, lambda sensor). Since the cruise control system automatically controls the speed of a car there are some safety aspects to be considered and it needs to fulfil a number of safety properties. For example, the cruise control system must be deactivated upon request of the driver or in case of a system fault. In the pilot deployment a methodology for applying Event-B was developed (see Section 2.1.4 and [D19] for details). The central aspect of the developed methodology was that the gap between the initial requirements document and the Event-B model is too big to be easily taken in one step. Therefore we used Problem Frames [J01] between the informal and the formal description of the system.
Sample 1
AutoNDA by SimpleDocs
Pilot Deployment. The deliverable [RD5] covers the DEPLOY WP3 activities since February 2009 until January 2010: • continuation of Event-­‐B modelling of BepiColombo SIXS/MIXS OBSW requirements, • specification of a realistic AOCS (Attitude and Orbit Control System), • precise Event-­‐B modelling of the AOCS, and • a lot of Event-­‐B proof activities in association with the modelling activities.
Sample 1

Related to Pilot Deployment

  • Deployment (a) In filling a position vacancy at a location NAV CANADA may proceed by the transfer of an employee at the same level.

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

  • Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

  • Preconstruction Phase Services Preconstruction Phase Services shall mean all services described in Article 3.1, and any similar services described in the Request for Proposals, including such similar services as are described in the Construction Manager at Risk’s Response to the Request for Proposals to the extent they are accepted by Owner, but excluding any Early Work. Early Work shall be considered part of Construction Phase Services.

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Building Commissioning Services The Owner may provide as a part of its testing services the Building Commissioning services involving the project’s HVAC and exhaust systems, temperature control systems, fire detection and alarm systems, emergency power and lighting system, fire suppression system, security locks and security locking control systems, food service equipment (if applicable), and laundry equipment (if applicable). In the event the Using Agency’s Program specifies additional commissioning services, the Owner shall procure such services as well. The Owner, through its Executive Administrator, may engage an independent Commissioning Authority. It is the intent of this Article that the Commissioning Authority enforce the requirements mentioned herein and certify that the systems and equipment listed all function properly prior to the initiation of each final inspection.

  • Design Development Phase Services 3.3.1 Based on the Owner’s approval of the Schematic Design Documents, and on the Owner’s authorization of any adjustments in the Project requirements and the budget for the Cost of the Work, the Architect shall prepare Design Development Documents for the Owner’s approval. The Design Development Documents shall illustrate and describe the development of the approved Schematic Design Documents and shall consist of drawings and other documents including plans, sections, elevations, typical construction details, and diagrammatic layouts of building systems to fix and describe the size and character of the Project as to architectural, structural, mechanical and electrical systems, and other appropriate elements. The Design Development Documents shall also include outline specifications that identify major materials and systems and establish, in general, their quality levels.

  • Commissioning Commissioning tests of the Interconnection Customer's installed equipment shall be performed pursuant to applicable codes and standards. If the Interconnection Customer is not proceeding under Section 2.3.2, the Utility must be given at least ten (10) Business Days written notice, or as otherwise mutually agreed to by the Parties, of the tests and may be present to witness the commissioning tests.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least thirty (30) days written notice to the SLDC and GUVNL, of the date on which it intends to synchronize the Power Project to the Grid System.

  • Synchronisation Commissioning and Commercial Operation 8.1 The Developer shall provide at least forty (40) days advanced preliminary written notice and at least twenty (20) days advanced final written notice to ESCOM of the date on which it intends to synchronize the Power Project to the Grid System.

Time is Money Join Law Insider Premium to draft better contracts faster.