Attachment 2_ATSSI II Section L.docx

DOCX document 517 KB Posted

Attached to
Automated Test System Sustainment Initiative II (ATSSI II)
Solicitation number
FA8224-20-R-0009
Issued by

About this file

This document provides instructions for proposals in response to a solicitation for the Automated Test System Sustainment Initiative II contract. Offerors must submit proposals by the closing date in four volumes: Volume I (Technical Approach), Volume II (Past Performance), Volume III (Cost/Price), and Volume IV (Contract Documentation).

Volume I requires information on the offeror's technical proficiency, including documentation and drawing examples, quality certifications, and descriptions of their approaches to small business participation, industrial process control, risk mitigation, program management, and sample task orders. Volume II requires past performance questionnaires for up to three relevant contracts. Volume III requires a completed Total Evaluated Price matrix specifying fully burdened labor rates by category and year. Volume IV includes contractual representations and certifications. The solicitation is issued by the Department of the Air Force Materiel Command Air Force Sustainment Center for automated test services at Hill Air Force Base over a potential nine-year period.

View the file

Other files

File Type Posted
Solicitation Amendment FA822420R00090004 SF 30.pdf PDF
Solicitation Amendment FA822420R00090001 SF 30.pdf PDF
Attachment 4_ATSSI II TEP Matrix 20 Jul 2020.xlsx XLSX spreadsheet
FA8224-20-R-0009 FINAL RFP QA Matrix 17July2020.xlsx XLSX spreadsheet
Solicitation Amendment FA822420R00090002 SF 30.pdf PDF
Solicitation Amendment FA822420R00090003 SF 30.pdf PDF
Attachment 3_ATSSI II Section M Rev01 - 21 Jul 2020.docx DOCX document
Attachment 2_ATSSI II Section L Rev01 - 21 Jul 2020.docx DOCX document
Attachment 1_ATSSI II PWS - 21 Jul 2020.docx DOCX document
Attachment 1_ATSSI II PWS - 15 Jul 2020.docx DOCX document
FA8224-20-R-0009 FINAL RFP QA Matrix - 15 Jul 2020.xlsx XLSX spreadsheet
ppi tool link.docx DOCX document
Attachment 2_ATSSI II Section L.docx DOCX document
Solicitation - FA822420R0009 30 June 2020.pdf PDF
Attachment 7- DD 254.pdf PDF
Attachment 4_ATSSI II TEP Matrix.xlsx XLSX spreadsheet
Attachment 1_ATSSI II PWS.docx DOCX document
Attachment 5_ATSSI II Technical Sample Task Order SOO.docx DOCX document
Attachment 6_ATSSI II Awardable Program Management Sample Task Order SOO.docx DOCX document
Attachment 3_ATSSI II Section M.docx DOCX document
Exhibit A_B_C_D - ATSSI II CDRL Package (X001-X042).pdf PDF
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

Appendix II: Cross Reference Matrix

Section L Instructions to Offerors

Automated Test System Sustainment Initiative II

(ATSSI II)

3 June 2020

ATSSI II: Section L

Table of Contents

SECTION L4
1.0PROPOSAL FORMAT4
1.1General4
1.2Communications4
1.2.1Exchange of Information5
1.2.2Submission, Modification, Revision, and Withdrawal of Proposals5
1.2.3Debriefings5
1.2.4Discrepancies5
1.2.5Amendments to Solicitation6
1.3Volume Organization6
1.3.1General6
1.3.2Page Limitations8
1.3.3Page Size and Format8
1.3.4Tables, Charts, Graphs, and Figures8
1.3.5Cost or Pricing Information8
1.3.6Cross-Referencing8
1.3.7Indexing9
1.3.8Electronic Offers9
1.3.9Distribution9
1.3.10Proposal Inquiries9
2.0VOLUME I, FACTOR 1: TECHNICAL9
2.1General10
2.1.1Amendments10
2.1.2Format and Specific Content10
2.1.3Cross Reference Matrix10
2.2Technical Approach11
2.3Technical Subfactors11
2.3.1Subfactor 1 – Technical/Management Proficiency11
2.3.2Subfactor 2 – Technical Approach12
2.3.3Subfactor 3 – Management Approach13
2.3.4Subfactor 4 – Sample Task Orders13
3.0VOLUME II, FACTOR 2: PAST PERFORMANCE14
3.1General14
3.2Organizational Structure Change History14
3.3Proposal Submittal Information15
4.0VOLUME III, FACTOR 3: COST/PRICE15
4.1General15
4.2Total Evaluated Price (TEP) Matrix, Section J Attachment 516
4.2.1Rounding16
4.3Cost/Price Data16
4.4Cost or Pricing Data Requirements16
4.4.1Contract Data Requirements List (CDRLs)16
4.5Estimating Techniques and Methods16
4.5.1Accounting System17
5.0VOLUME IV: CONTRACT DOCUMENTATION17
5.1Solicitation/Representations and Certifications17
5.1.1Section A – Solicitation/Contract Form17
5.1.2Section B – Supplies or Services and Costs/Prices17
5.1.3Section I – Contract Clauses17
5.1.4Section J – List of Documents, Exhibits, and Other Attachments17
5.1.5Section K – Representations, Certifications, and other Statements of Offerors17
5.2Other Information Required18
5.2.1Authorized Offeror Personnel18
5.2.2Compensation Plan18
5.2.3Small Business Subcontracting Plan18
6.0SOLICITATION REQUIREMENTS, TERMS AND CONDITIONS18
6.1.1Exceptions to Solicitation Requirements19
APPENDIX A: DOWNLOADING THE PPI TOOL20
Appendix B: Cross Reference Matrix27

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

