Attachment 4 Section L Instructions to Offerors 3 Jun 2020.pdf

FA8201-20-R-0007 Hill AFB Information Technology Consolidated Contract (ITCC)

Attachment 4 Section L Instructions to Offerors

Section L – Instructions to Offerors

Addendum to 52.212-1 INSTRUCTIONS TO OFFERORS – COMMERCIAL ITEMS

The following addendum replaces FAR provision 52.212-1 in its entirety.

1 PROPOSAL FORMAT

1.1 General

The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. Offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause the offeror’s proposal to be determined not eligible for award. Offerors shall submit only one proposal for Information

Technology Consolidated Contract (ITCC), as the Government will review only one proposal per offeror. Proposals received are subject to the requirements specified in FAR 52.212-1, unless otherwise tailored in an addendum to the solicitation. Proposals must be received by the

Contracting Officer at AFSC/OL:H/PZIEB, Attention Dawn Schmidt, 6038 Aspen Ave Bldg

1289 NE, Hill Air Force Base, UT 84056, no later than the date and time specified in Section A of the solicitation.

The Government intends to award a competitive 8(a) single award Indefinite Delivery Indefinite

Quantity (IDIQ) contract for the ITCC. The contractor will perform work to include, but not limited to, provide IT support services to Hill AFB personnel, Help Desk Client Support (Printer, e-Tool, Field Technician, TAA), Expeditor, Network, Server, Unit License Management, and

Giant Voice Support.

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The offeror’s proposal shall provide a description addressing how the offeror intends to meet the Government’s requirements and evidence of the effectiveness and ability to execute the proposed methodology.

Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and not desired.

The proposal acceptance period is specified in Section A of the solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid for a minimum of 365 days from solicitation closing.

In accordance with (IAW) FAR Subpart 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.

1.2 Communications

The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition. The offeror shall address any questions, concerns or requests for clarification to Contracting Officer

Dawn Schmidt at email dawn.schmidt.1@us.af.mil and Contract Specialist Brad Conroy at email bradley.conroy@us.af.mil. See paragraph 1.3.11 for suspense dates for submission of inquiries and questions.

mailto:dawn.schmidt.1@us.af.mil mailto:bradley.conroy@us.af.mil

1.2.1 Exchange of Information

Exchanges of source selection information between Government and offerors will be controlled by the PCO. Email may be used to transmit such information only if the email can be sent encrypted, and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. Otherwise, source selection information will be transmitted via direct mail.

1.2.1.1 The number and size of attachments (i.e., Attachment 2 Remedy Data) poses an issue to process via beta.SAM.gov (replaced FBO.gov) or email. Therefore, DoD Secure Access

File Exchange (SAFE) service can be used to exchange unclassified files up to 8GB.

1.2.1.2 The following link provide access to DoD SAFE https://safe.apps.mil

1.2.1.3 Requests for Attachment 2 Remedy Data, must be sent to Josh Douglass via email at joshua.douglass@us.af.mil and courtesy copy (CC) bradley.conroy@us.af.mil and dawn.schmidt.1@us.af.mil with the following information: Name of Prime 8(a)

Company, Cage Code, and the Name and email address of recipient to pick up the files in

SAFE. Ensure ‘FA8201-20-R-0007 Request for Attachment 2 Remedy Data – Prime

8(a) Company Name, Cage Code’ is in the subject line of the email.

1.2.1.4 The use of Remedy Data to prepare proposals is at the discreation of potential offoers.

1.2.1.5 If you have previously requested and received the Attachment 2 Remedy Data, it is not necessary to request it again as the data has not changed.

1.2.1.6 Regardless of when the Remedy Data is downloaded/dropped off in SAFE, the exact data is dropped off to each recipient. The Remedy Data can be requested at any time during the proposal preparation period, prior to the due date and time specified in the solicitation

(SF1449 Item 8 Offer Due Date and Time). Regardless of when the Remedy Data is requested or received, the due date and time specified in the solicitation will not be changed based on when the Remedy Data is received by the potential offeror. For example, if Remedy Data is received on the due date or close to the due date, the due date and time will not be changed to allow additional time to prepare and submit proposals.

