DRAFT_ATSSI_Section_L.pdf

1 | P a g e

SECTION L

PROPOSAL PREPARATION AND SUBMISSION INSTRUCTIONS

ATSSI

SOURCE SELECTION

1.0 PROGRAM STRUCTURE AND OBJECTIVES

The purpose of this effort is to develop and implement an IT infrastructure supportive of the OO-ALC 309 EMXG mission to perform critical test functions important to the ongoing operational safety, suitability, and effectiveness of multiple Air Force weapon systems/subsystems. The resulting IT infrastructure shall be referred to as the EMXG

Automated Test System Sustainment Initiative (ATSSI). The ATSSI infrastructure solution will provide for the integration, update, and consolidation of computer-based test stations (i.e., ATS), test fixtures, Test Program Sets (TPSs), database repositories, analytical software tools, and associated network communication functions. Additionally, the EMXG ATSSI will resolve current system obsolescence and performance issues while providing significant efficiency and cost improvements.

1.1 Budget/Funding Information

Funding will be obligated on each task order awarded under the basic contracts. Notice to Offeror(s)/Supplier(s): Funds are not presently available for this effort. No award will be made under this solicitation until funds are available for the initial task order/minimum guarantee. The Government reserves the right to cancel this solicitation, either before or after the closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an Offeror for any costs.

1.2 General Instructions

The offeror's proposal must include all data and information requested by this Instructions to Offeror (ITO) and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement

(PWS) and Contract Data Requirements List (CDRL). Non-conformance with the instructions provided in this ITO shall result in an unfavorable proposal evaluation.

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 offeror's proposal.

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

The proposal acceptance period is specified in Section A of the model contract/solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

2 | P a g e

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the offeror requests otherwise, the

Government will destroy extra copies of unsuccessful proposals.

2.0 GENERAL INFORMATION

2.1 Basic Proposal Guidelines

2.1.1 Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address located in Section A of the model solicitation and

Section L, 2.4.

2.1.2 Debriefings

The CO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a preaward debriefing or they may choose to wait until after the source selection decision to request a postaward debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.1.3 Discrepancies

If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the CO in writing with supporting rationale as well as the remedies the offeror is asking the CO to consider as related to the omission or error. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

2.1.4 Bidders Library

Offerors may request access to the restricted-access documentation. Access may be granted by secured mailing of a CD/DVD. In order to request access, the offeror must submit their DD Form 2345, Military Critical Technical Data Agreement, to Don Hoover at don.hoover.1@us.af.mil and Brady Smith at brady.smith@us.af.mil. It is recommended the offeror submit their DD Form 2345 as soon as possible after RFP release in order to have ample proposal preparation time.

2.1.5 Oral Presentations

Oral presentations will not be allowed.

mailto:don.hoover@us.af.mil mailto:brady.smith@us.af.mil

3 | P a g e

2.1.6 Communications

Exchanges of source selection information between the Air Force and offerors will be controlled by the Contracting Officer. Email may be used to transmit such information to offeror’s only if the email can be sent and received encrypted and includes “Source

Selection Information – See FAR 2.101 & 3.104” in the Subject line.

2.2 Proposal Organization

The offeror shall prepare the proposal as set forth in the Proposal Organization Table

(Table 2.2) below. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified. The volumes identified in the table shall be separately bound in three-ring, loose-leaf binders. The contents of each proposal volume are described in this Section (L) and summarized in the table below:

Table 2.2 - Proposal Organization

VOLUME TITLE COPIES PAGE LIMIT

I

Technical/ Potentially

Awardable Air Data

Computer Task Order

(ADCTO) Response

1 CD to include Original

Volume and Redacted

Volume

2 Hardcopies

Technical- 50 single-spaced pages, Times New

Roman font, size 12

ADCTO- 20 single-spaced pages, Times New Roman font, size 12

II

Past Performance

Note: Past Performance

Volume Shall be submitted

2 weeks after RFP release date

1 CD

2 Hardcopies

3 single-spaced pages per submission, Times New

Roman font, size 12

III Price Original plus 1

Hardcopy, and 2 CDs

Unlimited;

“Pricing Assumptions limited to 2 pgs.”

IV Contract Documentation

1 CD

2 Hardcopies Unlimited

Note: Proposal validity date shall be no less than 240 days from date of submission.

2.2.1 Page Limitations

