01 11 00 - 1 06S2206

Camp SLO – Range Road Repair 8 September 2025

SECTION 01 11 00

SUMMARY

PART 1 GENERAL

1 SCOPE

1.1

1.2

1.3

1.4

1.5

The work consists of furnishing all equipment, materials, plant and labor necessary to accomplish the following: This project is to repair and improve the Range Road Phase 2 (San Benito Road) pavement and culverts at Camp San Luis Obispo. The repairs and improvements will be completed per these plans and specifications herein..

Any materials that are suitable for recycling shall be recycled.

Accomplish all work in accordance with the drawings and specifications contained herein.

Accomplish all work in accordance with California Building Codes (2019 Editions).

Perform the above-mentioned work at the Highway 1, San Luis Obispo, California, 93405.

2 CONTRACTING OFFICER’S REPRESENTATIVE

3 Wherever in these specifications the abbreviation COR is referenced, it shall be the same as if the term Contracting Officer's Representative is referenced.

4 ENGINEER/CONSTRUCTION INSPECTOR

4.1 Wherever the specifications direct the Contractor to the

ENGINEER/CONSTRUCTION INSPECTOR (ECI) for appropriate determination, the Contractor will direct his inquiries to the State Military Department, 9800 Goethe Road, P.O. Box 269101, Sacramento, California 95826, ATTN: CAFE-EN Quality Control. Phone: (916) 854-3546.

5 CONTRACTOR'S RESPONSIBILITY

5.1 Nothing contained in these specifications shall relieve the contractor from the responsibility of visiting the site, accurately measuring the work or otherwise insuring that the quantities used in preparing his bid are the actual quantities of the work to be accomplished under the contract. By submitting a bid the contractor confirms that he has visited the aforementioned site and verifies that the quantities used in preparing his bid are the actual quantities of the work to be accomplished under the contract.

5.2 The Contractor shall maintain a competent foreman, English speaking, to continuously supervise the work, with authority to discard unsuitable materials and remove unsatisfactory workmen from the project.

01 10 00 -3

Camp SLO – Range Road Repair 8 September 2025

6 VEHICLE MOVEMENT

6.1 The following applies to all vehicles, except emergency vehicles responding to an emergency:

7 Vehicles shall observe posted speed limits on post at all times. Vehicles operated when in close proximity to military vehicles or buildings shall not exceed 5 MPH maximum.

8 Vehicles will not be backed without a ground guide.

9 All vehicles which do not require the engine to be running for contract purposes will have the ignition turned off and the parking brake set and the vehicle's transmission placed in park.

10 CONTRACTOR’S STORAGE AREA AND PERSONNEL

10.1 The COR will designate an area that the contractor may use as a storage area. The contractor shall contact the COR for information regarding parking areas to be used for contractors equipment and by contractor personnel and any restrictions that will be placed on contractor personnel while on the job site.

10.2 The Contractor shall maintain a clean site and prevent any materials removed or installed on site becoming FOD (Foreign Object Debris).

11 MATERIAL SUBMITTALS

11.1 Contractor shall submit to the Project Manager for approval, one (1) copy in writing, of a complete list of material submittals and equipment to accomplish the work specified.

11.2 Submittals shall comply with Section 01 33 00 of these specifications.

Transmit submittals (from Submittal List) on Submittal Log (the list and a blank log is provided after Section 01 33 00).

11.3 Project Manager must receive submittals for Specification identified materials (no substitutions permitted) within ten (10) working days after receiving the "Proposed Contract" for signature.

11.4 Receipt of Submittals that substitute an "or equal" are required within fifteen

(15) days after date of Contract Agreement.

11.5 Do not start work until Project Manager approves all project submittals, issues special instructions, and a "Notice of Award" is received from the Contracting Officer.

12 APPROVAL OF PROCEDURES

12.1 The manufacturer's recommended installation procedures and these specifications, will serve as a basis for inspection and acceptance or rejection of actual installation procedures used on the work.

12.2 Project Drawings are valid for construction only when stamped, signed and approved for construction by the Architect/Engineer(s) of Record.

Camp SLO – Range Road Repair 8 September 2025

12.3 Project Specifications are valid for construction when:

12.4 The cover sheet is dated and signed by the Architect of record

12.5 ALL included Sections bear dates on or before that shown on the signed cover sheet.

13 ORDINANCES AND REGULATIONS

13.1 All work shall be accomplished in accordance with all local, State and Federal regulations. Permits and fees shall be the responsibility of the contractor at no additional cost to the Government.

14 WORKING HOURS

14.1 The work site will be available for contractor's activities from 8:00 a.m.

until 4:30 p.m. Monday through Friday. The site will not be available for contractor's activities on weekends and State or Federal holidays.

14.2 The Contractor shall receive written approval from the Project Manager before implementing any form of compressed or alternative work schedule.

14.3 Contractor shall schedule operations so as not to conflict with airfield operations.

15 SCHEDULING AND INSPECTION

15.1 Within fifteen (15) calendar days after receipt of Notice to Proceed, and before commencing work, the contractor shall submit in writing to the Project Manager for approval, the complete scope of work and the procedures and sequence required to complete the work.

