Bid_#_2027-16_Davis_Lodge_Roof_Replacement_&_Kitchen_Remodel_-_Scope_of_Work_Project_Manual.pdf

PROJECT MANUAL

FOR

City of Bloomington

Davis Lodge Roof-Kitchen

Bloomington, IL

Project No: 02600932.001

October 16, 2026

200 W. College Avenue, Suite 301 Normal, IL 61761 (309) 663-8436 www.f-w.com

License Expiration Date: __________________

Signature: ___________________

Date Signed: ___________________

11/30/2026

10/16/2026

City of Bloomington - COB - Davis Lodge Roof-Kitchen

PROJECT NO.: 02600932.001

Table of Contents 00 01 10 - 1

TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

00 01 10 TABLE OF CONTENTS 1

00 01 15 LIST OF DRAWING SHEETS 1

DIVISION 01 - GENERAL REQUIREMENTS

01 10 00 SUMMARY 3

01 20 00 PRICE AND PAYMENT PROCEDURES 3

01 23 00 ALTERNATES 1

01 25 00 SUBSTITUTION PROCEDURES 3

01 30 00 ADMINISTRATIVE REQUIREMENTS 7

01 33 10 CADD FILE REQUESTS 1

01 33 11 ELECTRONIC FILES TRANSFER TO CONTRACTOR AGREEMENT 3

01 40 00 QUALITY REQUIREMENTS 2

01 60 00 PRODUCT REQUIREMENTS 2

01 70 00 EXECUTION AND CLOSEOUT REQUIREMENTS 6

01 74 19 CONSTRUCTION WASTE MANAGEMENT AND DISPOSAL 2

01 78 00 CLOSEOUT SUBMITTALS 4

DIVISION 05 - METALS

05 51 33 METAL LADDERS 2

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 01 50.19 PREPARATION FOR RE-ROOFING 3

07 31 13 ASPHALT SHINGLES 5

07 31 16 METAL SHINGLES 5

07 62 00 SHEET METAL FLASHING AND TRIM 3

DIVISION 12 - FURNISHINGS

12 35 30 RESIDENTIAL CASEWORK 3

12 36 00 COUNTERTOPS 3

City of Bloomington - COB - Davis Lodge Roof-Kitchen

PROJECT NO.: 02600932.001

List of Drawing Sheets 00 01 15 - 1

SECTION 00 01 15 - LIST OF DRAWING SHEETS

CO COVER SHEET

GENERAL

G0.1 GENERAL INFORMATION

ARCHITECTURAL

AD1.1 FIRST FLOOR DEMOLITION PLAN

AD2.1 ROOF DEMOLITION PLAN

A2.1 ROOF PLAN - BASE BID

A2.2 ROOF PLAN - ALTERNATE #1

A2.3 ROOF DETAILS

A2.4 METAL ROOF DETAILS - ALTERNATE #1

A8.1 INTERIOR ELEVATIONS AND ENLARGED PLANS - ALTERNATE #2

A8.2 CASEWORK DETAILS - ALTERNATE #2

INTERIORS

I0.1 FINISH SCHEDULES AND GENERAL INFORAMTION - ALTERNATE #2

END OF SECTION

PROJECT NO.: 02600932.001

Summary 01 10 00 - 1

SECTION 01 10 00 - SUMMARY

PART 1 GENERAL

1.1. PROJECT

A. Project Name: Davis Lodge Roof-Kitchen

B. Owner's Name: City of Bloomington.

C. Architect's Name: Farnsworth Group, Inc.

D. Davis Lodge is a historic lakefront rental facility located on Lake Bloomington and serves as a popular venue for weddings, reunions, and other community events. The project consists of roofing replacement and select interior renovations intended to extend the service life of the facility, improve building performance, and enhance functionality for ongoing public use.

1. The Work includes replacement of the existing roofing system and, if awarded, renovation of the existing kitchen. Due to the lack of existing record drawings, field verification of existing conditions will be required.

2. The project is organized as follows:

a. Base Bid

1) Remove and replace the existing asphalt shingle roof system with a new architectural asphalt shingle roofing system.

b. Alternate No. 1

1) Provide a new metal shingle roofing system in lieu of the architectural asphalt shingle roofing system included in the Base Bid.

c. Alternate No. 2

1) Renovate the existing kitchen, including replacement of cabinetry, countertops, and plumbing fixtures; installation of new interior finishes; and associated modifications to building systems necessary to support the renovation.

3. The Contract Documents are structured to provide flexibility in project award based on available funding through the use of bid alternates.

1.2. CONTRACT DESCRIPTION

A. Contract Type: A single prime contract based on a Stipulated Price as described in Document 00 52 00

- Agreement Form.

1.3. DESCRIPTION OF ALTERATIONS WORK

A. Scope of demolition and removal work is indicated on drawings and specified in Section 02 41 00.

B. Scope of alterations work is indicated on drawings.

1.4. OWNER OCCUPANCY

A. Owner will continue to occupy the existing building during the entire construction period.

B. Carefully coordinate with Owner to develop a schedule of construction activities that minimizes conflict and to facilitates Owner's operations.

C. Schedule the Work to accommodate Owner occupancy.

1.5. CONTRACTOR USE OF SITE AND PREMISES

A. Construction Operations: Limited to areas noted on Drawings.

B. Arrange use of site and premises to allow:

1. Normal Owner occupancy and operations.

2. Use of site by the public for scheduled events as described prior.

PROJECT NO.: 02600932.001

Summary 01 10 00 - 2

a. Schedule deliveries to minimize use of driveways and entrances by construction operations.

b. Schedule deliveries to minimize space and time requirements for storage of materials and equipment on-site.

C. Provide access to and from site as required by law and by Owner:

1. Emergency Building Exits During Construction: Keep all exits required by code open during construction period; provide temporary exit signs if exit routes are temporarily altered.

2. Do not obstruct roadways, sidewalks, or other public ways without permit.

