Section_L_25_Nov_2015.pdf

SECTION L

INSTRUCTIONS TO OFFERORS (ITO)

MULTIPLE AWARD CONSTRUCTION CONTRACT (MACC) III

SOURCE SELECTION

1. PROPOSAL PREPARATION INSTRUCTIONS

1.1. This acquisition will utilize Lowest Price Technically Acceptable (LPTA) source selection procedures in accordance with (IAW) the Federal Acquisition Regulation (FAR) 15.101-2.

Technical tradeoffs will not be made and no additional credit will be given for exceeding acceptability.

1.2. To assure timely and equitable evaluation of proposals, Offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including all stated terms, conditions, representations, certifications, and technical requirements, in addition to those identified as evaluation factors or sub-factors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. The Offeror shall submit all exceptions within 14 days of the release of the solicitation. The response shall consist of four (4) separate volumes; Volume I - Price, Volume II - Technical, Volume III - Past Performance;

and Volume IV - Contract Documentation.

2. PROGRAM STRUCTURE AND OBJECTIVES

2.1. The Government anticipates awarding approximately 5-6 Indefinite Delivery Indefinite Quantity

(IDIQ) contracts for the MACC III program. However, the Government reserves the right to award more or fewer total contracts if the Source Selection Authority (SSA) determines it is in the Government's best interest. If the Government determines to not award a contract, the Government will not be liable for costs incurred by Offeror(s). The SSA will consider the Government's expected volume of work, available funding, adequate competition, and the availability of best value proposals. The Government intends and reserves the right to award a contract without discussions; therefore, it is imperative that Offerors submit their best pricing and proposal terms initially. However, if during the evaluation period it is determined to be in the best interest of the Government to hold discussions, Offeror responses to Evaluation Notices (ENs) and the Final Proposal Revision (FPR) will be considered in making the source selection decision. Each contract will have a five-year ordering period. Individual task orders will be competed under fair opportunity rules cited in FAR 16.

2.2. Budget and Funding Information - Funding will be obligated on each task order awarded under the basic contracts. Notice to Offeror(s)/Supplier(s): Funds are not presently available for this effort.

No award will be made under this solicitation until funds are available. The Government reserves the right to cancel this solicitation, either before or after the closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an Offeror for any costs.

3. GENERAL INSTRUCTIONS

3.1. This section provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The Offeror's proposal must include all data and information requested and must be submitted IAW these instructions. Any Offeror who submits an incomplete package may be considered non-responsive and eliminated from the competition. The

Offer shall be compliant with the requirements as stated in the Statement of Work (SOW), Seed Project SOW, and Model Contract and Solicitation SF 1442. Non-conformance with these instructions may result in an “Unacceptable” proposal evaluation.

3.2. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal shall not simply rephrase, copy and paste, or restate the Government's requirements, but provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience, and will base its evaluation on the information presented in the Offeror's proposal.

3.3. Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

3.4. The proposal acceptance period is specified in Block 13 (D) of Section A (front page) of the model contract and solicitation. Offerors providing less than the specified calendar days for Government acceptance after the date offers are due may be considered non-compliant.

3.4.1. The Offeror agrees to hold the prices in their proposal for 240 calendar days from the date specified for receipt of offers.

3.5. IAW FAR 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

3.6. Point of Contact - The Contracting Officer (CO) is the sole point of contact for this acquisition.

Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address below:

AFSC OL:H/PZIEB

Attn: Marnie Whiteaker 6038 Aspen AVE, Bldg 1289 NE Wing Hill AFB, UT 84056 Office (801) 586-5546 marnie.whiteaker@us.af.mil

3.7. Debriefing

3.7.1. Pre Award Debriefings - The CO will promptly notify Offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing IAW FAR 15.505.

3.7.2. Post Award Debriefings - The CO will notify unsuccessful Offerors in the competitive range of the source selection decision IAW FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as applicable.

3.8. Discrepancies - If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the CO in writing with supporting rationale. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

3.9. Electronic Reference Documents - All referenced documents for this solicitation are available on the

Federal Business Opportunities (FedBizOpps) website at http://www.fedbizopps.gov. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation, including updates.

3.10. Oral Presentation - Oral presentations will not be allowed.

3.11. Amendments to Solicitation - If this Request for Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged and in full force and effect. Offerors shall acknowledge receipt of any amendment to this request by the date and time specified in the amendment(s) by signing and returning the front page of each.

3.12. Submission, Modification, Revision, and Withdrawal of Proposals

3.12.1. Proposals and modifications to proposals shall be submitted in both paper and electronic media to the address located in paragraph 3.6 of this document and shall include the time and date specified for receipt, the solicitation number, and the name and address of the Offeror. Late proposals will only be considered IAW FAR 15.208.

3.12.2. Acceptable evidence to establish the time of receipt at the Government installation includes the time and date stamp of that installation on the proposal wrapper, other documentary evidence of receipt maintained by the installation, or oral testimony or statements of Government personnel.

