FA7046-15-R-0001Amendment_2.doc

DOC document 384 KB Posted

Attached to
Fighter Test Services (FTS) Industry Day Federal contract opportunity
Solicitation number
FA7046-15-R-0001
Issued by
Department of the Air Force Materiel Command Test Center

About this file

FTS RFP Amendment 2

View the file

Other files for this federal contract opportunity

Other files attached to Fighter Test Services (FTS) Industry Day, newest first.
File Type Posted
FA7046-15-R-0001_Amendment_3.pdf PDF
Q A_12_Nov_15.docx DOCX document
Question_ _Answer_Document.docx DOCX document
FINAL_PWS_FA704615R0001-0002_26_Oct_15.docx DOCX document
FINAL_PWS_FA704615R0001-0001_26_Oct_15.docx DOCX document
FA7046-15-R-0001_Amendment_1.doc DOC document
FINAL_PWS_FA704615R0001-0002_21_Oct_15.docx DOCX document
Exhibit_A_FTS_CDRLs_21_Oct_15.docx DOCX document
FINAL_PWS_FA704615R0001-0001_21_Oct_15.docx DOCX document
RFP_FTS_FA7046-15-R-0001.doc DOC document
FINAL_PWS_FA704615R0001-0003_21_Oct_15.docx DOCX document
Attachment_1_PWS_FA704615R0001_-_BasicContract_21_Oct_15.docx DOCX document
Attachment_2_DRAFT_DD_Form_254_21_Oct_15.pdf PDF
All_FTS_DRFP_Questions_as_of_11_Sep_15.docx DOCX document
DRAFT_RFP_FA7046-15-R-0001.doc DOC document
DRAFT_DD_Form_254.pdf PDF
Draft_PWS_FA704615R0001-0005.docx DOCX document
Draft_FTS_CDRLs.docx DOCX document
Draft_PWS_FA704615R0001-0002.docx DOCX document
Draft_PWS_FA704615R0001_(Umbrella_Contract).docx DOCX document
Draft_PWS_FA704615R0001-0003.docx DOCX document
Draft_PWS_FA704615R0001-0001.docx DOCX document
Draft_PWS_FA704615R0001-0004.docx DOCX document
AFOTEC_FTS_Industry_Day_Questions_and_Answers.docx DOCX document
ABQ_Map_of_PTi__Sunport_ _Collaboration_Center.docx DOCX document
ABQ_Hotel-Transportation-Food_Resource_List.xlsx XLSX spreadsheet
DRAFT_PWS_-_FTS_(Umbrella_Contract)_-_Config_Control.docx DOCX document
Show all 27

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

FA7046-15-R-0001

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 30-Nov-2015 02:00 PM to 04-Dec-2015 02:00 PM.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0001

The CLIN extended description has changed from The contractor shall furnish the necessary labor reasonably required to accomplish phase-in effort of task orders issued pursuant to the requirements contained in the Basic Contract Performance Work Statement (PWS) entitled, "Air Force Operational Test and Evaluation Center (AFOTEC) Fighter Test Services (FTS)", dated 21 October 2015, Attachment 1, and Clause 5.8.1, "Phase-In" in Section 5.8 entitled "Transition" Three task orders will be issued at award of this ID/IQ contract. Subsequent task orders will be issued in accordance with Paragraph 10 of the Basic PWS entitled, "Task Order Proposal Procedures." to The contractor shall furnish the necessary labor reasonably required to accomplish phase-in effort of task orders issued pursuant to the requirements contained in the Basic Contract Performance Work Statement (PWS) entitled, "Air Force Operational Test and Evaluation Center (AFOTEC) Fighter Test Services (FTS)", dated 21 October 2015, Attachment 1, and Clause 5.8.1, "Phase-In" in Section 5.8 entitled "Transition" Two task orders will be issued at award of this ID/IQ contract. Subsequent task orders will be issued in accordance with Paragraph 10 of the Basic PWS entitled, "Task Order Proposal Procedures.".

CLIN 0002

