SECTION_L_20180212.docx

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

1 GENERAL INFORMATION

To assure timely and equitable evaluation of proposals, offerors must follow the instructions contained herein. Offerors are required to meet all Request for Proposal (RFP) requirements, including 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 RFP terms and conditions and provide complete accompanying rationale. Offerors are advised that taking exception to any requirements specified in this RFP may result in the Government finding the proposal unacceptable. Failure to meet a requirement may result in an offer being ineligible for award. The response shall consist of two separate volumes: Contract Documentation and Price Proposal (Volume 1) and Technical Proposal (Volume 2). Proposals shall be delivered in hardcopy and electronic form.

1.1 Restrictions on Contact. In accordance with (IAW) Air Force Federal Acquisition Regulation Supplement (AFFARS) Mandatory Procedure (MP) 5315.3 - Source Selection, Chapter 1.4, Paragraph 1.4.2.2.7, all appropriate organizations will be notified concurrent with issuance of this RFP announcing that a source selection is in progress for Global Positioning System (GPS) Engineering, Analysis & Remote Site Sustainment II (GEARSS II).

1.2 Point of Contacts. The primary point of contact is the Procuring Contracting Officer (PCO). The PCO controls all contact or exchanges with offerors or respondents and is the only person authorized to release source selection information before and after contract award. The secondary point of contact is the Contract Specialist (CS). Address all questions or concerns to both PCO and CS using the following contact information:

Stephanie M. VanDine Procuring Contracting Officer Robert E. Woolfolk Contract Specialist

AFSPC SMC/PKLG

1050 East Stewart Ave. Bldg. 2025 Peterson AFB, CO 80914-2902

AFSPC SMC/PKLG

1050 East Stewart Ave. Bldg. 2025 Peterson AFB, CO 80914-2902

Email: stephanie.vandine@us.af.mil Phone: (719) 556-2086 Email: robert.woolfolk@us.af.mil Phone: (719) 556-2856

1.3 Discussions. The Government intends to evaluate proposals and award a contract without discussions. If during the evaluation period, it is determined to be in the best interest of the Government to hold discussions, offeror responses to Evaluation Notices (ENs) and the Final Proposal Revision (FPR) will be considered in making the source selection decision.

1.4 Discrepancies. If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall notify the PCO in writing within seven calendar days after RFP and/or amendment release. Offeror shall provide supporting rationale as well as the remedies the offeror is asking the PCO to consider as related to the omission or error.

1.5 Non-Government Advisors. All data reserved in response to this RFP that is marked or designated as corporate or proprietary information will be fully protected from release outside the Government. Offerors are advised that responses submitted to the Government may be released to a Systems Engineering Technical Assistance (SETA) contractor, Booz Allen and Hamilton, for review. Respondents shall expressly state their objection to release of that information to the Non-Government Advisor. The Government will consider no response as consent to release that information to the SETA contractor.

2 PROPOSAL SUBMISSION

2.1 Method of Timely Submission. Both hardcopy and electronic copy shall be by hand carried (preferred method) or mailed to the address identified in Paragraph 1.2 to the PCO or CS. If using a courier, submit the name of the individual hand-carrying the proposal 24 hours in advance to the PCO or CS. The courier will be required to provide identification at the time of delivery. The delivered package(s) shall be labeled "To Be Opened by Addressee Only." These volumes must be received by the PCO or CS no later than the date and time specified in the final RFP FedBizOpps posting.

2.2 Proposal Delivery. Due to Peterson Air Force Base's (PAFB) mail security processes, the PCO cannot guarantee that mailed proposals will be processed and received by the proposal deadline. Therefore, the Government strongly encourages the offeror to hand-carry the required documents and information. Please call the PCO or CS at least two hours prior to your anticipated arrival time to ensure there will be authorized personnel available to receive your proposal. Offeror should speak personally with the PCO or CS, and not rely on voicemail.

2.3 Access to Base. Contractor personnel hand-delivering proposals are advised that they may be unable to access PAFB without a valid U.S. Uniformed Services Identification Card or Department of Defense (DoD) Common Access Card. The Pass and ID office is located at the West Gate, off of Powers Blvd. Offerors are advised that vehicles may be subjected to random searches and unexpected delays entering PAFB and should plan accordingly.

3 PREPARATION INSTRUCTIONS AND PROPOSAL FORMAT

This section provides general guidance for preparation of proposals as well as specific instructions on format and content of proposals. The offeror’s proposal must include all data and information requested and must be submitted IAW these instructions. Failure to do so may adversely affect the proposal evaluation. A proposal sufficiently documented to support performance in a complete, orderly, detailed manner will enable the Government to perform a thorough and fair evaluation.

