Site Specific Test Plan (SSTP Sample Clauses

Site Specific Test Plan (SSTP. The Project Manager shall ensure that information needed to develop an accurate SSTP is provided to TSA Test Lead at the earliest opportunity, but no later than 90 days prior to requested testing date. Such documentation includes: ■ BHS Specifications ■ Controls Description and/or Description of Operation (if both exist then provide both) ■ E-Stop Zone Drawings ■ BHS Drawings Plan and Elevation Views ■ Phasing Plan Narrative and Phasing Plan Drawings ■ Construction and Testing Schedule All drawings shall be clearly visible and readable when plotted on Arch D Size Stock, All documents shall be submitted electronically (e.g. text documents in MS Word or PDF and drawings in AutoCAD [.dwg] or PDF.) Any system constraints that will prevent compliance with TSA testing and performance criteria should be disclosed as far in advance as possible to allow for evaluation of applicable waivers. Any restrictions on system availability and accessibility for testing shall be disclosed. Cutover plans including any phasing plans that will affect the Testing Contractor's ability to test the full system from ticket counters through the outbound/sortation system shall also be disclosed to allow for the development of an accurate SSTP. The Project Manager will have the opportunity to review and comment on SSTP in advance of testing. Comments and/or questions should be directed to the TSA Project Lead and the TSA Site Lead.
Sample 1
AutoNDA by SimpleDocs
Site Specific Test Plan (SSTP. The PROJECT SPONSOR shall ensure that information needed to develop an accurate SSTP is provided to TSA Test Acceptance Lead at the earliest opportunity, but no later than 100 days prior to the requested testing date. Required documentation includes: • The Site Planning Checklist • BHS Specifications • Controls Description and/or Description of Operation (if both exist then provide both) • Fail-safe and/or E-Stop Zone Drawings • BHS Drawings, Plan Views (with control stations and locations, Photoelectric Cell numbering and locations, and conveyor numbering) and Elevation Views • Sample CBIS Reports per PGDS shall be provided along with the Site Planning Checklist and full CBIS Reports shall be provided during ISAT testing and throughout the Run-In period. These reports shall meet the requirements described in PGDS. • Conveyor Motor Manifest • Installation Phasing Plan Narrative and Phasing Plan Drawings • Construction and Testing Schedule provided at 120, 90, 60, 30 and 14 days prior to ISAT. All drawings shall be clearly visible and readable when plotted on Arch D Size Stock. All documents shall be submitted electronically (e.g. text documents in MS Word or PDF and drawings in AutoCAD [.dwg] or PDF.) Any system constraints that will prevent compliance with TSA testing and performance criteria must be disclosed in writing to TSA as far in advance as possible to allow for evaluation of applicable waivers. Any restrictions on system availability and accessibility for testing shall be disclosed. Cutover plans including any phasing plans that will affect the TSA Acceptance Test Contractor’s ability to test the full system from ticket counters and curbside inductions (if applicable) through the outbound/sortation system shall also be disclosed to allow for the development of an accurate SSTP. Cutover plans that will result in multiple testing phases shall also be presented to the TSA COR in writing for review and approval prior to the Test Coordination Meeting and no later than 30 days prior to ISAT. The PROJECT SPONSOR will have the opportunity to review and comment on SSTP in advance of testing. Comments and/or questions shall be directed to the TSA COR and the TSA Site Lead Contractor.
Sample 1

Related to Site Specific Test Plan (SSTP

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

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

  • Acceptance Testing At the time of installation of a LIS trunk group, and at no additional charge, acceptance tests will be performed to ensure that the service is operational and meets the applicable technical parameters.

  • Performance Testing 7.2.1 The Design-Builder shall direct and supervise the tests and, if necessary, the retests of the Plant using Design-Builder’s supervisory personnel and the Air Emissions Tester shall conduct the air emissions test, in each case, in accordance with the testing procedures set forth in Exhibit A (the “Performance Tests”), to demonstrate, at a minimum, compliance with the Performance Guarantee Criteria. Owner is responsible for obtaining Air Emissions Tester and for ensuring Air Emissions Tester’s timely performance. Design-Builder shall cooperate with the Air Emissions Tester to facilitate performance of all air emissions tests. Design-Builder shall not be held responsible for the actions of Owner’s employees and third parties involved in the Performance Testing, including but not limited to Air Emissions Tester.

  • Health plan specification The Employer will require health plans participating in the Group Insurance Program to develop and implement health promotion and health education programs for State employees and their dependents.

  • ACCEPTANCE TESTS 11.1 If the Contract provides acceptance tests for Goods and/or the result of Services after their completion and/or delivery to the Purchaser, the acceptance shall only be considered as definitive when such tests have demonstrated the compliance of the Goods and/or the result of the Services to the requirements in the Contract.

  • Performance Tests Contractor shall perform Performance Tests in accordance with Section 11.2 of the Agreement and Attachment S.

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

  • Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

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