15.2 The contractor shall work directly with the COR and ECI on work scheduling and inspection procedures prior to starting any work.

16 AS-BUILT DRAWINGS

16.1 The contractor shall provide one (2) full and accurate hardcopy sets of as-built drawings per Specification Sections 01 33 00 and 01 70 00, for the work accomplished by all trades for this contract marked up in a neat and understandable manner, submitted to the COR upon completion of the work and prior to issuance of a Certificate of Completion.

PART 2 PRODUCTS

17 MATERIALS

17.1 All materials for use under this project shall meet or exceed the standards of quality hereinafter set forth and per Section 01 60 00.

Camp SLO – Range Road Repair 8 September 2025

PART 3 EXECUTION

18 QUALITY CONTROL

18.1 To insure proper project quality control and required record keeping, contractor shall comply with Section 01 45 00.10 20

19 CONTRACT CLOSEOUT

19.1 Contract closeout requires contractor compliance with Section 01 70 00.

END OF SECTION

01 26 13 – 1

SECTION 01 26 13

CHANGES IN THE WORK

PART 1 - GENERAL

1.1 SUMMARY

A. Changes in the Plans and Specifications, requested in writing by the Contractor, which do not materially affect the Work and which are not detrimental to the Work or to the interests of the Agency, may be granted by the Contracting Officer’s Representative (COR). Nothing herein shall be construed as granting a right to the Contractor to demand acceptance of such changes.

B. The CMD may change the Plans and Specifications, character of the work, or quantity of work provided the total arithmetric dollar value of all such changes, both additive and deductive, does not exceed 25 percent of the contract price. Should it become necessary to exceed this limitation, the change shall be by written Supplemental Agreement between the Contractor and the CMD, unless both parties agree to proceed with the change by change order.

C. Change Orders shall be in writing and the state the dollar value of the change or establish the method of payment, any adjustment in the Contract time of completion, and when negotiated prices are involved, shall provide for the Contractor’s signature indicating acceptance.

PART 2 - PRODUCTS (NOT USED)

PART 3 - EXECUTION

3.1 CHANGE ORDERS

A. No cost change orders:

1. Contract Documents are complementary; therefore, before starting each portion of

Work, carefully study and compare various Drawings, Specifications and any other Contract Documents, coordination drawings, shop drawings, prior correspondence or documentation relative to that portion of Work, as well as information furnished by

CMD.

2. Contractor and Subcontractors shall evaluate and take field measurements of any existing conditions related to that portion of Work and shall observe any conditions at site affecting Work.

3. Contractor and subcontractors acknowledge that all documents pertaining to Work has been examined, have examined character of site and any existing conditions, and are satisfied with nature of Work, and all other matters which can in any way affect Work.

4. In event of inconsistency between portions of Contract Documents or within Contract Documents; provide better quality or greater quantity of Work, and comply with more stringent requirement, either or both in accordance with Architect’s interpretation.

5. Any errors, inconsistencies or omissions discovered in Contract Documents shall be reported promptly to Architect as a properly prepared and timely RFI.

6. Contractor and Subcontractors are not required to ascertain Contract Documents

8 September 2025 are in accordance with applicable laws, statutes, ordinances, codes, and rules and regulations, unless they bear upon construction means, methods, techniques or safety and health precautions, but any nonconformity discovered by or made known shall be reported promptly as a RFI.

7. If Contractor or Subcontractor fail to give such notice, and knowingly proceeds with Work affected by errors or omissions in Contract Documents, Contractor shall correct any such errors, inconsistencies, or omissions at no additional cost.

B. Contractor’s and Subcontractor’s Responsibilities:

1. When interpretation, clarification or explanation of portion of Construction Documents is needed by Contractor, Subcontractor, Vendor or Supplier, the request shall be processed through Contractor:

a. Review request for completeness, quality, proper referencing to drawing or specification section and reason submitted.

b. If request is not acceptable it shall be sent back to submitter with comments regarding reason for being returned.

c. Make every attempt to validate, resolve or respond to RFI by thoroughly researching and reviewing Contract Documents and field conditions.

d. Respond to RFI accordingly if review of RFI discloses a response or is related to coordination of construction or other issue not related to Contract Documents.

e. If unable to respond to request, it shall be restated in clear, concise, correct, complete and easily understood manner, and rewritten if necessary, additional information included if necessary, and only then submitted to Architect for response.

2. Request for interpretation, clarification or explanation of Contract Documents shall be submitted to CMD in writing:

a. List specific Contract Documents reviewed when seeking information being requested.

b. Reference all applicable Contract Drawings by sheet number, section, detail, room number, door number, etc., Specifications by section and paragraph number, and reference any other relevant documents.

c. The field titled "Regarding" on attached RFI form must be clear for future reference in reports or correspondence.

d. Clearly state request and provide Contract Document references and any additional information needed so request can be fully understood, including sketches, photos or other reference material.

e. Fully assess issues, suggest any reasonable solutions and include various factors, including potential costs, schedule impacts, if any, and recommendations which will aid in determining a solution or response. If a reasonable solution cannot be suggested, a statement to that effect should be so stated.

f. Indicate reason request is being submitted.

g. Any critical RFI’s requiring a rapid response shall clearly indicate such with an explanation as to why RFI is critical.

