Attachment_1_-_Requirements_Matrix.docx

DOCX document 25 KB Posted

Attached to
Information Technology (IT) Research Licenses Federal contract opportunity
Solicitation number
CC16HQQ0023
Issued by
Department of the Treasury Office of the Comptroller of the Currency

About this file

Attachment 1 - Requirements Matrix

View the file

Other files for this federal contract opportunity

Other files attached to Information Technology (IT) Research Licenses, newest first.
File Type Posted
Attachment_1_-_Requirements_Matrix_A0003.docx DOCX document
RFQ_A0003.docx DOCX document
Attachment_6_-_Q A_A0003.docx DOCX document
RFQ_A0002.docx DOCX document
RFQ_A0001.docx DOCX document
Attachment_4_-_Non-Disclosure_Agreement.doc DOC document
Attachment_5_-_Questions_Template.docx DOCX document
Attachment_2_-_Price_Schedule.xlsx XLSX spreadsheet
Attachment_3_-_OCC_IT_Accessibility_Questionnaire.docx DOCX document
RFQ.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

Attachment 1: Requirements Matrix

RFQ CC16HQQ0023

Information Technology (IT) Research Licenses Requirements Matrix

Per Section L of the Request for Quotations (RFQ), vendors must complete the requirements matrix below.

In the matrix below, the key requirements of the IT Research Licenses solicited for are identified. To complete the requirements matrix as a part of its technical quotation, a vendor should explain in the “Description of How Requirement is Met / Vendor Comments” column how its proposal fully meets the associated requirement. This space may also be used to provide any additional comments or clarifications.

Each blank column must be completed in order for a vendor’s response to be evaluated for award. Vendors who fail to complete the entire matrix may be considered deficient or unacceptable and may be excluded from further evaluation.

#
OCC Requirement
Description of How Requirement is Met / Vendor Comments

Executive IT Research/Advisory License Requirements

1
Access to the vendor's on-line IT research, including:
1a
White papers, such as emerging technology trends, best practices, capability maturity models, adoption benchmarks (case studies), and analyses of technology segments
1b
On-line tools (e.g. spreadsheets), such as those for evaluating technology products using customized weighting or estimating capacity
1c
IT product and service comparisons and assessments
1d
Materials and presentations that the vendor has presented at past conferences/symposiums
1e
Recordings of vendor hosted webinars
1f
No restrictions on the number of times on-line research can be accessed via the vendor’s web portal, and no restrictions on access to the vendor’s inventory of online IT research databases
2
Direct access to analysts for inquiries via phone call/conference call, as described:
2a
For a given topic of inquiry identified by the license holder, the vendor shall identify the analyst(s) who covers that topic
2b
There shall be no limit on the number of times the license holder may contact the analyst(s) during the active period of performance of the contract
3
A dedicated company advisor for each executive license holder whose area of expertise covers the area the senior executive is responsible for within the ITS organization, as described:
3a
The representative shall meet both in-person and via phone with the executive license holder to understand the individual’s needs, coordinate appropriate research requests, arrange calls with subject matter experts, provide best practices, coordinate networking opportunities with applicable industry experts and/or government peers, provide data on recent industry trends applicable to each executive’s area of interest, and assist with the formulation of research strategies and action plans
3b
Throughout the period of performance, this representative shall routinely correspond with both the executive and the Contracting Officer’s Representative (COR), both in-person and via phone, to assess the quality of the license support received. Such reviews must take place a minimum of twice per contract year.
3c
Vendor may assign advisors on a 1-to-1 basis (e.g. 7 distinct advisors for the 7 executive license holders); or, vendors may propose a few advisors spread across all executive licenses holders, as long as each advisor has the corresponding area(s) of expertise and can meet all of the noted requirements for each individual license holder

IT Research License Requirements

1
Access to the vendor's on-line IT research, including:
1a
White papers, such as emerging technology trends, best practices, capability maturity models, adoption benchmarks (case studies), and analyses of technology segments
1b
On-line tools (e.g. spreadsheets), such as those for evaluating technology products using customized weighting or estimating capacity
1c
IT product and service comparisons and assessments
1d
Materials and presentations that the vendor has presented at past conferences/symposiums
1e
Recordings of vendor hosted webinars
1f
No restrictions on the number of times on-line research can be accessed via the vendor’s web portal, and no restrictions on access to the vendor’s inventory of online IT research databases
2
Direct access to analysts for inquiries via phone call/conference call, as described
2a
For a given topic of inquiry identified by the license holder, the vendor shall identify the analyst(s) who covers that topic
2b
There shall be no limit on the number of times the license holder may contact the analyst(s) during the active period of performance of the contract
3
Document reviews for IT documents up to 20 pages in length, as described:
3a
Reviews shall include comments/feedback that may assist the license holder in addressing missing or unclear information, along with overall suggestions to improve the document; however, the review does not require document redline mark-up
3b
No restrictions on the amount of document reviews to be performed

File details come from the government source that posted it. Updated .