Atch_8_-_L-III__INFORMATION_TO_OFFERORS.pdf

FA8823-15-R-0001 Section J: Atch 8

L-III - INFORMATION TO OFFERORS and INSTRUCTIONS FOR PROPOSAL PREPARATION

By submission of a proposal, the Offeror represents that its team is capable of performing all contract requirements and meeting all standards specified in the solicitation and asserted included in the proposal throughout the awarded performance period.

1. GENERAL INFORMATION

1.0. In addition to the instructions provided in FAR 52.215-1, this section provides guidance for preparing proposals, as well as specific instructions on the format and content of the proposal.

Throughout this section, the term "Offeror" includes subcontractors, teammates, joint venture partners, and key personnel. The Offeror’s proposal must include all data and information requested, and must be submitted in accordance with these instructions. Any Offeror who submits an incomplete package may be considered technically unacceptable. The Offeror shall be compliant with the requirements as stated in the Request for Proposal (solicitation) and shall describe how the offer will satisfy the requirements stated in the Performance Work Statement (PWS) and Contract Data Requirements List (CDRL). A proposal that is sufficiently documented to support price and performance in a complete, orderly, and specific detailed manner will enable the Government to perform a thorough and fair evaluation. Non-compliance with the instructions in the solicitation may result in an unfavorable proposal evaluation and may be grounds to eliminate the proposal from consideration for contract award.

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

1.2. Proposal Depth. The Offeror is advised that its proposal is presumed to represent its best efforts and most complete responses to this solicitation. The Offeror is advised not to provide simple cursory responses or responses which merely reiterate the PWS.

1.3. Alternate proposals will not be accepted. This restriction does not prevent an Offeror from identifying areas of exception in the appropriate volume and section of the proposal.

1.4. Reference Documents. None of the regulations, manuals, or other publications referenced will be issued with the solicitation.

1.5. Bidders Library. Unclassified For Official Use Only (FOUO) documents are available via compact disc and will be provided upon written request to the PCO/CS.

1.6. Coordinating Access to Classified Bidders Library. Not Applicable.

1.7. Timely Submission. Both paper and electronic copies shall be delivered to the contract specialist by mail to AFSPC SMC/PKJ (Attn: Janet Stinson), 1050 East Stewart Ave. Bldg. 2025, Peterson AFB, CO 80914-2902 (least desirable) or shall be hand-carried to the contract specialist at Building 2025, by 05 October 2015 2:00 PM Mountain Time. If using a courier, submit the name of the individual hand-carrying these volumes 24 hours in advance to the contract specialist. 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 POC no later than the date and time specified in the final solicitation Request for Proposal posting.

1.8. Proposal Delivery. Due to Peterson Air Force Base's mail security processes, the Contracting Officer 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 Contracting Office 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 contract specialist, and not rely on voice mail.

1.9. Access to Base. Contractor personnel delivering proposals are advised that they may be unable to access PAFB without a valid U.S. Uniformed Services Identification Card or DOD Force Common Access Card (CAC). 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 Peterson Air Force Base and should plan accordingly.

2. GENERAL INSTRUCTIONS

2.1. Point of Contact (POC). The primary POC for this acquisition is the Procuring Contracting Officer (PCO), Robert M. Chernoff. The secondary POC is the Contract Specialist (CS), Janet Stinson.

Address all questions or concerns to both using the following contact information:

UPCO UCS

Robert M. Chernoff (robert.chernoff@us.af.mil) Janet Stinson (janet.stinson.2@us.af.mil)

AFSPC SMC/PKP AFSPC SMC/PKJ

483 North Aviation Blvd. Bldg. 271 1050 East Stewart Ave. Bldg. 2025 El Segundo, CA 90245-2808 Peterson AFB, CO 80914-2902 Phone: (310) 653-3128 Phone: (719) 556-2073

2.2. Safeguarding Information. Proprietary information submitted in response to this solicitation is restricted from unauthorized disclosure as required by 41 U.S.C. § 2102.

