Document routing The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system. Routing Data Table* Field Name in WAWF Data to be entered in WAWF Pay Official DoDAAC "To be cited in each individual task order" Issue By XxXXXX "To be cited in each individual task order" Admin DoDAAC "To be cited in each individual task order" Inspect By XxXXXX "To be cited in each individual task order" Ship To Code "To be cited in each individual task order" Ship From Code "To be cited in each individual task order" Mark For Code "To be cited in each individual task order" Service Approver (DoDAAC) "To be cited in each individual task order" Service Acceptor (DoDAAC) "To be cited in each individual task order" Accept at Other DoDAAC "To be cited in each individual task order" LPO DoDAAC "To be cited in each individual task order" DCAA Auditor DoDAAC "To be cited in each individual task order" Other DoDAAC(s) "To be cited in each individual task order" (*Contracting Officer: Insert applicable DoDAAC information or “See schedule” if multiple ship to/acceptance locations apply, or “Not applicable.”)
Document Imaging Investor shall be entitled, in its sole discretion, to image or make copies of all or any selection of the agreements, instruments, documents, and items and records governing, arising from or relating to any of Company’s loans, including, without limitation, this Agreement and the other Transaction Documents, and Investor may destroy or archive the paper originals. The parties hereto (i) waive any right to insist or require that Investor produce paper originals, (ii) agree that such images shall be accorded the same force and effect as the paper originals, (iii) agree that Investor is entitled to use such images in lieu of destroyed or archived originals for any purpose, including as admissible evidence in any demand, presentment or other proceedings, and (iv) further agree that any executed facsimile (faxed), scanned, emailed, or other imaged copy of this Agreement or any other Transaction Document shall be deemed to be of the same force and effect as the original manually executed document.
Document Delivery Borrower, on or prior to the Closing Date, shall have delivered to Lender the following:
OGS Centralized Contract Terms and Conditions have been renumbered as depicted in the following chart: Current Amended Section Title 4.25 4.26 Severability 4.26 4.27 Entire Agreement
Document Management The Contractor must retain sufficient documentation to substantiate claims for payment under the Contract and all other records, electronic files, papers, and documents that were made in relation to this Contract. The Contractor must retain all documents related to the Contract for five (5) years after expiration of the Contract or, if longer, the period required by the General Records Schedules maintained by the Florida Department of State available at the Department of State’s Records Management website.
Shared Transport The Shared Transport Network Element (“Shared Transport”) provides the collective interoffice transmission facilities shared by various Carriers (including Qwest) between end-office switches and between end-office switches and local tandem switches within the Local Calling Area. Shared Transport uses the existing routing tables resident in Qwest switches to carry the End User Customer’s originating and terminating local/extended area service interoffice Local traffic on the Qwest interoffice message trunk network. CLEC traffic will be carried on the same transmission facilities between end- office switches, between end-office switches and tandem switches and between tandem switches on the same network facilities that Qwest uses for its own traffic. Shared Transport does not include use of tandem switches or transport between tandem switches and end-office switches for Local Calls that originate from end users served by non- Qwest Telecommunications Carriers (“Carrier(s)”) which terminate to QLSP End Users.
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):
PARTICIPATION IN CENTRALIZED CONTRACTS a. Agencies All State Agencies may utilize and purchase under any Centralized Contract let by the Commissioner, unless the Bid Documents limit purchases to specific State Agencies.
Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process.
Sub-processing 1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the sub-processor which imposes the same obligations on the sub-processor as are imposed on the data importer under the Clauses. Where the sub-processor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the sub-processor’s obligations under such agreement.