Page limitations are identified in Table 2.2 — Proposal Organization and explained below. Offerors are advised that the limitations shall be treated as maximums. If exceeded, the excess not pages will not be evaluated or considered for award purposes;

rather, they will be returned to the offeror as soon as practicable. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Each page

4 | P a g e shall be counted except cover/title pages, cross-reference matrices, tables of content, tabbed dividers, acronym lists, and glossaries.

Resumes will not be counted toward the page limitation. Each resume shall not exceed 3 pages in length. Licenses and certifications also will not be counted toward the page limitation.

2.2.1.1 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. Pages shall be typed using single spacing, except for the reproduced sections of the solicitation document, the text size shall be no less than 12-point. Font will be Times New Roman. 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 1-inch side margins.

Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

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 x 17 inches in size. Foldout pages shall fold entirely within the volume, and each surface of a foldout shall be counted as a separate page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 10- font. These limitations shall apply to both electronic and hard copy proposals.

2.2.2 Cross Referencing

Each Volume (I – IV) of a proposal addresses a specific factor. The proposal shall be submitted, evaluated, and considered based solely on the information contained therein

(i.e., each volume “stands alone”). Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal. The offeror shall provide a cross reference matrix/table/note (e.g., exhibited below) in a clear and similar format to the exhibit shown below. The effect of the cross reference is to draw the evaluator’s attention to the criteria the Offeror’s addressing, indicating the proposal information as it relates to Sections L and M, PWS, CLIN numbers, and CDRL references. This shall be included in the Technical Volume

(Volume I).

5 | P a g e

Cross Reference Matrix

Volume Section L Section M

ADCTO

PWS

PWS

Proposal

(for Contractor

Fill-In)

Para. X.x. Para. X.x. Para. X.x. Para. X.x.

Proposal reference or section

I

Technical Approach

3.1 2.3.1

2.1.1,

2.1.8.3 3.4,3.2, 3.5

I

Management

Approach

3.2 2.3.2 2.1.2 3.1.1,3.1.1.3, 3.2.2

I

Air Data Computer

Task Order

3.3 2.3.3 n/a n/a

II

Past Performance

4.0 2.4 n/a n/a

III

Pricing Proposal

5.0 2.5 2.1.2 n/a

IV

Contract

Documentation

6.0 3.0 2.1.1.1 n/a

2.2.3 Indexing

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.2.4 Glossary of Abbreviations and Acronyms

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

2.2.5 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the offeror's name. The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and

Marking of Contractor Bid or Proposal Information and Source Selection Information.

6 | P a g e

Each page within a section shall be numbered consecutively.

Each page that contains proprietary information shall be marked inside the header and footer of each page with the following statement “SOURCE SELECTION

INFORMATION (FAR 3.104-4 and 2.101).”

2.3 Electronic Offers

The content and page size of electronic copies shall be identical to the hard copies. For electronic copies, indicate on each CD the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The offeror shall submit volumes I through IV in electronic format, using recordable CDs. (NOTE THAT “CD-RW’s CANNOT BE READ, EVALUATED, OR CONSIDERED) Each volume shall be in a different directory on a

CD. If files are compressed, the necessary decompression program must be included.

The electronic copies of the proposal shall be submitted in a format readable by

Microsoft (MS) Office Word 2007, MS Office Excel 2007, MS Office Project 2007, and

MS Office Power Point 2007, as applicable. If there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

2.4 Distribution

Provide to the Contracting Officer (address below) two (2) hardcopy and one (1) electronic proposal. The "original" proposal shall be identified and signed by the offeror’s authorized representative and the “copy” should be identified. All requested copies must be received by the due date identified on the front page of the RFP.

Proposals shall be addressed to the CO and delivered to:

AFMC OL_H/PZIMB

ATTN: Don Hoover

6038 Aspen Ave, Bldg 1289

Hill AFB, UT 84056-5825

Include Solicitation Number FA8224-17-R-0001 on the address label.

3.0 VOLUME I, FACTOR 1: TECHNICAL/MANAGEMENT APPROACH, AIR DATA COMPUTER

TASK ORDER

The Technical/Management Approach, ADCTO Volume I should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for

Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

7 | P a g e

3.1 Subfactor 1: Technical Approach

The offeror's technical approach will be evaluated on its ability to meet the requirements specified. The offeror's technical approach should demonstrate a clear understanding of the current technical environment and requirements.

In the Technical/Management Approach, ADCTO Volume I, address your technical solution for meeting or exceeding the Government’s minimum performance, as defined in each element, or capability requirements of each technical Subfactor and corresponding

