Questions_and_Answers_2_(all_inclusive).pdf
PDF 120 KB Posted
- Attached to
- Single Mobility System (SMS)/Coalition Mobility System (CMS) Federal contract opportunity
- Solicitation number
- HTC711-13-R-D012
About this file
Question and Answers 2 (all inclusive)
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Amendment_2_-_HTC711-13-R-D012.pdf | ||
| Conformed_HTC711-13-R-D012_(includes_all_Amendments).pdf | ||
| Atch_10_-_DODAF_SV6_ _AV1_Draft_Documents.pdf | ||
| Atch_4_-_Labor_Rates_-_Price_Proposal_Break_out.xlsx | XLSX spreadsheet | |
| Conformed_HTC711-13-R-D012_(includes_Amendment_1).pdf | ||
| Amendment_1_-_HTC711-13-R-D012.pdf | ||
| Questions_and_Answers_1.pdf | ||
| HTC711-13-R-D012_-_RFP.pdf | ||
| Atch_8_-_PWS_Sections_to_CLIN_Mapping_Table_(For_Info._only).pdf | ||
| Atch_4_-_Labor_Rates_-_Price_Proposal_Break_out.xlsx | XLSX spreadsheet | |
| Atch_7_-_PP_Log.doc | DOC document | |
| Atch_9_-_Subcontracting_Plan_Template.doc | DOC document | |
| Atch_5_-_PP_Reference_Sheet.docx | DOCX document | |
| Atch_2_-_SMS-CMS_QASP.pdf | ||
| Atch_3_-_SMS_CMS_CDRLs.pdf | ||
| Atch_1_-_DD254.pdf | ||
| Atch_6_-_PP_Questionnaire.docx | DOCX document | |
| SMS_CMS_PWS_FY14-18_-_9_May_13_(DRAFT).pdf |
Show all 18
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
SOLICITATION: HTC711-13-R-D012
SINGLE MOBILITY SYSTEM (SMS)/COALITION MOBILITY SYSTEM (CMS)
Questions and Answers
Number Question Answer
Is it possible to know the closing date for the solicitation Single Mobility System
(SMS)/Coalition Mobility System (CMS) Solicitation Number: HTC711-13-R-D012? The closing date for the solicitation is 2pm on 29 Jul 2013.
Regarding Exercise Operations Support (1.4.3,4 and 1.4.3.9), can the government provide a list of previous year’s exercises, both timeframe and duration in order to estimate staffing requirements estimates for future support?
Please refer to sections 1.4.3.4 and 1.4.3.9 of the PWS. These sections identify the anticipated support requirements to include the estimated # of exercises, estimated duty hours and frequency. In addition, section 1.4.3.9 of the PWS has been updated to include additional verbiage on the projected work to be performed. This task is a Labor Hour task therefore all work will be on an as needed basis and billed only as used/required.
Were the hours for PWS, 1.4.7, Task 7 (Optional Task) included in the Estimated Workload
Data (pg 84 of RFP)?
No, the hours for 1.4.7 (SMS Migration to a virtual environment supporting
Infrastructure, Platform, and/or Software as a Service.- OPTIONAL TASK) are not captured on pg 84. This task is in the PWS because it will likely occur sometime during the course of the 5 yr contract period; however, the level of effort for this task will be negotiated when Government decides to execute this option due to the unpredictability of the environment in which SMS will migrate to.
Reference: Section C - Performance Work Statement. Paragraph 1.4.2.1.1.7 Situational
Awareness and Collaboration states that the projected level of effort for this task is for 11,520 hours. The period of performance for this CLIN 0007 is from 1 October 2013 through 30
September 2015. Please clarify if the 11,520 estimated hours written in the PWS is for the entire task (two years) or if it should be 11,520 per year (23,040 total hours for CLIN 0007).
The 11,520 estimated hours are per year.
Reference: Section L – Instructions, conditions and Notices to Bidders.
Is a cover letter allowable for each volume and is it excluded from the page limits?
Yes, Cover letters are allowed for each volume, however cover letters are inclusive in the total page limits identified within section L - Instructions, Conditions and Notices to Bidders.
6 When does the current SMS ATO expire? Current SMS ATO expires 28 Feb 2015.
7 When does the current CMS/CTL ATO expire?
Current CMS/CTL ATO expires 1 Sep 2014; however, CMS/CTL is currently requesting a new 3 year ATO with a start date of 1 Aug 2013 which will replace the current ATO.
8 Does the DAA fall under TCJ6? Yes
In section1.4.8.1., it states "Prior to all SMS/CMS software releases, the source code shall be scanned with a Static Code Analysis Tool (Fortify 360 scanning tool, IBM Appscan, etc)," and deliverables listed as "1.4.8.2.b SMS DISA Application Security and Development Checklist , 1.4.8.2.d CMS DISA Application Security and Development Checklist ." However, according to the Application and Development STIG/Checklist, Static analysis tools are valuable if the code is very large, but it is not a replacement for manual code review. There should be manual code review for exposed code, such as network-facing code and mobile code. Does any of the
SMS/CMS code require a manual code review to meet STIG compliancy? Is there any legacy code as part of SMS and/or CMS that will require manual review?
There is currently no requirement for a manual code review to meet the
DIACAP requirements for either program.
Section 1.4.8.4, "Many of the controls for CMS are inherited from the sub-Contractor commercial cloud provider; however, the prime Contractor is responsible for ensuring the commercial cloud provider continues to meet these requirements." Will the contractor be required to test the inherited controls provided by the cloud subcontractor or will the test results be handed over from the cloud sub-contractor?
No the contractor will not be required to test the controls inherited from the commercial cloud provider. The documentation required of the commercial cloud provider will be available through FedRAMP.
Section L-4(b) Staffing Approach limits 5 pages to include a staffing matrix which “correlate each labor category by hours to each PWS task and sub-task “.
Please consider increasing the 5 page limit of Volume 2 to 10 pages (or remove limit entirely).
The limit for staffing has been increased to 10 pages. See updates in Section L.
PWS Paragraph 4.4 (rather than Section L or M) requires “generic resumes provided as part of the Contractor’s staffing approach.” Are these generic resumes required as part of our proposal? If so, can they be excluded from Volume 2's page limit?
Generic resumes are not required. Please reference section L and M for specific staffing requirements/guidelines. The PWS section 4.4 has been updated.
The PWS indicates that CMS is hosted in a “commercial cloud environment” however, this environment is never actually identified. Can you provide the name/company currently providing hosting services for CMS?
CMS is currently in the process of transitioning to Amazon Web Services and is expected to be fully transitioned prior to this contract start date.
Questions and Answers
Number Question Answer
4.3 of the PWS cites POPs as follows:
CMS:The base period of performance is 30 September 2013 through 29 September 2014.
The first option period of performance is 30 September 2014 through 29 September 2015.
The second option period of performance is 30 September 2015 through 29 September 2016.
The third option period of performance is 30 September 2016 through 29 September 2017.
The fourth option period of performance is 30 September 2017 through 29 September 2018
SMS:
The base period of performance 1 October 2013 through 30 September 2014.
The first option period of performance is 1 October 2014 through 30 September 2015.
The second option period of performance is 1 October 2015 through 30 September 2016.
The third option period of performance is 1 October 2016 through 30 September 2017.
The fourth option period of performance is 1 October 2017 through 30 September 2018.
However, SMS CLINs 0006, 0010, 1006, 1010, 2006, 2010, 3006, 3010, 4006, and 4010 cite a period of performance of 09/30/2013 – 09/29/2014 in their respective descriptions in Section
B – Supplies or Services and Prices.
Please clarify Period of Performance for SMS and CMS.
SMS CLINS 0006, 0010, 1006, 1010, 2006, 2010, 3006, 3010, 4006, and
4010 are for AFRC support & travel and operate on a different schedule than the other SMS CLINS. The correct POP for these CLINS are listed correctly in the CLIN structure. The PWS section 4.3 has been updated.
The CLIN structure does not have CLIN 0006 (Para 1.4.5) as optional and neither does the
PWS to CLIN mapping. Only in the PWS is that para 1.4.5 marked as optional.
Please clarify if CLIN 0006 is an optional task.
The intent is to fund this task; however, because the Air Force Reserve
Command funds this task directly it is listed as optional because there may be delays in receiving their funds and applying those funds to the contract. ---
OPTIONAL LANGUAGE HAS BEEN ADDED TO THESE CLINS.
Reference: Performance Work Statement. Section 1.4.7 Task Area 7 and Attachment 8 refer to, “SMS Migration to a virtual environment supporting infrastructure, Platform, and/or
Software as a Service. – OPTIONAL TASK.” However, in Section B, CLIN 0008 and
Attachment 4, CLIN 0008 which refers to PWS Para 1.4.7, it states, “OPTIONAL – Cyber
Security FFP…”
a. Please confirm if Section B, CLIN 0008 and Attachment 4, CLIN 0008 should be “SMS
Migration…..”
b. Please also confirm if the SMS Migration hours are already included under Appendix A: 5
Year Forecast.
A. Yes, the title of this CLIN should be SMS Migration to Virtual
Environment - CLIN HAS BEEN UPDATED ACCORDINGLY
B. No, hours for this task are not captured in Appendix A. Reference Q&A from RFP Amendment #1, #3 for further clarification.
Reference: Section C - Performance Work Statement. Section 4.4 Contract Manager states, “The Contractor shall ensure all personnel assigned to this contract meet the minimum requirements specified in the Contractor’s proposal, IAW the generic resumes provided as part of the Contractor’s staffing approach.” However, in Section L-4 (b) Staffing Approach it states, “The matrix shall correlate each labor category by hours to each PWS task and sub-task
(if applicable). Offerors shall submit labor category descriptions describing the requisite education, experience, security, or special skills proposed to perform the intended PWS tasks
(i.e. position descriptions, not resumes). Reference PWS para 4.5 for functional and technical labor category requirements. a. Please confirm that position/labor descriptions are required in
Volume 2 Staffing Approach and not generic resumes.
Position Discriptions are required and PWS section 4.4 has been updated to reflect this change.
Pg 36, Para 1.1 mentions a JCTD. Was CMS originally developed by the incumbent or was there another developer?
Yes, the incumbent is the original developer of both SMS and CMS
Pg 42 1.4.2.1.1.2 and Pg 47, 1.4.2.2.1.2 Is the system already JITC certified or is this a grounds up effort for both SMS and CMS in the respective paragraphs? Is there already JITC support documentation and successful test reports to start from?
The TISP and DODAF 2.0 architecture documents supporting the JITC certification are to be completed by 30 Sep 2013 for both SMS and CMS. The
JITC testing will occur in the FY14 - FY15 timeframe.
Please clarify what is wanted for “Section 1 – Sections A-K and Backup Documentation” under Volume 5 – Price Proposal (page 53 of 155). There is no mention of Sections A-K or
Backup Documentation being required as part of the proposal under “Paragraph (e) Price
Proposal” on Page 57 of 155 nor any mention of it being used as part of the evaluation under
“Factor 5- Price” on page 64 of 155.
Please reference section L-3 (1)
If sections A-K are a requirement, the solicitation does not appear to contain a section A (as page 2, immediately following Standard Form 33 starts with Section B). What does the
Government want returned as part of Section A? What specifically does the Government want included with Sections B – K as the majority of the sections have no information request fields nor any indication of what the Government is expecting in return. The majority appear to be for informational purposes only. Please outline, by section, what is expected in return as part of the proposal.
Section A is the very first page (Stanadard Form 33) and items 12-18 are required to be completed by the offeror. Please reference section L for instructions to offerors to include section L-3, proposal preparation instructions.
22 If “Backup Documentation” is required, what specifically is needed?
Please reference section L-3. Offerors may provide any back-up documentation to support their pricing.
Since there is no introductory volume, and no mention of the page count for Title page, Table of Contents, Acronym List. What volume should these be included in or should they be provided as an Attachment? If used, will they be counted against a page count?
Please reference Section L-3 (2).
For page count, can a 8.5 x 14 landscape page be used for larger tables/graphics or does everything have to be 8.5 x11?
Please reference section L-3 (2)(c)
Questions and Answers
Number Question Answer
25 If they exist, can you provide the DODAF SV6 & AV1?
Draft documents have been added as attachment 10 to the RFP - Final docs will be delivered at the end of the current contract period (29 September 2013). The
SMS SV-6 is from 2009 and is currently being updated; the SV-6 for just the
JOPES interface is attached to demonstrate the level of detail the revised SV-6 will incorporate. The current SMS SV-6 for the other interfaces is not available at this time. - SEE ATTACHMENT 10 FOR DRAFT DOCUMENTS.
What Amazon service(s) and service tier(s) are used? If they do not correlate directly to publicly advertised packages/tiers, what does it most closely match and what differences are there?
CMS is hosted in the Amazon GovCloud; the Amazon services include: Elastic
Compute Cloud (EC2), Elastic Load Balancing, Multi-Factor Authentication, Storage (S3), Simple Notification Service (SNS), CloudWatch, and VPC - all are commercial services that Amazon publishes information about on their website.
27 Is there a solution planned to support SIPR / “high side” capabilities.
SMS currently operates in NIPR and SIPR environments; CMS operates in the commercial internet.com environment with no plans to move into a NIPR or
SIPR environment at this time.
28 Who is Amazon’s contract with, the Government or incumbent?
The current Amazon's contract is with the incumbent and the Government plans to reimburse the follow on contractor for these service through the ODC funding line.
Are the Amazon services being used (or planned for use) for infrastructure, production data storage, production service hosting, or more than one of these?
Yes - all of these
30 What kind of security and encryption is used with Amazon services? The security and encryption requirements meet current DIACAP standards.
The pricing template only requires rates, hours and totals for each of the LH CLINs and does not give space for Offerors to demonstrate fully disclosed rate build-ups, should we be adding this to the template or demonstrate this derivation of the hourly rates on a separate tab?
(Attachment 4 – Price Proposal Break Out)
Please reference section L-3. Offerors may submit additional backup documentation to support their pricing.
Page 75 of the PWS states that “The Contractor shall provide a Contract Manager who shall be responsible for the performance of the work.” Are offerors supposed to identify the
Contract Manager in their proposal or at the time of award? (PWS 4.4)
Contract Manager information is required upon contract award - PWS
SECTION 4.4 HAS BEEN UPDATED TO REFLECT THIS CHANGE.
How are subcontractors supposed to be represented in the pricing template, specifically on the
LH CLINS? (Attachment 4 – Price Proposal Break Out). a. Will subcontractors be required to submit fully disclosed versions of their pricing? (Attachment 4 – Price Proposal Break Out)
Offerors should propose fully burdened rates for LH CLINS which would include prime and subcontractor rates. As referenced in L-3, Back-up documentation may be submitted with pricing proposals.
In Appendix A, the Estimated Workload Data is provided for SMS and CMS Sustainment and
Functional Support. Can the government provide greater fidelity in the estimated workload between the Firm Fixed Price and Labor Hour CLINS for SMS Sustainment (CLINS 0001, 0002) and Functional Support (CLINS 0004, 0005) and for CMS Sustainment (CLINS 0011, 0012)? (Appendix A)
The estimated workload data has been provided for the LH CLINS only and is located in appendix A of the PWS. No workload data has been provided for the FFP CLINS. In addition a CLIN to PWS task mapping document has been provided at attachment 8.
Government indicates in its answer that the LOE for optional task PWS 1.4.7/Schedule CLIN
0008 (1008 – 4008 for Options) was not included in the Government provided Estimated
Workload Data on pg. 84 of the RFP, further that the LOE for this optional task will be negotiated when the Government decides to execute this option due to the unpredictability of the environment in which SMS will migrate to.
Should offerors still price the aforementioned CLINs (0008 – 4008) or should those be left unpriced?
At this time price is not required for this CLIN due to the unpredictability of this task. - THE CLINS & ATTACHMENT 4 HAVE BEEN UPDATED TO
REFLECT THIS CHANGE.
Is Section C (PWS) of the RFP required to be submitted with the proposal and is PDF version ok?
Yes, Offerors should include sections A-K in their proposal's and Adobe (PDF) versions are acceptable. Section L-2 of the RFP has been updated to reflect this change.
Could you please confirm whether or not the 20% Small Business requirement includes the travel and ODCs or is it just 20% of labor?
Please reference subfactor 2 under section M: The offeror's proposed subcontracting utilization plan shall provide goals, expressed as dollars and percentages of total contract values.
File details come from the government source that posted it. Updated .