PROPOSAL FORMAT

General The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. Offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause the offeror’s proposal to be determined not eligible for award. Offerors shall submit only one proposal for ATSSI II, as the Government will review only one proposal per offeror. Proposals received are subject to the requirements specified in FAR 52.215-1, unless otherwise tailored in an addendum to the solicitation. Proposals must be received by the Contracting Officer at 6038 Aspen Ave. Bldg. 1289 NE, Hill Air Force Base, UT 84056, Attention: Ms. Emily J. McCollaum, no later than the date and time specified in Section A of the solicitation.

The Government intends to award a single Indefinite Delivery Indefinite Quantity (IDIQ) contract for ATSSI II. The purpose of this effort is to develop and implement an OO-ALC-wide ATE environment supportive of the OO-ALC mission to perform critical test functions important to the ongoing operational safety, suitability, and effectiveness of multiple Air Force Weapon system/subsystems. The contractor will perform work to include, but not limited to, test program set (TPS) development/re-host, IPC-process control, build-to-specification hardware manufacture, ATE technical refresh, and program management office activities.

The proposal shall be clear concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The offeror’s proposal shall provide a description addressing how the offeror intends to meet the Government’s requirements and evidence of the effectiveness and ability to execute proposed methodology.

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

The proposal acceptance period is specified in Section A of the solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid for a minimum of 365 days from the solicitation closing.

In accordance with (IAW) 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.

Communications The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition. The offeror shall address any questions, concerns or requests for clarification to Emily J. McCollaum at emily.mccollaum.2@us.af.mil. When appropriate, answers to questions and concerns will be made available to all offerors.

Exchange of Information Exchanges of source selection information between Government and offerors will be controlled by the PCO. Email may be used to transmit such information only if the email can be sent encrypted, and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. Otherwise, source selection information will be transmitted via direct mail.

Submission, Modification, Revision, and Withdrawal of Proposals Proposals and modifications to proposals shall be submitted by mail to the address located in paragraph 1.1. of this document, showing 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.

The offeror’s submission shall contain two identical sets of CD-R/DVD-R and each set shall be composed of four CD-Rs/DVD-Rs; one CD-R/DVD-R for each specified volume. The first set shall be identified as the Original Copy and the second identical set shall be identified as the Backup Copy. The offeror shall label each CD-R/DVD-R with the Volume Number, Volume Title, Company’s name and solicitation number.

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.

Debriefings The PCO will notify offerors of any decision to exclude them from the competitive range; whereupon they may request and receive a debriefing IAW FAR 15.505, Pre-Award Debriefing of Offerors. 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.

The PCO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.503, Notifications to Unsuccessful Offerors. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make the request IAW the requirements of FAR 15.505 or 15.506, as applicable.

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.

Amendments to Solicitation If this Request for Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged. If the RFP is amended prior to proposal delivery, offerors shall acknowledge each amendment by signing and returning the front page of each amendment with the proposal submission. If the RFP is amended after proposal submission, offerors shall respond by the date and time specified in the amendment to include a signed front page of the amended RFP.

Volume Organization General The offeror shall prepare the proposal as set forth in the Proposal Organization Table below. The volume numbers, volume 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.

The title page of each volume must show:

1) Solicitation Number

2) Company name, address, Commercial and Government Entity (CAGE) Code and Data Universal Numbering System (DUNS) Number

3) Primary point of contact name, telephone number and email address

4) Volume number and volume title (e.g. Volume III, Cost/Price) Table 1: Proposal Organization

Volume Number
Volume Title
Number of Electronic Copies
Total Page Limits
Description

I

Technical

2 Copies (1 Original Copy, 1 Backup Copy)

Technical Subfactor 1 – Technical/Management Proficiency

· Documentation and Drawing