1.2.1.7 Upon receipt of the email request, the Remedy Data files will be dropped off (uploaded) into SAFE as quickly as possible, during the proposal preparation period. The recipient will receive an automated email containing instructions for downloading the files.

1.2.1.8 Files are automatically deleted from DoD SAFE 7 days after drop-off (upload).

1.2.2 Submission, Modification, Revision, and Withdrawal of Proposals

Proposals and modifications to proposals shall be submitted in both paper and electronic media to the address located in paragraph 1.1 of this document, showing 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.

Proposals may be withdrawn by written notice received via email 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.

1.2.3 Debriefings

The PCO will notify offerors of any decision to exclude them from the competitive range;

whereupon, they may request and receive a debriefing IAW FAR 15.505, Pre-Award Debriefing https://safe.apps.mil/ mailto:joshua.douglass@us.af.mil mailto:dawn.schmidt.1@us.af.mil of Offerors. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing.

The PCO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.503, Notifications to Unsuccessful Offerors. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make the request IAW the requirements of FAR 15.505 or 15.506, as applicable.

1.2.4 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 PCO in writing with supporting rationale, as well as the remedies the offeror is asking the PCO to consider as related to the omission or error. When appropriate, Government responses will be provided to all offerors.

1.2.5 Amendments to Solicitation

If this Request for Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged. If the RFP is amended prior to proposal delivery, offerors shall acknowledge each amendment by signing and returning the Attachment 6 List of Attachments with the proposal submission. If the RFP is amended after proposal submission, offerors shall respond by the date and time specified in the amendment to include signing and returning the Attachment 6

List of Attachments with the amended RFP.

1.3 Volume Organization

1.3.1 General

The offeror shall prepare the proposal as set forth in the Proposal Organization Table 1 below.

The titles and contents of the volumes shall be as defined in Table 1, all of which shall be within the required page limits and with the number of copies as specified. The volumes identified in the Table 1 shall be separately bound in three-ring, loose-leaf binders.

The title page of each volume must show:

1.3.1.1 Solicitation Number

1.3.1.2 Company name, address, Commercial and Government Entity (CAGE) Code and Data

Universal Numbering System (DUNS) Number.

1.3.1.3 Primary point of contact name, telephone number and email address

1.3.1.4 Volume number and name (e.g. Volume II, Cost/Price) and copy number (i.e. Original)

Table 1: Proposal Organization

Volume Volume Title

Total

Page

Limits

Number of

Paper

Copies

Number of

Electronic

Copies

(CDs)

Description

I Technical 30

(Original)

2 (1

Original; 1

Copy)

Technical Volume includes:

1) Table of Contents

2) List of Table and

Drawings

3) Glossary

4) Cross Reference

Matrix

5) Subfactor One – Help

Desk Surge Scenario

6) Subfactor Two –

Help Desk Surge and Cross-

Utilization

7) Subfactor Three –

CST Support

8) Subfactor Four –

Corporate Experience

9) Subfactor Five –

Server Support

II Cost/Price N/A

(Original)

2 (1

Original; 1

Copy)

Cost/Price Volume

III

Contract

Documentation N/A

(Original)

2 (1

Original; 1

Copy)

Contract Documentation

Volume

1.3.2 Page Limitations

Individual page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) will be shredded.

If Evaluation Notices (ENs) are issued, page limitations may be placed on responses. The specified page limits for EN responses will be identified in the letters forwarded with the ENs to the offerors. Each page shall be counted except the following: blank pages, title pages, tables of contents, lists of tables and drawings, cross-reference matrices, tabs, and glossaries.

1.3.3 Page Size and Format

A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Except for the reproduced sections of the solicitation document, the text size shall be Times New Roman font and no less than 12 point. 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 and bottom and 1-inch side margins.

Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

1.3.4 Tables, Charts, Graphs and Figures

Organizations, systems and layout, implementation schedules, plans, etc. shall be depicted in tables, charts, graphs, or figures wherever practical. These items shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, 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 Times New Roman 10 point and searchable for text in Microsoft (MS)