The CLIN extended description has changed from The contractor shall furnish the necessary labor reasonably required to accomplish task orders issued pursuant to the requirements contained in the Basic Contract Performance Work Statement (PWS) entitled, "Air Force Operational Test and Evaluation Center (AFOTEC) Fighter Test Services (FTS)", dated 21 October 2015, Attachment 1, Three task orders will be issued at award of this ID/IQ contract. Subsequent task orders will be issued in accordance with Paragraph 10 of the Basic PWS entitled, "Task Order Proposal Procedures." to The contractor shall furnish the necessary labor reasonably required to accomplish task orders issued pursuant to the requirements contained in the Basic Contract Performance Work Statement (PWS) entitled, "Air Force Operational Test and Evaluation Center (AFOTEC) Fighter Test Services (FTS)", dated 21 October 2015, Attachment 1, Two task orders will be issued at award of this ID/IQ contract. Subsequent task orders will be issued in accordance with Paragraph 10 of the Basic PWS entitled, "Task Order Proposal Procedures.".

CLIN 0006

The CLIN extended description has changed from The contractor shall furnish the necessary labor reasonably required to accomplish phase-out effort of task orders issued pursuant to the requirements contained in the Basic Contract Performance Work Statement (PWS) entitled, "Air Force Operational Test and Evaluation Center (AFOTEC) Fighter Test Services (FTS)", dated 21 October 2015, Attachment 1, and Clause 5.8.2, "Phase-Out", in Section 5.8 entitled "Transition." Three task orders will be issued at award of this ID/IQ contract. Subsequent task orders will be issued in accordance with Paragraph 10 of the Basic PWS entitled, "Task Order Proposal Procedures." to The contractor shall furnish the necessary labor reasonably required to accomplish phase-out effort of task orders issued pursuant to the requirements contained in the Basic Contract Performance Work Statement (PWS) entitled, "Air Force Operational Test and Evaluation Center (AFOTEC) Fighter Test Services (FTS)", dated 21 October 2015, Attachment 1, and Clause 5.8.2, "Phase-Out", in Section 5.8 entitled "Transition." Two task orders will be issued at award of this ID/IQ contract. Subsequent task orders will be issued in accordance with Paragraph 10 of the Basic PWS entitled, "Task Order Proposal Procedures.".

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L INSTRUCTIONS

L1.0 General Instructions

(a) The Offeror's proposal must include all data and information requested by this Instruction to Offerors (ITO) and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

(b) The proposal shall be clear, concise, and shall 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 is specified in Section A of the model contract/solicitation. The Offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

