SF_30_-_Amendment_01.docx

DOCX document 45 KB Posted

Attached to
Applications, Infrastructure, and Systems Support - Third Iteration (AISS III)
Solicitation number
FA4452-17-R-0003
Issued by

About this file

SF 30 - Amendment 01

View the file

Other files

File Type Posted
GATES_Estimated_Workload_(corrected).xlsx XLSX spreadsheet
Sys_Int_AISS_Estimated_Workload.xlsx XLSX spreadsheet
SF_30_-_Amendment_02.pdf PDF
AISS_Questions_Jun_15.docx DOCX document
ACAS_Estimated_Workload.xlsx XLSX spreadsheet
GATES_Estimated_Workload.xlsx XLSX spreadsheet
GCCS_Estimated_Workload.xlsx XLSX spreadsheet
AISS_Questions_8_Jun.docx DOCX document
GDSS-AVORM-MACD_Estimated_Workload.xlsx XLSX spreadsheet
GDSS-AVORM_Estimated_Workload.xlsx XLSX spreadsheet
AISS_III_-_RFP_Atch_4_-_Pricing_Attachment_AMENDMENT_01.xlsx XLSX spreadsheet
AISS_Questions_7_Jun.docx DOCX document
NDA.docx DOCX document
AISS_III_-_RFP_-_Addendum_to_FAR_52.212-1,_Attachment_4_-_PPQ.docx DOCX document
AISS_III_-_RFP_Atch_3_-_DD254.doc DOC document
AISS_III_-_RFP_Atch_2_-_QASP.docx DOCX document
AISS_III_-_RFP_Atch_4_-_Pricing_Attachment.xlsx XLSX spreadsheet
AISS_III_-_RFP_Exhibit_A_-_CDRL_Portfolio.pdf PDF
AISS_III_-_RFP_-_Addendum_to_FAR_52.212-1,_Attachment_2__-_Sample_Consent_Letter.docx DOCX document
AISS_III_-_RFP_-_Addendum_to_FAR_52.212-1,_Attachment_1_-_PPIS.docx DOCX document
AISS_III_-_RFP_-_FA4452-17-R-0003.docx DOCX document
AISS_III_-_RFP_-_Addendum_to_FAR_52.212-1,_Attachment_5_-_PPQ_Cover_Letter.pdf PDF
AISS_III_-_RFP_-_Addendum_to_FAR_52.212-1,_Attachment_3_-_Sample_Client_Authorization_Letter.docx DOCX document
AISS_III_-_RFP_Atch_1_-_PWS.docx DOCX document
Show all 24

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

FA4452-17-R-0003

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been modified:

ADDENDUM TO FAR 52.212-1

ADDENDUM TO FAR 52.212-1 INSTRUCTIONS TO OFFERORS (ITO) – COMMERCIAL ITEMS

1.0 General Instructions

(a) The offeror’s proposal must include all data and information requested by this 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 (CDRLs). Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

(b) The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the government’s requirements but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the offeror's proposal.

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

(d) The solicitation issue date of 19 May 17 and offer due date of 26 Jun 17 are specified in blocks 6 and 8, respectively, of the solicitation. The offeror shall make a clear statement in Volume IV that the proposal is valid through the anticipated contract start date.

(e) In accordance with FAR Subpart 4.8 (Government Contract Files), the government will retain one copy of all unsuccessful proposals. Once offerors proposals are uploaded into the contract file, the CDs will be destroyed.

1.1 General Information

1.1.1 Point of Contact

The Chief of acquisition Flight, Ms. Jennifer Gasparich, and the Contracting Officer (CO), Maj John Hofmann are the points of contact for this acquisition. Address any questions or concerns you may have to the CO via email at john.hofmann@us.af.mil. The Flight Chief and CO can be reached via mail at:

763 SCONS/ PKA

Attn: Solicitation FA4452-17-R-0003 Attn: Jennifer Gasparich / Maj John Hofmann 507 Symington Drive, Room W202 Scott AFB IL 62225-5022

1.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.503. 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.

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

