Section_L_DRAFT_ICPS_16MAR18.pdf

ATTACHMENT 4 - INSTRUCTIONS TO OFFERORS (ITO)

DRAFT COPY-Section L will be reviewed and updated prior to issuance of the Formal

RFP.

Section L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO RESPONDENTS FOR

PROPOSAL PREPARATION USING TRADEOFF SOURCE SELECTION

PROCEDURES

1.0 Program Structure and Objective

1.1.1 The Government plans to award a single contract for the Integrated Cyber Protection System (ICPS) effort. This acquisition will procure skill sets practical for a variety of platform innovations in support of the overall AF mission. These skill sets demonstrate proficiency in enhancing and developing computer network data monitoring, threat detection, reporting, management, correlation, visualization, and tracking capabilities supporting AF Space Command (AFSPC), 24 Air Force (AF), 67 Cyberspace Wing (CW) and 688 CW at locations world-wide.

1.1.2 Award will be made on the basis of “best value” utilizing Tradeoff Source Selection Procedures. Award will be made to the contractor that provides the “best value” to the Government.

1.2 Budget/Funding Information

Funding will be obligated for the Firm-Fixed-Price (FFP)-Labor Contract Line Item Number (CLIN) and Cost-Plus-Fixed-Fee Labor CLIN for the transition period.

2.0 General Instructions

a. This section of the Request for Proposal (RFP) 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 by the RFP and must be submitted IAW these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract Data Requirements (CDRL), and RFP. Non-conformance with the instructions provided in this RFP may result in an unfavorable proposal evaluation. Alternate proposals will not be accepted.

b. The proposal shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply 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 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.

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

d. The proposal acceptance period must be for a period of no less than 365 days after the closeout of the solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid for this amount of time.

e. In accordance with 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.

2.2 General Information

2.2.1 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 located in Section A of the model contract/solicitation.

2.2.2 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 in accordance with FAR 15.505.

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 for each proposal. The CO will notify unsuccessful offerors in accordance with FAR

15.503. Upon such notification, unsuccessful offerors may request and receive a debriefing.

Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.2.3 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, as well as, the remedies the offeror is asking the CO to consider as related to the omission or error. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussions. This reservation includes matters of additional or substitute pages of the initial proposal.

2.2.4 Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at http://www.fbo.gov. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

http://www.fbo.gov/

2.2.5 Communications

The CO will control exchanges of source selection information between Government and offerors. The Government may use email to transmit such information to offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR

2.101 & FAR 3.104” in the Subject line. Otherwise, the Government will transmit source selection information via U.S. Postal Service or commercial carrier.

2.2.6 Amendments to Solicitation

If this 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 and provide confirmation upon submission of the offeror’s proposal. Any unacknowledged amendments in the offeror’s proposal are subject to solicitation provision in Sections L and M.

2.2.7 Submission, Modification, Revision, and Withdrawal of Proposals Proposals and modifications to proposals shall be submitted in sealed envelopes or packages in paper media and electronic media addressed to the CO at the address shown in Section A of the model contract/solicitation, and showing the time and date specified for receipt, the solicitation number, and the name and address of the offeror.

2.2.8 Questions

All questions related to this solicitation must be submitted to amy.barnes.2@us.af.mil no later than 3:00 PM (CST) XX XXX 2018. Late requests will not be considered.

2.2.9 To be considered for award, offerors must comply with all security requirements specified in the DD Form 254, Contract Security Classification Specification included in this solicitation, complete Blocks 6.a., b. and c. thereof, and return the completed DD Form 254, Contract Security Classification Specification, along with evidence that:

1) Offeror has an Active TOP SECRET Facility Clearance, or have submitted a TOP SECRET Facility Clearance request to the DSS Facility Clearance Branch and show evidence of the Government Delay of the Transfer to the National Industrial Security System (NISS).

2) Show evidence that each position identified in Offeror’s proposal, to fulfill the requirements of this effort has a final TOP SECRET or SECRET personal security clearance; some positions must be eligible for access to Sensitive Compartmented Information in accordance with Intelligence Community Directive (ICD)704 and Intelligence Community Policy Guidance (ICPG) 704.2., along with their offers. The DD254 shall be included in Volume IV, Contract Documentation. A Qualified Offeror must have an Active TOP SECRET Facility Clearance at the time of award or have submitted a TOP SECRET Facility Clearance request to the Defense Security Service (DSS) Facility Clearance Branch (FCB) and if affected by the Government Delay of the Transfer to the National Industrial Security System (NISS) are authorized to submit appropriate Facility Clearance (FCL) as soon as the request has been approved by DSS.

