Amendment_0002.docx
DOCX document 61 KB Posted
- Attached to
- Sources Sought Notice
- Solicitation number
- FA4890-18-R-0006
About this file
Amendment 0002
View the file
Other files
Show all 32
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
FA489018R0006
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION SF 1449 - CONTINUATION SHEET
The following have been modified:
SECTION 6
SECTION 6 OF THE SOLICITATION – INSTRUCTIONS TO OFFERORS
52.215-1 INSTRUCTIONS TO OFFEROR – Competitive Acquisition (Jan 2017) FAR Clause 52.215-1(d) Offer expiration date. Proposals in response to this solicitation will be valid for 180 calendar days.
SECTION 6 – INSTRUCTION TO OFFERORS
SPECIAL NOTICES TO OFFERORS
This solicitation is to provide non-personal services for the follow-on EC-130H/A-10C Contract Aircrew Training (CAT) and Courseware Development (CWD) contract to include Instrument Refresher Course (IRC) for personnel in support of operations, as required, at Davis-Monthan Air Force Base (AFB), and Moody AFB. Additional CONUS locations may be required to support Continuation Training (CT) in the future which may include Distributed Mission Operations (DMO) training capability. If required, a modification to the contract will be accomplished.
Notice to Offerors: Funds are not presently available for this effort. No award will be made under this solicitation until funds are available. The Government reserves the right to cancel this solicitation, either before or after the closing date for receipt of proposals. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an Offeror for any costs incurred in the development of the proposal. This solicitation will not permit foreign contractor participation. Foreign contractors will not be permitted as the prime contractor due to the required security classifications. A non-US company cannot receive the required Top Secret Facility Clearance for this contract and thus are prohibited from submitting proposals.
Proprietary information submitted in response to this solicitation will be protected from unauthorized disclosure as required by Subsection 27 of the Office of Procurement Policy Act as amended (41 U.S.C.423) (hereinafter referred to as "the Act") as implemented in the FAR.
1.0 GENERAL INSTRUCTIONS
1.1 This section of the RFP provides general guidance for preparing proposals as well as specific instructions on the format and content of the required proposal volumes. Each proposal must include all data and information requested in the RFP. The offeror shall comply with the solicitation requirements as stated and the PWS. The offeror’s proposal must reflect a thorough understanding of the services required and display a logical development of the offeror's plans to implement all PWS requirements as assessed by the RFP evaluation criteria.
1.2 Efforts shall be made to keep offers as concise as possible with the emphasis being on providing information essential for proper evaluation. The proposal shall be clear, concise, and shall include sufficient detail to provide for adequate evaluation and for substantiation of the validity of stated claims. Submitted documents must contain adequate information to enable the evaluation team to fully ascertain an offeror's capability to perform contract requirements, must meet the requirements of the RFP, and must address the evaluation factors for award.
1.3 All information contained in the proposal an offeror feels is “Proprietary Information” and therefore not releasable under the Freedom of Information Act (FOIA), should be labeled “Proprietary Information, Source Selection Information—See FAR 2.101 and 3.104.”
1.4 In accordance with the Department of Defense Source Selection Procedures, dated 31 Mar 2016, past performance evaluation factor need not be evaluated if the PCO, after consultation with the SSA and PM, waives this requirement. The past performance evaluation factor has been waived by the PCO to assist with the efficiency of this requirement. The contractor base is known and the contracting officer, IAW FAR 9.105-2, will document and report past performance prior to award.
1.5 Offerors shall acknowledge awareness of all amendments to the solicitation by signing and dating Page 1 of each Standard Form 30, Amendment of Solicitation/Modification of Contract, and including it in Volume II, Price.
1.6 The Contracting Officer has determined there is a high probability of adequate price competition for this acquisition so offerors are cautioned to submit their best pricing and technical information up-front.
2.0 FORMAL COMMUNICATIONS
Any formal communication shall be submitted in writing (via email) to the POCs below. It is the offeror’s responsibility to confirm receipt of all formal communications.
ACC AMIC/PKB
Capt Hannah J. Kosirog (CO) hannah.kosirog.1@us.af.mil Ms. Susan L. Dunnigan (CM) susan.dunnigan@us.af.mil 129 Andrews Ave., Suite 110 Joint Base Langley-Eustis VA 23665-2788
Reference: Solicitation FA4890-18-R-0006
3.0 PRE-PROPOSAL CONFERENCE
The pre-proposal conference will be held at the 42nd ECS, 6020 E. Zapper Avenue, Davis-Monthan AFB, AZ 85756 on 9 May 2018 starting at 0900 hours local time. All potential offerors are encouraged to attend. Offerors desiring to attend the conference must pre-register no later than 7 calendar days prior to the conference. Offerors that do not pre-registered may not have access to the base/facilities. The Government reserves the right to cancel or reschedule the conference. The Government will not be liable for any expense incurred by offerors prior to contract award.
3.1 Registration. The number of attendees shall not exceed 3 per company or 5 per joint venture/partner arrangement. The registration information shall include the company name, individual name(s), phone number and social security number, and security clearance level of each attendee. This information is for security purposes and access to the base/facilities. The Government requests this information under the authority of 10 U.S.C. 8013. Offerors must submit their pre-registration notification by e-mail to Susan L. Dunnigan.
3.2 Advance Questions. Questions concerning this solicitation should be submitted under separate cover, clearly marked as "Advance Questions" to include solicitation number, name of person submitting the question(s), company name and phone number. Each question should reference the specific section, paragraph and/or attachment number of the solicitation or PWS (as applicable). These questions must be received by ACC AMIC/PKB, 9 calendar days prior to the Pre-Proposal Conference in order for an appropriate response to be given at the conference. Please submit your advance questions and registration information by email to Susan L. Dunnigan.
3.3 Remarks and Explanations. Remarks and explanations at the conference shall not alter the terms and conditions of the solicitation unless the solicitation is formally amended. Any oral statements by Government representatives shall not be binding upon the Government; the CO will make all necessary changes in writing via an amendment if required. If an offeror discovers discrepancies or omissions in any portion of the solicitation, the matter should be submitted in writing and provided to the CO as soon as the discrepancy is noted or not later than ten (10) days prior to the proposal due date.
4.0 SUBMISSION OF PROPOSALS
4.1 The original proposal and copies as specified in this document shall be sent to the issuing office listed in Block 9 of Standard Form (SF) 1449; on or before the date and time specified in Block 8 of SF1449.
Please mark all packages as follows:
DO NOT OPEN IN MAIL ROOM
ATTN: Capt. Hannah J. Kosirog and Ms. Susan L. Dunnigan
ACC AMIC/PKB
Solicitation No. FA4890-18-R-0006, Volume # and Title Note: If proposals are hand delivered, offerors shall contact the CM at 757-225-6037 to schedule delivery.
4.2 Offerors are cautioned to strictly comply with all instructions within this solicitation to ensure submission of a complete proposal. Failure to furnish a complete proposal at the time of proposal submission may result in the proposal being considered non-compliant to the Government and eliminated from consideration for award. Late proposals will be processed in accordance with FAR 52.212-1(f) “Late submission, modifications, revisions, and withdrawals of offers.” The Government will retain the unopened proposal. However, the proposal will not be evaluated or considered for award.
4.3 Contact Information. Offeror shall provide:
· Names, titles, addresses, telephone and email addresses of persons authorized to negotiate on the offeror’s behalf with the Government in connection with this solicitation.
· Name, title, and signature of person authorized to sign the proposal. Proposals signed by an agent shall be accompanied by evidence of that agent’s authority, even if that evidence has been previously furnished to the issuing office.
4.4 Disposition of Proposals. In compliance with FAR Subpart 4.8, the Government will retain one (1) copy of all unsuccessful proposals. Extra copies of unsuccessful proposals will be destroyed. No destruction certificate will be provided.
5.0 PROPOSAL PREPARATION INSTRUCTIONS
5.1 The following instructions prescribe the format for proposals, and describe the approach to be used for the development and presentation of the proposal data. The proposal shall include all of the information requested in the specific instructions. Failure to include all information requested may adversely affect the evaluation. A proposal that merely reiterates or promises to accomplish the requirements of the PWS will be considered unacceptable. A proposal that is orderly and sufficiently documented will enable the Government to easily understand the proposal and perform a thorough and fair evaluation of it. The Government may incorporate into the contract by reference or full text portions of the successful offeror’s proposal as revised and supplemented through the final proposal revision that is submitted in response to the solicitation.
5.2 Proposal Volumes. Proposals shall be prepared in two (2) separate and distinct volumes:
| Volume I – Technical |
| Volume II – Price |
5.3 Proposal Format. The proposal text shall be printed single-sided. Type size for text shall not be smaller than Microsoft Word Times New Roman 12 point font, single column, normal proportional spacing and one inch (1”) margins (top, bottom, left and right). The text for charts, tables, graphs, and figures shall be no smaller than Microsoft Word, Times New Roman or Arial Narrow, 8 point font. Text lines and table lines of text shall be single-spaced. Page color for each page of the proposal submission shall be white or ivory stock only. Information submitted shall not exceed the page limits stated below for each volume.
What Counts as a Page. A page shall be an 8 ½” x 11” sheet of paper. Fold-outs shall not exceed 11” x 17” and shall count as two (2) pages. Fold-outs shall be kept at a minimum, and shall be used only where a table or other graphic cannot be accommodated by a single 8-1/2” x 11” page. All material shall be contained within the page limit identified for each volume, and all appendices, charts, graphs, diagrams, tables, photographs, drawings, etc., are included in the page count, with exception of items stated in the next paragraph. Page numbering shall be in a sequential order (i.e., 1 through 75). Do not number each section of the proposal volume separately.
Pages Not Included in Page Count. The organizational chart, glossary of abbreviations, acronyms and cross-reference matrix will not be included in the page count. Covers for volumes, tables of contents, indices, title pages, and section dividers/tables will not be included in the page count if they are inserted solely to provide ease to the reader in locating parts/sections of the proposal. They will be counted if they contain any other information, e.g., diagrams, extraneous data, etc. Pages marked “This page intentionally left blank” and without any additional information will not be counted. Executive Summary will not be included in the proposal page limitation as stated in paragraph 5.5 below, and if applicable exceptions will be documented in each volumes executive summary and clearly marked as such.
5.4 Electronic Copies. Electronic copies of all proposal information for each volume shall be submitted on CD-ROM using Microsoft Office 2010 or later and/or Portable Document Format (PDF) using Adobe Acrobat 9.0 or later. Both volumes may be included on the same CD-ROM. Offerors shall not submit any documents in PDF that cannot be electronically searched. Offerors may use JPEG images for charts or screen shots. Volume II - Price shall be submitted in Microsoft Excel 2010 or later. Offerors shall name using standard naming conventions for each volume (e.g., Offeror name-volume name.docx). Each volume shall be contained in its own single searchable file, with copy/paste capability, and stored in a folder that corresponds to the proposal volume it represents. Offerors shall insert the file name in the header of each document. All disks shall be virus checked prior to submission. Replacement disks/CD ROM will be required to update the final proposal resulting from any discussions should they occur. It is the offeror’s responsibility to ensure that electronic copies and hard copies are an exact match. If there is a discrepancy between electronic copies and hard copies referenced in paragraph 5.5 below, the hard copy submission will be used to conduct evaluation.
5.5 Copies and Page Limits. Evaluators will only read up to the maximum number of pages specified. If the page limit is exceeded, the excess pages will be removed from the proposal and returned unread to the offeror. One copy of each Volume shall be marked “Original” and shall include a signature on the SF1449 in Volume II, Price. Copy requirements and page limitations are as follows:
| VOL |
| TITLE |
| PAPER COPIES |
| CD ROM |
| Page Limit |
| Due Date |
| I |
| TECHNICAL CAPABILITY |
| 8 |
| 1 |
| 75 |
| 31 May 2018 |
| II |
| PRICE2 |
| 3 |
| 1 |
| None |
| 31 May 2018 |
Notes:
1. An Executive Summary shall be included in Volume I, Technical – summary shall not exceed 3 pages. The 3 page limitation is not included in the 75-page limit for Volume I.
1. The Price Volume is for price only – Technical information shall not be included in this volume. The original, plus required copies shall be submitted IAW the instructions provided in paragraph 5.5 for evaluation. See paragraph 7.4 for requested Supporting Price Backup Data.
5.6 Cross-Referencing. Offerors shall not cross reference between Volumes I and II. Each Volume shall be written on a standalone basis so that its contents may be evaluated without cross-referencing to the other Volume of the proposal. NOTE: Information required for proposal evaluation, which is not found in its designated Volume, will be assumed to have been omitted from the proposal.
5.7 Exceptions. Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award. If the offeror finds it necessary to take exception to any of the requirements specified in this solicitation, the offeror shall clearly identify the applicable Volume and exceptions with a complete explanation of why the exception was taken, what benefit accrues to the Government (if any), and its impact, if any, on the performance, schedule, price and specific requirements of the solicitation. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Offerors are cautioned that taking an exception may render the offer ineligible for award. This information shall be provided in the format below.
Table 1 – Solicitation Exceptions
| Solicitation Document |
| Page/Paragraph |
| Requirement/Portion |
| Rationale & Impact |
| Contract Line Items section, PWS, Section 6 and Section 7, etc. |
| Applicable Page and Paragraph Numbers |
| Identify the requirement or portion to which exception is taken |
| Describe the rationale and impact of the exception |
5.7.1 If the offeror takes no exception to any of the stated requirements in the solicitation, a statement to this effect is required at the front of each proposal volume in the Executive Summary.
6.0 INSTRUCTIONS FOR VOLUME I -- TECHNICAL CAPABILITY (FACTOR I)
6.1 To facilitate the evaluation, the Technical Volume should be specific, detailed, and complete to clearly and fully demonstrate that the offeror has a thorough understanding of the requirements to accomplishment the effort. This volume of the proposal shall consist of the offeror’s technical approach, addressing risk management or mitigation strategies, if applicable. The offeror shall provide a clear and concise description of how the offeror plans to meet or exceed the requirements of the RFP, specifically identifying any innovations or efficiencies that would result in cost reductions, cost avoidance, or qualitative improvements resulting in a benefit to the Government in relation to the PWS and the technical evaluation subfactors. The Source Selection Authority, in consultation with the Source Selection Evaluation Team and advisors, is the sole arbiter of whether or not qualitative improvements represent a benefit to the Government. Statements that the offeror understands, can, or will comply with the PWS (including Air Force (AF) publications, technical requirements, etc.); statements paraphrasing the PWS or parts thereof (including applicable AF publications, technical data requirements, etc.); and phrases such as “standard procedures will be employed” or “well known techniques will be used” etc., will be considered unacceptable. Offerors should note that data submitted prior to the proposal submission including data submitted for current contracts and other solicitations will not be considered in the Government’s evaluation. Therefore, such data should not be relied upon nor incorporated in the Technical proposal by reference. Offerors shall address the requirements noted in this section by imperative verbs regardless of whether such requirements are preceded by “the offeror shall”. The offeror’s proposal shall, at a minimum, be prepared in a form consistent with the Technical Criteria set forth in Section 7, Evaluation Factors for Award, of this solicitation. All information that the offeror deems appropriate to address for this factor and subfactors must be included in the proposal in an orderly format. The Technical Volume shall address all the technical subfactors. This section shall not contain any pricing data.
6.2 Technical Contents
A. Table of Contents. A table of contents shall be included in Volume I. Each subfactor, aspect, and section will be clearly marked and tabbed for easy reference and pages shall be numbered in a consistent/sequential manner as stated under Proposal Preparation Instructions, paragraph 5.3.
B. Glossary of Abbreviations and Acronyms. Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each.
C. Executive Summary. Included in this volume is the offeror’s Executive Summary (limit is 3 pages). It should include a concise summary of the offeror’s proposed approach to the EC-130H/A-10C CAT/CWD effort.
D. Technical Factor Cross Reference Matrix. The offeror shall fill out the Technical cross reference matrix indicating the proposal reference information as it relates to the RFP, PWS, and CLIN references found therein. See Appendix 1 and paragraph 5.6 for instruction on cross-referencing. PWS paragraph references are cited regarding aspects of the subfactors. These paragraph references are not however, exclusive, and offerors must thoroughly review the complete PWS.
SUBFACTOR A: Human Resource Management. Under this subfactor, the Government will evaluate three (3) aspects:
Aspect I – Manning Workload Analysis
a) Demonstrates a detailed CAT manning workload analysis that clearly explains all proposed manning, manning mix (including number of personnel per position), full and part-time employees (if used), for CAT instruction and management at each site. Your CAT man year calculations will include all direct, indirect and ancillary time; scheduled leave, holidays and any other workload capability. The analysis should show how offeror arrived at proposed manpower ensuring all PWS requirements are met. (IAW PWS Appendix 1)
b) Demonstrates a detailed flying contractor manning workload analysis that clearly explains all proposed manning, manning mix (including number of personnel per position), full and part-time employees (if used) for flying aircrew instruction. Your flying aircrew instructor man year calculations will include all direct, indirect and ancillary time; scheduled leave, holidays and any other workload capability. The analysis should show how offeror arrived at proposed manpower ensuring all PWS requirements are met. (IAW PWS Appendix 1)
c) Presents a detailed courseware (CWD) manning workload analysis for all courseware requirements. Explain the proposed manning and manning mix, including number of personnel per position. Explain the proposed development time in hours for each lesson instructional hour, providing a percentage breakdown of each proposed courseware skill for each type of courseware, and clearly identified proposed manpower for each skill to meet all PWS requirements. (IAW PWS Appendix 1)
d) Demonstrates a clear understanding of formal training unit support positions (schedulers and registrar) workload and proposed manning meets PWS requirements. (IAW PWS Appendix 1)
e) Demonstrates a detailed programmer/work group manager manning workload analysis that clearly explains all proposed manning, manning mix, full and part-time employees (if used). Your man year calculations will include all direct, indirect and ancillary time; scheduled leave, holidays, and any other workload capability. The analysis should show how offeror arrived at proposed manpower ensuring all PWS requirements are met. (IAW PWS Appendix 1)
Aspect II – Training Workload Management Plan
a) Clearly demonstrates methods, innovations and policies which ensure all required work is accomplished IAW the PWS, paragraph 1.9.13.
b) Demonstrates effective processes for daily and long range scheduling that mitigate risk associated with workload fluctuations or other factors to ensure all PWS work is accomplished. (IAW PWS 1.6.3 & 1.6.4)
Aspect III – Recruitment, Training and Retention Plan
a) Provides an effective and comprehensive recruitment plan that ensures sufficient, qualified personnel are hired for each position and specifically identifies and addresses contract instructor positions that may be hard to fill. (IAW PWS 1.9.14)
b) Clearly explains how the offeror will train and certify new personnel and provides a plan for training new instructors if Government training resources are not available. (IAW PWS 1.9.1)
c) Provides an effective and comprehensive retention plan to retain sufficient, qualified personnel for each position and specifically identifies and addresses contract instructor positions that may be hard to fill. (IAW PWS 1.9.14)
SUBFACTOR B: Organizational and Functional Management. Under this subfactor, the Government will evaluate four (4) aspects:
Aspect I – Organizational Structure
a) Demonstrates an effective organizational structure detailing contractor’s line(s) of authority to include subcontractors and/or teaming partners.
Aspect II – Roles, Responsibilities and Communications
a) Demonstrates cohesive functional relationships and effective roles and responsibilities that will ensure effective communication procedures both within the company and with the government representatives to effectively execute the PWS requirements.
b) Provide an effective and comprehensive plan to meet requirements for contract flying defined in
DCMA INST 8210.1C. (IAW PWS 1.9.1.1. & 1.9.6.1.)
Aspect III – Transition Plan
a) Demonstrates a thorough understanding of all transitions requirements and identifies priority allocation of resources and personnel. (IAW PWS 1.7.3)
b) Identifies risk factors and plans for mitigating any identified risk.
c) Provides a spreadsheet that clearly depicts all Phase In actions with appropriate start and completion dates which ensures the offeror is prepared on the contract start date.
d) Clearly explains how the incoming contractor shall interface with Government personnel in a manner that minimizes disruption of student training activities.
e) Clearly explains how the contractor shall ensure continuity of services in the event the incumbent does not receive the follow-on award. (IAW PWS 1.7.3.)
f) Clearly explains how the contractor shall provide for a smooth/ uninterrupted transition of the incumbent personnel if the incoming contractor wants to retain such personnel. (IAW PWS 1.7.3.)
Aspect IV – Instructor Training and Certification Plan
a) Demonstrates a thorough understanding of instructor qualification requirements for each major block of training to be instructed, qualification/evaluation performed before a previously qualified instructor instructs, and written notification of each instructors’ qualifications for conducting unmonitored student instruction. (IAW PWS 1.7.3.1)
b) Clearly explains all ISD training accomplished to personnel supporting the CWD effort. (IAW PWS 1.5.2. and Attachment 1, para A1.2.11.)
c) Clearly explains the re-qualification process/procedures when an instructor is de-certified or goes non-current. (IAW PWS 1.9.4 & 1.9.5)
SUBFACTOR C: IT Systems Approach and Management. Under this subfactor, the Government will evaluate four (4) aspects:
Aspect I – Learning Management System (LMS) and SLATE
a) Demonstrates a detailed approach that describes how you will provide an internet based knowledge portal which manages courseware to include; reviews, scheduling, publishing, inventory, critiques, master test database and other academic material for the EC-130H/A-10C community. (IAW PWS 1.7.5.)
b) Demonstrate how your LMS will be operational 24 hours a day, 7 days a week, 365 days a year except when down for scheduled maintenance. (IAW PWS 1.7.5)
c) Demonstrates processes to ensure LMS format and internet processes are standardized across all work locations and available to all FTUs and associated squadrons.
d) Demonstrate your approach for network operating maintenance that ensures capability sufficient to support the database and meet computer network requirements of all users. (IAW PWS 1.7.5)
e) Describe in detail how access of unclassified material will be accomplished through a portal on the FTU/TRSS unclassified LAN and all classified material is located on a classified server that can be accessed via the SIPRNET web page with PASSWORD controls. This includes a central pubs/scenario SharePoint for worldwide A-10C access. (IAW PWS 1.7.5.1/ 1.7.8.)
f) Describe how LMS software/licenses (if required), computers and appropriate servers are approved and online and available for use at all sites on the contract start date and all systems and operations are in compliance with all Government Security regulations. (IAW PWS 1.7.5.)
g) Describe in detail how you will establish a service (SLATE) to provide secure, application based, push-technology access to all course material and scheduling via a handheld wireless device. (IAW PWS 1.7.7.)
Aspect II – Brief/Debrief (WEdge) and BRI
a) Demonstrates a detailed approach that describes how you will manage the internet based brief/debrief (WEdge) system and the BRI system for the EC-130H/A-10C community. (IAW PWS 1.6.8 and 1.7.5).
Aspect III – Electronic Grade Book (EGB)
a) Demonstrates a detailed approach that describes how you will manage an internet based EGB for the EC-130H/A-10C community. Demonstrate how your EGB will be operational 24 hours a day, 7 days a week, 365 days a year except when down for scheduled maintenance. Describe in detail how access of EGB will be available to all students/instructors on and off-base. (IAW PWS 1.7.5.)
Aspect IV: Contractor Furnished Equipment
a) Demonstrates that proposed CFE is compliant with the Air Force Network Integration Center approved product list. (IAW PWS 3.5.2)
b) Demonstrates that proposed CFE is sufficient to meet all PWS requirements. (IAW PWS 3.5.)
7.0 INSTRUCTIONS FOR VOLUME II -- PRICE PROPOSAL (FACTOR 3)
7.1 The offeror shall complete Section 3 of the solicitation (Schedule of Supplies and Services (CLINS)) by inserting the price elements (unit price and extended amount) for all Firm Fixed Price (FFP) contract line item numbers (CLINS), including Phase-In, Base Year, Option Years, and Optional CLINs. For ease of administration, all TOTAL pricing should be rounded to whole dollar amounts and divisible by 12. The solicitation will provide pre-established NTE amounts for the Fixed Price Travel CLINs that will become part of the total evaluated price for all offerors.
7.2 Complete in its entirety the "Offeror" portion of the Standard Form 1449. An official having authority to legally bind the company contractually must sign and date the Standard Form 1449. One copy of the Standard Form 1449 must bear an original signature and if applicable, all amendments. Failure to acknowledge any amendment(s) to the solicitation can result in an offeror being deemed non-compliant. Note: Be sure to sign and date where required.
7.3 Representations and Certifications. Complete the required Representations and Certifications or indicate if information is contained in the System for Award Management (SAM) located at https://www.sam.gov.
7.4 Supporting Price Backup Data for Prime and Subcontractors. Certified cost or pricing data is not required. However, supporting data is requested to verify that pricing is balanced per FAR 15.404-1(g). Supporting data should explain the methodology used in developing proposed CLIN prices. Supporting data shall be provided in a table format, to include, at a minimum, a breakdown (by CLIN) of labor (labor category, number of positions and productive hours and rates used), breakout of Other Direct Costs (ODC), Direct and Indirect Rates, and Subcontract costs. Supporting data may be submitted in a format selected by the offeror, but must address the information requested in this paragraph. The Government reserves the right to request additional pricing information after receipt and evaluation of proposals.
8.0 DEBRIEFING OF OFFERORS
8.1 Debriefings are conducted with the goal of identifying to unsuccessful offerors where changes can be made to improve future source selection participation.
8.2 Successful or unsuccessful offerors may request debriefings by providing a written request to the Procuring Contracting Officer. Debriefings shall be conducted in accordance with FAR 15.505 for pre-award debriefings and FAR 15.506 for post-award debriefings.
9.0 RESPONSIBILITY DETERMINATION
9.1 For the purposes of making a determination of contractor responsibility, past performance information may be obtained from sources such as the Government’s Past Performance Information Retrieval System (PPIRS), the Defense Contract Management Agency, interviews with Program Managers, COs, and Award Fee Determining Officials, and other sources known to the Government. The Government reserves the right to obtain more past performance data from any source that it deems appropriate.
Appendix 1 to Section (6)
Technical Factor Cross-Reference Matrix
As part of Offerors’ proposals, a separate cross-reference matrix shall be completed and submitted with Volume I, Technical. The cross-reference matrix below is to assist in the proposal preparation process. Offerors shall complete the last column of this attachment with paragraph number references, including all subsequent subparagraphs (for example, 5.0 includes 5.1, 5.2, 5.2.1, etc.) from their Technical Volume. Offerors may provide additional references to the other columns as deemed necessary. Offerors are ultimately responsible for ensuring that their proposal fully addresses all areas and that all requested information is completed in accordance with this solicitation.
TECHNICAL FACTOR CROSS REFERENCE MATRIX
| Subfactors |
| Reference |
| Service Summary Item |
| Section 6 |
| Section 7 |
| Technical Proposal Paragraph(s) |
Subfactor A: Human Resource Management
Aspect I: Manning Workload Analysis
Aspect II: Training Workload Management Plan
Aspect III: Recruitment, Training and Retention Plan
Subfactor B: Organizational and Functional Management
Aspect I: Organizational Structure
Aspect II: Roles, Responsibilities and Communications
Aspect III: Transition Plan
Aspect IV: Instructor Training and Certification Plan
Subfactor C: IT Systems Approach and Management
Aspect I: Learning Management System and SLATE
Aspect II: Brief/Debrief (WEdge) and BRI
Aspect III: Electronic Gradebook (EGB)
Aspect IV: Contractor Furnished Equipment
SECTION 7
SECTION 7 of the Solicitation – EVALUATION FACTORS FOR AWARD ADDENDUM to 52.212-2 EVALUATION – COMMERCIAL IT ITEMS (Oct 2014)
BASIS OF AWARD
1. This competitive best value source selection will be conducted using the Tradeoff source selection process in accordance with (IAW) Federal Acquisition Regulation (FAR) Part 15, Contracting by Negotiation, Department of Defense (DoD) Source Selection Procedures effective 31 Mar 2016 and Air Force Federal Acquisition Regulation Supplement (AFFARS) Mandatory Procedures 5315.3 as revised 3 Oct 2017. The Government will award one contract resulting from this solicitation to the responsible (IAW FAR Part 9) offeror whose offer conforming to the solicitation will be most advantageous to the Government, price and other factors considered.
2. Factor ratings and assessments will focus on each proposal’s technical strengths, deficiencies, weaknesses, risk and price analysis findings. This may result in an award being made to a higher rated, higher priced offeror where the decision is consistent with the evaluation factors and the Source Selection Authority (SSA) determines that the technical superiority of the higher priced offeror outweighs the price difference. The SSA bases the source selection decision on an integrated assessment of the evaluation factors and subfactors. While the Government evaluation team and the SSA will strive for maximum objectivity, the source selection process, by its nature, is subjective; therefore, professional judgment is implicit throughout the entire process.
3. As set forth in Section 6, the Government intends to award without discussions IAW FAR 52.215-1 (except clarifications as described in FAR 15.306(a)). The Government may make a final determination as to whether the offeror’s proposal is the best value solely on the basis of the initial proposal as submitted. Accordingly, offerors are advised to submit initial proposals that are fully and clearly acceptable without additional information. Should the Government determine it is in their best interest to open and conduct discussions, discussion will be held only with those offerors determined to be in the competitive range. The competitive range will be comprised of the most highly rated proposals based on the ratings of each offeror’s technical and price proposals.
4. If the Government holds discussions, the Government may issue evaluation notices to offerors in the competitive range. Formal responses to evaluation notices and final proposal revisions will be considered in making the source selection decision for award.
5. Final Proposal Revisions (FPRs) will be requested from each offeror in the competitive range at the conclusion of discussions. Any revision or non-concurrence to contract terms and conditions submitted in the submitted FPR will not be subject to further discussion or negotiation. This provision is not intended to restrict the offeror’s opportunity to revise figures (e.g., prices, discounts, percentages, rates, etc.); rather, it is intended to preclude any misunderstandings by the Government which could result if new or revised terms and conditions are submitted in the FPR that have not been fully disclosed, discussed and understood during discussions. Hence, such new or revised terms and conditions are not solicited and, if submitted in the FPR, may render the offer unacceptable to the Government.
EVALUATION FACTORS AND METHODOLOGY
1. Proposals will be evaluated using three (3) Factors which are as follows: (1) Technical Capability (2) Risk, (3) Price. In terms of the hierarchy of importance, Technical Capability is most important and significantly more important than Risk and Price. Risk is less important than technical but more important than Price. Price is the least important factor. However, the greater the equality of technical proposals the more important Price becomes in selecting the best value for the Government. Furthermore, there are three subfactors within the Technical Capability Factor: (A) Human Resource Management, (B) Organizational and Functional Management, and (C) IT Systems Approach and Management. Subfactor (A) is significantly more important than subfactors (B) and (C). Subfactors (B) and (C) are equally important.
2. As a basis for award, price is of the least importance. Therefore, the Government reserves the right to award to other than the lowest proposed price. Price is not the most significant factor in the selection of an offeror for this solicitation; however, the degree of importance of price as a factor could become greater depending upon the equality of the proposals for the other factors evaluated. However, the greater the equality of technical proposals the more important Price becomes in selecting the best value for the Government. Prices will be evaluated to determine if the proposed price is reasonable and to assess the offeror’s understanding of the solicitation. Any inconsistency, whether real or apparent, between technical and price must be clearly explained in the price proposal. For example, if unique and innovative approaches are the basis for an abnormally priced cost estimate, the nature of these approaches and their impact on price must be completely documented. The burden of proof of price credibility rests solely with the offeror. Price proposals will not be rated or scored. The Government will make a subjective evaluation to determine if the offeror’s technical approach and proposed price represents the greatest value to the Government.
EVALUATION FACTORS
A) FACTOR 1 – TECHNICAL CAPABILITY
1. The technical capability subfactors shall receive a separate technical and risk rating in conjunction with the strengths, weaknesses, significant weaknesses and deficiencies in the offeror’s proposal.
Technical Rating. The offeror’s technical solution will be rated separately from the risk associated with its technical approach. The technical rating evaluates the quality of the offeror’s technical solution for meeting the Government’s requirements. If an offeror’s proposal demonstrates a material failure to meet a Government requirement, this is a deficiency in the offeror’s proposal resulting in a Red/Unacceptable rating and the proposal is not awardable. The severity of the deficiency will determine if the offeror will be able to correct the deficiency through discussions. Technical ratings will be assessed at the subfactor level; an overall factor-level rating will not be assigned. The definitions for technical ratings are IAW Table 2A of the DoD Source Selection Procedures and are listed below.
TABLE 2A
TECHNICAL CAPABILITY RATING
COLOR
RATING
ADJECTIVAL
RATING
DESCRIPTION
| Blue |
| Outstanding |
| Proposal indicates an exceptional approach and understanding of the requirements and contains multiple strengths. |
| Purple |
| Good |
| Proposal indicates a thorough approach and understanding of the requirements and contains at least one strength. |
| Green |
| Acceptable |
| Proposal indicates an adequate approach and understanding of the requirements. |
| Yellow |
| Marginal |
| Proposal has not demonstrated an adequate approach and understanding of the requirements. |
| Red |
| Unacceptable |
| Proposal does not meet requirements of the solicitation and, thus, contains one or more deficiencies and is unawardable. |
2. The following are the Technical Capability subfactors:
Subfactor A: Human Resource Management. Under this subfactor, the Government will evaluate three (3) aspects:
Aspect I – Manning Workload Analysis
a) Demonstrates a detailed CAT manning workload analysis that clearly explains all proposed manning, manning mix (including number of personnel per position), full and part-time employees (if used), for CAT instruction and management at each site. Your CAT man year calculations will include all direct, indirect and ancillary time; scheduled leave, holidays and any other workload capability. The analysis should show how offeror arrived at proposed manpower ensuring all PWS requirements are met. (IAW PWS Appendix 1)
b) Demonstrates a detailed flying contractor manning workload analysis that clearly explains all proposed manning, manning mix (including number of personnel per position), full and part-time employees (if used) for flying aircrew instruction. Your flying aircrew instructor man year calculations will include all direct, indirect and ancillary time; scheduled leave, holidays and any other workload capability. The analysis should show how offeror arrived at proposed manpower ensuring all PWS requirements are met. (IAW PWS Appendix 1)
c) Presents a detailed courseware (CWD) manning workload analysis for all courseware requirements. Explain the proposed manning and manning mix, including number of personnel per position. Explain the proposed development time in hours for each lesson instructional hour, providing a percentage breakdown of each proposed courseware skill for each type of courseware, and clearly identified proposed manpower for each skill to meet all PWS requirements. (IAW PWS Appendix 1)
d) Demonstrates a clear understanding of formal training unit support positions (schedulers and registrar) workload and proposed manning meets PWS requirements. (IAW PWS Appendix 1)
e) Demonstrates a detailed programmer/work group manager manning workload analysis that clearly explains all proposed manning, manning mix, full and part-time employees (if used). Your man year calculations will include all direct, indirect and ancillary time; scheduled leave, holidays, and any other workload capability. The analysis should show how offeror arrived at proposed manpower ensuring all PWS requirements are met. (IAW PWS Appendix 1)
Aspect II – Training Workload Management Plan
a) Clearly demonstrates methods, innovations and policies which ensure all required work is accomplished IAW the PWS paragraph 1.9.13.
b) Demonstrates effective processes for daily and long range scheduling that mitigate risk associated with workload fluctuations or other factors to ensure all PWS work is accomplished. (IAW PWS 1.6.3 & 1.6.4)
Aspect III – Recruitment, Training and Retention Plan
a) Provides an effective and comprehensive recruitment plan that ensures sufficient, qualified personnel are hired for each position and specifically identifies and addresses contract instructor positions that may be hard to fill. (IAW PWS 1.9.14)
b) Clearly explains how the offeror will train and certify new personnel and provides a plan for training new instructors if Government training resources are not available. (IAW PWS 1.9.1)
c) Provides an effective and comprehensive retention plan to retain sufficient, qualified personnel for each position and specifically identifies and addresses contract instructor positions that may be hard to fill. (IAW PWS 1.9.14)
Subfactor B: Organizational and Functional Management. Under this subfactor, the Government will evaluate four (4) aspects:
Aspect I – Organizational Structure
a) Demonstrates an effective organizational structure detailing contractor's line(s) of authority to include subcontractors and/or teaming partners.
Aspect II – Roles, Responsibilities and Communications
a) Demonstrates cohesive functional relationships and effective roles and responsibilities that will ensure effective communication procedures both within the company and with the government representatives to effectively execute the PWS requirements.
b) Provide an effective and comprehensive plan to meet requirements for contract flying defined in
DCMA INST 8210.1C. (IAW PWS 1.9.1.1. & 1.9.6.1.)
Aspect III – Transition Plan
a) Demonstrates a thorough understanding of all transition requirements and identifies priority allocation of resources and personnel. (IAW PWS 1.7.3)
b) Identifies risk factors and plans for mitigating any identified risk.
c) Provides a spreadsheet that clearly depicts all Phase In actions with appropriate start and completion dates which ensures the offeror is prepared on the contract start date.
d) Clearly explains how the incoming contractor shall interface with Government personnel and incumbent contractor in a manner that minimizes disruption of student training activities.
e) Clearly explains how the contractor shall ensure continuity of services in the event the incumbent does not receive the follow-on award. (IAW PWS 1.7.3)
f) Clearly explains how the contractor shall provide for a smooth/ uninterrupted transition of the incumbent personnel if the incoming contractor wants to retain such personnel. (IAW PWS 1.7.3.)
Aspect IV – Instructor Training and Certification Plan
a) Demonstrates a thorough understanding of instructor qualification requirements for each major block of training to be instructed, qualification/evaluation performed before a previously qualified instructor instructs, and written notification of each instructors’ qualifications for conducting unmonitored student instruction. (IAW PWS 1.7.3.1)
b) Clearly explains all ISD training accomplished to personnel supporting the CWD effort. (IAW PWS 1.5.2. and Attachment 1, para A1.2.11)
c) Clearly explains the re-qualification process/procedures when an instructor is de-certified or goes non-current. (IAW PWS 1.9.4 & 1.9.5)
Subfactor C: IT Systems Approach and Management. Under this subfactor, the Government will evaluate four (4) aspects:
Aspect I – Learning Management System (LMS) and SLATE
a) Demonstrates a detailed approach that describes how you will provide an internet based knowledge portal which manages courseware to include; reviews, scheduling, publishing, inventory, critiques, master test database and other academic material for the EC-130H/A-10C community. (IAW PWS 1.7.5.)
b) Demonstrate how your LMS will be operational 24 hours a day, 7 days a week, 365 days a year except when down for scheduled maintenance. (IAW PWS 1.7.5)
c) Demonstrates processes to ensure LMS format and internet processes are standardized across all work locations and available to all FTUs and associated squadrons.
d) Demonstrate your approach for network operating maintenance that ensures capability sufficient to support the database and meet computer network requirement of all users. (IAW PWS 1.7.5)
e) Describe in detail how access of unclassified material will be accomplished through a portal on the FTU/TRSS unclassified LAN and all classified material is located on a classified server that can be accessed via the SIPRNET web page with PASSWORD controls. This includes a central pubs/scenario SharePoint for worldwide A-10C access. (IAW PWS 1.7.5.1/ 1.7.9.)
f) Describe how LMS software/licenses, if required, computers and appropriate servers are approved and online and available for use at all sites on the contract start date and all systems and operations are in compliance with all Government Security regulations. (IAW PWS 1.7.5.)
g) Describe in detail how you will establish a service (SLATE) to provide secure, application based, push-technology access to all course material and scheduling via a handheld wireless device. (IAW PWS 1.7.7.)
Aspect II – Brief/Debrief (WEdge) and BRI
a) Demonstrates a detailed approach that describes how you will manage the internet based brief/debrief (WEdge) system and the BRI system for the EC-130H/A-10C community. (IAW PWS 1.6.8 and 1.7.5).
Aspect III – Electronic Grade Book (EGB)
a) Demonstrates a detailed approach that describes how you will manage an internet based EGB for the EC-130H/A-10C community. Demonstrate how your EGB will be operational 24 hours a day, 7 days a week, 365 days a year except when down for scheduled maintenance. Describe in detail how access of EGB will be available to all students/instructors on and off-base. (IAW PWS 1.7.5.)
Aspect IV – Contractor Furnished Equipment
a) Demonstrates that proposed CFE is compliant with the Air Force Network Integration Center approved product list. (IAW PWS 3.5.2)
b) Demonstrates that proposed CFE is sufficient to meet all PWS requirements. (IAW PWS 3.5.)
B) FACTOR 2 – TECHNICAL RISK
Technical Risk Rating. Assessment of technical risk considers the risk associated with the technical approach to meeting the Government’s requirements which is manifested by the identification of weakness(es) and deficiencies, considers potential for disruption of schedule, increased cost or degradation of performance, the need for increased Government oversight, and/or the likelihood of unsuccessful contract performance based on the offeror’s identified approach and/or processes. In conducting the risk assessment, the Government will also consider information provided by the offeror in its proposal as to how the contractor will manage and mitigate risk. Technical risk shall be rated using the ratings listed in Table 2B of the DoD Source Selection Procedures. Ratings will be assessed at the subfactor level and overall factor-level rating will not be assigned.
TABLE 2B
TECHNICAL RISK RATING
ADJECTIVAL RATING
DESCRIPTION
| Low |
| Proposal may contain weakness(es) which have little potential to cause disruption of schedule, increased cost or degradation of performance. Normal contractor effort and normal Government monitoring will likely be able to overcome any difficulties. |
| Moderate |
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.