Office Word and/or PDF formats to the maximum practical extent. Ensure all tables, foldouts, graphics, and figures in the electronic version of the proposal are pasted into the proposal in a format that allows a word search by the host program (do not paste as pictures) to the maximum practical extent. These limitations shall apply to both electronic and hard copy proposals.

1.3.5 Cost or Pricing Information

All cost or pricing data shall be addressed only in the Cost/Price Proposal and Contract

Documentation Volumes.

1.3.6 Cross-Referencing

Each volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal. Information required for proposal evaluation which 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 where its use would conserve space without impairing clarity, but must be hyperlinked IAW Section 2.1.3.

1.3.7 Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. Tables of contents do not count against the page limits for the offeror’s respective volumes.

Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitations for the offeror’s respective volumes.

1.3.8 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose-leaf binder permitting the volume to lie flat when open. Staples shall not be used. The outside of each binder shall include a cover sheet, clearly marked, identifying volume number, title, copy number, solicitation identification, and the offeror's name. The same identifying data should be placed on the spine of each binder. 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. Any page containing proprietary information should be so marked.

1.3.9 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 the electronic copy, the hard copy shall take precedence and will be used for evaluation. The offeror shall submit Volumes I through III in electronic format, using virus-free CD-R. In no cases shall the offeror use CD-RW. Re-writable CDs (i.e., CD-RW) WILL NOT BE READ, EVALUATED, OR CONSIDERED. Each volume will be on a separate CD. If files are compressed, the necessary decompression program must be included. The electronic copies must be submitted in a format readable by Microsoft

(MS) Word 2010, MS Excel 2010, and MS-Power Point 2010, as applicable. PDF formats shall not be used. Word documents – Set “save as type” to “Word Document (*.docx)” only. Excel spreadsheets – Set “save as type” to “Excel (*.xlsx)” only. For electronic copies, indicate on each CD the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The file naming shall specify the appropriate volume. Each volume shall be on a separate CD. If files are compressed, the necessary decompression program must be included.

The Table of Contents of all proposal volumes shall be hyperlinked to the corresponding material within each proposal volume such that clicking the mouse on an item in the Table of Contents will take the reader to the corresponding section within the body of the proposal volume. Any heading or sub-heading appearing in the Table of Contents shall be hyperlinked as described above. The Table of Contents shall include the file names, as well as page numbers where content is cross-referenced between subfactors. Also, any reference within the body of the proposal volume that refers the reader to another location within the referring document shall be hyperlinked in the manner described above. Hyperlinking references between different filenames is not necessary.

Proposals shall not be emailed.

1.3.10 Distribution

The original proposal shall be identified “Original.” The proposal shall be addressed to the PCO and mailed or hand-carried to the address cited in paragraph 1.1.

Delivery of proposals shall be coordinated via email at least 24 hours in advance of the due date/time with the PCO. The purpose of the email is to notify the PCO of the estimated delivery date and time and delivery method (mail or hand carried) of the proposal. Proposals received after the due date and time specified in the solicitation (SF1449 Item 8 Offer Due Date and

Time) shall be treated IAW FAR 15.208, Submission, Modification, Revision, and Withdrawal of Proposals.

Offerors are cautioned that Hill AFB has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass prior to entrance. Some delay should be anticipated when hand-delivering proposal packages. Offerors should allow for sufficient time to obtain a visitor pass and arrive at the specified office prior to the time specified for receipt of proposals.

1.3.11 Proposal Inquiries

All inquiries and questions shall be submitted no later than 26 May 2020, 12:00 pm MDT (Hill

AFB local time) via e-mail to the PCO and Contract Specialist. Ensure ‘FA8201-20-R-0007

Proposal Inquiry – Prime 8(a) Company Name, Cage Code’ is in the subject line of the email.

Inquiries and questions, if appropriate as determined by the Government, will be answered as quickly as possible. Inquiries and questions received after 26 May 2020, 12:00 pm, if appropriate as determined by the Government, may or may not be answered by the Government.

When appropriate, answers to questions and concerns will be made available to all offerors.

2 VOLUME I, FACTOR 1: TECHNICAL PROPOSAL

2.1 General

