Atch 6 WICS II Section L 05 Aug 20 FA255020R0004.docx

FA255020R0004 Atch 6 RFP Section L – Instructions to Offerors Amendment 06, 05 Aug 2020

1.0 Budget / Funding Information. The 50th Space Wing receives baseline funding from United States Space Force (USSF) and SMC mission partners in order to accomplish the Wing Information and Communications Support (WICS-II) requirements. The WICS-II budget is part of a larger Program Objective Memorandum (POM). Cost/Price proposals will be evaluated for reasonableness and affordability based on the affordability table below. Cost reimbursable travel and ODCs have been calculated into these estimates below:

Affordability Table Phase-In (30 Days)

FY21

(1 Mar 21 – 29 Mar 21) Base Year

FY 21

(30 Mar 21 – 29 Mar 22) Option 1

FY22

(30 Mar 22 – 29 Mar 23) Option 2

FY23

(30 Mar 23 – 29 Mar 24) Option 3

FY24

(30 Mar 24 – 29 Mar 25) Option 4

FY25

(30 Mar 25 – 29 Mar 26) Option 5

FY26

(30 Mar 26 – 29 Mar 27) Option 6

FY27

(30 Mar 27 – 29 Mar 28) (6 mos)

FY28

(30 Mar 28 – 29 Sep 28) Total

Note: This does not include $20M cost reimbursable (3080) procurement funding

2.0 General Instructions. This section provides general guidance for preparing proposals, as well as, specific instructions on the format and content of the proposal. Throughout this section, the term “offeror” includes affiliates, subcontractors, teammates and/or joint venture partners. The offeror’s proposal must include all data and information requested and must be submitted in accordance with (IAW) these instructions. Any offeror who submits an incomplete package may be considered non-responsive.

2.1 Proposal Clarity. The proposal shall be clear, concise, and include sufficient detail for effective evaluation of the offeror’s capabilities and substantiate the validity of stated claims in all Volumes. 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 and such information, including past performance information, as it is available to the Government.

2.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’s Technical Experience and solutions to Scenarios shall demonstrate technical experience, capability, and qualifications that clearly demonstrate and support the offeror’s claims. Proposals shall not contain classified information. By submitting a proposal, the offeror represents that its team is capable of performing all requirements specified in the solicitation.

2.3 Alternate Proposals. The Government will not accept alternate proposals.

2.4 Proposal Acceptance Period. The offeror shall specify the proposal acceptance period in Section A, Block 12 of the solicitation. The offeror’s proposals shall be valid for a minimum of 365 days from proposal submission.

2.5 Size Standard. This acquisition is a small business 8(a) set aside under NAICS code 517410, Satellite Telecommunications with a $35M size standard.

3.0 General Information.

3.1 Point of Contacts (POCs). The POC for this acquisition is Mr. William Ray and Mr. James Knight. Address any questions or concerns using the following contact information:

3.2 Debriefings.

3.2.1 Pre-Award Debriefings. At the Government’s discretion, a competitive range may be established. Using the phased approach, an offeror’s proposal may be eliminated from consideration IAW FAR 15.307(a) at specific times through the evaluation process. The CO will promptly notify an offeror of any decision to exclude that offeror from the competitive range or otherwise eliminated IAW FAR 15.503, whereupon it may request and receive a debriefing in accordance with FAR 15.505.

3.2.2 Post-Award Debriefings. An unsuccessful offeror will have three days from the date of Government notice of contract award to submit a written request for a post-award debriefing in accordance with FAR 15.506. An unsuccessful offeror who fails to submit a timely request will not be entitled to a debriefing. In accordance with FAR 15.506, the CO may elect to conduct the debriefing orally, in writing, or any other acceptable method. Offerors will only receive one debriefing.

3.3 Discrepancies and Ambiguities. If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the CO in writing with supporting rationale, as well as the remedies the offeror is asking the CO to consider as related to the omission or error. Notify the CO in writing no later than 15 calendar days after the RFP release.

3.4 Reference Documents. Unclassified documents will be available on Beta.SAM.gov. Other documents designated For Official Use Only (FOUO) will be located in the WICS II Bidders’ Library, which will be available through accessible digital media. Offerors should contact the personnel identified in Section L, paragraph 3.1 for a copy of the Bidders’ Library. Potential offerors are encouraged to subscribe to Beta.SAM.gov for real-time email notifications when information is posted to the website for this solicitation.