1.1.4 Electronic Reference Documents

All referenced documents for this solicitation will be available to contractors on the FBO website at fbo.gov.

1.1.5 Oral Presentations

Oral presentations will not be permitted.

1.1.6 Communications

Exchanges of source selection information between government and offerors will be controlled by the CO. Email may be used to transmit such information to offerors 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. Otherwise, source selection information will be transmitted via mail or picked up/dropped off by a local contractor representative.

1.1.7 Amendments to Solicitation

If this Request for Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged. Offerors shall acknowledge receipt of any amendment to this request by the day and time specified in the amendment(s).

1.1.8. Use of Non-Government Personnel in Source Selection

(a) It is the government’s intent to utilize non-government advisors in the conduct of this source selection. Offerors are advised that data, including proprietary data, submitted to the government in response to this solicitation will be released to non-government advisors for review and analysis.

(b) The non-government advisors who will be involved in this source selection and the manner in which they will be involved are as follows:

MITRE Corporation 505 Corporate Center Drive Shiloh, IL 62221

Employees of this firm will serve as non-voting advisors to the Source Selection Evaluation Board (SSEB). These advisors may be required to provide advice regarding proposal strengths and weaknesses but will not determine ratings or rankings of offerors’ proposals. Non-government advisors will be prohibited from reviewing Past Performance information. All participants have signed nondisclosure agreements.

(c) Submission of offeror’s proposal in response to this request for proposal will constitute acceptance of non-governmental personnel participation as advisors in the source selection. If the offeror has any objection to non-government advisors access to its proposal information, the offeror shall provide grounds and justification for its objections to the Contract Specialist. The CO will then make a determination whether the non-government advisor(s) shall be permitted to participate in the source selection. The Contract Specialist will inform objecting offeror of the final determination, and, if the use of non-government advisors has been changed, will inform all offerors of the change.

1.2 Organization/Number of Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1.2 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 1.2. The volumes identified in the table shall be on a single CD. The contents of each proposal volume are described in the ITO paragraphs as noted in the table below:

Table 1.2 - Proposal Organization

VOLUME
ITO Paragraph

Number

VOLUME TITLE
COPIES
PAGE LIMIT
I
2.0
Executive Summary
1
10
II
3.0
Technical/Technical Risk
1
50*
III
4.0
Past Performance
1
**
IV
5.0
Contract Documentation and Price
1
No Limit

*Plans required as part of the submission carry a 10-page limit that do not count against the total 50-page limit.

**Limit past performance to five pages per past/present contract submitted. Complete a Past Performance Information Sheet (PPIS) (Addendum to FAR 52.212-1, Attachment 1) for each contract submitted. No more than five PPQs (total) for each offeror/team will be evaluated.

1.2.1 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and disregarded. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Each page shall be counted except the following: blank pages, cover pages, table of contents, tabs, glossaries, resumes of key personnel, and those noted in the Proposal Organization Table (Table 1.2) as unlimited.

1.2.1.1 Page Size and Format

(a) A page is defined as each face of a sheet of paper containing information. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs.

(b) Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 8.5 x 11 inches in size. For tables, charts, graphs and figures, the text shall be no smaller than 10 point.

1.2.2 Cost or Pricing Related Data

All cost or pricing data shall be addressed ONLY in the Price Proposal and Contract Documentation Volume. Cost trade-off information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions.

1.2.3 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 not permitted.

1.2.4 Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume.

1.2.5 Title Page

Each volume must include a title page. The title pages must show:

(a) Solicitation Number

(b) Name, address, telephone numbers and e-mail address of the offeror

1.2.6 Glossary of Abbreviations and Acronyms

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

1.2.7 Tables and Figures

Include an indexed list of Tables and Figures. This index will not count against page limitations.

1.3 Electronic Offers

Only Electronic offers will be accepted. Each offeror is required to submit their proposal on a CD no later than the required proposal due date. The CD is the copy designated in Table 1.2 above. The outside of the CD or the CD jacket must be labeled to identify contents. The CD shall be submitted in a format readable by Microsoft (MS) Office 2013 suite of applications.