· Drawing are not included in the 25 page limit. Each drawing example (manufacturing drawing, assembly drawing, vendor item control drawing, electrical schematic, and mechanical schematic) shall be limited to no more than 3 pages each

· SGML source code for the documentation example excerpt is not included in the 25 page limit and is allowed unlimited pages

· QMS and CMMI Certification

· Small Business Participation

Technical Subfactor 2 – Technical Approach

· Industrial Process Control (IPC) Configuration Control, and System Engineering Process

· Government Furnished Equipment (GFE) Risk Mitigation Plan Technical Subfactor 3 – Management Approach

· Contractor/Government Interface Plan

· The offeror shall include resumes for Government interface personnel in an Appendix. This Appendix is not included in the 120 page limit and is allowed unlimited pages.

· Contractor Bias Mitigation Plan

· Subcontracting Plan

· Small Business Participation Technical Subfactor 4 – Sample Task Orders

· Technical Sample Task Order

· Awardable Program Management Sample Task Order

II

Past Performance 2 Copies (1 Original Copy, 1 Backup Copy)

3 pages per submission

Past Performance

III

Price 2 Copies (1 Original Copy, 1 Backup Copy)

Unlimited Cost/Price

IV

Contractual Documentation
2 Copies

(1 Original Copy, 1 Backup Copy)

Unlimited Contractual Documentation

· RFP compliance

· Other Information

Page Limitations Individual page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. If Evaluation Notices (ENs) are issued, page limitations may be placed on responses. The specified page limits for EN responses will be identified in the letters forwarded with the ENs to the offerors. Each page shall be counted except the following: blank pages, title pages, tables of contents, lists of tables and drawings, cross-reference matrices, tabs, glossaries, and the Appendix in Vol I that includes resumes for Government interface personnel.

Page Size and Format 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. Except for the reproduced sections of the solicitation document, the text size shall be Times New Roman font and 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.

Tables, Charts, Graphs, and Figures Organizations, systems and layout, implementation schedules, plans, etc. shall be depicted in tables, charts, graphs, or figures wherever practical. These items shall be uncomplicated, legible and shall not exceed 11 x 17 inches in size. For tables, charts, graphs and figures, the text shall be no smaller than Times New Roman 10 point and searchable for text in Microsoft (MS) Office Word and/or PDF formats to the maximum practical extent. Ensure all tables, foldouts, graphics, and figures in the electronic version of the proposal are pasted into the proposal in a format that allows a word search by the host program (do not paste as pictures) to the maximum practical extent.

Cost or Pricing Information All cost or pricing data shall be addressed only in the Cost/Price Proposal and Contract Documentation Volumes.

Cross-Referencing Each volume shall be written on a stand-alone basis so that its contents may be evaluated without 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.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity, but must be hyperlinked IAW Section 2.1.3.

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. Tables of contents do not count against the page limits for the offeror’s respective volumes.

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 the offeror’s respective volumes.

Electronic Offers The offeror shall submit Volumes I through IV in electronic format, using virus-free CD-R or DVD-R. In no cases shall the offeror use CD-RW or DVD-RW. The offeror shall indicate on each CDs/ DVD the Volume Number, Volume Title, Company’s name, solicitation number and either “Original Copy” or “Backup Copy”. Each volume shall be on a separate CD/DVD. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The file naming shall specify the appropriate volume number, volume title and a descriptive identifier. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable and searchable by MS Office Word, Adobe PDF, and MS Office Excel (2016 or later).

The Table of Contents of all proposal volumes shall be hyperlinked to the corresponding material within each proposal volume such that clicking the mouse on an item in the Table of Contents will take the reader to the corresponding section within the body of the proposal volume. Any heading or sub-heading appearing in the Table of Contents shall be hyperlinked as described above. The Table of Contents shall include the file names, as well as page numbers where content is cross-referenced between subfactors. Also, any reference within the body of the proposal volume that refers the reader to another location within the referring document shall be hyperlinked in the manner described above. Hyperlinking references between different filenames is not necessary.

Distribution The proposal shall be addressed to the PCO and mailed to the address cited in paragraph 1.1. Delivery of proposals shall be coordinated at least 24 hours in advance of the due date/time with the PCO. Proposals received after the due date and time specified in the solicitation shall be treated IAW FAR 15.208, Submission, Modification, Revision, and Withdrawal of Proposals.

Proposal Inquiries All inquiries must be submitted via e-mail to the PCO. Questions, if appropriate as determined by the Government, will be answered as quickly as possible, during the proposal preparation period. When appropriate, answers to questions and concerns will be made available to all offerors.

VOLUME I, FACTOR 1: TECHNICAL

General The Technical Volume should be specific and include all requirements of Volume I. Offeror’s responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, the offeror shall provide as specifically as possible the actual approach and/or capabilities it would use for satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By its proposal submission, the offeror is representing that its firm will perform all the requirements specified in the solicitation. The offeror shall not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

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