D. Condition of Existing Building: Maintain portions of existing building affected by construction operations in a weather-tight condition throughout construction period until Substantial Completion of new building. Repair damage caused by construction operations to maintain safe structure.

E. Protect existing site improvements and public access ways to remain. If pavements, curbs, , and other site improvements to remain are damaged or defaced during construction operations, repair and restore all to condition at start of construction or better.

F. Keep paved driveways on Owner’s property, full project site and public streets, alleys and walkways clear of earth and debris spillage from trucking and traffic involved in construction operations.

1.6. WORK RESTRICTIONS

A. Work Restrictions, General: Comply with restrictions on construction operations.

1. Comply with limitations on use of public streets and other requirements of authorities having jurisdiction.

2. On-Site Work Hours: Limit work in the existing building to normal business working hours of 7 a.m. to 5 p.m., Monday through Friday, except as otherwise indicated.

a. Weekend Hours: same as workday hours.

b. Early Morning Hours: Comply with regulations from authorities having jurisdiction for restrictions on noisy work.

c. Hours for Utility Shutdowns: Coordinate with owner.

3. Existing Utility Interruptions: Do not interrupt utilities serving facilities unless permitted under the following conditions and then only after providing temporary utility services according to requirements indicated:

a. Notify Architect and Owner not less than 7 business days in advance of proposed utility interruptions.

b. Obtain Owner's written permission before proceeding with utility interruptions.

4. Noise, Vibration, Dust and Odors: Coordinate operations that may result in high levels of noise and vibration, odors, or other disruption with owner.

a. Notify Architect and Owner not less than two days in advance of proposed disruptive operations.

b. Obtain Owner's Liaison’s written permission before proceeding with disruptive operations.

c. Comply with applicable noise control laws, ordinances, and regulations. Where field sound measurements exceed allowable limits cease operating such equipment and repair or replace it with equipment that complies with requirements.

d. Dust: Take precautions necessary to keep Work under this contract and adjoining properties free from dust. Perform dust control in compliance with authorities having jurisdiction. Follow procedures and protocol to prevent pollution of land, air, and water.

PROJECT NO.: 02600932.001

Summary 01 10 00 - 3

5. Nonsmoking Site and Building: Smoking or use of any tobacco is not permitted within the building or on the site.

6. Controlled Substances: Use controlled substances on the Project site are not permitted.

Contractor is responsible for maintaining a drug-free work place.

7. Employee Identification: Provide identification tags for Contractor personnel working on the Project site. Require personnel to utilize identification tags at all times.

8. Employee List: Provide a list of all contractor and subcontractor employees to the City of Bloomington prior to commencement of construction activities.

1.7. SPECIFICATION AND DRAWING CONVENTIONS

A. Specification Content: The Specifications use certain conventions for the style of language and the intended meaning of certain terms, words, and phrases when used in particular situations. These conventions are as follows:

1. Specification requirements are to be performed by Contractor unless specifically stated otherwise.

B. Division 01 General Requirements: Requirements of Sections in Division 01 apply to the Work of all Sections in the Specifications.

C. Drawing Coordination: Requirements for materials and products identified on the Drawings are described in detail in the Specifications. One or more of the following are used on the Drawings to identify materials and products:

1. Terminology: Materials and products are identified by the typical generic terms used in the individual Specifications Sections.

2. Abbreviations: Materials and products are identified by abbreviations scheduled on Drawings.

PROJECT NO.: 02600932.001

Price and Payment Procedures 01 20 00 - 1

SECTION 01 20 00 - PRICE AND PAYMENT PROCEDURES

PRICE AND PAYMENT PROCEDURES

PART 1 GENERAL

1.1. SECTION INCLUDES

A. Procedures for preparation and submittal of applications for progress payments.

B. Documentation of changes in Contract Sum and Contract Time.

C. Change procedures.

D. Correlation of Contractor submittals based on changes.

E. Procedures for preparation and submittal of application for final payment.

1.2. RELATED REQUIREMENTS

1.3. SCHEDULE OF VALUES

A. Use Schedule of Values Form: AIA G703, edition stipulated in the Agreement.

B. Electronic media printout including equivalent information will be considered in lieu of standard form specified; submit draft to Architect for approval.

C. Forms filled out by hand will not be accepted.

D. Submit Schedule of Values in duplicate within 15 days after date of Owner-Contractor Agreement.

E. Format: Utilize the Table of Contents of this Project Manual. Identify each line item with number and title of the specification section. Identify site mobilization.

F. Include in each line item, the amount of Allowances specified in this section. For unit cost Allowances, identify quantities taken from Contract Documents multiplied by the unit cost to achieve the total for the item.

G. Include separately from each line item, a direct proportional amount of Contractor's overhead and profit.

H. Revise schedule to list approved Change Orders, with each Application For Payment.

1.4. APPLICATIONS FOR PROGRESS PAYMENTS

A. Payment Period: Submit at intervals stipulated in the Agreement.

B. Use Form AIA G702 and Form AIA G703, edition stipulated in the Agreement.

C. Electronic media printout including equivalent information will be considered in lieu of standard form specified; submit sample to Architect for approval.

D. Forms filled out by hand will not be accepted.

E. Execute certification by signature of authorized officer.

F. Submit one electronic and one hard-copies of each Application for Payment.

G. Include the following with the application:

1. Transmittal letter as specified for submittals in Section 01 30 00.

2. Partial release of liens from major subcontractors and vendors.

3. Affidavits attesting to off-site stored products.

H. When Architect requires substantiating information, submit data justifying dollar amounts in question. Provide one copy of data with cover letter for each copy of submittal. Show application number and date, and line item by number and description.

PROJECT NO.: 02600932.001

Price and Payment Procedures 01 20 00 - 2

1.5. MODIFICATION PROCEDURES

A. For minor changes not involving an adjustment to the Contract Sum or Contract Time, Architect will issue instructions directly to Contractor.

