PS&E Package Sample Clauses

PS&E Package a. 30% Plans Submittal: • One set of 11” x 17” plan sheets for the State’s district review. • Estimate of construction cost. • Engineer’s internal QC markup set.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
PS&E Package. The Engineer shall submit: A 3D model with each milestone submittal, if applicable and if requested by the State. The 3D model, created using Bentley’s and/or 3D MicroStation\Civil tools, shall have detail to verify the design.
Sample 1Sample 2Sample 3See All (4)
PS&E Package. The Engineer shall submit:
Sample 1
PS&E Package. DocuSign Envelope ID: CCFE3302-82A5-48DE-9B9A-8BCFBEBFCC46 The Engineer shall submit: A 3D model with each milestone submittal, if applicable and if requested by the State. The 3D model, created using Bentley’s and/or 3D MicroStation\Civil tools, shall have detail to verify the design.
Sample 1
PS&E Package. The 60% design PS&E package will be revised and further developed to incorporate comments from the City’s review of the 60% design. Develop design plans, contract documents, technical specifications, and opinion of cost to 95% design level. At the 95% design level, the drawings and specifications are essentially complete with only minor details left to resolve. Changes required after this submittal should be minor and result from permit reviews, City comments, QA/QC input, and proofreading of the final documents. Substantial changes after the 95% design shall not be permitted unless directed by City and may require additional City review.
Sample 1

Related to PS&E Package

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where EveryCall has requested an Unbundled Loop and BellSouth uses Integrated Digital Loop Carrier (IDLC) systems to provide the local service to the end user and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to EveryCall. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for EveryCall (e.g. hairpinning):

  • ODUF Pack Rejection 6.4.1 Image Access will notify BellSouth within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes will be used. Image Access will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to Image Access by BellSouth.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Software Subscription Use Case Red Hat Storage Server for On- Premise Red Hat Storage Server for On-Premise is intended to be used as a storage system and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non- server hardware such as desktops or workstations. Red Hat Storage Server for On-Premise is intended for use on a dedicated System, Physical Node, Virtual Node or Virtual Guest; running other applications and/or programs of any type on the System, Physical Node, Virtual Node or Virtual Guest can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage Server for Public Cloud Red Hat Storage Server for Public Cloud is intended to be used as a storage system and will be supported only when used as a storage node. When running in Amazon Web Services, an EC2 M1 Large dedicated instance is required in order to be supported. Running other applications and/or programs of any type on the same instance can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage for Red Hat Enterprise Linux OpenStack Platform Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended to be used as a storage system with Red Hat Enterprise Linux OpenStack Platform and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non-server hardware such as desktops or workstations. Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended for use on a dedicated Physical Node; running other applications and/or programs of any type on the Physical Node can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Voice Grade Unbundled Copper Sub-Loop Unbundled Sub-Loop Distribution – Intrabuilding Network Cable (aka riser cable)

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • Completion of Review for Certain Review Receivables Following the delivery of the list of the Review Receivables and before the delivery of the Review Report by the Asset Representations Reviewer, the Servicer may notify the Asset Representations Reviewer if a Review Receivable is paid in full by the Obligor or purchased from the Issuer in accordance with the terms of the Basic Documents. On receipt of such notice, the Asset Representations Reviewer will immediately terminate all Tests of the related Review Receivable, and the Review of such Review Receivables will be considered complete (a “Test Complete”). In this case, the related Review Report will indicate a Test Complete for such Review Receivable and the related reason.

  • REVIEW OF CONTRACT DOCUMENTS 4.2.1 The Contractor shall carefully study and compare the Contract Documents and shall immediately report in writing to the Architect and the State any error, inconsistency or omission he may discover. The Contractor shall not be liable to the State or the Architect for any damage resulting from any such errors, inconsistencies or omissions in the Contract Documents. The Contractor shall perform no portion of the Work at any time without Contract Documents or, where required, approved Shop Drawings, Product Data or Samples for such portion of the Work.

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