AIS_Section_L_Amend_01.pdf
PDF 298 KB Posted
- Attached to
- Maintenance, Repair, and Rebuilding of Equipment
- Solicitation number
- FA8251-17-R-0055
View the file
Other files
| File | Type | Posted |
|---|---|---|
| FA825117R0055_______0001.pdf | ||
| AIS_Section_M_Amed_01.pdf | ||
| Question_and_Answers_Post_RFP_Release_19_Oct.pdf | ||
| Question_and_Answers_Post_RFP_Release.pdf | ||
| FA825117R0055.pdf | ||
| Question_and_Answers_Posted_to_FBO_17_Aug_2017.pdf | ||
| Question_and_Answers_-_Posted_to_FBO_24_July_2017.pdf | ||
| Question_and_Answers_Posted_to_FBO_11_July_2017.pdf | ||
| Question_and_Answers_Posted_to_FBO_15_June_2017_V2.pdf | ||
| Question_and_Answers_Posted_to_FBO_15_June_2017.pdf | ||
| Quality_Assurance_Surveillance_Plan_Final_1.pdf | ||
| Question_and_Answers.pdf | ||
| FA825117R0055.pdf | ||
| AISSectionL.docx | DOCX document | |
| USAFSampleTask.docx | DOCX document | |
| F16AISProductSupportIntegrationPWS.docx | DOCX document | |
| AISCDRL.docx | DOCX document | |
| AISLaborMaterialRatesWorksheet.xlsx | XLSX spreadsheet | |
| APPENDIXC.docx | DOCX document | |
| AISSectionM.docx | DOCX document | |
| FMSSampleTask.docx | DOCX document |
Show all 21
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
Section L - Page 1 of 16
Section L – Instructions, Conditions, and Notifications to Offerors (ITO)
Instruction Criteria
For the
Avionics Intermediate Shop (AIS) / Product Support Integration (PSI) Program
March 2017
Section L - Page 2 of 16
SECTION CONTENT
1 – Program Structure and Objectives
2 – General Instructions
3 – Volume I – Executive Summary
4 – Volume II – Price
5 – Volume III – Technical
6 – Volume IV – Contract Documentation
7 – Attachments
1. PROGRAM STRUCTURE AND OBJECTIVES
1.1. The objective of this effort is to provide AIS/PSI support for the F-16 aircraft in accordance with (IAW) the requirements specified within the Performance Work
Statement (PWS).
1.2. To assure timely and equitable evaluation of proposals, offerors shall follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including all stated terms, conditions, representations, certifications, and technical requirements, in addition to those identified as evaluation factors or sub-factors.
Proposals shall consist of four (4) separate volumes; Volume I – Executive Summary, Volume II - Price, Volume III – Technical; and Volume IV – Contract Documentation.
2. GENERAL INSTRUCTIONS
2.1. This section provides general guidance for preparing proposals as well as specific instructions on format and content. The offeror's proposal shall include all data and information requested and shall be submitted in accordance with these instructions. Any offeror who submits an incomplete package may be eliminated from the competition.
The offer shall be compliant with the requirements as stated in the Performance Work
Statement (PWS), Contract Data Requirements Lists (CDRLs), and Model Contract /
Solicitation. Non-conformance with these instructions may result in an unacceptable proposal evaluation.
2.2. Include Sufficient Detail: The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal shall 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 proposal.
2.3. Embellishments Not Desired: Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.
Section L - Page 3 of 16
2.4. Proposals Acceptance and Validity Dates: The proposal acceptance period is specified on the first page of the solicitation. The Offeror shall make a clear statement on the front page of the contract documentation volume (Volume IV) that the proposal is valid through this date. The proposal acceptance period is specified in Block 11 of Standard
Form (SF) 1447 Model Contract/Solicitation. Offerors providing less than the specified calendar days for Government acceptance after the date offers are due, may be considered grounds for elimination.
2.5. Disposition of Proposal: In accordance with FAR Subpart 4.803(a), the Government will retain one (1) copy of all proposals. Unless the Offeror requests otherwise (in their proposal), the Government will destroy extra copies of the successful and unsuccessful proposals.
2.6. Past Performance: Past Performance will not be evaluated.
2.7. Points of Contact: The Contracting Officer (CO) and the Contract Negotiator are the sole points of contact for this acquisition. Address any questions or concerns you may have to the CO and Contract Negotiator. All questions and answers shall be sent through the Prime Offeror. Written requests for clarification may be sent to the CO at the address below:
Contracting Officer:
AFSC OL:H/PZABB
ATTN: Aaron Velasco, Capt, USAF
6050 Gum Lane, Bldg. 1215
Hill AFB, UT 84056
Office (801) 586-2122
Aaron.velasco@us.af.mil
Contract Negotiator:
ATTN: Rustin Miller
6050 Gum Lane, Bldg. 1215
Hill AFB, UT 84056
Office (801) 586-6899 rustin.miller@us.af.mil
2.8. Pre Award Debriefings: The CO will promptly notify offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing in accordance with FAR 15.505.
2.9. Post Award Debriefings: The CO 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 mailto:Aaron.velasco@us.af.mil mailto:rustin.miller@us.af.mil
Section L - Page 4 of 16 desiring debriefing must make their request in accordance with the requirements of FAR
15.505 or 15.506, as applicable.
2.10. Discrepancies: If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the
CO in writing with supporting rationale. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussions.
2.11. Electronic Reference Documents: All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at http://www.fedbizopps.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.
2.12. Oral Presentation: Oral presentations will not be allowed.
2.13. Communications: Exchanges of source selection information between Government and
Offerors will be controlled by the Contracting Officer. Email may be used to transmit such information to Offerors. The PCO may determine to conduct telephone exchanges when deemed appropriate by the Government.
2.14. Amendments to Solicitation: If this Request for Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged. Offerors shall acknowledge receipt of any amendment by the date and time specified on the front page by signing and returning the front page of each amendment.
2.15. Submission, Modification, Revision, and Withdrawal of Proposals
2.15.1. Proposals and modifications to proposals shall be submitted in both paper and electronic media to the address:
ATTN: Aaron Velasco, Capt, USAF
6050 Gum Lane, Bldg. 1215
Hill AFB, UT 84056
2.15.2. All submissions shall show the time and date specified for receipt, the solicitation number, and the name and address of the offeror. Late proposals will only be considered IAW FAR 15.208.
http://www.fedbizopps.gov/
Section L - Page 5 of 16
2.15.3. Acceptable evidence to establish the time of receipt at the Government installation includes the time/date stamp of that installation on the proposal wrapper, other documentary evidence of receipt maintained by the installation, or oral testimony or statements of Government personnel.
2.15.4. Proposals may be withdrawn by written notice received at any time before award.
Proposals may also be withdrawn in person by an offeror or an authorized representative, if the identity of the person requesting the withdrawal is established and the person signs a receipt for the proposal before award.
2.16. Organization/Number of Copies/Page Limits: The title page of each volume must show:
- Solicitation Number
- Company name, address, cage code and DUNS
- Primary point of contact name, telephone number and email address
- Volume number and name (e.g. Volume I, Price) and copy number (i.e.
Original, copy 1, copy 2, etc.)
2.16.1. The offeror shall prepare the proposal as set forth in the Proposal Organization table 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 specified. The volumes identified in the table shall be separately bound in three-ring, loose-leaf binders.
Table 1 - Proposal Organization
VOLUME SECTION L
PARAGRAPH
TITLE COPIES PAGE LIMIT
I 3.0 Executive
Summary
Original plus 1
Hardcopy, and 1 CD
10 pages
II 4.0 Price Original plus 1
Hardcopy, and 2 CDs
Unlimited
III 5.0 Technical Original plus 4
Hardcopies, and 4 CDs
200 pages
IV 6.0 Contract
Documentation
Original plus 1
Hardcopy, and 1 CD
Unlimited
2.17. Page Limitations: Page limitations shall be treated as maximum and are explained in
Table 1 – Proposal Organization. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal; rather, the Offeror will be notified of which pages of the proposal were determined excess as soon as practical. Page
Section L - Page 6 of 16 limitations may be placed on responses to Evaluation Notices (ENs) if applicable. The specified page limits for EN responses will be identified in the letters forwarding the
ENs to the offerors. Each page shall be counted except the following: blank pages, title pages, tables of contents, tabs, Glossary of Abbreviations and Acronyms, Cross
Reference Matrix, and those noted in the Proposed Organization Table as “Unlimited.”
2.18. Pricing Information: All pricing information shall be addressed ONLY in the Price
Volume (Volume II).
2.19. Cross Referencing
2.19.1. Each volume (I - IV) of the Offeror’s proposal shall be submitted, evaluated, and considered based solely on the information contained therein (i.e. each volume
“stands-alone”). Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal.
2.19.2. The offeror shall fill out the cross reference matrix IAW Table 2 – Sample Cross
Reference Matrix. The Cross Reference Matrix shall be included in the
Technical Volume (Volume III). The cross reference matrix addresses each requirement within the PWS, Section L, and Section M factors and sub-factors.
The offeror shall fill-in each section independently labeled with the appropriate paragraph number or page number that addresses the requirement or sub-factor.
Table 2 – Sample Cross Reference Matrix
Section L Section M PWS Technical
Volume
Para. X.x. Para. X.x. Para. X.x. Para. X.x.
2.20. Indexing
2.20.1. Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.
2.20.2. Include an indexed list of Tables and Figures.
2.20.3. Glossary of Abbreviations and Acronyms – Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each.
2.21. Page Size and Format
Section L - Page 7 of 16
2.21.1. 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.
Pages shall be typed using single spacing, except for the reproduced sections of the solicitation document and contractor deliverable plans, for which the CDRL
Data Item Descriptions state shall be prepared in contractor formatting.
• Page size shall be 8.5 by 11 inches (foldouts must fold into no larger than 11 by 17 inches).
• Foldouts shall be considered as two pages
• The text size shall be no less than 12 point in Times New Roman typeface except for tables, charts, graphs and figures.
• For tables, charts, graphs and figures, the text shall be no smaller than 8 point font.
• Use at least 1 inch margins on the top and bottom and 3/4 inch side margins.
• Pages shall be numbered sequentially by volume—including response to ENs
• These limitations shall apply to both electronic and hard copy format.
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. These limitations shall apply to both electronic and hard copy proposals.
2.22. Binding and Labeling: The three-ring loose leaf binders used to contain the proposal information shall permit the volumes to lie flat when open. Staples shall not be used. A cover sheet should preface each volume, 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. Since classified information shall not be provided in the proposal, all 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 IAW FAR 52.215-1(e), Restriction on Disclosure and Use of
Data, and FAR 3.104-5, Disclosure, Protection, and Marking of Contractor Bid or
Proposal Information and Source Selection Information.
2.23. Electronic Offers: The content and page size of electronic copies must be identical to the hard copies. In the event there is a discrepancy between the hard copy and electronic copy, the hard copy shall take precedence for all volumes and elements of the proposal other than the TEP Workbook. The soft copy of the TEP Workbook will be the only version used during the evaluation. For electronic copies, indicate on each CD the volume number and title. Use separate files for each volume to permit rapid location of all portions, including sub-factor required plans, exhibits, annexes, and attachments, if any. The offeror shall submit Volumes II and III in electronic format, using read only CDs (i.e. CD-R). Re-writable CDs (i.e. CD-RW) WILL NOT BE
READ, EVALUATED, OR CONSIDERED. Each volume shall be on a separate CD.
Section L - Page 8 of 16
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) Word 2010, MS Excel 2010, and MS-Power Point 2010, as applicable. PDF formats shall NOT be used. Word documents – Set “save as type” to “Word Document
(*.docx)” only. Excel spreadsheets – Set “Save as type” to Microsoft Excel Workbook
(*.xlsx)” no hidden or locked cells. PowerPoint presentation – Set “Save as type” to
“Microsoft PowerPoint 2010 Presentation (*.pptx).”
2.24. Distribution: The "original" proposal shall be so designated and signed by the Offeror's authorized representative, and the "copies" should be identified appropriately. All requested copies must be received by the due date identified on the front page of the
RFP. Proposals shall be addressed to the PCO and delivered to:
OL:H/PZABB
Attn: Aaron Velasco, Capt, USAF
6050 Gum Lane, Bldg. 1215
Hill AFB, UT 84056
3. VOLUME I – EXECUTIVE SUMMARY
Executive Summary Volume Organization: The Executive Summary shall be organized according to the following outline:
1. Table of Contents
2. Authorized Offeror Personnel POCs
3. Government Office POCs
4. Company Address, Cage Codes, and Applicable Designations
In the executive summary volume, the Offeror shall provide the following information:
3.1. Table of Contents: Provide a master table of contents for the entire proposal.
3.2. Authorized Offeror Personnel: Provide the name, title, telephone number, and email address of the company/division point of contact regarding decisions made with respect to the Offeror's proposal and who can obligate (as to this proposal) the Offeror's company/firm contractually. Also identify those individuals authorized to negotiate with the Government.
3.3. Government Office: Provide the mailing address, telephone number, email address, and facility code for the cognizant Contract Administration Office, Defense Contract Audit
Agency (DCAA), and Government Paying Office for the Offeror's company/firm. Also provide this information for the Administrative Contracting Officer (ACO).
Section L - Page 9 of 16
3.4. Company/Division Address, Identifying Codes, and Applicable Designations; and verifications:
(a) Offeror shall provide company/division's street address, county and facility code; CAGE code; DUNS code; and labor surplus area designation. This same information must be provided if the work (for completing what is proposed) will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.
(b) Offeror shall provide verification that unlimited/unrestricted rights IAW DFARS 252.227-
7013 or 252.227-7015 apply for all required technical data deliveries, since such deliveries are either (1) necessary for operation, maintenance, installation, or training (other than detailed manufacturing or process data) or (2) funded completely by the Government under this contract, or both.
4. VOLUME II – PRICE (Factor One)
Volume Organization: The Price Volume shall consist of the following sections:
1. Table of Contents
2. Pricing information and supporting data, to include estimating methodology
3. Glossary
4.1. General: The price evaluation criteria consists of: (1) Price Reasonableness, (2) Balance,
(3) Total Evaluated Price (TEP), and (4) Evaluation of Compensation for Professional
Employees. Offerors shall review Section M criteria to ensure the minimum requirements are met.
4.1.1. Total Evaluated Price: The TEP will be assessed from the Offeror’s information provided in this volume. The burden of proof for credibility of proposed prices rests with the Offeror.
4.1.1.1. Offerors shall input fixed composite labor rates (for both Government Site and Contractor Site) and material burden rates for all categories and years identified in the TEP Workbook IAW the instructions contained therein.
Submit a copy of the completed TEP Workbook in the Price Volume
(Volume II) in Microsoft Excel format (non-PDF).
4.1.1.2. Composite labor rates shall be fully burdened to include all direct labor, fringe, indirect rates (Overhead, General and Administrative, etc.), profit, and
Facilities Capital Cost of Money (if applicable) necessary for the performance of the entire requirement. Base and fringe rates shall be provided per labor category to facilitate the Evaluation of Compensation for
Professional Employees (see 4.1.2).
Section L - Page 10 of 16
4.1.1.3. Composite material burden rates shall include all costs other than direct material costs to include indirect rates (Overhead, General and
Administrative, etc.), profit, and Facilities Capital Cost of Money (if applicable) necessary for the performance of the entire requirement.
4.1.2. Evaluation of Compensation for Professional Employees: The offeror shall submit a professional employee compensation plan meeting the requirements of
FAR 52.222-46.
4.1.3. Approved Accounting and Purchasing Systems: As portions of this contract will be other-than fixed price, the Offeror must provide evidence of an approved accounting and purchasing system for themselves and any subcontractors who will be issued other-than fixed price subcontracts. The offeror shall indicate whether the accounting or purchasing systems are Government approved and if so, provide evidence of such approval.
4.2. Pricing Assumptions: Summarize all significant pricing assumptions, scope limitations and/or qualifications of the Price Volume.
4.3. Estimating Techniques and Methods: Estimating methods used in the proposal shall be described in a manner that will show clear traceability into the proposed pricing throughout the Price Volume. Indicate whether you have Government approval of your estimating system and if so, provide evidence of such approval.
4.4. Pricing Information Requirements: In the event that adequate competition does not emerge in response to the solicitation, the PCO may require submission of certified cost and pricing data, and a Certificate of Current Cost or Pricing Data (IAW FAR 15.403-4).
IAW FAR 15.403-1(b) and 15.403-3(a), information other than certified cost or pricing data may be required to support price reasonableness. If, after receipt of proposals, the
PCO determines that there is insufficient information available to determine price reasonableness the Offeror shall be required to submit other than certified cost or pricing data; if none of the exceptions in FAR 15.403-1 apply, the Offerors may be required to submit certified cost or pricing data. Information shall be provided in format that is IAW
FAR 15.403-5.
4.5. Price Information: Information beyond that required by this instruction shall not be submitted, unless Offeror considers it essential to document or support their price position. All information relating to the proposed price including all required supporting documentation must be included in the Price Volume and Contract Document Volumes.
Under no circumstances shall this information and documentation be included elsewhere in the proposal.
5. VOLUME III – TECHNICAL (Factor Two)
Section L - Page 11 of 16
Technical Volume Organization: This Volume shall be organized according to the following general outline:
1. Table of Contents
2. List of Tables and Drawings
4. Technical Approach
5.1. General: The Technical Capability Volume shall be specific and complete. Legibility, clarity and coherence are very important. Your responses will be evaluated against the
Technical Sub-factors defined in Section M. Offerors should review Section M criteria to ensure the minimum requirements are met. In addition, offerors should provide as specifically as possible the actual methodology that would be used for accomplishing/satisfying each sub-factor. It is imperative that you fully describe how you will meet the sub-factor requirements. Do not simply copy and paste, rephrase or restate PWS/Technical Order language for the technical volume. The provided sample tasks are for evaluation purposes only and are not awardable.
5.2. Factor Two – Technical
5.2.1. Sub-factor One, Sample Task One (USAF): The Offeror shall submit the following information in response to satisfy Sample Task One – see Section L, Attachment 1.
5.2.1.1. ATE Hardware: evidence that material is sourced from correct OEM, evidence of an Obsolescence Mitigation process that identifies all tasks, a
Delta Function Configuration Audit, and evidence of a process to analyze predicted assembly failure data with the function of developing changes to
Operational Readiness Spares Kit and Depot Readiness Spares Kit.
5.2.1.2. ATE Software: evidence of approach to perform integration, qualification testing of replacement parts, development, and delivery of modified Control and Support (C&S) software to enable on-system testing of replacement assemblies.
5.2.1.3. TPS Software: evidence of approach for software integration reflects minimizing impacts to existing F-16 Test Program Sets (TPS) Software, identifies redlines for TPS software, and documentation for affected TPS programs (System Test Specification [STS] Vol I & Vol II).
5.2.1.4. Integration: evidence of approach to perform integration and qualification testing of replacement parts to ensure the IAIS/VXI-IAIS/R-IAIS configurations execute TPS(s) as outlined in the Test Plan. In addition, identifies all parties/organizations, their required function, and explains the
Section L - Page 12 of 16 process of de-conflicting potential C&S and TPS Software discrepancies in order to complete integration.
5.2.1.5. Data Requirements: show approach to develop a Test Plan, approach to develop all required Field Service Bulletins, and show that ATE data to be updated includes the following: specifications, Technical Orders, engineering data, provisioning documentation, and Calibration and
Measurement Requirements Summary (CMRS).
5.2.1.6. Program Management: evidence of a Program Management approach that adheres to the PWS PMP (para 4.2.1.2) and satisfies this Sample Task One to include addressing AIS hardware, software, and data management IAW a
Configuration Management Plan that satisfies Sample Task One. Additionally, the offeror’s Master Schedule will be reviewed for evidence of incorporating necessary milestones and technical reviews that are required to satisfy Sample
Task One.
5.2.1.7. Contract Data Requirements: evidence that 100 percent of Sample Task One’s
CDRLS are present and accurate.
5.2.1.8. Quality Assurance / Certifications: evidence of utilization of a quality system such as International Organization for Standardization (ISO) 9001:2008 as a means of ensuring that the requisite quality assurance oversight is exercised in fulfilling the requirements of this effort. Additionally, Capability Maturity
Model Integration (CMMI) Level 3 Certification shall be appraised and maintained at Level 3 throughout the duration of this effort.
5.2.2. Sub-factor Two, Sample Task Two (FMS): The Offeror shall submit the following information in response to satisfy Sample Task Two – Attachment 02:
5.2.2.1. ATE, ATE spares, and SERD Hardware: evidence that material is sourced from correct OEM(s), properly configured for use with R-IAIS end items, risk mitigation approach for obsolescence issues, method of handling & incorporating Commercial-Off-The-Shelf (COTS) items, method of
Acceptance Test Procedures (ATP), approved means of shipping & transportation procedures.
5.2.2.2. ATE Hardware: Identification of correct ATE and ancillary Support
Equipment part numbers and quantities, acceptable approach for the sourcing and identification of required ATE spares, evidence of approved means of
Installation and Check-Out (ICO) procedures.
5.2.2.3. SERD Hardware: Identification of correct part numbers, quantities, and GFE.
Section L - Page 13 of 16
5.2.2.4. ATE and TPS Software: evidence of approach for production and development. Specifically for TPS Software, evidence of proper integration within subsystems and systems of IAIS/VXI-IAIS/R-IAIS systems, TPS software is sourced correctly, approved Acceptance Test Procedures, software delivery requirements are identified and correct.
5.2.2.5. ATE Data Requirements: ATE Data to be updated is identified and defined.
5.2.2.6. SERD Data Requirements: identification of SERD Data to be updated is addressed to include: Technical Order updates, LM Aero Managed Technical
Orders, Automated Technical Order System (ATOS) managed Technical
Orders, SERD updates ACPINs updates.
5.2.2.7. Program Management: evidence of a Program Management approach that adheres to the PWS PMP (para 4.2.1.2) and satisfies this Sample Task Two to include addressing AIS hardware, software, and data management IAW a
Configuration Management Plan that satisfies Sample Task Two.
Additionally, the offeror’s Master Schedule will be reviewed for evidence of incorporating necessary milestones and technical reviews that are required to satisfy Sample Task Two.
5.2.2.8. Contract Data Requirements: evidence that 100 percent of Sample Task Two’s
CDRLS are present and accurate.
5.2.2.9. Quality Assurance / Certifications: evidence of utilization of a quality system such as International Organization for Standardization (ISO) 9001:2008 as a means of ensuring that the requisite quality assurance oversight is exercised in fulfilling the requirements of this effort. Additionally, Capability Maturity
Model Integration (CMMI) Level 3 Certification shall be appraised and maintained at Level 3 throughout the duration of this effort.
5.2.3. Sub-factor Three, Program Management Plan (PMP): The Offeror shall submit a
PMP that provides information on the offeror’s organization, practices, techniques to be used in managing the program, and includes a Transition Plan that meets the requirement to have operational control of this acquisition within
45 days after contract award (IAW PWS, para 4.2.1.3). At a minimum, the following needs to be provided:
5.2.3.1. Necessary equipment and facilities ready for use within the 45-day transition period
5.2.3.2. Necessary Personnel are (or will be) employed, trained, and able to work accordingly to satisfy the AIS requirements within the 45-day transition period
Section L - Page 14 of 16
5.2.3.3. Process to ensure accountability of GFP/GFE (IAW PWS, para 3.1)
5.2.3.4. Identification of key personnel positions and how they will be phased-in for each of their respective areas. Key personnel positions are identified in the
PWS, Attachment 1.
5.2.3.5. Diminishing Manufactured Sources and Material Shortages (DMSMS)
Management Plan: The Offeror shall provide a detailed DMSMS approach that provides methodologies, rationale, and evidence to demonstrate that they will support this requirement and be IAW PWS para 4.2.4. This DMSMS approach will be general in nature to the AIS requirement and not be particular to a National Stock Number (NSN) or Technical Order (TO). The
Offeror shall state how the following work will be accomplished:
5.2.3.5.1. Identify and manage the loss, or impending loss, of manufacturers or suppliers of parts
5.2.3.5.2. Identify material required for sustained operational availability of the
AIS System to include ATE and TPS system components
5.2.3.5.3. Identify both the reactive and proactive obsolescence management processes that will be used for DMSMS Management process
6. VOLUME IV – CONTRACT DOCUMENTATION
1. Table of Contents
2. Model Contract/Representations and Certifications
6.1. Model Contract/Representations and Certifications: The purpose of this volume is to provide information to the Government for preparing the contract document and supporting files.
6.2. Complete blocks 13 and 27 of the RFP Section A. In doing so, the Offeror accedes to the contract terms and conditions as written in the RFP Section A through K. Sections A through J constitute the model contract. Offerors shall include signatures on all amendments associated with the RFP.
6.3. Section B – Supplies or Services and Costs/Prices: Do not input pricing information in
Section B of the model contract. All required proposed prices shall be stated in the TEP
Workbook.
6.4. Section K – Representations, Certifications, and other Statements of offerors: Complete representations, certifications, acknowledgments and statements. Offeror must have filled out an online FAR clause 52.204-8 Annual Representations and Certifications (Jan
Section L - Page 15 of 16
2017), Online Reps and System at System for Award Management
(http://www.sam.gov). Offer shall ensure certification as a small business under NAICS
541330 – Engineering Services (Military and Aerospace Equipment and Military
Weapons).
6.5. Exceptions to Solicitation Requirements – 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 sub-factors. Failure to meet a requirement may result in an offer being ineligible for award.
Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken.
Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 3.
Table 3 – Solicitation Exceptions
6.6. Other Information Required
6.6.1. Ability to obtain resources – Submit evidence that your company possesses adequate financial resources to perform the contract. This information will be used as part of the Contracting Officer’s determination of responsibility IAW
FAR 9.104.
6.6.2. Offeror shall provide a Subcontracting Plan – If the Offeror is other than a small business, the Offeror shall submit a Small Business Subcontracting Plan in accordance with FAR 52.219-9, Small Business Subcontracting Plan that separately addresses and specifies the extent of Offeror's commitment to the participation of Small Businesses (SB), Veteran-Owned Small Business (VOSB), Service Disabled Veteran-Owned Small Business (SDVOSB), HUBZone Small
Business (HUBZONE), Small Disadvantaged Business (SDB), and with Woman-
Owned Small Business (WOSB) concerns with a separate part with the basic contract and separate part for each option (if any). The plan shall be included in and made a part of the resultant contract. Failure to submit and negotiate the subcontracting plan shall make the offeror ineligible for award of contract. If applicable, submit a copy of your approved master plan. In the event the offeror has negotiated a comprehensive subcontracting plan pursuant to DFARS
SOLICITATION
Document
Page/
Paragraph
Requirement/
Portion
Rationale
SOO, PWS, SPEC,
Model Contract, ITO, etc.
Applicable Page and Paragraph
Numbers
Identify the requirement or portion to which exception is taken
Describe why the requirement can/will not be met
Section L - Page 16 of 16
219.702, the small business contracting program, statutory requirements, the offeror must submit the information that identifies and specifies the extent of their commitment to the participation of SB, VOSB, SDVOB, HUBZONE, SDB and WOSB. These targets will be provided in the small business subcontracting plan IAW FAR 52.219-9.
6.6.3. Submit evidence that your company, along with all teaming partners/ interdivisional transfers/subcontractors who will be issued other-than fixed price work, has an adequate accounting system.
6.6.4. Teaming arrangement – The teaming arrangement must consist of a prime contractor (who will be the sole point of contact, and have overall responsibility for the contract) and any subcontractor whose technique, capability, certifications, or qualifications are used in the technical proposal.
6.6.5. Offeror shall submit evidence of a signed formal agreement between the prime contractor and any other contractors listed in the teaming arrangement. The agreement must provide evidence that it will be valid beginning on the date of contract award. Additionally, the general roles and responsibilities of the applicable member of the teaming arrangement shall be listed in each individual agreement. This agreement does not preclude offerors from adding team members after contract award. Failure to provide this agreement may be considered grounds for elimination and therefore ineligible for award.
6.6.6. Offeror shall submit evidence of a valid U.S. security clearance of Secret or
Higher in order to respond to this RFP: FA8251-17-R-0055. All classified material must be handled in accordance with the National Industrial Security
Program Operating Manual (NIPSOM) (DoD 5220-22-M) and Industrial
Security Regulation (DoD 5220.22-R).
7. SECTION L – ATTACHMENTS
ATTACHMENT 1: Sample Task 1 – USAF
ATTACHMENT 2: Sample Task 2 – FMS
File details come from the government source that posted it.