Sub-bullet. Address Technical Risk associated with those aspects of your proposed technical approach. Consider any risk that has the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. Provide the rationale for each risk including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements

(for example: PWS or specification requirements), whether or not those requirements are identified as sub-bullets. Propose a realistic "work-around" or risk mitigations for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation.

The Government has identified several areas of risk for this proposed effort. The following risks are included for evaluation under the Technical Approach. Those risks include:

Documentation/Drawings

Configuration Control/System Engineering Process

Government Furnished Equipment (GFE) Mitigation Plan

Each element will be evaluated and rated according to their technical risk to the overall performance of the contract effort.

3.1.1 Documentation/Drawings

Offeror shall clearly describe proposed procedures to properly document and submit all necessary documentation to cognizant Government organizations for the work proposed in the PWS. These requirements are identified in ATSSI’s Performance Work Statement

Section 3.4.2 and Section 3.4.6. Submissions should highlight offeror’s staff experience to accomplish the work identified.

Also separately clearly describe proposed procedures and processes to support the ability to properly provide the Government with approved drawings for development work.

These drawings must conform to required regulations and procedures IAW the requirements identified in ATSSI’s Performance Work Statement 3.4.6. and 3.5.2.

3.1.2 Configuration Control/System Engineering

Offeror shall clearly describe proposed methodology to support the ability to provide configuration control and adhere to industry best practices identified in ATSSI’s

Performance Work Statement (PWS) Section 3.2.2, 3.1.1.1, and 3.1.3 highlighting

8 | P a g e offeror’s staff experience to accomplish the work identified. Also the offeror shall clearly describe the information to support the ability to provide System Engineering

Processes for the development of hardware and software identified in ATSSI’s

Performance Work Statement (PWS) Section 3.1.1, highlighting offeror’s staff experience to accomplish the work identified.

3.1.3 GFE Mitigation Plan

Offeror shall clearly describe information to support the ability to provide the

Government a plan for mitigating risk associated with Government Furnished Equipment

(GFE) identified in ATSSI’s Performance Work Statement (PWS) Section 5.1.2, highlighting offeror’s staff experience to accomplish the work identified.

3.2 Subfactor 2: Management Approach

The offeror shall clearly describe its management approach, IAW PWS Section 3.1.1

Develop EMXG ATSSI IMP, Section 3.1.1.3 Program Management Plan, and Section

3.2.2 Infrastructure Support Services. Detailed responses to each of these requirements shall provide an explanation indicating offeror’s ability and proposed methodology to be utilized to meet each requirement. Responses shall not be a restatement of the requirement but shall be comprehensive, well-conceived, and include detailed approaches to accomplishing the tasks and providing the deliverables. The offeror shall address the elements identified in the following sections.

3.2.1 Management Approach/Team Structure

The contractor shall institute and maintain an effective, efficient and responsive management organization that shall be responsible for the management and oversight of all personnel and financial resources utilized in the performance of this contract, including the management of its subcontractor(s). The contractor's management organization shall ensure that all work activities are performed timely, and in a cost effective manner, while maintaining the highest quality of performance and necessary communications with the Government. To this end, the contractor shall furnish a Team

Structure with sufficient detail to describe the resources and the company's policies and procedures for the effective management of the contract, the work to be performed, and the risk management strategy. Offerors should also include all assumptions that it considers relevant to the understanding of the PWS, taskings therein, and planned execution strategy.

Included in this Team Structure, the offeror shall provide labor categories relevant to the work identified in all of the sections of the PWS and specific explanations as to why each

Labor Category is relevant and how it will be used in the process of accomplishing the

PWS objectives. Of particular interest, the offeror should readily identify key labor categories relevant to the work to be performed and include such categories in this volume with associated labor rates included in the Pricing Volume III.

3.2.2 Contactor/Government Interface Plan

It is fully anticipated that the Contractor will require subcontracting to fulfill the requirements of the PWS, in particular, Section 3.1.1 Develop EMXG ATSSI IMP. The

9 | P a g e offeror’s proposal shall provide a plan by which the contractor will interface with the

Government in the course of the work performed by subcontractors. To this end, the offeror shall provide their plan for such Government interface to the contractor and all subcontractors.

The contractor shall provide resumes for all key personnel which interface with the