2.3. Organization/Number of Copies/Page Limits

2.3.1 The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1 below). The titles and content of the volumes shall be defined in this table, all of which shall be within the required page limits and with the number of copies, as specified in Table 1.

Page limitations shall be treated as maximums. If exceeded, the excess pages will be retained in the official record, but not evaluated. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Each page shall be counted except the following: cover pages, table of contents, matrices, and glossary. Proposal change pages are customarily subject to same page limitations stated in the table below; however, deviated page limitations may be required on responses to ENs.

TABLE 1 – PROPOSAL ORGANIZATION (within binders)

VOLUME VOLUME TITLE COPIES PAGE LIMIT

I Present/Past Performance Information 4 30 II Technical 4 50

III Price Proposal 2 No Limit (See Para F) IV Contract Documentation 2 No Limit (See Para G)

TABLE 2 – BINDER ORGANIZATION (within binders)

VOLUMES TO INCLUDE:

ORIGINAL I, II, III, IV

COPY 1 I, II, III

COPY 2 I, II

COPY 3 I, II

COPY 4 I, II

BINDER SIZE LIMITATIONS: Binders shall not exceed 2”. Reproduction of the entire RFP is unnecessary (and unwanted).

2.3.3 Page Limitations

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 disposed of. Page limitations may also be placed on responses to ENs. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Each page shall be counted except the following: blank pages, title pages, tables of contents, tabs, indexes, glossaries, and those noted in the Proposed Organization Chart as unlimited.

2.3.4 Cost or Pricing Information

The price proposal shall not include information beyond that required by this instruction unless the offeror considers it essential to document or support offeror’s price position. All information relating to the proposed price, including all required supporting documentation must be included in this part or assumptions of the proposal. Under no circumstances shall this information and documentation be included in the Technical or Past Performance volumes.

2.3.5 Cross Referencing

(a) The offeror shall fill out the Cross-Reference Matrix (Section L, Attachment 1) indicating the proposal reference information as it relates to the PWS, CLIN numbers, and CDRL references found therein and the corresponding proposal paragraph. The Cross Reference Matrix shall be included in the Volume 1, Technical Proposal, following the Table of Contents.

(b) To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Cross referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

2.3.6 Indexing

Tab indexing shall be used to identify volumes.

2.3.7 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. A cover sheet should be bound in each binder, clearly marked with the offeror’s name, volume number and title, solicitation identification and the copy number (for example: Company A, Vol I, FA8773-18-R- 8008, ICPS, copy 1 of 4). 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 in accordance with 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.

2.3.8 Electronic Offers

The content and page size of electronic proposal must be identical to the hard copies. The offeror shall submit proposal volumes I, II, III, & IV via email in a format readable by Microsoft (MS) Office Word 2010, MS Office Excel 2010, and MS Office Power Point 2010, as applicable. Each volume shall be submitted as a separate attachment to an email addressed to amy.barnes.2@us.af.mil. If there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation. No zip files will be accepted.

2.3.9 Change Pages

During or after discussions, any change pages submitted by the offeror shall be a different color, as specified by the CO, from the original proposal pages, and shall clearly mark the changed information with a vertical line in the right margin of the page. The revision number and date shall be reflected on each changed page (preferably on, or next to, the vertical change line).

Make spreadsheet revisions obvious by highlighting cells that changed. Page limitations may also apply on responses to ENs. The Government will identify specified page limits for EN responses in the EN transmittal letters to the offeror.

2.4 Proposal Delivery

2.4.1 Delivery

Offerors must make an appointment with Ms. Amy Barnes via email at amy.barnes.2@us.af.mil for any deliveries of proposal documentation. The appointment must be scheduled at least one workday in advance of the planned delivery date. Deliver hard copies of all proposal volumes I - IV to the Contracting Officer at:

DEPARTMENT OF THE AIR FORCE

ATTN: Amy L. Barnes

Tinker AFB: Bldg 4004, 38 CONS/LGCC 4004 Hilltop Rd