3.5 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) to this RFP. If such amendments require material changes in quantities or costs / prices, the solicitation closing date may be extended to provide additional time for offerors to revise proposals. 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 SF 33 of any solicitation amendments issued by the Government.

3.6 Mistakes. Mistakes in contractor’s proposal shall be handled IAW FAR 15.508, Discovery of Mistakes.

3.7 Final Proposal Revisions (FPR). Once discussions (if conducted) have been concluded with an offeror determined to be in the competitive range, the CO will request the offeror to provide a FPR. The offeror is advised that any changes to the proposal in the FPR must be fully addressed/explained and reflected in the proposed cost / price. Failure to comply with this requirement can adversely influence the evaluation of the proposal. The CO will establish a common due date and time for submission of the FPR. The number of copies required for the FPR are the same as the basic proposal.

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

3.8.1 Organization / Number of Copies / Page Limits. The offeror’s proposal shall consist of four (4) proposal volumes: a Technical Proposal Volume, a Past Performance Volume, a Cost / Price Volume, and a Contract Documentation Volume. The offeror shall prepare the proposal volumes as set forth in the following Table L-1 - Proposal Organization Table. 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 in Table L-1 - Proposal Organization Table. The contents of each proposal volume are described in the paragraph as noted in the table below.

Table L-1 - Proposal Organization Table

Technical Experience One electronic copy

8 total pages for all technical experience responses.

This page limitation excludes the Executive Summary and copies of relevant PWS’s referenced.

Mission Essential Plan

Scenarios

No more than 3 Present/Past Performance Information Submittals per focus area (includes Prime and Subcontractors).

3.8.2 Electronic Copies. The offeror shall submit a complete copy of the proposal, including all proposal volumes and attachments, in electronic format. The content and page size of electronic copies shall be IAW Section L, paragraph 3.8.5. Indicate on each document, the volume number and title. Use separate files and folders and ensure the file-naming convention is simple and straightforward to permit rapid location of all portions, to include subfactors, exhibits, annexes, and attachments, if any. Each volume shall be on a separate file. All files must be uncompressed. Ensure the electronic documents submitted can be opened and that all information is accessible on Government computers.

The electronic copies of the proposal shall be submitted in a format readable by MS Office 2013® applications (e.g. Microsoft (MS) Word 2013®, MS Excel 2013®, and MS-Power Point 2013®) and/or Adobe Acrobat®). The proposal may be submitted in portable document format (PDF), but if used must be formatted to allow the text to be selected (i.e. not as an image). Electronic copies of price tables and spreadsheets shall be provided in MS Excel® to allow Government evaluation and review of equations. Ensure clarifying notes used to calculate price are reflected in the spreadsheets. In the technical proposal volume, a list of 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. If files contain links, the links shall be maintained in all revisions. Electronic submissions for each file must be accessible on stand-alone computers.

3.8.3 Data Transmission. To facilitate review and evaluation for this source selection, the Government proposes to transmit data utilizing both government and commercial systems. Within the Government, material will be distributed via encrypted email, will be marked as source selection sensitive and/or contractor proprietary as appropriate, and distribution will be limited to approved personnel. Should any offeror object to its proposal information being shared between source selection evaluation team members or advisors via Government email systems or between the CO and the offeror via commercial email systems please advise the CO in writing before or with submission of the proposal.

3.8.4 Page Limitations. Page limitations shall be treated as maximums. Total page count will be based on the electronic files when the proposal submission is printed. If exceeded, the excess pages will not be read, nor considered in the evaluation of the proposal. Page limitations may be placed on responses to Evaluation Notices (ENs). The Government will identify specified page limits for EN responses in the letters forwarding the ENs to the offeror.

3.8.5 Page Size and Format. A single page size will be 8.5 x 11 inches, with at least 1-inch margins around the page perimeter, not including foldouts and spreadsheet templates that are provided by the Government. Pages will be single-spaced. The background color of each page of the original proposal submission shall be white only. Use Times New Roman, with a font no smaller than 11-point with normal proportional spacing. Text embedded in graphics and tables can vary from the font style and size requirement but must be readable to the reviewer.

3.8.6 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.8.7 Stand Alone Volumes. Each volume shall be written on a standalone basis so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Information required for proposal evaluation, which is not found in its designated volume, will be assumed to have been omitted from the proposal.

3.8.8 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). Make spreadsheet revisions obvious by highlighting cells that changed.

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

3.8.10 Classified Information. Proposals shall not include any classified data in any proposal volume. The Government appreciates and is aware of the sensitive, and sometimes classified, nature of some proposal information, especially past performance information. The offeror shall provide as much information as they are able in an unclassified proposal, and include contact information to obtain further information as the Government requires. The offeror shall make every attempt to summarize relevant information and ensure any additional classified information available through the contact is truly necessary to the Government’s understanding and decision. The Government is not obligated to contact these references, but will rely on the unclassified information provided to the maximum extent possible.

3.8.11 Proposal Delivery. Electronic copies shall be delivered by utilizing DoD Safe at the website https://safe.apps.mil. Offerors and their subcontractors must contact the CO and the CS at the addresses stated in Section L, paragraph 3.1 to request a “Drop-off” which will be provided allowing the requestor to upload proposals and support documentation. This request may be made anytime within 14 days prior to the proposal due date. DoD Safe will send an automated notification of the Drop-off request. Provide email confirmation directly to the CO and CS at 50 CONS/PKD at the addresses stated in Section L, paragraph 3.1 when receiving the notification, and when submitting documents through DoD Safe. These volumes must be received no later than the date and time specified in the Beta.SAM.gov final solicitation posting. All volumes must be received no later than 1:00 pm Mountain Standard Time (MST) on 17 June 2020. Email confirmation will be provided to offerors within 45 minutes of receipt. Should confirmation not be received, contact the POCs in Section L, paragraph 3.1.

4.0 Specific Proposal Instructions and Format:

4.1 Volume I – Technical. The offeror shall provide a narrative and support documentation to establish adequate technical experience, and certify agreement to respond to scenarios on the date specified. 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 Experience Proposal Subfactor 1 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 experience. All the requirements specified in the solicitation are mandatory. Upon proposal delivery, the offeror is representing that it will perform all the requirements specified in the solicitation. It is not necessary or desirable for the offeror to state so in the proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.1.1 Technical Proposal Volume Format. The offeror shall format the Technical Proposal Volume as follows:

4.1.2 Tab 1: Executive Summary. The offeror shall provide a concise narrative executive summary of the entire proposal, excluding the cost / price information while including technical aspects. 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 other volumes of the proposal. Information included in this tab is excluded from the volume page limitations, but shall not exceed five (5) pages.

4.1.3 Tab 2: Table of Contents, Index, and Glossary. No page limitation

4.1.4 Tab 3: Subfactor 1 –Technical Experience. The offeror shall provide evidence of a minimum of three years of technical experience within the past seven years of each requirement within the PWS, as detailed in Section L, Attachment L-8. GBSOC, SDIN, MIR, and MILSATCOM are the specific experience areas required. Commercial and or Government experience is acceptable. Offeror’s response is limited to 8 pages.

4.1.5 Tab 4: Subfactor 2 – Draft Mission Essential Plan. IAW the provision at DFARS 252.237-7024 Notice of Continuation of Essential Contractor Services, offerors shall submit a draft of their Mission Essential Contractor Services Plan to support the services listed in the PWS, Appendix E. The plan will be evaluated as technically “acceptable” or “unacceptable” as part of the technical submission. The plan will be finalized after award, prior to the first day of performance.

4.1.6 Tab 5: Subfactor 3 – Scenarios. For offeror’s who remain in consideration after evaluation of Subfactors 1 and 2, scenarios will be provided on 06 August 2020with at least three business days notice, on a yet to be determined date. Offerors will be given the scenarios via email at 9:00 A.M. MDT. The Government will allow the offerors 30 hours to provide responses. Offeror’s shall provide an email address for acceptance of the scenarios on behalf of the company. Responses shall not exceed 10 pages (a page is defined in Section L, paragraph 3.8.5). The scenario topics will include typical problem solving in the areas of GBSOC, SDIN, MIR, MOC and MILSATCOM. The offeror shall provide a sound technical approach demonstrating an understanding of the issues identified in the scenarios provided. The offeror shall include all assumptions used within the response to each scenario.