B. For other required changes, Architect will issue a document signed by Owner instructing Contractor to proceed with the change, for subsequent inclusion in a Change Order.

1. The document will describe the required changes and will designate method of determining any change in Contract Sum or Contract Time.

2. Promptly execute the change.

C. For changes for which advance pricing is desired, Architect will issue a document that includes a detailed description of a proposed change with supplementary or revised drawings and specifications, a change in Contract Time for executing the change with a stipulation of any overtime work required and the period of time during which the requested price will be considered valid. Contractor shall prepare and submit a fixed price quotation within 14 days.

D. Contractor may propose a change by submitting a request for change to Architect, describing the proposed change and its full effect on the work, with a statement describing the reason for the change, and the effect on the Contract Sum and Contract Time with full documentation. Document any requested substitutions in accordance with Section 01 60 00.

E. Computation of Change in Contract Amount: As specified in the Agreement and Conditions of the Contract.

1. For change requested by Architect for work falling under a fixed price contract, the amount will be based on Contractor's price quotation.

2. For change requested by Contractor, the amount will be based on the Contractor's request for a

Change Order as approved by Architect.

3. For pre-determined unit prices and quantities, the amount will based on the fixed unit prices.

F. Substantiation of Costs: Provide full information required for evaluation.

1. Provide the following data:

a. Quantities of products, labor, and equipment.

b. Taxes, insurance, and bonds.

c. Overhead and profit.

d. Justification for any change in Contract Time.

e. Credit for deletions from Contract, similarly documented.

2. Support each claim for additional costs with additional information:

a. Origin and date of claim.

b. Dates and times work was performed, and by whom.

c. Time records and wage rates paid.

d. Invoices and receipts for products, equipment, and subcontracts, similarly documented.

3. For Time and Material work, submit itemized account and supporting data after completion of change, within time limits indicated in the Conditions of the Contract.

G. Execution of Change Orders: Architect will issue Change Orders for signatures of parties as provided in the Conditions of the Contract.

H. After execution of Change Order, promptly revise Schedule of Values and Application for Payment forms to record each authorized Change Order as a separate line item and adjust the Contract Sum.

I. Promptly revise progress schedules to reflect any change in Contract Time, revise sub-schedules to adjust times for other items of work affected by the change, and resubmit.

PROJECT NO.: 02600932.001

Price and Payment Procedures 01 20 00 - 3

J. Promptly enter changes in Project Record Documents.

1.6. APPLICATION FOR FINAL PAYMENT

A. Prepare Application for Final Payment as specified for progress payments, identifying total adjusted Contract Sum, previous payments, and sum remaining due.

B. Application for Final Payment will not be considered until the following have been accomplished:

1. All closeout procedures specified in Section 01 70 00.

PART 2 PRODUCTS - NOT USED

PART 3 EXECUTION - NOT USED

PROJECT NO.: 02600932.001

Alternates 01 23 00 - 1

SECTION 01 23 00 - ALTERNATES

PART 1 GENERAL

1.1. SECTION INCLUDES

A. Description of Alternates.

B. Procedures for pricing Alternates.

1.2. ACCEPTANCE OF ALTERNATES

A. Alternates quoted on Bid Forms will be reviewed and accepted or rejected at Owner's option.

Accepted Alternates will be identified in the Owner-Contractor Agreement.

1.3. SCHEDULE OF ALTERNATES

A. Alternate No. 1

1. Provide a new metal shingle roofing system in lieu of the architectural asphalt shingle roofing system included in the Base Bid.

B. Alternate Bid No. 2

1. Renovate the existing kitchen, including replacement of cabinetry, countertops, and plumbing fixtures; installation of new interior finishes; and associated modifications to building systems necessary to support the renovation.

PART 2 PRODUCTS - NOT USED

PART 3 EXECUTION - NOT USED

PROJECT NO.: 02600932.001

Substitution Procedures 01 25 00 - 1

SECTION 01 25 00 - SUBSTITUTION PROCEDURES

PART 1 GENERAL

1.1. SECTION INCLUDES

A. Procedural requirements for proposed substitutions.

1.2. RELATED REQUIREMENTS

A. Section 01 30 00 - Administrative Requirements: Submittal procedures, coordination.

B. Section 01 60 00 - Product Requirements: Fundamental product requirements, product options, delivery, storage, and handling.

1.3. DEFINITIONS

A. Substitutions: Changes from Contract Documents requirements proposed by Contractor to materials, products, assemblies, and equipment.

1. Substitutions for Cause: Proposed due to changed Project circumstances beyond Contractor's control.

a. Unavailability.

b. Regulatory changes.

2. Substitutions for Convenience: Proposed due to possibility of offering substantial advantage to the Project.

a. Substitution requests offering advantages solely to the Contractor will not be considered.

1.4. REFERENCE STANDARDS

A. CSI/CSC Form 1.5C - Substitution Request (During the Bidding/Negotiating Stage); Current Edition.

B. CSI/CSC Form 13.1A - Substitution Request (After the Bidding/Negotiating Phase); Current Edition.

PART 2 PRODUCTS - NOT USED

PART 3 EXECUTION

3.1. GENERAL REQUIREMENTS

A. A Substitution Request for products, assemblies, materials, and equipment constitutes a representation that the submitter:

1. Has investigated proposed product and determined that it meets or exceeds the quality level of the specified product, equipment, assembly, or system.

2. Agrees to provide the same warranty for the substitution as for the specified product.

3. Agrees to coordinate installation and make changes to other work that may be required for the work to be complete, with no additional cost to Owner.

4. Waives claims for additional costs or time extension that may subsequently become apparent.

5. Agrees to reimburse Owner and Architect for review or redesign services associated with re-approval by authorities.

B. Document each request with complete data substantiating compliance of proposed substitution with Contract Documents. Burden of proof is on proposer.

1. Note explicitly any non-compliant characteristics.

C. Content: Include information necessary for tracking the status of each Substitution Request, and information necessary to provide an actionable response.

