Attachment 3 Instructions to Offerors Technical Proposals Key Points .pdf

Technical Proposals – Key Points

SBU - CONTRACTING AND ACQUISITIONS

To improve the likelihood of receiving an acceptable rating on their technical proposal for the SAFE program, an offeror should ensure that their proposal addresses the following key points:

1. Acquisition of Licenses and Maintenance Services: Clearly outline how the offeror will provide licenses and maintenance and support services for the Department’s enterprise ENA system. This includes ensuring that all domestic sites and overseas posts have access to a single vehicle for procuring these services.

2. Management of the ENA Cloud-Based Software System: Clearly outline how the offeror will manage the deployed ENA cloud-based software system effectively.

3. Improvement of Data Collection and Standardization: Describe the methods and tools the offeror will use to improve the ability of posts and sites to collect, standardize, and track emergency contact data from United States Direct Hire (USDH) staff, family members, and other eligible individuals.

4. Tracking Accountability During Emergencies: Explain how the offeror will facilitate the tracking of accountability at the post/site level during a domestic or overseas emergency.

5. Reduction of Cybersecurity Vulnerabilities: Describe, in detail, the measures the offeror will take to reduce cybersecurity vulnerabilities by maintaining a standard solution that adheres to department standards and governance.

6. Integration of Multiple Data Feeds: Describe how the offeror will integrate multiple data feeds that adhere to the Master Reference Database requirements to standardize data collection and accountability.

7. Operational Skills Transfer: Detail the approach for sharing and conveying operational skills to Government personnel and other support contractors. This is crucial for ensuring a functional understanding of the process, providing continuity, and improving workforce efficiency.

8. Compliance with Policies and Requirements: Demonstrate how the acquisition will conform with the official policy and business requirements approved by Department leadership. Reference Attachment 3 and Attachment 4 to the Statement of Work for the full text of the policy and requirements.

9. Partnership and Coordination: Describe the partnership and coordination efforts with sites and posts to maintain and support the ENA software system. Emphasize the importance of managing communication and outreach, which is expected to be 30%-50% of the overall effort.

Technical Proposals – Key Points

SBU - CONTRACTING AND ACQUISITIONS

10. Support and Concept of Operations: Provide details on how Tier 2 and Tier 3 support will be offered to all customers for ticket closure. Outline the development of a concept of operations, tracking and updating a repository for local modality options, and defining user and operator roles, responsibilities, and business processes.

11. Integration with Existing Systems: Ensure that the ENA system will supplement existing PENS and integrate into the Emergency Action Plan at each post/site.

12. Security and Compliance: Address the security categorization of the solution (FISMA moderate) and adherence to privacy protection practices. Mention the requirement for a facility security clearance at the SECRET level and that personnel must be U.S. citizens with a security clearance at the MODERATE RISK PUBLIC TRUST (MRPT) or SECRET level.

13. Adaptability to Emergencies: Acknowledge the potential for unforeseen emergencies or natural/national disasters and the need for the deployment timeline to be adaptable in collaboration with key DOS stakeholders.