The Technical Volume should be specific and include all requirements of Volume I. Offerors’ responses will be evaluated against the Technical subfactors defined in Section M, Evaluation

Factors for Award. Using the instructions provided below, the offeror shall provide as specifically as possible the actual approach, methodologies, capabilities it would use for satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By its proposal submission, the offeror is representing that its firm will perform all the requirements specified in the solicitation.

The written technical proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation. The proposal should not simply reiterate, rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume the Government has no prior knowledge of their capabilities, work processes, facilities, and experience and will base its evaluation on the information presented in the offeror’s technical proposal.

The Technical Volume shall be organized according to the following general outline:

Section Title

1 Table of Contents

2 List of Tables and Drawings

3 Glossary

4 Cross Reference Matrix

5 Subfactor One: Help Desk Surge Scenario

6 Subfactor Two: Help Desk Surge and Cross-Utilization

7 Subfactor Three: CST Support

8 Subfactor Four: Corporate Experience

9 Subfactor Five: Server Support

Note: Offerors shall not address Addendum III Safety, Health, and Fire Protection Requirements of the PWS in the offeror’s proposal. However, the successful offeror shall submit a Safety Plan

IAW PWS Addendum III at the Post Award Conference and obtain 75th Air Base Wing Safety

Office approval.

2.1.1 Amendments

For any amendments to Volume I, the offeror’s proposal will include a cover letter delineating any changes from initial proposal, to include changes/revisions (if needed) for Final Proposal

Revisions (FPR).

2.1.2 Format and Specific Content

The information in paragraphs 2.2 - 2.3 shall be provided in the written technical proposal and will be used to assess the proposed technical approach in accordance with Section M, Evaluation

Factors for Award. The written technical proposal shall address each of the following paragraphs

(2.1.3 through 2.3.5) to describe the offeror’s proposed approach, methodologies, and capabilities in performing the requirements set forth in the subfactors.

2.1.3 Cross Reference Matrix

The offeror shall fill out the Cross Reference Matrix (Section L: Appendix A), and submit with the proposal indicating where in its proposal the information can be found as it relates to the

PWS, Section L, and Section M. The cross reference matrix will help an offeror ensure it has responded to all the evaluation criteria and proposal submittal requirements identified in the solicitation. If the matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over the matrix. Section M references in the matrix are for informational purposes only, and the Government will evaluate proposals solely in conformance with Section M of the solicitation. This matrix will be used for reference only and will not become contractually binding.

2.2 Technical Approach

In the Technical Volume, address the scenarios, corporate experience, and capabilities and also provide evidence of meeting or exceeding the minimum requirements of each subfactor.

2.3 Technical Subfactors

Subfactor One: Help DeskSurge Scenario

Subfactor Two: Help Desk Surge and Cross-Utilization

Subfactor Three: CST Support

Subfactor Four: Corporate Experience

Subfactor Five: Server Support

2.3.1 Subfactor One: Help Desk Surge Scenario

The Offeror shall describe the capability to manage surges in Help Desk workload by completing a sample task scenario. This scenario is for evaluation purposes only and is not contractually binding. Workload surges occur when a significant number of users across the enterprise are affected by an issue and Help Desk call volume unexpectedly and significantly increases by

100% above the average call volume during the time the surge occurs. Ref: PWS 1.1, 1.3, 1.3.4, 3.8

Help Desk SURGE SCENARIO: It’s 8AM and the Help Desk is staffed to support normal workload for this time of day when call volume unexpectedly increases by 100% from 42 calls to

84 calls. Customers are reporting issues with website connectivity, loss of email service, and no access to the network share drive.

Describe in detail the steps the Offeror proposes to follow to ensure the Help Desk effectively responds to the unplanned workload surge to meet the metrics in PWS 1.3.4.2. The proposal must describe in detail the approach to receive, document, assign, troubleshoot, resolve, and report all end user workstation and information network issues and demonstrate how these issues are tracked and documented in an Automated Information System (AIS).

2.3.2 Subfactor Two: Help Desk Surge and Cross-Utilization

The Offeror shall describe their approach to: (1.) identify Help Desk surges, (2.) maintain Help