3.1 Bidder’s Library. Unclassified for Official Use Only (FOUO) documents are available via Digital Versatile Disc (DVD). Offerors may request the DVD no later than 15 business days prior to proposal submission due date. Offerors shall submit a written request and a valid Attachment 7: DD Form 2345, Militarily Critical Technical Data Agreement to the PCO and CS prior to receipt of disk. Offerors must fill out, sign, and send to the appropriate office listed at the top of the form. NOTE: This process may take up to five business days for approval. After the form is signed by the DoD Official and returned to the offeror, the offeror will send the completed form with a request for the DVD to the PCO and CS. The DVD can be picked up at the address identified in Paragraph 1.2 (preferred method). If an offeror requests the DVD to be shipped, offeror shall provide mailing address.

3.2 Proposal Clarity. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation of the offeror's capabilities and for substantiating the validity of stated claims. The offeror's proposal shall not simply rephrase, reiterate, or restate the Government's requirements, but rather shall provide convincing rationale to describe the requirements and address how the offeror intends to meet the requirements. The offeror shall assume that the Government has no prior knowledge of its capabilities, facilities and experience, and will base its evaluation on the information presented in the offeror's proposal.

3.3 Alternate Proposals. The Government will not accept or consider alternate proposals.

3.4 Classified Information. No classified information shall be included in offeror’s proposal.

3.5 Restriction on Disclosure and Use of Data. Proprietary information submitted in response to this RFP is restricted from unauthorized disclosure as required by 41 United States Code (U.S.C.) § 2102. Apply all appropriate markings including those prescribed IAW Federal Acquisition Regulation (FAR) 52.215-1(e), Restriction on Disclosure and Use of Data.

3.6 Separate Volumes. The offeror's proposal shall consist of two separate volumes: a Contract Documentation and Price Proposal (Volume I) and a Technical Proposal (Volume II). The offeror shall prepare the proposal volumes and its contents as set forth in the following Proposal Organization, Table L-2. Each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. A cover sheet shall be inserted at the front of each volume, clearly marked with the offeror's name, volume number and title, and the RFP number. Each volume shall contain a detailed table of contents to delineate the Sections, Tabs and subparagraphs within that volume. The table of contents shall also include figures and tables. In the electronic version of the offeror’s proposal, each item in the table of contents shall be hyperlinked to the specific section and tab in the proposal. Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. The glossary shall also contain definitions in a separate section, as applicable. The table of contents and glossary are excluded from volume page limitations. Contract and price information will not be included in any other volume unless specifically instructed otherwise.

3.7 Solicitation Cross Reference Matrix. The offeror will provide a matrix indicating where the proposal meets the requirements of the RFP and Performance Work Statement including the applicable reference to the instructions in Section L and evaluation criteria in Section M. This matrix serves to highlight the evaluation areas in the proposal that are intended to meet the criteria for an award. If the matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over the matrix. The matrix is excluded from volume page limitations. Complete a table using a comparable format as shown below and include it on a cover page for both Volumes I and II:

Table L-1: Solicitation Cross Reference Matrix

Description PWS Para or RFP Section

Requirements List Proposal Mapping

3.8 Hardcopy Proposal

3.8.1 Binding and Labeling. The volumes identified in the table shall be separately bound in three-ring, loose-leaf binders. Staples shall not be used.

3.8.2 Page Size and Format. Page size will be 8.5 x 11 inches, not including foldouts, with at least 1-inch margins around the page perimeter. Pages will be single-spaced. Pages shall be printed as double-sided where possible (i.e., do not print on both sides if the next page would be a fold-out, tab break, etc.). Each printed side of information on a page of paper shall count as one page (i.e. single-sided pages count as one page, double-sided count as two pages). Fold-out pages will be counted as a single page for each 8.5 x 11 section.

3.8.3 Font. Use Times New Roman, with a font no smaller than 11 point with normal proportional spacing. Text embedded in graphics can vary from the font style and size requirement. If the offeror uses a different format (font size, margin, etc.), the Government reserves the right to adjust the proposal to fit the parameters of the format as stated in the RFP, and if this results in the proposal exceeding the page limitations in any one area, the Government will not consider those excess pages.

3.8.4 Page Limitations. Page limitations shall be treated as maximums (Reference Proposal Organization, Table L-2). Total page count will be based on the printed proposal submission. If page limitations are exceeded, excess pages will not be read nor considered in the evaluation of the proposal.