2.3. Revisions and Amendments. The Government reserves the right to revise or amend the specifications or the solicitation. Such revisions or amendments will be communicated by formal amendment (Standard Form 30/SF30) to this solicitation. If such amendments require material changes in quantities or price, the solicitation closing date may be extended to enable an Offeror to revise its proposal. In such cases, the amendment will include an announcement of the new solicitation closing date and time. The Offeror shall provide acknowledgement in Block 14 of the Standard Form (SF) 33 of any solicitation amendments issued by the Government and include in the Contract Volume.

2.4. Discrepancies and Ambiguities. If an Offeror believes that the Solicitation contains errors, omissions, or is otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale no later than seven calendar days after the presolicitation or solicitation release.

2.5. Rounding. All dollar amounts provided shall be rounded to the nearest dollar.

2.6. Mistakes. Mistakes in contractor's proposal shall be handled in accordance with FAR §15.508.

2.7. Communications. All communications regarding this procurement will be directed to the PCO. Exchanges with industry may be conducted using any of the following means: facsimile, U.S.

postal service or commercial carriers, telephone or in person. Preferred method for source selection and proprietary information is facsimile.

2.8. Debriefings. At the Government's discretion, a competitive range determination may be utilized. The PCO will promptly notify Offeror of any decision to exclude them from the competitive range IAW FAR § 15.503. An unsuccessful Offeror will have three days from the date of exclusion from competitive range or date of Government notice of contract award to submit a written request for a pre-award or post award debriefing in accordance with FAR § 15.503. In accordance with FAR §15.506, the PCO may elect to conduct the debriefing orally, in person, or by teleconference. An Offeror will receive only one debriefing.

2.9. Discussions. The Government intends to evaluate proposals and award a contract without discussions, but reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary.

2.10. Final Proposal Revisions (FPR). Once discussions have been concluded (if conducted) with an Offeror determined to be in the competitive range, the PCO may request that the Offeror provide a FPR. The Offeror is advised that any changes to the proposal in the FPR must be addressed and fully explained showing the total effect to the proposed price. Failure to comply with this requirement can adversely influence the evaluation of the proposal. The PCO will establish a common due date and time for submission of the FPR. The number of copies required for the FPR is identified in Table L-1.

2.11. Proposal Retention. In accordance with Federal Acquisition Regulation (FAR) §4.8 (Government Contract Files), the Government will retain one copy of all proposals in accordance with (IAW) the Federal Records Disposition Schedule.

3. PROPOSAL PREPARATION AND FORMAT INSTRUCTIONS. This section provides general guidance for preparing proposals, as well as specific instructions on the format and content of the proposal. Each volume shall be complete in itself and contain a Table of Contents.

3.1. Solicitation Cross Reference Matrix. The Offeror will provide a matrix indicating where the proposal meets the requirements of the solicitation 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. Complete a table using a comparable format as shown below and include it on a cover page for both Volumes I, II and III:

CLIN

Task Description

PWS Para or RFP Section

Section L

Section M

CDRL

3.2. Proposal Presentation. Elaborate brochures, binding, detailed artwork, or other embellishments are unnecessary and not desired.

3.3. Classified Information. Classified data shall not be included any volume.

3.4. Organization/Number of Copies/Page Limits. The Offeror's proposal shall consist of three

(3) proposal volumes: a Contract Volume (Volume I), a Price Volume (Volume II) and a Technical Proposal Volume (Volume III). The Offeror shall prepare the proposal volumes as set forth in the Proposal Organization Table (Table L-1). The titles and contents of the volumes shall be as defined in this table, all of which shall be with the number of copies and within the required page limitations as specified. The contents of each proposal volume are described in the paragraph as noted.

3.5. Stand Alone Volumes. 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. Contract and price information will not be included in any other volume unless specifically instructed otherwise.

3.5.1. Table of Contents, Indexing and Glossary. Each volume shall contain a detailed table of contents to delineate the Tabs and subparagraphs within that volume. Tab indexing shall be used to identify sections. A separate table of contents shall identify sections/tabs, figures, and tables. 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, index, and glossary are excluded from volume page limitations.

3.6. Change Pages after Initial Proposal Submission. If the Government opens discussions and requests the Offeror submit proposal revisions, during or after discussions, any changed pages that are submitted shall have changed information clearly marked by a vertical line in the right margin of the page identifying the changed content. The date of the revision and revision number shall be reflected on each changed page (preferably on, or next to, the vertical change line). Additionally, a different color paper shall be used for each round of revisions. Make spreadsheet revisions obvious by highlighting cells that changed. NOTE: Change pages must conform to original RFP instructions and page restrictions.

Table L-1: RFP/FPR Proposal Organization/Number of Copies/Limitations/Restrictions –

Volume/Attachment Section Title

Factor

Subfactor

Section L Reference

Elec.

Copies

Paper Copies

Page Limit Other Restrictions

VOLUME I & II

UVOLUME IU

CONTRACT

DOCUMENTATION

UVOLUME II

PRICE PROPOSAL

UResponsibility

UPrice Evaluation:

Total Evaluated Price

Reasonableness

Unbalanced Pricing

4.1

4.2

1 Original plus one copy

No limit for Offer Cover

Letter

No Limit for Contracts Section

(Sections A-K) Add’l Info

No Limit for Price Section

No Classified Information in volume

VOLUME III

UVOLUME IIIU

TECHNICAL

Executive Volume Summary

4.3.1.1

3 pages

Phase-In 4.3.2 Original plus one copy

15 pages

Total of these items volume

Critical Staffing 4.3.3

Technical Process Approach

4.3.4

TECHNICAL VOLUME ATTACHMENTS

Phase-In Plan Phase-In 4.3.2

Original plus one copy

10 pages volume

Job Requisitions Critical Staffing 4.3.3 No Limit

Hiring Procedures, Retention Statistics & Contingency Offers

Critical Staffing 4.3.3 No Limit

Staffing Matrix Critical Staffing 4.3.3 No Limit Completed Section J Atch 3

Technical Process Approach

4.3.4.2 No Limit

3.6.1. Binding and Labeling. Except as described below for the Original (Government record-copy) each volume of the proposal shall be separately bound in a three-hole binder which shall permit the volume to lie flat when open. Staples shall not be used. All binders shall allow for easy removal and replacement of pages. A cover sheet shall be inserted at the front of each volume, clearly marked with the Offeror's name, volume number and title, solicitation identification (e.g. solicitation number and title), and the copy number (e.g. copy 2 of 5) (e.g., Company A, Volume I, Solicitation FA8823-15-R- 0001 copy X of Z). The same identifying data shall be placed on the spine and front of each binder.

Apply all appropriate markings including those prescribed in accordance with FAR §52.215-1(e), Restriction on Disclosure and Use of Data, and §3.104-4, Disclosure, Protection, and Marking of

Contractor Bid or Proposal Information and Source Selection Information. The original shall be clearly marked "original."

3.6.2. Electronic Copies. The Offeror shall submit a complete copy of the proposal, including all proposal volumes and attachments, in electronic format, using non-re-writable DVDs. The content and page size of electronic copies shall be identical to the hard copies. If there is an inconsistency between the printed copy and the electronic copy, the printed document will take precedence. Indicate on each DVD the volume number and title. Use separate tiles and 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. Each volume shall be on a separate DVD. All files must be uncompressed. Ensure the electronic documents stored on DVDs can be opened and that all information is accessible on Government computers. Offeror shall "close the session" on all DVDs submitted to the Government so no changes can be made to the information.

3.6.3. The electronic copies of the individual proposal elements shall be submitted in a format readable by Microsoft (MS) Word ®, MS Excel®, MS-Power Point ® 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 copies 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, 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 unless specifically stated. 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. Electronic submissions for each file can be no larger than 1GB and must be accessible on stand-alone computers.

3.6.4. Page Limitations. Page limitations shall be treated as maximums (Reference Proposal Organization Table (Table L-1)). Total page count will be based on the printed proposal submission. For the Technical Volume, if page limitations are exceeded excess pages will not be read, nor considered in the evaluation of the proposal and will be returned to the Offeror. Page limitations may be placed on responses to Evaluation Notices (ENs) if required. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offeror. Extra pages will be removed and returned.

3.6.5. 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. The background color of each page of the original proposal submission shall be white or ivory stock only. 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.

4. SPECIFIC PROPOSAL CONTENT.

4.1. VOLUMES I - CONTRACT DOCUMENTATION.