4.2 Volume II - Past Performance. This portion of the evaluation will consider the offeror's performance and that of its affiliates, subcontractors, teammates and/or joint venture partners. The information submitted as past performance is separate from the information submitted for Technical Experience; however, this information can be duplicative.

4.2.1 Provide rationale if no past performance information is submitted for a particular team participant. This information is requested of the offeror and all affiliates, subcontractors, teammates and/or joint venture partners. The Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance. Offerors (including affiliates, subcontractors, teammates and/or joint venture partners) shall only submit past performance in the areas that they are proposed to perform IAW Attachment L-7 - Relevancy Matrix.

4.2.2 General. Offerors are cautioned that the Government will use data provided in this volume and data obtained from other sources in the evaluation of past performance. The CO may contact Government installations where the offeror performed or other performance information sources. The performance information sources may include qualified, impartial sources of information, for example: State Better Business Bureau, Dun & Bradstreet, etc. The CO will reference other sources to determine past performance, including Federal Awardee Performance and Integrity Information System (FAPIIS), Past Performance Information Retrieval System (PPIRS), and System for Award Management (SAM).

4.2.3 Past Performance Volume Format. There is no volume page limitation. Each citation is limited to the space limitation of the Past Performance Information (PPI) Tool. The offeror shall format the Past Performance Volume as follows:

4.2.3.1 Executive Summary. The Past Performance Volume shall include an Executive Summary and a Table of Contents. The Executive Summary shall describe the role of the prime and each teaming partner that will potentially perform on the contract.

4.2.3.1.1 Organizational Structure Change History. Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this executive summary, a roadmap describing all such changes in the organization of the company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes affects the relevance of any efforts identified for past performance evaluation / performance confidence assessment. Since the Government intends to consider past performance information provided by other sources, as well as that provided by the offeror(s), the roadmap should be both specifically applicable to the efforts identified and general enough to apply to efforts on which the Government receives information from other sources. Include traceability data.

4.2.3.2 Tab 2: Relevancy Matrix. The proposal shall provide a completed relevancy matrix for the offeror including each proposed teaming partner (see format at Attachment L-7) for areas the team is proposed to work. Do not identify past performance for proposed team members in areas they are not proposed to perform. The tab has no page limitation. Each offeror (including affiliates, subcontractors, teammates and/or joint venture partners), will be assessed for relevancy as outlined in Section M, paragraph 2.3.2.3.

4.2.3.3 Tab 3: Relevant Contracts. Submit information IAW the instructions for the PPI tool, Attachment L-3, for up to three recent citations per focus area that is identified in Attachment L-7. Include rationale supporting the offeror’s assertion of relevance. For a description of the characteristics or aspects, the Government will consider in determining recent and relevant, see Section M, paragraph 2.3 – Past Performance.

4.2.3.3.1 Specific Content. Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts, as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required.

4.2.3.4 Tab 4: Consent Letters. The proposal shall contain a consent letter, executed by each affiliates, subcontractor, teaming partner, and/or joint venture partner, authorizing release of past performance information to the offeror so the offeror can respond to such information. Past performance information submitted concerning subcontractors and teaming partners, if proposed, cannot be disclosed to a private party without the subcontractor’s or teaming partner’s written consent. Because the offeror is a private party, the Government will need consent before disclosing subcontractors / teaming partner’s present and past performance information to the offeror during exchanges. In an effort to assist the Government evaluators in assessing past performance relevancy and confidence, request the subcontractor / teaming partners identified in the offeror’s proposal complete the consent (if any). Should the offeror not submit consent, the Government will only discuss past performance information directly with the prospective subcontractor or teaming partner that is being reviewed. If there is a problem with the proposed subcontractor’s or teaming partner’s past performance, the offeror can be notified of a problem, but no details may be discussed without the subcontractor’s / teaming partner’s permission. A sample consent letter is attached to the solicitation as Attachment L-4. There is no page limit for the information in this tab.