Tinker AFB OK 73145-3020

The offeror shall submit one electronic copy of a CD-R and/or DVD-R with each hard copy volume. These volumes must be received no later than 3:00 PM central time on XX XXX 2018. Late deliveries will be handled IAW paragraph (c) (3) of FAR 52.215-1, Instruction to Offerors-Competitive Acquisition.

2.4.2 Early Submission

Offerors are encouraged to submit Volumes II (Past Performance) and Volume IV (Contract Documentation), as early as XX XXX 2018 but not later than XX XXX 2018, for Volume II (Past Performance) only. Please contact the Contracting Officer to arrange for early delivery.

Failure to submit early proposal information will not result in offeror disqualification.

3.0 Technical

3.1 General Instructions

The Technical Volume should be specific and complete. Legibility, clarity and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is neither necessary nor desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

3.2 Format and Specific Content

3.2.1 Technical

In the Technical Volume, address your proposed approach to meeting the minimum performance or capability requirements of each technical subfactor.

3.2.2 Volume Organization

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

(1) Table of Contents/Glossary

(2) Cross Reference Matrix

(3) Subfactor One – System Architecture Design and Development

(4) Subfactor Two – System Administration and Sensor Maintenance

(5) Subfactor Three – Operations Support

3.2.3 Format and Specific Content. Offeror shall address its proposed approach to meeting the performance or capability requirements of each Technical Proposal subfactor as follows:

SUBFACTOR 1 – SYSTEM ARCHITECTURE DESIGN AND DEVELOPMENT

The offeror shall present an approach that explains how it will conduct network security monitoring, intrusion detection analysis, IOP support, and hardware/software interfaces that meet PWS 3.1.1-3.1.3, 3.2.1-3.2.2, 3.3.3-3.3.5, 3.4.2, and 6.1.1 requirements.

Scenario: Air Force gateways are at or are approaching the throughput capacity of their current DISA circuit interfaces. The current cyber defense system, IOP, hardware is either End-of-Support and/or End-of-Life and will not support the higher data throughput rates that are being deployed at Air Force gateways. Also, increasing the bandwidth of the existing circuits is not feasible as the current infrastructure cannot support connectivity beyond current speeds. Therefore, an upgrade is necessary to equip each of the gateways with interfaces and infrastructure capable of transporting data at rates 10 to 40 times the current threshold rates.

SUBFACTOR 2 – SYSTEM ADMINISTRATION AND SENSOR

MAINTENANCE.

The offeror shall present an approach that explains how it will conduct network security monitoring and intrusion detection analysis that meet PWS 3.1.3, 3.3.1-3.3.2, 3.4.1, 3.4.8, and 3.5 requirements.

Scenario: The ATO (under DIACAP) for the software development network expires in six months. The development network is relatively dynamic; new systems are added, modified (OS reinstallations, new applications) and removed as needed.

Several servers have obsolete software loads (e.g. Windows server 2003) that are no longer approved for use. The network must have an ATO (under RMF) before the current ATO expires, plus up-to-date tracking of the equipment (Asset Management, AFI 23-111) on the network.

SUBFACTOR 3 – OPERATIONS SUPPORT.

The offeror shall present an approach of how to support cyber defense platform capabilities for the 90th COS customers performed IAW PWS Sections 3.4.

Scenario: A new threat detection/mitigation capability is required urgently to meet mission requirements. Approaches to generating the new capability are evaluated, a data visualization/detection application is rapidly prototyped, and the IPS system is modified to enable blocking of the malicious traffic. Because of the potential for blocking legitimate traffic, effectively using the new capability requires analyst and field maintenance training. It is decided to field the capability immediately, requiring installation, troubleshooting and training to be performed at the site of deployed systems capable of handling the software changes. Older systems that require hardware/software upgrades to support the capability are to be rapidly shipped in, updated, configured and shipped back out.

The contractor shall maintain/enhance active mode and in-line feature sets which allows for network management and control via static firewall and dynamic IDS/IPS activity rule establishment; configurable timeouts of IDS/IPS actions; and controls for operator initiated and autonomous rule/policy enforcement.

4.0 Factor 2 – Past Performance

4.1 General