1. Forms indicated in the Project Manual are adequate for this purpose, and must be used.

D. Limit each request to a single proposed substitution item.

PROJECT NO.: 02600932.001

Substitution Procedures 01 25 00 - 2

1. Submit an electronic document, combining the request form with supporting data into single document.

3.2. SUBSTITUTION PROCEDURES DURING PROCUREMENT

A. Submittal Time Restrictions:

B. Submittal Form (before award of contract):

1. Submit substitution requests by completing CSI/CSC Form 1.5C - Substitution Request. See this form for additional information and instructions. Use only this form; other forms of submission are unacceptable.

C. Owner will consider requests for substitutions only if submitted at least 5 days prior to the date for receipt of bids.

3.3. SUBSTITUTION PROCEDURES DURING CONSTRUCTION

A. Submittal Form (after award of contract):

1. Submit substitution requests by completing CSI/CSC Form 13.1A - Substitution Request (After

Bidding/Negotiating). See this form for additional information and instructions. Use only this form; other forms of submission are unacceptable.

B. Submit request for Substitution for Cause within 14 days of discovery of need for substitution, but not later than 14 days prior to time required for review and approval by Architect, in order to stay on approved project schedule.

C. Submit request for Substitution for Convenience immediately upon discovery of its potential advantage to the project, but not later than 14 days prior to time required for review and approval by Architect, in order to stay on approved project schedule.

1. In addition to meeting general documentation requirements, document how the requested substitution benefits the Owner through cost savings, time savings, greater energy conservation, or in other specific ways.

2. Document means of coordinating of substitution item with other portions of the work, including work by affected subcontractors.

3. Bear the costs engendered by proposed substitution of:

a. Owner's compensation to the Architect for any required redesign, time spent processing and evaluating the request.

b. Other construction by Owner.

c. Other unanticipated project considerations.

D. Substitutions will not be considered under one or more of the following circumstances:

1. When they are indicated or implied on shop drawing or product data submittals, without having received prior approval.

2. Without a separate written request.

3. When acceptance will require revisions to Contract Documents.

3.4. RESOLUTION

A. Architect may request additional information and documentation prior to rendering a decision.

Provide this data in an expeditious manner.

B. Architect will notify Contractor in writing of decision to accept or reject request.

1. Architect's decision following review of proposed substitution will be noted on the submitted form.

PROJECT NO.: 02600932.001

Substitution Procedures 01 25 00 - 3

3.5. ACCEPTANCE

A. Accepted substitutions change the work of the Project. They will be documented and incorporated into work of the project by Change Order, Construction Change Directive, Architectural Supplementary Instructions, or similar instruments provided for in the Conditions of the Contract.

3.6. CLOSEOUT ACTIVITIES

A. See Section 01 78 00 - Closeout Submittals, for closeout submittals.

B. Include completed Substitution Request Forms as part of the Project record. Include both approved and rejected Requests.

PROJECT NO.: 02600932.001

Administrative Requirements 01 30 00 - 1

SECTION 01 30 00 - ADMINISTRATIVE REQUIREMENTS

PART 1 GENERAL

1.1. SECTION INCLUDES

A. General administrative requirements.

B. Electronic document submittal service.

C. Preconstruction meeting.

D. Site mobilization meeting.

E. Construction progress schedule.

F. Submittals for review, information, and project closeout.

G. Number of copies of submittals.

H. Requests for Information (RFI) procedures.

I. Submittal procedures.

1.2. RELATED REQUIREMENTS

A. Section 01 60 00 - Product Requirements: General product requirements.

B. Section 01 70 00 - Execution and Closeout Requirements: Additional coordination requirements.

C. Section 01 78 00 - Closeout Submittals: Project record documents; operation and maintenance data;

warranties and bonds.

1.3. GENERAL ADMINISTRATIVE REQUIREMENTS

A. Comply with requirements of Section 01 70 00 - Execution and Closeout Requirements for coordination of execution of administrative tasks with timing of construction activities.

B. Make the following types of submittals to Architect:

1. Requests for Interpretation (RFI).

2. Shop drawings, product data, and samples.

3. Test and inspection reports.

4. Manufacturer's instructions and field reports.

5. Applications for payment and change order requests.

6. Progress schedules.

7. Coordination drawings.

8. Correction Punch List and Final Correction Punch List for Substantial Completion.

9. Closeout submittals.

PART 2 PRODUCTS - NOT USED

PART 3 EXECUTION

3.1. ELECTRONIC DOCUMENT SUBMITTAL SERVICE

A. All documents transmitted for purposes of administration of the contract are to be in electronic (PDF, MS Word, or MS Excel) format, as appropriate to the document, and transmitted via an Internet-based submittal service that receives, logs and stores documents, provides electronic stamping and signatures, and notifies addressees via email.

1. Besides submittals for review, information, and closeout, this procedure applies to Requests for

Interpretation (RFIs), progress documentation, contract modification documents (e.g.

supplementary instructions, change proposals, change orders), applications for payment, field

PROJECT NO.: 02600932.001

Administrative Requirements 01 30 00 - 2 reports and meeting minutes, Contractor's correction punchlist, and any other document any participant wishes to make part of the project record.

2. Contractor and Architect are required to use this service.

3. It is Contractor's responsibility to submit documents in allowable format.

4. Subcontractors, suppliers, and Architect's consultants will be permitted to use the service at no extra charge.

5. Users of the service need an email address, internet access, and PDF review software that includes ability to mark up and apply electronic stamps (such as Adobe Acrobat, www.adobe.com, or Bluebeam PDF Revu, www.bluebeam.com), unless such software capability is provided by the service provider.

6. Paper document transmittals will not be reviewed; emailed electronic documents will not be reviewed.

7. All other specified submittal and document transmission procedures apply, except that electronic document requirements do not apply to samples or color selection charts.

B. Submittal Service: Use one of the following:

1. ProCore.