3.12.3. Proposals may be withdrawn by written notice received at any time before award.

Proposals may also be withdrawn in person by an Offeror or an authorized representative, if the identity of the person requesting the withdrawal is established and the person signs a receipt for the proposal before award.

3.13. Organization/Number of Copies/Page Limits

3.13.1. The title page of each volume must show-

3.13.1.1. Solicitation Number

3.13.1.2. Name, address, telephone and facsimile numbers, Commercial and Government Entity (CAGE) code, Data Universal Numbering System (DUNS) number, and email address of the Offeror

3.13.1.3. Volume number and name (e.g. Volume I, Price) and copy number (i.e. Original, copy 1, copy 2, etc.)

3.13.2. The Offeror shall prepare the proposal as set forth in Table 1 - Proposal Organization.

The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies specified. Each volume identified in the table shall be separately bound in three-ring, loose-leaf binders. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Table 1 - Proposal Organization

VOLUME SECTION L

PARAGRAPH NO.

VOLUME TITLE COPIES PAGE LIMIT

I 4.0 Price Original plus 1 Hardcopy, and 2 CDs

Unlimited, Pricing Assumptions &

Estimating Techniques and Methods limited to 2 pgs.

II 5.0 Technical

Acceptability Original plus 1 Hardcopy, and 2 CDs Sub-factor 1:

- 200 pages, excluding Safety Plan – unlimited pages

Sub-factor 2: 100 pages

Sub-factor 3: 50 pages

III 6.0 Past Performance Original plus 1 Hardcopy and 1 CD

15 pages

IV 7.0 Contract Documentation

Original Hardcopy Unlimited

3.14. Page Limitations - Page limitations identified in Table 1 – Proposal Organization shall be treated as maximums. If page limitations are exceeded, the excess pages will not be read or considered and Offeror will be notified of such. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the ENs to the Offerors.

Each page shall be counted except the following: blank pages, title pages, tables of contents, tabs, glossaries, Cross Reference Matrix, and those noted in the Proposed Organization Tables and Figures as “Unlimited.”

3.15. Pricing Information - All pricing information shall be addressed ONLY in the Price Proposal.

3.16. Cross Referencing

3.16.1. Each volume shall be written on a standalone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted.

3.16.2. The Offeror shall fill out Table 2 - Cross Reference Matrix in the format below, indicating the proposal reference information as it relates to the Section L - Instructions to Offerors, and Section M - Evaluation Factors for Award. This shall be included in the Technical Volume (Volume II). The Cross Reference Matrix addresses each requirement within the Basic and Seed SOWs (Section J, Attachments 5 and 11) and sub-factors. The Offeror shall fill in each section independently labeled with the appropriate paragraph number or page number from their proposal that addresses the requirement or factor and sub-factor.

Table 2 - Cross Reference Matrix

Cross Reference Matrix Section L Section M Basic SOW Seed SOW Proposal

4.1 2.3.1, 2.3.2, 2.3.4

4.2 2.3.5 4.5

5.3 2.4.3

5.3.1 2.4.3.1.1 App. C

5.3.2 2.4.3.1.2 3.1

5.3.3 2.4.3.1.3 2.1

5.3.8 2.4.3.1.8 2.1.1

5.3.4 2.4.3.1.4 2.2

5.3.6 2.4.3.1.6 2.3

5.3.7 2.4.3.1.7 2.4

5.3.5 2.4.3.1.5 2.5

5.3.9 2.4.3.1.9 2.6

5.3.10 2.4.3.1.10 2.7

5.4 2.4.3.2

5.4.1 2.4.3.3

5.4.2 2.4.3.4 1.3.1.3

5.4.3 2.4.3.4 1.3.1.3, 2.2

5.4.4 2.4.3.6

5.4.5 2.4.3.7 2.1

5.5 2.4.4

5.5.1.1 2.4.4.1 1.1.1

5.5.1.2 2.4.4.2

5.5.1.3 2.4.4.3

5.5.2 2.4.4.4 3.4.2

5.5.3 2.4.4.5

6.1 2.5

6.1.1 2.5.1.1

6.1.2 2.5.1.2

7.1 2.6.1

7.3 2.6.3

7.4 2.6.4

7.5 2.6.6

7.6 2.6.5

3.17. Indexing

3.17.1. Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

3.17.2. Include an indexed list of Tables and Figures. Tables and Figures do not count against the page limitations for their respective volumes.

3.17.3. Glossary of Abbreviations and Acronyms - Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

3.18. Page Size and Format

3.18.1. A page is defined as each face of a sheet of paper containing information. Page size shall be 8.5 x 11 inches, not including foldouts, and printed on both sides. Sheets shall be double-sided which will count as two pages. Except for the reproduced sections of the solicitation document, the text shall be New Times Roman, font size shall be no less than 12 point, and lines shall be single spaced. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top, bottom, and sides. Pages shall be numbered sequentially by volume. These page format restrictions shall also apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

