View the file

Other files

File Type Posted
FedBizOpps Posting.docx DOCX document
Amendment 10 SF30 Summary of Changes.doc DOC document
Amendment 10 CSMC RFP 11 Dec 09.docx DOCX document
Amendment 9 CSMC RFP 11 Dec 09.docx DOCX document
Amendment 9 SF30 Summary of Changes.doc DOC document
Amendment 8 Attachment L-3 MWMD PWS FINAL 13 Oct 09.doc DOC document
Amendment 8 CSMC RFP.doc DOC document
Amendment 8 SF30 Summary of Changes.doc DOC document
Amendment 7 SF30 Summary of Changes.doc DOC document
Amendment 7 CSMC RFP.doc DOC document
Amendment 7 Questions Responses.doc DOC document
Attachment 5 Section L Attachments Amendment 6.doc DOC document
SF30 Summary of Changes - Amendment 6.doc DOC document
CSMC RFP Amendment 6.doc DOC document
Block 13 Continuation Sheet 2 Oct 09.docx DOCX document
Q A 29 Sep 09.docx DOCX document
Amendment 5 Attachment L-3 MWMD PWS FINAL 29 Sep 09.doc DOC document
Questions Responses - Amendment 5.doc DOC document
CSMC RFP 29 Sep 09 Amendment 5.doc DOC document
SF30 Summary of Changes - Amendment 5.doc DOC document
SF30 Summary of Changes - Amendment 4.doc DOC document
Questions Responses - Amendment 4.doc DOC document
Amendment 4 Attachment L-3 MWMD PWS FINAL 25 Sep 09.doc DOC document
CSMC RFP 25 Sep 09 Amendment 4.doc DOC document
Q A 25 Sep 09.doc DOC document
SF30 Summary of Changes - Amendment 3.doc DOC document
Amendment 3 Attachment L-3 MWMD PWS FINAL 23 Sep 09.doc DOC document
CSMC RFP 23 Sep 09 Amendment 3.doc DOC document
Attachment L-2 MILSATCOM CSMC PWS Amendment 3.docx DOCX document
Questions Responses - Amendment 3.doc DOC document
Attachment 5 Section L Attachments Amendment 3.doc DOC document
Q A 23 Sep 09.doc DOC document
Questions Responses - Amendment 2.doc DOC document
Attachment 8 Contingency Plan Template.doc DOC document
Amendment 2 Attachment L-3 MWMD PWS FINAL 21 Sep 09.doc DOC document
Attachment 9 OCI Disclosure and Analysis Form.xlsx XLSX spreadsheet
Attachment 1 CSMC PWS FINAL 21 Sep 09.docx DOCX document
Attachment 3 CSMC 254 21 Sep 09.pdf PDF
Attachment 5 Section L Attachments 21 Sep 09.doc DOC document
SF30 Summary of Changes - Amendment 2.doc DOC document
CSMC RFP 21 Sep 09 Amendment 2.doc DOC document
Q A 22 Sep 09.doc DOC document
Q A 21 Sep 09.doc DOC document
Attachment 5 Section L Attachments Amendment 1.doc DOC document
CSMC RFP 15 Sep 09 Amendment 1.doc DOC document
CDRL 0026 Sec H-2 Limitations on Subcontracting 15 Sep 09.rtf RTF text file
Questions Responses - Amendment 1.doc DOC document
Attachment 6 Proposal Delivery Directions.docx DOCX document
CDRLS Master List MCCR 24.rtf RTF text file
CDRLS Master List IPSC 22 23.rtf RTF text file
Show 40 more

Latest 50 of 347 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Q&A 13 Oct 09 Questions and Answers

1. Question: The DD254 for the contract has been updated with the requirement that “the contractor is required to have access to existing contractor SIPRNet upon contract award.” In an answer to an earlier question (21 Sep 2009), it was stated that the contractor could use a teammate’s SIPRNet connection. Now that the DD254 has been changed, is that statement still true? If a contractor/contractor team fails to demonstrate SIPRNet connectivity at the time of submission of the two task order proposals, will that contractor’s task order proposals be deemed “inadequate” and could the contractor be disqualified on this basis alone from receiving a CSMC award?

Answer: Offerors may still gain access to SIPRNet via a teammate’s SIPRNet. Access to SIPRNet is not evaluation criteria; however, it is a requirement of the MILSATCOM PWS.

2. Question: Volume II, MILSATCOM Task Order Performance Work Statement (PWS), Paragraph 1.4, “Facilities and Supplies.” The reference states: “SIPRNET access is required to support this task order.” As the Government knows, obtaining contractor facility SIPRNET access is a process that includes a partnership of the Defense Security Service, the Government Sponsor and the Contractor. Will the Government relax the requirement for SIPRNET access to support the task order, or will the Government relax the timing of access to allow for approval and installation post-award?

Answer: The Government will allow a reasonable amount of time for an offeror to establish SIPRNet capability at the offeror’s facility with the understanding that the offorer shall make progress for SIPRNet capability immediately after task order. Until contractor SIPRNet capability is established, the Government will provide 10 SIPRNet connections within Building 1 for use by the contractor to accomplish MILSATCOM PWS requirements. Requirements stated in the MILSATCOM PWS must be accomplished during the interim without mission degradation. Each offeror shall determine an approach to meet PWS requirements in the interim pending establishment of SIPRNet capability at the contractor facilities.

File details come from the government source that posted it. Updated .