Section
Title
0
Title Page
1
Table of Contents
2
List of Tables and Drawings
3
Glossary
4
Cross Reference Matrix
5
Subfactor 1 – Technical/Management Proficiency
6
Subfactor 2 – Technical Approach
7
Subfactor 3 – Management Approach
8
Subfactor 4 – Sample Task Orders
9
Appendix

Note: Offerors shall not address Appendix “C” Safety, Fire Protection and Health Specification, Industrial Security Requirements of the PWS in the offeror’s proposal. However, the successful offeror shall implement a safety program IAW Appendix C of the PWS.

Amendments For any amendment to Volume I, the offeror’s proposal will include a cover letter delineating any changes from initial proposal, to include changes/revisions (if needed) for Final Proposal Revisions (FPR).

Format and Specific Content The information in paragraphs 2.2 - 2.3 shall be provided in the written technical proposal and will be used to assess the proposed technical approach in accordance with Section M, Evaluation Factors for Award. The written technical proposal shall address each of the following to describe the offeror’s proposed approach and/or capabilities in performing the requirements set forth in the subfactors.

Cross Reference Matrix The offeror shall fill out the Cross Reference Matrix (Section L: Appendix B), and submit with the proposal indicating where in its proposal the information can be found as it relates to the PWS, Section L, and Section M. The cross reference matrix will help an offeror ensure it has responded to all the evaluation criteria and proposal submittal requirements identified in the solicitation. If the matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over the matrix. Section M references in the matrix are for informational purposes only, and the Government will evaluate proposals solely in conformance with Section M of the solicitation. This matrix will be used for reference only and will not become contractually binding.

Technical Approach In the Technical Volume, address the technical/management proficiency, technical approach, management approach and sample task orders, and also provide evidence of meeting or exceeding the minimum requirements of each subfactor.

Technical Subfactors Subfactor 1 – Technical/Management Proficiency Subfactor 2 – Technical Approach Subfactor 3 – Management Approach Subfactor 4 – Sample Task Orders Subfactor 1 – Technical/Management Proficiency The offeror shall describe as specifically as possible the actual approach and/or capabilities it would use for satisfying each element within Subfactor 1 - Technical/Management Proficiency.

1) Documentation and Drawings The offeror shall submit a minimum of two (2) documentation excerpt examples that are completed in SGML and adhere to MIL-DTL-38807D, MIL-DTL-87929E, MIL-STD-38784A, follows TO 00-5-1, TO 00-5-3, TO 00-5-16. A documentation excerpt example is expected to be no more than 10 pages and the first page of the excerpt must be the title page or the page displaying the proper Government statements and notices of the document the excerpt was taken from. The offeror shall provide the SGML source code associated with the submitted documentation excerpt examples and the SGML source code will not be included in the 25 page limit. There are several documentation requirements identified in ATSSI II’s Performance Work Statement (PWS), including but not limited to Test Program Manual as defined in ATSSI II’s PWS Section 3.1.3.8, Test Program Hardware Operation & Maintenance Manual as defined in ATSSI II’s PWS Section 3.1.3.9, and Technical Order as defined in ATSSI II’s PWS Section 3.3.6, which can be used as examples of options for documentation excerpts.

The offeror shall submit drawings that adhere to the ASME Y14 standard and provide Product Level detail IAW MIL-STD-31000B.. There shall be one (1) example submitted for each of the following types of drawings: manufacturing drawing, assembly drawing, vendor item control drawing, electrical schematic, and mechanical schematic. Each drawing shall be labeled according to the type to drawing and no more than three (3) pages. The drawings will not be included in the 25 page limit. The drawings requirement is defined in section 3.1.3.10 of the PWS.

2) Quality Management System (QMS) and CMMI Certification The offeror shall demonstrate evidence of certification or third party validation of offeror’s QMS, a QMS recertification plan, and current appraisal rating certificate for CMMI Level 3 or higher IAW section 7.6 of the PWS.

3) Small Business Participation The offeror shall describe their Small Business Participation approach to address the small business subcontracting goal as stated in section 7.21.1 of the PWS. The Small Business Participation approach shall also include the extent to which such firms are specifically identified in proposals and the extent of commitment to use such firms. The Small Business Participation approach is not to be confused with the offeror’s Small Business Subcontracting Plan (clause 52.219-9), which is covered under Section 5.2.3 of this document.

Subfactor 2 – Technical Approach The offeror shall describe as specifically as possible the actual approach and/or capability it would use for satisfying each element within Subfactor 2 – Technical Approach

