PF2-RFP-Attachment_5-addenda_to_52_212-1.pdf
PDF 114 KB Posted
- Attached to
- COMSATCOM Pathfinder #2 Federal contract opportunity
- Solicitation number
- FA8808-17-R-0004
About this file
PF2-RFP-Attachment 5-addenda to 52 212-1
View the file
Other files for this federal contract opportunity
Show all 27
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
UNCLASSIFIED
Attachment 5
COMMERCIAL SATELLITE
COMMUNICATIONS (COMSATCOM)
Pathfinder #2
ADDENDA TO 52.212-1
INSTRUCTIONS TO OFFERORS --
COMMERCIAL ITEMS
FA8808-17-R-0004
16 MAY 2017
THIS PAGE INTENTIONALLY LEFT BLANK
UNCLASSFIED
ADDENDA TO 52.212-1 INSTRUCTIONS TO OFFERORS - COMMERCIAL ITEMS
THIS SECTION IS FOR SOLICITATION PURPOSES ONLY. THIS SECTION WILL BE
PHYSICALLY REMOVED FROM ANY RESULTANT AWARD.
THIS ADDENDA SUPPLEMENTS FAR 52.212-1.
INSTRUCTIONS TO OFFERORS
Notice: The following provisions are hereby replaced in full text:
Addendum to 52.212-1(c), Period for Acceptance of Offers. The offeror agrees to hold the prices in its offer firm for 180 calendar days from the date specified for receipt of offers.
PROPOSAL PREPARATION INSTRUCTIONS
Each Offeror is required to submit their proposal as specified in solicitation provision 52.212-1, Instructions to Offerors-Commercial Items, along with the following addendum. Failure to provide any required information may result in an offer being determined unawardable.
A. Proposal Submittal and Inquiries.
1. The Procurement Contracting Officer (PCO), Ms. Eva Rae Hoskins, is the sole point of contact for this acquisition. All questions or concerns must be directed to the PCO at eva.hoskins.1@us.af.mil. On all email correspondence (reference additional guidance in paragraph 2. below) courtesy copy the lead Contract Specialist, Mr. Dominic Garcia Jr. at dominic.garcia.8@us.af.mil. Questions regarding the solicitation must be in writing and emailed to the PCO (with a courtesy copy) no later than ten (10) calendar days prior to the close of the solicitation due date. The Government may choose not to accept any questions after this time. You may confirm receipt of your question by requesting a return email. A copy of the returned email, along with associated metadata, shall be proof of receipt of the question. All answers to questions and any amendments to this solicitation will be posted to the Federal Business Opportunities (FedBizOpps) website at www.fbo.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.
2. All communications between the Government and Offerors will be controlled by the PCO.
Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. In order to facilitate the sending and receiving of encrypted emails, offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. To insure the process is working correctly, send a test encrypted message first (without including any source selection information).
http://www.fbo.gov/ https://cs1.eis.af.mil/sites/afcc/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc#T2101 https://cs1.eis.af.mil/sites/afcc/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC#b3104
3. Proposals are due no later than 5:00 P.M., Pacific Standard Time on 31 August 2017.
Proposals may be mailed or delivered via courier service to the physical address below so they are received by the contracting office by the due date and time.
For shipments using the United States Postal Service (USPS):
Space and Missiles System Center (SMC) – MILSATCOM/PKJ ATTN: Ms. Eva Rae Hoskins, Procurement Contracting Officer 2310 El Segundo Blvd Aerospace Visitor Center #1 El Segundo CA 90245
For shipments using Couriers/Physical Address (Fed Ex, DHL, and UPS):
Space and Missiles System Center (SMC) – MILSATCOM/PKJ ATTN: Ms. Eva Rae Hoskins, Procurement Contracting Officer 483 N. Aviation Blvd El Segundo, CA 90245
Proposals received after the specified date and time shall be handled in accordance with FAR 52.215-1 Instructions to Offerors-Competitive. Delivery of proposals before the proposal due date shall be coordinated with the PCO.
B. General Instructions/Information.
1. The Government intends to award a contract to the Offeror who provides the Lowest Price Technically Acceptable (LPTA) offer to the Government based on the evaluation of the factors and subfactors in the addenda to provision FAR 52.212-2 – Evaluation of Commercial Items, Attachment 6, of this solicitation. The Offeror’s proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. The Offeror shall be compliant with the requirements as stated in the SOW, TRD, CDRLs and Model Contract. Non-Conformance with the instructions provided in this ITO may result in an offer being ineligible for award.”
2. The Government intends to award without discussions. Offerors are encouraged to present their best technical proposal and prices in their initial proposal submission.
3. The submission of the documentation specified below will constitute the Offeror's acceptance of the terms and conditions of the solicitation, the Statement of Work (SOW) (Attachment 1 of this solicitation), and the Technical Requirements Document (TRD) (Attachment 2 of this solicitation). A written notice of award or acceptance of an offer, mailed or otherwise furnished to the successful Offeror within the time for acceptance specified in the offer, shall result in a binding contract without further action by either party. Before the offer's specified expiration time, the Government may accept an offer (or part of an offer), whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award.
4. The Offeror’s proposal shall be clear, concise, and include sufficient detail for substantiating the validity of stated claims. The proposal should not rephrase or restate the
Government’s requirements, but shall provide rationale to address how the Offeror intends to meet the requirements. The Offeror shall assume that the Government has no prior knowledge of the Offeror’s facilities and experience. The Government will make its evaluation based solely on the information presented in the Offeror’s proposal.
5. Proposals that do not address requirements within the SOW and TRD may not be considered and will be deemed unawardable.
6. Offerors are required to meet all solicitation requirements, terms and conditions, representations and certifications, and technical requirements. Failure to comply with the terms and conditions of the solicitation may result in the offeror being determined unawardable.
7. If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately, notify the Contracting Officer in writing with supporting rationale, as well as, the remedies the Offeror is asking the Contracting Officer to consider as related to the omission or error. Such notices shall be received no later than ten (10) calendar days prior to the close of the solicitation due date.
The Government may choose not to consider any notices after this time.
8. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.
9. The Government reserves the right to cancel this solicitation, either before or after the closing date for receipt of proposals. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an Offeror for any costs.
10. All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at www.fbo.gov.
11. Non-Government Advisors. Offerors are advised that data submitted to the Government in response to this solicitation will be released to individuals who work for the following companies as non-government advisors for review and analysis. Per Air Force Federal Acquisition Regulation Supplement (AFFARS) 5315.305(c)(2)(v), the Offeror may object to the release of its proposal information to any non-Government advisor. The Offeror shall expressly state in the Executive Summary section of its proposal whether or not it concurs with the release of its proposal information to the below non-Government advisors.
Table 1. Non-Government Advisors
Company Name
DISA Support Contractor (TriSept Corporation)
Technical, non-cost
FFRDC Support Contractor (Aerospace Corporation)
Technical, non-cost http://www.fbo.gov/
C. Proposal Preparation Instructions.
1. The proposal instructions in this section are designed to assist Offerors in preparing a complete response that reflects a full understanding of the approach proposed to accomplish all the requirements as stated in the SOW, TRD, and evaluation criteria.
2. Offeror’s proposal shall consist of three (3) separate volumes:
Volume I – Contract Documentation
Volume II – Technical Capability
Volume III – Cost/Price
Proposal Format:
(a) Documents submitted in response to this solicitation must be fully responsive to and compliant with the following:
i. Requirements of the solicitation (Sections A-K of the Model Contract, the SOW, the TRD, and Contract Data Requirements List (CDRL) Exhibit A).
ii. Evaluation factors for award in accordance with addenda to provision FAR 52.212-2 – Evaluation of Commercial Items, Attachment 6, of this solicitation.
iii. Any limitation on the number of proposal pages. Pages exceeding the page limitations set forth in this provision will not be read or considered in the evaluation of the proposal.
(b) Offerors shall submit an original and two (2) hard copies of their proposal listed in Table 2 - Number & Type of Copies Required, below. In addition to submitting hard copies of the proposals, two (2) digital copies shall be provided on CD-ROM disk. All CDs shall be placed in plastic sleeves in their respective binder.
Table 2. Number & Type of Copies Required
VOLUME TITLE
NO. HARD
COPIES
*NO. OF DIGITAL
COPIES
(CD ROM)
PAGE
LIMITS
I Contract Documentation 2 2 N/A
II Technical Capability 2 2 20
III Cost/Price 2 2 N/A
*Where there are inconsistencies between the hard copy proposal and the digital copy of the proposal, the hard copy proposal shall take precedence.
The electronic copies of the proposal shall be in a format readable by Adobe Acrobat 9.0 (with ”Select” and “Copy” enabled to allow for text and graphics transfer), Microsoft (MS) Word 2010, MS Excel 2010, Crystal Ball, ACE-IT, MS Project 2010, Palisade @Risk, SEER-SEM 8.0 and MS PowerPoint 2010. Hypertext links may be used to facilitate navigation within the document. Use separate files to permit rapid location of all portions, including exhibits, annexes, and attachments, if any. Each volume shall be in a different CD-ROM directory. If files are compressed, the necessary decompression program (e.g., WINZIP) must be included. The proposal shall include the native file (e.g., .DOC(x)) and .PDF versions of all textual material.
(c) Proposals shall be organized into 3 (three) volumes. Each volume of the proposal should be separately bound in a three-ring loose leaf binder which shall permit the volume to lie flat when open. Do not overload binders and do not use staples. Each volume must include a cover sheet with the following information:
i. Volume number and name of volume
ii. Solicitation title
iii. Offeror’s name, address, and contact information
iv. Date of proposal and validity date
v. Indication of whether the volume is an original or copy
vi. Cage Code
vii. DUNS Number
viii. Tax Identification Number (TIN)
1) The spine of each volume should include the following information from the list above: i., ii., iii., and v.
2) Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.
3) All volumes shall contain page numbers. Offerors shall use a standard page numbering system.
4) Each volume shall contain a glossary of all abbreviations and acronyms used, with a definition for each.
(d) Proposals must be prepared as follows:
1) Proposals shall be submitted on 8 ½” x 11” paper, except for fold-outs used for charts, tables or diagrams, which may not exceed 11” x 17”.
2) All pages shall be printed on one side only.
3) All documentation provided in the proposal must be in English. Should any original document (i.e. certification) be issued by a non-u.s. entity, an English translation shall accompany the document.
4) Margins for all pages shall be at least 1-inch on the top and bottom and ¾-inch on the side.
4) All text shall be single spaced and printed black on white paper; black and white requirement does not apply to graphics, photos, etc. - company stationary and logos are acceptable. Printing shall be easily readable; 12-pitch type, Times New Roman font.
6) Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, and plans. Foldout pages shall fold entirely within the volume, and count as two pages for each side used. Foldout pages may only be used for large tables, charts, graphs, diagrams, and schematics, but not for pages of text. Text inside graphics, matrices, spreadsheets, focus boxes, and tables shall use single-line spacing and shall be no less than 10-pitch type, Times New Roman font.
7) Elaborate formats, bindings or color presentations are not desired or required.
8) The Offeror shall number each page in order to eliminate any confusion. In the event the Offeror creates an ambiguity in their numbering of pages, the Government may exercise its own discretion in counting pages.
9) All information submitted in the proposal shall be unclassified.
(e) Cross Referencing:
1) Each volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other parts of the proposal.
2) Information required for proposal evaluation, which is not found in its designated volume, will be assumed to have been omitted from the proposal.
3) Each response to each sub-factor shall be self-contained. No cross-referencing between sub-factor responses is permitted.
(f) Proposal Limitation. The proposal shall not exceed the limits stated in Table 2 - Number & Type of Copies required, above. If the page limits are exceeded, the pages in excess of the limit shall not be read or considered in the evaluation of the proposal and will not be returned to the Offeror.
1) Page limits include: all attachments, appendices, charts, graphs, diagrams, tables, photographs, and drawings. Note: completed TAB T1 and TAB T2 are excluded from the page count limitations.
2) Page limits do not include: covers sheets for volumes, tables of contents, glossary of abbreviations and acronyms, indices, title pages, and section dividers/tables if they are inserted solely to provide ease to the reader in locating parts/sections of the proposal. Pages will be counted if they contain any other information, i.e., diagrams, extraneous data, etc. Pages marked “This page intentionally left blank” will not be counted.
(g) Technical Attachments/TABS. TABs T1 through T3 will be used in the evaluation of Technical subfactors and shall support the Offeror’s proposed approach. More than one Technical Attachment/TAB may be combined in sequential order in a single binder;
however, Offerors shall clearly tab each Technical Attachment/TAB so it is clear which Attachment/TAB is being reviewed. Offerors shall identify the Attachment/TAB numbers contained in the binder. TABs T1 and T2 can be found in Appendix 1 of this document.
TAB T3 can be found in Attachment 5.
3. Proposal Content
(a) Volume I – Contract Documentation. Offerors shall submit the required documentation below:
i. TAB A, Solicitation, Offer and Award – Complete blocks 12, 17a. (including CAGE code) and 30a.-c. of the Standard Form (SF) 1449 (Solicitation, Offer and Award). In doing so, the Offeror accedes to the contract terms and conditions as written in the solicitation/Request for Proposal (RFP), with attachments. The solicitation constitutes the model contract. Provide a signed SF 1449 and signed SF 30 (Amendment of Solicitation/Modification of Contract), if applicable. All solicitation amendments must be acknowledged in accordance with FAR 52.212-1, Instruction to Offerors-Commercial Items and submitted with the proposal. The Offeror shall provide the name, title and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.
ii. TAB B, Section B (Supplies or Services and Prices/Costs) - The Offeror shall complete pricing information for all CLINs as part of the basic contract by inserting the proposed price in the “Descriptive Data” and the Unit Price and Total Item Amount in the blanks provided for each CLIN in Section B of the SF 1449.
iii. TAB C, 52.212-3, Offeror Representations and Certifications – Commercial Items
(Apr 2016) - The Offeror shall ensure the provision is thoroughly completed with all blocks in each certification/representation completed truthfully and completely.
In addition, Offerors shall complete and submit the required evidence per Federal Acquisition Regulation 52.204-7 System for Award Management and 52.204-13 System for Award Management Maintenance.
iv. TAB D, Contract Security Classification Specification (DD Form 254) – The
Offeror shall complete the DD Form 254 per the instructions included in solicitation Attachment 3, Contract Security Classification Specification (DD Form 254).
v. TAB E, Points of Contact - Offerors shall provide primary and alternate points of contact including job title, telephone number and email address responsible for working non-disclosure agreements and subcontractor agreements as well as all program management and contracting functions. In addition, provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office, if applicable.
Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).
vi. TAB F, Attachment(s) to the Model Contract – The Offeror shall provide the following as an attachment to the Model Contract:
Subcontracting Plan - Participation of Small Businesses (SB), Historically Black Colleges and Universities, or Minority Institutions (HBCU/MI)
If the Offeror is other than a small business, the Offeror shall submit a Small Business Subcontracting Plan in accordance with FAR 52.219-9 that also identifies and specifies the extent of offeror's commitment to the participation of small businesses (SB), historically black colleges or universities (HBCU) and minority institutions (MI), whether as joint venture members, teaming arrangement partners, or subcontractors. If applicable, submit a copy of your approved Master Plan. In the event the Offeror has negotiated a comprehensive subcontracting plan pursuant to DFARS 219.702, the Offeror must submit the information that identifies and specifies the extent of its commitment to the participation of SB, HBCU and MI.
Associate Contractor Agreements – The Offeror shall include Associate Contractor Agreements, if applicable.
Security for Government Financing -The offeror shall submit proposed security to support Government Financing of CLIN 0001 and justify adequacy of this security in accordance with FAR Subpart 32.202-4 Security for Government Financing and 10 U.S.C. 2307(f) and 41 U.S.C.
4505.
(b) Volume II – Technical Capability – Factor 1. The Technical Volume shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims in the Offeror’s proposal. Legibility, clarity and coherence are very important. Responses will be evaluated against the technical factors defined in the addendum to provision FAR 52.212-2 Evaluation – Commercial Items, Attachment 6, of this solicitation. By submitting a proposal, offerors are representing that they will perform all the requirements in the SOW and TRD.
1. The proposal should not simply rephrase or restate the Government's requirements, but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements. Statements that the Offeror understands, can, or will comply with the SOW (including referenced publications, technical data, etc.);
statements paraphrasing the SOW or parts thereof (including applicable publications, technical data, etc.); and phrases such as “standard procedures will be employed” or “well known techniques will be used,” etc., will be considered unacceptable. The Offeror shall assume that the Government has no prior knowledge of the Offeror’s facilities and experience. The Government will base its evaluation on the information presented in the Offeror's proposal. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.
2. The Technical Volume shall be organized according to the following outline:
• Executive Summary: The purpose of the Executive Summary is to provide an overview of the Offeror’s proposal.
• Table of Contents
• List of Tables, Drawings, and Figures
• Factor 1 – Technical Capability (see below for detailed breakdown of required documentation) o Subfactor 1: USG Pre-Launch Transponder(s) Specification
TAB T1: USG Pre-Launch Transponder(s) Identification Template o Subfactor 2: Spectrum Policy Compliance TAB T2: Reserved o Subfactor 3: Cybersecurity Compliance TAB T3: Cybersecurity Compliance Matrix (CCM) o Subfactor 4: USG Pre-Launch Transponder(s) Protection.
3.1 Factor 1 – Technical Capability (Required Documentation)
i. Subfactor 1: USG Pre-Launch Transponder(s) Specification. This section will allow the Government to understand the Offeror’s proposed approach to identifying pre-launched commercial Fixed Satellite Service (FSS) transponders (the USG Pre-Launch Transponder(s)), that meet the requirements of the SOW and TRD and subsequently delivering it/them to the Government for acceptance and on-orbit operations.
The Offeror shall:
a) Identify USG Pre-Launch Transponder(s). Provide pre-launch identifying information for a minimum of one (1) transponder by completing the USG Pre-Launch Transponder(s) Identification Template, found at Appendix 1, TAB T1 of this attachment. The Transponder(s) Identification Template shall be TAB T1, of the Technical Volume. The information provided in TAB T1 will be used in the Contract Line Item Number (CLIN) item description under CLIN 0001 of the contract.
b) Provide the following information that reflects the Transponder(s) will meet the in-orbit test completion date prior to the end of calendar year 2022:
Either the planned spacecraft contract date and provider; or documentary evidence that the spacecraft is under contract and on schedule to meet the planned in-orbit test completion date listed in TAB T1; and
Either the planned launch vehicle contract date, launch vehicle type, and launch vehicle provider; or documentary evidence that the launch vehicle is under contract and on schedule to meet the planned in-orbit test completion date listed in TAB T1.
c) Identify USG Pre-Launch Transponder(s) Gain/Temperature (G/T) Performance. For each USG transponder, the Offeror shall complete Appendix 1, TAB T1, of this attachment to state the fraction of the required coverage area (as a percentage) where the G/T performance is equal to or greater than -1 dB/K. The Offeror shall provide clear supporting evidence, to include coverage contour maps, for these coverage fractions. If the G/T performance exceeds -1 dB/K over the entirety of the required coverage area, the fractional value shall be stated as 100%.
d) Identify USG Pre-Launch Transponder(s) Equivalent Isotropically Radiated Power (EIRP) Density Performance. For each USG transponder, the Offeror shall complete Appendix 1, TAB T1, of this attachment to state the fraction of the required coverage area (as a percentage) where the EIRP density performance is equal to or greater than -35 dBW/Hz. The Offeror shall provide clear supporting evidence, to include coverage contour maps, for these coverage fractions. If the EIRP density performance exceeds -35 dBW/Hz over the entirety of the required coverage area, the fractional value shall be stated as 100%.
ii. Subfactor 2: Spectrum Policy Compliance. This section will allow the Government to understand the Offeror’s proposed approach to spectrum compliance.
Requirement 2.1.: Licensing USG Pre-Launch Transponder(s)
The Offeror shall:
a) Provide a copy of any applicable national license(s) for the satellite by the national spectrum regulator for the proposed solution for the USG Pre-Launch Transponder(s). If a license has not yet been issued, the Offeror shall provide a copy of the licensing documents submitted to the national spectrum regulator (e.g., a copy of the license application and the authority’s official declaration that the application has been accepted for filing).
b) Provide a copy of the notification that the applicable frequency assignments have been entered into the ITU Master International Frequency Register (“ITU registration”), or a copy of the Coordination Request (CR) that was sent to the ITU to initiate the international spectrum coordination procedure, and a copy of the corresponding acknowledgement notification by the Bureau of Radio Communication (BR) (or, in lieu of the acknowledgement, if available, a copy of the relevant "As Received" or Coordination Request/Coordination (CR/C) data published by the BR).
c) Ensure the current version of the license and ITU registration have not been obtained through a country listed in the National Defense Authorization Act (NDAA) States-of-Concern list.
The documents provided for this requirement (2.1.) will not count towards the page count limit.
Requirement 2.2.: ITU Notification Process Competence
The Offeror shall provide a copy of a letter that has been received from the ITU for notification that any satellite within the Offeror's satellite network has been brought into use in the past.
The documents provided in this requirement (2.2.) will not count towards the page count limit.
iii. Subfactor 3: Cybersecurity Compliance. This section will allow the Government to understand the Offeror’s proposed approach to comply with DOD standards for cybersecurity.
The Offeror shall:
a) Describe the process in which the Offeror will establish a Memorandum of Agreement (MOA) with the National Security Agency (NSA) for the embedment of NSA certified cryptography into spacecraft on which the USG Pre-Launch Transponder(s) reside and will receive NSA issuance of Committee on National Security Systems Policy Number 12 (CNSSP-12) compliance letter. Additionally the Offeror shall identify the National Security Agency (NSA)-approved cryptographic techniques for telemetry and command (T&C) to/from the spacecraft.
b) The Offeror shall complete Appendix 1, TAB T3, Cybersecurity Compliance Matrix (CCM), of this attachment. The CCM shall be TAB T3, of the Technical Volume and will subsequently become the attachment under Contract Delivery Requirement List (CDRL) A002 of the contract.
This is a stand-alone document and will not count towards the page count limit. A single CCM must be submitted in its original Microsoft Excel Workbook format for evaluation. The Offeror shall only input data in unlocked shaded cells.
c) The Offeror shall identify in the CCM the compliance as “Compliant”, “Non-Compliant” or “Not Applicable” for each security control based on the Offeror’s proposed solution for this solicitation. The Offeror shall provide the facts, rationale and proposed artifacts for mitigations that support the compliance rating selected. The Offeror shall identify facts and capabilities of the proposed solution to meet the intent, according to the references, of each security control as well as identify artifacts which can be evaluated by the government during system reviews. The Offeror shall identify potential mitigations which may be implemented for all “Non- Compliant” controls. Lastly, the Offeror shall provide justification for the selection of “Not-Applicable” for any security controls. For the purposes of this evaluation, Column B depicting the platform defines “Ground” as all terrestrial components to include C2 terminals for the satellite, user terminals and mission planning systems. Any platform identified as “Space” includes the transponder as well as the satellite bus. Submission of your offer shall constitute self-certification that the information provided in support of the proposed solution is accurate.
The Contractor shall describe their practices for supply chain risk management to provide authentic material and mitigate risks for counterfeit parts.
d) The Contractor shall describe their process for vetting personnel security clearances and access control to development facilities as well as operations locations.
iv. Subfactor 4: USG Pre-Launch Transponder(s) Protection. This section will allow the Government to understand the Offeror’s proposed approach to provide the required uplink overdrive protection on the spacecraft which hosts the USG Pre- Launch Transponder(s).
The Offeror shall describe methods for analysis and/or testing to demonstrate adequate protection against transponder uplink overdrive signals in the range of 4 to 30 GHz, to include the expected delivery date of the report.
(c) Volume III – Cost/Price – Factor 2. This section will assist the offeror to submit information other than certified cost or pricing data required to evaluate the reasonableness and affordability of the proposed cost/price. Compliance with these requirements is mandatory and failure to comply may result in rejection of the offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness and affordability.
i. Price Data. Data beyond that required by this instruction shall not be submitted, unless the Offeror considers it essential to document or support their price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Cost/Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.
ii. Adequate Price Competition. The Contracting Officer has determined there is a high probability of adequate price competition for this acquisition.
Upon examination of the initial offers, the Contracting Officer will review this determination and if, in the Contracting Officer’s opinion, adequate price competition exists, no additional cost information will be requested and certification under FAR 15.406-2 will not be required. If at any time during this acquisition the Contracting Officer determines adequate price competition no longer exists, Offerors may be required to submit other than certified cost and pricing information necessary for the Contracting Officer to determine the price fair and reasonable in accordance with FAR 15.402.
iii. Cost or Pricing Data Requirements. Certified Cost and Pricing Data are not required to be submitted with the proposal at this time. In accordance with FAR 15.403-1(b) and 15.403-3(a), 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 FAR 15.403-5. The PCO will provide further instructions for content and format if additional cost and pricing data will be required.
a) The Offeror shall complete pricing information for all CLINs by inserting the proposed price in the Unit Price and Total Item Amount in the blanks provided for each CLIN in Section B of the SF 1449. It should be noted that CLINs 0002, 0003, and 0004 are Not Separately Priced (NSP). The Government intends to use Commercial Interim Payments (FAR 32.001 & 32.202-1) under CLIN 0001. A breakout of the proposed payment schedule is included as Attachment 4 of the Model Contract.
b) The Government may use various price analysis techniques and procedures defined in FAR15.404 for the purpose of determining the lowest reasonably priced offer and to make a reasonableness determination. For a price to be reasonable, it shall represent a price to the Government that a prudent person would pay in the conduct of competitive business (FAR 31.201-3). The priced proposal should be predicated on a Firm Fixed Price (FFP) pricing arrangement.
c) Affordability. Offerors shall verify that the total price for Contract Line Item Numbers (CLINs) 0001-0004 do not exceed the values in Table 3 below.
Table 3. Affordability
CLIN No. Item Description QTY Price https://cs1.eis.af.mil/sites/afcc/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b154031 https://cs1.eis.af.mil/sites/afcc/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b154033 https://cs1.eis.af.mil/sites/afcc/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b154035
0001 Pre-Launch Transponder(s) **TBD Not to Exceed $20,000,000.00
*0002
Data and Reports
(in Support of CLIN 0001) N/A Not Separately Priced
(NSP)
*0003
Satellite Health and Monitoring
(in Support of CLIN 0001) N/A NSP
*0004
Data and Reports
(in Support of CLIN 0003) N/A NSP
*CLINs 0002, 0003, and 0004 are Not Separately Priced (NSP) which means the price for these CLINs shall be included in the unit price of CLIN 0001.
**To Be Determined (TBD) by the Offeror. At least one (1) USG pre-launch transponder; in total, the USG Pre-Launch Transponder(s) shall comprise at least 72 MHz.
i. Cost/Price Volume Organization.
The offeror shall provide a consolidated Cost/Price Volume, organized as follows:
• Table of Contents
• Section 1 – Introduction Section
• Section 2 – Discussion of Business Systems, Offeror Unique
Approaches, Best Commercial Practices
• Section 3 – Cost/Price Attachments
• Attachment CP-1 to Volume III: Estimating Systems and
Disclosure Statements
• Attachment CP-2 to Volume III: Subcontractor/IWTA/Team A
Information
• Attachment CP-3 to Volume III: Subcontractor/IWTA/Team n
Information
D. List of Appendix(s): appendix(s) to this instruction are listed below:
Appendix 1: Volume II - TAB T1: USG Pre-Launch Transponder Identification Template Appendix 1: Volume II - TAB T2: Reserved Appendix 1: Volume II - TAB T3: Cybersecurity Compliance Matrix (CCM)
(End of Provision)
Appendix 1
Volume II - TAB T1: USG Pre-Launch Transponder Identification Template Complete one (1) line of TAB T1 for each USG Pre-Launch Transponder.
Primary Operator(s) Host Spacecraft Name
Transponder Identification Number or Name Planned Operational
Longitude
Planned Completion Date of In-Orbit Test for the Transponder
Transponder Center
Frequency (Uplink)
Transponder Center
Frequency (Downlink)
Transponder Bandwidth
Uplink and Downlink
Polarization of the Transponder
Confirm the Coverage Area for the Transponder
(CONUS) is Served by a Single Uplink Beam and a
Single Downlink Beam (Yes / No)
Percentage (%) of CONUS where EIRP density performance
>= -35 dBW/Hz
Percentage (%) of CONUS where G/T density performance
>= -1 dB/K
Confirm the TRD Specifications Are Met by the Relevant ITU Coordination Request (Yes/No)
Volume II - TAB T2: Reserved
| PROPOSAL PREPARATION INSTRUCTIONS |
| Appendix 1 |
| Volume II - TAB T1: USG Pre-Launch Transponder Identification Template |
Contract Documentation
File details come from the government source that posted it. Updated .