4.2.3.5 Tab 5: Client Authorization Letters. The proposal shall include client authorization letters for each identified effort for a commercial customer authorizing release to the Government of requested information on the offeror’s performance. A sample client authorization letter is attached to the solicitation as Attachment L-5.

4.3 Volume III – Cost / Price.

4.3.1 Price. This portion of the evaluation will consider the offeror’s proposed price for the proposed support.

4.3.1.1 FACTOR 1 - Price. All activities associated with the processes described in the offeror’s proposal to perform the required services must be priced within this volume. The offeror shall ensure the information presented in the volume is consistent with the information contained in the other parts of the proposal. The offeror shall provide a firm fixed price proposal that reflects the offeror’s planned approach and labor mix. The offeror’s price proposal may vary from, but shall not exceed the government's budget.

4.3.1.2 Price Information Requirements. IAW FAR 15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. Information shall be provided IAW FAR 15.403-5. If, after receipt of proposals, the PCO determines that there is insufficient information available to determine price reasonableness, and none of the exceptions in FAR 15.403-1 applies, the offeror shall be required to submit cost or pricing data. Information beyond that required by this instruction shall not be submitted, unless the offeror considers it essential to document or support its price position.

4.3.1.3 Price Reasonableness and Affordability. These instructions are to assist the offeror in submitting information, other than cost or pricing data, which is required to evaluate the reasonableness and affordability of the offeror’s proposed price. Compliance with these instructions is mandatory and failure to comply may result in rejection of the proposal. Offerors are cautioned to ensure their pricing is balanced IAW FAR 15.404-1(g). Note that unrealistically low or high proposed price, initially or subsequently, may be grounds for eliminating an offeror from the competitive range either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Offers shall be sufficiently detailed to demonstrate reasonableness and affordability. The burden of proof for credibility of proposed price rests with the offeror.

4.3.1.4 Rounding. All dollar amounts, to include unit prices, shall be rounded to the nearest whole dollar.

4.3.1.5 Government Approved Travel, Equipment, Supplies, and Incidentals CLIN. The government has provided an estimated amount for materials and travel. No additional cost breakout is required. The established baseline amounts include allowances for reimbursement of applicable contractor burdens. No profit is allowed for these costs. However, prime contractor G&A burden is allowed and shall be identified, if applicable. (See Ceiling G&A rates - Section L, paragraph 4.3.1.7)

4.3.1.6 SDIN Technical Refresh Cost Reimbursable CLIN. The government has provided an estimated amount for the SDIN Technical Refresh. No additional cost breakout is required. The established baseline amounts include allowances for reimbursement of applicable contractor burdens. No profit is allowed for these costs. However, prime contractor G&A burden is allowed and shall be identified, if applicable.

4.3.1.7 Ceiling G&A Rates. The Cost Reimbursable CLIN values are estimated amounts. It is uncertain whether they will be funded in whole, in part or at all. Reimbursement using these funds will not contain profit or fee, but are subject to applicable G&A rates. The Offeror shall propose a “Rate Ceiling” for the G&A applied to the estimated cost reimbursable CLINs. This Rate Ceiling will be multiplied by the estimated ODC CLIN amounts and the product will be added to the Total Evaluated Cost/Price (TEP) of the proposal. The clause H-001 will be included in the final contract to document this G&A Rate Ceiling applicable to ODC reimbursement. Actual G&A rates established through DCAA audits will apply up to the ceiling rate proposed.

4.3.2 Tab 1: Total Price Summary – Attachment L-1.

4.3.3 Tab 2: Cross-Referencing Proposal to Staffing Plan. The offeror’s price proposal shall be cross-referenced to the proposed staffing plan presented in Volume IV - Contract Documentation. The level of detail in the staffing plan, presented to support the Professional Employee Compensation Plan shall match and be cross-referenced to the price data.

4.4 Volume IV - Contract Documentation. This volume shall contain the offeror’s contractually related documentation. All documentation shall be clearly identified for each member of the offeror’s team. The offeror shall format its Contract Documentation volume as follows:

4.4.1 Tab 1: Completed Standard Form 33 (Solicitation, Offer, and Award). Complete Section A of the SF33, as applicable. Signature by the offeror on the SF 33 constitutes an offer, which the government may accept. In doing so, the offeror accedes to the contract terms and conditions as written in the solicitation Sections A through J unless specific exception is taken. These sections constitute the model contract. The contractor shall specify the proposal acceptance period, which shall be valid for a minimum of 365 days.

