Responses to Questions.xlsx
XLSX spreadsheet 30 KB Posted
- Attached to
- Enterprise Vulnerability Scanning Solution (EVSS) Federal contract opportunity
- Solicitation number
- 19AQMM21R0234
About this file
This document includes a solicitation for an Enterprise Vulnerability Scanning Solution released by the Department of State Office of Acquisition Management. The solicitation seeks proposals for a solution to scan over 250,000 assets across multiple networks, including classified, unclassified, remote office networks with low bandwidth connections, dedicated internet networks, and isolated air-gapped networks. The solution must provide centralized management and reporting capabilities. It must also be scalable to support future growth. Proposals are due by August 10, 2021 at 4 PM EST and shall be delivered electronically. The document includes an attached Performance Work Statement, Pricing Template, and Past Performance Customer Satisfaction Survey with additional requirements information. Questions about the solicitation are due by July 16, 2021 and shall be sent to the Contracting Officer and Contract Specialist via email.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 19AQMM21R0234 P00001.pdf | ||
| Updated and revised PWS.pdf | ||
| updated and revised pricing template.xlsx | XLSX spreadsheet | |
| 19AQMM21R0234.pdf | ||
| Attachment 1 - EVSS_PWS_07062021.pdf | ||
| Attachment 4 - Procurement Timeline.pdf | ||
| Attachment 2 - Pricing Template.xlsx | XLSX spreadsheet | |
| Attachment 5 - Past Performance Customer Satisfaction Survey.docx | DOCX document |
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
Q&A
| 19AQMM21R0234 Q&A | ||||
| Number | Category | Reference | Question | Answer |
| 1 | Technical | 19AQMM21R0234 I.2 Performance Confidence Assessment (Past Performance) Page 5 | Please clarify the definition of a significant subcontractor. The Offeror shall identify a minimum of three (3) and a maximum of five (5) separate references for the prime contractor as well as a maximum of one (1) separate reference for each of the subcontractors/teaming partners expected to perform aspects of the effort that the Offeror considers critical to the overall success of the program. | The inclusion of a reference for a prospective subcontractor depends on the Offeror's determination of their expected impact on the overall success of the program as proposed. Without knowing the Offeror's approach, it is prohibitively difficult for the Government to set minimum definitions of significance for subcontractors. |
| 2 | Technical | 19AQMM21R0234 I.2 Performance Confidence Assessment (Past Performance) Pages 57-58 | Please provide instructions to clarify whether the past performance references should be part of the Technical Volume, how many pages are allowed for each reference and is this included in the 30 page count of the Technical Volume. For each reference, the Offeror shall send a corresponding Past Performance Customer Satisfaction Survey (Attachment 5) to the respective customer reference (i.e. person with direct knowledge of the Offeror's performance), asking them to complete and return the survey via email to CrumRB@state.govand MooreGC2@state.govno later than the proposal due date/time identified on the Standard Form 1449 Solicitation, Offer, and Award, Box 8. The respective customer reference shall delete all unnecessary narrative instructions (information in blue boxes) from Attachment 4 before transmitting to the Contracting Officer. | Past Performance references are limited to a total of ten (10) pages as detailed in the revised solicitation sections I.2 and I.4. |
| 3 | Technical | 19AQMM21R0234 Phase I Proposal format Page 59 | Would the Government consider reducing the minimum font size requirement for supplemental information (headers/ footers, text boxes, tables/graphics) from 12 pt to 10 pt? | Yes, the minimum font size for supplemental information (headers/footers, text boxes, tables/graphics) may be in 10 pt font as detailed in the revised solicitation section I.4. |
| 4 | Technical | 19AQMM21R0234 Phase I Proposal format Page 59 | Would the Government consider allowing a font other than Times New Roman for supplemental information (headers/footers, text boxes, tables/graphics)? | No, please utilize Times New Roman font throughout the Phase I Proposal submission. |
| 5 | Technical | 19AQMM21R0234 H-016 Key Personnel Page 21 | Would the Government provide Labor Category descriptions/requirements for Key Personnel? | The Government is seeking innovative solutions from the Offeror and will not limit the Offeror’s proposal preparation decisions. The Government will evaluate competitive proposals and then assess their relative qualities solely on the factors and sub-factors specified in the solicitation. Please provisions 52.215-1 Alt II in the revised solicitation. |
| 6 | Technical | Attachment 1_EV_PWS PWS 7.5 Page 15 | Will DOS require a complete asset management platform or require the capability to ingest data from existing DOS platform? What tool would that be? | PWS 7.5 represents the requirement for the availability of information related to the vendor's overall solution. The subsequent bullets identify minimum characteristics specific to the vendor's overall solution that must be made available. 7.5.1.1 is specific to an inventory of the individual solution components provided by the vendor. |
| 7 | Technical | Attachment 1_EV_PWS PWS 4.10 Page 1 | Will DOS require diodes for low to high secure data transfers? |
Per PWS 2.1.1 DOS requires the capability to rapidly scan, assess, and report on the security posture of the Department's networks. When referencing secure data transfer between low to high, we distinguish between system classification and categorization. The scope of this contract and the proposed solution do not include transfer of data between various system classifications (e.g. Unclass and Secret). For the purpose of communicaton between seperate system categorizations (e.g., FIPS-199 Low, Moderate, High) vendors have flexibility to design the solution for optimal effectiveness and security.
| 8 | Technical | Attachment 1_EV_PWS PWS 4.10 Page 11 | Will DOS require networks of all types to be centralized with protected views? | PWS 4.1.1 states: "Provide consolidated management capability allowing for centralized analysis, monitoring, reporting, configuration, policy assignment, and device management." The scope of the PWS does not include centralization of networks. The intent described in PWS 4.1.1 is the deployment of an enterprise vulnerability scanning solution consolidated management console. The purpose of the vendor-provided management console is managing solution assets, collecting data, and executing scan activities world-wide through a single platform. |
| 9 | Technical | Attachment 1_EV_PWS PWS 4.10 Page 11 | Physical and virtual infrastructure (hardware servers) procurements to be in the solution pricing or not? Same with OS and other Related licenses. | The offer should include in the price whatever virtual infrastructure (hardware servers) are needed to implement the solution. Some solutions that are cloud based might not require supporting hardware. DOS is leaving contractors flexibility to propose a solution. All solution costs shall be included in the contractors solution pricing submission. |
| 10 | Technical | 19AQMM21R0234 H-016 Key Personnel Pages 21 | Please confirm if key personnel have to be on-site: The Government considers the Dedicated Account Subject Matter Expert (SME) and the On-site Engineering and Vulnerability Scanning Solution Subject Matter Expert (SME) positions to be key personnel under the contract. | Yes, Dedicated Account Subject Matter Expert (SME) is expected to be on-site executing functions outlined in PWS section 7.8 Monthly On-Site Subject Matter Expertise; System Health Checks, Configuration Management and delivery of relevant deliverables. On-Site Engineering and Vulnerability Scanning Solution Subject Matter Expert (SME) is expected to be on-site executing functions outlined in PWS section 6.0 Installation services. |
| 11 | Technical | 19AQMM21R0234 I.3 Small Business Participation Page 58 | Paragraph I.2 asks for a Small Business Participation Commitment Document (SBPCD). Where should The SBPCD be submitted? Are there any page limitations to the SBPCD? | The Small Business Participation Commitment Document (SBPCD) shall be limited to ten (10) total pages in Times New Roman 12 pt font as detailed in revised sections I.3 and I.4 of the solicitation. This does not count towards the thirty (30) maximum page limitation for the Phase I Technical Proposals. |
| 12 | Technical | 19AQMM21R0234 I.1 Technical Approach and Demonstrated Functionality/Capability Page 57 | Paragraph I.1 (2) (e) asks for Resumes. Where should the Resumes be submitted? Are there any page limitations to resumes? | The total page limit for Key personnel resumes is a total of 4 pages that will count towards the the thirty (30) maximum page limitation for the Phase I Technical Proposals as detailed in revised section I.4 of the solicitation. |
| 13 | Cost | 19AQMM21R0234 B-005 Type of Contract Pages 9 | In this section, the Government allows for the usage of T&M for technical support and technical deliveries in the technical approach. The provided Pricing Template only allows for FFP cost data. Can the Contractor revise the Pricing Template to show T&M rates and the required cost buildup? | Yes, please see section B-005 of the revised solicitation for more details. |
| 14 | Cost | 19AQMM21R0234 B-005 Type of Contract Pages 9 | Is it acceptable for the Contractor to submit a T&M rate table for ad hoc technical support and technical deliveries not accounted for in the LOE hours submtted? | Yes, please see section B-005 of the revised solicitation for more details. |
| 15 | Cost | 19AQMM21R0234 52.215-20 (1) Pages 51 | The following statement is included in the RFP "The offeror shall prepare and submit certified cost or pricing data, data other than certified cost or pricing data, and supporting attachments in accordance with the instructions contained in Table 15-2 of FAR 15.408";" The instructions in Table 15-2 are incorporated as a mandatory format to be used in this contract, unless the Contracting Officer and the Contractor agree to a different format and change this clause to use Alternate I." Since this is a competitive bid Is it the Government's intention to not require submittal to be 15-2? | Please see the revised solicitation that replaces 52.215-20 with 52.215-20 Alt I that references the format detailed in Attachment 2 Pricing Template rev 07212021. |
| 16 | Cost | 19AQMM21R0234 I.4 (3) Comprehensive Cost/Price Proposal Page 58 | This section requires the Pricing to be at "the lowest level of granularity showing all proposed direct labor costs, indirect costs, facilities capital cost of money (as applicable) and profit data,…". Standard FFP contract type proposals include pricing data at the Total Sell level as reflected in the provided Pricing Template. Is the Contractor required to supply any additional cost buildup beyond what is required in the Price Template? | Please see the "Wrap Fee Calculation" tab of Attachment II Pricing Template rev 07212021 for the specific ifnormation surrounding the cost buildup. |
| 17 | Cost | Attachment 2 - Pricing Template CLIN *0005 | In the Pricing Template, Travel CLINs are prepopulated with an amount of $5,000. Should the subcontractor use this figures as a 'plug' or is it the Government's expectation that the Contractor will update this amount with estimates? | Utilize the $5,000 from the pricing template as a plug number for travel costs. |
| 18 | Technical | Attachment 1 - EVSS_PWS_07062021 PWS 2.1.1 Page 4 | Page 4 of PWS, 2.1.1 – Please explain your definition and requirement around device management? For example, is it full life-cycle hardware management? Is it the operational status of the hardware? | In this case we are referring to solution management and monitoring of the individual components that compose the overall solution. |
19 Technical Attachment 1 - EVSS_PWS_07062021 PWS 2.3.2 Page 4 Page 4 of PWS, 2.3.2 – Does this requirement mean that contractor may not use any elements of managed services in their solution? For example, hosted cloud platform, remote analyst? Iaas and SaaS solutions are acceptable as long as they are FedRAMP certified. The solution will be turned over to the Government for solution management so remote analysts are not acceptable. Service activity appropriate to this contract is outlined in the PWS requirements including: system integration, installation, support, training and project management.
| 20 | Technical | Attachment 1 - EVSS_PWS_07062021 PWS 4.1.1 Page 6 | Page 6 of the PWS – 4.1.1 – Does management capability require consolidation of classified and unclassified networks? | No, the PWS does not include centralization or consolidation of networks. The intent described in PWS 4.1.1 is the deployment of an enterprise vulnerability scanning solution consolidated management console. For the purpose of networks of different classification levels (Unclass and Secret), this would include seperate management solutions. |
| 21 | Technical | Attachment 1 - EVSS_PWS_07062021 PWS 4.9.2 Page 11 | Page 11 of the PWS – 4.9.2 – Please provide additional information on the Department’s CI/CD pipeline to support response on ability to integrate contractor’s solution | Offerors need to demonstrate the capability to support detection and remediation of vulnerabilities and malware during development when the pipeline to deployment is largely automated. The Department operates CI/CD pipelines within Azure (Government and Commercial), AWS (Government and Commercial) and has future plans for Google Cloud Platform (GCP). Each environment uses native CI/CD pipeline capabilities (e.g., AWS DevOps and AWS CloudDeploy) while specific Department system owners may leverage other pipeline capabilities. |
| 22 | Technical | Attachment 1 - EVSS_PWS_07062021 PWS 4.9.3 Page 11 | Page 11 of the PWS – 4.9.3 – Does the government want to see solution can scan multiple disparate cloud environments simultaneously? And or – can solution support disparate cloud platforms? | The strategic design is up to the vendor. The solution shall support simultaneous scanning of multiple disparate cloud enviroments. |
| 23 | Technical | Attachment 1 - EVSS_PWS_07062021 PWS 4.10 Page 11 | Page 11 of the PWS – 4.10 – How many networks do you currently have that are not connected to the Internet? How many networks do you have that are isolated? | Solution shall include a strategy and scalable capacity to meeting requirements outlined in 2.2.1, SBU network, classified network, and SBU Azure Cloud, and SBU AWS cloud enviroment. Section 4. functionality and capabilities within the PWS provides additional details into the size, technology, and scale of the required endpoints and networks. |
2.3 includes overall solution scalability to later onboard additional enclaves, DMZs, air-gapped networks, and additional cloud service providers through an exansion of the provisioned solution with aquisition.
There are currently 158 distinct DOS DMZ subnets hosted at two different geographical locations. Each subnet is not full populated with hosts.
There are quantity 52 /24 subnets, quantity 14 /25 subnets, quantity 42 /26 subnets, quantity 14 /27 subnets, quantity 26 /28, and quantity 10 /29 subnets.
There are 273 posts.
| Line Speed | Post Count (number of posts with this line speed) |
| .2 to 5 megabyte: | 88 |
| 6 to 25 megabyte: | 132 |
| 26 to 50 megabytes: | 166 |
| 53 to 100 megabyte | 109 |
110 to 1000 megabytes: 50 Subtotal: 545
At present, there are approximately 776 DOS Dedicated Internet Networks (DINs) hosted at posts and annexes around the world leveraging dedicated internet connections not connected to the enterprise network. Many posts, approximately 75%, only have 1 DIN, but 16% have between 5 and 10 DINs, and approximately 4% have more than 10 DINs. Over the past six years the number of DINs have increased at a rate of 44% per year. Each DIN would have multiple endpoints, but typically a range of 1 to 100 endpoints. Vendors need to describe how the solution will scale and accomodate these types of networks.
24 Technical Attachment 1 - EVSS_PWS_07062021 PWS 4.10.1 Page 11 Page 11 of the PWS – 4.10.1 – Please provide additional details on the characteristics/definition/configurations of the remote office networks mentioned in this requirement. For example, connection protocols, device types. Please see question 23 comments above. In particular the table below describes the line speed at posts.
There are 273 posts.
| Line Speed | Post Count (number of posts with this speed) |
| .2 to 5 megabyte: | 88 |
| 6 to 25 megabyte: | 132 |
| 26 to 50 megabytes: | 166 |
| 53 to 100 megabyte: | 109 |
110 to 1000 megabytes: 50 Subtotal: 545
25 Technical Attachment 1 - EVSS_PWS_07062021 PWS 4.10.2 Page 11 Page 11 of the PWS – 4.10.2 – Please provide additional details on the characteristics/definition/configurations and conditions of the isolated internet connected networks Offerors need to demonstrate the solution's scalability, capability and strategy. DOS considers these DINS as described in the answer to Question 23. PWS 4.10.2 merely requires offerors to "demonstrate solution scalability and capability." Both the number and configuration of the dedicated internet networks (DINs) and internet-connected networks at posts throughout the world varies greatly. Sometimes a DIN consists of one server and WiFi router that enables foreign nationals visiting a post to obtain a visa to access the internet to obtain one more piece of information needed for a form. Other times the DINS and internet-connected networks can be quite complex.
26 Technical Attachment 1 - EVSS_PWS_07062021 PWS 4.10.3 Page 11 Page 11 of the PWS – 4.10.3 – Please provide additional details on the characteristics/definition/configurations and conditions of the (non-internet connected) air-gapped networks The non-internet connected, air-gapped networks referenced in PWS 4.10.3 are typically air-gapped for security reasons. These would include the types of data processing systems, infrastructure, and databases described in PWS 4.3 Scanning Domain. Offerors need to demonstrate the capability by describing how they scan air-gapped networks. Offerors need to demonstrate the solution's scalability, capability and strategy.
See question 23 comments.
27 Technical Attachment 1 - EVSS_PWS_07062021 PWS 5.1.1 Page 13 Page 13 of the PWS – 5.1.1 – Please provide information on iPost’s interface/API capabilities. Please provide information on the capabilities of iPost The solution shall make available the fields identified in section 5.1 via a database, SQL preferred, for database query and pull from iPost.
| 28 | Technical | Attachment 1 - EVSS_PWS_07062021 PWS 5.2.1 Page 13 | Page 13 of the PWS – 5.2.1 – Are all the networks covered in this procurement – to include air gapped networks included in this requirement? Are installations of CyberArk included on remote or non-internet connected networks to support this requirement? | PWS section 2.2 includes details into the network covered in the the initial procurement. Sections 2.3 covers networks that the solution shall include scalability to cover through additional acquisition (hardware, software, licenses, labor, etc...). CyberArk is the primary privilidged account management solution leveraged on the networks identified in PWS section 2.2. |
| 29 | Technical | Attachment 1 - EVSS_PWS_07062021 PWS 7.5.1.1 Page 15 | Page 15 of PWS, 7.5.1.1 – Does the Inventory of all assets and versioning details pertain to Department of State (DoS) assets or something else? For example DoS assets per scope of this RFP (2.2.1) consist of endpoints, applications and infrastructure. Or the details of the contractor solution? | Section 7 is related to services and support for the solution. Section 7.5.1.1 represents inventory of assets and software relevant to the vendor solution. |
| 30 | Technical | Attachment 1 - EVSS_PWS_07062021 PWS 7.5.1.4 Page 15 | Page 15 of PWS, 7.5.1.4 – Is the scope of this requirement for the break/fix requests of the contractor’s solution only? Does the government want the contractor to propose a ticketing system for the Vulnerability Scanning solution only or leverage a ticketing solution that may already exist within the environment? | PWS 7.5.1.4 on page 15 of the PWS refers to the contractor's ticketing and incident tracking system specific to the enterprise vulnerability scanning solution (ex: vendor help desk ticketing system, incident journal). |
| 31 | Technical | Attachment 1 - EVSS_PWS_07062021 PWS 7.7.1 Page 16 | Page 16 of the PWS, 7.7.1 – As device management was mentioned in the scope section of the PWS, are these requirements limited to the contractor’s solution hardware only? Or does this pertain to upgrades of the contractor’s solution? | PWS 7.7.1 pertains to upgrades to the contractor's solution including both software and hardware. DOS would expect to receive notices regarding updated capabilities available for the solution as well as support, release of new solution software updates, security content, patches, and bug fixes. This requirement for notifications is specific to the offerings within the vendor's solution. |
| 32 | Technical | Attachment 1 - EVSS_PWS_07062021 PWS 7.9.1 Page 16 | Page 16 of the PWS, 7.9.1 – As device management was mentioned in the scope section of the PWS, are these requirements limited to the contractor’s solution hardware only? | Since the planned contract duration spans 10 years, and solutions sometimes meet end of life at 5 to 6 years, the intent of Section 7.9 Solution Lifecycle Technology Management Plan includes a requirement for the contractor to furnish a solution lifecycle management plan intended to maintain the currency and effectiveness of the contractor's overall solution over a 10 year period of performance. |
| 33 | Technical | Attachment 1 - EVSS_PWS_07062021 PWS 7.9.2 Page 16 | Page 16 of the PWS, 7.9.2 – As device management was mentioned in the scope section of the PWS, do these requirements pertain to the contractor’s solution only? Or to all assets within the scope of this procurement? | Section 7.9 of the PWS applies to the solution itself, not the assets being scanned. |
| 34 | Technical | 19AQMM21R0234 I.1 Technical Approach and Demonstrated Functionality/Capability Page 57 | Paragraph I.1 (3) asks for the submission of multiple Accessibility Conformance Reports. Where should the ACRs be submitted since they will be many pages long? | Accessibility Conformance Reports shoud be provided as a separate attachment and are not included in the total page count of the Phase I Technical Volume per section I.4 Phase I page limitations. |
| 35 | Technical/Past Performance | Section L -I.2 | What are the past performance requirements for offerors in Contractor Teaming Arrangements where there is no prime/sub relationship? Each member is of equal standing. | The only way for each member to be equal would be to form a legal joint venture rather than a subcontracting arrangement. In that case, past performance as primes in a situation where the work was performed as part of a joint venture would be used. |
| Performance Confidence Assessment. | ||||
| Pg 57 | ||||
| 36 | Technical | Section L – I.2. Performance Confidence Assessment. | Will the government consider changing the requirement to zero prime past performances? “For at least 2 of the references, the Offeror must have been the prime.” | Please see section L - I.2 of the revised solicition that requires the offeror to provide at least two (2) references where they served as the prime. |
| Pg 57 | ||||
| 37 | Technical | PWS Section 12. Page 20 | The PWS stipulates that the offeror must be an authorized product reseller. If a subcontractor teaming partner is a reseller, will this be acceptable to the government? If a CTA partner is a reseller, will this be acceptable to the government? | No. The prime offeror must be an authorized reseller. |
| 38 | Technical | PWS Section 46 Federal Regulatory Requirements | The “solution compatibility with the Dell EMC CloudLink Key Management Server.” We have experience with “KeySecure.” Is this an acceptable technology? | The amended PWS allows for alternative approaches to encryption as stated in section 4.6.2 aside from the use of Dell EMC CloudLInk. However, all approaches must comply with Key Management Interoperability Protocol (KMIP) standard and support central storage of keys in the Department's centralized key management solution. Encryption keys must be maintained, generated, and controlled in a Department data center under the control of the US Government (5 FAH-8 H-354.2 (4))). |
See Amended PWS section 4.6 for clarification on federal regulatory controls requirements.
39 Technical PWS Section 2 – Scope. 2.3.1 – Scalable Capacity The solution that is to be provided, will it be duplicated for the disparate network, disconnected networks, not connected to the enterprise network? Or is it the idea that a single solution will take care of those disparate networks as well? PWS 2.3.1 emphasizes that the solution needs to be able to scale up as the DOS need for vulnerability scanning grows. DOS leaves flexibility to the offeror to design the solution. The solution will take care of those disparate networks as well.
PWS 4.10 provides further detail on restricted environments that need to be covered, including: 4.10.1 low bandwidth internet connection, 4.10.2 dedicated internet networks (DINs), and 4.10.3 isolated air-gapped networks.
| Pg. 4 | ||||
| 40 | Technical | PWS Section 12. Pg 20 | Given the requirement for the offeror to be an authorized product reseller, can the government elaborate on what products will be required? | It is the vendor's responsibility to provide the products and solution that meet the requirements of the PWS. |
| 41 | Cost | PWS Section 4.4 Scheduling, | Does the Dept of State want pricing for 250k assets exactly (since 250K+ is listed), or would they like a buffer? | PWS 4.4.1 referred to 250k+ because the number continues to grow. The capacity to scale with the Department is mentioned in the scope (PWS 2.3, and in Scheduling PWS 4.4). |
| Page 8 | ||||
| 42 | Technical | PWS General Question | Does the Dept of State want responses to the tech requirements questions provided as “meets requirement” only, or a descriptive description as well? | Vendor should provide evidence or description of how they would meet each requirement whenever possible. Including a screen shot of evidence or describing a procedure to illustrate how the requirement would be met boosts confidence and reduces risk. |
| 43 | Technical | PWS Section 4.63, page 8 | Please clarify what you would like to see to meet this requirement "FIPS 140-2 module validation certificate numbers" | Vendor must provide evidence of FIPS 140-2 NIST certification: https://csrc.nist.gov/Projects/cryptographic-module-validation-program/validated-modules |
| 44 | Technical | PWS Section 4.7 FedRamp Certification, page 10 | Would you be willing to consider technologies that are FedRAMP “in process”. | For solutions including cloud-hosted service offerings, vendors need FedRAMP certification. PWS 4.7 specified FedRAMP certification because we have seen long delays occur in the FedRAMP process and need the contractor to be able to start expeditiously. Also, the elements could be on prem and not require a cloud based solution. DOS leaves the vendor flexibility to design the solution. |
| 45 | Technical | PWS Section 4.61 Federal Regulatory Requirements, page 8 | Please clarify what you would like to see to meet this requirement "FIPS 140-2 module validation certificate numbers as they apply to solution user interface, data in motion, and data at rest." | Vendor must provide evidence of FIPS 140-2 NIST certification. https://csrc.nist.gov/Projects/cryptographic-module-validation-program/validated-modules |
| 46 | Technical | Solicitation Section I.2 Performance Confidence Assessment (Past Performance), Page 57 | Does the Department of State want want references / past performance contacts you can speak with directly, or just named? | Please see Section I.2 of the solicitation and Attachment 5 - Past Performance Customer Satisfaction Survey for more details surrounding the types of information that is required. |
| 47 | Technical | PWS Section 7.1.1., page 15 | Is US citizen support during business hours adequate? as this is how we currently support many other US Federal customers? | No. Per PWS 7.1.1, support must be accessible from U.S. citizens at all times (24/7/365). |
| 48 | Technical | PWS Section 6.1.2 On-site Expertise, page 14 | Is clearance required of the on-site SME and if so what level? | Yes, Secret. Per PWS 10. Security Requirements, personnel working on site require a Secret clearance. And in RFP H-031 Security requirements. |
| 49 | Technical | PWS General | Is there a maximum page count? | Please see section I.4 of the revised solicitation for more details surrounding the page limitations. |
&1#&"Times New Roman"&10&K000000SBU - CONTRACTING AND ACQUISITIONS
File details come from the government source that posted it. Updated .