h. Priority for responses shall be indicated when multiple RFI’s are submitted within short period of time.

3. Copies of responses to RFI’s shall be distributed to all parties affected.

4. A response to RFI shall not be considered a notice to proceed with a change that may revise the Contract Sum or Contract Time, unless authorized by CMD in writing.

5. If response to RFI is determined incomplete, it shall be resubmitted with reason response is unacceptable and any necessary additional information within five (5) days of time of receipt of response to RFI.

8 September 2025

6. If determined or believed that additional cost or time is involved because of clarifications, interpretations or instructions issued by Architect in response to a RFI, resubmit RFI within five (5) days of receipt of response with reason and alternate solution or suggestion for performing work at no additional cost. If no other solution is possible or desirable, submit Claim in accordance with the Contract Documents with in twenty-one (21) days of receipt of response to the RFI.

C. RFI Submittal Format:

1. Request for information shall be submitted to Architect on RFI form provided at end of this section, or form provided by Architect in electronic text file format, or in similar format acceptable to Architect:

a. RFI’s shall be assigned unique numbers in sequential order (1, 2, 3, 4, etc.).

b. A resubmitted RFI or a previously answered RFI requiring revising or further clarification shall be submitted using original RFI number proceeded by “.1” to indicate revision one of RFI (i.e.: RFI No. 34.1 for revision 1 to RFI No. 34).

c. RFI form shall be electronically filled out and emailed to Architect’s designated representative in text file format. Attachments shall be in electronic text or PDF file format. Photo attachments may be in JPG format.

D. Architect’s Response to Request for Information (RFI):

1. Clarifications, interpretations and decisions of Architect in response to RFI will be consistent with intent of and reasonably inferable from Contract Documents, and will be in writing, and if determined to be necessary by Architect, will be provided in form of drawings and other attachments or both.

2. When making such interpretations and initial decisions, Architect will endeavor to secure faithful performance by both CMD and Contractor, will not show partiality to either and will not be liable for results of interpretations or decisions so rendered in good faith.

3. Architect’s decisions on matters related to aesthetic effects will be final if consistent with intent expressed in Contract Documents.

4. Architect will not undertake to settle differences between Contractor, Subcontractors, trades suppliers, fabricator or manufacturer, or act as arbiter as to which Subcontractor, trade, supplier or manufacturer is to furnish or install various items indicated or required.

5. Architect shall provide responses to RFI’s with reasonable promptness, but will endeavor to respond within twenty-one (21) days from date of receipt:

a. If multiple RFI’s are submitted on same day or within a five (5) day period, review time may be extended by mutual agreement of parties

b. Architect will provide a written response to RFI if Architect believes response only involves an interpretation, clarification, supplemental information or orders a minor change in Work not involving an adjustment in Contract Sum or extension of Contract Time, and is not inconsistent with intent of Contract Documents, and shall be binding.

c. If Architect believes response may result in a change to Contract Sum or Contract Time, response will indicate that a change document will be issued for the response, and appropriate change document will be issued indicating changes to Contract Documents.

d. Architect will provide any additional or supplemental drawings, specifications or other information as Architect may deem necessary to facilitate response.

6. Architect may return RFI without response for following reasons:

a. Unclear.

b. Incomplete.

c. Detailed information not provided.

d. Is related to construction means, methods or techniques.

e. Is related to health or safety measures.

f. Is due to Contractor’s lack of adequate coordination

8 September 2025

g. Is considered a “Substitution Request.”

h. Is due to non-conformance.

i. Response is required by another party.

E. If requested information is available from careful study and comparison of Contract Documents, field conditions, other CMD-provided information, coordination drawings, or prior Project correspondence or documentation, Architect may invoice CMD as a change in services for costs involved in Architect’s review, analysis, responding and processing of such

RFI:

1. Contractor shall reimburse CMD for such costs.

01 30 00 - 1

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this specification to the extent referenced.

The publications are referred to within the text by the basic designation only.

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 385-1-1 (2014) Safety and Health Requirements

Manual

U.S. NATIONAL ARCHIVES AND RECORDS ADMINISTRATION (NARA)

15 CFR 772 Definition of Terms

15 CFR 773 Special Licensing Procedures

1.2 SUBMITTALS

Government approval is required for submittals. Refer to section 01 33 00 Submittal Procedures for instruction.

1.3 PROGRESS AND COMPLETION PICTURES

Photographically document site conditions prior to start of construction operations. Provide monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit true color 300 minimum resolution in [JPEG] file format showing the sequence and progress of work. Take a minimum of 20 digital photographs each week throughout the entire project from a minimum of ten views from points located by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, each set on a separate compact disc (CD) or data versatile disc (DVD), cumulative of all photos to date. Indicate photographs demonstrating environmental procedures.

Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file. Include a date designator in file names. Cross reference submittals in the appropriate daily report. Photographs provided are for unrestricted use by the Government.

1.4 MINIMUM INSURANCE REQUIREMENTS

Provide the minimum insurance coverage required by the contract, during the entire period of performance under this contract. Provide other insurance coverage as required by California state law.

01 30 00 - 2

1.5 FIRST TIER CONTRACTOR REQUIREMENTS FOR ASBESTOS CONTAINING