4.1.1 Each offeror shall submit Past Performance Information (PPI) with its proposal IAW the format contained in paragraph 3.5 below. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 30 percent or more of the proposed effort based on the total proposed price or perform aspects of the effort the offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance. Each offeror shall submit PPI. Past performance of either party in a joint venture counts for the past performance of the entity.

4.1.2 New Corporate Entities. New corporate entities may submit data on prior contracts involving officers, employees, and key personnel who have relevant experience and/or data of efforts that will depict performance of major or critical aspects of the requirement. Discuss the roles and responsibilities of personnel involved in the prior contracts cited.

4.2 Relevant Contracts. Offeror shall submit PPI on a minimum of three, but no more than five recent contracts that offeror considers most relevant in demonstrating ability to perform the proposed effort. The contracts must have been completed in the past five years with on-going actions considered recent as long as the effort has been performed for at least six months prior to the date for receipt of proposals for the RFP. The total includes any subcontractors or teaming partners; however, at least one PPI must be from the prime and no more than three of the recent contracts shall be submitted on your teaming partners and/or significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. Do not duplicate a contract reference for prime and subcontractor but rather explain the role each played within the contract reference itself. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M Attachment 1, Relevancy Assessment Matrix.

4.2.1 Specific Content

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified, which may allow the offeror to be considered a higher confidence candidate. For example, if submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required;

the relevant information should be categorized into the specific Technical sub factors and Cost/Price factor used to evaluate the proposal.

4.2.2 Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent present/past efforts and this source selection. As a result, it is sometimes difficult to determine what present/past performance is relevant to this acquisition.

To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of offeror’s company. As part of this explanation, show how these changes impact the relevancy of any efforts the offeror identifies for present/past performance evaluation/performance confidence assessment. Since the Government intends to consider PPI provided by other sources as well as that provided by the offeror(s), offeror’s "roadmap" should be both specifically applicable to the efforts offeror identifies and general enough to apply to efforts on which the Government receives information from other sources.

4.3 PPI Questionnaire.

4.3.1 The offeror shall send out, and confirm receipt and submission of the PPI Questionnaire (Section L, Attachment 2), from each of the offeror’s, critical subcontractors’, teaming contractors’ and/or joint venture partners’ (i.e., each entity’s) POCs identified in the PPI

Questionnaire Tracking Record (Section L, Attachment 3). The responsibility to send out the PPI Questionnaires rests solely with the offeror. For each questionnaire, complete and sign a letter containing substantially the same information as in the Sample Questionnaire Cover Letter (Section L, Attachment 4). Cover letters should be printed on company letterhead. The offeror shall exert its best effort to ensure that a current POC, per relevant contract, submits a completed PPI Questionnaire directly to the Government not later than the proposal due date. Each of the offerors’ POCs shall e-mail the completed PPI Questionnaire directly to Ms. Amy L. Barnes at amy.barnes.2@us.af.mil. Please instruct POC to call Ms. Amy L. Barnes (405)736-8739 with any questions.

4.3.2 Questionnaires shall be sent directly to the Government from at least one of the following POCs: Program/Project Manager or equivalent, Contracting Officer/Contract Administrator or equivalent, or Contracting Officer Representative (COR). Once the PPI Questionnaires are completed by the POCs, the information contained therein shall be considered sensitive and shall not be released to the offeror.

4.3.3 Format for Contract Information. Using the format below, the offeror shall provide the following information for each contract reference submitted for past performance evaluation.

Provide concise comments regarding Offeror’s performance on the contracts Offeror identifies.

It shall include a cross-reference matrix identifying the PWS references and the team members proposed to perform that function.

a. Offeror/Subcontractor Name (Company/Division):

CAGE Code:

DUNS Number:

(NOTE: If the company or division performing this effort is other than the offeror, or the relevancy of this effort to the instant acquisition is impacted by any company/corporate organizational change, refer to paragraph 3.2.2, "Organizational Structure Change History," and provide as part of the Present/Past Performance proposal.)

b. Acquisition Title:

c. Contract Specifics:

(1) Contracting Agency or Customer:

(2) Contract Number:

(3) Contract Type (e.g. firm-fixed-price, CR, etc):

(4) Period of Performance (within the last three years):

(5) Contract Dollar Value: $

d. Description of Effort as __Prime or __Subcontractor

(Highlight portions considered most relevant to current acquisition) mailto:amy.barnes.2@us.af.mil

