Electronic File Requirements Sample Clauses

Electronic File Requirements. Closeout 1. All documents (including as-built drawings) shall be converted or scanned into the Abode Acrobat (.PDF) file format and uploaded to the web based application database selected and provided by City. 2. In addition to the standard closeout submittal requirements detailed elsewhere in the Contract Documents, the Prime Design Professional/Consultant and Sub-Consultants shall also submit all closeout documents including but not limited to all “As-Built Drawings”, catalog cuts and Owner’s Operation and Maintenance manuals in digital format.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
Electronic File Requirements. Closeout 1. All documents (including as-built drawings) shall be converted or scanned into the Adobe Acrobat (.PDF) file format and uploaded to the web based application database selected and provided by City. 2. In addition to the standard closeout submittal requirements detailed elsewhere in the Contract Documents, the Prime Design Professional/Consultant and Sub-Consultants shall also submit all closeout documents including but not limited to all “As-Built Drawings”, catalog cuts and Owner’s Operation and Maintenance manuals in digital format.
Sample 1
Electronic File Requirements. Furnish digital file compatible with AutoCAD of the completed survey. Electronic base file should collectively include the entire project limits and must contain all the survey information depicted on the signed and sealed hard copy, excluding signature and seal. Seal must be replaced as required by 21 NCAC 56. • Furnish Digital Terrain Model TIN of completed work and LandXML file of the surface. Task 4 – SUE Investigation XXX will provide SUE Locating services in accordance with CI/ASCE Standard 38-02, Standard Guideline for the Collection and Depiction of Existing Subsurface Utility Data: “A branch of engineering practice that involves managing certain risks associated with: utility mapping at appropriate quality levels, utility coordination, utility relocation design and coordination, utility condition assessment, communication of utility data to certain parties, utility relocation cost estimates, implementation of utility accommodation policies, and utility design.” Quality Level B – Designating and Marking XXX staff will utilize the suite of geophysical equipment in each vehicle to attempt to designate the utilities identified in the Project Description within the area(s) of interest. Quality Level B services for this project include: • Obtaining permits from city, county or other municipalities to allow XXX, LLC staff to work in streets, roads, or right-of-ways. • Utilizing normal traffic control, including standard placement of traffic cones, freestanding warning signage and vehicle-mounted traffic directional sign.
Sample 1

Related to Electronic File Requirements

  • Electronic Records You acknowledge and agree that we may in our discretion store all records electronically; and that we will not retain and have no obligation to retain any original documents for any period of time. This applies to all documentation including but not limited to checks, transaction records, notes, mortgages, deeds of trust and other loan and/or security documentation. We will routinely destroy all original documentation. We may store records electronically via imaging, scanning, filming or other technology used in the financial services industry for the storage of documentation via internal processes or third-party processors that we approve for these services. You agree that such storage shall be secure, and further agree that such records shall for all purposes be recognized and admissible in evidence or otherwise to prove the agreements, rights and obligations of the parties pursuant to any such records.

  • Electronic Documents We may make periodic statements, disclosures, notices, and other documents available to you electronically, and, subject to any delivery and receipt verification procedures required by law, you agree to receive such documents electronically and to check the statements for accuracy. If you believe any such statement contains incorrect information, you must follow the procedures set forth in the Related Agreement(s).

  • Electronic Visit Verification ("EVV A. To ensure: 1. the EVV system is used to verify the provision of services governed under 40 TAC, Chapter 68 or its successor; 2. only authorized people access the Contractor's EVV account; 3. all data elements required by HHSC or HHSC's designee are uploaded or entered and maintained in the EVV system completely, accurately, and prior to submitting the claim; 4. that each time services governed by 40 TAC Chapter 68 or its successor are delivered to an individual, the Contractor's staff uses an HHSC-approved EVV system; and 5. service delivery documentation is immediately available for review by HHSC when requested. B. Equipment provided to Contractor by HHSC, HHSC’s designee, or an HHSC-approved EVV vendor, must be returned in good condition when the equipment is no longer needed under this Contract. In the context of this agreement, “good condition” means Contractor must not place any marks or identifying information on the equipment and may not alter information on the equipment including logos and serial numbers. If the equipment is lost, stolen, marked, altered or damaged by Contractor, Contractor may be required to pay the replacement cost for each piece of equipment that is lost, stolen, marked or damaged. Replacement costs for lost, stolen, marked or damaged equipment may be assessed periodically. If Contractor recovers previously lost or stolen equipment for which Contractor paid the replacement cost in the prior 12 months, Contractor may return the equipment and be reimbursed for the replacement costs within 12 months of the date HHSC, HHSC’s designee or an HHSC-approved EVV vendor (as applicable) received payment in full from the Contractor. This is provided the equipment is returned in good condition as specified above. C. HHSC may perform EVV compliance oversight reviews to determine if Contractor has complied with EVV compliance requirements as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC EVV website or EVV Policy Handbook. D. If the Contractor determines an electronic record in the EVV system needs to be adjusted at any time, the Contractor will make the adjustment in the EVV system using the most appropriate EVV reason code number(s), EVV reason code description(s) and enter any required free text when completing visit maintenance in the EVV system, if applicable. E. Contractor must begin using an HHSC-approved EVV system prior to submitting an EVV relevant claim. F. All claims for services required to use EVV (EVV claims) must match to an accepted EVV visit transaction in the EVV Aggregator (the state’s centralized EVV database) prior to reimbursement of an EVV claim. Without a matching accepted EVV visit transaction, the claim will be denied. G. Contractor must submit all EVV related claims through the Texas Medicaid Claims Administrator, or as otherwise described in the EVV Policy posted on the HHSC EVV website or in the EVV Policy Handbook. H. Contractor must complete all required EVV training as outlined in the EVV Policy posted on the HHSC EVV website or EVV Policy Handbook: • Prior to using either an EVV vendor system or an EVV proprietary system and • Yearly thereafter. I. Contractor and, if applicable, the Contractor’s appointed EVV system administrator, must complete, sign and date the EVV Onboarding Form as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC website or EVV Policy Handbook.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!