This volume shall contain the Offeror's contractually related documentation. Any material presented here shall not be considered as meeting the requirements for portions required in other volume of the proposal.

The Offeror shall present a complete and accurate price for meeting the requirements of its technical approach. The volume and sections shall be specific and complete. Legibility, clarity, and coherence are very important. The Offeror's responses will be evaluated against the price criteria 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 acceptability. All the requirements specified in the solicitation are mandatory. Any proposal that does not address all requirements or clearly meet the requirements may be deemed an alternate proposal and alternate proposals will not be considered.

UContract Documentation Volume Format

4.1.1. Tab C1 – Summary Section. The Offeror will provide a concise offer cover letter signed by an authorized agent of the company. This offer cover letter will:

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

4.1.1.2. Company/Division Address, Identifying Codes, and Applicable Designations. Provide company/division's street address, county code, and facility code; Commercial and Government Entity (CAGE) code; Data Universal Numbering System (DUNS) code; 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.

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.1.4. DCMA/DCAA. Provide mailing addresses, telephone numbers, fax numbers, and facility codes for the Contract Administration Office, DCAA, and Government provide the name, telephone numbers, and fax numbers for the ACO, if applicable.

4.1.1.5. ConWrite. Provide an affirmative statement that administrative or structural changes made to the model contract or its attachments to accommodate the contract writing system as a result of the Offeror’s proposal are acceptable and will not invalidate the offer.

4.1.2. Tab C2 - Responsibility:

4.1.2.1. Financial Resources. The proposal shall describe adequate financial resources to perform the prospective contract or demonstrate an ability to obtain adequate financial resources, through balance sheets and cash flow statements as required by FAR 9.104-1(a) and DFARS 232.072.

4.1.2.2. Limitation on Subcontracting. The Offeror shall provide the required information for subcontracts to reflect compliance with FAR 52.219-14 Limitation on Subcontracting.

4.1.3. Tab C3 - Exceptions to Terms and Conditions. The Offeror shall identify all exceptions taken to terms and conditions of the model contract, to any of its formal attachments or to other parts of the solicitation. Each exception shall be specifically related to a specific document identifying 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. Material exceptions to the terms and conditions may render an Offeror not acceptable.

4.1.4. Tab C4 - Organizational Conflicts of Interest (OCI) documentation. The Offeror shall include information regarding OCI as described in Section L, 5.1 and Section J Attachment 10.

4.1.5. Tab C5 – Contract Schedule. The Offeror’s proposal shall include an original signed copy of the Contract Standard Form (SF33) as well as original signed copies of all SF30 amendments to cover submission of Sections A through K. Signature by the Offeror on the SF33 constitutes an offer, which the Government may accept without discussions. In signing, the Offeror agrees to the contract terms and conditions as written in the solicitation Sections A through K unless specific exception is taken and documented. The format and content includes:

4.1.5.1. Section A: Complete Standard Form 33 (Solicitation, Offer, and Award) Blocks 12 through 16, and sign and date blocks 17 and 18.

The Offeror's proposal shall be valid for a minimum of 180 days. The Offeror shall specify the proposal acceptance period in SF 33 Block 12 of the solicitation.

The Offeror shall also sign acknowledgement of all amendments in Block 14 of each Standard Form (SF) 33 issued by the Government. Sections A through J constitute the model contract with information provided in Section K incorporated by reference in the final award.

The “original” copy of the signed SF33 and all SF 30s shall be clearly marked and provided under a separate section.

4.1.5.2. Section B: Supplies or Services and Prices/Costs

The Offeror shall fill in the Total Item Amount Column for FFP CLINs 0001, 1001, 2001, and 3001 (3001 is the sum of 6 months) and if proposal includes pricing for CLINs 4001 and 4002, fill in column entries for unit of issue and unit price as well. All FFP CLINs are for 1-month periods with payments authorized by

CDRL A002 in Exhibit A.

FFP CLIN 4001 with CR CLIN 4002 Period of Performance is a component of the Offeror’s Phase-In Plan for proposals including pricing.

The Offeror shall complete the UPricing Volume Contract Schedule TableU. Include Totals and Subtotals in the table for Total Proposed Price, Total TEP Price, Total Phase-In Transition Price, and totals for base performance period, annual option periods and extension periods.

4.1.5.3. Sections C, D, and E:

The Offeror shall include RFP pages with proposal. No other instructions.

4.1.5.4. Section F: Performance/Delivery Data

The Offeror shall complete the UPricing Volume Contract Schedule TableU. Include Totals and Subtotals in the table for Total Proposed Price, Total TEP Price, Total Phase-In Transition Price, and totals for base performance period, annual option periods and extension periods.

4.1.5.5. Section G: Contract Administration Data

The Offeror shall provide names and contact information for contract management and administration Points of Contact in Program Management, Contract Management, and Accounts Receivable to be included in a contract award.

4.1.5.6. Section H: Special Contract Clauses

The Offeror shall acknowledge acceptance of the FFRDC Enabling Clause.

4.1.5.7. Part II – Section I Clauses:

The Offeror shall include RFP pages with proposal and complete all applicable fill-ins.

4.1.5.8. Section J: List of Attachments

4.1.5.8.1. The Offeror’s shall fill in Sections 6-8 of the DD 254 Contract Security Classification provided in Attachment 2.

4.1.5.8.2. The Offeror shall complete Attachment 3 GEARSS Rights in Data in accordance with the following instructions:

4.1.5.8.2.1. The Government has determined its minimum needs for this acquisition include:

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

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

4.1.5.8.2.1.3. Special License Rights to review all data used by the Contractor to create any 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).

4.1.5.8.2.2. 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).

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

4.1.5.8.2.4. Complete Table 1 in Attachment 3 in the following manner:

4.1.5.8.2.4.1. With regard to items of technical data associated with cells in Column 3 of that table labeled as “Unlimited”, leave those cells as-is. If, however, the Offeror is not willing to sell Unlimited 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.

4.1.5.8.2.4.2. Insert a proposed estimated cost 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 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)).

4.1.5.8.2.5. Complete Table 2 in Attachment 3 in the following manner:

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

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

4.1.5.8.2.5.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.1.5.8.2.5.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.

4.1.5.8.2.5.5. In Column 5 of that table, insert an estimated cost/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/price 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.)

4.1.5.8.2.6. Complete Table 3 in Attachment 3 by inserting a proposed estimated cost/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.

4.1.5.8.2.7. In subsection c.(4), replace the asterisk (**) with the estimated direct cost/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 (“—“).

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

4.1.5.8.2.9. To ensure that the parties will maintain proper configuration control of all licenses throughout the performance of the resulting contract, create an “Appendix A” to Attachment 3 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 Appendix A 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 Appendix A 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 appendix 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 Appendix A, 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)-(11), 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.5.8.3. The Offeror shall identify any GFP it believes is unnecessary, missing or otherwise in error in the Contracts Section, as appropriate. Clearly identify any additional GFP the Offeror is requesting by providing a revised attachment.

4.1.5.8.4. 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 a Collective Bargaining Unit has an agreement in place for the employees proposed. The Offeror shall comply with all terms and conditions required by the SCA and must conform its employee’s labor classification to the categories in the attached wage determination unless the Offeror asserts exemptions to the SCA as instructed under Section K and Paragraph 5.

4.1.5.9. Section K: Representations and Certifications

The Offeror shall complete provision fill-ins for certifications, acknowledgments, and statements and provide copies of the Offeror’s SAM certifications.

Size Standard. This acquisition will be a 100% small business set-aside competition under NAICS Code 517919 with a size standard of $32.5M. The submittal must include representations and certifications supporting the assertion the Offeror meet the size standard.

Failure to provide the certification indicating compliance with this size standard with the initial proposal is grounds for the offer to be determined technically unacceptable.

Service Contract Act Applicability. The Offeror shall submit written certification regarding Service Contract Act exemptions as described in Section 5.2 – Additional Information – Service Contract Act Applicability.

Professional Employee Compensation. The Offeror and Subcontractors shall submit their Total Compensation Plan for Professional Employees, which will not become part of the awarded contract. The