1) Industrial Process Control (IPC), Configuration Control, and System Engineering Process The offeror shall submit their system engineering process as defined in section 7.6.1 of the PWS. The offeror shall describe how they will apply their system engineering process to meet the technical ATSSI II requirements. The system engineering process shall at a minimum describe the offeror’s system engineering approach to material solution analysis, technology development, engineering and manufacturing development, production and deployment. The offeror’s system engineering process shall include relevant internal checklists, quality controls, configuration controls, decision points and stakeholder interaction. Additionally, the offeror may include relevant certification/accreditation that may help illustrate a higher level of quality control/assurance of their system engineering process, such as AS9100/AS9110/ISO 9001 certification, NADCAP accreditation, etc. The certification and/or accreditation must include authorizing authority and date of issue.

In addition, the offeror shall submit two (2) preliminary IPC plans IAW section 7.1 and 7.1.2 of the PWS for Test Program Set Process Control Plan (TPSPCP) and Build-to-Specification Hardware Manufacture Process Control Plan (BHMPCP).

2) Government Furnished Equipment (GFE) Risk Mitigation Plan The offeror shall submit a Government Furnished Equipment (GFE) Risk Mitigation Plan to address the risk associated with non-available GFE for Task Order requirements, the offeror’s understanding of how to obtain GFE, the offeror’s understanding of the Government’s Loan/Lease process, and the offeror’s mitigation strategy if GFE is not available. Section 6.1 of the PWS explains GFE.

Subfactor 3 – Management Approach The offeror shall describe as specifically as possible the actual approach and/or capability it would use for satisfying each element within Subfactor 3 – Management Approach

1) Contractor/Government Interface Plan The offeror shall submit a Contractor/Government Interface Plan that indicates specific interface personnel for the functions of Logistics, Configuration Control, and Program Management. This plan shall also provide evidence of the offeror’s experience working with relevant Government organizations (i.e. PMEL, AFMETCAL, ATSG, TOMA, etc.) The offeror shall include applicable resumes for Government interface personnel in an appendix. This appendix is not included in the 120 page limit.

2) Contractor Bias Mitigation Plan The offeror shall submit a preliminary Contractor Bias Mitigation Plan that demonstrates how the offeror will address Contractor Bias Mitigation IAW Section 7.2.1 of the PWS.

3) Subcontracting Plan The offeror shall submit a preliminary Subcontracting Plan that demonstrates how the offeror will address the Subcontracting Plan IAW Section 7.2.2 of the PWS.

Subfactor 4 – Sample Task Orders The offeror shall describe as specifically as possible the actual approach and/or capability it would use for satisfying each element within Subfactor 4 – Sample Task Orders

1) Technical Sample Task Order The offeror shall propose to the Technical Sample Task Order provided (Attachment 6, Technical Sample Task Order). The offeror shall submit a detailed approach to the sample task IAW ATSSI II PWS section 3.6.3. The offeror shall provide a schedule, milestones, development process, design phases, proposed man-hours, proposed labor categories, assumptions, inherent risk concerns, documentation, drawings, and other relevant details for a complete approach to the Sample Task Order. The offeror shall select the ATS Support solution deemed most appropriate for this particular application. Full justification shall be provided for the selection of this ATS support solution (ref. PWS Sections 3.3.5).

2) Awardable Program Management Sample Task Order The offeror shall propose to the Program Management Sample Task Order provided (Attachment 7, Awardable Program Management Sample Task Order). The offeror shall submit a detailed approach to the sample task IAW ATSSI II PWS section 3.6.3. The offeror shall provide a schedule, program management support activities, proposed man-hours, proposed labor categories, assumptions, inherent risk concerns, and other relevant details for a complete approach to the Sample Task Order.

VOLUME II, FACTOR 2: PAST PERFORMANCE

General Each offeror shall submit a Past Performance Volume with its proposal, containing past performance information in accordance with the format contained in Section L, Appendix A, Past Performance Questionnaire (maximum of three contracts, if available). This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform a significant portion of the effort (20% or more of contract effort). This is based on the offeror’s total proposed price, or performance aspects of the effort the offeror considers critical to overall successful performance. Offerors past performance shall be recent, within five (5) years of the date of solicitation. For each recent past performance citation submitted, the performance quality of the work performed will be assessed for the similarity to the ATSSI II scope, identified in PWS section 1.3, and magnitude. 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.

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 offer to resolve problems such as issues 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. Submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is an example of this. Categorize the relevant information into the specific scop elements identified in PWS section 1.3 and the magnitude of the effort.

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.

The quality of the service performance assessment may result in positive or adverse findings. Adverse is defined as past performance information that supports an unsatisfactory rating on any evaluation element or any unfavorable comment received from sources without a formal rating system. For adverse information identified, the evaluation will consider the number and severity of the problem(s), mitigating circumstances, and the effectiveness of corrective actions that have resulted in sustained improvements. Process changes will only be considered when objectively measurable improvements in performance have been demonstrated.

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. A pamphlet or other commercial document describing such reorganizations may suffice. 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. This structure change history will not be counted against page limitation, but will be restricted to no more than 3 pages.