C. Project Closeout: Architect will determine when to terminate the service for the project and is responsible for obtaining archive copies of files for Owner.

3.2. PRECONSTRUCTION MEETING

A. Schedule meeting after Notice of Award.

B. Attendance Required:

1. Owner.

2. Architect.

3. Contractor.

C. Agenda:

1. Execution of Owner-Contractor Agreement.

2. Submission of executed bonds and insurance certificates.

3. Distribution of Contract Documents.

4. Submission of list of subcontractors, list of products, schedule of values, and progress schedule.

5. Designation of personnel representing the parties to Contract.

6. Procedures and processing of field decisions, submittals, substitutions, applications for payments, proposal request, Change Orders, and Contract closeout procedures.

7. Scheduling.

8. Materials staging.

9. Background checks.

D. Record minutes and distribute copies within two days after meeting to participants, with two copies to Architect, Owner, participants, and those affected by decisions made.

3.3. SITE MOBILIZATION MEETING

A. Attendance Required:

1. Contractor.

2. Owner.

3. Architect.

4. Contractor's superintendent.

5. Major subcontractors.

PROJECT NO.: 02600932.001

Administrative Requirements 01 30 00 - 3

B. Agenda:

1. Use of premises by Owner and Contractor.

2. Owner's requirements.

3. Construction facilities and controls provided by Owner.

4. Temporary utilities provided by Owner.

5. Security and housekeeping procedures.

6. Schedules.

7. Application for payment procedures.

8. Procedures for maintaining record documents.

C. Record minutes and distribute copies within two days after meeting to participants, with two copies to Architect, Owner, participants, and those affected by decisions made.

3.4. CONSTRUCTION PROGRESS SCHEDULE

A. Within 10 days after date of the Agreement, submit preliminary schedule defining planned operations for the first 60 days of work, with a general outline for remainder of work.

B. If preliminary schedule requires revision after review, submit revised schedule within 10 days.

C. Within 5 days after review of preliminary schedule, submit draft of proposed complete schedule for review.

D. Submit updated schedule with each Application for Payment.

3.5. REQUESTS FOR INTERPRETATION (RFI)

A. Definition: A request seeking one of the following:

1. An interpretation, amplification, or clarification of some requirement of Contract Documents arising from inability to determine from them the exact material, process, or system to be installed; or when the elements of construction are required to occupy the same space (interference); or when an item of work is described differently at more than one place in Contract Documents.

2. A resolution to an issue which has arisen due to field conditions and affects design intent.

B. Whenever possible, request clarifications at the next appropriate project progress meeting, with response entered into meeting minutes, rendering unnecessary the issuance of a formal RFI.

C. Preparation: Prepare an RFI immediately upon discovery of a need for interpretation of Contract Documents. Failure to submit a RFI in a timely manner is not a legitimate cause for claiming additional costs or delays in execution of the work.

1. Prepare a separate RFI for each specific item.

a. Review, coordinate, and comment on requests originating with subcontractors and/or materials suppliers.

b. Do not forward requests which solely require internal coordination between subcontractors.

2. Prepare using software provided by the Electronic Document Submittal Service.

3. Combine RFI and its attachments into a single electronic file. PDF format is preferred.

D. Reason for the RFI: Prior to initiation of an RFI, carefully study all Contract Documents to confirm that information sufficient for their interpretation is definitely not included.

1. Include in each request Contractor's signature attesting to good faith effort to determine from

Contract Documents information requiring interpretation.

2. Unacceptable Uses for RFIs: Do not use RFIs to request the following::

PROJECT NO.: 02600932.001

Administrative Requirements 01 30 00 - 4

a. Approval of submittals (use procedures specified elsewhere in this section).

b. Approval of substitutions (see Section - 01 60 00 - Product Requirements)

c. Changes that entail change in Contract Time and Contract Sum (comply with provisions of the Conditions of the Contract).

3. Improper RFIs: Requests not prepared in compliance with requirements of this section, and/or missing key information required to render an actionable response. They will be returned without a response, with an explanatory notation.

E. Content: Include identifiers necessary for tracking the status of each RFI, and information necessary to provide an actionable response.

1. Official Project name and number, and any additional required identifiers established in

Contract Documents.

2. Owner's, Architect's, and Contractor's names.

3. Discrete and consecutive RFI number, and descriptive subject/title.

4. Issue date, and requested reply date.

5. Reference to particular Contract Document(s) requiring additional information/interpretation.

Identify pertinent drawing and detail number and/or specification section number, title, and paragraph(s).

6. Annotations: Field dimensions and/or description of conditions which have engendered the request.

7. Contractor's suggested resolution: A written and/or a graphic solution, to scale, is required in cases where clarification of coordination issues is involved, for example; routing, clearances, and/or specific locations of work shown diagrammatically in Contract Documents. If applicable, state the likely impact of the suggested resolution on Contract Time or the Contract Sum.

F. Attachments: Include sketches, coordination drawings, descriptions, photos, submittals, and other information necessary to substantiate the reason for the request.

G. RFI Log: Prepare and maintain a tabular log of RFIs for the duration of the project.

1. Indicate current status of every RFI. Update log promptly and on a regular basis.

2. Note dates of when each request is made, and when a response is received.

3. Highlight items requiring priority or expedited response.

4. Highlight items for which a timely response has not been received to date.

5. Identify and include improper or frivolous RFIs.

H. Review Time: Architect will respond and return RFIs to Contractor within seven calendar days of receipt. For the purpose of establishing the start of the mandated response period, RFIs received after 12:00 noon will be considered as having been received on the following regular working day.

1. Response period may be shortened or lengthened for specific items, subject to mutual agreement, and recorded in a timely manner in progress meeting minutes.

I. Responses: Content of answered RFIs will not constitute in any manner a directive or authorization to perform extra work or delay the project. If in Contractor's belief it is likely to lead to a change to Contract Sum or Contract Time, promptly issue a notice to this effect, and follow up with an appropriate Change Order request to Owner.