MATERIALS

Accomplish all contract requirements of Section 02 82 00 ASBESTOS REMEDIATION, assigned to the Private Qualified Person, Designated Competent Person, directly with a first tier subcontractor.

1.6 SUPERVISION

1.6.1 Minimum Communication Requirements

Have at least one qualified superintendent, or competent alternate, capable of reading, writing, and conversing fluently in the English language, on the job-site at all times during the performance of contract work. In addition, if a Quality Control (QC) representative is required on the contract, then that individual must also have fluent English communication skills.

1.6.2 Superintendent Qualifications

The project superintendent must have a minimum of 5 years’ experience in construction with at least 5 of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent.

The Contracting Officer may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question.

For routine projects where the superintendent is permitted to also serve as the Quality

Control (QC) Manager as established in Section 01 45 00.10.20 Quality Control, the superintendent must have qualifications in accordance with that section.

1.6.2.1 Duties

The project superintendent is primarily responsible for managing and coordinating day-to-day production and schedule adherence on the project. Project superintendent shall attend project meetings and quality control meetings. The superintendent or qualified alternative must be on-site at all times during the performance of this contract until the work is completed and accepted.

1.6.3.1 Project Manager Qualifications

The Project Manager must have a minimum 5 years’ experience as a Project Manager or Superintendent on projects of similar size and complexity.

1.6.4 Non-Compliance Actions

The Project Superintendent is subject to removal by the Contracting Officer for non-compliance with requirements specified in the contract and for failure to manage the project to insure timely completion. Furthermore, the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken.

01 30 00 - 3

No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.

1.7 MEETINGS

1.7.1 PRECONSTRUCTION MEETING

A. After award of the contract but prior to commencement of any work at the site. Project Manager will schedule and preside over meeting at the Project Site prior to Contractor occupancy.

B. Attendance Required: Project Manager, Architect/Engineer, Contractor, major Subcontractors, and Inspector of Record.

C. The meeting will be chaired by the Project Manager and minutes taken by the contractor.

D. Location, time and date will be site by the Project Manager.

E. The subjects to be reviewed include, but are not limited to:

1. Introduction.

2. Construction Coordination.

3. Correspondence.

4. Submittals.

5. Permits.

6. Dust Control.

7. Schedule.

8. Survey Control.

9. Contractor’s Representative.

10. Testing and Inspection.

11. Contractor Reporting Requirements.

12. Changes and Clarifications.

13. Clean-up.

14. As-Built Documents.

15. Prevailing Wage Requirements.

16. Environmental Protection, Plan and Procedures.

17. Temporary Facilities Construction.

18. Notice of Labor Disputes.

19. Progress Payments.

20. Site Regulations.

21. Security.

22. Operation and Maintenance Data.

23. Training Requirements.

24. General Discussion.

F. Project Manager: Record minutes and distribute copies to participants within two days after meeting, with one copies each to Architect/Engineer, and those affected by decisions made.

01 30 00 - 4

1.7.2 WEEKLY CONTRACTOR MEETINGS

A. Once a week during the Contract period, Contractor shall meet at the Work Site with the Project Manager.

B. Time and location of the meeting will be determined during the Preconstruction Conference.

C. The Contractor will serve as chairman and take minutes of meetings.

D. Topics for discussion will include schedule, requests for information, disputed items, Potential Change Order (PCO) and Change Order (CO) status, Quality control, submittals, exception notices, and other topics as required.

1.7.3 PREINSTALLATION CONFERENCES

A. Prime Contractor shall convene a preconstruction conference for items of Work contained in each Division of the Specifications, each trade within the Division, and each subcontractor within the Division.

1. Convene a preconstruction conference prior to commencing the Work of the

Section, trade, or subcontractor.

2. Require attendance of each subcontractor and each trade directly affecting or affected by the Work within the Division.

3. Convene additional conferences when required by individual Section.

4. Prepare an agenda, preside over the conference, and record minutes, and distribute copies within two days after the conference to participants, with two copies to the Project Manager.

5. Review conditions of installation, coordination, preparation, approved submittals, Contract Documents, and means and methods planned to be used to perform the Work.

ii. Within 15 days after Notice to Proceed, submit a proposed list of preconstruction conferences, and items of Work to be covered, for approval by the Project Manager.

1.7.4 CONTRACT CLOSEOUT MEETING

A. Schedule Project closeout meeting with sufficient time to prepare for requesting Substantial Completion. Preside over meeting and be responsible for minutes.

B. Attendance Required: Contractor, Project Manager, Inspector of Record and Architect/Engineer, and others appropriate to agenda.

C. Notify Facility Representative five days in advance of meeting date.

D. Minimum Agenda:

1. Start-up of facilities and systems.

2. Operations and maintenance manuals.

3. Testing, adjusting, and balancing.

4. System demonstration and observation.

5. Operation and maintenance instructions for Owner's personnel.

01 30 00 - 5

6. Contractor's inspection of Work.

7. Contractor's preparation of an initial "punch list."

8. Procedure to request Architect/Engineer inspection to determine date of

Substantial Completion.

9. Completion time for correcting deficiencies.

10. Inspections by authorities having jurisdiction.