Government, showing sufficient detailed descriptions to demonstrate the qualifications, certifications, and experience necessary to perform specified tasks and functions that the contractor will be contractually obligated to provide. Key personnel refers to those main points of contact with the Government as identified by the contractor as critical to coordination of PWS and Task Order activities.

Resumes shall comply IAW the PWS Section 3.1.1.3 Program Management Plan and shall provide the specific qualifications as required.

3.2.3 Transition Plan

The offeror shall provide a Transition Plan to identify and mitigate transition risks and ensure the government's access to qualified personnel and required expertise in an expeditious manner. A detailed schedule should be provided for evaluation of how long it will take for the offeror to establish their team and ability of the contractor to comply with the PWS (Section 5.20 Transition Support). Such a plan should provide enough detail to allow evaluators the ability to determine the feasibility of the plan within the time frame proposed. Also included are:

1) Management plans to ensure PWS objectives and requirements are met; plan must discuss support organization structure and required Level of Effort (LOE) and skill levels, and discuss approach to continuity of operations, performance measurement, deliverables, and quality assurance requirements.

2) Corporate, teaming partner(s) (as applicable), and

3) Technical staff expertise (resumes and certifications). Resumes should be provided only for “key personnel” as identified by the Contractor as vital to the transition process. These resumes are subject to the same conditions and restrictions as found in

Section 2.2.1.

3.2.4 Small Business Participation Plan (IAW PWS 5.19)

The Offeror shall provide a proposed Small Business Participation Plan within the technical proposal. The Small Business Participation Plan is not to be confused with the

Subcontracting Plan.

3.3 Subfactor 3: Potentially Awardable Air Data Computer Task Order

This subfactor shall provide a proposal response to the potentially awardable ADC Task

Order (ADCTO) and, at a minimum, be prepared in a form consistent with stated

ADCTO. The response shall be prepared in an orderly format and in sufficient detail to enable the Government to make a thorough evaluation of the Contractor’s technical capability and ability to comply with the contract task requirements specified in the

10 | P a g e

ADCTO. The offeror shall specifically address the methodology used for accomplishing the tasks.

3.3.1 Offeror Procedures and Processes at Task Order Level

Each response should include sufficient information to describe the offeror’s procedures, processes, controls, etc. that are established at the TO level. The offeror shall specifically identify and explain their process to achieve full capability of performance; identify and explain how they will be staffed to include identifying necessary skill sets to complete each task; how work will be scheduled and executed. The offeror shall address the following elements:

1) Detailed explanation of how the offeror will accomplish the ADCTO requirements specified in Attachment Air Data Computer Task Order PWS with minimal risk to the

Government.

2) For depicting staffing, offerors shall provide the following information:

a) Complete list of labor categories in attached TEP PRICING MATRIX, number of personnel proposed for each labor category, and associated labor hours deemed necessary to perform the requirements. Clearly depict in a staffing chart the total number of productive man-hours and associated Full Time Equivalents (FTE's) for each proposed labor category. All cross utilization of the labor force shall be clearly explained and depicted.

b) Job qualifications associated with each key labor category to demonstrate the skills necessary for each labor category proposed to meet or exceed the qualifications required in the ADCTO.

4.0 VOLUME 2, FACTOR 2: PAST PERFORMANCE

4.1 Specific Content

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified.

This may allow the offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required. Categorize the relevant information into the specific Technical subfactors and Price Proposal Factors used to evaluate the proposal.

Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Section L, Attachment 1. This information is required on the offeror and all subcontractors, teaming

11 | P a g e partners, and/or joint venture partners who are proposed to perform a significant portion of the effort. This is based on the total evaluated price, or perform aspects of the effort the offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.

Along with the information required in this paragraph, the offeror shall submit a consent letter executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. For each identified effort for a commercial customer, the offeror shall also submit a client authorization letter, authorizing release to the

Government of requested information on the offeror's performance.

4.2 Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc.

In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent 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 less than 3 pages.

4.3 Proposal Submittal Information

Offeror shall submit Past Performance Volume II, 2 weeks after RFP release date. PPI sheets shall be submitted using the EZ Source PPI Tool (reference Section L, Attachment

1: Project Submissions). All PPI sheets shall contain contract number and/or task order number and shall be saved as Access Database files (.accdb).

5.0 VOLUME 3, FACTOR 3: PRICE PROPOSAL

5.1 General Information

5.1.1 Cost/Price Reasonableness, Realism and Balance

This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness, realism (where identified), and balance of your proposed price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. The burden of proof for credibility of proposed costs/prices rests with the offeror.