e. Primary and Secondary Customer Points of Contact: Provide verified, up to date, Points of Contact on all past performance references.

Name:

Office:

Address:

Telephone:

E-mail:

f. Relevancy: Include a list of tasks performed on the effort that are relevant to this requirement. For a description of the characteristics or aspects the Government will consider relevant, see Section M, Paragraph 2.2.

g. Address any technical (or other) area about this contract/program considered unique.

h. Describe the nature or portion of the work on the proposed effort to be performed by the business entity whose PPI is being reported. Also, estimate the percentage of the total proposed effort that will be performed by this entity and whether it will be performing as the prime, subcontractor, or a corporate division related to the prime (define relationship).

i. Describe any past or present litigation or administrative proceeding pertaining to the contract reference, including the results if the proceedings are complete or the status if the proceedings are ongoing. Provide a copy of any cure notices or show cause notices received on each contract reference and a description of any corrective action taken. Indicate if any of the contract references were terminated and the type and reasons for termination.

j. Discuss the number and severity of any problems in the contract reference considered relevant to the proposed efforts and identify the effectiveness of corrective actions to resolve the problems. Provide any contract discrepancy reports, corrective action reports or other non-compliance correspondence.

k. Include any information not previously covered, which will enhance the evaluators’ understanding of the offeror or any sub-contractor’s proposed qualifications.

4.4. Consent Letters. (Attachment X) The offeror shall submit a consent letter, executed by any potential subcontractors, teaming partners, and/or joint venture partners. The consent letter authorizes release of adverse PPI to the offeror so the offeror can, in turn, respond to such information. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information in the Offeror’s performance. A sample letter follows:

SAMPLE

Contracting Officer:

We are participating as a (subcontractor/teaming partner) with (prime contractor or name of entity providing proposal) in responding to the 38 CONS/LGCC, Tinker Air Force Base Request for Proposal FA8773-18-R- 8008 for the contract at 90th COS primary location JBSA-Lackland AFB, TX.

We understand the Government is placing increased emphasis on past performance in order to obtain best value in source selections. In order to facilitate the performance confidence assessment process we are signing this consent letter to allow you to discuss our past and present performance information with the prime contractor during the source selection process.

(Signature, printed name, and title of individual who has the authority to sign for and legally bind the company) Company Name:

Address:

4.5. Client Authorization Letters.

PPI concerning private sector contractors, subcontractors and joint venture partners cannot be disclosed to the Government without their consent. Client authorization letters are required for each identified effort for a commercial customer. This letter will authorize release to the Government of requested information on the offeror’s performance. The Government will need the consent before contacting commercial customers to assess the offeror’s past performance. In an effort to assist the evaluators in assessing offeror’s past performance relevancy and confidence, the Government requests the following client authorization letter be completed for any commercial customers identified in offeror’s proposal. Offeror shall include the completed client authorization letter(s) within the Present/Past Performance Volume II.

SAMPLE

“Client:”

We are responding to the 38 CONS/LGCC, Tinker Air Force Base Request for Proposal FA8773-18-R-8008 for the contract at 90th COS primary location (JBSA-Lackland AFB, TX).

The Government is placing increased emphasis on past performance as a source selection factor. The Government requires entities responding to their solicitation to identify clients and requests client participation in the evaluation process. You are hereby authorized to respond to those inquiries if the contracting office contacts you for information on work performed by our firm.

We have identified ______ of your organization as the point of contact based on his/her knowledge of our work.

We appreciate your cooperation. You may direct any questions to:

4.6 Reference Data. The Government reserves the right to contact and use information provided by the references and any other sources. The Government will also obtain and consider information about other contracts not mentioned in the Offeror’s proposal, but which the Government believes to be similar to the proposed effort. It is the Offeror’s responsibility to ensure all reference data is current and correct so that the Government can properly evaluate PPI.

5.0. Factor 3 – Cost/Price

5.1. General Instructions

5.1.1 Price Reasonableness, Completeness, Balance, Affordability, and cost realism (only for CPFF Labor CLINs and Professional Compensation Plans). This section is to assist you in submitting information other than cost or pricing data that is required to evaluate the reasonableness, completeness, balance, affordability, and cost realism of the offeror’s proposed price. Compliance with these requirements is mandatory and failure to comply may result in rejection of the Offeror’s proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness, cost realism (for CPFF Labor CLIN and professional compensation only), completeness, balance, and affordability. The burden of proof for credibility of proposed prices rests with the offeror at the time of proposal or during subsequent discussions (if any are held). Additionally, the offerors proposed price shall be within the affordability amounts listed in Section M.

