We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Basic Configuration Sample Clauses

Basic Configuration. 27 The Schematic Design included in the RIDs conveys the general intent and layout of the 28 Project. The Basic Configuration means the following: 29 A. Those portions of the Schematic Design that depict the following: 30 1. The number and types of lanes; 31 2. The approximate location of shoulders; 32 3. The approximate location of service interchanges; 33 4. The approximate location of grade separations; 34 5. The number of entrance and exit ramps at each service interchange; 35 6. A bridge, existing or new, at 63rd Avenue that provides connectivity to the Xxxxxxxx 00 Xxxxx Xxxxxxxx Xxxx development on the south (see zoning document Xxxxxxxx 00 Xxxxx Xxxxxxxx Xxxx Development.PDF in the RIDs) and to 63rd Avenue on the 38 north; 39 7. The approximate location of the bridges for multiuse crossings; 40 8. The approximate location and number of ramp lanes at I-10 Papago Freeway system 41 interchange; 42 9. The approximate location of frontage roads; 1 B. Within the lines delineating the outside boundaries of the Project set forth in the 2 Schematic ROW, as such boundaries may be adjusted from time to time in accordance 3 with the Contract Documents (including adjustments for ADOT Additional Properties, 4 Developer-Designated ROW and avoided parcels or partial parcels, in whole or in part); 5 C. The control of access limits as set forth in Section DR 440 of the TPs; 6 D. The provision of maintenance roads; 7 E. A pedestrian crossing at the Xxxxxx Street alignment (mid-mile between Xxxxxxxx 0 Xxxx xxx Xxxxx Xxxxxxx Xxxx; 9 F. A connector road at the Durango Street alignment (just south of the Roosevelt Xxxxxxxxxx 00 Xxxxxxxx xxxxx) between the northbound and southbound frontage roads; and 11 G. The avoidance of the environmentally sensitive areas as further described in Section DR 12 420 of the TPs.
Sample 1Sample 2Sample 3See All (9)
Basic Configuration. 28 The Schematic Design included in the RIDs conveys the general intent and layout of the 29 Project. The Basic Configuration means those portions of the Schematic Design that depict: 30 A. The Schematic ROW and control of access limits as set forth in Section DR 440 of the 31 TPs; 32 B. The number and types of lanes; 33 C. The approximate location of Shoulders;
Sample 1
Basic Configuration. The RTT-MBT model checker currently depends on the following basic con- figuration items: • the unrolling depth k ≥ 0 • the multi-model M The unrolling depth and the LTL formula have their obvious meaning. The multi-model is the overall system model that is exported from Modelio via XMI. This multi-model contains a connection diagram, which expresses which ports and signals are used as inputs and outputs of each sub-model. Con- figuring these items is the only necessity for executing the RTT-MBT model checker. Details regarding the configuration of these parameters via the command-line interface and the INTO-CPS application, respectively, are given in Sect. 4.2 and Sect. 4.3.
Sample 1
Basic Configuration. ‌ 9 The Basic Configuration is the Project elements referenced in the Contract Documents including 10 dimensions, details, access requirements, criteria, restrictions, and the following roadway and bridge 11 features:
Sample 1
Basic Configuration. 30 The Schematic Design included in the RIDs conveys the general intent and layout of the Project.
Sample 1
Basic Configuration. 29 The Schematic Design included in the RIDs conveys the general intent and layout of the 30 Project. The Basic Configuration means the following: 31 A. Those portions of the Schematic Design that depict the following: 32 1. The number and types of lanes; 33 2. The approximate location of Shouldersshoulders; 34 3. The approximate location of service interchanges; 35 4. The approximate location of grade separations; 36 5. The number of entrance and exit ramps at each service interchange; 37 6. A bridge, existing or new, at 63rd Avenue that provides connectivity to the Xxxxxxxx 00 Xxxxx Xxxxxxxx Xxxx development on the south (see zoning document Xxxxxxxx 00 Xxxxx Xxxxxxxx Xxxx Development.PDF in the RIDs) and to 63rd Avenue on the 40 north; 41 7. The approximate location of the bridges for multiuse crossings; 1 8. The approximate location and number of ramp lanes at I-10 Papago Freeway system 2 interchange; 3 9. The approximate location of frontage roads; 4 B. Within the lines delineating the outside boundaries of the Project set forth in the 5 Schematic ROW, as such boundaries may be adjusted from time to time in accordance 6 with the Contract Documents (including adjustments for ADOT Additional Properties, 7 Developer-Designated ROW and avoided parcels or partial parcels, in whole or in part); 8 C. The control of access limits as set forth in Section DR 440 of the TPs;
Sample 1

Related to Basic Configuration

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • AIRCRAFT CONFIGURATION The guarantees defined below ("the Guarantees") are applicable to the A330-200 Aircraft as described in the Technical Specification ***, as amended by the Specification Change Notices ("SCN's") for: i) implementation of engines: GENERAL ELECTRIC CF6-80E1A3

  • Layout DocuSign Envelope ID: 7E35C160-7769-4E34-87BF-0A3AF65FF97E a. Estimate and quantity sheet (1) List of all bid items (2) Bid item quantities (3) Specification item number (4) Paid item description and unit of measure b. Basis of estimate sheet (list of materials) c. General notes and specification data. d. Condition diagram (1) Highway and intersection design features (2) Roadside development (3) Traffic control including illumination e. Plan sheet(s) (1) Existing traffic control that will remain (signs and markings) (2) Existing utilities (3) Proposed highway improvements (4) Proposed installation (5) Proposed additional traffic controls (6) Proposed illumination attached to signal poles. (7) Proposed power pole source f. Notes for plan layout g. Phase sequence diagram(s) (1) Signal locations (2) Signal indications (3) Phase diagram (4) Signal sequence table (5) Flashing operation (normal and emergency) (6) Preemption operation (when applicable) (7) Contact responsible Agency to obtain interval timing, cycle length and offset h. Construction detail sheets(s) (1) Poles (State standard sheets) (2) Detectors (3) Pull Box and conduit layout (4) Controller Foundation standard sheet (5) Electrical chart i. Marking details (when applicable)

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

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • SERVICE LEVEL DESCRIPTION The Fund Accounting Agreement is hereby amended by deleting the Service Level Description attached thereto and replacing it in its entirety with the Service Level Description attached hereto.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

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

  • Changes to Specifications All Specifications and any changes thereto agreed to by the parties from time to time shall be in writing, dated and signed by the parties. Any change to the Process shall be deemed a Specification change. No change in the Specifications shall be implemented by Catalent, whether requested by Client or requested or required by any Regulatory Authority, until the parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change (including any change to Unit Pricing). Catalent shall respond promptly to any request made by Client for a change in the Specifications, and both parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. As soon as possible after a request is made for any change in Specifications, Catalent shall notify Client of the costs associated with such change and shall provide such supporting documentation as Client may reasonably require. Client shall pay all costs associated with such agreed upon changes. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control. Catalent reserves the right to postpone effecting changes to the Specifications until such time as the parties agree to and execute the required written amendment.

  • Customization ICP shall customize the Customized Site and Customized Programming for AOL Members as follows: (a) ICP shall customize and co-brand the Customized Site and Customized Programming for distribution over the AOL Properties listed in Exhibit A-1 using AOL's design guideline templates and co-branding requirements, including by (x) displaying on each page of the Customized Site framing (e.g., C-frame, side navigation/menu bars, headers and footers) of size and type determined by AOL and which contain branding for the applicable AOL Property and ICP as determined by AOL and, as determined by AOL, links to the applicable AOL Property, a search box and/or promotional spaces to be programmed by AOL, and (y) matching the look and feel of the applicable AOL Property on the Customized Site. In addition, ICP shall comply with any customization and co-branding requirements set forth on Exhibit A. ICP shall make any changes to the customization and/or co-branding of the Customized Site to conform to the standard requirements of any AOL Property or otherwise reasonably requested by AOL during the Term. (b) ICP shall ensure that AOL Members accessing the Customized Site and/or Customized Programming or linking to any ICP Interactive Site from the Customized Site or Customized Programming do not receive advertisements, promotions or links (i) for any entity reasonably construed to be in competition with AOL or the applicable AOL Property, (ii) in a category in which AOL or the applicable AOL Property has an exclusive or other preferential relationship (but this limitation only applies to the Team Pages, Stars Pages, and the Extreme Main Page), or (iii) otherwise in violation of the applicable AOL Property's then- standard advertising policies. ICP shall ensure that all Advertisements sold by ICP or its agents comply with all applicable federal, state and local laws and regulations. (c) Within the Customized Site, ICP shall use and/or feature solely AOL's tools and technology for the following utilities and functionality: instant messaging, chat, personalized news service, calendaring (including "click-to-add event" functionality associated therewith), web page community services, message boards, and commerce/content aggregation services (e.g., Shop@AOL and local content) ("AOL Tools"). If any such AOL Tool is not made available for use on the Customized Site within a reasonable time upon ICP's request, ICP shall be permitted to utilize on the Customized Site similar tools and technology provided [*], provided that such tools and technology are not [*] and no links or promotions for such third party appear on the Customized Site and, provided, further that ICP will convert such tools and technology over to the corresponding AOL Tool once such AOL Tool is made available. In addition, the Customized Site shall not (x) provide or promote any email service, or (y) use or feature the tools or technology of any Interactive Service other than AOL. (d) Within the AOL Service, ICP shall host the Main Teams Page, Team Aggregate Screens, Main Stars Page, Stars Aggregate Screens and the Extreme Main Page of the Customized Programming and Customized Site under a domain name co-branded with the applicable AOL Property as follows: xxxxxxxxxxxxx.xxx.xxx and all other pages within the Customized Site will have domain names with applicable ICP Property extension such as xxx.xxxxxxxxxxxxx.xxx or xxxxxxx.xxx.xxxxxxxxxxxxxxx.xxx. Within all other AOL Properties, ICP shall host the Team Pages, Stars Pages and Extreme Online Area of the Customized Programming and Customized Site under a domain name co-branded with the applicable AOL Property as follows: xxxxxxxxxxxxx.xxxxxxxx.xxx and all other pages within the Customized Site may have domain names such as xxxxxxxx.xxxxxxxxxxxxx.xxx. AOL will use commercially reasonable efforts to have [*] for traffic on the Team Pages within the AOL Service so long as such pages remain in Rainman format. With respect to traffic on any other pages relating to the Customized Site or Customized Programming which appear on an AOL URL, AOL will use commercially reasonable efforts, including by providing any necessary [*], to help [*]. For pages appearing on an ICP URL, then AOL will use commercially reasonable efforts, including by providing any necessary [*], to help ICP [*] and ICP shall used [*].

Most Referenced Clauses

Most Referenced Definitions