12 | P a g e

5.1.2 Estimating Techniques and Methods

When responding to the Cost/Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating

Relationships (CERs), commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop their estimates. If necessary, reasonable and supportable allocation techniques may be used to spread hours and/or costs to lower levels of the work breakdown structure (WBS).

5.1.3 Cost/Price Data

Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your 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 Cost/Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

5.1.4 Cost or Pricing Data Requirements

If, after receipt of proposals, the CO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit additional cost or pricing data.

5.2 Required Attachments

5.2.1 Total Evaluated Price (TEP) Pricing Matrix

Offerors shall populate the pricing and cost cells in Section J Attachment, TEP Pricing

Matrix per the instructions in the Matrix. The offeror shall complete only green shaded cells in both the FFP and CPFF tabs within the worksheet. Do not alter the MS Excel formatting. The Government will use this worksheet to calculate the TEP. The offeror shall complete and return this in MS Excel 2007 format.

5.2.2 Evaluation of Compensation for Professional Employees

The offeror shall submit a professional employee compensation plan meeting the requirements of FAR 52.222-46, Evaluation of Compensation for Professional

Employees. The offeror shall detail the base labor rate, fringe, all other burdens, and profit/fee contained in labor rates to facilitate comparisons in accordance with FAR

52.222-46.

5.2.3 Air Data Computer Task Order Price Proposal

The offeror shall provide a price proposal for its ADCTO submission IAW paragraph 3.3 above. The offeror shall complete the ADCTO tab in the TEP Pricing Matrix (see 5.2.1 above) with hours and any amounts proposed under CLINs 0005 and 0006. The offeror file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b154031

13 | P a g e shall provide a separate Basis of Estimate for hours and amounts proposed for CLINs

0005 and 0006 if any. This Basis of Estimate shall detail how these amounts were calculated and include applicable verification of amounts (i.e., invoices, proposals, historical pricing, etc.).

5.2.4 Approved Accounting System

The offeror shall provide evidence of Government approval of its accounting system along with all subcontractors who will be issued other-than Fixed Price subcontracts.

6.0 VOLUME IV, FACTOR 4: CONTRACT DOCUMENTATION

6.1 Executive Summary

The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

6.2 Table of Contents

Include a master table of contents of the entire proposal.

6.3 Model Contract/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 Model Contract, and Sections A through K.

6.3.1 Section A - Solicitation and Model Contract Form

Complete blocks 12, 13, 14, 15A, 15B, 15C, and include signed amendments to the solicitation (if any). Signature by the offeror on the SF 33 constitutes an offer, which the

Government may accept.

6.3.2 Section B - Services and Prices

Supplies or Services and Costs or Prices: Do not input pricing information in Section B of the Model Contract and Solicitation. All required prices shall be proposed in the TEP

Worksheet Section J Attachment- TEP Worksheet.

6.3.3 Section I - Contract Clauses

Offerors shall complete all required clause fill-ins.

14 | P a g e

6.3.4 Section K - Representations, Certifications, and other Statements of Offerors

Complete representations, certifications, acknowledgments and statements. Offeror must have filled out an online FAR provision 52.204-8 Annual Representations and

Certifications (May 2014), Online Reps and Certs at http://www.sam.gov.

6.3.4.1 TCIR/DART Rates

Submit Annual Total Case Incident Rate (TCIR) and Days Away, Restricted and/or

Transferred (DART) Rates using the Summary of Work-Related Injuries and Illnesses, OSHA Form 300A. Offerors that do not have annual TCIR and DART rates established shall submit consecutive recording data or other comparable data from a recognized agency such as workers compensation, insurance rates, etc., for the time period the offeror does possess.

6.3.5 Attachments

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 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, 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 in accordance with FAR 52.219-9.

6.4 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 subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and

15 | P a g e specific requirements of the solicitation. This information shall be provided in the format and content of Table 7.2.

Table 7.2 - Solicitation Exceptions

Solicitation

Document

Page/

Paragraph

Requirement/

Portion Rationale

PWS, 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

6.5 Other Information Required

6.5.1 Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the

Government.

6.5.2 Government Offices

Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office.

Also, provide the name and telephone and fax number for the Administrative Contracting

Officer (ACO).

6.5.3 Company/Division Address, Identifying Codes, and Applicable Designations

Provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract 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.

Section L, Attachment 1: Project Submissions

