Attachment 3 - Eval Factors Traceability Matrix.docx
DOCX document 34 KB Posted
- Attached to
- Cloud E-Mail and Collaboration Services Federal contract opportunity
- Solicitation number
- D12PS00041
About this file
Attachment 3 - Eval Factors Traceability Matrix
View the file
Other files for this federal contract opportunity
Show all 20
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
Traceability Matrix for all Factors & SubFactors
Notice: The Offeror shall place section titles and page numbers where specific responses can be located for each Factor and SubFactor. The Government’s technical evaluators will review each Proposal in its entirety, however, it is not the responsibility of the Government to seek out and identify buried evidence within the Proposal. If responses are not noted on this list, it may be assumed that the Offeror’s proposal provides no response applicable to the Factor or SubFactor. There is no page limit associated with this document.
Instructions: The Traceability Matrix for all Factors & SubFactors has been provided as an editable document to enable Offerors to insert additional rows where multiple sections provide evidence for a Factor/SubFactor. The Factor/SubFactor have been listed in the left hand column titled “Factors and SubFactors.” Provide the proposal section that discusses the Factor and SubFactors in the center column titled “Offeror’s Proposal Section.” Use a new row for each section listed. Where new rows are added, place “See Above” in the “Factors and SubFactors” column to indicate a continuation of references for the above-mentioned Factor/SubFactor. In the right-hand column titled “Page(s),” list the section pages where pertinent supporting information is located for each section cited.
The following technical factors will be used to evaluate offers:
A. Service Delivery, Management, and Technical Approach B. Usability and Functionality C. Information Security and Regulatory Compliance Approach D. Organizational Experience E. Past Performance
Complete the table on the following pages to ensure all Factors and SubFactors are addressed.
Traceability Matrix for all Factors & SubFactors RFP D12PS00041 - Attachment 3
A. Service Delivery, Management, and Technical Approach
| Factors and SubFactors: |
| Offeror’s Proposal Section |
| Page(s) |
A. Service Delivery, Management, and Technical Approach
1. Service Delivery: The government will evaluate Offeror’s demonstrated data portability capability that supports export to another email and collaboration platform upon contract completion/termination. The government will evaluate Offerors’ proven service delivery model, including the specific methods and techniques for implementing a suite of solutions as indicated in the SOO, including such items as quality assurance and service delivery as detailed in the Quality Assurance Plan and high-level Implementation Project Management Plan. The government will also evaluate the Offeror’s proposed standard service offerings to determine the extent to which integrating or delivering these services in Interior’s operating environment requires additional software deployment and/or development work by DOI staff in order to meet SOO objectives.
A. Service Delivery, Management, and Technical Approach
2. Management: Offerors will be evaluated based on described SLAs for individual services and associated penalties assessed for failure to meet SLAs. The government will evaluate the manner and extent to which the Offeror demonstrates corporate stability and those capabilities required to accomplish a smooth transition, provide a superior solution, maintain sufficient resources to fulfill the government’s requirements, shows the corporate dedication to superior technical service and best practices, and increases the potential for meeting program objectives. Interior will also evaluate Offeror’s service reporting capabilities as described in the SOO.
A. Service Delivery, Management, and Technical Approach
3. Technical: The Offeror will be evaluated on its technical capabilities as well as the capabilities of the offered services. The government will evaluate the manner and extent to which the Offeror’s transition strategy and training plan provide confidence that a smooth transition has been sufficiently designed, has adequately identified and mitigated risks, is feasible, practical, complete, and executable, and fulfills the program objectives and satisfies the program requirements. The government will evaluate the exit strategy provisions to insure they are adequate and practical and to determine the way in which they provide access to archive and litigation hold data. The government will evaluate the adequacy of the proposed periodic testing of the exit plan. The government will evaluate the adequacy of the proposed email journaling solution that allows Interior to journal mail to an external electronic records management provider as identified in the SOO. The Government will also evaluate to the extent to which proposals indicate anticipated or potential problem areas and proposes creative, feasible solutions that address problems resulting from the future integration of new processes and technology enhancements.
B. Usability and Functionality
| Factors and SubFactors: |
| Offeror’s Proposal Section |
| Page(s) |
B. Usability and Functionality
1. System features, functionality and capabilities that meet industry performance and interoperability standards and utilize best practices as indicated in the SOO.
B. Usability and Functionality
2. Service offerings’ interoperability with the Government’s installed base of standard software and hardware, including mobile devices.
B. Usability and Functionality
3. Demonstrates service offering’s capabilities to meet objectives and improve user experience and productivity.
C. Information Security and Regulatory Compliance Approach
| Factors and SubFactors: |
| Offeror’s Proposal Section |
| Page(s) |
C. Information Security and Regulatory Compliance Approach
1. The degree to which the proposal defines a secure computing environment that complies with all required federal regulations and DOI specific security requirements as indicated in the SOO, its attachments, and referenced Information Security and regulatory compliance documents.
C. Information Security and Regulatory Compliance Approach
2. The extent to which the proposal demonstrates a design specification and Concept of Operations that fully addresses the Government’s Information Security, Privacy, and Regulatory requirements as outlined in the SOO and its attachments, and referenced Information Security and regulatory compliance documents including. These include, but are not limited to: an interconnection architecture that supports Trusted Internet Connection (TIC) 2.0 and Data Loss Prevention (DLP) requirements with the least burden to the Government; services that support federal IPv6 mandates for externally facing services; a FISMA “Moderate” security categorization security control requirements, in addition to the security control enhancements as specified by FedRAMP and in the DOI Security Control Standards; and services that support HSPD-12 PIV card two factor authentication.
C. Information Security and Regulatory Compliance Approach
3. The Offeror’s experience achieving successful Assessment and Authorization (A&A) on projects of similar size and scope determined acceptable by other organizations with similar requirements.
C. Information Security and Regulatory Compliance Approach
4. The Offeror’s Service Level Agreements related to Information Security and other regulatory compliance requirements.
C. Information Security and Regulatory Compliance Approach
5. Documentation of risk mitigation strategies as appropriate.
D. Organizational Experience
| Factors and SubFactors: |
| Offeror’s Proposal Section |
| Page(s) |
D. Organizational Experience
1. Demonstrates an ability to implement cloud-based projects of similar size and scope.
D. Organizational Experience
2. The Government will evaluate the offeror's demonstration of lessons learned.
E. Past Performance
| Factors and SubFactors: |
| Offeror’s Proposal Section |
| Page(s) |
E. Past Performance
1. The organization’s history of successful completion of projects; history of producing high quality reports and other deliverables; history of staying on schedule and within budget.
E. Past Performance
2. The quality of cooperation (with each other) of key individuals within your organization, and quality of cooperation, and performance, between your organization and its clients.
E. Past Performance
3. Quality of Service and Improvement - The Government will evaluate the offeror's Quality of Service and Improvement as represented by the past performance data. The Government will also evaluate offeror’s approach to implementing performance measures and for improving system effectiveness over time.
E. Past Performance
4. Responsiveness to Customers - The Government will evaluate the offeror's Responsiveness to Customers as represented by past performance data. The Responsiveness to Customers is the offeror’s success in the ability to respond to requests, both scheduled and ad-hoc, for services, data, analysis, and additional tasks in a timely and appropriate manner.
File details come from the government source that posted it. Updated .