Amended_CyOFTS_II_Section_L_September_2017.docx
DOCX document 65 KB Posted
- Attached to
- Solicitation Notice Federal contract opportunity
- Solicitation number
- FA8773-17-R-8005
View the file
Other files for this federal contract opportunity
Show all 50
Solicitation Notice has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
L-1 PROPOSAL PREPARATION INSTRUCTIONS
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 Request for Proposal RFP. Non-conformance with the instructions provided in this Request for Proposal preparation Instructions 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.1 GENERAL INFORMATION
2.1.1 Point of Contact (POC)
The Contracting Officer (CO) is the sole point of contact for this acquisition. Written requests for clarification may be sent to the CO at the address located in Section A of the solicitation.
2.1.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 (IAW) 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 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.
2.1.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 and CS 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.
2.1.4 Electronic Reference Documents
All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at http://www.fedbizopps.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications in order to receive information posted to the website for this solicitation.
2.1.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.1.6 Reading Room Library
A Reading Library containing a list of Exhibits has been established at Hurlburt Field, Florida. The single POC for access is Mr. Scott Runyan who can be reached at (850) 884-5450 or scott.runyan@us.af.mil. Instructions for the library are included in the request for proposal (RFP) as Section L, Attachment 8. Reservations shall be made in advance no later than 6:00 PM CST on 13 September 2017. The library will be open Monday, 18 September 2017 to Friday, 22 September 2017.
2.1.7 Questions.
All questions related to this solicitation must be submitted to shela.colon.1@us.af.mil no later than 3:00 PM (CST) 19 September 2017. Late requests will not be considered.
2.1.8 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; and 2) 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 time it submits its proposal. Failure to do so shall result in the government determining a proposal unacceptable.
2.2. ORGANIZATION
2.2.1 Number of Copies/Page Limitations
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, glossary, and Lesson Plan Development (Technical Subfactor 2). 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 Evaluation Notices (ENs).
2.2.2 Offeror’s proposal shall consist of four separate volumes: Volume I – Technical Proposal, Volume II – Present/Past Performance Information (PPI), Volume III – Price Proposal, and Volume IV – Contract Documentation. The content of each proposal binder is described in detail as follows:
TABLE 1 – PROPOSAL ORGANIZATION (within binders)
| VOLUME |
| VOLUME TITLE |
| COPIES |
| PAGE LIMIT |
| I |
| Technical |
| 5 |
| 50 however scenarios (Technical subfactor 2) are not included in 50 page limit |
| II |
| Past Performance |
| 5 |
| 50 |
| III |
| Cost/Price |
| 2 |
| No Limit (See Paragraph 5) |
| IV |
| Contract Documentation |
| 2 |
| No Limit (See Paragraph 6) |
TABLE 2 – BINDER ORGANIZATION (within binders)
VOLUMES TO INCLUDE:
ORIGINAL
I, II, III, IV
| COPY 1 |
| I, II, III, IV |
| 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.2.3 Page Size and Format
(a) 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. Pages shall be single-spaced/typed with 1.5 line spacing, and at least double-spaced between paragraphs and factors or sub-factors. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12-point, Times New Roman, Arial or Courier type. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least one-inch margins on all sides. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to EN responses.
(b) Legible tables, charts, graphs and figures may be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and shall count as two pages. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics and not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than ten-point. These limitations shall apply to both electronic and hard copy proposals.
2.2.4 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.2.5 Indexing
Tab indexing shall be used to identify volumes.
2.2.6 Binding and Labeling
Each volume of the proposal shall be separately bound in one-inch, three-ring, loose leaf binders permitting the binders to lie flat when open. Staples shall not be used. All binders shall allow for easy removal and replacement of pages. A cover sheet shall 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-17-R-8005, CYOFTS II, Copy 1 of 4). The same identifying data shall be placed on the spine and front of each binder. Be sure to apply all appropriate classification 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. The original shall be marked “Original”.
2.2.7 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. Adobe PDF format is acceptable for portions of the proposal submissions not required to use MS Excel. Each volume shall be submitted as a separate attachment to an email addressed shela.colon.1@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.
2.2.8 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.3 PROPOSAL DELIVERY
2.3.1 Delivery
Offerors must make an appointment with Ms. Shela Colon via email @shela.colon.1@us.af.mil, (405) 736-8736 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, Shela Colon, at 38 CONS/LGCC, 4004 Hilltop Road, Room 208, Tinker AFB, OK 73145. 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 24 October 2017. Late deliveries will be handled IAW paragraph (c) (3) of FAR 52.215-1, Instruction to Offerors-Competitive Acquisition.
2.3.2 Early Submission
Offerors are encouraged to submit Volumes II (Past Performance) and, Volume IV (Contract Documentation), as early as 17 October 2017 but not later than 24 October 2017. Please contact the Contracting Officer to arrange for early delivery. Failure to submit early proposal information will not result in offeror disqualification.
3.0 Volume I – TECHNICAL PROPOSAL
3.1 GENERAL
3.1.1 The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Offeror’s 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 offeror would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By Offeror’s proposal submission, Offeror is representing that Offeror’s firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for an Offeror to tell us so in Offeror’s proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.
3.1.2 Identify submitted material by corresponding factor, subfactor, and paragraph/element herein. If an offeror is subcontracting/teaming with another vendor, the prime shall clearly identify work to be performed by each specific subcontractor within the appropriate factors in the prime’s proposal. The technical proposals shall provide a clear distinction of functions to be performed by the prime and subcontractor to include the following: the nature of work, criticality of the work, and the percentage of overall effort performed by each subcontractor in each area of service. Technical and past performance information should be provided on each subcontracting/teaming arrangement.
3.2 Volume Organization
The format of the Technical volume shall be as follows:
| Tab 1: | Table of Contents/Glossary |
| Tab 2: | Cross-Reference Matrix |
| Tab 3: | Management Plan/Staffing Plan (Subfactor 1) |
| Tab 4: | Mission Operations Approach (Subfactor 2) |
3.3 FORMAT AND SPECIFIC CONTENT
3.3.1 Technical
3.3.1.1 In the technical volume, address your technical solution for meeting the Government’s minimum performance or capability requirements of each technical subfactor.
Subfactor One - Management Plan/Staffing Plan. The offeror shall present a staffing and management approach that explains how it will meet the PWS requirements and Appendices. The approach shall not include employee names or resumes. The approach shall provide the following:
(1) Submission of CAGE code that shows offeror has an Active TOP SECRET Facility Clearance, which will be verified in the Joint Personnel Adjudication System (JPAS).
(2) Completed CyOFTS II Labor Matrix Chart (Section L, Attachment 9), identifying proposed labor categories, quantity of personnel by task, technical certifications, and security clearance by labor category.
(3) Position descriptions for each labor category. (No more than one page each and will not be included in the technical proposal page limitations).
(4) Methods of recruiting, accession, retention, training (e.g. continuation, certification, and upgrade), and obtaining and maintaining personnel clearances and certifications.
(5) Methods of how continuity of service will be met during personnel absences due to sickness, leave, and vacancies (to include military Reserve and National Guard obligations) so that the mission is not impacted
(6) The offeror shall present a transition plan that ensures continuity of services and a smooth effective transition where they have the ability to be fully staffed and ready to begin performance on day 1 of the contract.
Subfactor Two - Mission Operations. Present mission operations acceptable approach for each of the two scenarios that complies with policy and guidance identified in the PWS pertaining to Lesson Plan/Virtual Environment Configuration lesson plan IAW PWS. Note: Subfactor two submissions will not count toward the 50-page technical page limit
Scenario One: A new course for Incident Response is being implemented at the schoolhouse and it requires you to create a cognitive lesson plan IAW PWS Sections 3.1.1 and 3.1.2.
(1) Utilizing the Master Training Task List (MTTL) (Section L, Attachment 2), create a one-hour cognitive lesson IAW Section L, Attachment 3, which covers the incident response process as defined by the National Institute of Standards and Technology (NIST) (Additional sources may be used for amplification), and how this process is applied across the USAF enterprise network through the AF Cyber Weapons Systems.
(2) Summarize how understanding the configuration of the systems in the environment can aid the incident response process.
(3) The offeror shall submit the lesson in the cognitive format (Section L, Attachment 3), that is written clearly, concisely and measurable that supports the objectives at the appropriate blooms taxonomy level of learning. All reference must be valid and up to date. All lesson plan parts must be free of grammar and spelling errors.
Scenario Two: A new course for Incident Response is being implemented at the schoolhouse and requires you to create a virtual (hands-on) Environment lesson that supports scenario one IAW PWS Sections 3.1.1 thru 3.1.3.
(1) Utilizing the MTTL (Section L, Attachment 2), create a one hour Virtual Environment, hands-on lesson supporting scenario one IAW Section L, Attachment 4. Demonstrate how to implement NIST standards and DISA Security Technical Implementation Guides (STIGs) to secure and harden an “out of the box” Windows 10 enterprise workstation, according to Microsoft Windows 10 STIG - Ver 1, Rel 9; use a VMWare ™ Platform. Lesson must be submitted in correct psychomotor format (Section L, Attachment 4), that is written clearly, concisely and meaurable and support the objectives at the appropriate blooms taxonomy level of learning. All lesson parts must be free of grammar and spelling errors.
(2) Employ an open-source investigative forensic toolkit, demonstrate capabilities for scenario one.
(3) Configure the workstation to properly support the designed lesson to be completed by the student. The virtual machine should be provided in VMware’s “OVA” format so that in can be imported into VMware Workstation 12 or vSphere 6. Ensure that VMware tools is properly installed, and that the virtual machine is utilizing the proper virtual hardware set for operations. This virtual machine should be provided along with the written student lab, login instructions, and configuration notes to be evaluated. Submissions for this virtual machine MUST be accomplished on a portable hard drive. Once the portable hard drive is submitted, the government will not return this drive after delivery. In addition, “NO” USB thumb drives or CD’s are authorized for government use and will not be accepted for this submission.
4.0. VOLUME II – PAST PERFORMANCE INFORMATION
4.1 GENERAL
4.1.1 Each offeror shall submit Past Performance Information (PPI) with its proposal IAW the format contained in paragraphs below. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform any of the proposed effort. Offerors are cautioned that the Government will use data provided by each offeror in this part and data obtained from other sources in the evaluation of past performance. Each offeror shall submit Present/Past Performance Information (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 maximum of five recent contracts that the 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 PPQ (Section L, Attachment 7), from each of the offerors’, critical subcontractors’, teaming contractors’ and/or joint venture partners’ (i.e., each entity’s) POCs identified in the PPQ Tracking Record (Section L, Attachment 5). The responsibility to send out the PPQ 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 6). 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. Shela Colon at shela.colon.1@us.af.mil. Please instruct POC to call Ms. Shela Colon (405) 736-8736 with any questions.
4.3.2 Questionnaires shall be sent directly 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 your performance on the contracts you identify. In the cross reference matrix identified in paragraph 2.2.4 above, specify the work that will be performed by teaming partners and which PPI references for the applicable teaming partner are relevant to this work.
| 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 7 below, | "Organizational Structure Change History," and provide as part of the 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 the Prime or the Subcontractor | ||
| (Highlight portions considered most relevant to current acquisition) | |||
| 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, Attachment 1 | ||||
| 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, based on total proposed price, 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 listed and a description of any corrective action taken. | Indicate if any of the contract reference listed 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
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-17-R-8005 for Cyber Operations Formal Training support (CyOFTS II) contract for the 39th Information Operations Squadron. The primary locations for this contract are Hurlburt Field, FL and 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-17-R-8005 for Cyber Operations Formal Training support (CyOFTS II) contract for the 39th Information Operations Squadron. The primary locations for this contract are Hurlburt Field, FL and 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 may also obtain and consider information about other contracts not mentioned in the offeror’s proposal, but which the Government determines 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. VOLUME III –PRICE PROPOSAL
5.1 GENERAL INSTRUCTIONS
5.1.1 Price Reasonableness, Completeness, Balance, and Affordability
This section is to assist you in submitting information other than cost or pricing data that is required to evaluate the reasonableness, completeness, balance, and affordability 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, price realism (for 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 Price 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 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 1). 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 system and invoicing processes and 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 assumptions and exception. Annotate “none,” if no assumptions or exceptions apply.
Section 4: Pricing Table: (included as Section J, Attachment 1 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. Option to Extend Services, CLIN 5002, will be automatically populated with established formulas on the Pricing Table.
b. For evaluation purposes, Offerors are required to submit only FFP 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 1, 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, 611420 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 EXCEPTIONS AND/OR ASSUMPTIONS
6.2.1 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. 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/assumption and fully explain its impact, if any, on the performance, schedule, price, and specific requirements of the solicitation. This information shall be provided in the following format and content:
Solicitation Exceptions
Solicitation Document Reference PWS, Solicitation, Section L, etc.
Page/Paragraph Provide applicable page and paragraph numbers and/or clause/provision numbers
Requirement/Portion Identify the requirement or portion to which exception is taken
Rationale Describe why the requirement can/will not be met
6.3 OTHER INFORMATION REQUIRED
6.3.1 Authorized Offeror Personnel
Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.
6.3.2 Section L Attachments:
Attachment 1: Sample Solicitation Cross Reference Matrix Attachment 2: Master Training Task List (MTTL) Attachment 3: Sample Instruction Plan (Parts I, II, III, and IV) Attachment 4: Sample Psychomotor Lesson Attachment 5: Past Performance Questionnaire (PPQ) Tracking Record Attachment 6 Past Performance Questionnaire (PPQ) Sample Cover Letter Attachment 7: Past Performance Questionnaire (PPQ) Attachment 8 Reading Room Library Attachment 9: Labor Matrix Attachment 10: Offeror Compensation Evaluation Spreadsheet
File details come from the government source that posted it. Updated .