3.8.5 Electronic Copy Proposal. The content and page size of the electronic copy shall be identical to the hardcopy. If there is an inconsistency between the printed copy and the electronic copy, the printed document will take precedence. All volumes shall be included on one DVD. Use separate folders and ensure the file-naming convention is simple and straightforward to permit rapid location of all portions, to include factors, exhibits, annexes, and attachments, if any.

The offeror shall submit a complete copy of the proposal, including all proposal volumes and attachments, in electronic format, using non-rewritable DVD. Ensure the electronic documents stored on the discs can be opened and that all information is accessible on Government computers. Offeror shall "close the session" on all disks submitted to the Government so no changes can be made to the information. The electronic copy of the individual proposal elements shall be submitted in a format readable by Microsoft (MS) Word, MS Excel, MS PowerPoint or Adobe Acrobat Reader. The entire proposal package may be submitted in PDF format, and if used, must be formatted to allow the text to be selected (i.e. not as an image). Electronic copy of tables and spreadsheets shall be provided in MS Excel to allow Government evaluation and review of imbedded formulae and equations. In the Technical Proposal (Volume II), simple list tables can be included in the volume file (i.e. as part of the MS Word or Adobe Acrobat file) and need not be separately included in MS Excel format. Ensure formulas and clarifying notes used to calculate price are reflected in the spreadsheets. If files contain links, the links shall be maintained in all revisions.

4 VOLUME I, CONTRACT DOCUMENTATION AND PRICE

4.1 Volume I, Section 1: Contract Documentation

The purpose of this volume is to provide necessary data to the Government for preparing the contract document and supporting file. ONLY this volume shall contain the offeror's contractually related documentation and pricing information.

4.1.1 TAB 1: Company Cover Letter. The offeror will provide a concise offer cover letter signed by an authorized agent of the company. This offer cover letter will include the following:

4.1.1.1 Authorized Personnel. Offerors shall provide the name, title, telephone number, and E-mail address of the company/division point of contact regarding their proposal and who can obligate their company contractually. Offerors shall identify those individuals authorized to negotiate with the Government.

4.1.1.2 Company/Division Address, Identifying Codes, Small Business (SB) classification and Applicable Designations. Offerors shall provide the company/division’s street address, county, state and facility code; Commercial and Government Entity (CAGE) code and Data Universal Numbering System (DUNS) number; SB classification under NAICS 541330, Engineering Services, with a small business size standard of $38.5 million; and other applicable designations.

4.1.1.3 Subcontractor Representatives. Provide the name, title, and telephone number of the company/division point who are authorized to represent its company to the Government for subcontractors of the proposed effort.

4.1.2 TAB 2: Standard Form (SF) 33. The proposal acceptance period is 180 calendar days after the date set for receipt of proposals. The offeror shall make a clear statement in the signed offer (SF 33 Block 12) that the proposal is valid until this period has ended. Complete Blocks 12, 13, 15, 16, 17 and 18 of the RFP Section A, SF33. In doing so, the offeror accedes to the contract terms and conditions as written in the RFP Sections A through K. If this RFP is amended, all terms and conditions that are not amended remain unchanged. Offerors shall acknowledge receipt of any amendment to this RFP in Block 14 by the date and time specified in the amendment(s). Complete the necessary fill-ins and certifications in Sections I through K. For Sections C through I, the offeror shall submit only those pages that require a fill-in.

4.1.3 TAB 3: Data Rights. The Government has determined that its minimum needs for this acquisition include:

(a) Unlimited Rights to all noncommercial technical data listed in Table 1 of Attachment 3 where the phrase “Unlimited” is stated in column 4 of the row associated with that item of technical data;

(b) Government Purpose Rights to all noncommercial technical data and computer software listed in Table 1 of Attachment 3 where the phrase “Government Purpose” is stated in column 4 of the row associated with that item of technical data;

(c) Special License Rights to data other than technical data or computer software delivered to the Government described in Attachment 3 paragraph c.(3); and

(d) Special License Rights to review all data used by the Contractor to create any Contract Data Requirements List (CDRL) delivered under this contract to verify the currency, accuracy and completeness of the data contained in those CDRLs described in Attachment 3 paragraph c.(4).

(e) The Government made the determination that various CDRLs listed in Attachment 3 and Exhibit A must be delivered with Unlimited Rights after reviewing the tailored Data Item Descriptions referenced in those CDRLs consistent with the statutorily-defined categories in 10 U.S.C. § 2320(a)(2)(F)(i)(II). The Government made the determination that various CDRLs listed in Attachment 3 and Exhibit A must be delivered with Government Purpose Rights after reviewing the tailored Data Item Descriptions referenced in those CDRLs and determining which persons would need to use those deliverables for what purposes for what periods.

(f) Where there are valid reasons why an offeror must develop entirely at private expense or provide previously developed technical data or computer software under this contract, the offeror may not be required, either as a condition of being responsive to this RFP or as a condition for award, to sell or otherwise relinquish to the Government any proprietary right in technical data or computer software developed at private expense, except for the items identified at DFARS 227.7103-5(a)(2) and (a)(4) through (a)(9), DFARS 227.7203-5(a)(3) through (6) and DFARS 227.7102-1.

(g) Complete Table 1 in Attachment 3 in the following manner:

(1) With regard to items of technical data associated with cells in Column 3 of that table labeled as “Unlimited” or “Government Purpose”, leave those cells as-is. If, however, the offeror is not willing to sell Unlimited Rights Government Purpose Rights to an item labeled as such in Column 3, place the following character (“—“) in the corresponding cell in Column 3 of the table in Attachment 3 associated with that item.

(2) Insert a proposed price into each cell in Column 4 of that table for those items of data or computer software associated with that item’s corresponding cell in Columns 1-2. If the offeror is not willing to sell Unlimited Rights or Government Purpose Rights to an item labeled as such in Column 3, the offeror shall place the following character (“—“) in the corresponding cell in Column 4 of the table in Attachment 3 associated with that item to signify that the offeror is not willing to sell such rights to that item. The Government notes that it is entitled to Unlimited Rights in technical data and computer software associated with certain items delivered under this contract in certain situations, even where those items were not developed exclusively with Government funding (see DFARS 252.227-7013(b)(1)(ii, iv-ix) and DFARS 252.227-7014(b)(1)(ii-vi)).

(h) Complete Table 2 in Attachment 3 in the following manner:

(1) In Column 1 of that table, identify the CDRL number which will contain that commercial item technical data or computer software.

(2) In Column 2 of that table, identify the Data Item Title (Subtitle) of that CDRL

(3) In Column 3 of that table, identify the names of all vendors that will be supplying commercial item technical data or computer software in alphabetical order, the trade name(s) of the technical data or computer software applications(s) and the version number or issue date of that technical data or computer software application(s) (e.g., “Adobe Professional X”), and the license number(s) of that commercial item of technical data or computer software to be delivered or otherwise furnished as part of that CDRL. (Note: If the offeror proposes to deliver any Public Domain/Open Source Software (PD/OSS), the offeror shall only identify the base product in Column 3 – not the dependencies (e.g., PD/OSS licenses referenced in the proposed PD/OSS license)). The Government anticipates the offeror may propose to reuse previously delivered technical data and computer software in subsequent CDRL deliverables. If the offeror proposes to do so, all licenses associated with delivery of technical data or computer software in previous CDRL deliveries shall be listed in that column underneath that subsequent CDRL associated with those subsequent deliveries in addition to all licenses associated with delivery of technical data or computer software that were not the subject of previous CDRL deliveries.

(4) In Column 4 of that table, insert the quantity associated with the licenses relating to the delivery of commercial item technical data, commercial item computer software, or commercial item software documentation the offeror proposes to deliver to the Government in that CDRL or CLIN.

(5) In Column 5 of that table, insert a proposed price into each cell associated with that item’s corresponding cell in Columns 3-4 including only direct costs. (As used in this subsection, the term “direct costs” is defined as the cost proposed to be charged the offeror by a prospective subcontractor excluding any overhead or G&A the offeror anticipates expending to acquire that commercial item technical data, computer software or computer software documentation from that prospective subcontractor.)

(i) Complete Table 3 in Attachment 3 by inserting a proposed price into each cell associated with that item’s corresponding cell in Columns 1-2 including only direct costs. If the offeror is not willing to sell the rights described in Attachment 3 to an item listed in that table, the offeror shall place the following character (“—“) in the corresponding cells in Column 3 of that table associated with that item to signify that the offeror is not willing to sell such rights to that item.

(j) In subsection c.(4), replace the asterisk (**) with the estimated price for Special License Right Category B. If the offeror is not willing to sell the rights described in Attachment 3 for the rights described in that subsection, the offeror shall replace the asterisk (**) with the following character (“—“).

(k) In subsection d.(1), replace the asterisks ("**") with the offeror's name in uppercase letters;