11. Certificate of Occupancy and transfer of insurance responsibilities.

12. Partial release of retainage.

13. Final cleaning.

14. Preparation for final inspection.

15. Closeout Submittals:

a. Project record documents.

b. Operating and maintenance documents.

c. Operating and maintenance materials.

d. Affidavits.

16. Final Application for Payment.

17. Contractor's demobilization of Site.

18. Maintenance.

1.14 ELECTRONIC MAIL (E-MAIL) ADDRESS

Establish and maintain electronic mail (e-mail) capability along with the capability to open various electronic attachments as text files, pdf files, and other similar formats. Within 10 days after contract award, provide the Project Manager a single (only one) e-mail address for electronic communications from the Project Manager related to this contract including, but not limited to contract documents, invoice information, request for proposals, and other correspondence. The Contracting Officer may also use email to notify the Contractor of base access conditions when emergency conditions warrant, such as hurricanes or terrorist threats. Multiple email addresses are not allowed.

It is the Contractor's responsibility to make timely distribution of all Project Manager initiated e-mail with its own organization including field office(s). Promptly notify the Contracting Officer, in writing, of any changes to this email address.

PART 2 PRODUCTS - Not Used

PART 3 EXECUTION

3.1 ALTERATION PROCEDURES

A. Employ skilled and experienced installer to perform alteration and renovation Work.

B. Remove unsuitable material not marked for salvage, including rotted wood, corroded metals, and deteriorated masonry and concrete. Replace materials as specified for finished Work.

C. Remove debris and abandoned items from area and from concealed spaces.

D. Prepare surface and remove surface finishes to permit installation of new Work and finishes.

01 30 00 - 6

E. Close openings in exterior surfaces to protect existing Work from weather and extremes of temperature and humidity.

F. Where new Work abuts or aligns with existing Work, provide smooth and even transition. Patch Work to match existing adjacent Work in texture and appearance.

G. Patch or replace portions of existing surfaces that are damaged, lifted, discolored, or showing other imperfections.

End of Section

Section 01 30 10 – Administrative Requirements

COLLABORATION SOFTWARE

1. SUMMARY

a. Contractor shall utilize web-based construction project management collaboration software commonly known as Procore (www.procore.com) to submit, track, distribute and fully collaborate on project documentation and action items. Wherein this specification references Procore it shall mean the California Military Department (CMD) Procore account.

b. The intent of utilizing a web-based construction management application is to reduce cost and schedule risk, improve quality and safety, and maintain a healthy team dynamic by improving information flow, reducing non-productive activities, reducing rework and decreasing turnaround times.

2. SOFTWARE USAGE (including but not limited to)

a. Daily Log

i. Using the Daily log tool within Procore, Contractor shall provide a separate daily log entry for the Superintendent, Site Safety and Health Officer and Quality Control team (as defined elsewhere in this contract). Should contractor already have an established process for documenting Daily work activities, Safety and QCM, the CMD may, at its sole discretion, permit the use of some or all of the contractors' reports provided they are uploaded daily into Procore Daily log tool as directed by the Department.

ii. Contractor shall upload pictures daily when work is performed. A reasonable number of pictures shall be taken to illustrate the work of the project but in any event no less than 10 photos daily, if work is interior and exterior there shall be 10 of each area of work. Photos shall be made available to the entire project team, loaded directly into the Procore platform, using the “Photos” tool and provided relevant naming convention to permit search features at a later date.

These uploads shall be in addition to those required in the Section 01 30 00 (if addressed) and elsewhere in the contract.

b. Directory

i. Contractor shall input and update (as required) the Procore project directory to include all key project team members. As directed by the CMD, subcontractors may not be required to participate within the Procore project. Should CMD require participation of subcontractors withing Procore, participation will be at no additional cost or expense.

c. Deficiency Tracking

i. Contractor shall respond promptly to deficiencies and observations identified in PROCORE and do so in accordance with the terms and conditions of this contract.

d. Documents

i. Contractor will, as directed by the Department, utilize the Procore “Documents” storage location for miscellaneous project documents. Contractor shall not upload documents unless directed by the Department. Documents loaded shall have a naming convention of title/subject to permit search functions of the Procore system.

ii. Contractor shall use proper version control and check out files, without compromising access to all previous revisions.

e. Drawings

i. Project Drawings will be located in the Drawings tool of Procore. Any drawing revisions will be made in Procore and it shall be contractors' sole responsibility to stays abreast of any changes including contract modifications. Contractor shall, as directed by the Department, maintain the contractually required “as built” drawings in the Procore.

f. Invoicing

i. If requested by the Department, the Contractor shall utilize Procore Invoicing tool for invoice submission. Invoicing shall be submitted as further defined in this contract using AIA forms uploaded as attachments to each submission.

g. Inspections

i. Contractor shall utilize the Procore platform as directed by CMD for all project inspection requests. Inspection process shall be as defined elsewhere the contract documents.

h. Meetings

i. Contractor shall utilize Procore Meetings tool to create, edit and post meeting minutes. Prior Meeting minutes shall remain accessible through the duration of the project. At the sole discretion of the department, the contractor may be permitted to utilize existing meeting practices if they meet the intent of the government, in which case contractor shall ensure a record copy of any such meeting is posted in Procore as directed by the department.