3.18.2. Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be legible and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume, be printed only on one side, and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics; not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 10 point. Tables and Charts will not count against the page count. These limitations shall apply to both electronic and hard copy proposals.

3.19. Binding and Labeling - Each volume of the proposal should be separately bound in a three-ring loose-leaf binder, which shall permit the volume to lie flat when open. Staples shall not be used.

The outside of each binder shall include a cover sheet, clearly marked as to volume number, title, original or copy number, solicitation identification and the Offeror's name. The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed IAW FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

3.20. Electronic Offers - The content and page size of electronic copies must be identical to the hard copies. In the event there is a discrepancy between the hard copy and electronic copy, the hard copy shall take precedence. For electronic copies, indicate on each CD the volume number and title.

Each volume shall be on a separate CD. Use separate files within each CD to permit rapid location of all portions, including sub-factor required plans, exhibits, annexes, and attachments, if any. The Offeror shall submit Volumes I – IV in electronic format, using read only CDs (i.e. CD-R). Re-writable CDs (i.e. CD-RW) shall NOT be used. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal, as applicable, shall be submitted in a format readable by Microsoft (MS) Word 2010, MS Excel 2010, and MS- Power Point 2010, or in a “word searchable” PDF format. The Price volume tables and charts shall be in MS Excel 2010 format. Word documents – Set “save as type” to “Word Document (*docx)” only. Excel spreadsheets – Set “Save as type” to Microsoft Excel Workbook (*xlsx).” PowerPoint presentation – Set “Save as type” to “Microsoft PowerPoint 2010 Presentation (*.pptx).” PDF formats shall ONLY be used for drawings, cut sheets, and related types of documents. Do not use PDF formats for Excel or PowerPoint material.

3.21. Distribution - The "original" proposal shall be identified. Proposals shall be addressed to the CO and mailed or hand-delivered to:

AFSC OL:H/PZIEB

Attn: Marnie Whiteaker 6038 Aspen AVE, Bldg 1289 NE Wing Hill AFB, UT 84056 Office (801) 586-5546 marnie.whiteaker@us.af.mil

4. VOLUME I - PRICE

4.1. General Instructions - The pricing evaluation criteria will be: (1) Reasonableness, (2) Balance, and

(3) Total Evaluated Price (TEP) as defined in Section M of the RFP which will be assessed from the information provided in this volume. Offerors shall review Section M to ensure the minimum requirements are met.

4.2. Total Evaluated Price (TEP) – All pricing detail shall be included in Section J Attachment 2 R1

Pricing Matrix IAW the below instructions. The Offeror shall not alter the formulas or content of the worksheets, and shall only populate the shaded cells IAW the instructions below. Although the Offeror may not alter spreadsheets other than populating indicated cells, the Offeror may alter column/row size to facilitate readability.

4.2.1. Offerors shall input fully- burdened Not To Exceed (NTE) Labor Rates into the section in the Rate Worksheet located in Section J Attachment 2 R1 Pricing Matrix – IAW the instructions contained thereon. Proposed NTE fully- burdened Labor Rates will be contractually binding ceiling rates that shall not be exceeded for any future task orders.

4.2.2. Offerors shall populate the “Rate Worksheet” and “Seed Project Division Detail WS,” located in Section J Attachment 2 R1 Pricing Matrix – IAW the instructions contained thereon. The Offeror shall populate the Professional labor category hours [not subject to the Construction Wage Rate Requirements Statute – formerly Davis Bacon Act (DBA)] for the Seed Project in the “Seed Project Rollup Costs WS.” The