Total Compensation Plan is not to include the labor categories and rates that are a part of Wage Determinations and Collective Bargaining Agreements. The plan shall set forth salaries and fringe benefits proposed for professional employees as prescribed in the instructions below:

In accordance with FAR 22.1103, all Offerors and Subcontractors shall submit their Total Compensation Plan for Professional Employees for service contracts when the contract amount is expected to exceed $650,000 and the services which are to be provided will require meaningful numbers of professional employees. For the purpose of this acquisition, the number of meaningful professional employees is defined as the contract or any subcontracts having more than eight (8) full-time equivalent employees classified as “professional employees”. The Offeror and Subcontractors shall submit a total compensation plan setting forth salaries and fringe benefit package proposed for the professional employees. The prime Offeror should instruct its subcontractors to submit their Total Compensation Plan directly to the Government. The prime Offeror shall also submit a list professional employee compensation packages to the Government.

The Offeror and Subcontractors shall provide the following:

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

(2) Surveys and Studies: Provide 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 and provide copies of the supporting documentation with the Offeror’s surveys and studies. Include a comparison of the source rates to the Offeror’s rates, clearly identifying which category and rate being used for the comparison. If not using one of the sources listed above, explain the credibility of the source providing the surveys and studies.

(3) Offeror’s/Subcontractor’s Assessment: Discuss how the proposed compensation package in the Total Compensation Plan from paragraph (1) above and the Surveys and Studies from paragraph (2) 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 retention of employees, especially, at the geographically separated locations.

4.2. VOLUME II - PRICE

4.2.1. Price Data. This section is to assist the Offeror in submitting information other than certified cost or pricing data that is required to evaluate the total evaluated price, reasonableness, and unbalanced pricing of the Offeror’s proposed price. Compliance with these requirements is mandatory and failure to comply may result in rejection of the proposal. Offers should be sufficiently detailed to demonstrate their reasonableness and balanced pricing. The burden of proof for credibility of proposed prices rests with the Offeror. Only data in the Price Volume will be evaluated in the Price Factor. The Offeror shall complete the UPricing VolumeU USummary of Contract Schedule Table.xls Excel attachmentU. Include and verify Totals and Subtotals in or beneath table for Total Proposed Price, Total TEP Price, Total Phase-In Transition

Price, and totals for base performance period, annual option periods and extension periods.

4.2.2. CLIN Structure.

4.2.2.1. Sustainment Services CLINs 0001, 1001, 2001, 3001. Sustainment Services CLINs are FFP.

For CLIN 3001, Offeror shall provide monthly prices, but the TEP will be based on the sum of the all 6 months.

4.2.2.2. ODC CLINs 0002, 1002, 2002, 3002. (Government Established Amount for Evaluation of Total Contract Price). The ODC CLINs are Cost Reimbursement only. No indirect burdens or fee is allowed on these costs. For the purposes of calculating the total contract price, the Offeror shall propose the Government Established amount for ODC for each CLIN as shown below.

CLINS Amounts 0002 $250,000 1002 $250,000 2002 $250,000 3002 $125,000

4.2.2.3. Phase-In Transition Sustainment CLIN 4001. The Phase-In Sustainment CLIN is FFP.

The Offeror shall propose a FFP associated with its effort to become fully staffed/teamed, trained, located, etc. to meet performance standards. The Offeror shall propose a period of performance for this transition effort that will not exceed 90 calendar days from contract award.

4.2.2.4. Phase-In Transition ODC CLIN 4002 (Government Established Amount for Evaluation of the Total Contract Price). This Phase-In Transition ODC CLIN is Cost Reimbursement only. No indirect burdens or fee is allowed on these costs. The Offeror shall propose the Government established amount of $75,000.

4.2.3. Total Evaluated Price (TEP). Provide the Offeror’s calculation of the TEP. UThe Pricing Volume Contract Schedule Table Uis shown on page 21 of this section and provided as an Excel spreadsheet template.

CLIN Amounts ($)

CLIN 0001

CLIN 1001

CLIN 2001

CLIN 3001 (for total of 6 months)

TEP

4.2.4. Reasonableness. CLIN prices should be clearly identified in the Price Volume. The burden of proof for credibility and reasonableness of proposed prices rests with the Offeror.