1. Response may include a request for additional information, in which case the original RFI will be deemed as having been answered, and an amended one is to be issued forthwith. Identify the amended RFI with an R suffix to the original number.

2. Do not extend applicability of a response to specific item to encompass other similar conditions, unless specifically so noted in the response.

PROJECT NO.: 02600932.001

Administrative Requirements 01 30 00 - 5

3. Upon receipt of a response, promptly review and distribute it to all affected parties, and update the RFI Log.

4. Notify Architect within seven calendar days if an additional or corrected response is required by submitting an amended version of the original RFI, identified as specified above.

3.6. SUBMITTAL SCHEDULE

A. Submit to Architect for review a schedule for submittals in tabular format.

1. Submit at the same time as the preliminary schedule.

2. Coordinate with Contractor's construction schedule and schedule of values.

3. Format schedule to allow tracking of status of submittals throughout duration of construction.

4. Arrange information to include scheduled date for initial submittal, specification number and title, submittal category (for review or for information), description of item of work covered, and role and name of subcontractor.

5. Account for time required for preparation, review, manufacturing, fabrication and delivery when establishing submittal delivery and review deadline dates.

a. For assemblies, equipment, systems comprised of multiple components and/or requiring detailed coordination with other work, allow for additional time to make corrections or revisions to initial submittals, and time for their review.

3.7. SUBMITTALS FOR REVIEW

A. When the following are specified in individual sections, submit them for review:

1. Product data.

2. Shop drawings.

3. Samples for selection.

B. Submit to Architect for review for the limited purpose of checking for compliance with information given and the design concept expressed in Contract Documents.

C. Samples will be reviewed for aesthetic, color, or finish selection.

D. After review, provide copies and distribute in accordance with SUBMITTAL PROCEDURES article below and for record documents purposes described in Section 01 78 00 - Closeout Submittals.

3.8. SUBMITTALS FOR INFORMATION

A. When the following are specified in individual sections, submit them for information:

1. Design data.

2. Certificates.

3. Test reports.

4. Inspection reports.

5. Manufacturer's instructions.

6. Manufacturer's field reports.

7. Other types indicated.

B. Submit for Architect's knowledge as contract administrator or for Owner.

3.9. SUBMITTALS FOR PROJECT CLOSEOUT

A. Submit Correction Punch List for Substantial Completion.

B. Submit Final Correction Punch List for Substantial Completion.

C. When the following are specified in individual sections, submit them at project closeout in compliance with requirements of Section 01 78 00 - Closeout Submittals:

1. Project record documents.

PROJECT NO.: 02600932.001

Administrative Requirements 01 30 00 - 6

2. Operation and maintenance data.

3. Warranties.

4. Bonds.

5. Other types as indicated.

D. Submit for Owner's benefit during and after project completion.

3.10. NUMBER OF COPIES OF SUBMITTALS

A. Electronic Documents: Submit one electronic copy in PDF format; an electronically-marked up file will be returned. Create PDFs at native size and right-side up; illegible files will be rejected.

B. Samples: Submit the number specified in individual specification sections; one of which will be retained by Architect.

1. After review, produce duplicates.

2. Retained samples will not be returned to Contractor unless specifically so stated.

3.11. SUBMITTAL PROCEDURES

A. General Requirements:

1. Use a single transmittal for related items.

2. Transmit using approved form.

a. Use form generated by Electronic Document Submittal Service software.

3. Sequentially identify each item. For revised submittals use original number and a sequential numerical suffix.

4. Identify: Project; Contractor; subcontractor or supplier; pertinent drawing and detail number;

and specification section number and article/paragraph, as appropriate on each copy.

5. Apply Contractor's stamp, signed or initialed certifying that review, approval, verification of products required, field dimensions, adjacent construction work, and coordination of information is in accordance with the requirements of the work and Contract Documents.

a. Submittals from sources other than the Contractor, or without Contractor's stamp will not be acknowledged, reviewed, or returned.

6. Schedule submittals to expedite the Project, and coordinate submission of related items.

a. For each submittal for review, allow 15 days excluding delivery time to and from the Contractor.

b. For sequential reviews involving Architect's consultants, Owner, or another affected party, allow an additional 7 days.

7. Identify variations from Contract Documents and product or system limitations that may be detrimental to successful performance of the completed work.

8. Provide space for Contractor and Architect review stamps.

9. When revised for resubmission, identify all changes made since previous submission.

10. Distribute reviewed submittals. Instruct parties to promptly report inability to comply with requirements.

11. Incomplete submittals will not be reviewed, unless they are partial submittals for distinct portion(s) of the work, and have received prior approval for their use.

12. Submittals not requested will be recognized, and will be returned "Not Reviewed", B. Product Data Procedures:

1. Submit only information required by individual specification sections.

2. Collect required information into a single submittal.

3. Do not submit (Material) Safety Data Sheets for materials or products.

PROJECT NO.: 02600932.001

Administrative Requirements 01 30 00 - 7

C. Shop Drawing Procedures:

1. Prepare accurate, drawn-to-scale, original shop drawing documentation by interpreting Contract

Documents and coordinating related work.

2. Do not reproduce Contract Documents to create shop drawings.

3. Generic, non-project-specific information submitted as shop drawings do not meet the requirements for shop drawings.

3.12. SUBMITTAL REVIEW

A. Submittals for Review: Architect will review each submittal, and approve, or take other appropriate action.

B. Submittals for Information: Architect will acknowledge receipt and review. See below for actions to be taken.

C. Architect's actions will be reflected by marking each returned submittal using virtual stamp on electronic submittals.

1. Notations may be made directly on submitted items and/or listed on appended Submittal

Review cover sheet.

D. Architect's and consultants' actions on items submitted for review:

1. Authorizing purchasing, fabrication, delivery, and installation:

a. "No Exceptions or No Exceptions Taken ", or language with same legal meaning.