Provide the information requested in this attachment for each contract/program (limit of three) being described. Provide frank, concise comments regarding the contracts you identify. Attachment “Past

Performance Questionnaire” has the “(fill in)” text that may be deleted; otherwise limit responses to the space provided.

17 | P a g e

18 | P a g e

Section L Attachment “2”

Instructions to Offerors

Past Performance Information (PPI) for Offerors

Offerors must use the PPI Tool (Use latest version from FBO.gov) in order to electronically submit the PPI portion of the Past Performance Volume in accordance with the RFP.

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 FedBizOpps (https://www.fbo.gov/) website.

2. Find the solicitation posting.

3. Locate the “ppi tool” link from the “All Files” column on the solicitation’s “Notice Details” tab .

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. XYZCompanyFA861710R6158.accdb).

Note: PPI Tools saved in Microsoft Office versions 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 .

3. 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. XYZCompanyFA861710R6158.accdb).

https://www.fbo.gov/

19 | P a g e

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

Figure 2: Setup Pop-Up

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

Figure 3: Application Setup Screen

Note: Once the Offeror’s Name and RFP Number have been entered they can be edited by selecting the “Edit Offeror and RFP Number” button from the “Contractor’s Menu”

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

Figure 4: Continue the Application Setup

7. Choose the appropriate option by selecting the corresponding radio button and then click the

“Next” button. The “Contractor’s Menu” displays.

20 | P a g e

Figure 5: Contractor’s Menu

8. Click the “Step 1: Set up Business Relationships” button to create a business relationship, if applicable, for each business entity 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

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

21 | P a g e

Figure 7: Enter New Business Relationship

10. 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 business entity

Responsibilities: Detail proposed responsibilities of specified business entity.

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

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

13. Click the “Step 2: Enter Past Performance Information (PPI)” button to enter the Past Performance Information. The “Past

Performance” screen displays.

Figure 8: Past Performance

14. Click the “New” button to enter Past Performance Information for the proposed acquisition.

An additional “Past Performance” screen displays.

22 | P a g e

Figure 9: Enter Past Performance Information

15. 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 business entity.

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:

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

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

23 | P a g e o Explain the differences in Contract Value, if applicable: Enter an explanation of the difference between the original contract dollar value and the revised value as of the time of PPI submission.

Period of Performance (mm/dd/yy) o Start Date: Input start date of contract.

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

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

o 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:

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

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

o ****If applicable: Provide information on performance 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 performance on this contract is relevant for each applicable factor or subfactor, as instructed under Past Performance in Section M of the RFP.

Include any unique aspects that demonstrate relevancy in this effort. Provide evidence to support such relevance to the requirements as described in the RFP.

Include relevant information concerning your compliance with FAR 52.219-8, Utilization of Small Business Concerns, on the contract you are submitting, if applicable.

Identify whether a subcontracting plan was required for the contract you are submitting. If one was required, identify in percentage terms the planned versus achieved goals during contract performance. Explain why goals were not met, if applicable:

POC & Key Individuals Tab

Key Individuals: Click the “New” button to specify any key individual or individuals who participated in this program or who may support the proposed acquisition. Also indicate their roles for both acquisitions, previous and current. To edit or delete an existing key individual, double-click an item from the list.

Note: In accordance with FAR 15.305(a)(2)(iii), relevant contract efforts performed by from key personnel may be evaluated. If you wish to include the past performance of individual key personnel, select the “New” button for each individual and fill out the necessary information.

24 | P a g e

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.

For commercial contracts provide points of contact fulfilling these same roles, if available.

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

17. 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 displays.

25 | P a g e

Figure 11: Submission Instructions

4. Follow the submission instructions. Hard copies of the pages generated from this tool shall be used in the hard copy of the past performance volume subject to the limitations outlined in this RFP and should be Tab 1 of the past performance volume.

Note:

Submit an electronic copy (e.g. CD) of the saved PPI database file with your proposal. If a prime contractor is submitting the file enter the filename as:

o prime contractor + RFP number + file extension (e.g.

XYZCompanyFA861710R6158.accdb)

If a subcontractor is submitting the file enter the filename as:

o subcontractor + RFP number + file extension (e.g.

ABCCompanyFA861710R6158.accdb)

Once the file is saved to a CD or any location that is marked as “Read-only,” it must first be saved to the desktop in order to read/edit the file.

Editing Offeror and RFP Number In order to edit the Offeror name and/or the RFP number identified during start-up, perform the…