4.2.5. Unbalanced Pricing. Unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an Offeror’s proposal.

4.2.6. Other than Cost and Pricing Information Requirements. In accordance with 32TFAR 15.403- 1(b)32T Prohibition on Obtaining Certified Cost or Pricing Data and 32T15.403-3(a) Requiring Data Other Than Certified Cost or Pricing Data32T, data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided in accordance with 32TFAR 15.403-5 Instructions for Submission of Certified Cost or Pricing Data and Data Other Than Certified Cost or Pricing Data. 32T If, after receipt of proposals, the PCO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in 32TFAR 15.403-132T Prohibition on Obtaining Certified Cost or Pricing Data apply, the Offeror shall be required to submit additional cost or pricing data.

4.3. VOLUME III -TECHNICAL PROPOSAL

The Offeror shall present a clear and concise description of its proposed approach for meeting the requirements of each technical subfactor. The Technical Proposal Volume 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 solicitation 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.

4.3.1.Technical Proposal Volume Format. The Offeror shall submit its Technical Proposal Volume as follows:

4.3.1.1. Tab 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. Information included in this Tab is excluded from the volume page limitations. However, this tab shall not exceed three (3) pages.

4.3.1.2. Tab 2: Table of Contents, Index and Glossary

4.3.1.3. Tab 3: 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.

4.3.1.4. 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:

4.3.2. SUBFACTOR 1- Phase-In and 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.

4.3.2.1. Provide a Phase-In Plan that describes the specific steps or methodology the Offeror proposes to use to meet program phase-in milestones IAW PWS 3.6.

4.3.3. SUBFACTOR 2 - Critical Staffing: The Offeror shall provide a completed staffing plan (see Table L-2) demonstrating that the proposed number of Full-Time Equivalents (FTE) provide sufficient labor-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. Offeror’s shall provide a completed staffing plan table (provided at Table L-2).

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 (by Labor CLIN) to satisfy each of the PWS paragraph requirements. The staffing table shall demonstrate that the proposed number of FTEs results in sufficient labor-hours to accomplish all required tasks:

4.3.3.1. Provide the job requisitions for the technical and management staff the Offeror proposes to perform specified PWS tasks 3.2.1, 3.3.1, 3.3.9, 3.3.10, 3.4.1, 3.4.2, 3.4.3 and 3.4.5.

4.3.3.2. Provide clear evidence (e.g., hiring procedures, retention statistics, 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.

4.3.3.3. Identify and detail all contractual inter-dependencies, cross-utilization, or other shared resources, including any GFP usage proposed. Describe assessed risk to meeting performance standards on all associated contracts, how those risks were mitigated, and how the Offeror prevents duplication of costs to the Government. Include evidence the other contracting and program authorities accept the Offerors technical approach.

Table L-2: Staffing Plan Matrix Expandable Format

ELEMENT

PWS

Para

CLIN 0001

FTE/Hours

CLIN 1001

FTE/Hours

CLIN 2001

FTE/Hours

CLIN 3001

FTE/Hours

Specify GEARSS Support Element/Task here and include PWS reference Labor Cat 1—Title/Grade Company Name Clearance Level Location

Labor Cat 2—Title/Grade Company Name

Additional Categories, as needed SubTotal Specify GEARSS Support Element/Task here and include PWS reference Labor Cat 1—Title/Grade Company Name

Labor Cat 2—Title/Grade Company Name

Additional Categories, as needed SubTotal Total Hours

4.3.4. SUBFACTOR 3 – Technical Process Approach: The Offeror shall:

4.3.4.1. Describe how the proposal satisfies the requirements of PWS 3.2, 3.3 and 3.4 that demonstrate a clear understanding of the technical and operational environment.

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

4.3.4.2.1. Unlimited Rights to CDRL A003.

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

4.3.4.2.3. 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) and Exhibit A.

5. OTHER INFORMATION

5.1. Organizational Conflict of Interest (OCI)

(a) In accordance with FAR 9.5, Organizational and Consultant Conflicts of Interest, the Contracting Officer has analyzed the planned acquisition and determined that no known actual or potential Organizational Conflict of Interest (OCI) situations exist with respect to this solicitation.

(b) 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.