(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.

L1.1 General Information

L1.1.1. Point of Contact

The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the PCO. Written requests for clarification may be sent to the PCO:

AFOTEC A-7K

ATTN: Linda Buix, Contracting Officer

1251 Wyoming Blvd SE

Kirtland AFB, NM 87117 e-mail: linda.buix@us.af.mil Phone: 505-846-1955

L1.1.2. Debriefings

The PCO 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 PCO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. 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 with FAR 15.505or FAR 15.506, as applicable.

L1.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 PCO in writing with supporting rationale as well as the remedies the Offeror is asking the PCO to consider as related to the omission or error. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion. This reservation includes matters of additional or substitute pages of the initial proposal.

L1.1.4. Electronic Reference Documents

All referenced documents for this solicitation are available on FBO. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

L1.1.5. Oral Presentations

Oral presentations will not be used for this solicitation.

L1.1.6 Communications

Exchanges of source selection information between Government and Offerors will be controlled by the PCO. E-mail may be used to transmit such information to Offerors only if the e-mail can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. Otherwise, source selection information will be transmitted via fax, USPS, FedEx, UPS, or pick-up by local representative, as appropriate.

L1.2 Organization/Number of Copies/Page Limits

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 1.2. The attachments identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

Table L1.2 - Proposal Organization

VOLUME
ITO Paragraph

Number

VOLUME TITLE
COPIES *
PAGE LIMIT
I
2.0
Executive Summary
Original +3

+ 1 CD-R/DVD-R

25 pages

II
3.0
Technical Volume

Written responses to task orders1

Original +3

+ 1 CD-R/DVD-R

200 pages total

3.2.6
Small Business Subcontracting and Participation Plan (Subfactor 4)
Original +3

+ 1 CD-R/DVD-R

No Limit

III
4.0
Past Performance
Original +3

+ 1 CD-R/DVD-R

See Para L4.0

IV
5.0
Cost/Price
Original + 3

+ 1 CD-R/DVD-R

No Page Limit

V
6.0
Contract Documentation
Original + 3

+ 1 CD-R/DVD-R

No Page Limit

1Responses to Task Orders will be used as evaluation data for subfactors

L1.2.1 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 excess paper copies will be returned to the Offeror as soon as practicable. 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, tables of contents, tabs, glossaries, acronym lists, lists of figures, resumes, letters of intent to accept employment, information regarding Potential Conflicts of Interest, and conflict of interest mitigation plans.

L1.2.1.1. 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. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

(b) Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and each 8.5 x 11 surface of a foldout shall be counted as a separate page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 9 point. These limitations shall apply to both electronic and hard copy proposals. Provide Microsoft Office Excel formulas in any spreadsheets.

L1.2.2 Cost or Pricing Related Data

(a) All cost or pricing data shall be addressed ONLY in the Cost/Price Proposal and Contract Documentation Volumes. Cost trade‑off information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade‑off decisions. Pricing information relative to the Small Business Subcontracting Plan may be addressed in the Small Business Subcontracting Plan, as necessary.

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

1. Data file should be submitted on a CD-R or DVD-R.

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

L1.2.3 Classified Information All proposals shall be unclassified. Classified addendums will not be accepted.

L1.2.4 Cross-Referencing

(a) 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. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

(b) Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

The Offeror shall provide a Solicitation Cross Reference Matrix indicating by ITO, PWS, paragraph number, the corresponding proposal paragraph in that section which addresses the referenced item.

L1.2.5 Indexing

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

L1.2.6 Glossary of Abbreviations and Acronyms

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

L1.2.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 book, clearly marked as to volume number, title, copy number, solicitation identification, and the Offeror's name. The same identifying data should be placed on the spine of each binder. 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. Any controlled unclassified information (CUI) incorporated into the proposal shall be marked accordingly.

L1.3 Electronic Offers

Offerors shall not submit proposals by e-mail. Proposals must be mailed or hand-carried and must be received at the address in Paragraph L1.4 by the time and date specified in this RFP. The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each CD-R/DVD-R the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. In addition to the hard copies, the Offeror shall submit all volumes in electronic format, using Windows compatible CD-Rs or DVD-Rs ONLY. Each volume shall be in a different directory on a CD-R/DVD-R. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2010 or earlier, MS Office Excel 2010 or earlier, MS Office Project 2010 or earlier, and MS Office Power Point 2010 or earlier, as applicable. In the event that hard copies and electronic copies of a proposal are submitted and if there are any discrepancies between the hard copies and the electronic copies of the proposal, the electronic copies will be used for evaluation.

L1.4. Distribution

The "original" proposal shall be identified. Proposals shall not be sent via e-mail. Proposals shall be addressed to the CO and mailed or hand carried to:

AFOTEC A-7K

ATTN: Linda Buix

REF: Solicitation FA7046-15-R-0001

1251 Wyoming Blvd SE

Kirtland AFB, NM 87117

L2.0 Volume I ‑ Executive Summary

In the executive summary volume, the Offeror shall provide the following information:

L2.1 Narrative Summary The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal. The narrative summary should be a "big picture" explanation and provide the Offeror’s overall approach and supporting rationale for the performance/management of the FTS requirements. Offerors shall provide an Organizational Chart or the Offeror’s proposed performance/management structure that defines the functional relationships, areas of responsibility, and lines of control/authority among the organizational elements, including proposed subcontractors and/or teaming members. The format of the Executive Summary is at the discretion of the Offeror. Within the Executive Summary, the Offeror shall state that its proposal is valid for 180 days beyond the due date.

L2.2 Table of Contents

Include a master table of contents of the entire proposal.

L3.0 Volume II - Technical Volume

L3.1 General The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. 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 not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

L3.2 Format and Specific Content

L3.2.1 Technical

(a) In the technical volume, address your technical solution for meeting or exceeding the Government’s minimum performance or capability requirements of each technical subfactor. The proposals should demonstrate your technical approach and qualifications to perform the Government’s requirements. Additionally, the proposals should describe how report requirements and any other pertinent information will be accomplished in accordance with each Task Order PWS identified.

(b) The Technical proposal shall consist of individual proposals for both of the Performance Work Statements (PWS) identified below:

Task Order Performance Work Statements:

Task Order 0001 – Planning (Sub-Factors 1 and 2)

Task Order 0002 – Test Execution (Sub-Factors 1 and 2)

Basic Performance Work Statement - Sub-Factors 3 and 4

Sub-Factors 1 and 2 address the performance of Task Orders 0001 and 0002, PWSs while Sub-Factors 3 and 4 address the performance of the Basic IDIQ PWS/contract.

L3.2.1.1 Technical Risk

Address Technical Risk associated with those aspects of your proposed technical approach you consider to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. Classify each risk in accordance with DoD Source Selection Procedures at http://www.acq.osd.mil/dpap/policy/policyvault/USA007183-10-DPAP.pdf (paste link into web browser), Table 3, Technical Risk Rating. Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: PWS or specification requirements), whether or not those requirements are identified as subfactors. Propose a realistic "work‑around" or risk mitigators for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation.

L3.2.2 Volume Organization

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

(1) Table of Contents

(2) List of Table and Drawings

(3) Glossary

(4) Cross Reference Matrix

(5) Subfactor One

(6) Subfactor Two (etc.)

(7) Risk Matrix

L3.2.3 SUBFACTOR 1: TECHNICAL SOLUTIONS

L3.2.3.1 Offeror’ s shall submit a written proposal detailing how their company shall meet the Government’s technical requirements for Task Order 0001 and Task Order 0002. The proposals need to demonstrate an understanding of AFOTEC core processes, understanding of operational test and evaluation, and a technically adequate approach for accomplishing the task order PWS technical requirements to include:

L3.2.3.1.1 Develop operational representative test scenarios and coordinate assets (to include defining range requirements, coordination with range resources and coordination and scheduling of operational test assets) to evaluate 5th generation fighter capabilities and determine effectiveness, suitability, and mission capability.

L3.2.3.1.2 Define requirements for mission level (man-in-the-loop, software-in-the-loop facilities such as ACS and the F-35 Joint Simulated Environment (JSE)) modeling and simulation and conduct VV&A activities.

L3.2.3.1.3 Modify or develop data analysis tools capable of high fidelity mission data reply, RMA (reliability, maintainability, availability) analysis, and supportability analysis (using any combination of aircraft M&S and/or range instrumentation truth data) to include applicable VV&A tools as required.

L3.2.3.1.4 Understand fighter operational test and evaluation process and methodologies, develop and perform a wide variety of analytical capabilities to support OT&E.

L3.2.4 SUBFACTOR 2: KNOWLEDGE AND EXPERIENCE

L3.2.4.1 Offeror’ s shall submit written documentation detailing their knowledge, experience, and currency in the core competencies required to meet the PWS requirements and Task Order 0001 and Task Order 0002 requirements.

OFFERORS SHALL NOT SUBMIT NAMES OF PROPOSED PERSONNEL IN ANY VOLUME OF THE PROPOSAL EXCEPT WHERE SPECIFICALLY INSTRUCTED. Competency areas to be addressed include:

L3.2.4.1.1 Breadth and currency of 4th and 5th generation fighter aircraft operational tactics, techniques and procedures (TTPs), maintenance and logistics TTPs, LO TTPs and instrumentation and real time/post flight data processing knowledge.

L3.2.4.1.2 Breadth and currency of advanced sensors (AESA radar, RF, EO, IR) and sensor fusion knowledge.

L3.2.4.1.3 Breadth and currency of system interoperability to include fighter datalinks in a net centric environment.

L3.2.4.1.4 Breadth and currency of Information Operations to include cybersecurity, information assurance and electronic warfare.

L3.2.4.1.5 Offeror shall provide qualifications of personnel deemed key/critical by the Offeror and how Offeror plans to fill these positions (DO NOT SUBMIT NAMES). If personnel to fill a key/critical position are either not currently employed by the Offeror or have not yet committed to employment, submit the qualifications from which the Offeror will recruit.

(1) Positions deemed key/critical by the Government and the qualifications for those positions are:

(a) Operations Subject Matter Expert (SME):

(1) Experience as a rated military aviator (pilot/navigator) is required to perform the duties of the position.

(2) Experience in aircraft test, either developmental test or operational test, as an aircrew member is highly desired.

(3) Previous experience as an instructor in a military aircraft is highly desirable.

(4) A master's degree in a related technical area (Engineering, Mathematics or Physics) is highly desirable. Other titles such as “Aircraft Engineering Technology”, “Aerospace Science”, “Technology” or “Aircraft” will not be considered a “related technical area.”

(5) Combat flight experience is highly desired.

(b) Engineer / Analyst SME:

(1) Knowledge of a wide range of qualitative and quantitative methods for the planning and assessment of operational tests for highly complex weapon systems and subsystems is required.

(2) A master's degree in a related technical area (Engineering, Mathematics or Physics) is highly desirable. Other titles such as “Aircraft Engineering Technology”, “Aerospace Science”, “Technology” or “Aircraft” will not be considered a “related technical area.”

(3) Experience in aircraft test, either developmental test or operational test, as an engineer/analyst is highly desired.

(4) Advanced knowledge of test and evaluation methodologies to develop and implement advanced or innovative modifications to standard accepted methods and practices of aircraft system testing, necessitated by unique limitations and requirements of operational testing is highly desired.

(5) Knowledge to design and conduct comprehensive test programs where the boundaries of the test are extremely broad and difficult to determine in advance is highly desired.

L3.2.5 SUBFACTOR 3: MANAGEMENT APPROACH

L3.2.5.1 This subfactor addresses the Offeror’s approach to program management and personnel. This section should provide insight into the Offeror’s capabilities and personnel practices to ensure successful support to the mission throughout the life of this contract and addresses the Offeror’s management approach to ensure full continuity of mission support and all services on the contract/task order performance start date. Provide, as specifically as possible, the actual methodology/approaches the Offeror would use for accomplishing/satisfying this subfactor. OFFERORS SHALL NOT SUBMIT NAMES OF PROPOSED PERSONNEL IN ANY VOLUME OF THE PROPOSAL EXCEPT WHERE SPECIFICALLY INSTRUCTED.

L3.2.5.1.1 Describe staffing requirements in numbers and labor categories.

L3.2.5.1.2 Provide a matrix showing proposed manning by labor category and hours for each task order period of performance.

L3.2.5.1.3 Identify those positions that are considered key/critical to successful mission performance and describe how these key/critical positions will influence mitigation of the program risks.

L3.2.5.1.4 Applicable to Task Orders 0001 and 0002, a Phase-In Plan which provides specific definition of how the risks associated with service transition will be addressed; especially during the phase-in period and first quarter thereafter. All costing data shall be embedded in the task order proposals, to be provided in Volume IV.

L3.2.5.1.5 State which personnel resources are currently employed or in place, or describe how the Offeror plans to acquire, manage, and retain personnel qualified to accomplish contract requirements. This discussion shall include, but is not limited to:

(a) How the Offeror plans to provide the initial base of qualified personnel. Specifically include estimated percentages of incumbent personnel retention, basis for the estimate, worst case percentage, and contingency for the worst case.

(b) The Offeror’s plans for personnel recruitment, both initially and throughout the contract life.

(c) How the Offeror plans to maintain a qualified base of personnel and to maximize talent as the contract matures. Specifically address plans for one-time training, recurring training, and cross-training.

(d) The Offeror’s overtime policies, bonuses, special leave incentives, and procedures to be used with this program. Address how these, or other, policies and procedures, will be used to ensure initiative, motivation, and high morale while minimizing personnel turnover.

(e) Evidence that all key/critical positions have back-up personnel capable of performing the tasks.

(f) Describe ability and process to meet surge and time-sensitive requirements.

(g) How the Offeror plans to meet personnel security clearance requirements.

(h) The Offeror’s proposed process of receiving, planning, coordinating, costing, and responding to task orders issued under this contract.

L3.2.5.1.6 Include an organizational chart and supporting narrative portraying the Offeror’s business (corporate) structure and the management office the Offeror proposes to establish to manage this contract.

L3.2.5.1.7 Define the direct lines of control, responsibilities, functional relationships, and authority between the management office and the Offeror’s other organizational elements.

L3.2.5.1.8 Describe all interfaces between the Offeror and the Government and between the Offeror and other contractors which are necessary and pertinent to the accomplishment of contractual tasks, projects, and programs.

L3.2.5.1.9 Explain the functional relationships among internal management operations, engineering, development and logistics support entities, as well as associated elements needed to successfully accomplish the program. If you are submitting your proposal as a team of companies (joint venture or significant subcontractors), explain the inter-company relationships as well as program placement and reporting relationships in each company involved.

L3.2.6 SUBFACTOR 4: SMALL BUSINESS SUBCONTRACTING AND PARTICIPATION PLANS

L3.2.6.1 Small Business Subcontracting Plan Offerors, unless otherwise exempt due to being a small business concern or a company performing outside of any State, territory, or possession of the United States, the District of Columbia, and the Commonwealth of Puerto Rico, shall, in accordance with FAR 19.7 and FAR 52.219-9 - Alternate II, and DFARS 252.219-7003, submit a Small Business Subcontracting Plan. If the Offeror is a participant in the Department of Defense (DoD) Comprehensive Subcontracting Test program specified in DFARS 219.7, the Offeror shall provide a copy of the approved comprehensive plan. Failure to submit and negotiate a subcontracting plan acceptable to the Contracting Officer shall make the offer ineligible for award of a contract. The same small business goals listed in the Small Business Participation Plan apply to the Small Business Subcontracting Plan.

L3.2.6.2 Small Business Participation Plan The Offeror shall submit a Small Business Participation Plan which will be used for the purposes of evaluating the extent to which offerors identify and commit to small business in contract performance on the FTS program. The plan will be incorporated into the resulting contract. The Participation Plan is required from all Offerors, including small businesses and companies with commercial subcontracting plans and comprehensive subcontracting plans.

L3.2.6.2.1 The following target small business participation goals are provided to assist in the development of your Small Business Participation Plan. The percentages are to be based on those subcontracting dollars awarded to the small business providing the technical requirements of the performance work statement, such as, but not limited to, test planning, test execution, test report writing, etc. and not for administrative/overhead purposes such as, but not limited to, travel agencies, clerical services, etc. First and second tier subcontracting dollars can be counted towards meeting your small business participation goals. Use of small business for administrative/overhead tasks may be identified as part of the Offeror’s overall approach but does not meet the intent of the solicitation to provide opportunities for small businesses with relevant technical capability.

Small Business - 17%

Small Disadvantaged Business - 5%

Woman-Owned Small Business - 5%

HUB Zone Small Business - 3%

Service-Disabled Veteran-Owned Small Business - 3% L3.2.6.2.2 ALL Offerors shall provide (1) through (3) below:

(1) A table which lists the following:

(a) All proposed first and second tier subcontractors, individually by name with their addresses,

(b) Subcontractor business type (large, small (SB), small disadvantaged businesses (SDB) to include Historically Black Colleges and Universities/Minority Institutions (HBCU/MI), women-owned (WOSB), Historically Underutilized Business Zone (HUB Zone), veteran-owned (VOSB), service-disabled veteran-owned (SDVOSB)), as determined by the SBA size standard for the specific work being subcontracted. List all applicable categories for each subcontractor.

(c) The principal service/supply being provided by the subcontractor.

(d) The complexity of the service/product provided. A brief narrative on complexity of subcontract services/products must describe:

Product: Complex performance specifications or stringent tolerances;

Services: Advanced professional skills or application of innovative technologies.

(e) Expected percentage of the contract

(2) A table which summarizes the total 1st and 2nd tier subcontract dollars proposed for each category of small business: SB, SDB, WOSB, HUBZone, VOSB and SDVOSB. Subcontractors that qualify for inclusion in more than one category shall be included in each category for which they qualify. For example, the value of subcontracts at both tiers to be awarded to a WOSB in a HUBZone shall be included in WOSB, HUBZone and SB totals.

(3) A copy of binding agreements and enforceable commitments executed with the firms identified in the table required by 3.2.6.2.2 above.

A sample of the table described in 3.2.6.2.2 is provided below:

Name of 1st and 2nd Tier Subcontractors
Sub- contractor Address
Type of Business (Large, SB, HUBZone, SDB, WOSB, VOSB, SDVOSB)
Principal Supply/Service Provided
Complexity of Product /Service Provided
Percentage of Contract
XYZ Corp.
123 Main St. Anytown, NY 01345
Large
Castings
Manufactured to .01 tolerance
15%
Acme, Ltd.
456 First Ave. Somewhere, NY 54321
SB, SDB, VOSB
Logistics software
Utilizing ISO 9000 and S100D Standards with XML
10%

Note 1: The System for Award Management (SAM) & Small Business Administration (SBA) Dynamic Small Business Search (http://www.sam.gov/ and http://dsbs.sba.gov/dsbs/search/dsp_dsbs.cfm) databases will be viewed to verify the small business category or categories of the proposed small businesses in the table. The Offerors shall list all applicable business types for which each subcontractor qualifies. The definition of a small business concern is as set forth in 13 CFR 121.105. The definition of “subcontract” is as set forth in FAR 19.701.

Note 2: The Small Business Participation Plan is in addition to, not in place of, the subcontracting plan. If a subcontracting plan is required, (See FAR 19.702.) the plan shall be submitted by the Offeror in accordance with FAR 52.219-9 – Alternate II stating cumulative subcontracting goals and for each option in dollars, percentages of total subcontracted amount and percentage of total contract value. (See AFFARS 5319.704(a)(1).)

Note 3: Offerors are reminded that in accordance with DFARS 215.304(c)(i) (C), the small businesses and HBCU/MIs considered in evaluation shall be listed in any subcontracting plan submitted pursuant to FAR 52.219-9 to facilitate compliance with DFARS 252.219-7003(g). In addition, all goals accepted and incorporated into the resulting contract will be subject to FAR Clause 52.219-16, “Liquidated Damages-Subcontracting Plan”, unless the Offeror is a participant in the Comprehensive Subcontracting Program.

Note 4: Offerors are reminded that the Small Business Subcontracting Plan (required from large businesses only) shall correlate with the proposal information on small business participation as well as all other sections of the proposal.

L3.2.6.3 Small Business Innovation The Offeror shall cite current and planned initiatives to assist, promote, and utilize all categories of small business in the Fighter Test Services program. Demonstrate examples of how the Offeror is maximizing Small Business (SB) opportunities and using SB in mission critical aspects (e.g. technology innovation) throughout the proposed program.

L4.0 Volume III - Past Performance

L4.1 General Each Offeror shall submit a past performance volume with its proposal, containing past performance information. This information is required on the Offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 10 percent or more of the proposed effort based on the total proposed cost 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.

Along with the information required in this paragraph, the Offeror shall submit a consent letter executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror so the Offeror can 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 on the Offeror's performance.

L4.2 Early Proposal Information

Each Offeror is requested to submit the information shown in Section L for each relevant contract 14 days prior to the date set for receipt of proposals. Failure to submit early proposal information will not result in Offeror disqualification.

L4.3 Relevant Contracts

Submit information in accordance with Attachment L1 Past Performance Information on recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort. Also include information on recent contracts performed by each of your teaming partners and significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. Include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M, provision M004 - Past Performance Factor.

L4.4 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. This may allow the Offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an Offeror has overcome past problems is required. Categorize the relevant information into the specific Technical subfactors and Cost/Price factor used to evaluate the proposal.

L4.4.1 Content of Past Performance Volume

For each proposal submitted, the Offeror’s Past Performance Volume shall contain the following and within the specified page constraints.

Item
Page Limit
Exclusions
Table of Contents Glossary
No Page Limit
None
Organizational Structure Change History
Three pages
Pre-published items such as brochures, flyers, reference article, etc. are excluded
Summary Page Describe the role of the Offeror and each subcontractor, teaming partner, and/or joint venture partner
Five pages
None
Past Performance Information Sheets
Five Pages (See L4.4.6)
None
Consent/Client Authorization Letters
No Page Limit
None
Relevancy matrix
Per format, as required, Attachment L6
None
List of Questionnaire Recipients
No Page Limit
None
Specific Content
One page
None

L4.4.2 Table of Contents The Table of Content shall list all documents contained in the Past Performance Volume.

L4.4.3 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 past efforts and this source selection. As a result, it is sometimes difficult to determine what 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 your company. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the Offeror(s), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

L4.4.4 Past Performance Summary

This summary shall describe the role and efforts to be performed by the Prime Offeror and each subcontractor/teaming member for which past performance information is provided.

L4.4.5 Determination of Responsibility Even though the assessment of Past Performance as a specific evaluation factor is separate and distinct from the Determination of Responsibility required by FAR 9.1, Responsible Prospective Contractors, information obtained as part of the proposal evaluation process will be used to support the Determination Responsibility for the successful Offeror(s).

L4.4.6 Past Performance Information Sheets A Past Performance Information Sheet is required on the Prime Offeror and each subcontractor/teaming member who will be completing 10% or more of the technical work of this acquisition. Offerors shall submit information on contracts they consider most relevant in demonstrating their ability to perform the proposed effort. Past performance on Indefinite Delivery Indefinite Quantity (IDIQ) type contracts/task orders shall be submitted according to the manner in which performance is formally assessed (e.g. per specific delivery/task order or for the IDIQ contract as a whole). For instances where performance is formally assessed for the IDIQ contract as a whole, the Offeror shall identify the single point of contact that can verify the Offeror's performance record under that IDIQ type contract. In instances where performance is not formally assessed at either level, Offerors shall submit past performance information at the delivery/task order level. Each delivery/task order submitted will be counted as one contract. Offerors shall include rationale supporting their assertion of relevance, but note the Government is not bound by the Offeror's opinion of relevancy. Clearly link the past performance information to the relevancy information specified in the Past Performance area of Section M. Offerors are required to explain what aspects of the contracts submitted for review are deemed relevant to the Fighter Test Services (FTS) effort. Where problems existed, clearly demonstrate what management actions were employed in overcoming the problems and the effect(s) those actions had rectifying the problem and improving performance.

The Offeror shall submit Performance Information Sheets in accordance with the format contained in Section L Attachment L1. The Offeror shall submit no more than a total of five Performance Information Sheets identifying active or completed contracts, either Government or commercial. Limits on Performance Information Sheets are as follows:

If subcontractors are to be used:

- Three (3) identifying active or completed contracts, either Government or commercial, for the prime, team, and/or joint venture (within the same division or cost center).

- Two (2) from each subcontractor who will be completing 10% or more of the technical work.

Each relevant contract shall have been completed or ongoing during the past three years from the date of issuance of this solicitation. Each Performance Information Sheet for each contract is limited to five pages, one page for the table and not to exceed two pages for the narrative portion. 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 and present performance.

L4.4.6.1 Alternate Past Performance Assessment Forms If an evaluation method other than a Past Performance Information Reporting System (PPIRS) has been used in conducting performance assessments (e.g. an Award Fee notification letter, a subcontractor’s prime contractor performance evaluation, etc.), this should be noted on the Past Performance Information Sheet submitted with the contract number, phone number and e-mail address of the individual that can be contacted to obtain this past performance information.

L4.4.7 Consent and Client Authorization Letters

Past Performance information concerning subcontractors/teaming members cannot be disclosed to a private party without the subcontractor’s or team member’s consent. Because the Offeror is a private party, the Government will need consent from the appropriate subcontract/teaming member before disclosing subcontractor/teaming member past performance information to the Offeror during any exchanges. In an effort to assist the Government in assessing the Offeror’s past performance record, a consent letter, similar to that included in Section L, Attachment L2, should be completed by each major or critical subcontractor/teaming member identified in the Offeror’s proposal. The completed consent letter(s) submitted as part of the Past Performance Information Volume will not be considered in the page count of that Volume. Should the Offeror not submit a completed consent letter for a major or critical subcontractor/teaming member, the Government will not disclose/discuss the applicable past performance information other than with that prospective subcontractor or teaming member being reviewed. If there is a concern with the proposed subcontractor’s/teaming member’s past performance, the Offeror can be notified, but no details may be discussed without the subcontractor’s or teaming member’s consent. For each identified effort for a commercial customer, the Offeror shall also submit a Client Authorization (Consent) Letter in Section L, Attachment L2, authorizing release to the Government the requested information on the Offeror’s performance.

L4.4.8 Recency and Relevancy of Past Performance Volume The Government will consider recency and relevancy of past performance. See Section M, Table 5, “Past Performance Relevancy Ratings”. Offerors shall include their rationale why the contract, or a specific portion of the contract submitted, is relevant for consideration in demonstrating their ability to perform an of the Fighter Test Services (FTS) requirements. The Government is not bound by the Offeror’s opinion of relevancy. The Government may contact references other than those identified by the Offeror, and use the information received, to evaluate the Offeror’s past performance. For the purpose of satisfying this requirement, types of past performance work that are essentially the same as this acquisition will be considered more relevant than types of work that are not as similar.

L4.4.9 Past Performance Questionnaire The Past Performance Questionnaire is included in Section L, Attachment L4. Although it will become part of the Past Performance content, the completed questionnaires shall not be submitted with the rest of the Past Performance Volume. The Offeror shall distribute the questionnaire to each point of contact (POC) listed on the Past Performance Information Sheets. A cover letter for transmitting the questionnaire to each POC is provided in Section L, Attachment L3. The Offeror shall exert its best efforts to ensure that there are at least two points of contact (PCO, Program/Project Manager, ACO, or equivalent) per relevant contract. Each of the POCs shall e-mail or fax the completed Present and Past Performance Questionnaire directly to the PCO’s attention (see paragraph 1.1). Responses routed through the Offeror will not be accepted. Mailing the questionnaire(s) is an acceptable alternative method of transmission. If mailing, the outside envelope must be marked with: “NOTE: TO BE OPENED BY ADDRESSEE ONLY.”

L4.4.8.1 Questionnaire Recipients

For each proposal submitted, Offerors shall provide a summary list of questionnaire recipients to include the POCs and phone numbers.

L5.0 Volume IV - Cost/Price

L5.1 General Instructions L5.1.1 Cost/Price Reasonableness and Realism

This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness and realism of your proposed cost/price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low or high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the Offeror does not understand the requirement or has submitted an unreasonable or unrealistic 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. The burden of proof for credibility of proposed costs/prices rests with the Offeror.

L5…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .