Proposed ATS Architecture Sample Clauses

Proposed ATS Architecture. Vendor proposed architecture positions the County for the future. Open System Environment and Operating System and County IT support The converted system will run on Windows Server 2016 and virtual machines. Vendor has defined server sizes and storage tiers based in the current Orange County Office of Information Technology Service Catalog (xxxx://xxxxx.xxx/civicax/filebank/blobdload.aspx?BlobID=43549) for data center services to meet the requirement for County IT support. Vendor has made choices in Vendor’s architecture for MS SQL server 2016 and Windows Server 2016 operating system to drive to the best value to deliver upon the County’s requirements. The Vendor has chosen this approach based on Vendor’s understanding of the County’s technology standards. Vendor will work with the County to validate Vendor’s thoughts during the assessment phase of the re-platforming project.
AutoNDA by SimpleDocs

Related to Proposed ATS Architecture

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

  • Physical Architecture 59.2.1 CenturyLink's network architecture in any given local exchange area and/or LATA can vary markedly from another local exchange area/LATA. Using one or more of the NIMs herein, the Parties will agree to a physical architecture plan for a specific LATA, or if appropriate based on other requirements in Section 59, Local Calling Area. The physical architecture plan, as described in the Local Interconnection POI Profile, will be discussed during joint implementation planning. CLEC and CenturyLink agree to Interconnect their networks through existing and/or new Interconnection Facilities between CLEC switch(es) and CenturyLink's End Office Switch(es) and/or Tandem Switch(es). The physical architecture plan will be in accordance with Forecasting and Planning requirements in Article IV.

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

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

  • Architect/Engineer (A/E) means a person registered as an architect pursuant to Tex. Occ. Code Xxx., Chapter 1051, as a landscape architect pursuant to Tex. Occ. Code Xxx., Chapter 1052, a person licensed as a professional engineer pursuant to Tex. Occ. Code Xxx., Chapter 1001 and/or a firm employed by Owner or a design-build contractor to provide professional architectural or engineering services and to exercise overall responsibility for the design of a Project or a significant portion thereof, and to perform the contract administration responsibilities set forth in the Contract.

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

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

  • Drawings and Specifications at the Project Site The Contractor shall keep at the Site at least one copy of the Contract Documents and Change Orders, all in good order and available to the Design Professional and to his representatives.

  • ROAD DIMENSIONS Purchaser shall perform road work in accordance with the dimensions shown on the TYPICAL SECTION SHEET and the specifications within this road plan.

  • Design Review At appropriate stages of design, documented reviews of the design results shall be planned and conducted. Participants at each Design Review shall include representatives of all functions concerned with the design stage being reviewed, as well as other specialist personnel, as required. Records of such reviews shall be maintained. Any computer software used to perform alternative calculations or verify clearances through the use of scale models or computer-aided design and drafting (CADD) techniques shall be validated before the use of the application, with validation documented in accordance with Section 2.2.15. In addition, at each submittal to IFA for review, Developer shall provide hand calculations that validate any calculations performed by computer software.

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