(l) To ensure that the parties will maintain proper configuration control of all licenses throughout the performance of the resulting contract, create an “Attachment 8” with a separate tab for each vendor listed in Table 2. Insert into that separate tab one copy of every license listed in column 3 of Table 2 associated with any technical data or computer software the offeror will purchase from that vendor and subsequently deliver to the Government, including, but not limited to all licenses associated with any Public Domain/Open Source Software (PD/OSS)(including licenses to the base software application and all dependencies) proposed to be delivered to the Government under any CDRL listed in the order in which that license appears in that table. If an offeror proposes to deliver such software to the Government, the base license(s) associated with that PD/OSS may incorporate by reference licenses from dependent PD/OSS. Under such circumstances, to minimize duplication of such dependent licenses in Attachment 8 the offeror shall (1) list those dependent licenses on a separate sheet of paper immediately following a copy of the base license and indicate in which tab of Attachment 8 that/those dependent license(s) may be found, and (2) include only one copy of that/those dependent license(s) in a separate tab for that vendor. Each non-PD/OSS license contained in that Attachment 8 shall expressly refer to the identical vendor, trade name, version number and issue date of that technical data or computer software listed in Table 2. The Government expects that prior to inserting any proposed license into Attachment 8, the offeror will have carefully read the license to ensure that its terms and conditions are consistent with all requirements of this RFP. In this regard, Attachment 3.i includes an order of precedence clause placing the burden of compliance with those requirements on the prime contractor. In accordance with DFARS 227.7202-1(a), the Government is not required to acquire licenses to commercial computer software (or related documentation) where such licenses are inconsistent with Federal procurement law. Certain provisions in the Order of Precedence provision contained in Attachment 3.i, specifically, subsections (1), (3), (4), (5), and (7)-(13), summarize Federal procurement law. The Government cannot accept any offer that proposes to modify those subsections in a manner that is inconsistent with Federal procurement law.

4.1.4 TAB 4: Organizational Conflict of Interest (OCI). In accordance with FAR 9.5, Organizational and Consultant Conflicts of Interest, the PCO has analyzed the planned acquisition and determined that no known actual or potential OCI situations exist with respect to this RFP.

(a) The offeror shall perform its own OCI analysis and submit the results of that analysis as part of its proposal. Specifically, the offeror shall analyze the planned acquisition for actual or potential OCI situations associated with its or any of its teammate’s or subcontractor’s performance under any contract it or any of its teammates or subcontractors has been or may be awarded by any federal agency or other entity. The offeror shall describe in detail the methodology used to identify actual or potential OCI issues. If the offeror identifies any actual or potential OCIs with respect to the performance of itself or its subcontractors or teammates, the offeror shall provide an OCI Mitigation Plan to be incorporated as an attachment to any resulting contract. At a minimum, the plan shall address all of the items identified in the most current version of SMC’s OCI Mitigation Plan Checklist provided as an attachment to this RFP. Any proposed avoidance or mitigation techniques shall be consistent with FAR 9.5 and the most recent decisions of the Government Accountability Office and the U.S. Court of Federal Claims.

(b) If award is made to the offeror, the resulting contract may include an OCI limitation applicable to subsequent Government work, at either a prime contract level, at any subcontract tier, or both. During evaluation of proposals, the Government may, after discussions with the offeror and consideration of ways to mitigate or avoid identified actual or potential conflicts of interest, insert a clause or term and condition in the resulting contract which disqualifies the offeror from further consideration for award of future contracts.

(c) Resolution of OCI issues are treated in a manner similar to the PCO’s contractor responsibility determination. Any communications necessary to resolve OCI issues shall not be considered discussions. As such, the PCO may issue Evaluation Notices to the offeror prior to any decision to enter into discussions in order to resolve questions or concerns with the offeror’s OCI analysis or mitigation plan.

4.1.5 TAB 5: Responsibility. Provide information that presents a brief verifiable self-assessment in the areas of responsibility as described in FAR 9.104 as supplemented by DFARS and AFFARS. Elements of responsibility to address include but are not limited to, management of government property, capability, resources, competency, capacity, credit, integrity, perseverance, tenacity, and limitations on subcontracting. If responsibility information is provided in other proposal volumes, the offeror shall include a Cross Reference Matrix that indicates the Volume ID and Page # containing information supporting the elements of responsibility. NOTE: Inability to perform in compliance with the limitations of subcontracting clause FAR 52.219-14 is a matter of responsibility. In the event the PCO is unable to determine the offeror’s responsibility, procedures at FAR Part 19.6 will be used.