b. "Furnish as Corrected", or language with same legal meaning.

1) At Contractor's option, submit corrected item, with review notations acknowledged and incorporated.

2) If specifically noted or requested on the submittal review, resubmit corrected itemwith review notations acknowledged and incorporated. Resubmit separately, or as part of project record documents.

2. Not Authorizing fabrication, delivery, and installation:

a. "Revise and Resubmit or Exceptions Noted".

1) Resubmit revised item, with review notations acknowledged and incorporated.

2) Non-responsive resubmittals may be rejected.

b. "Not Accepted or Rejected".

1) Submit item complying with requirements of Contract Documents.

E. Architect's and consultants' actions on items submitted for information:

1. Items for which no action was taken:

a. "Not Reviewed or Received" - to notify the Contractor that the submittal has been received for record only.

2. Items for which action was taken:

a. "Reviewed" - no further action is required from Contractor.

PROJECT NO.: 02600932.001

CADD File Requests 01 33 10 - 1

SECTION 01 33 10 - CADD FILE REQUESTS

RELATED DOCUMENTS

1.1. DRAWINGS AND GENERAL PROVISIONS OF THE CONTRACT, INCLUDING GENERAL AND SUPPLEMENTARY

CONDITIONS AND OTHER DIVISION 01 SPECIFICATION SECTIONS, APPLY TO THIS SECTION.

1.2. SUMMARY

A. Architect/Engineer's AutoCAD (.DWG) and Revit (.RVT) electronic files may be made available to facilitate Contractor’s understanding of the Project.

B. To request AutoCAD or Revit files, Contractor shall email the Architect identifying the drawing files and format of electronic CADD files requested.

1. The Architect shall complete Farnsworth Group's standard "Electronic Files Transfer to

Contractor Agreement" and return to contractor for signature prior to transferring electronic files.

C. Related Requirements:

1. Division 01 Section “Submittal Procedures” for submittal requirements and procedures.

2. Division 01 Section "Project Record Documents" for submitting record Drawings, record

Specifications, and record Product Data.

1.3. SUBMITTAL ADMINISTRATIVE REQUIREMENTS

A. Architect/Engineers’ Digital Data Files: Electronic digital data files of the Contract Drawings will be provided by Architect/Engineer for Contractor's use in preparing submittals. Refer to Section 013300

- Submittal Procedures for specific information.

PART 2 - PRODUCTS (NOT USED)

PART 3 - EXECUTION (NOT USED)

NOTE: SEE SECTION 01 33 11 - ELECTRONIC FILES TRANSFER TO CONTRACTOR AGREEMENT FOR FOR

ARCHITECT/ENGINEER'S ELECTRONIC MEDIA/CADD AGREEMENT FORM.

END OF SECTION 01 3310

PROJECT NO.: 02600932.001

Electronic Files Transfer to Contractor Agreement

01 33 11 - 1

SECTION 01 33 11 - ELECTRONIC FILES TRANSFER TO CONTRACTOR AGREEMENT

ELECTRONIC FILES TRANSFER TO CONTRACTOR AGREEMENT

THIS AGREEMENT, MADE AND ENTERED INTO THIS ____ DAY OF ___________, 20__, BY AND BETWEEN FARNSWORTH GROUP, INC., HEREINAFTER REFERRED TO AS FARNSWORTH GROUP, LIQUIDATED DAMAGES, WITH REFERENCE TO ITS AGREEMENT WITH XYZ CORPORATION, HEREINAFTER REFERRED TO AS OWNER, FOR SITE VISIT NOTIFICATION LOCATION, HEREINAFTER REFERRED TO AS PROJECT, AND

________________________________________, HEREINAFTER REFERRED TO AS CONTRACTOR.

WHEREAS, FARNSWORTH GROUP HAS PREPARED ELECTRONIC FILES WHICH CONTAIN MACHINE-READABLE INFORMATION OR CERTAIN INFORMATION FOR THE PROJECT REFERENCED HEREIN (HEREINAFTER

REFERRED TO AS “PROJECT FILES”), AND;

WHEREAS, FARNSWORTH GROUP PROJECT FILES INCLUDE 2-DIMENSIONAL INFORMATION, 3-DIMENSIONAL

INFORMATION, AND TEXT-BASED INFORMATION, AND;

WHEREAS, FARNSWORTH GROUP HAS PREPARED PROJECT FILES TO PRODUCE SPECIFIC HARD COPY

CONTRACT DRAWINGS AND SPECIFICATIONS AND NOT FOR THE PURPOSES OF CONSTRUCTION OR

COORDINATION OF ASPECTS OF CONSTRUCTION, AND;

WHEREAS, CONTRACTOR HAS REQUESTED FARNSWORTH GROUP’S PROJECT FILES TO FACILITATE

CONTRACTOR’S UNDERSTANDING OF THE PROJECT, BUT NOT TO BE USED IN LIEU OF CONTRACT

DOCUMENTS OR FOR THE PURPOSE OF DETERMINING CONTRACTOR’S MEANS AND METHODS OF

CONSTRUCTION, AND;

WHEREAS, FARNSWORTH GROUP AND CONTRACTOR RECOGNIZE THAT THE PROJECT FILES ARE SUBJECT TO

ALTERATION, EITHER INTENTIONALLY OR UNINTENTIONALLY, DUE TO, AMONG OTHER CAUSES,

TRANSMISSION, CONVERSION, MEDIA DEGRADATION, SOFTWARE ERROR OR HUMAN ALTERATION, AND;

WHEREAS, FARNSWORTH GROUP AND CONTRACTOR UNDERSTAND THAT THE TRANSFER OF PROJECT FILES FROM THE SYSTEM AND FORMAT USED BY FARNSWORTH GROUP TO AN ALTERNATE SYSTEM OR FORMAT

CANNOT BE ACCOMPLISHED WITHOUT THE INTRODUCTION OF ANOMALIES AND/OR ERRORS, AND;