1.4 Distribution

Proposals shall be addressed to the following and mailed or hand carried to:

763 SCONS/PKA

Attn: Solicitation FA4452-17-R-0003 Attn: Jennifer Gasparich and Maj John Hofmann 507 Symington Drive, Room W202 Scott AFB IL 62225-5022

Access to Scott AFB for Delivery of Hand Carried Proposals: Offerors are cautioned that when hand-carrying proposals individuals not affiliated with this installation must obtain visitors’ passes prior to entrance. The Shiloh gate has been designated as the “Visitor’s Control Center.” Some delays can be anticipated for visitors to process through the “Visitor’s Control Center” and offerors should allow sufficient time to obtain visitors’ passes. Each visitor must have an on-site sponsor to obtain a visitor’s pass. Please contact Maj John Hofmann at (618) 256-9826 for more information.

Proposals are due by 12:00pm Central on the due date. Late proposals will be processed in accordance with FAR 52.212-1(f) Late Submissions, Modifications, Revisions, and Withdrawals of Offers.

2.0 Volume I Executive Summary

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

2.1 Narrative Summary

The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding price. The salient features should tie in with Addendum to FAR 52.212-2 Evaluation – Commercial Items. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

2.2 Table of Contents

Include a master table of contents of the entire proposal.

3.0 Volume II - Technical Volume

3.1 General

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Addendum to FAR 52.212-2 Evaluation – Commercial Items. 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.

3.2 Format and Specific Content

3.2.1 Technical

In the technical volume, address your technical solution for meeting or exceeding the government’s minimum performance or capability requirements of each technical subfactor.

3.2.1.1 Technical Risk

Address Technical Risk associated with those aspects of your proposed technical approach you consider to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased government oversight, or the likelihood of unsuccessful performance by submitting a Risk Matrix. Classify each risk in accordance with DoD Source Selection Procedures Table 2B, Technical Risk Rating (listed in Addendum to FAR 52.212-2). Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: PWS), whether or not those requirements are identified as subfactors. Propose a realistic "workaround" or risk mitigators for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation.

3.2.2 Volume Organization

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

(1) Title Page

(2) Teaming Matrix

(3) Table of Contents

(4) List of Table and Figures

(5) Glossary of Abbreviations and Acronyms

(6) Technical Approach (Subfactor One)

(7) Staffing Approach (Subfactor Two)

(8) Configuration Management Approach (Subfactor Three)

(9) Risk Matrix

3.2.3 Teaming Matrix

A Teaming Matrix (if applicable) shall be submitted with the Technical Approach – Volume II. Teaming arrangements are encouraged. Offerors shall describe which tasks each member of their teaming arrangement will be responsible for and indicate any potential OCI concerns and mitigations.

3.2.4 Subfactor One – Technical Approach

Each offeror shall provide an integrated technical solution. The technical solution must represent the offeror’s approach to meeting overall PWS requirements. Identify any best practices/innovations proposed. Required documents for the offeror’s technical approach include a draft quality plan, draft testing plan, and draft training plan with each having a 10-page limit. These documents will not count against the 50-page technical volume limit. Additional requirements for Subfactor One – Technical Approach are described in Addendum to FAR 52.212-2

3.2.5 Subfactor Two – Staffing Approach

Each offeror shall provide a plan with their approach to overall staffing of and transition to AISS III. Required documents for each offeror’s staffing approach include a staffing plan and a transition plan with each having a 10-page limit. These documents will not count against the 50-page technical volume limit. Additional requirements for Subfactor Two – Staffing Approach are described in Addendum to FAR 52.212-2.

3.2.6 Subfactor Three – Configuration Management Approach

Offerors shall provide their approach to overall Configuration Management and Asset Management. Required documents for each offeror’s configuration management approach include a draft configuration management plan and a draft asset management plan each with a 10-page limit. These documents will not count against the 50-page technical volume limit.

Addendum to FAR 52.212-2 describes the measures of merit for each Technical subfactor.