5.1.2 Pricing Information Requirements

The price proposal shall not include information beyond that required by this instruction unless the offeror considers it essential to document or support offeror’s position. All information relating to the proposed price, including all required supporting documentation or assumptions of the proposal must be included in the section of the proposal designated as the Price Volume.

Under no circumstances shall this information and documentation be included in the Technical or Past Performance volumes.

5.1.3 Adequate Price Competition

The Government has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the Contracting Officer will review this determination and if, in the Contracting Officer’s opinion, adequate price competition exists, no additional cost information will be requested and certification under FAR 15.406-2 will not be required. However, if at any time during this competition the Contracting Officer determines that adequate price competition no longer exists; offerors may be required to submit Other than Cost or Pricing Data information to the extent necessary to determine the reasonableness of the price.

5.1.4 Rounding

All dollar amounts (unit and extended prices and other price factors) provided shall be rounded to the nearest penny (two decimal places only). This includes base period and out-year (option) prices. Failure to round unit prices to no more than two decimals may result in rejection of proposal. Rounding errors caused by Government formulas will be corrected during evaluation to round to the nearest penny.

5.1.5 Professional Compensation

As part of the price proposal, offerors shall provide a total compensation plan setting forth salaries and fringe benefits proposed for the professional employees who will work under the contract IAW FAR 52.222-46 -- Evaluation of Compensation for Professional Employees (Feb 1993).

5.1.5.1 Professional Employee Compensation

In accordance with FAR Subpart 22.11 and FAR Provision 52.222-46, Evaluation of Compensation for Professional Employees, the offeror and subcontractors/teaming partners/joint venture partners shall submit a total compensation plan setting forth salaries and fringe benefit package proposed for the prime’s professional employees. The prime Offeror shall instruct its subcontractors to submit their total compensation plan directly to the contracting officer. The prime Offeror shall also submit a list of the subcontractors to include points of contact and phone numbers who will be submitting professional employee compensation packages to the Government. The total compensation plan submitted in the proposal will not become a part of the awarded contract.

5.1.5.2 Total Compensation Plan

Provide the planned compensation for all professional employee labor categories proposed to perform the effort. Describe the job skills and qualification requirements associated with each identified labor category. Identify the Standard Occupational Classification (SOC) code for each labor category using the Bureau of Labor Statistics SOC system, http:www.bls.gov/soc/. The labor categories shall be identified by geographic location of contract performance. Provide the corresponding salary and quantified fringe benefits for each labor category and skill level. The fringe benefit data shall also include a description of the benefits offered, and to which professional employee category (ies) the fringe benefits would apply.

5.1.5.3 Labor Rates

Offerors shall propose fully burdened Firm Fixed Price (FFP) direct labor rates. The Offeror shall complete and submit Labor Rate Tables for the Prime and all teaming partners for the entire contract periods using the excel spreadsheet (Section J, Attachment 2). Failure to propose rates for all labor categories will render the proposal incomplete, and the entire proposal will be subject to rejection.

FULLY BURDENED FFP LABOR RATES:

The following provides guidelines for the major cost/price elements normally associated with the buildup of fully burdened labor rates and required support documentation:

Base Labor Rates: Show base labor rates associated with each labor category. Base rates are the hourly rates that the employees will be paid for performance under the basic contract. The most common basis for a proposed base rate is the actual rate the employee is currently being paid. If an individual in a particular labor category is currently not employed, a verifiable method used to establish the reasonableness of proposed rate must be provided, e.g. Payrolls, Salary.com, quotes, etc.

Base Labor Rate Escalation: Current rates will require adjustment for annual cost of living increases. Base rates for contract out-years will require escalation adjustments to reflect what employees will receive for those periods.

Indirect Rates: Common indirect rates are Labor Overhead, Fringe Benefits, General & Administrative (G&A), and Facilities Capital Cost of Money (FCCOM). To support reasonableness, describe the basis of estimate of the proposed direct and indirect rates and factors and provide narrative support for all elements.

5.1.5.4 Survey and Studies