WHEREAS, FARNSWORTH GROUP AND CONTRACTOR ACKNOWLEDGE THAT PROJECT FILES ARE NOT THE

CONTRACT DOCUMENTS, AND;

WHEREAS, FARNSWORTH GROUP WILL SUPPLY ITS PROJECT FILES TO CONTRACTOR, BUT ONLY BASED UPON

THE EXPRESS TERMS AND CONDITIONS SET FORTH HEREIN;

THEREFOR, IN CONSIDERATION OF THE RECITALS ABOVE, IN CONSIDERATION OF FARNSWORTH GROUP SUPPLYING ITS PROJECT FILES TO CONTRACTOR AND IN CONSIDERATION OF THE COVENANTS AND CONDITIONS AGREED TO BY CONTRACTOR AS SET FORTH HEREIN, ALL OF WHICH SHALL BE DEEMED TO BE SUFFICIENT CONSIDERATION TO SUPPORT THIS AGREEMENT, FARNSWORTH GROUP AND CONTRACTOR

AGREE AS FOLLOWS:

A. This Agreement between Farnsworth Group and Contractor applies to the transfer from Farnsworth Group to Contractor of the following electronic information:

Project: Site Visit Notification Location Project Files: ____________________________________________________________

B. With regard to the transfer of any Project Files, the Parties hereto agree as follows:

1. These Project Files may not be used for any purpose not related specifically to the Project. Use of these files for development of other Projects; additions to the Project; or duplication of the Project at any location is expressly prohibited.

PROJECT NO.: 02600932.001

Electronic Files Transfer to Contractor Agreement

01 33 11 - 2

2. Farnsworth Group reserves the right to retain hardcopy originals of the Project Files delivered to Contractor and all such originals shall be controlling in the event of any inconsistency between the hardcopies and the Project Files.

3. Farnsworth Group will transfer to Contractor its Project Files, as of the date of this Agreement, for the exclusive use of Contractor.

4. The Project Files and documents are not contract documents as defined in the construction agreement entered into by Contractor, and Contractor expressly agrees that it is not relieved from any of its duties or obligations under the construction agreement. The Project Files are provided for information purposes only and are not intended as an end product. The Project Files may be a work in process, and Farnsworth Group is under no obligation to provide Contractor with any updated version(s) of the Project Files.

5. Contractor acknowledges and understands that the Project Files may not reflect all data contained in the contract documents, addenda, or other pertinent contract-related documents.

Contractor acknowledges and understands that the Project Files may contain data which is not included in the contract documents.

6. Contractor expressly agrees that the Project Files are not being furnished for the purposes of determining Contractor’s means and methods of construction, which remains the sole prerogative of Contractor, or for Contractor’s coordination of building systems required by Contractor’s agreement with Owner.

7. Contractor hereby waives any and all claims, known and unknown, now or in the future, against Farnsworth Group and its consultants, including its employees and representatives, and the Owner which in any way relate to Contractor’s use of Farnsworth Group’s Project Files.

Contractor further agrees that the Project Files shall not be used by Contractor in any manner to support a change order request, nor shall they be used as evidence in support of any such request or in support of any alleged error or omission on the part of Farnsworth Group or Owner. The Owner is hereby deemed to be an intended beneficiary of this provision.

8. In the event Contractor breached any provision contained herein, then Farnsworth Group, at its sole discretion, in addition to all remedies provided by law, shall be entitled to the return of all Farnsworth Group Project Files. Contractor shall promptly comply with any request by Farnsworth Group for the return of Farnsworth Group’s Project Files. This provision shall be specifically enforceable in the District Courts of Illinois.

C. With regard to the transfer of Building Information Model (BIM) digital files, both Farnsworth Group and Contractor agree as follows:

1. Farnsworth Group will provide only those BIM files created for this Project. There is no representation the BIM files are comprehensive or comprise a complete model of the building.

2. The level of development of the model, as defined in AIA Document AIA G202-2013, is understood to be level LOD 100, containing generalized systems or assemblies and some non-geometric information. After reviewing and verifying the accuracy of the information contained within Farnsworth Group’s BIM files, Contractor is authorized to develop its own model to a higher level of development for its own uses, but, in doing so, expressly agrees to assume all risks associated therewith.

D. Contractor acknowledges that digital Project Files constitute Intellectual Property: their use is the exclusive right of Farnsworth Group, and they shall not be shared with others without Farnsworth Group’s express written permission.

PROJECT NO.: 02600932.001

Electronic Files Transfer to Contractor Agreement

01 33 11 - 3

E. Contractor shall indemnify and hold harmless Farnsworth Group and its consultants, employees, directors, agents and representatives from any and all claims, including any such claim which may be filed by Owner, which in any way relates, whether in whole or in part, to Contractor’s use of or utilization of Farnsworth Group’s Project Files.

F. All claims, disputes or other matters in question between Farnsworth Group and Contractor arising out of or relating to this Agreement may, at Farnsworth Group’s sole option, and only upon the exercise of that sole option by Farnsworth Group, be submitted to mediation prior to submittal for resolution in a court of competent jurisdiction. In the event Farnsworth Group prevails at all in any such action, it shall recover all of its reasonable costs, expert witness fees and attorneys’ fees from Contractor.

G. The transfer of the Project Files shall not be deemed a sale. To the extent this transfer is construed otherwise, then ALL WARRANTIES, INCLUDING ANY EXPRESS WARRANTY OR IMPLIED WARRANTY OF

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE ARE HEREBY DISCLAIMED.

IN WITNESS WHEREOF, THE PARTIES HERETO HAVE EXECUTED THIS AGREEMENT AS OF THE DATES SET

FORTH BELOW.

FARNSWORTH GROUP, INC. CONTRACTOR:

BY: ______________________________ BY:______________________________

NAME: ___________________________ NAME: ___________________________

TITLE: ____________________________ TITLE: ____________________________

DATE: ____________________________ DATE:…