SF30_Amend 0001.pdf
PDF 200 KB Posted
- Attached to
- Commercial Broadband Satellite Program (CBSP) Federal contract opportunity
- Solicitation number
- HC1013-09-R-0001_
- Issued by
- Defense Information Systems Agency
About this file
SF30 Amendment 0001
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| SF30_Amend 0002.pdf | ||
| Attachment 1_CBSP Statement of Objectives_Amend 0001.pdf | ||
| Attachment 6_Proposal Preparation Instructions to Offerors_Amend 0001.pdf | ||
| SF1449.pdf | ||
| Attachment 4_CBSP DD Form 254_Amend 0001.pdf | ||
| Attachment 2_CBSP Price Schedule_Amend 0001.XLS | XLS spreadsheet | |
| Attachment 6_Proposal Preparation Instructions to Offerors.pdf | ||
| HC1013-09-R-0001.pdf | ||
| Attachment 1_CBSP Statement of Objectives.pdf | ||
| Attachment 5_Evaluation Criteria and Basis for Award.pdf | ||
| Attachment 2_CBSP Price Schedule.XLS | XLS spreadsheet | |
| Attachment 4_CBSP DD Form 254.pdf | ||
| Attachment 3_CBSP Past Performance Questionnaire.pdf |
Show all 13
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
HC1013-09-R-0001
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
15A. NAME AND TITLE OF SIGNER (Type or print)
30-105-04EXCEPTION TO SF 30
APPROVED BY OIRM 11-84
STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA
FAR (48 CFR) 53.243
The purposes of this amendment are as follow s:
A. To extend the date for receipt of proposals as follow s: Proposals are due at 2:00 PM Central on Tuesday, 7 April 2009.
B. To add the follow ing instructions for submitting proposals: --One (1) electronic version posted to DITCO Contracting Opportunities w ebsite: https://w w w .ditco.disa.mil/dcop/Public/ASP/dcop.asp. Attachment 6, Proposal Preparation Instructions to Offerors, has been changed accordingly.
C. To incorporate the follow ing questions and answ ers into the solicitation. If the answ ers prompted a change to another RFP document, the commensurate changes have been made and the revised documents form a part of the amendment.
1. CONTRACT ID CODE PAGE OF PAGES
1 29
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 19-Mar-2009
16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR
(Signature of Contracting Officer)(Signature of person authorized to sign)
8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HC1013-09-R-0001
X 9B. DATED (SEE ITEM 11)
02-Mar-2009
10B. DATED (SEE ITEM 13)
9A. AMENDMENT OF SOLICITATION NO.
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.
Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing Items 8 and 15, and returning 0 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE
RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN
REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
12. ACCOUNTING AND APPROPRIATION DATA (If required)
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE
CONTRACT ORDER NO. IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority)
E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
10A. MOD. OF CONTRACT/ORDER NO.
2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)
6. ISSUED BY
3. EFFECTIVE DATE
19-Mar-2009
CODE
DISA/DITCO-SCOTT
2300 EAST DRIVE - BLDG 3600
SCOTT AFB IL 62225-5406
HC1013 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
SUMMARY OF CHANGES
SECTION SF 30 - BLOCK 14 CONTINUATION PAGE
The following have been added by full text:
QUESTIONS AND ANSWERS
QUESTION #1: The RFP proposal preparation instructions require offerors to submit confirmation of registration in the OFCCP’s National Preaward Registry. [Vendor] is not currently listed in the registry because we have not been reviewed in the last two years. We have filed the appropriate reports and are prepared for the review. I understand in order to be listed in the registry a government entity must request the Department of Labor to conduct a review.
ANSWER #1: Offerors are not required to confirm their registration in OFCCP’s National Preaward Registry. Prior to awarding a contract $10 million dollars or more, agencies are required to get EEO clearance from OFCCP. To facilitate the awarding of contracts, the National Pre-Award Registry was developed. The Registry contains the names of contractors that OFCCP evaluated within the last two years. If a contracting officer finds the name of the prospective contractor on the list, he or she need only note that the company was on the list and can proceed to issue the contract. However, if the company in question is not found in the Registry, contracting officials must make a request for EEO Clearance to OFCCP. Attachment 6, Proposal Preparation Instructions to Offerors, has been revised and will be posted to FEDBIZOPPS with this RFP Amendment 0001.
QUESTION #2: Reference SOO, Attachment 6, Page 2, Paragraph C.4.b. Please advise if the following items would be included in or excluded from the page limit for combination of Volumes 1, 2, and 4: Licenses (FCC, HNAs), Link Budget Calculation Spread Sheets, Prior Coordination Notices Material, Reps/Certs (Is ORCA sufficient?), Front Materials (e.g., Table of Contents, SF 1449, Cover Pages, Cross Reference Matrices), Incident Response Plan (assuming Contractor responsibility), and Amendment Changes. Your reply will help the offerors know what materials may be excluded from the page limitations.
ANSWER #2 - Licenses (FCC, HNAs), Table of Contents, Cover Pages will be excluded in the page limit for combination of Volumes 1, 2, and 4 . Link Budget Calculation Spread Sheets, Prior Coordination Notices Material, Reps/Certs, SF 1449, Cross Reference Matrices, Incident Response Plan, and Amendment Changes will be included in the page limit for combination of Volumes 1, 2, and 4.
QUESTION #3: Reference 1: Section D of Attachment 6, Page 4, Section 3 of Volume II – Technical/Management Proposal and Reference 2: Section D of Attachment 6, Page 6, Volume IV – Contract Information, last bullet. The two references require a Subcontracting Plan. Should the Subcontracting plan be placed in both sections and, if not, in which section should it be placed?
ANSWER #3 Large business offerors must include a subcontracting plan in Volume II - Technical/Management Proposal and not in Volume IV - Contract Information. Attachment 6, Proposal Preparation Instructions to Offerors, has been revised and will be posted to FEDBIZOPPS with this RFP Amendment 0001.
QUESTION #4: Will the management approach evaluation involve the method and means that the Navy can rely on to verify the cost effectiveness of the chosen system facilities by the single contractor selected -over the period of the contract. Clarification: " chosen system facilities": the individual communication elements selected that are available from multiple suppliers where these suppliers may be in competition with the one supplier that is contracted to implement the system. Communication elements may involve satellite links and commercially available terminals among other facilities that make up the communication system to be engineered and provided.
ANSWER #4 - Refer to the Evaluation Criteria, Attachment 5 of the RFP. Subfactor 1-6, Management Approach, includes six measures for meeting the standard. The offeror is responsible for the management of all subcontractors and for establishing business partnerships and arrangements to successfully execute a program of this size and complexity.
QUESTION #5: Attachment 6 Proposal Preparation Instructions to Offerors. C.3.B. With the exception of Volume III - Cost and Price, proposals should be no more than 100 pages, that is, the combined page count for Volumes I, II, and IV should not exceed 100 pages. Are contour maps included in the Technical/Management Volume page count?
ANSWER #5 - Yes, contour maps are included in the Technical/Management Volume page count.
QUESTION #6: Attachment 6 Proposal Preparation Instructions to Offerors. C.3.B. With the exception of Volume III - Cost and Price, proposals should be no more than 100 pages, that is, the combined page count for Volumes I, II, and IV should not exceed 100 pages. Are tables, glossary, compliance matrix and key personnel resumes included in the page count?
ANSWER #6 - Tables, glossary, and compliance matrix are included in the page count. Key personnel resumes are not included in the page count.
QUESTION #7: Attachment 6 Proposal Preparation Instructions to Offerors. C.3.B. With the exception of Volume III - Cost and Price, proposals should be no more than 100 pages, that is, the combined page count for Volumes I, II, and IV should not exceed 100 pages. Are the QASP and PWS page counts within the required 100 pages for Volumes I, II and IV?
ANSWER #7 - Yes, QASP and PWS page counts are within the required 100 pages for Volumes I, II, and
IV.
QUESTION #8: 3.3.2 Points of Contact (POC). The Government requires the contractor to provide a POC at the Government Points of Presence and a single worldwide POC for 24/7/365 operations. An individual cleared to C level and empowered to make programmatic decisions. Does the Government Points of Contact requirement relate to Navy PoPs we choose to connect to or to all PoPs? Please clarify what ‘an individual cleared to the C level’ means.
ANSWER #8 - The Government requires the contractor to provide a single worldwide POC for 24/7/365 operations. “C” level means a high-level manager with overall responsibility for the analysis and interpretation of data including decision making authority relevant to the activities and events applicable to this contract. SOO para
3.3.2 has been amended to clarify.
QUESTION #9: 3.1.2 Media Capabilities. The Government requires software applications and work products that are compatible with those used by the DoD (SOAP/XML). What are the criteria for demonstrating compatibility with DoD (SOAP/XML) for software applications and work products?
ANSWER #9 - See SOO, Paragraph 3.3, Operational Support Requirements. Also see Appendix VII.
QUESTION #10: Attachment 2 CBSP Pricing Schedule Non-Bandwidth tab CLIN0228 Portability. Please provide definition of quantity and time increments for CLIN0228 Portability.
ANSWER #10 - SOO PG 6 - Per SOO Paragraph 3.2.1: Space segment frequency band portability on a space available basis that allows Navy operators of multi-band CBSP user terminals to change operating frequency bands, satellites in specific regions to adapt to changing mission requirements.
QUESTION #11: Attachment 2 CBSP Pricing Schedule Non-Bandwidth tab CLIN0224 Terrestrial BACKHAUL Circuits (Navy PoP's). What are the bandwidth requirements for the terrestrial backhaul CLIN0224?
ANSWER #11 - Per Attachment 6 Volume III- Price, Paragraph 4: Proposed prices for CLIN 0224 – Terrestrial Backhaul Circuits (Navy Point of Presence) shall be inclusive of all circuit costs to the Point of Presence.
Per SOO, Paragraph 3.2.1 Space Segment: Appendix III provides CBSP terminal segment fielding information and translates Table 1 data rate thresholds into regional RF bandwidth estimates by contract year and CBSP user terminal variant type. This information is provided to help the Contractor provide space segment capable of satisfying threshold CBSP data throughput requirements. See Attachment 5 Evaluation Criteria and Basis for Award Paragraph 9 and Bandwidth Evaluation Quantities table.
QUESTION #12: Attachment 2 CBSP Pricing Schedule Non-Bandwidth tab CLIN0225 Integration (Start-up, IA Certificate/Accreditation, MAC Levels). What is the scope of the start-up integration? What is the timeline for current services to transition to the new provider?
ANSWER #12: 60 days from award.
QUESTION #13: Attachment 2 CBSP Pricing Schedule Non-Bandwidth tab Attachment 2 CBSP Pricing Schedule Non-Bandwidth tab CLIN0229 Teleport. What are the quantity and time units for teleport services (i.e. MHz)?
ANSWER #13: See Attachment I, Pages 8 and 9 Paragraph 3.2.2.
QUESTION #14: Volume 4, Section 3 - Equal Employment Opportunity (EEO) Pre-award Clearance: Submit confirmation of registration in OFCCP’s National Preaward Registry. See FAR 22.805(a)(4) and register at http://www.dolesa.gov/preaward/OFCCP National registry is required preaward. This can only be initiated by the customer’s Contracting Officer. How should the offeror respond to this requirement?
ANSWER #14 Offerors are not required to confirm their registration in OFCCP’s National Preaward Registry. Prior to awarding a contract $10 million dollars or more, agencies are required to get EEO clearance from OFCCP. To facilitate the awarding of contracts, the National Pre-Award Registry was developed. The Registry contains the names of contractors that OFCCP evaluated within the last two years. If a contracting officer finds the name of the prospective contractor on the list, he or she need only note that the company was on the list and can proceed to issue the contract. However, if the company in question is not found in the Registry, contracting officials must make a request for EEO Clearance to OFCCP. Attachment 6, Proposal Preparation Instructions to Offerors, has been revised and will be posted to FEDBIZOPPS with this RFP Amendment 0001.
QUESTION #15: RFP - Attachment 1 - Statement of Objectives (SOO), Page 11, Paragraph 3.3.1 Last bullet. This paragraph states that : “The Government requires IA operations support to staff the positions specified in the CBSP Incident Response plan.” Will a copy of this plan be available?
ANSWER #15 - Government will provide Post Award.
QUESTION #16: RFP- Attachment I, SOO, Section 3.3, Operational Support, Page 10, Paragraph Web Based Access Tool bullet. Is the web portal intended to be operational on Day One of the completion of transition of services?
ANSWER #16: Yes; 90 days from contract award
QUESTION #17: RFP – Attachment 1 – SOO - Appendix I - CBSP User Terminal Segment Characteristics, Section Legacy CBSP User Terminal Variants (ULV FFG), Page 13, Section 1.2. Appendix I does not provide the ULV FFG terminal variant technical characteristics although the ULV FFG is specified as one of the terminals in Attachment 1, Table 1 in Section 3.2.1 Space segment, page 7 for data throughput requirements and in Appendix III, Table 4. In absence of ULV FFG terminal specifications, should it be assumed, aside from the threshold and objective data rates, that the ULV FFG antenna diameter, frequency band, maximum EIRP, G/T and polarity are the same as the ULV?
ANSWER #17 - ULV and FFG ULV are the same terminal.
QUESTION #18: RFP – Attachment 1 – SOO - Appendix II – Technical Specifications for Small Ship, Unit-level Ship, and Force-level CBSP Satellite Communications Terminal Variants, Section Legacy CBSP User Terminal Variants (ULV FFG), Page 15. Appendix II does not provide the ULV FFG terminal variant technical specifications although the ULV FFG is specified as one of the terminals in Attachment 1, Table 1 in Section 3.2.1 Space segment, page 7 for data throughput requirements and in Appendix III, Table 4. In absence of ULV FFG terminal specifications, should it be assumed, aside from the threshold and objective data rates, that the ULV FFG antenna diameter, frequency band, maximum EIRP, G/T and polarity are the same as the ULV?
ANSWER #18 - ULV FFG antenna diameter, frequency band, maximum EIRP, G/T and polarity are the same as the ULV terminal specifications.
QUESTION #19: RFP – Attachment 1 – SOO - Appendix I, CBSP User Terminal Segment Characteristics, Page 13, Paragraph 12. Section 1.2 (first paragraph) mentions that, among other parameters, the “required operational data rates” are listed in Table 2 of Section 1.2. This parameter is not found in Table 2. Could the Government please provide?
ANSWER #19 - See Table 1, Page 7 of SOO.
QUESTION #20: SOO, Appendix I, CBSP User Terminal Segment Characteristics, Page 13, Paragraph 1.2. 1. For link budget analyses purposes and in the determination of meeting SOO end-to-end availability performance requirements can a higher than SOO-specified Ku-band ULV transmit EIRP of 49.7 dBW be assumed (refer to Table 2, Section 1.2, page 13, and Table 2 excerpts at the end of this list of questions)? This question is asked because of two concerns:
a. Noted “inconsistencies” in SOO Ku-band transmit EIRPs when compared to SOO threshold data rate requirements between the ULV and SSV:
i. The 49.7 dBW Ku-band ULV EIRP is 1.3 dB lower than the 51 dBW SSV EIRP - even though the ULV has ~ 4-5 times larger threshold/objective data rates:
a. ULV = 49.7 dBW for 3.4/16 Mbps (threshold/objective)
b. SSV = 51.0 dBW for 0.881/3.36 Mbps (threshold/objective)
b. The 49.7 dBW (“SOO threshold”) Ku-band ULV EIRP may unnecessarily limit the ULV performance area at threshold (and objective) data rates, particularly if it is shown that the actual transmit EIRP may be 9.1 dB higher at
58.8 dBW. Attached is the ULV performance specification from Harris that shows a 58.8 dBW ULV Ku-band transmit EIRP capability.
ANSWER #20 - ULV Ku-band EIRP is 49.7.
QUESTION #21 (REVISED): RFP-Attachment 2, Non-Bandwidth Tab, Paragraph Portability (CLIN 0208 [CLIN 0228]). In the SOO in Section 3.2.1 (p. 6) it states an objective as: "Space segment frequency band portability on a space available basis that allows Navy operators of multi-band CBSP user terminals to select and/or change operating frequency bands to adapt to changing mission requirements." What is meant please by “subject to availability”? How can a bidder provide a fixed price without parameters?
ANSWER #21 - The Government understands that satellite constellation resources are not unlimited.
Therefore, “space available basis” or “subject to availability” is included to acknowledge this fact. Offerors should propose their best solutions to allow maximum flexibility while factoring in this reality.
QUESTION #22: RFP - Attachment 5 - Evaluation Criteria and Basis for Award, Page 3, 7, Technical/Management Evaluation,1-6, Management Approach. This “Standard” states in part “ 3. The offeror has experienced key personnel either presently on staff or resumes of potential employees with letters of commitment.”
Are the resumes of potential employees and letters of commitment required with proposal submittal? If so, do these resumes and letters of commitment count towards the 100 page limit?
ANSWER # 22 - Resumes and letters of commitment do not count towards the 100 page limit.
QUESTION #23: RFP - Attachment 5 - Evaluation Criteria and Basis for Award, Page 4, Paragraph D Volume II- Technical/Management Proposal, 2. This paragraph states that the Technical/Management Volume must contain a Performance Work Statement (PWS) that “addresses all objectives in the SOO in sufficient detail” and a Quality Assurance Surveillance Plan (QASP) “consistent with the PWS.” The SOO alone is 176 pages. (a) Are the PWS and QASP counted against the 100 Page Limit? (b) Can the PWS and QASP be contained in an Appendix that is not counted against the 100 Page Limit
ANSWER #23 – The PWS and QASP are counted against the 100 page limit.
QUESTION #24: RFP - Attachment 5 - Evaluation Criteria and Basis for Award, Page 3, Paragraph 7 - Technical/Management Proposal - 1-6, Management Approach. The “Rating Standard” for Section 1-6 states in part: “6. Subcontracting Plans submitted in accordance with FAR 19.702 are acceptable to the CO and meet the requirements of FAR 19.704.” Is it the Government’s intention that the offeror’s Subcontracting Plan is to be a part of “Volume II - Technical and Management” as well as part of “Volume IV – Contract Information”?
ANSWER #24: Large business offerors must include a subcontracting plan in Volume II - Technical/Management Proposal and not in Volume IV - Contract Information. Attachment 6, Proposal Preparation Instructions to Offerors, has been revised and will be posted to FEDBIZOPPS with this RFP Amendment 0001.
QUESTION #25: RFP - Attachment 6 - Proposal Preparation Instructions, Section Volume IV- Contract Information, Page 2, Paragraph C.4.b. Was it the Government’s actual intention to have Volume I – Past Performance and Vol IV – Contract Information count against the 100 Page Limit?
ANSWER #25 - Volume I – Past Performance: Past performance questionnaires do not count toward the page limits; past performance descriptions provided by the offeror in Volume I will count against the page limit.
Vol IV – Contract Information will count against the page limit.
QUESTION #26: RFP - Attachment 6 - Proposal Preparation Instructions, Page 6, Paragraph D - Volume IV- Contract Information. Do the completed representations and certifications (11 pages) count towards the 100 page limit? Would The Government consider lifting the page limits on the Contract Volume?
ANSWER #26 - Licenses (FCC, HNAs), Table of Contents, Cover Pages will be excluded in the page limit for combination of Volumes 1, 2, and 4 . Link Budget Calculation Spread Sheets, Prior Coordination Notices Material, Reps/Certs, SF 1449, Cross Reference Matrices, Incident Response Plan, and Amendment Changes will be
QUESTION #27: RFP - Attachment 6 - Proposal Preparation Instructions, Page 2, Paragraph C.4.b. Are Attachments or Appendices, which do not count against the Page Limitation, allowed for Volume II – Technical and Management Proposal?
ANSWER #27 - Attachments and appendices to the Technical and Management Proposal information do count against the page limitation. See Attachment 6, Page 2, Paragraph C.4.b. With the exception of Volume III - Cost and Price, proposals should be no more than 100 pages, that is, the combined page count for Volumes I, II, and IV should not exceed 100 pages.
QUESTION #28: RFP - Attachment 6 - Proposal :Preparation Instructions, Page 2, Paragraph C.4.b. Are Cover Pages, Divider Pages, Table of Contents, List of Exhibits, Acronym Lists, Attachments and etc., counted against the Page Count Limitation?
ANSWER #28 - Cover pages, divider pages, and table of contents are not counted against the page count limitation. Acronym Lists and attachments are counted against the page count limitation.
QUESTION #29: RFP - Attachment 6 - Proposal Preparation Instructions, Page 2, Paragraph C.4.b. If 11 x 17 Fold-Out Pages are used, do these count as one page?
ANSWER #29 - All pages should be standard 8 ½ x 11. However, 11 x 17 pages may be used for block diagrams, contour maps, and or spreadsheets, but they will be counted as two pages.
QUESTION #30: RFP - Attachment 6, Proposal Preparation Instructions, Page 4, Paragraph D – Volume II – Technical and Management - 2. This paragraph states that the Technical/Management Volume must contain a Performance Work Statement (PWS) and a Quality Assurance Surveillance Plan (QASP). Does the government have templates or sample PWSs and/or QASPs they wish the offeror to use?
ANSWER #30 - Example PWS and QASP templates are not available. Vendor should clearly delineate how the proposal will be implemented and how performance will be assured.
QUESTION #31: RFP – SOO, Attachment 1, Section 3.2.1, Space Segment, Page 6. For CBSP user terminal capable of operating in commercial X-band, the Government requires coverage greater than or equal to 95% of the area between latitudes 65N & 65S from 100W longitude to 110E longitude (threshold requirement) and to 95% of the area between 65N & 65S worldwide (objective requirement). Given the threshold coverage requirement includes S1 and S2 coverage areas, please confirm the Navy’s intent, if any, to operate submarines at X-band in S1. The estimated submarine requirement in S3 is in the objective coverage area from 3.2.1 for X-band. Is the estimate for submarines in S3 a requirement or an objective? If we can support 8 simultaneous submarine user terminals in the threshold coverage areas, is that compliant?
ANSWER #31 - Government response to specific scenario-type questions could limit the Government’s intent to receive offers which provide innovative solutions to meet the objectives identified in the SOO.
QUESTION #32: Appendix III, CBSP User Terminal Fielding & RF Bandwidth Estimates, Page 166, Paragraph
3.0. “Space segment bandwidth must be available to support up to eight (8) simultaneous Submarine user terminals operating as described in Appendix I, Table 2. It is estimated that up to four Submarine user terminals will operate in region S2 while the remaining four Submarine user terminals will operate in region S3 (see Figure 3 above).” The estimated submarine requirement in S3 is in the objective coverage area from 3.2.1 for X-band. Is the estimate for submarines in S3 a requirement or an objective? If we can support 8 simultaneous submarine user terminals in the threshold coverage areas, is that compliant?
ANSWER #32 - Government response to specific scenario-type questions could limit the Government’s intent to receive offers which provide innovative solutions to meet the objectives identified in the SOO.
QUESTION #33: RFP – SOO, Attachment 1, Page 12, Paragraph 3.3.2, Points of Contact. “The Government requires the contractor to provide a POC at the Government Points of Presence and a single worldwide POC for 24/7/365 operations…. An individual available 24/7 at the satellite operator center (SOC) for incident response that is cleared…An individual cleared to C level and empowered to make programmatic decisions.” (a) Does the contractor need to provide a physical person at each of the Navy PoPs shown in Paragraph 4.0, Points of Presence?
(b) Is this 24/7 operation? (c) What is the clearance level needed for the SOC incident response individual?
Secret?
ANSWER #33 - The Government requires the contractor to provide a single worldwide POC for 24/7/365 operations. No contractor presence required at Navy PoPs.
QUESTION #34: RFP – SOO, Attachment 1, Section Sections 3.2.5.1 (polarization) associated with technical specs of SSV, ULV, and FLV, Pages 20, 72, and 115. The requirements state that the antenna (associated with SSV, ULV, and FLV) shall transmit and receive linear polarized signals. Transmit/Receive polarization of either vertical/horizontal or horizontal/vertical shall be remotely selectable. Does the Government accept any space segment that will require any of the antennas (associated with SSV, ULV, and FLV) to operate in vertical/vertical or horizontal/horizontal sense of polarization?
ANSWER #34 - The government will not operate vertical transmit/vertical receive or horizontal transmit/horizontal receive.
QUESTION #35: RFP – SOO, Attachment 1, Section 3.1( technical spec for FLV), Page 114. The requirements state that simultaneous operation is required to allow transmissions in one frequency band and reception in the other frequency band. However, referring to Bandwidth Evaluation Quantities Table listed in Attachment No. 5 (Evaluation Criteria and Basis for Award) indicates all FLV requirements in all regions are mapped to C-band only.
Please clarify.
ANSWER #35 - Nothing in Attachment 5, Bandwidth Evaluation Quantities maps FLV requirements to C-band.
QUESTION #36: SOO, Attachment 6, Page 2, Paragraph C.4.b, Page Count Inclusions. Please advise if the following items will be included in the page limit for the combination of Volumes 1, 2, and 4: Licenses (FCC, HNAs), Link Budget Calculation Spread Sheets, Prior Coordination Notices Material, Reps/Certs (Is ORCA sufficient?), Front Materials (e.g., Table of Contents, SF 1449, Cover Pages, Cross Reference Matrix), Incident Response Plan (assuming Contractor responsibility), and Amendment Changes.
ANSWER #36 - Licenses (FCC, HNAs, Table of Contents, Cover Pages will be excluded in the page limit for combination of Volumes 1, 2, and 4 . Link Budget Calculation Spread Sheets, Prior Coordination Notices Material, Reps/Certs, SF 1449, Cross Refernce Matrices, Incident Response Plan, and Amendment Changes will be
QUESTION #37: SF 1449 in Volume IV. Will the Government provide an SF 1449?
ANSWER #37 - An SF1449 is included with Amendment 0001.
QUESTION #38: SOO, Appendix III, Page 167, Table 4. Bandwidth Requirement: Please explain how the Government arrived at the 9.7 MHz number. Without clarification and or corrections to Table 4, offerors could be considered noncompliant if they provide only the bandwidth requested. According to the SOO, the Government arrived at their bandwidth requirements by this methodology: The allocated bandwidth for a satellite carrier is calculated assuming 0.5 Turbo FEC and QPSK modulation. In this case, the allocated bandwidth is equal to the data rate multiplied by the RF carrier spacing factor (e.g., 1.35) when dissimilar RF carriers are placed adjacent to each other. The threshold requirement for the FLV is a ship receiving 21.4 Mbps and transmitting 4 Mbps. Without regard to power or bandwidth limitations, the minimum bandwidth required between large antennas would be 34.3 MHz. According to Table 4, the amount of bandwidth required for Regions S1 to S4 inclusive for an FLV terminal in transit is 9.7 MHz. This is insufficient, since the above calculation shows that 34.3 MHz is required.
ANSWER #38 - The threshold 21.4 Mbps receive and 4 Mbps transmit requirement for FLV is the specification for the terminal itself. The 9.7 MHz bandwidth requirement is the amount of total bandwidth required for Navy operations in a specific region. Vendor should not assume 9.7 MHz bandwidth is only one terminal.
QUESTION #39: SOO, Appendix III, Page 167, Table 4. Throughput Requirements for Submarines: Please explain how the Government arrived at its throughput requirements for submarines. The size of the terminals and the EIRP must considered in the link analyses process to determine if the antenna has enough power and directivity to achieve threshold using global beams. This is particularly true of the submarine terminal that has very low discrimination toward a spacecraft. Radiating sufficient power would violate ITU off-axis emissions from the antenna. This limits the EIRP that can be transmitted. In turn, this reduces the throughput that can be realistically achieved with such a small aperture.
ANSWER #39 - Terminal characteristics as listed in Table 2 are sufficient to close the link threshold and objective data rates as stated in the SOO.
QUESTION #40: SOO, Appendix III, Page 167, Table 4. Apparent Discrepancy between Rate of Capacity Growth and the Number of Terminals Deployed: Please explain this apparent discrepancy and provide a terminal deployment table that is current. The SOO states that bandwidth growth is in line with terminal deployment. The terminal deployment given is dated 2007, but Table 4 identifies the start year as Calendar Year 2008. If the deployment table is unchanged from 2007, please explain the apparent inconsistencies present in Table 4 for the rate of growth of capacity with the number of terminals deployed. For example in Region A, the number of FLV terminals to be deployed is 26. This number would use 58.2 MHz according to Table 4; however, 58.2 MHz would be insufficient bandwidth to support 26 FLVs. Fifty-four ULVs are to deployed in Region A by 2012. According to the previously discussed calculation of allocated bandwidth, each ULV will require 9.18 MHz of bandwidth. To support 54 ULVs will require 495.7 MHz of bandwidth, not 42.5 MHz. The SSV bandwidth rises three-fold for only 15 terminals.
ANSWER #40 - Not all terminals are simultaneously active or operating in the same geographical regions.
QUESTION #41: SOO, 3.3.2 Points of Contacts, Page 12. Location of Points of Contact: We suggest that this section be moved to be included under Operations Support Requirements or included with the Management Approach.
ANSWER #41 - No change made.
QUESTION #42: 52.211-3, Reps & Certs, Page 6 of 24. How to Provide Representations and Certifications: Will a statement stating that the company has filed its annual representations and certifications electronically at Http://orca.bpn.gov suffice, or should the representations and certifications themselves be included?
ANSWER #42 - The following Government clarification is provided:
If your firm’s representations and certifications have been entered into the web site at http://orca.bpn.gov/, do not include them with your offer. In this case, include (in Volume IV) the following: (1) Your firm’s DUNS number; and (2) A statement that the online representations and certifications are current; however, If your firms’ representations and certifications have not been entered at the web site, include them with your offer in Volume IV.
QUESTION #43: SOO 2.0, Reference Documents, Page 6, Last Bullet. Status of CBSP Commercial Telecon Services Pricing Table: Has this table been deleted? It is listed on page 6 of the Referenced Documents, but it is not included in the SOO.
ANSWER #43 - The table was deleted. Updated SOO reflects this change.
QUESTION #44: SOO 3.1.2, Media Capabilities, Page 6, SOAP/XML. SOAP/XML Compatibility: Please explain the requirement for SOAP/XML compatibility more fully.
ANSWER #44 - SOAP is defined as Simple Object Access Protocol, is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks. It relies on Extensible Markup Language (XML) as its message format, and usually relies on other Application Layer protocols
(most notably Remote Procedure Call (RPC) and HTTP) for message negotiation and transmission. SOAP can form the foundation layer of a web services protocol stack, providing a basic messaging framework upon which web services can be built. See SOO, Paragraph 3.3, Operational Support Requirements. Also see Appendix VII.
QUESTION #45: SOO 3.2.1 Appendix 2, Space Segment Price Schedule, Page 6, 3rd Bullet CLIN 0228.
Portability Definition: Please clarify the definition of Portability. The SOO definition of portability that includes frequency portability contradicts the definition of portability in the CLIN that includes both band and region.
ANSWER #45 - Space segment frequency band portability on a space available basis that allows Navy operators of multi-band CBSP user terminals to select and/or change operating frequency bands and/or satellites in the same or different regions to adapt to changing mission requirements and/or satellites in the same or different regions. Updated SOO reflects this change.
QUESTION #46: CLIN 0228, Portability, Non Bandwidth. The Unit of “1”: Please define the unit of “1.” Does this refer to the amount of MHz utilized in each of the regions?
ANSWER #46 - The Revised Attachment 2 - CBSP Price Schedule_Amend 0001, reflects the Unit and Quantity changes to the Non-Bandwidth CLINs. The original Attachment 2 had unit and quantity entries reversed.
QUESTION #47: SOO 3.2.1, Table 1, Page 7. Clarification of Data Requirements: AN/WSC-8 was removed from Table 1, but WSC- 8 is referred to in Table 4 of Appendix III. AN/WSC-8 is included in Appendix 1, page 13. If the legacy terminals are to be included, should the data requirements be mentioned for a period of time until replaced by the variant terminals?
ANSWER #47 - See Appendix III, Table 4 for WSC-8 data requirements.
QUESTION #48: SOO 3.3.1, Security & IA Requirements Attachment 2, DD254, Page 11, 2nd bullet. Facility Clearance Requirements: Please clarify which (of if all) facilities require facility access up to SECRET. SOO 3.3.1 requires facility access up to SECRET; however, the DD 254 requires no facility clearance. Does this mean the LES and NOC facilities are not required to be SECRET, but the PoP facilities are?
ANSWER #48 - Technical LES facilities are not required to be Secret. Proposal does require strategy to accommodate specific objectives for CBSP security and Information Assurance.
QUESTION #49: SOO 3.3.1, Security & Information Assurance requirements, Page 11, 8th bullet. CBSP Incident Response Plan: Will the Government provide a copy of the CIRP or should the contractor provide it?
ANSWER #49 - Government will provide Post award.
QUESTION #50: SOO 3.3.1, Security & IA Requirements, Page 11, 4th bullet. Lack of Attachment for DD 254:
All work is required to be done in accordance with DoD and OPSEC requirements attached to the DD 254. There was no attachment.
ANSWER #50 - Reference to the OPSEC Attachment has been removed from the SOO and from the DD254. Revised DD254 is attached.
QUESTION #51: SOO 3.3.2, Point of Contact, Page 12, Text and 3rd bullet. Location of POC for Incident Response: Please clarify the requirement for an individual available at the SOC for incident response. Is this POC to be located at the contractor SMC/NOC or at a Navy PoP?
ANSWER #51 - POC to be located at discretion of vendor. The POC will not be located at the Navy PoP.
QUESTION #52: SOO, Appendix I, Page 13, 1st Sentence. Operational Data Rates: The required operational data rates for all the terminal types (9) were deleted from the draft RFP. Are they provided elsewhere?
ANSWER #52 - See SOO, Appendix I, page 7, Table 1.
QUESTION #53: SOO, Appendix III, Page 167, Table 4. WSC-8s Bandwidth Inclusion: There no requirements for WSC-6 Bandwidth in Table 4. Should WSC-8s bandwidth be included in the table since they were removed from Table 1, page 7?
ANSWER #53 - WSC-8 bandwidth requirements are provided in Appendix III, page 167, Table 4.
QUESTION #54: SOO, Appendix VII, Page 174, Government to Commercial Service Provider Links. Provision and Control of Modem K7 Lock: Is the Modem K7 Lock identified in the first bullet Government-provided hardware, and if so, who controls it?
ANSWER #54 - K7 Lock is a function of the modem (receive status).
QUESTION #55: SOO, Attachment 6, Pages 4 & 6, Subcontracting Plan. Subcontracting Plan: Is it acceptable to provide the subcontracting plan in one volume and only refer to in another volume: Both Volume II and Volume IV request a subcontracting plan.
ANSWER #55 - Large business offerors must include a subcontracting plan in Volume II - Technical/Management Proposal and not in Volume IV - Contract Information. Attachment 6, Proposal Preparation Instructions to Offerors, has been revised and will be posted to FEDBIZOPPS with this RFP Amendment 0001.
QUESTION #56: SOO, FLV Terminal Specifications, Page 122, Paragraph 3.3.2.1.1. FLV Terminal Specifications: Please clarify. The Objective TX/RX requirement noted in SOO 3.3.2.1.1 is 21.4/103. SOO Table 1, page 7, shows 103 Mbps for Objective TX/RX. Should this read 21.4/103 (Objective)?
ANSWER #56 - The threshold 21.4 Mbps receive and 4 Mbps transmit requirement for FLV is the specification for the terminal itself. The 9.7 MHz bandwidth requirement is the amount of total bandwidth required for Navy operations in a specific region. Vendor should not assume 9.7 MHz bandwidth is only one terminal.
QUESTION #57: SOO, FLV Terminal, Page 122, Paragraph 3.3.2.1.3. FLV Modulation as an Objective: Should FLV Modulation as an objective be 16 QAM or 8 QAM? THE FLV modulation is listed up to 16 QAM on page 122, and 8 QAM on page 13.
ANSWER #57 - Refer to Appendix I, page 13, Table 2. The 16 QAM is a FLV terminal requirement.
QUESTION #58: SOO, Appendix III, Page 167, Table 4. Unspecified Legacy Terminal Data Rates: Please specify the threshold and objective data rates if they will continue to remain operational under CBSP.
ANSWER #58 - See Appendix III, page 167, Table 4, WSC-8.
QUESTION #59: Attachment 2, CLIN Structure. MHz Requirements for On-demand BW: Are there any 3 MHz requirements for on-demand BW? The CLIN Structure has a bandwidth increment: 3 MHz for projected BW Threshold. The on-demand CLINS do not address 3 MHz requirements.
ANSWER #59 - There is no 3 MHZ bandwidth increment for on-demand bandwidth.
QUESTION #60: Attachment 5, 5 - Relative Importance, Page 1. Relative Importance of the PWS and QASP:
How will the Government evaluate the PWS and QASP—as part of the technical/management factor? They are not included as subfactors for evaluation in paragraphs 4 and 5 on page 1.
ANSWER #60: The PWS and QASP will be evaluated as part of the subfactor 1.6, Factor 1, Technical/Management Approach. Reference Attachment 5, Page 2, Paragraph 7; and Attachment 5, Page 3, subfactor 1-6, items 4 and 5 in the “standards” block.
QUESTION #61: Attachment 6, Volume II, Technical / Management Proposal, Page 4, Paragraph 2. Specifics of PWS and QASP: Please provide specifics about what the Government requires in the PWS and QASP. Should these to be written from the contractor’s viewpoint of how the contractor will perform the work and ensure the quality?
ANSWER #61 - Contractor should provide details on how they will perform the work and how they will ensure the quality of services provided.
QUESTION #62: Attachment 5, 9 – Price Evaluation, Page 10. Estimate of the On-demand Requirements: To properly ensure the availability and pricing of on-demand bandwidth, would the Government consider providing an estimate of the on-demand requirements? The RFP states that On-Demand Bandwidth evaluation quantities will not be released until after contract award.
ANSWER #62 - The Government will not release On-Demand Bandwidth evaluation quantities until after contract award.
QUESTION #63: Attachment 6, Volume IV Contract Information, Page 6, Pre-award clearance of contractor.
Please clarify the requirement in Volume IV, Section 3 for offerors not currently on the National Pre-award Registry? Per FAR 22.805 and the OFCCP website, only the Government Contracting Officer can request Pre-award clearance of a contractor. Contractors cannot self register. “Placement on OFCCP’s National Pre-award Registry is valid for only two years after clearance by the OFCCP, after which the contractor is dropped from the Registry.”
ANSWER #63: Attachment 6, Proposal Preparation Instructions to Offerors, has been revised and will be posted to FEDBIZOPPS with this RFP Amendment 0001. Offerors are not required to confirm their registration in OFCCP’s National Preaward Registry. Prior to awarding a contract $10 million dollars or more, agencies are required to get EEO clearance from OFCCP. To facilitate the awarding of contracts, the National Pre-Award Registry was developed. The Registry contains the names of contractors that OFCCP evaluated within the last two years. If a contracting officer finds the name of the prospective contractor on the list, he or she need only note that the company was on the list and can proceed to issue the contract. However, if the company in question is not found in the Registry, contracting officials must make a request for EEO Clearance to OFCCP.
QUESTION #64:
RFP, Attachment 4 – DD Form 254, Block 13 continued, 11.J, Page 4. The contactor is directed to perform all work in accordance “with DoD and Navy Operations Security (OPSEC) Requirements and in accordance with the OPSEC Attachment to the DD 254.” Please provide the OPSEC Attachment to the DD254.
ANSWER #64: Reference to the OPSEC Attachment has been removed from the SOO and from the DD254. Revised DD254 is attached.
QUESTION #65: RFP- Section SF 1449- Continuation Sheet. Please provide the SF 1449 for this Continuation Sheet.
ANSWER #65: An SF1449 is included with Amendment 0001.
QUESTION #66: RFP – Attachment 2- CLIN Structure. If there is potentially not enough available satellite capacity on a single satellite to meet the “evaluation” bandwidths in a region, can separate price schedules (CLINs) be developed for alternative satellites? Would also potentially apply to satellite transitions for planned EOL/replacements/new roles expected during the 5 year timeframe.
ANSWER #66: Offerors are advised to use the price template (revised version) for their proposed solution. The CLINs are specific to regions, not to satellites.
QUESTION #67: RFP, SOO, Attachment 1, Page 9, Paragraph 3.2.2. Are there any modems available from the Government to enable transition?
ANSWER #67: Modems are GFE and will be available for the transition.
QUESTION #68: RFP, SOO, Attachment 6, Proposal Preparation Instructions to Offerors, Page 2, C.3, first bullet.
This bullet requires that one copy of the entire proposal package be submitted on a CD ROM. Does the Government have a preference for documents created in Microsoft Office 2003 of Microsoft Office 2007?
ANSWER #68: Proposals must be provided in Microsoft Office 2003.
QUESTION #69: RFP, SOO, Attachment 2, Pricing, Last Page, Non-Bandwidth. CLIN 0229 Teleport - If, in the same Region, there are two teleports, one for a frequency band and one for a different frequency band, and they have different prices, can a bidder divide the CLIN into two separate CLINs? For instance, CLIN 0229X would become CLINs 0229X1 and 0229X2.
ANSWER #69: Per Attachment 6_ Proposal Preparation Instructions to Offerors: Item #8. Teleport, CLIN 0229, NRC’s will be evaluated in the Base Year. The Government does not have a requirement to identify separate non-recurring frequency band charges in the base year.
UPDATED CLAUSES
By Reference:
52.212-4 Contract Terms and Conditions--Commercial Items OCT 2008 52.222-50 Combating Trafficking in Persons FEB 2009
In Full Text:
52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS--COMMERCIAL ITEMS (FEB 2009)
ALTERNATE I (APR 2002)
An offeror shall complete only paragraph (b) of this provision if the offeror has completed the annual representations and certifications electronically at http://orca.bpn.gov. If an offeror has not completed the annual representations and certifications electronically at the ORCA website, the offeror shall complete only paragraphs (b) through (i) of this provision.
(a) Definitions. As used in this provision:
"Emerging small business" means a small business concern whose size is no greater than 50 percent of the numerical size standard for the NAICS code designated.
"Forced or indentured child labor" means all work or service-
(1) Exacted from any person under the age of 18 under the menace of any penalty for its nonperformance and for which the worker does not offer himself voluntarily; or
(2) Performed by any person under the age of 18 pursuant to a contract the enforcement of which can be accomplished by process or penalties.
“Manufactured end product” means any end product in Federal Supply Classes (FSC) 1000-9999, except—
(1) FSC 5510, Lumber and Related Basic Wood Materials;
(2) Federal Supply Group (FSG) 87, Agricultural Supplies;
(3) FSG 88, Live Animals;
(4) FSG 89, Food and Related Consumables;
(5) FSC 9410, Crude Grades of Plant Materials;
(6) FSC 9430, Miscellaneous Crude Animal Products, Inedible;
(7) FSC 9440, Miscellaneous Crude Agricultural and Forestry Products;
(8) FSC 9610, Ores;
(9) FSC 9620, Minerals, Natural and Synthetic; and
(10) FSC 9630, Additive Metal Materials.
“Place of manufacture” means the place where an end product is assembled out of components, or otherwise made or processed from raw materials into the finished product that is to be provided to the Government. If a product is disassembled and reassembled, the place of reassembly is not the place of manufacture.
Restricted business operations means business operations in Sudan that include power production activities, mineral extraction activities, oil-related activities, or the production of military equipment, as those terms are defined in the Sudan Accountability and Divestment Act of 2007 (Pub. L. 110-174). Restricted business operations do not include business operations that the person conducting the business can demonstrate--
(1) Are conducted under contract directly and exclusively with the regional government of southern Sudan;
(2) Are conducted pursuant to specific authorization from the Office of Foreign Assets Control in the Department of the Treasury, or are expressly exempted under Federal law from the requirement to be conducted under such authorization;
(3) Consist of providing goods or services to marginalized populations of Sudan;
(4) Consist of providing goods or services to an internationally recognized peacekeeping force or humanitarian organization;
(5) Consist of providing goods or services that are used only to promote health or education; or
(6) Have been voluntarily suspended.
Service-disabled veteran-owned small business concern--
(1) Means a small business concern--
(i) Not less than 51 percent of which is owned by one or more service-disabled veterans or, in the case of any publicly owned business, not less than 51 percent of the stock of which is owned by one or more service-disabled veterans; and
(ii) The management and daily business operations of which are controlled by one or more service-disabled veterans or, in the case of a service-disabled veteran with permanent and severe disability, the spouse or permanent caregiver of such veteran.
(2) Service-disabled veteran means a veteran, as defined in 38 U.S.C. 101(2), with a disability that is service-connected, as defined in 38 U.S.C. 101(16).
"Small business concern" means a concern, including its affiliates, that is independently owned and operated, not dominant in the field of operation in which it is bidding on Government contracts, and qualified as a small business under the criteria in 13 CFR Part 121 and size standards in this solicitation.
Veteran-owned small business concern means a small business concern--
(1) Not less than 51 percent of which is owned by one or more veterans (as defined at 38 U.S.C. 101(2)) or, in the case of any publicly owned business, not less than 51 percent of the stock of which is owned by one or more veterans; and
(2) The management and daily business operations of which are controlled by one or more veterans.
"Women-owned small business concern" means a small business concern--
(1) That is at least 51 percent…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .