Project Delivery Directive PD 06 Attachment A Detailed .

3y ago
21 Views
2 Downloads
208.23 KB
5 Pages
Last View : 3m ago
Last Download : 3m ago
Upload by : Lilly Kaiser
Transcription

Project Delivery Directive PD 06 Attachment ADetailed Guidance regarding the sharing of electronic filesTable 1. Summary of Electronic file guidance for each categoryCategory 1Category 2Electronic files from an active project beingprovided to prospective bidders. They do nothave a contract with the state for this work, yetproviding certain information during thebidding process to all bidders could lead tobetter and more accurate bids from prospectivebidders.Category 3DescriptionElectronic Files where the sharing of filesis beneficial to delivery of a Caltranssponsored project (i.e. the requestor isconsidered part of the PDT)Type of requestorA member of the PDT(Design, R/W, Environmental, DES,a utility company, etc.)Prospective biddersA local partner(city, county, regional transportation agency, etc.)Time FramePID through project closeoutProject advertisementPID through project closeout of their locally sponsoredproject on the SHS.Forms RequirednonenoneConfidentiality and Hold Harmless Agreementfor the Sharing of Electronic FilesType of files to besharedThe PDT will share the appropriate staticor vector files in order to expedite deliveryof the project.Type of files shared depends on the type ofproject but can include PDF, TIF, MicroStation,LandXML, or Roadway Design files.Requested files are to be provided in a static format. Vectorfiles should be shared if the Caltrans PM and PDT teamdetermine that those vector files would be beneficial to theimplementing agency for the delivery of their project on theSHS.Focal Point forRequests:From PID to Project Closeout, all requestscan be made by one PDT member toanother, except for contractors. FromContract Award until Project Closeout, allcontractor requests are to go through theResident Engineer.During advertisement, prospective biddersshould send all requests for additional electronicfiles in as a "Bidder's Inquiry" through thedistrict construction office, Duty Senior.Caltrans Project ManagerResourcesProject numberProject numberProject number (Oversight)Page 1 of 5Electronic Files and the requestor is an implementing agency(external agency responsible for a project on the SHS) wherethe information will be used to deliver a project on the SHS.

PD-06Attachment A2/8/16For all categories, contact your local Information Technology (IT) or CADD Supportgroup for recommendations on methods of sharing large electronic files (i.e. e-mail, ftpsites, cd/dvd media, etc.)Category 1:On current Caltrans sponsored projects (active, completed, or shelved) that follow thestandard design-bid-build process, it is vital that the PDT share electronic files in order toincrease communication and productivity. The PDT consists of any internal and externalforces required to deliver a project including internal functional units, A&E consultants,contractors under contract with Caltrans, etc. Forms or disclaimers are not needed inorder to share information about the project within the PDT. Full disclosure shall beprovided regarding the source of the information or its degree of confidence (i.e. was dataonly field verified, surveyed in a certain year, etc).Utility companies should also be treated as part of the PDT. If they request an electroniccopy of the base map, design should send that information to facilitate their utilityverifications. Utility companies are not required to submit a hold harmless agreement,nor a confidentiality statement. They are doing a part of the work for the project, whetherdeveloping relocation plans or verifying data.Consultants working directly for Caltrans as part of the PDT are bound by their task orderor contract. The task order or contract should define what information they need and willbe given.Whenever electronic files are shared with any external parties (e.g. utility companies,consultants, etc.), the Project Manager and Task Managers are to be informed of whatfiles were shared.Before Plans, Specifications, and Estimate (PS&E) are turned into District OfficeEngineer (DOE), any vector files that are shared electronically MUST NOT include theengineer’s signature. There are no other restrictions on the type of file (.DGN, .PDF, etc)that is shared with the team before the PS&E is turned into DOE. Between PS&E andwhen the project is awarded, all DGN files of plan sheets will be locked and will not beshared, except when necessary to prepare an addendum. After contract award, any vectorfiles that are shared electronically MUST NOT include the engineer’s signature, sealinformation, or printed name.See Appendix QQ of the Project Development Procedures Manual (PDPM) and sections3.6 & 3.7 of the CADD Users Manual for guidance on Digital Design Models (DDM’s)and other survey deliverables.Before PS&E, all requests can be made by one PDT member to another and do not needto go through any focal point. After contract award, all requests for electronic files fromthe contractor shall be directed to the Resident Engineer (RE). It will be the RE’sresponsibility to request and provide the appropriate file from another PDT member.Page 2 of 5

PD-06Attachment A2/8/16For most requests, extra resources are not needed to cover the sharing of current activeproject files. However, occasionally a member of the PDT may ask for files from past orshelved projects to use on new projects from a functional unit that is not resourced towork on the project. Historical project files were developed specifically for a previousproject and it is incumbent on the engineer who will be taking responsible charge of thecurrent active project to verify all aspects of the accuracy of the information beforeincorporating any portion of that historical project file.If there is a request for archived vector data, in DGN format, it is the PDT’sresponsibility to make sure the unit is resourced with enough hours in the active projectto search for the archived data. The signature, seal information, printed name, and asbuilt stamp must be removed from the DGN files before providing them to the team. Asbuilt plans in static format can be shared with the signature, seal information, names andas-built stamp intact.PDT members are not to share electronic project information with anyone outside of thePDT. Requests for any information (i.e. completed work such as a project report, etc.) ona current Caltrans sponsored project from individuals who are not a part of the PDT are tobe treated as a CPRA request. See DD-79: California Public Records Act (CPRA)Compliance.Category 2:This category is for bidders/contractors during the advertisement and bidding of a project.Prior to advertisement, files to be shared shall be identified in the Special Provisionsunder Supplemental Project Information and shall be made available at the time ofadvertisement and posted with the bid set. The following files must be provided for allprojects with earthwork: The digital terrain model (a 3 dimensional model representing the original groundbefore job site activities start) in 3D DGN or LandXML format; Roadway design alignments and profiles in LandXML format; Cross-sections in a 2D DGN and PDF file format; and The digital design model (a 3 dimensional model consisting of roadway designalignments, profiles, and cross sections representing the finished grade) inLandXML format.Other electronic files that may be made available to facilitate use of automated machineguidance include finished grade break lines in a 3D DGN format.NOTE: It will be the bidder's responsibility to do any other data conversions and Caltranswill not be held responsible for any errors created by the bidder’s conversion process.Page 3 of 5

PD-06Attachment A2/8/16Any files that are shared electronically as a .DGN file MUST NOT include anyengineer’s signature, seal information, nor printed names. All DGN files must alsocontain the text “For Design Study Only.If a bidder does request any electronic files not originally posted, the request is to besubmitted as a bidder inquiry so that any files released after being deemed appropriate forbidding can be provided to all bidders.Category 3:In the case of locally sponsored projects on the SHS, Caltrans wants to increasepartnering and cooperation to help in the efficient delivery of projects.This category applies to electronic file requests from an implementing agency for aproject on the SHS. It does not apply to consultants working for the implementingagency. Consultants working for the implementing agency should not make electronicfile requests except through the implementing agency. All electronic file requests fromthe implementing agency shall be directed to the Caltrans Project Manager (PM).Requests for any information received directly from a consultant working for animplementing agency is to be treated as a CPRA request. See DD-79: California PublicRecords Act (CPRA) Compliance.Static file format is the standard format for requested electronic files. Vector fileshowever, should be shared when the PM and the PDT team agree that the requestedvector files would be beneficial to the implementing agency in the delivery of theirproject.Vector files that are shared electronically as a .DGN file MUST NOT include theengineer’s signature, seal information, nor printed names. Full disclosure shall beprovided regarding the source of the information or its degree of confidence, if known(e.g. data was field verified, surveyed in a certain year, etc.).The PM shall request that the implementing agency designate a project specificrepresentative who is authorized to sign a Confidentiality and Hold Harmless Agreementfor the Sharing of Electronic Files. If a cooperative agreement has been signed whichalready includes indemnification clauses, this requirement can be waived. The PM shallensure that copies of all confidentiality and hold harmless agreements are maintained inthe project history folder.The PM shall also require that the implementing agency provide Caltrans with the asbuilt plans and any applicable archived vector files (e.g. basemaps, DTM’s, sheet files,etc.) at the completion of the project.It is the PM’s responsibility to contact the appropriate author of the files being requestedand obtain permission to provide these electronic files.Page 4 of 5

PD-06Attachment A2/8/16Once the appropriate files are released to the implementing agency, the agency may sharethem with only those individuals that have a contract/agreement to deliver their project.The electronic files provided are to be used only for the specific project for which therequest was initiated.With the exception of data files (such as a CAiCE project file or an XML file, etc.), eachelectronic file should have the following note:“By accepting this file, the recipient expressly agrees to treat this document asconfidential. All of the information provided in this file shall be properlysafeguarded and protected from unauthorized viewing, use, and disclosure.”If files are transmitted via e-mail, the following note is to be included with the e-mail:“CONFIDENTIALITY NOTICE: This communication with its contents maycontain confidential and/or legally privileged information. It is solely for the useof the intended recipient(s). Unauthorized interception, review, use or disclosureis prohibited and may violate applicable laws including the ElectronicCommunications Privacy Act. If you are not the intended recipient, please contactthe sender and destroy all copies of the communication.”Since a project number is established to do oversight on projects, that project numbershould be used for any time spent finding electronic files and in the case of vector files,for removing their signature, seal information, and printed names. It is the PM’sresponsibility to make sure resources are available for the time needed to locate anddeliver the files.Page 5 of 5

Electronic files from an active project being provided to prospective bidders. They do not have a contract with the state for this work, yet providing certain information during the bidding process to all bidders could lead to better and more accurate bids from prospective bidders. Electronic Files and the requestor is an implementing agency

Related Documents:

(f.2) “Directive 050” means Directive 050: Drilling Waste Management; (g) “Directive 056” means Directive 056: Energy Development Applications and Schedules; (g.1) “Directive 058” means Directive 058: Oilfield Waste Management Requirements for the Upstream Petroleum Industry; (h) “Directive 060” means Directive 060: Upstream

In addition to the Pressure Equipment Directive (97/23/EC), there is the Simple Pressure Vessel Directive (87/404/EC, for vessels containing air and nitrogen), the Transportable Pressure Equipment Directive (99/36/EC), and the Aerosol Dispensers Directive (75/324/EEC). This publication provides an outline of the Pressure Equipment Directive only.

Directive 75/443/EEC UNECE Regulation 39.00 Speedometer and reverse gear Directive 70/311/EEC UNECE Regulation 79.01 Steering effort Directive 71/320/EEC UNECE Regulation 13.10 Braking Directive 2003/97/EC UNECE Regulation 46.02 Indirect vision Directive 76/756/EEC UNECE Regulation 48.03 Lighting installation

Directive 67/548/EEC (dangerous substances Directive, DSD), and Directive 1999/45/EEC (dangerous preparations Directive, DPD), and Regulation 1272/2008 (CLP – Classification, labelling and packaging of substances and mixtures) The CLP –regulation will replace the two directives

detailed in this manual. Note: Our equipment as described in this manual conforms to all applicable rules and regulations of the ‘LowVoltage Directive’ (European Council Directive 73/23/EEC) as set out and amended by Council Directive 93/68/EEC) and to the National legislation for the enforcement of this Directive.

Department of Defense Directive SUBJECT: Physical Security Review Board References: (a) DoD Directive 5100.76, "Physical Security Review Board," May 17, 1977 (hereby canceled) (b) DoD Directive 5025.1, "Department of Defense Directives System," October 16, 1980 E TE SC (c) DoD Instruction 5100.84, "Physical Security of

This text does not contain the Annex to Directive 2001/83/EC. The Annex currently in force is laid down in Commission Directive 2003/63/EC of 25 June 2003 amending Directive 2001/83/EC of the European Parliament and of the Council on the Community code relating to medicinal products for human use (Official Journal L 159, 27/6/2003 p. 46 - 94).

1. Status. This directive supersedes Bi-Strategic Command Directive 40-1, dated 2 September 2009. Since the adoption of Bi-Strategic Command (Bi-SC) Directive 40-1 (hereafter referred to asthe "Directive") in2009, additional United Nations Security Council Resolutions (UNSCRs) and policies have been passed. This, incombination with LessonsFile Size: 525KB