ii. Contractor will record and distribute meeting minutes and action items via the Meetings tool within the Procore software.

i. Mobile Accessibility

i. Contractor shall provide at least one mobile (Apple or Android) tablet or computer (phone is not acceptable) with the Procore App installed for the use of Contractor’s team for the duration of the project. Contractor is responsible for ensuring a reliable internet connection for the device.

j. Photos

i. Contractor shall utilize Procore Photos tool or other tools as directed to upload and view photos from web and mobile.

ii. Contractor shall utilize Procore to markup or comment on photos to clarify the intent of RFI’s etc.

k. Punchlist

i. All punch list items will be managed through the Procore software.

ii. Contractor shall utilize Procore to create and manage punch list items utilizing mobile products and link them to specific locations on the drawings.

iii. Punchlist items will be created by the Contractor while walking with the CMD and applicable consultants.

iv. Contractor shall utilize Procore to distribute punch list items and to mark them as resolved with photographic proof of resolution as required.

v. Unless otherwise agreed in writing, Punchlist Items may not be closed while a representative from the CMD or applicable consultant acting on behalf of CMD is not present.

l. Requests for Information (RFIs)

i. Contractor shall utilize the RFI tool within Procore to create and process RFIs with assignees, due dates and attachments.

ii. Contractor shall fully complete the RFI tool request form, posting the RFI to the drawing(s) and link all relevant specifications, photos, etc. in the Procore RFI tool whenever submitting RFI’s to the CMD. Failure to do so will result in rejection of the review and be deemed a review by the CMD as defined elsewhere in the contract documents.

iii. If project includes design, drawings will be provided to the CMD in accordance with the following requirements:

https://support.procore.com/faq/how-can-i-improve-the-accuracy-of-ocr-on-my-drawings

m. Schedule

i. Contractor shall provide native files as required by Procore and as defined elsewhere in the contract documents. Procore accepts typical scheduling software such as Microsoft Project, Primavera P3, or Primavera P6.

n. Specifications

i. Project Specifications will be uploaded into Procore. Any project revisions will be made in Procore and it shall be the contractors' sole responsibility to stays abreast of any changes including contract modifications.

o. Submittals

i. Contractor shall maintain the submittal register in Procore of all submittals as directed by the CMD.

ii. Contactor shall submit all submittals through the Procore “Submittals” tool utilizing the multi-step approval workflows predefined by the CMD and in accordance with the terms provided elsewhere in the contract documents.

iii. Contractor shall fill out the submittals completely. A failure to do so will result in automatic rejections and be deemed a “review” as provided elsewhere in the

3. TECHNOLOGY

a. Contractor shall have PDF and the Microsoft suite software as they are a requirement of Procore. Attachments to RFIs, Submittals, Meetings, etc. should be uploaded in PDF as required by Procore.

4. TRAINING AND SUPPORT

a. Contractor shall designate a minimum of one primary and one backup staff person to administer the contractors’ Procore responsibilities of this project. Those personnel will be trained as defined below and shall not rely on the CMD staff for training.

b. The Contractor shall ensure adequate training of all staff utilizing the Procore software.

Selected staff must complete all required training necessary to fully function in the system and on this project. Training is offered in the form of self-paced learning videos as well as interactive webinars. Training is free and can be found at:

https://education.procore.com/page/procore-certification-general-contractor-client

c. The contractor shall host a kickoff meeting with the CMD and applicable team members at the beginning of the project to discuss how the software will be used, routing & naming protocols, etc. Project Subcontractors should not be part of the Procore platform unless otherwise directed by the Department.

5. PROCEDURES

a. RFIs and Submittals

i. The Contractor will be responsible for submitting all RFIs and Submittals through the Procore software tools and assigning them to the appropriate parties using predetermined workflows. All data fields shall be filled out completely and routed as defined in the project kickoff/Job Start meeting.

ii. All project team members including Architects / Engineers / Consultants etc. are responsible for posting all responses to these items via the Procore software, including uploading all relevant attachments.

iii. The Contractor will, as directed by CMD, distribute responses to all affected subcontractors and confirm agreement with the response by “close and distribute” action on the item.

b. Construction Documentation

i. The Contractor will construct pursuant to Drawings, Specifications and Documents in the software and ensure that the current version of all applicable construction documentation is available to the entire team within Procore software.

ii. The Contractor will ensure that all RFIs which modify the current drawings are posted/linked to the drawings and available in the Procore software immediately upon response from the department.

6. COST

a. The Contractor’s bid proposal shall be inclusive of full utilization of the Procore software costs. The program is hosted by the CMD and no adjustment to the contract will be made for utilization.

01 32 16.00 20 - 1

Camp SLO – Range Road Repai

SECTION 01 32 16.00 20

SMALL PROJECT CONSTRUCTION PROGRESS SCHEDULES

1.1 SUBMITTALS

Government approval is required for all submittals. Submit the following in accordance with Section 01 33 00 Submittal Procedures:

A. Preconstruction Submittals

B. Baseline Construction Schedule

C. Monthly Updates

1.2 PRE-CONSTRUCTION SCHEDULE REQUIREMENT