Desk surge capabilities, and (3) cross utilize personnel to meet these surges, while maintaining the performance metrics in PWS section 1.3.4. The offeror shall describe the intended plan to manage personnel during surge events. ref: 1.3, 1.3.4, 3.8.

2.3.3 Subfactor Three: CST Support

The Offeror shall describe an approach and process that demonstrates the ability to meet the CST support metrics in PWS 1.3.1, 1.3.2, 1.3.3 for end devices, both NIPR and SIPR. The Offeror describes in detail the ability to provide:

2.3.3.1 Equipment moves

2.3.3.2 Repair of end device hardware or software malfunctions

2.3.3.3 Installation of new hardware or software

2.3.3.4 Resolution of network connectivity issues

2.3.4 Subfactor Four: Corporate Experience

The Offeror shall provide corporate experience information regarding up to three (3) current or past examples of similar contracts to this requirement. The examples can include any contracts awarded to the 8(a) Prime within the last 5 years, awarded between 1 March 2015 and 29

February 2020. Offeror shall address each element below; however, offeror is not required to address all areas for each example.

2.3.4.1 Client Support, PWS 1.3

2.3.4.1.1 Help Desk Support, PWS 1.3.4

2.3.4.1.2 Printer Support, PWS 1.3.5

2.3.4.1.3 End Devices, PWS 1.3.1

2.3.4.1.4 eTool devices, PWS 1.3.2

2.3.4.1.5 TAA devices, PWS 1.3.3

2.3.4.2 Expeditor Support, PWS 1.3.6

2.3.4.3 Server Administration, PWS 1.4

2.3.4.4 Network Support, PWS 1.5

2.3.4.5 Unit Software Support, PWS para 1.6

2.3.5 Subfactor Five: Server Support

The Offeror shall describe in detail their approach, processes and software tools to vulnerability management of multiple physical and virtual servers running Windows Server OS and Red Hat

Linux OS, while supporting and documenting all security requirements on them (PWS 1.4).

3 VOLUME II, FACTOR 2: COST/PRICE

3.1 General

The Price Volume should be specific and include all information required of Volume II.

Compliance with these requirements is mandatory and failure to comply may result in rejection of the offeror’s proposal. Note that unrealistically low or unreasonably high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Additionally, unbalanced pricing poses an unacceptable risk to the

Government and may be a reason to reject the offeror’s proposal. Offers should be sufficiently detailed to demonstrate reasonableness. The burden of proof for credibility of proposed costs/prices rests with the offeror.

3.1.1 Offerors’ responses will be evaluated in the following areas as defined in Section M of the

RFP:

3.1.1.1 Completeness

3.1.1.2 Reasonableness

3.1.1.3 Balance

3.1.1.4 Total Evaluated Price (TEP)

The Cost/Price Volume shall be organized according to the following general outline:

1 Table of Contents

2 Listing of Abbreviations and Acronyms (used within cost/price volume)

3 List of Tables and Drawings

4 General

4-1 TEP Pricing Matrix Worksheet

3.2 Total Evaluated Price (TEP) Matrix, Section J Attachment 3

Offerors shall input into the TEP Pricing Matrix, located in the Section J Attachment 3, Not-to-

Exceed (NTE) fully burdened rates (regular rate) for all labor categories and task order price years. Fully burdened rates shall include direct labor rates, all direct costs, indirect costs

(Overhead, General and Administrative, Fringe Benefits, etc.) and profit necessary for the performance of the entire requirement. All fully burdened labor rates provided shall be rounded to the nearest penny.

The formula for application of hours and the notional hours used will not be disclosed to offerors. The TEP is for evaluation purposes only; however, all proposed fully burdened NTE rates are contractually binding.

Submit a copy of the completed TEP Pricing Matrix in Cost/Price Volume II in MS Excel (non

PDF format).

3.3 Cost/Price Data

Data beyond that required by this instruction shall not be submitted, unless the offeror considers it essential to document or support its cost/price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Price Volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

3.4 Cost or Pricing Data Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided

IAW FAR 15.403-5, Instructions for Submission of Certified Cost or Pricing Data and Data other than Certified Cost or Pricing Data. If, after receipt of proposals, the PCO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1, Prohibition on Obtaining Certified Cost or Pricing Data (10 U.S.C. 2306a and

41 U.S.C. 254b) apply, the offeror shall be required to submit additional cost or pricing data.

3.4.1 Contract Data Requirements Lists (CDRLs)

CDRLs will not be separately priced. Cost required to produce each CDRL should be included in the offeror’s proposed program manager labor rates.

3.5 Estimating Techniques and Methods

Offerors shall use generally accepted estimating techniques to develop their estimates for the proposed rates.

4 VOLUME III, CONTRACT DOCUMENTATION

4.1 Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror's proposal shall include a signed copy of the

Model Contract, and Sections A through K. This includes delivery of all applicable documents.

4.1.1 Section A - Solicitation/Contract Form

Complete Blocks 30b and 30c, then sign and date Block 30a of the Standard Form (SF) 1449, Solicitation/Contract. Signature by the offeror on the SF1449 constitutes an offer, which the

Government may accept. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.

4.1.2 Section B - Supplies or Services and Costs/Prices

The offeror shall not propose prices for each CLIN in Section B of the model contract. All required rates shall be provided in the TEP Matrix of Section J, Attachment 3.

4.1.3 Section I - Contract Clauses

The offeror shall comply with the clauses specified within Section I of the model contract.

Furthermore, any inference of a clause and or provision will be adhered to. All laws, regulations, and statutory authorities will also be applied within the model contract.

4.1.4 Section J – List of Documents, Exhibits, and Other Attachments

The offeror shall complete and provide the following attachments:

Attachment 3 – TEP Matrix. In accordance with paragraph 3.2 submit a copy of the completed

TEP Pricing Matrix in Cost/Price Volume II in MS Excel (non PDF format) as part of Volume II

Cost Price Volume.

4.1.5 Section K - Representations, Certifications, and other Statements of Offerors

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

(NAICS) Code 541513.

4.2 Other Information Required

4.2.1 Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to the proposal and who can obligate the company contractually. Also, identify those individuals authorized to negotiate with the Government.

Additionally, provide the name and telephone number of the CEO, Division President, and/or

Vice President.

4.2.2 13 CFR 126.1 Prime Contractor’s Limitations on Subcontracting

IAW 13 CFR 125.1 and 125.6 Prime Contractor’s Limitations on Subcontracting, in the case of a contract for services (except construction), it will not pay more than 50% of the amount paid by the government to its firms that are not similarly situated. Any work that a similarly situated subcontractor further subcontracts will count towards the 50% subcontract amount that cannot be exceeded. Submit documentation that demonstrates how the prime contractor will meet the requirements of the aforementioned 13 CFR 125.1 and 125.6.

4.2.3 Compensation Plan

The Offeror shall submit a total professional employee compensation plan meeting the requirements of FAR 52.222-46. The Offeror shall detail the base labor rate, fringe, all other burdens, and profit/fee contained in labor rates to facilitate comparisons IAW FAR 52.222-46.

5 SOLICITATION REQUIREMENTS, TERMS AND CONDITIONS

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 subfactors. Failure to meet a requirement may result in an offer being ineligible for award.

5.1 Exceptions to Solicitation Requirements

Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete supporting rationale. Each exception shall be specifically related to each paragraph and 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 performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content provided in Table 2, Solicitation Exceptions, below.

Table 2: Solicitation Exceptions

SOLICITATION

Document

Page/

Paragraph

Requirement/

Portion

Rationale

PWS, 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/will not be met

APPENDIX A: CROSS REFERENCE MATRIX

Cross Reference Matrix

Offeror’s Proposal

Paragraph Number(s) Section L Section M PWS Paragraph Vol

2.3.1 2.4.1 1.3.4, 1.3.4.2 I

2.3.2 2.4.2 1.3.4, 1.3.4.2 I

2.3.3 2.4.3 1.3.1, 1.3.2,

1.3.3 I

2.3.4 2.4.4 1.3, 1.4, 1.5, 1.6 I

2.3.5 2.4.5 1.4 I