4.0 Volume III - Past Performance

4.1 General

Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Addendum to FAR 52.212-1, Attachment 1. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to 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 (Addendum to FAR 52.212-1, Attachment 2) 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 (see sample at Addendum to FAR 52.212-1, Attachment 3), authorizing release to the government of requested information on the offeror's performance.

4.2 Early Proposal Information

Each offeror is requested to submit the information shown in Addendum to FAR 52.212-1, Attachment 1 for each relevant contract 10 calendar days prior to the date set for receipt of proposals. Failure to submit early proposal information will not result in offeror disqualification.

As soon as practicable, offerors shall e-mail the Past Performance Questionnaire (PPQ) (Addendum to FAR 52.212-1, Attachment 4) with section 1 completed and the Past Performance Questionnaire Cover Letter (Attachment 5) to the points of contact (POCs) the offeror has listed in the PPIS (Addendum to FAR 52.212-1, Attachment 1). The POCs listed in the PPIS’s should represent the individuals most knowledgeable about the offeror’s performance on the identified contract or program, such as the following: (1) Contracting Officer’s Representative; (2) Program/Project Manager; (3) Contracting Officer. The POCs will complete the questionnaires and forward them by email directly to the CO, Maj John Hofmann at john.hofmann@us.af.mil and to Jennifer Gasparich at jennifer.gasparich@us.af.mil. RESPONDENTS TO THE QUESTIONNAIRES SHALL NOT SEND THE COMPLETED INFORMATION SHEETS BACK TO THE OFFEROR. The Source Selection Evaluation Board (SSEB) will conduct follow-up with any POC as necessary. The SSEB will evaluate no more than five PPQs (total) for each offeror/team. If more than five PPQs are received, a maximum of five will be evaluated in the order in which they were received via mail or email by the Contract Specialist. PPQs should be submitted to the Contract Specialist 10 calendar days prior to the date set for receipt of proposals.

4.3 Relevant/Recent Contracts

Submit information in accordance with Addendum to FAR 52.212-1, Attachment 1: Past Performance Information Sheets shall consist of no more than five contracts that you consider most relevant in demonstrating your team’s ability to perform the proposed effort. A task order will count as a single contract. As such, multiple task orders from an IDIQ contract will count as multiple contracts against the five contract limit. A contract is considered recent if it is an ongoing contract or if it was completed within three years of the date of issuance of the solicitation. As stated above, no more than five contracts total shall be submitted for each offeror/team. Include rationale supporting your assertion of relevance as it relates to each relevancy criteria in the applicable relevancy rating table. For a description of the characteristics or aspects the government will consider in determining recency and relevance, see Addendum to FAR 52.212-2. The government may consider past performance in the aggregate in addition to on an individual contract basis. Contractors without a record of relevant past performance or for whom information on past performance is not available or is so sparse that a confidence assessment cannot be reasonably assigned will not be evaluated favorably or unfavorably on past performance and as a result, will receive a “Neutral Confidence” rating for the Past Performance factor.

4.3.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 factor used to evaluate the proposal.

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

5.0 Volume IV – Contract Documentation and Price

5.1 Contract Documentation

5.1.1 RFP Standard Form 1449

Offeror is required to complete blocks 17a, 17b, 30a, 30b, and 30c of the RFP, Standard Form 1449. By completing blocks 17a, 17b, 30a, 30b, and 30c of the Standard Form 1449 the offeror accedes to the contract terms and conditions as written in the RFP. RFP Certifications – Complete and submit all required information (fill-ins, signatures, etc.) found in the provisions FAR 52.212-3 and DFARS 252.212-7000.

5.1.2 SF 1449 Continuation Sheet – Price

The offeror shall insert its proposed unit and extended prices based on the quantities for each Firm Fixed Price (FFP) CLIN (Refer to Addendum to FAR 52.212-2). Utilize “Attachment 4 - Pricing Attachment for funding traceability” to arrive at CLIN prices. Price shall reflect all prices associated with providing the AISS III function. All prices shall be rounded as described in paragraph 5.2.5 below.