4.1.6 TAB 6: Service Contract Act. The Service Contract Act (SCA) Wage Determination for Primary Place of Performance in El Paso County, Colorado is attached and will be incorporated into the contract unless an offeror’s Collective Bargaining Unit has an agreement in place for the employees proposed.

If the contractor, subcontractors or other service providers assert their intent to utilize employees meeting the exemption criteria set forth in 29 CFR Part 541 for bona fide executive, administrative, or professional employees, the offeror shall submit a Total Compensation Plan setting forth salaries and fringe benefit package proposed for the professional employees, as required under FAR 52.222-46. The prime offeror should instruct its subcontractors to submit their total compensation plan directly to the PCO. The prime offeror shall also submit a list of the subcontractors to include points of contact and phone numbers who will be submitting professional employee compensation packages to the Government. The offeror shall verify consistency of the information provided in the Compensation Plan and data provided in the Price volume. The Government expects the information to be consistent. If the information is inconsistent, the Contractor shall explain the difference and provide reasons as to why the inconsistency should be accepted by the Government. The total compensation plan submitted in the proposal will not become part of the awarded contract. The plan shall set forth salaries and fringe benefits proposed for professional employees as prescribed in the instructions below:

(a) Total Compensation Plan. Provide the planned compensation for all professional employee labor categories proposed to perform the effort. Describe the job skills and qualification requirements associated with each identified labor category. The labor categories shall be identified by geographic location of contract performance. Provide the corresponding salary and quantified fringe benefits for each labor category. The fringe benefit data shall also include a description of the benefits offered, and to which professional employee category the fringe benefits would apply.

(b) Surveys and Studies. Provide the recent surveys and studies from professional, public, and private organizations (e.g., Watson & Wyatt, Economic Research Institute, Bureau of Labor Statistics, etc.) used to support the proposed salaries and fringes. Identify the source with the provided surveys and studies. If not using one of the sources listed above, explain the credibility of the source providing the surveys and studies.

(c) Offeror’s/subcontractor’s/teaming partner’s/joint venture partner’s Assessment. Discuss how the proposed total compensation plan package and the Surveys and Studies above are consistent and reflects a sound management approach, an understanding of the contract requirements, and will provide uninterrupted high-quality work. Also address how your proposed salary and fringe benefits will facilitate the recruitment and retaining of employees.

4.2 Volume I, Section 2: Price Proposal

All activities associated with the offeror's technical approach described in Volume II shall be priced within this volume in the Pricing section. The volume shall be prepared in an orderly format and in sufficient detail to enable the Government to make a thorough evaluation. Compliance with these instructions is mandatory and failure to comply may result in rejection of the proposal.

4.2.1 Price Reasonableness. Proposals should be sufficiently detailed to demonstrate price fair and reasonable. The PCO has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the PCO will review this determination and if, in the PCO's opinion, adequate price competition exists, no additional data will be requested. However, if at any time during this competition the PCO determines that adequate price competition no longer exists; offerors may be required to submit cost data to the extent necessary for the PCO to determine price is fair and reasonable. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. The burden of proof for credibility of proposed price rests with the offeror.

4.2.2 Pricing Summary. In addition to filling out Section B of the SF33, the offeror shall complete a table using a comparable format as shown below in Table L-3, Pricing Summary. The table shall be submitted in MS Excel to allow Government evaluation and review of imbedded formulae and equations. Additionally, insert proposed unit and extended prices in Section B for each Contract Line Item Number (CLIN), including all option periods. The extended amount must equal the whole dollar unit price multiplied by the number of units. All dollar amounts provided shall be rounded to the nearest dollar. Offerors shall also provide a cost breakdown of Prime and Subcontractor total price to demonstrate that in performance of this contract at least 50 percent of the cost of contract performance will be incurred by the Prime IAW FAR 52.219-14.

Table L-3: Pricing Summary

BASE PERIOD

OPTION PERIOD 1

OPTION PERIOD 2

OPTION PERIOD 3

OPTION PERIOD 4

OPTION PERIOD 5

OPTION PERIOD 6

Option to Extend Services (FAR 52.217-8)

TOTAL EVALUATED PRICE

CLINs 0001 + 1001 + 2001 + 3001 + 4001 + 5001 + 6001 + 7001 $ (Offeror fill-in)

TOTAL CONTRACT PRICE

All CLINs $ (Offeror fill-in)

COST OF CONTRACT PERFORMANCE BREAKOUT

4.2.2.1 The following instructions are to assist the offeror in submitting pricing information.