Provide the recent surveys and studies from professional, public, and private organizations (e.g., Watson & Wyatt, Economic Research Institute, Bureau of Labor Statistics, etc.) used to support the proposed salaries and fringes. Identify the source with the provided surveys and studies. If not using one of the sources listed above, explain the credibility of the source providing the surveys and studies.

5.2 Volume Organization.

The Price volume shall consist of the following sections:

SECTION 1 - Table of Contents; summary descriptions of estimating, purchasing, and accounting systems; changes to estimating, and accounting practices.

SECTION 2 - Pricing Notes/Methodology: pricing information and supporting data, to include estimating methodology. Provide the Professional Compensation Plan and all information and supporting data for the Professional Compensation Plan in this section.

SECTION 3 - Pricing Assumptions/ Exceptions: Identify any assumptions and exceptions taken to the pricing requirements stated in this solicitation. Provide complete rationale for each assumption and exception. Annotate “none,” if no assumptions or exceptions apply.

SECTION 4 – Pricing Table: (included as Section J, Attachment 2 to the solicitation).

The offeror shall comply with the following requirements and instructions:

a. Price Contract Line Item Numbers (CLINs) X001 and X002. Limit unit prices to two decimal places. If the offeror is providing a CLIN to the Government at no additional charge, “$0.00” must be entered for that item.

The dollar value of CLINs X003 and X004 are amounts established by the Government and shall not be altered by the Offeror.

b. For evaluation purposes, Offerors are required to submit only FFP and CPFF

Labor pricing. Cost Reimbursable CLINs will be established by the government.

c. The rates as proposed in the Pricing Table shall be contractually binding rates should Offeror be awarded a contract.

d. Electronic Media Submission of the Pricing Table. The CLINs in the Pricing Table of this solicitation are an electronic file, presented as Excel for Microsoft Office spreadsheet/workbook format. Submit both a hard copy and an electronic copy using the exact file provided by the Government without changing the format of the files. Do not password protect any Microsoft Excel spreadsheets.

e. Description of Files:

(1) Summary Sheet: Contains cells for the entry of unit prices for CLINs X001 and X002, and calculates extended prices for the Option to Extend Services CLINs.

(2) Option to Extend Services, CLINs 5002 will be automatically populated IAW clause 52.217-8 and continued performance shall be the same pricing as Option IV. While it is not the Government’s intent to utilize this option CLIN, it is included to facilitate the extension of services if it is deemed necessary at the end of the base or any option period.

6.0 VOLUME IV-CONTRACT DOCUMENTATION

6.1 CONTRACT DOCUMENT SECTIONS

6.1.1 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 SF 33 and SF 30 for any subsequent amendments issued. The offeror shall complete and submit “ONLY” the contract document sections as follows:

Section A -- Solicitation/Contract Form. Completion of Blocks 12 through 18 (including original signature and date) of the SF 33. Signature by the offeror on the SF 33 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked and should contain each volume identified in the above Table 2 - BINDER ORGANIZATION. Copy 1, Copy 2, Copy 3, and Copy 4 should each be clearly marked and should contain each volume identified in Table 2 - BINDER

ORGANIZATION.

Section B -- Supplies or Services and Costs/Prices. Do not include. This section will be populated by the Government at contract award from data provided from Section J, Attachment 2, Pricing Table.

Section C, E, and F -- Do not include. These sections are not modifiable by the offeror and are redundant to include with the proposal submission.

Section G -- Contract Administrative Data. Do not include. This section is not modifiable by the offeror and is redundant to include with the proposal information.

Section I -- Contract Clauses. Submit RFP Section I pages for only clauses which require offeror fill-ins. Other pages in this section shall not be included with the submission.

Section J -- Attachments. Please include completed DD254, OCI Mitigation Plan, if applicable.

The Offeror shall submit an OCI Mitigation Plan if an OCI issue is identified. The Offeror shall include, in Volume IV, the OCI Mitigation Plan IAW AFFARS 5352.209- 9000 and AFFARS 5352.209-9001 which will become part of the contract upon award.

The proposed OCI mitigation plan shall: 1) Describe in detail any actual or potential OCI of which the Offeror is aware of with the performance with its division, affiliates, and/or subcontractors under any contract the Offeror or any of its divisions/affiliates/subcontractors has been or may be awarded by any federal agency or any other entity whose performance may create an OCI if awarded this contract; 2) Describe in detail the methodology the Offeror used to identify those potential or actual OCI described in paragraph 1); and 3) Describe in detail the specific techniques the