5.1.3 Technical Proposal Checklist

There is no requirement to submit a Technical Proposal Checklist.

5.1.4 Attachments

Attachments to the RFP include:

Attachment 1 – Performance Work Statement (PWS) Attachment 2 – Quality Assurance Surveillance Plan (QASP) Attachment 3 – DD Form 254 Attachment 4 – Pricing Attachment for funding traceability.

Each offeror is required to complete sections 6a, 6b, 6c, 7a, 7b, and 7c of the DD Form 254. The DD254 shall be submitted in Volume IV, Contract Documents and Price.

5.1.5 Exceptions to Solicitation Requirements

Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or 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 specific requirements of the solicitation. This information shall be provided in the format and content of Table 5.1.

Table 5.1 - Solicitation Exceptions

Solicitation Document Page/ Paragraph Requirement/ Portion Rationale and Impact (if any)

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

5.2 Other Information Required

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

5.2.2 Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division's street address; CAGE code; DUNS code; TIN; and size of business (large or small). This same information must be provided if the work for this contract will be performed at any other location(s).

5.2.3 Price Completeness and Reasonableness

The offeror shall submit pricing information to support the completeness and reasonableness of their proposed prices for all CLINs, including phase-in and phase-out. The pricing information submitted should fully support PWS requirements for each major functional element specified in the PWS. A breakdown should also be provided for price traceability which shows the skill mix, labor categories, position descriptions, estimated number of hours, and estimated fully burdened labor rates. Information shall also be segregated by the performance periods and a total price for each CLIN as specified in the solicitation. Information shall also show the consolidated total price for performance.

Surge CLIN pricing shall only include the labor categories, position descriptions, and fully burdened labor rates that are provided for the other tasks in the requirement. Hours will be negotiated at the time of utilization. Not to exceed amounts for Surge are provided in the Pricing Attachment for a frame of reference as to the extent of which Surge use is estimated.

Note that incomplete, unreasonable, or unbalanced 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 unreasonableproposal. Offers should be sufficiently detailed to demonstrate their reasonableness. The burden of proof for credibility of proposed prices rests with the offeror.

5.2.4 Price Data

Data beyond that required by this instruction shall not be submitted unless you consider it essential to document or support your 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 Contract Documentation and Price Volume.

5.2.5 Rounding

All dollar amounts provided shall be rounded to the nearest penny. All loaded labor rates shall be rounded to the nearest penny. The total dollar amounts for all CLINs shall be exactly divisible by each respective CLINs quantity.

5.2.6 Government Furnished Property (GFP)

There is no GFP for this contract. The government will provide items to the contractor to use in performance of the contract. All items provided are considered incidental to place of performance. A list of property will be given to the awardee prior to the start of performance. Refer to the PWS for a description of items incidental to the place of performance. The government currently has approximately 182 workstations available for AISS III contractor support; however this number is subject to change. This number DOES NOT constitute the number of bodies required to provide the AISS III services. It is only provided for informational purposes.

5.2.7 Organizational Conflict of Interest (OCI)

At time of submitting proposal, offeror must either state affirmatively it has no OCI issues, or it must submit an Organizational Conflict of Interest Identification and Mitigation Plan (OIMP). If the award of this contract either creates or has the potential to create an actual or perceived OCI by the contractor, its employees, or subcontractors, the offeror shall submit an OIMP at the time of technical proposal. The OIMP shall include, among other information, processes and internal controls necessary to identify, capture, and mitigate OCI activities. The government-accepted OIMP shall be incorporated by reference into a resultant contract.

5.2.8 Security Clearance

All contractor personnel will be required by the DD Form 254 to have SECRET clearance at contract award. Offerors shall address this requirement in Volume IV.

Attachments to Addendum to FAR 52.212-1:

(1) Past Performance Information Sheet (PPIS)

(2) Consent Letter

(3) Client Authorization Letter

(4) Past Performance Questionnaire (PPQ)

(5) PPQ Cover Letter

(End of Summary of Changes) image1.wmf

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