Construction Costs will auto populate from the ‘Seed Project Division Detail WS’ (below, and the Professional labor category rates will auto populate from the ‘Rate Worksheet’ (see above). For the purposes of the Seed Project, all rates shall be proposed and evaluated at the ceiling or NTE level for Ordering Period 1. If the Offeror is selected for award, the Offeror will be at liberty to propose lower rates on future task orders.

4.2.3. Offerors shall input pricing for the Seed Project for each applicable division price field as identified in the Seed Project Division Detail Worksheet, located in the Section J Attachment 2 R1 Pricing Matrix – IAW the instructions contained thereon.

Proposed Seed Project prices are Firm-Fixed Price (FFP) and contractually binding.

A no bid or an omitted division field may result in an incomplete price submission. If a division is not applicable to the Seed Project, enter N/A in that division field. The TEP is for evaluation purposes for the basic contract award and Seed Project Task Order.

4.3. Pricing Information Requirements – IAW FAR 15.402, 15.403-1(b) and 15.403-3(a), “information other than cost or pricing data” may be required to support price reasonableness. If, after receipt of proposals, the CO determines that there is insufficient information available to determine the reasonableness of the proposed pricing, the Offeror may be required to submit additional information other than cost or pricing data. If during the source selection process the CO determines that adequate competition no longer exists, then cost and pricing data may be required.

4.4. Rounding - All total dollar amounts provided shall be rounded to the nearest dollar.

4.5. Pricing Assumptions - Summarize all significant pricing assumptions, scope limitations and qualifications of the Price proposal IAW with Table 1 – Proposal Organization, pricing assumptions shall not exceed two pages.

4.6. Estimating Techniques and Methods - When responding to the Price Volume requirements in the solicitation, the Offeror and associated subcontractors shall use generally accepted construction estimating techniques, such as RS Means or equivalent to develop their estimates on the Seed Project. Provide a summary description of your standard estimating system or methods.

4.7. Price Information - Information beyond that required by this instruction shall not be submitted unless you consider it essential to document or support your price position. All information relating to the proposed prices, including all required supporting documentation must be included in the section of the proposal designated as the Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

4.8. Submit the price proposal in Microsoft Word and Microsoft Excel worksheets as appropriate. Word documents and Excel spreadsheets must be editable and NOT password protected other than protections placed by the Government on Government provided files. Each CD-R shall be clearly labeled. The paper and electronic copies shall be clearly identified. PDF files are NOT acceptable for the price proposal.

5. VOLUME II – TECHNICAL ACCEPTABILITY

5.1. General - The Technical Volume shall be clear, specific, complete, and include sufficient detail for effective evaluation. Legibility, clarity and coherence are very important. Your responses will be evaluated against the Technical sub-factors defined in Section M, Evaluation Factors for Award.

Offerors should review Section M criteria to ensure the minimum requirements are met. Provide as specifically as possible the actual methodology the Offeror would use for accomplishing and satisfying each sub-factor. There will be no reference to rates or price in this volume. Offerors shall assume that the Government has no prior knowledge of their experience and certifications, and will base its evaluation on the information presented in the Offeror’s proposal. All the requirements specified in the solicitation are mandatory. By the Offeror’s proposal submission, the Offeror is representing that the company will perform ALL the requirements specified in the solicitation (including SOW); it is not necessary or desirable to tell us so in the proposal.

5.1.1. Adequate Responses - It is imperative that the Offeror fully describe and provide detail as to how the Offeror shall meet the sub-factor requirements. Do not merely copy and paste, rephrase or restate the objectives or reformulate the requirements specified in the solicitation. Evidence (which clearly demonstrates and supports the Offeror’s claims) is essential. The absence of such evidence may result in a technically “Unacceptable” proposal.

5.2. Volume Organization - The Technical Volume shall be organized according to the following general outline:

1. Table of Contents

2. List of Tables and Drawings

3. Glossary

4. Sub-Factor One – Seed Project – Renovation of Building 270

5. Sub-Factor Two – Architect-Engineer (A-E) Qualifications

6. Sub-Factor Three – Contractor Requirements

5.3. Sub-Factor One: Seed Project - Renovation of Building 270

The proposal shall include the following documentation:

5.3.1. A comprehensive Safety Plan to cover all expected safety concerns specified in the Basic SOW Section 3.3 and Appendix C for MACC III.

5.3.2. A Quality Control Plan (QCP) for the work identified in the Basic SOW Section 3.1 and IAW UFGS 01 45 00.00 10. The QCP shall comply with the applicable UFGS specification. The QCP shall also describe in detail how the project will be managed, including interim status reports, remediation and change management procedures to meet and maintain schedule milestones. The QCP shall also describe in detail the testing necessary for material control and how the mechanical systems will be commissioned.

5.3.3. A Demolition Plan that provides a detailed approach of how the requirements will be met, including a schedule that details each phase specified in the Seed Project SOW, Section 2.1. The plan shall describe how Paint Booth 1 operational time will be optimized. The plan shall provide removal procedures including the route of material removal considering airfield restrictions on the east side and salvage. The plan shall also include a section on sanding booth deconstruction. The deconstruction section shall describe in detail how the sanding booth will be disassembled to minimize damage and optimize reassembly. The demolition plan shall describe any analysis and procedures necessary to assure the existing building structure is not compromised.

The demolition plan shall describe how dust control for personnel and networking equipment will be accomplished.

5.3.4. A comprehensive Architectural Plan that provides a detailed approach of how the requirements will be met. The Architectural Plan must have a pdf concept drawing.

The concept drawing, notes included, must indicate minimum ABA slopes, ABA door openings, ABA handicap stalls including 5'-0 dia turning radii in order to show fundamental understanding of ABA requirements and the other architectural elements listed in the Seed Project SOW, Section 2.2.

5.3.5. A Security Plan that provides a detailed approach of how the requirements specified in the Seed Project SOW Section 2.5 will be met.

5.3.6. An Electrical Plan that describes in detail how the requirements in the Seed Project SOW, Section 2.3, will be met. The plan must include a description of how the Main Distribution Panels will be modified and a One Line Diagram for each of the two Main Distribution Panels showing the equipment and areas listed in the Seed Project SOW. The One Line Diagrams shall include wire and conduit sizing between each Main Distribution Panel and the new sub-panels shown on Seed Project SOW Addendum 2, E101.

5.3.7. A Mechanical Systems Plan that describes in detail how the Mechanical requirements identified in the Seed project SOW will be met, including:

All new Heating, Ventilation, and Air Conditioning (HVAC), breathing air and shop air IAW the requirements in the Seed Project SOW Section 2.4.

5.3.8. A Concrete Structural Design IAW Seed Project SOW, paragraph 2.1.1. The proposal shall include accurate footing or foundation and floor structural calculations and detailed sketches prepared by a Professional Structural Engineer who is to be identified on the Structural Design documentation along with their state of licensure.

The proposal shall include complete calculations and detailed sketches that clearly illustrate reinforcing size, placement, dimensions, and pertinent foundation information. This design is to be based upon data provided by the government in the Seed Project SOW documentation and may be marked with a disclaimer statement indicating the calculations are for proposal purposes only.

5.3.9. A Communications Design Plan that demonstrates how the contractor will comply with, 75 AFW/SC Communication & Information Directorate Hill AFB, Utah Telecommunications Installation Criteria for Facility Design and Renovation (Appendix 7), ETL 02-12 and UFC-3-580-01. The Communications Design Plan shall include CER and TR concept sketches and a description of protection for network equipment throughout construction. The contractor shall identify the individuals acting as the Building Industry Consulting Service International (BICSI) certified technician and the Registered Communications Distribution Designer (RCDD) IAW the Seed Project SOW Section 2.6. Proof of certification shall be submitted.

5.3.10. A Basis of Design for Fire Protection that is prepared by a registered Professional Engineer licensed to practice Fire Protection engineering who is to be identified on the

Basis of Design documents along with their state of licensure. The Basis of Design shall include all major subsystems required to meet Unified Facilities Criteria (UFC) 3-600-1, Engineering Technical Letter (ETL) 02-15, National Fire Protection Association (NFPA) with Air Force Civil Engineering Center (AFCEC) interim guidance taking precedence, ref. Seed Project SOW Section 2.7.

5.4. Sub-Factor Two: Architect-Engineer (A-E) Qualifications

5.4.1. One example of a past project containing short circuit, coordination, arc flash and voltage drop calculations signed and stamped by a licensed Professional Electrical Engineer similar in scope in regards to complexity, cost, and size of the Seed Project.

Example project shall be contractually complete and less than five (5) years old from the issue date of the RFP.

5.4.2. A-E Qualifications shall be submitted on Standard Form (SF) 330, Section L Attachment 3, for each discipline: Architectural, Civil, Structural, Electrical and Mechanical Engineering. Five years of experience as a licensed Professional is required for each discipline.

5.4.3. An example of a past project that was designed by the partnered A-E firm and was successfully certified as LEED AP Silver. Past project example shall be formatted as shown in Example Project Template found on Page 15. The A-E team shall have one or more Leadership in Energy and Environmental Design (LEED) Accredited Professional(s) (AP) IAW Basic SOW paragraph 1.3.1.3. and Section 2.2. Example project shall be contractually complete and less than five (5) years old from the issue date of the RFP.

5.4.4. A successfully designed and constructed example of a past project similar in scope with regards to complexity, cost, and size of the Seed Project. Project example shall be formatted as shown in Example Project Template found on Page 15. Example project shall be contractually complete and less than five (5) years old from the issue date of the RFP.

5.4.5. A Fire Protection Engineering Plan that demonstrates the capability to obtain services as required by AFI 32-10141, Page 19, Attachment 3, as well as the following:

5.4.5.1. Technical qualifications for the design of a Fire Alarm System IAW UFC 3-600- 01 paragraph 5-1.1.

5.4.5.2. Additional qualifications for combined fire alarm and mass notification systems IAW UFC 4-021-01, paragraphs 3-2.1.

5.4.5.3. Technical qualifications for the design of High Expansion Foam Systems in hangars IAW ETL 02-15, section A1.6.

5.4.5.4. Engineering services IAW UFC 4-021-01 paragraph 4-6.1.2.

5.5. Sub-Factor Three: Contractor Requirements:

5.5.1. Past project examples shall be formatted as shown in the Example Project Template found on Page 15.

5.5.1.1. A signed partnership agreement with an established Architect-Engineer (A-E) firm that meets the requirements specified in basic SOW 1.1.1.

5.5.1.2. Design-build experience as a Prime Contractor on military installations or design-build experience for both commercial aviation infrastructure within airport secured areas and industrial production facilities by submitting no more than two design-build example projects totaling at least $2.5M that were successfully completed. Project examples shall be formatted as shown in the Example Project Template found on Page 15. The combined contractual dollar value of the experience must total at least $2.5M. If two projects are submitted, the lesser of the two shall not be less than $500K. Example project(s) shall be contractually complete and less than five (5) years old from the issue date of the

RFP.

5.5.1.3. Design-build experience as a Prime Contractor on projects involving Architectural, Civil, Electrical, Mechanical, Fire Suppression, Structural, Security and Communications construction disciplines. A maximum of three example projects shall demonstrate experience in each of the disciplines above.

Each example project does not have to be inclusive of all disciplines, but the combination of all example projects must demonstrate experience in each of the disciplines above. Submission of multiple projects will not be evaluated more favorably than one. Three example project submissions are allowed in the event one example project does not demonstrate experience in all disciplines referenced above. Example project(s) shall be contractually complete and less than five (5) years old from the issue date of the RFP.

5.5.2. Annual Total Case Incident Rate (TCIR) and Days Away, Restricted and/or

Transferred (DART) rates using the Summary of Work-Related Injuries and Illnesses, OSHA Form 300A.

5.5.3. A prequalification letter from an A.M. Best “A” rated surety (not a bonding agent), that verifies your bonding relationship and shows a minimum bond capacity of $5 Million per project and $20 Million aggregate for MACC III.

6. VOLUME III – PAST PERFORMANCE

6.1. Offerors shall submit recent and relevant contracts (maximum of three contracts) as defined below.

The Government will consider this information, along with information obtained from other sources to include Government databases such as Past Performance Information Retrieval System (PPIRS), Contractor Performance Assessment Reports System (CPARS), and/or through the use of Government and commercial customer interviews and questionnaires.

6.1.1. Recency is defined as performance less than (3) three years old from the issue date of the RFP. The Government will not consider performance on contracts or task orders where performance was concluded more than (3) three years prior to this solicitation’s issue date.

6.1.2. Relevancy is defined as performance of efforts involving construction that are similar or greater in scope and magnitude that involves similar types and complexities of construction described in this RFP. For Government contracts, any relevant Government contract where the Offeror was the Prime Contractor will be considered and reviewed to determine past performance history.

6.2. Offerors will have an opportunity to provide information to address any performance problems and issues that the Government may identify that they have not previously been able to address and explain corrective action taken and current status. The Government will consider this information in determining the Offeror’s past performance rating.

6.2.1. An Offeror’s failure to address performance problems and issues within this volume does not preclude the Government from using such information in determining a past performance rating.

6.3. If a joint venture is contemplated, provide complete information as to the joint venture. Include any relevant and recent past performance information on previous joint ventures with the same partner.

If this is a first time joint venture, each party to the joint venture should provide a list of past relevant contracts (maximum of three).

6.4. Offerors must use the Past Performance Information (PPI) Tool (Use latest version from FBO.gov) in order to electronically submit the Past Performance Volume IAW the RFP. See Appendix I for instructions.

7. VOLUME IV – CONTRACT DOCUMENTATION

7.1. Provide all Volume IV Contract Documentation in the prescribed format identified in Table 1 –

Proposal Organization.

7.1.1. Model Contract

7.1.2. Section A - Solicitation/Contract Form: Complete blocks 14, 15, 16, 19, and 20 and SF1442. Signature by the Offeror on the SF1442 constitutes an offer, which the Government may accept.

7.1.3. Section I - Contract Clauses - Offerors shall complete all required clause fill-ins.

7.1.4. Section K - Representations, Certifications, and other Statements of Offerors -

Complete representations, certifications, acknowledgments and statements. Offeror must have filled out an online FAR provision 52.204-08 Annual Representations and Certifications (Dec 2012), Online Reps and Certs at http://www.sam.gov. Offeror shall ensure certification as a small business under North American Industry Classification System (NAICS) 236220.

7.2. Submit attendance list of up to three individuals (by position title and name) that will attend the post award conference at Hill AFB. Attendance at the post award conference is mandatory and will serve to fulfill the contract’s “minimum guarantee amount.”

7.3. Ability to obtain resources - Submit acceptable evidence that your company possesses adequate financial resources to perform the contract. An example of acceptable evidence is a commitment or explicit arrangement that will be in existence at the time of contract award, to acquire the needed materials, equipment, personnel and other resources necessary to sustain operations. This information will be used as part of the CO’s determination of responsibility IAW FAR 9.104.

7.4. Plans Required by Regulation or Policy - Submit the following plan IAW applicable FAR and

DFARS and SOW Sections. These plans shall be placed in individual binders that are subtitled (e.g., Volume IV, Contract Documentation). Provide copies in the formats and quantities identified in Table 1.

7.4.1. IAW FAR Clause 52.219-14 Limitations of Subcontracting at least 15 percent of the cost of contract performance incurred for personnel shall be expended for employees of the concern. Small businesses that intend to count the performance of other small businesses in meeting the 15 percent requirement of FAR Clause 52.219-14, Limitations of Subcontracting, must include in their Contract Documentation Volume evidence of a joint venture has been approved by the Small Business Administration (SBA). Submit documentation that demonstrates how the prime contractor will meet the requirements of the aforementioned FAR Clause.

7.5. Exceptions to Solicitation Requirements - Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or sub-factors. Failure to meet a requirement may result in an offer being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale.

Each exception shall be specifically related to each paragraph and or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation.

This information shall be provided in the format and content of Table 3 - Solicitation Exceptions.

Table 3 – Solicitation Exceptions

7.6. Other Information Required

7.6.1. Authorized Offeror Personnel - Provide the name, title, telephone number, and email address of the company and division point of contact responsible for negotiating with the Government.

SOLICITATION

Document

Page/ Paragraph

Requirement/ Portion

Rationale

SOW, Model Contract, Section L, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can or will not be met

Example Project Template

1. Example Project: Number example projects consecutively. If the contract was not direct with the end user, then the example project experience is not considered to be Prime Contractor experience.

2. Contractor Name: Provide Name, Address, Point of Contact, Email, and Telephone number.

3. Contract Basic Information: Provide contract number, title, location, award amount and date, and completion date.

4. Project End User: Provide project owner or end user, such as a government agency or installation, an institution, or corporation or private individual. Provide name, title and telephone number (including area code) of a person associated with the end user or the organization that contracted for the project, who is familiar with the project and the firm’s performance.

5. Description of the Project: Provide contract type (design or design-build), physical size, and brief description of the effort. Provide sufficient detail to establish the relevance to the proposed contract. Pictures may be provided but are not required.

SECTION L APPENDIX I

Downloading the PPI Tool

The PPI Tool can be downloaded by performing the following steps (if you are unable to download the Tool, contact the contracting officer for assistance):

1. Access the FedBizOpps (https://www.fbo.gov/) website.

2. Find the solicitation posting.

3. Locate the “ppi tool” link from the “All Files” column on the solicitation’s

“Notice Details” tab .

4. Select the link and save the “ppi tool” to your computer. Name the file as the prime contractor +

RFP number + file extension (e.g. XYZCompanyFA8201-15-R-XXXXX-.mdb).

Note: PPI Tools saved in Microsoft version 2007 and greater will be saved with “.accdb” file extension.

Entering information in the PPI Tool

After selecting and saving the tool, enter information by performing the following steps:

1. Open the saved PPI Tool.

2. Select the “Options” button from the “Security Warning” banner, if applicable

. The “Security Alert” pop-up screen displays.

Figure 1: Security Alert Pop-up

Note:

https://www.fbo.gov/

• Files saved using Microsoft Office 2010 will have the “Enable Content” button on the “Security Warning” banner and therefore will not get a Security Alert pop-up.

• If a "read only" file is opened, in order to populate data in the file, click "Save As" in the "Read- Only" message bar. Enter the filename as the prime contractor + RFP number + file extension (e.g.

XYZCompanyFA8224-15-R-0019.mdb).

3. Select the radio button “Enable this content” and then click “OK.” A setup pop-up screen displays.

Figure 2: Setup Pop-Up

4. Select the “Start” button. The “Application Setup” screen displays.

Figure 3: Application Setup Screen

5. Enter the Offeror’s Name and RFP Number and then click the “Next” button. The application setup continues.

Figure 4: Continue the Application Setup

6. Choose the appropriate option by selecting the corresponding radio button and then click the “Next” button. The “Contractor’s Menu” displays.

Figure 5: Contractor’s Menu

7. Click the “Step 1: Set up Business Relationships” button to create a business relationship, if applicable, for each contributing contracting organization before proceeding throughout the PPI Tool (refer to Section L of the RFP for detailed instructions). Identify all prime and sub-prime organizations and categorize them according to the appropriate role in the proposed acquisition. The “Business Relationships” screen displays.

Figure 6: Business Relationships

8. Click the “New” button to create a business relationship for the proposed acquisition. An additional “Business Relationships” screen displays.

Figure 7: Enter New Business Relationship

9. Complete the fields as follows (fields marked on the screen with an asterisk ‘*’ are required):

• Contractor’s Name: Self-explanatory

• Role in Proposed Acquisition: Choose one of the four options – Prime, Sub, Joint Venture, or

Other (Explain). An explanation comment box will display when you select “Other.”

• Place of Work: Location where contractor will perform work.

• Percentage of Work: Identify percentage of work contributed by specified contracting organization.

• Responsibilities: Detail responsibilities of specified contracting organization.

10. Select one of the buttons at the bottom of the screen.

• Add – Saves the current business relationship and allows for the addition of a new one.

• Close – Cancels the current business relationship without saving.

Note: In order to edit or delete an existing business relationship in the list, double-click on it.

11. Select the “Close” button on the “Business Relationships” screen after all of the business relationships has been added.

12. Click the “Step 2: Enter Past Performance Information (PPI)” button to enter the Past Performance Information. The “Past

Performance” screen displays.

Figure 8: Past Performance

13. Click the “New” button to enter Past Performance Information for the proposed acquisition. An additional “Past Performance” screen displays.

Figure 9: Enter Past Performance Information

14. Complete the fields on each of the tabs as follows (fields on the screen marked with an asterisk ‘*’ are required):

• Contract Information Tab Contractor: Select from the dropdown the appropriate contractor.

Cage Code: Self-explanatory.

Contract Number: If you don’t have a contract number, enter “N/A.”

Program Title: Enter full name of program.

Contracting Agency/Customer: Enter servicing contracting agency and customer (office symbols suffice).

DUNS Number: Self-explanatory

Delivery Task/Order: If the order is provided as a stand-alone reference, enter the task/call/delivery/purchase order number.

Contract Type: Enter Firm-Fixed-Price (FFP), Cost Plus Fixed-Fee (CPFF), Indefinite Delivery/Indefinite Quantity (ID/IQ), LH, Blanket Purchase Agreement (BPA), Cost Plus Incentive-Fee (CPIF), Cost Plus Award Fee (CPAF), etc. For additional clarification, click the question mark button.

Short Program Title (i.e. Acronym): Enter abbreviated title for the program or enter “N/A.”

Contract Dollar Value:

o Original: Input total contract dollar value, with all options if applicable, in the amount originally awarded on the referenced contract.

If ID/IQ or BPA, provide total ceiling.

If stand-alone task/call/delivery/purchase, provide amount of the individual contract.

o Current: Input total contract dollar value, with all options if applicable, as the contract stands at time of PPI submission.

If ID/IQ or BPA, provide total ceiling.

If stand-alone task/call/delivery/purchase, provide amount of the individual contract.

Period of Performance (mm/dd/yy) o Start Date: Input start date of contract.

o Original End Date: Input original end date based on award.

o Current End Date: Input end date, as the contract stands at time of PPI submission.

o Explain the differences in Period of Performance, if applicable: Enter an explanation of the difference between “Original End Date” and “Current End Date.”

• Program Details Tab Brief Description of Effort as:

o Select Prime, Sub, Joint Venture, or Other (Explain). An explanation comment box will display when you select “Other.”

o Provide a brief description of the service provided and actual work performed under this contract reference.

o ****If applicable: Provide information on problems encountered on the identified contracts. At a minimum, briefly describe the problem experienced, actions taken to alleviate the problem, and whether or not the problem was satisfactorily overcome.****

Explain how your experience on this program is relevant for each sub-factor under the Technical Factor in Section M of the RFP, including any unique aspects that demonstrate relevancy in this effort. Provide evidence to support how the contract referenced has relevant experience and demonstrates the ability to perform the solicitation requirements as described in Section M of the RFP. As applicable, address how the proposed reference relates to each of the Technical Sub-factors.

• POC & Key Individuals Tab Customer Points of Contact: Click the “Program/Site Manager,” “Contracting Officer” or

“Admin POC” button for the point of contact that you would like to add, edit, or delete.

Note: For government contracts provide current information on Program Manager, Contracting Officer, and Admin POC, if available.

15. Select from the buttons at the bottom of the Past Performance screen:

• Save – Saves the Past Performance Information and displays the “Contract Information” tab on the Past Performance screen.

• Close – Closes the Past Performance screen. If there were any updates, a pop-up window displays asking to save before closing.

• Delete – Deletes the current PPI record. A pop-up window displays, select “Yes” to delete the record or “No” to close the window without deleting the record.

Note: In order to edit or delete an existing PPI record in the list, double-click on it.

16. Select the “Close” button on the “Past Performance Information” screen after all of the PPI records have been added.

Printing Reports and Submitting PPI Tool In order to print the Business Relationships and PPI reports, perform the following steps:

1. Click the “Step 3: Print Report” button . A pop-up displays asking which report to print.

Figure 10: Select Report to Print

2. Select separately each of the two options, “Business Relationships” or “Past Performance.” The Business Relationships and Past Performance documents will print separately; combine the two to create your Past Performance Volume.

In order to submit the Business Relationships and PPI, perform the following steps:

3. Click the “Step 4: Submit” button . The “Submission Instructions” screen displays.

Figure 11: Submission Instructions

4. Follow the submission instructions. Hard copies of the pages generated from this tool shall be used in the hard copy of the Past Performance Volume subject to the limitations outlined in this RFP and should be Tab 1 of the Past Performance Volume.

Note:

• Submit an electronic copy (e.g. CD) of the saved PPI database file with your proposal. Enter the filename as the prime contractor + RFP number + file extension (e.g. XYZCompanyFA8224-15- R-0019.mdb).

• Once the file is saved to a CD or any location that is marked as “Read-only,” it must first be saved to the desktop in order to read/edit the file.