Proposal Submittal Information The Government requests the offeror submit Past Performance Volume, no later than the proposal due date. PPI sheets shall be submitted using the EZ Source PPI Tool (reference Section L, Appendix A, Instruction to Offerors: Past Performance Information for Offerors). All PPI sheets shall contain contract number and/or task order number and shall be saved as Access Database files (.accdb).

VOLUME III, FACTOR 3: COST/PRICE

General The Price Volume should be specific and include all information required of Volume III. Compliance with these requirements is mandatory and failure to comply may result in rejection of the offeror’s proposal. Note that unreasonably 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 unrealistic proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject the offeror’s proposal. Offers should be sufficiently detailed to demonstrate reasonableness. The burden of proof for credibility of proposed costs/prices rest with the offeror.

Offeror’s responses will be evaluated in the following areas as defined in Section M of the RFP:

1) Completeness

2) Reasonableness

3) Balance

4) Total Evaluated Price (TEP)

The Cost/Price Volume shall be organized according to the following general outline:

Section
Title
1
Table of Contents
2
Listing of Abbreviations and Acronyms (used within cost/price volume)
3
General
3-1
TEP Matrix Worksheet
3-2
Accounting System

Total Evaluated Price (TEP) Matrix, Section J Attachment 5 Offerors shall input into the TEP Matrix, located in Section J, Attachment 5, Not-to-Exceed (NTE) fully burdened rates for all labor categories and years. Fully burdened rates shall include direct labor rates, all direct costs, indirect costs (overhead, General and Administrative, Fringe Benefits, etc.) and profit necessary for the performance of the entire requirement. The formula for application of hours and the notional hours used will not be disclosed to the offerors. The TEP is for evaluation purposes only; however, all proposed fully burdened NTE rates and formula results and numbers directly entered for the Awardable Program Management Sample Task Order are contractually binding.

Submit a copy of the completed TEP Matrix in Cost/Price Volume III in MS Excel (non PDF format).

Rounding All fully burdened labor rates provided shall be rounded to the nearest penny.

Cost/Price Data Data beyond that required by this instruction shall not be submitted, unless the offeror considers it essential to document or support its cost/price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Price Volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

Cost or Pricing Data Requirements In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided IAW FAR 15.403-5, Instructions for Submission of Certified Cost or Pricing Data and Data other than Certified Cost or Pricing Data. If, after receipt of proposals, the PCO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1, Prohibition on Obtaining Certified Cost or Pricing Data (10 U.S.C. 2306a and 41 U.S.C. 254b) apply, the offeror shall be required to submit additional cost or pricing data.

Contract Data Requirements List (CDRLs) CDRLs will not be separately priced. Cost required to produce each CDRL should be included in the offeror’s proposed labor hours.

Estimating Techniques and Methods Offerors shall use generally accepted estimating techniques to develop their estimates for the proposed rates.

Accounting System Because a portion of the contemplated contract type is other than Fixed-Price, the Offeror must provide evidence of an approved accounting system for themselves and any subcontractors who will be issued other-than fixed price subcontracts. If not, the Offeror will be required to return a pre-award survey as part of the solicitation documents. If an offeror’s accounting system has been disapproved in whole or in part, they shall provide the status of actions taken to correct noted deficiencies. Also, the contractor shall identify any deviations from their standard procedures in preparing this proposal.

VOLUME IV: CONTRACT DOCUMENTATION

Solicitation/Representations and Certifications The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror’s proposal shall include a signed copy of the solicitation, and Sections A through K. This includes delivery of all applicable documents.

Section A – Solicitation/Contract Form Complete Blocks 13, 14 (when applicable), 15, and 16, then sign and date Block 17 of the Standard Form (SF) 33, Solicitation/Contract. Signature by the offeror on the SF 33 constitutes an offer, which the Government may accept. The “original” copy should be clearly marked under separate cover and should be provided without any punched holes.

Section B – Supplies or Services and Costs/Prices The offeror shall not propose prices for each CLIN in Section B of the solicitation. All required rates shall be provided in TEP Matrix of Section J, Attachment 5, which shall be submitted in Volume III.

Section I – Contract Clauses The offeror shall comply with the clauses specified within Section I of the solicitation. Furthermore, any inference of a clause and or provision will be adhered to. All laws, regulations, and statutory authorities will also be applied within the solicitation.

Section J – List of Documents, Exhibits, and Other Attachments The offeror shall complete and provide the following attachments:

Attachment 5 – TEP Matrix (Submit in Volume III) Section K – Representations, Certifications, and other Statements of Offerors The offeror shall provide completed representations, certifications, acknowledgments, and statements. Offeror must have filled out an online provision 52.204-8 Annual Representations and Certifications (Dec 2012), Online Reps and Certs at http://www.sam.gov. Offer shall ensure certification of its business size under North American Industry Classification System (NAICS) Code 541512.

Other Information Required Authorized Offeror Personnel Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to the proposal and who can obligate the company contractually. Also, identify those individuals authorized to negotiate with the Government. Additionally, provide the name and telephone number of the CEO, Division President, and/or Vice President.

Compensation Plan The Offeror shall submit a total professional employee compensation plan meeting the requirements of FAR 52.222-46. The Offeror shall provide detailed information IAW FAR 52.222-46. Any cost/price data included in the employee compensation plan that is not included in Vol III shall not be evaluated for TEP or any pricing evaluation.

Small Business Subcontracting Plan In the event that a subcontracting plan is needed the offeror shall provide the following as attachments to the model contract: Subcontracting Plan 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 Women Owned Small Business (WOSB).

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, and DFARS 252.219-7003, Small Business Subcontracting Plan (DoD Contracts) that separately addresses and specifies the extent of the offeror’s commitment to the participation of SB, VOSB, SDVOSB, HubZone, SDB, and WOSB concerns. If the offeror is submitting an individual contract plan, the plan must separately address subcontracting with SB, VOSB, SDVOB, HUBZone, SDB, and WOSB concerns with a separate part for 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 a 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 219.702-70, Statutory requirements for the Test Program for Negotiation of Comprehensive Small Business Subcontracting Plans, 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 in accordance with FAR 52.219-9 and DFARS 252.219-7003.

SOLICITATION REQUIREMENTS, TERMS AND CONDITIONS

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.

Exceptions to Solicitation Requirements Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete supporting 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 performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content provided in Table 2, Solicitation Exceptions, below.

Table 2: Solicitation Exceptions

SOLICITATION

Document

Page/ Paragraph
Requirement/ Portion
Rationale

PWS, Solicitation, Section L, 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

Appendix A: Downloading the PPI Tool The PPI Tool can be downloaded by performing the following steps (if you are unable to download the Tool, contact the contracting officer for assistance):