CLIN X001: Sustainment Services (FFP). Include the proposed price (including profit) for the base period plus all options. The proposed prices for CLIN X001 shall include the prices the offeror proposes for data rights in Attachment 3. The offeror shall include any transition costs for DCO in this CLIN respective to the year the DCO will transition (~Feb 2021). The Government anticipates a 90 day transition period for DCO activities.

CLIN X002: Other Direct Costs (Cost). DO NOT PROPOSE. The Government material, supplies and travel budget is intended for allowable costs directly related to mission support. The Government will provide an estimated amount for other direct costs the Government will reimburse. No additional cost breakout is required unless the offeror included related assumptions. The established baseline amounts include allowances for reimbursement of applicable contractor burdens. No profit or fee is allowed on these costs.

Examples of allowable reimbursable expenses may be initial and contract completion relocation expenses for OCONUS locations, travel required by the Government or terms of the contract, and materials and supplies. Examples of unallowable or unreasonable reimbursable expenses may be personal, some personnel or morale related expenses.

CLIN X003: Data (FFP). NOT SEPARATELY PRICED. Cost associated with this CLIN series is included in with its corresponding CLIN X001 and is not separately priced.

CLIN 0004: Phase-In Transition Services (FFP). Include the proposed price associated with its direct effort to become fully staffed/teamed, trained, located, and with qualification standards and otherwise fully prepared to meet performance standards. The offeror may propose a period of performance not to exceed 60 calendar days for this effort which allows time for the offeror to carry out their proposed phase-in plan and be fully stood up at the start of the base period of performance.

CLIN 0005: Phase-In Transition ODCs (Cost). The offeror shall include the assumption basis for the outlays the offeror anticipates will be Government cost reimbursable expenditures in support of the proposed Phase-In Plan (Technical Subfactor 1). Identify key or noteworthy expenses and general classifications with a reasonable approximation of cost if the offeror expects the outlays to exceed the Government estimated ODC budget. See CLIN X002 description for examples of allowable and unallowable expenses. No profit or fee is allowed on these costs.

CLIN 7001: FAR 52.217-8 Sustainment Services. DO NOT PROPOSE. To account for the option period(s) possible under FAR 52.217-8 (maximum six months), the Government will take the price for the final option period, i.e. CLIN 6001, and prorate it to a six-month value.

CLIN 7002: FAR 52.217-8 ODCs. DO NOT PROPOSE. To account for the option period(s) possible under FAR 52.217-8 (maximum six months), the Government will take the estimated ODC amount for the final option period, i.e. CLIN 6002, and prorate it to a six-month value.

4.2.3 Total Evaluated Price (TEP). For source selection evaluation purposes only, the TEP calculation shall include: CLINs 0001, 1001, 2001, 3001, 4001, 5001, 6001, and 7001 (possible 52.217-8 extension).

The TEP calculation excludes:

· The budgeted ODC amounts provided by the Government for CLINs 0002, 1002, 2002, 3002, 4002, 5002, 6002, and 7002;

· Deliverables identified under CLINs 0003, 1003, 2003, 3003, 4003, 5003, and 6003 are Not Separately Priced; and

· The proposed price for the Phase-In Transition Services CLIN 0004 and Phase-In Transition ODCs CLIN 0005 will not be included in the TEP calculation but shall be included in the offeror's price proposal.

4.2.4 Total Contract Price (TCP). The offeror shall include the TCP that includes the sum of the proposed prices for the following:

· Sustainment Services (FFP): CLINs 0001, 1001, 2001, 3001, 4001, 5001, 6001

· Other Direct Costs (Cost): CLINs 0002, 1002, 2002, 3002, 4002, 5002, 6002

· Phase-In Transition Services (FFP): CLIN 0004

· Phase-In Transition ODCs (Cost): CLIN 0005

5 VOLUME II, TECHNICAL

The offeror shall present a clear and concise description of its proposed approach for meeting the requirements of each technical subfactor. The Technical Proposal shall be specific and complete. Legibility, clarity, and coherence are very important. The offeror's responses will be evaluated against the Technical Proposal factors defined in Section M, Evaluation Factors for Award. The volume shall be prepared in an orderly format and in sufficient detail to enable the Government to make a thorough evaluation of the offeror's technical competence and ability to comply with PWS and CDRL requirements. Address as specifically as possible, the actual methodology the offeror would use for accomplishing/satisfying the requirements of each Technical Proposal factor. All the requirements specified in the RFP are mandatory. Any proposal that does not address all requirements or clearly meet the requirements will be deemed an alternate proposal and alternate proposals will not be considered. The offeror shall submit its Technical Proposal Volume as follows:

5.1 Volume II, Section 1: Executive Summary

The offeror shall provide a concise narrative Executive Summary of the entire proposal, excluding the price information while including technical aspects and a highlight of any key or unique features of the proposal. The summary shall also list all subcontract team members, a brief description of the team, and each team member's major area of responsibility. Any summary material presented here shall not be considered as meeting the requirements for any portions of any volume of the proposal.

5.2 Volume II, Section 2: Technical Proposal

The offeror shall address the proposed approach to meeting the requirements. An acceptable proposal will address each of the subfactors with sufficient detail to demonstrate both understanding of, and an acceptable approach/process/methodology toward, requirement fulfillment. The offeror shall identify and discuss all assumptions upon which its proposed approached is based.

Within each subfactor, the offeror shall discuss the extent to which the proposed technical approach has the potential to disrupt schedule, increase costs, degrade performance, increase Government oversight, or increase the likelihood of unsuccessful contract performance. Provide rationale for the impact on cost, schedule, and performance. Propose realistic mitigations for identified impacts that will eliminate or reduce impacts to an acceptable level. The proposal shall include a discussion of the following items to allow evaluation of the offeror's approach IAW Section M.

5.2.1 TAB 1: Subfactor 1 - Phase-In Transition. The offeror shall provide a single integrated Phase-in plan with schedule milestones. The plan shall include placement of personnel at all site locations with specific deployment, badging, training, security and travel requirements defined.

5.2.1.1 Provide a Phase-In Plan that describes the specific steps or methodology the offeror proposes to use to meet program phase-in task IAW PWS 3.8. Once the contract is awarded, the phase-in Plan will become part of the official contract file.

5.2.2 TAB 2: Subfactor 2 - Critical Staffing. The offeror shall provide a completed staffing plan (see Table L-4) demonstrating that the proposed number of Full Time Equivalents (FTEs) provide sufficient staff-hours to perform the requirements of the PWS. The plan shall present and explain the details of required operational- and troubleshooting-level experience, qualifications, security clearances and expertise with systems identified in the PWS. The table shall include the proposed labor category, PWS paragraph, which teammate, joint venture partner or subcontractor responsible for performing, and the number of FTEs proposed to satisfy each of the PWS paragraph requirements. Offerors shall also define the FTE equivalency in hours. The staffing table shall demonstrate that the proposed number of FTEs results in sufficient man-hours to accomplish all required tasks:

Table L-4: Staffing Plan Matrix Expandable Format

ELEMENT

Program Management

Labor Cat 1—Title/Grade Company Name Clearance Level Location

Labor Cat 2—Title/Grade

Additional Labor Category X, as needed

SubTotal Program Management

NAO Support

Labor Cat 1—Title/Grade

Labor Cat 2—Title/Grade

Additional Categories, as needed

SubTotal NAO Support

Total Hours

NOTE: Add additional function areas as necessary to the table above.

5.2.2.1 Provide the job requisitions for the technical and management staff the offeror proposes to perform paragraphs 3.2.1, 3.3.1, 3.3.10, 3.4.1, 3.4.3, 3.4.5, 3.5.1, and 3.6.1 of the PWS.

5.2.2.2 Provide clear evidence (e.g., hiring procedures, contingency offers to potential employees) that demonstrates the offeror has the ability to obtain the proposed staff to accomplish the skills required to perform all the tasks in the PWS.

5.2.3 TAB 3: Subfactor 3 – Technical Process Approach. The offeror shall:

5.2.3.1 Describe how the proposal satisfies the requirements of PWS 3.2, 3.3, 3.4, 3.5 and 3.6 that demonstrate a clear understanding of the technical and operational environment. The offeror’s methodology shall include, but not limited to: a description of each position, their roles and responsibilities and their interactions with customers and other agencies.

5.2.3.2 Rights in Data (Including Technical Data, Computer Software and Computer Software Documentation). The Government has determined its minimum needs for this acquisition include:

5.2.3.2.1 Special License Rights to data other than technical data (e.g., schedule/milestone data, financial data) delivered to the Government described in Section J: Attachment 3 paragraph c.(3); and

5.2.3.2.2 Special License Rights to review all data used by the Contractor to create any CDRL or CLIN delivered under this contract to verify the currency, accuracy and completeness of the data contained in those CDRLs/CLINs described in Section J Attachment 3 paragraph c.(4).

5.2.3.2.3 Provide Rights in Data per Section 4.1.3 of this document.

image1.emf