4.4.2 Tab 2: Completed Section B - Supplies or Services and Prices / Cost.

4.4.3 Tab 3: Section G - Contract Administrative Data. (Not used)

4.4.4 Tab 4: Section H - Special Contract Requirements. The Offeror shall submit a ceiling G&A rate to be included in the contract clause H-001. This rate shall be used as a not to exceed G&A rate. DCAA audited rates shall be applicable so long as the rate does not exceed the proposed ceiling G&A rate.

4.4.5 Tab 5: Completed Section I - Contract Clauses - IAW FAR 52.219-14 Limitations on Subcontracting, (Class Deviation 2019-O0003) primes shall submit certification, demonstrate how it is performing at least 50% of the effort, and provide this information within Tab 5. Information for this certification is limited to two pages.

4.4.6 Tab 6: Completed Section K - Representations and Certifications - Provide a signed copy of the representations and certifications within Section K of this proposal.

4.4.7 Tab 7: Other Representations - Complete other statements or representations required by the solicitation, or which the offeror chooses to bring to the attention of the CO. Additionally, submit a copy of any teaming arrangements.

4.4.7.1 Joint Venture Agreements and Mentor Protégé Agreements. Joint Ventures and Mentor protégé are allowable on competitive Small Business set-asides; however, Small Business Administration (SBA) prior to contract award must approve the agreements. If the offeror is contemplating an agreement on this project, the offeror must advise, in writing, the assigned SBA Business Opportunity Specialist (BOS) as soon as possible. It is also recommended that the agreement be submitted as soon as practicable to ensure compliance with established regulations. Any corrections and/or changes needed can be made only when the BOS has adequate time for a thorough review before the proposal due date.

NO CORRECTIONS AND/OR CHANGES ARE ALLOWED AFTER TIME OF SUBMISSION OF PROPOSAL.

4.4.8 Tab 8: Other Information Required.

4.4.8.1 Authorized Offeror Personnel. Provide the name, title, telephone number and, email address of the company / division point of contact regarding decisions made with respect to the proposal and who has authority to obligate the offeror’s company contractually. Also, identify those individuals authorized to negotiate with the government.

4.4.8.2 Company / Division Address, Identifying Codes, and Applicable Designations. Provide company / division's street address, and facility code; CAGE code; data universal numbering system (DUNS) code; size of business (large or small) and labor surplus area designation.

4.4.9 Tab 9: Financial Documentation.

4.4.9.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 cash flow statements as required by FAR 9.104-1(a) and DFARS 232.072.

4.4.10 Tab 10: Professional Employee Compensation Plan.

4.4.10.1 General Information. IAW the provision at FAR 52.222-46, Evaluation of Compensation for Professional Employees, the offeror shall submit a total compensation plan setting forth salaries and fringe benefit package proposed for the prime's professional employees. The prime offeror should instruct its subcontractors to submit total compensation plan directly to the contracting officer. 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. Submit utilizing Attachment L-6 - Professional Employee’s Compensation Plan.

4.4.11 Tab 11: Other Documentation / Information Required

4.4.11.1 DD254. The offerors shall provide evidence of their ability to meet the Facility Clearance Requirements of this effort, and complete the DD 254 Security Requirements Block 6, a., b., and c. Failure to meet this requirement shall be cause to reject the offeror’s proposal.

4.4.11.2 Organizational Conflicts of Interest (OCI). Pursuant to FAR 9.504(a), offerors shall submit potential OCI situations, or contracts that may pose OCI concerns, or any situation that may prohibit the offeror from submitting a proposal for this effort. The offeror is required to identify any real or perceived OCI issues and submit an OCI mitigation plan at the time of proposal in accordance with provision 5352.209-9001, Potential Organizational Conflict of Interest. The OCI mitigation plan is not an evaluation criterion; it is a basic contract requirement. Failure to provide the required information, or demonstrate the ability to successfully mitigate the OCI, will result in the offeror being ineligible for award.

5.0 Section L – Attachments

Table L-2 - Section L Attachments