DD1423-2__CDRL_A005_Appendix_Metrics.docx
DoD Form DOCX document 30 KB Posted
- Solicitation number
- FA4600-14-R-0017
About this file
This document outlines metrics for a contract to provide information technology capabilities support to the United States Strategic Command. The contractor will be expected to report monthly on key performance indicators including a list of patches applied to systems, details of change requests including time intervals from receipt to implementation, and a customer satisfaction survey gathering feedback from users, program managers, and other stakeholders. Suggested reporting formats are provided but can be adapted to existing tools. The metrics are intended to measure the timeliness and quality of the contractor's patch management, change management, and customer service.
CDRL Appendix
View the file
Other versions and copies of DD Form 1423-2
Show all 20
Who attaches DD Form 1423-2
Other files
Show 40 more
Latest 50 of 77 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
Metrics The below table is a set of metrics that shall be delivered as part of the CDRL A005. Where historical data exists or as history is established, data from the prior 365 days should also be reported to aid in the identification of trends. Archive of the metrics and reports should be maintained for the life of the contract and be available upon request for analysis of longer term trends. Suggested report formats are identified, but this is flexible and can/should be adapted to be consistent with existing tools and processes
| Metric |
| Report Format |
| Description |
| Calculation |
| Purpose |
Implementation & Change Management
| Summary patch report |
| List |
| List of patches (security or normal) (new, open, or applied) during the reporting cycle. |
| Categorized list of each new patch, open patch, or patch closed during the reporting cycle to include category and time duration from patch release, to notification through implementation |
| How much work is my IT support organization doing to keep systems that support my capability up to date? |
| Remedy change requests summary |
| List |
| List of requests during reporting cycle (new, currently open, closed). |
| For each request (application release, software purchase, hardware purchase, other) report time intervals from receipt to engineering solution, implementation, ATO/IATO, and production acceptance |
| What have I asked my IT support organization to do and how fast are they doing it? |
Customer Satisfaction
| Customer Survey |
| Survey Report |
| Montly survey of users/program managers/ functional managers/data managers or other stakeholders to garner perception of satisfaction with the above categories and anecdotal feedback to address customer service issue repair. |
| Recommend survey design effort be conducted with stakeholder (users, PM, FM) involvement |
| Are stakeholders satisfied with the service they’re getting from the IT support organization? |
File details come from the government source that posted it. Updated .