Offeror intends to use to mitigate each identified potential or actual OCI Times New Roman, Arial or Courier type”.

Section K --

(1) System for Award Management (SAM) (Representations, Certifications, and other Statements of Offerors). Completed SAM representations, certifications, acknowledgments and statements shall be included with submission. Ensure SAM is current, complete, and accurate at the time of proposal. SAM representations and certifications must include those specified within Section K of this RFP. SAM can be accessed at https://www.sam.gov/portal/public/SAM/#1. Offeror shall be eligible for award under the specified NAICS code, 541512 and as a SBA 8 (a) at the time of their proposal submission and remain eligible when verified again prior to award of the contract.

(2) Joint Venture Agreements. Per the Small Business Administration (SBA), Joint Ventures are allowable on competitive 8(a) set-asides; however, the joint venture agreement must be received by SBA PRIOR to proposal due date and approved before award of any resulting contract. If you are contemplating a joint venture on this project, you must advise your assigned SBA Business Development Specialist (BDS) as soon as possible. It is also recommended that the agreement be submitted as soon as practicable to ensure compliance with established regulations. Any corrections and/or changes needed can be made only when the BDS has adequate time for a thorough review before the proposal due date. No corrections and/or changes are allowed after time of submissions of proposals.

(3) Submit RFP Section K pages for clauses which require offeror fill-ins.

Section L – Do not include. This section is not modifiable by the offeror and is redundant to include with the proposal submission.

Section M - Do not include. This section is not modifiable by the offeror and is redundant to include with the proposal submission.

6.2 Pricing Support Information

6.2.1 Estimating System

Provide a summary description of your standard estimating system or methods. Also, identify any deviations from your standard estimating procedures in preparing this proposal volume.

Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

6.2.2 Purchasing System

Provide a summary description of your purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). Also, identify any deviations from your standard procedures in preparing this proposal. Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

6.2.3 Accounting System

Indicate whether you have Government approval of your accounting system and if so, provide evidence of such approval. Also, identify any deviations from your standard procedures in preparing this proposal.

6.2.4 Annual Price Changes

Proposed price increases greater than 5% per period shall be verified and addressed for reasonableness in this section.

6.2.5 SCA/CBA

It is the responsibility of the Offeror and the subsequent contract awardee to comply with the Services Contract Act (SCA) or Collective Bargaining Agreement (CBA). In this section of the Cost/Price Volume, a table shall be provided conforming (linking) the Offeror’s proposed job categories/skill levels considered subject to the SCA or CBA with the job categories/skill levels of the Wage Determination (WD). This cross-reference provides a tie between the labor categories/skill levels proposed and the labor categories/skill levels listed in the SCA WD or

CBA.

6.2.6 Government Field Support Agencies

38 CONS/LGCC is responsible for administration of the Offeror’s Government contracts.

6.2.7 Other Documentation

Other documentation considered by Offerors to be essential for support of proposed prices shall be presented in this section.

6.2.8 Probable Subcontractors

Submit a list of the proposed probable subcontractors and inter-divisional transfers showing (a) the supplier and (b) description of effort.

6.2.9 Submission of Price/Cost Models

Submit an electronically encoded price/cost model in support of the proposed Total Evaluated Price (TEP). Any price/cost model submitted must be consistent with your approved estimating system and must duplicate the logic and mathematical formulas reflected in the paper copy of your proposal. Cost/price models submitted must comply with the following format requirements:

(a) Data file should be submitted on a CD.

(b) Data file should be .XLS file format (MS-Excel 2010 or earlier) compatible format.

ITO ATTACHMENTS

ITO Attachment – 1.0 PROPOSED TEAM LIST

ITO ATTACHMENT 1.0

PROPOSED TEAM LIST

TEAMING LIST

Offeror (Prime) Contractor: CAGE Code: DUNS Number:

Designation Codes:

Joint Venture: JV Informal Joint Venture: IJV Prime/Sub: PS Mentor/Protégé: MP

Subs/Teaming Contractor: Designation Code: CAGE Code: DUNS Number:

1.

2.

3.

4.

5.

6.

7.

8.

9.

10.