1. Access the SAM (https://www.beta.sam.gov/) website.

2. Find the solicitation posting.

3. Locate the “ppi tool” link under “Attachments/Links” section.

4. Select the link and save the “ppi tool” to your computer. Name the file as the prime contractor + RFP number + file extension (e.g. XYZCompanyFA822420R0009.mdb).

Note: PPI Tools saved in Microsoft version 2007 and greater will be saved with “.accdb” file extension.

Entering information in the PPI Tool After selecting and saving the tool, enter information by performing the following steps:

1. Open the saved PPI Tool.

2. Select the “Options” button from the “Security Warning” banner, if applicable . The “Security Alert” pop-up screen displays.

Figure 1: Security Alert Pop-up Note:

· Files saved using Microsoft Office 2010 will have the “Enable Content” button on the “Security Warning” banner and therefore will not get a Security Alert pop-up.

· If a "read only" file is opened, in order to populate data in the file, click "Save As" in the "Read-Only" message bar. Enter the filename as the prime contractor + RFP number + file extension (e.g. XYZCompanyFA822420R0009.mdb).

3. Select the radio button “Enable this content” and then click “OK.” A setup pop-up screen displays.

Figure 2: Setup Pop-Up

4. Select the “Start” button. The “Application Setup” screen displays.

Figure 3: Application Setup Screen

5. Enter the Offeror’s Name and RFP Number and then click the “Next” button. The application setup continues.

Figure 4: Continue the Application Setup

6. Choose the appropriate option by selecting the corresponding radio button and then click the “Next” button. The “Contractor’s Menu” displays.

Figure 5: Contractor’s Menu

7. Click the “Step 1: Set up Business Relationships” button to create a business relationship, if applicable, for each contributing contracting organization before proceeding throughout the PPI Tool (refer to Section L of the RFP for detailed instructions). Identify all prime and sub-prime organizations and categorize them according to the appropriate role in the proposed acquisition. The “Business Relationships” screen displays.

Figure 6: Business Relationships

8. Click the “New” button to create a business relationship for the proposed acquisition. An additional “Business Relationships” screen displays.

Figure 7: Enter New Business Relationship

9. Complete the fields as follows (fields marked on the screen with an asterisk ‘*’ are required):

· Contractor’s Name: Self-explanatory

· Role in Proposed Acquisition: Choose one of the four options – Prime, Sub, Joint Venture, or Other (Explain). An explanation comment box will display when you select “Other.”

· Place of Work: Location where contractor will perform work.

· Percentage of Work: Identify percentage of work contributed by specified contracting organization.

· Responsibilities: Detail responsibilities of specified contracting organization.

10. Select one of the buttons at the bottom of the screen.

· Add – Saves the current business relationship and allows for the addition of a new one.

· Close – Cancels the current business relationship without saving.

Note: In order to edit or delete an existing business relationship in the list, double-click on it.

11. Select the “Close” button on the “Business Relationships” screen after all of the business relationships has been added.

12. Click the “Step 2: Enter Past Performance Information (PPI)” buttonto enter the Past Performance Information. The “Past Performance” screen displays.

Figure 8: Past Performance

13. Click the “New” button to enter Past Performance Information for the proposed acquisition. An additional “Past Performance” screen displays.

Figure 9: Enter Past Performance Information

14. Complete the fields on each of the tabs as follows (fields on the screen marked with an asterisk ‘*’ are required):

· Contract Information Tab

· Contractor: Select from the dropdown the appropriate contractor.

· Cage Code: Self-explanatory.

· Contract Number: If you don’t have a contract number, enter “N/A.”

· Program Title: Enter full name of program.

· Contracting Agency/Customer: Enter servicing contracting agency and customer (office symbols suffice).

· DUNS Number: Self-explanatory

· Delivery Task/Order: If the order is provided as a stand-alone reference, enter the task/call/delivery/purchase order number.

· Contract Type: Enter Firm-Fixed-Price (FFP), Cost Plus Fixed-Fee (CPFF), Indefinite Delivery/Indefinite Quantity (ID/IQ), LH, Blanket Purchase Agreement (BPA), Cost Plus Incentive-Fee (CPIF), Cost Plus Award Fee (CPAF), etc. For additional clarification, click the question mark button.

· Short Program Title (i.e. Acronym): Enter abbreviated title for the program or enter “N/A.”

· Contract Dollar Value:

· Original: Input total contract dollar value, with all options if applicable, in the amount originally awarded on the referenced contract.

· If ID/IQ or BPA, provide total ceiling.

· If stand-alone task/call/delivery/purchase, provide amount of the individual contract.

· Current: Input total contract dollar value, with all options if applicable, as the contract stands at time of PPI submission.

· If ID/IQ or BPA, provide total ceiling.

· If stand-alone task/call/delivery/purchase, provide amount of the individual contract.

· Period of Performance (mm/dd/yy)

· Start Date: Input start date of contract.

· Original End Date: Input original end date based on award.

· Current End Date: Input end date, as the contract stands at time of PPI submission.

· Explain the differences in Period of Performance, if applicable: Enter an explanation of the difference between “Original End Date” and “Current End Date.”

· Program Details Tab

· Brief Description of Effort as:

· Select Prime, Sub, Joint Venture, or Other (Explain). An explanation comment box will display when you select “Other.”

· Provide a brief description of the service provided and actual work performed under this contract reference.

· ****If applicable: Provide information on problems encountered on the identified contracts. At a minimum, briefly describe the problem experienced, actions taken to alleviate the problem, and whether or not the problem was satisfactorily overcome.****

· Explain how your experience on this program is relevant for each subfactor under the Technical Factor in Section M of the RFP, including any unique aspects that demonstrate relevancy in this effort. Provide evidence to support how the contract referenced has relevant experience and demonstrates the ability to perform the solicitation requirements as described in Section M of the RFP. As applicable, address how the proposed reference relates to each of the Technical Subfactors.

· POC & Key Individuals Tab

· Customer Points of Contact: Click the “Program/Site Manager,” “Contracting Officer” or “Admin POC” button for the point of contact that you would like to add, edit, or delete.

Note: For government contracts provide current information on Program Manager, Contracting Officer, and Admin POC, if available.

15. Select from the buttons at the bottom of the Past Performance screen:

· Save – Saves the Past Performance Information and displays the “Contract Information” tab on the Past Performance screen.

· Close – Closes the Past Performance screen. If there were any updates, a pop-up window displays asking to save before closing.

· Delete – Deletes the current PPI record. A pop-up window displays, select “Yes” to delete the record or “No” to close the window without deleting the record.

Note: In order to edit or delete an existing PPI record in the list, double-click on it.

16. Select the “Close” button on the “Past Performance Information” screen after all of the PPI records have been added.

Printing Reports and Submitting PPI Tool In order to print the Business Relationships and PPI reports, perform the following steps:

1. Click the “Step 3: Print Report” button . A pop-up displays asking which report to print.

Figure 10: Select Report to Print

2. Select separately each of the two options, “Business Relationships” or “Past Performance.” The Business Relationships and Past Performance documents will print separately; combine the two to create your Past Performance Volume.

In order to submit the Business Relationships and PPI, perform the following steps:

3. Click the “Step 4: Submit” button . The “Submission Instructions” screen…

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 .