Attachment_0016_Amendment_0013_Questions_and_Answers.xlsx
XLSX spreadsheet 15 KB Posted
- Solicitation number
- W52P1J-16-R-0172
About this file
Questions and Answers
View the file
Other files
Show 40 more
Latest 50 of 57 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
Sheet1
| ADDITIONAL QUESTIONS/COMMENTS AND ANSWERS - REQUEST FOR PROPOSAL (RFP) UC SOFT CLIENT (W52P1J-16-R-0172) | |||||||
| RFP Section | VOLUME | ATTACHMENT | PAGE | PARAGRAPH | QUESTION/COMMENT | RESPONSE | |
| 1 | ALL | SF1449 | N/A | NAICS | Would the Government entertain modification of the NAICS code from 518210 to 541519 utilizing the 150 employee maximum as the limitation to encourage and enable a higher rate of small business participation? | The NAICS code is approved and assigned in the acquisition strategy. The NAICS code does not prevent any business from proposing, just dictates what size standard It has to annotate on its proposal. | |
| 2 | Pricing Proposal | VI | 0005 | CLIN 0010 | TASK ONE - PSTN and DSN Sustainment Price - OPTIONAL TASK | Can the Government please clarify what is meant by "sustainment cost" on an annual basis in an as-a-service offer? Can the Government please define what the sustainment cost is meant to include? | The price matrix includes descriptions of what should be included under each tab. Sustainment costs is the cost to maintain the PSTN and DSN Integration after it has been integrated into the Government environment. |
| 3 | Pricing Proposal | VI | 0005 | N/A | N/A | Will Government accept billing on an annual basis or require monthly billing based on the End User subscribers? | As provided previously, payments will be discussed after contract award. Billing will be based upon allowable practices for commercial contacts and agreements between the USG and the awardee, based on what is best for both parties. |
| 4 | Pricing Proposal | VI | 0005 | N/A | N/A | Is funding for the Option Years going to be allocated to the Government on an annual basis? | Options will be handled in accordance with the option clauses contained in the solicitation and done on an annual basis. |
| 5 | Pricing Proposal | VI | 0005 | SUMMARY | Proposed Total Amount | The formulas in the cell do not align with the description. For instance, Row 19, CLIN0005, Cell C19 states Base + Option Years; however, cell G19 does not show the Base Year included in the formula. Please clarify. | Task One for CLIN 0005 is included within cell reference G18's formula. Task Two for CLIN 0005 includes OY 1 thru Four and is included in the cell reference G19's formula. The description for CLIN 0005 Task Two has been updated to state only Option Years One thru Four Total. |
| 6 | Amendment 12, Q&A (Amendment 0007), Specifically Questions 5 | Question 5 | Please clarify your answer. For any cloud based solution (on premise or off premise) it must meet IL 5 for NIPRNET and IL 6 for SIPRNET. For any non-cloud-based solution (on premises or off premise) solution, RMF requirements must be met. What is an on premise cloud? What is a non cloud off premise solution? Please confirm there are only 3 deployment models. Cloud which is commercial data center, on premise, and hybrid. | As the Government is not dictating the solution(cloud/non-cloud/hybrid) that an offeror proposes or how they would deploy their solution (on premise/off premise/hybrid)the offeror shall propose its solution based on how it believes it can best meet the Governments requirements and objectives by deploying its solutions via cloud/non-cloud/on premise/off premise/ hybrid solutions. Amendment 0011 answered this question in relation to security requirements that must be met when deploying a cloud based solution regardless if on-premise or off-premise, a non-cloud solution if on-premise or off-premise and a combination or hybrid of these solutions. | |||
| 7 | Amendment 12, Q&A (Amendment 0007), Specifically Questions 10 | Attachment 0009 | g. For any portion of a solution which is on premise[s], the Offeror’s system design documents and proposed architecture must clearly document how it’s proposed on premise[s] hardware and software has gone through JTIC certification processes and is approved to for use on a DoD network; in compliance with the DoD UC Approved Products List. | We do not believe your answer is correct and suggest you verify with DISA/JITC. Products (both hardware and software) that deliver IM, Chat, Presence, etc. must be on UC APL. Supporting or enabling products do not need to be on UC APL. In the past, any product that touches the network must be JITC certified. | Answer in Amendment 0011 is correct. Please refer to Section 2.2 of the SOO on what must be on the UC APL. | ||
| 8 | SOO, Attachment 0001, Section 3.1.2 and Price Proposal | I and V | Please confirm that any Government delay as articulated in the RFP (i.e. C+550) will not impact the contractor’s ability to bill for the initial deployment of 150,000 NIPR and 16,000 SIPR users if we are ready to deploy in the imposed timeframe (i.e. C+551). There is a significant investment required to build this capability and any Government delay (network readiness) would negatively impact our profitability. | Until this situation arises, as delays could be USG or Contractor caused, this cannot be determined. Issues driving a delay would be situation specific and the resolution of, based on the cause of the delay, will determine how the delay is resolved. | |||
| 9 | Amendment 12 Q&A (Amendment 0007), Specifically Question 5 | Please confirm that any on premise deployment only requires RMF. If you do not agree, please explain the rationale behind additional compliance and/or certification that is considered necessary. | As provided in amendment 0011, if an offeror is to propose an on-premise solution which is cloud based it would have to meet the IL 5 and IL 6 security requirements. Non-cloud would have to meet RMF if deployed on premise. | ||||
| 10 | Past Performance | SOO Section 3.1.3 Gate 3 0002, Section 3.3.1 | Contract References shall represent demonstrated performance on recent and relevant contracts as a prime or first tier subcontractor under Department of Defense (Army, Navy, DLA, etc.), USG (Federal, State, Local) and/or commercial contracts. References shall match the solution being proposed. Example: if proposing a cloud based service, | The Past Performance being requested seems very narrowly scoped especially in an emerging marketplace and one the Government is just beginning to adopt. To our knowledge, only one manufacturer can provide customer data as it is requested in the RFP. It is highly likely that a vendor could have demonstrated in one UC area but not all inclusive, especially with the voice capability in conjunction with the UC Client. | Please read attachment 0003 Past Performance section on how an offeror will be evaluated when they have limited past performance information. | ||
| 11 | SOO, Section 3.3 and Amendment 12 Q&A (Amendment 0007) | Attachment 0001 | Regarding E911, we have some concerns with respect to the Army's responses to previous questions submitted by the industry participants. It is our understanding that the UCaaS requirement is the US Army's voice implementation for non-assured connectivity for the non-C2 users. The Army has made reference that E911 capability will be handled in another system. Please clarify why the US Army does not need to comply with Kari's Law Act and/or the Response Act of 2016. | Assured services is out of scope of this particular effort. The Army will address the assured services requirements via other efforts. | |||
| 12 | Attachment 0002, Section 3.1.2 | The Government appears to be very limiting with respect to Past Performance criteria. Clearly there are many companies that have significant past performance but do not meet the overly restrictive criteria that has been detailed in the RFP. The manner in which is was written, specifically for Pass/Fail purposes by the Government, does not allow any subjectivity for different examples and potentially at lower quantities of Past Performance but that are exemplary of the company's capabilities. This overly restrictive PP criteria is severely limiting competition. Is the Government willing to modify the Past Performance requirements? | This question references past performance which is not a pass /fail evaluation. Please confirm if this is related to experience. | ||||
| 13 | 2.1.1 | SOO, Attachment 0001 | Access to Gov't Network/Remote Management | Are there any specific requirements the Gov't has related to remote access to the network for security purposes (i.e. 2-factor authentication)? | The solicitation requires 2-factor authentication as part of the multi layer security approach. The requirements for remote access and to the network for security purposes are called out in the SOO. Appendix D of the SOO provides additional security requirements. | ||
| 14 | 2.4 | SOO, Attachment 0001, Amendment 15 and Attachment 0005, Pricing | 13 | Fielding Objectives | Please clarify whether the 15K SIPR users are part of the IOC and are considered part of the FOC. Attachment 0005, Pricing Summary page, has a line item for SIPR Base Year and the table in Section 2.4 of the SOO suggests that the initial wave of SIPR users are part of the Base installation subset yet the table shows "FOC." | The 15,000 SIPR users funded at time award represent IOC. Instructions for the price model shall be followed in accordance with the RFP. | |
| 15 | 2.4 | SOO, Attachment 0001 | 13 | Fielding Objectives | Should Contractor assume that the Gov't will produce Task Orders as End Users are to be added to the system? Should we assume that there are going to be multiple TO's in any given year? | This is not an IDIQ solicitation. Task orders will not be issued, a single contract award will be issued. | |
| 16 | 2.10, CDRL A0007 | SOO, Attachment 0001 | 15, 27 | Change Management | The RFP states that the Change Management Plan must comply with Section 5.3.2 of the DoD Cloud Computing SRG. This "Change" control language is specific to Configuration Management of a solution. Please confirm that the Government is seeking Contractors' response to Configuration Management and system updates and not specific on how to manage changes requested that vary from a contract execution. | The Change Management Plan is specific to the Configuration Management of the system. However, responsiveness and clear communication of contract execution change management is also required in many forms as stated in the SOO to include project schedules, tasks, meetings, documentation, reports, SLA, training and other requirements. Change management of the system and change management of contract execution are intrinsically linked, requiring efforts to manage change of both, even when an official documented Change Management Plan is only required for the system, this document will cover most contract execution elements when properly detailed for the system. |
File details come from the government source that posted it. Updated .