Prior to the start of work, prepare and submit to the Project Manager a Baseline Design Schedule and Baseline Construction Schedule. The approval of a Baseline Construction Schedule is a condition precedent to:

a. The Contractor starting demolition work or construction stage(s) of the contract.

b. Processing Contractor's invoice(s) for construction activities/items of work.

c. Review of any schedule updates.

Submittal of the Baseline Design and Construction Schedule, and subsequent schedule updates, is understood to be the Contractor's certification that the submitted schedule meets the requirements of the Contract Documents, represents the Contractor's plan on how the work will be accomplished, and accurately reflects the work that has been accomplished and how it was sequenced (as-built logic).

1.3 SCHEDULE FORMAT

1.3.1 Project Schedule (NAS)

Use the critical path method (CPM) to schedule and control project activities. Prepare and maintain project schedules using Microsoft Project 2010. The scheduling software that will be utilized by the Government on this project is Microsoft Project 2010 by Microsoft, Inc.

Notwithstanding any other provision in the contract, schedules submitted for this project must be prepared using Microsoft Project. Submission of data from another software system where data conversion techniques or software is used to import into Microsoft Projects scheduling software is not acceptable and will be cause for rejection of the submitted schedule. Importing data into the scheduling program using data conversion techniques or third party software is cause for rejection of the submitted schedule.

Within 15 calendar days after approval of the Initial Schedule or approval of the final design for a design build project, submit to the Project Manager a final project schedule.

01 32 16.00 20 - 2

1.3.1.1 Activity Requirements

a. At a minimum, identify the following in the schedule:

(1) Design and Construction time for major systems and components

(2) Each activity assigned with its appropriate Responsibility Code

(3) Each activity assigned with its appropriate Phase and Area Codes

(4) Major submittals and submittal processing time

(5) Major equipment lead time

b. Build the Schedule as follows:

(1) Show design periods, submittals, Government review periods, material/equipment delivery, utility outages, on-site construction, inspection, testing, and closeout activities. Government and Contractor on-site work activities must be driven by calendars that reflect Saturdays, Sundays and all Federal Holidays as non-work days for 5-day work week calendars.6-day work week calendars must reflect Sundays and all Federal Holidays as non-work days. 7-day work week calendars must reflect all Federal Holidays as non-work days unless otherwise agreed to by the Project Manager. Total work hours/day for all defined calendars is set to 8 unless otherwise agreed upon.]

(2) With the exception of the Contract Award and End Contract milestone activities, use of open-ended activities is not allowed; each activity must have predecessor and successor ties. No activity must have open start or open finish (dangling) logic.

Minimize redundant logic ties. Once an activity exists on the schedule it must not be deleted or renamed to change the scope of the activity and must not be removed from the schedule logic without approval from the Project Manager.

While an activity cannot be deleted, where said activity is no longer applicable to the schedule but must remain within the logic stream for historical record, it can be changed to a milestone. Document any such change in the milestone's "Notebook," including a date and explanation for the change. The ID number for a deleted activity must not be re-used for another activity.

(3) Assign each activity its appropriate Responsibility Code and Area Code, indicating location and responsibility to accomplish the work indicated by the activity, Phase Code, and Work Location Code. Include anticipated tasks to be assigned Government responsibility.

(4) Date/time constraints or lags, other than those required by the contract, are not allowed unless approved by the Project Manager. Include as the last activity in the contract schedule, a milestone activity named "Contract Completion Date".

01 32 16.00 20 - 3

(5) Include the following Contract Milestones:

(a) Include as the first activity on the schedule a start milestone titled "Contract Award", which must have a Mandatory Start constraint equal to the Contract Award Date;

(b) Include Interim or Phased Completion Milestones required by the Contract or as approved by the Project Manager;

(c) Include Facility Turnover Planning Meeting Milestones;

(d) Include an unconstrained finish milestone on the schedule titled "Substantial Completion". Substantial Completion is defined as the point in time the Government would consider the project ready for beneficial occupancy wherein by mutual agreement of the Government and Contractor. Government use of the facility is allowed while construction access continues in order to complete remaining items (e.g. punch list and other close out submittals).

(e) Include an unconstrained finish milestone on the schedule titled "Projected Completion". Projected Completion is defined as the point in time the Government would consider the project complete. This milestone must have the Contract Completion Date (CCD) milestone as its only successor.

(f) Include as the last activity on the schedule a finish milestone titled "Contract Completion (CCD)" with constraint type "Must Finish No Later Than". Calculation of schedule updates must be such that if the finish of the "Projected Completion" milestone falls after the contract completion date, then negative float will be calculated on the longest path and if the finish of the "Projected Completion" milestone falls before the contract completion date, the float calculation must reflect positive float on the longest path. This milestone must be set to 5:00 pm.

(6) Provide lead time for major equipment.

1.3.1.2 Anticipated Weather Lost Work Days

Use the National Oceanic and Atmospheric Administration's (NOAA) Summary of Monthly

Normals report to obtain the historical average number of days each month with precipitation, using a nominal 30-year, greater than 2.5 mm 0.10 inch precipitation amount parameter, as indicated on the Station Report for the NOAA location closest to the project site as the basis for establishing a "Weather Calendar" showing the number of anticipated non-workdays for each month due to adverse weather, in addition to Saturdays, Sundays and all Federal Holidays as non-work days.

Use the following schedule of anticipated monthly non-work days due to adverse weather as the basis for establishing a "Weather Calendar" showing the number of anticipated non-workdays for each month due to adverse weather, in addition to Saturdays, Sundays and all Federal and State Holidays as non-work days.

01 32 16.00 20 - 4

MONTHLY ANTICIPATED ADVERSE WEATHER DELAYS

JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC

[2][_] [2][_] [2][_] [2][_] [2][_] [2][_] [2][_] [2][_] [2][_] [2][_] [2][_] [2][_]

Assign the Weather Calendar to any activity that could be impacted by adverse weather.

The Project Manager will issue a modification in accordance with the contract clauses, giving the Contractor a time extension for the difference of days between the anticipated and actual adverse weather delay if the number of actual adverse weather delay days exceeds the number of days anticipated for the month in which the delay occurs and the adverse weather delayed activities are critical to contract completion.

A lost workday due to weather conditions is defined as a day in which the Contractor cannot work at least 50 percent of the day on the impacted activity.

1.3.1.3 Activity Identification

a. Identify Government, Construction Quality Management (CQM), Construction activities planned for the project and other activities that could impact project completion if delayed.

b. Identify administrative type activity/milestones including pre-construction submittal and permit requirements prior to demolition or construction stage.

c. Create separate activities for each Phase, Area, Floor Level, and Location the activity is occurring.

d. Do not use construction category activity to represent non-work type reference (Such as, Serial Letter or Request for Information) in NAS.

e. Place non-work reference within P6 activity details notebook. Activity categories included in the schedule are specified below.

1.3.1.4 Responsibility Code

Assign each activity its appropriate Responsibility Code indicating responsibility to accomplish the work indicated by the activity, Phase Code and Work Location Code.

1.3.1.5 Microsoft Project 2010 Settings and Parameters

Use the following MS Project 2010 settings and parameters in preparing the Baseline Schedule:

a. The Network must have a minimum of 30 construction activities.

b. No on-site construction activity may have durations in excess of 20 working days.

c. Critical is defined as having zero days of Total Slack. Within the Baseline Schedule no more than 20 percent of the activities shall be critical.

01 32 16.00 20 - 5

d. Logic: include the following setting: File, Options, Schedule tab - Split in-progress tasks - must be selected.

e. Status Date gridline is displayed in the Gantt Chart view.

f. Task Type is set to Fixed Work for "boots-on-the-ground" construction activities.

g. Task Type is set to Fixed Duration for design activities, submittals, Government reviews, procurement, material/equipment delivery, and utility outages.

h. "Effort Driven" is turned ON for Fixed Duration tasks.

i. Time Periods established for the project are set to 8 Hrs/Day, 40 Hrs/Week and 20 days/month.

j. Week starts on Monday must be selected.

k. Default start time is set to 8am (0800).

l. Default end time is set to 5pm (1700).

1.3.1.7 Cost Loading Microsoft Project 2010 Schedules

Assign material, labor and equipment costs to their respective Construction Activities.

Assign material and equipment costs, for which payment will be requested in advance of installation, to their respective procurement activity (i.e. the material/equipment on-site activity). Evenly disperse overhead and profit to each activity over the duration of the project.

Cost loading must total to 100 percent of the value of the contract.

1.3.1.7.1 Software Settings

a. Resource Sheet

(1) Resource Name: Enter each code and resource for the project

(2) Type: Set to "Material"

(3) Material Label: Enter units of measurement for each resource

(4) Std. Rate: Enter unit cost for each resource

(5) Accrue at: Set to "Prorated"

b. Assigning Resources to Each Activity

(1) Select each activity in Gantt Chart

(2) Assign resources, Resource Tab

(3) Select each resource and enter the quantity of the units; then, assign the resource(s) to the activity

c. Baseline for Earned Value Calculation, File Tab, Options, Advanced, Default task Earned Value method: Set to "Physical % Complete" or as directed by the Project Manager.

01 32 16.00 20 - 6

1.3.1.7.2 Tabular Reports

1.3.1.7.2.1 Tracking Gantt Schedule with Cost Table

Submit a Tracking Gantt Schedule with each schedule update showing activity baseline cost, cost percent complete, and Budgeted Cost of Work Performed (BCWP), as directed by the Project Manager.

1.3.1.7.2.2 Earned Value Over Time Report

a. With each schedule submission, submit Earned Value Over Time Report S-Curves indicating Planned Value to the contract completion date based on projected early and late activity finish dates and Earned Value.

b. Revise Earned Value Over Time Report S-Curves when the contract is modified, or as directed by the Project Manager.

1.3.2 Bar Chart Schedule

The Bar Chart must, as a minimum, show work activities, submittals, Government review periods, material/equipment delivery, utility outages, on-site construction, inspection, testing, and closeout activities. The Bar Chart must be time scaled and generated using an electronic spreadsheet program.

1.3.3 Schedule Submittals and Procedures

Submit Schedules and updates in hard copy and on electronic media that is acceptable to the Project Manager.