The file's text, extracted by GovTribe without its formatting.
Attachment 9 – Service Level Agreements
1.0 Service Level Agreements
A service level agreement (SLA) provides a measurable framework for services to be delivered by the Contractor. The intent of the SLAs defined by the SEC is to set a high level of service to be provided by the Contractor, and to drive the right behavior to maintain the high level of performance. All Service Levels will be reported by the Contractor as outlined in this attachment, and are a critical element of the ISS contract.
This document sets forth the performance requirements subject to Quality Control by the Contractor and Quality Surveillance by the government. This document also defines key terms and credits for failure to meet performance standards.
These are the SEC SLA Targets as formulated for this solicitation; however, the final SLA will be validated and agreed upon with the successful Offeror during the Transition Period, and prior to Day 1 of full Operations.
1.1 Quality Control Plan (QCP)
All Service Levels defined within this attachment must be addressed with the Contractors Quality Control Plan (QCP). The Contractor shall develop a draft Quality Control Plan (QCP) and deliver it to the SEC within 120 days of contract award. The QCP will address how quality control activities will be documented, and the data stores for maintaining documentation.
1.2 Service Level Credits
There are four components to monitoring Contractor’s overall performance and issuance of credits based upon such performance – Performance Indicators, Performance Levels, Service Level Failures, and Service Level Credits.
· Performance Indicators (Service Levels or SLAs): a metric to be monitored, measured, and reported by Contractor. Each Service Level is classified as a Critical Performance Indicator (CPI) or a Key Performance Indicator (KPI) as further described below:
· CPI: a metric that possesses a documented and defined Expected and Minimum Service Level. CPIs will be subject to financial credits based on actual performance (i.e., Service Level Credits), and failure to meet a CPI may constitute a Service Level Failure.
· KPI: a metric that possesses a documented and defined Expected and Minimum Service Level. KPIs will not be subject to financial credits based on actual performance (i.e., Service Level Credits).
· Performance Level: the required level of performance for each Performance Indicator as defined by a “Minimum Service Level” and a “Target Service Level.”
· Minimum Service Level: the minimum standard of performance required for each Performance Indicator.
· Target Service Level: the expected standard of performance for each Performance Indicator.
· Service Level Credit: a financial credit payable to SEC by Contractor based on a Service Level Failure with respect to any CPI.
· Service Level Failure: inability to meet the Minimum Service Level for any CPI or KPI during a given month.
If the contractor misses the Minimum Service Level on a CPI in any given month, the SEC may assess a Service Level Credit. An example of a Service Level Credit is shown below:
· Contractor is expected to place 5% of its aggregate monthly fees at risk (referred to below as the “Amount at Risk”), depending on the number of Target Service Levels missed with respect to CPIs during the month.
· Each CPI will be assigned the same weight based upon the number of CPIs
· Failure to meet the Minimum Service Level of any CPI will lead to a proportional reduction of the Amount at Risk monthly fees.
For example, if there are 10 designated CPIs and there is a Service Level Failure with respect to one CPI in a month, the Service Level Credit will be calculated in accordance with the following example:
· Assumptions: Assume that the aggregate fees during the month were $1 million and that the Credit Percentage for the CPI with respect to which the Service Level Failure occurred was 10% (100% / 10 CPIs).
· Result: In that case:
· The Amount at Risk would be $50,000 (i.e., $1 million x 5%)
· One CPI achieved below Minimum Service Levels for the month, or 10% of CPIs
· The Service Level Credit would be $5,000 (i.e., $50,000 x 10%)
1.3 Service Level Reporting
Throughout the relationship, the Contractor shall be required to provide accurate documentation of quality control activities in accordance with the Quality Control Plan. Additionally, it is SEC’s expectation that the Contractor will work to continually improve performance and will improve the Minimum and Expected Service Levels to drive and reflect quality advancements.
1.4 Service Level Promotion
In response to its business needs, SEC may in its sole and reasonable discretion add, modify, or remove Performance Indicators and/or the associated Service Level Credits, and designate any KPI as a CPI no more than once per quarter. SEC will submit any changes to Performance Indicators in writing and Contractor will implement the changes within thirty (30) days of receipt for those Performance Indicators. Contractor will be obligated to measure, monitor, and report the Performance Indicators and meet or exceed the Service Levels throughout the term.
1.5 SLA Review and Acceptance
The SEC will work with the contractor during the initial 60 day period of the contract to review and assess SLAs and performance levels. Based on the operating environment and available tools, both parties will recommend any changes to the tools, measurement methodology, service levels and performance levels. All recommendations will be reviewed by the SEC, and only the SEC will maintain the rights to make adjustments to the tools, measurement methodology, service levels and performance levels. Additionally, both parties will also discuss and agree to CPIs and KPIs that should be continually improved. The amount of improvement in the performance level will be jointly defined and agreed to by both parties.
2.0 Service Levels Metrics
Performance standards and metrics are delineated below. Any Contractor request for an exception or waiver from any performance standard or metric, or to exclude any particular data from the calculation of any performance standard or metric, shall be made in writing by the Contractor to the SEC. Requests shall include relevant supporting documentation and rationale. Exceptions and waivers must be approved in writing by the SEC.
2.1 Speed to Answer – Phone
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Average Speed to Answer call made to Central Service Desk- measures the percentage of timely answered calls from callers who select the option to speak to a Service Desk analyst |
| Average Phone response time |
| ≤ 30 seconds, 100% of the time |
| ≤ 40 seconds |
100% of the time
| Calculation Methodology |
| (Number of events within performance target / total number of events during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.2 Speed to Answer – Messages
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Speed to Answer Messages - measures the percentage of messages electronically submitted to the Service Desk by Service Desk users (e.g., via Email, Self-service via web page, or voicemail) that are timely acknowledged, responded to and ticketed |
| Response time measure from the time created by the user (not when logged in), until attempt to make first non-automated contact (i.e., first personalized email, or leaving a voicemail) |
| ≤ 60 minutes, 98% of the time |
≤ 60 minutes, 95% of the time
| Calculation Methodology |
| (Number of events within performance target / total number of events during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.3 Speed to Answer – Chat Messages
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Speed to Answer Chat Messages - measures the percentage of messages electronically submitted to the Service Desk by Service Desk users via chat that are timely acknowledged, responded to and ticketed |
| Chat response time |
| ≤ 60 seconds, 100% of the time |
| < 120 seconds, 100% of the time |
| Calculation Methodology |
| (Number of events within performance target / total number of events during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Exceptions |
| Within chat hours 7am-7pm |
| Performance Indicator |
| KPI |
2.4 Speed to Answer – Call Abandonment Rate
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Call Abandonment Rate |
| Calls Abandoned by Users |
| <3% |
| < 3.5% |
| Calculation Methodology |
| (Number of events within performance target / total number of events during Measurement Interval)*100 = percent (%) attained. Total number of events per type during the measurement interval will not include any calls that are abandoned within the first 30 seconds |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.5 Incident Resolution – First Contact Resolution
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| First Contact Resolution for all failure incidents (escalation outside Service Desk does not qualify as being resolved) |
| First Contact Resolution percentage. Measures the effectiveness of service desk to resolve incidents on first contact regardless of if contact was made over phone, walk-in to Service Desk, walk-up to Mobile cart, chat, or other means. Resolution can be achieved via multiple contractors teams |
| 85% |
| 80% |
| Calculation Methodology |
| (Number of instances within performance target / total number of instances during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Exceptions |
| Excludes those that cannot be resolved over the phone (e.g., HW swap). Vendor to propose categories of incidents that will not be resolvable at first contact. Government will review and determine final list |
| Performance Indicator |
| CPI |
2.6 Incident Resolution – First Contact Resolution (Afterhours)
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| First Contact Resolution for all failure incidents logged afterhours, weekends, and holidays (escalation outside Service Desk does not qualify as being resolved |
| First Contact Resolution percentage. Measures the effectiveness of service desk to resolve incidents on first contact regardless of if contact was made over phone, walk-in to Service Desk, walk-up to Mobile cart, chat, or other means. Resolution can be achieved via multiple contractors teams |
| 85% |
| 80% |
| Calculation Methodology |
| (Number of instances within performance target / total number of instances during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Exceptions |
| Excludes those that cannot be resolved over the phone (e.g., HW swap). Vendor to propose categories of incidents that will not be resolvable at first contact. Government will review and determine final list |
| Performance Indicator |
| KPI |
2.7 Incident Resolution – Follow-On Calls
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Follow-On Calls (due to problem repeated after initial fix failed or customer request to be re-opened) |
| Follow-on Contact percentage |
| 1.5% |
| 2.5% |
| Calculation Methodology |
| (Number of repeat calls / total calls)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.8 Incident Response and Resolution – Priority 1
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Response: Contact End User to acknowledge receipt of Priority 1 Service Desk Trouble Ticket and schedule repair (Applies to incidents that are not initial warm contacts or resolved during first contact) |
| Elapsed time between incident creation and when a contractor representative contacts the user regarding a resolution for an unresolved incident |
| ≤ 30 minutes 98% of the time |
| ≤ 30 minutes 95% of the time |
| Resolution: Time to Resolution for Priority 1 Incidents |
| Elapsed time between incident creation to when the incident is fully resolved, adjusted for any clock stoppage based on mutually agreed to reasons |
| ≤ 2 hours 98% of the time |
| ≤ 2 hours 95% of the time |
| Calculation Methodology |
| Response: (Number of events per event type within performance target / total number of events per type during Measurement Interval)*100 = percent (%) attained. |
Resolution: (Number of instances resolved within performance target / total number of instances resolved at Level 1 during Measurement Interval)*100 = percent (%) attained
| Measurement Interval |
| Monthly |
| Exceptions |
| Vendor to provide a valid list of reasons to stop the SLA clock (user requested delay, customer unreachable after multiple attempts, customer accepted work around etc.). Does not include customer cancelled incidents |
| Performance Indicator |
| CPI |
2.9 Incident Response and Resolution – Priority 2
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Response: Contact End User to acknowledge receipt of Priority 2 Service Desk Trouble Ticket and schedule repair (Applies to incidents that are not initial warm contacts or resolved during first contact) |
| Elapsed time between incident creation and when a contractor representative contacts the user regarding a resolution for an unresolved incident |
| ≤ 1 hour minutes 98% of the time |
| ≤ 1 hour 95% of the time |
| Resolution: Time to Resolution for Priority 2 Incidents |
| Elapsed time between incident creation to when the incident is fully resolved, adjusted for any clock stoppage based on mutually agreed to reasons |
| ≤ 6 hours 98% of the time |
| ≤ 6 hours 95% of the time |
| Calculation Methodology |
| Response: (Number of events per event type within performance target / total number of events per type during Measurement Interval)*100 = percent (%) attained |
Resolution: (Number of instances resolved within performance target / total number of instances resolved at Level 1 during Measurement Interval)*100 = percent (%) attained
| Measurement Interval |
| Monthly |
| Exceptions |
| Vendor to provide a valid list of reasons to stop the SLA clock (user requested delay, customer unreachable after multiple attempts, customer accepted work around etc.)*** |
| Performance Indicator |
| CPI |
2.10 Incident Response and Resolution – Priority 3
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Response: Contact End User to acknowledge receipt of Priority 3 Service Desk Trouble Ticket and schedule repair (Applies to incidents that are not initial warm contacts or resolved during first contact) |
| Elapsed time between incident creation and when a contractor representative contacts the user regarding a resolution for an unresolved incident |
| ≤ 2 hours 98% of the time |
| ≤ 2 hours 95% of the time |
| Resolution: Time to Resolution for Priority 3 Incidents |
| Elapsed time between incident creation to when the incident is fully resolved, adjusted for any clock stoppage based on mutually agreed to reasons |
| ≤ 24 hours 98% of the time |
| ≤ 24 hours 95% of the time |
| Calculation Methodology |
| Response: (Number of events per event type within performance target / total number of events per type during Measurement Interval)*100 = percent (%) attained |
Resolution: (Number of instances resolved within performance target / total number of instances resolved at Level 1 during Measurement Interval)*100 = percent (%) attained
| Measurement Interval |
| Monthly |
| Exceptions |
| Vendor to provide a valid list of reasons to stop the SLA clock (user requested delay, customer unreachable after multiple attempts, customer accepted work around etc.)*** |
| Performance Indicator |
| CPI |
2.11 Incident Response and Resolution – Priority 4
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Contact End User to acknowledge receipt of Priority 4 Service Desk Trouble Ticket and schedule repair (Applies to incidents that are not initial warm contacts or resolved during first contact) |
| Elapsed time between incident creation and when a contractor representative contacts the user regarding a resolution for an unresolved incident |
| ≤ 2 hours 98% of the time |
| ≤ 2 hours 95% of the time |
| Time to Resolution for Priority 4 Incidents |
| Elapsed time between incident creation to when the incident is fully resolved, adjusted for any clock stoppage based on mutually agreed to reasons |
| ≤ 2 Business Days 98% of the time |
| ≤ 2 Business Days 95% of the time |
| Calculation Methodology |
| Response: (Number of events per event type within performance target / total number of events per type during Measurement Interval)*100 = percent (%) attained |
Resolution: (Number of instances resolved within performance target / total number of instances resolved at Level 1 during Measurement Interval)*100 = percent (%) attained
| Measurement Interval |
| Monthly |
| Exceptions |
| Vendor to provide a valid list of reasons to stop the SLA clock (user requested delay, customer unreachable after multiple attempts, customer accepted work around etc.) |
| Performance Indicator |
| CPI |
2.12 Scheduled Service Requests – 5 or less and 6-10 Scheduled Service Requests
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| 5 or less Scheduled Service Requests (users or machines) |
| Contractor meets requested time frame as agreed to with the SEC |
| 98% within agreed to timeframe |
| 95% within agreed to timeframe |
| 6-10 Scheduled Service Requests (users or machines) |
| Contractor meets requested time frame as agreed to with the SEC |
| 90% within agreed to timeframe |
| 75% within agreed to timeframe |
| Calculation Methodology |
| (Number of instances per type completed on time within performance target / total number of instances per type during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Exceptions |
| Vendor shall be provided with an approximate expected mix of IMAC timeframes required by the SEC. See IMAC mix below |
| Performance Indicator |
| CPI |
2.13 Scheduled Service Requests – 10 or greater Scheduled Service Requests
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| 10 or greater Scheduled Service Requests |
| % complete |
| TBD on a case by case basis |
| TBD on a case by case basis |
| Calculation Methodology |
| (Number of instances completed on time within performance target / total number of instances during Measurement Interval) *100= percent (%) attained |
| Measurement Interval |
| Monthly |
| Exceptions |
| ****Contractor and government will mutually establish a target performance that will determine the performance against this SLA*** |
| Performance Indicator |
| KPI |
2.14 Service Requests Response and Resolution Times – Priority 1
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Response times for Priority 1 Service Requests |
| Elapsed Time |
| ≤ 30 minutes 95% of the time |
| ≤ 30 minutes 92.5% of the time |
Resolution times for Priority 1 Service Requests
| Elapsed Time |
| ≤ 4 hours 95% of the time |
| ≤ 4 hours 92.5% of the time |
| Calculation Methodology |
| (Number of events per event type within performance target / total number of events per type during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.15 Service Requests Response and Resolution Times – Priority 2
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Response times for Priority 2 Service Requests |
| Elapsed Time |
| ≤ 1 hours 95% of the time |
| ≤ 1 hours 92.5% of the time |
| Resolution times for Priority 2 Service Requests |
| Elapsed Time |
| ≤ 1 business day 95% of the time |
| ≤ 1 business day 92.5% of the time |
| Calculation Methodology |
| (Number of events per event type within performance target / total number of events per type during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.16 Service Requests Response and Resolution Times – Priority 3
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Response times for Priority 3 Service Requests |
| Elapsed Time |
| ≤ 2 hours 95% of the time |
| ≤ 2 hours 92.5% of the time |
| Resolution times for Priority 3 Service Requests |
| Elapsed Time |
| ≤ 2 business days 95% of the time |
| ≤ 2 business days 92.5% of the time |
| Calculation Methodology |
| (Number of events per event type within performance target / total number of events per type during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.17 Service Responsiveness – Account Adds
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| New User Account Adds |
| Elapsed time |
| ≤ 1 business day from request 99% of the time |
| ≤ 1 business day from request 95% of the time |
| Calculation Methodology |
| (Number of instances within performance target / total number of instances during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.18 End User Account Administration – Account Changes
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| End User Account change |
| Elapsed time |
| ≤ 1 business day from request 99% of the time |
| ≤ 1 business day from request 95% of the time |
| Calculation Methodology |
| (Number of instances within performance target / total number of instances during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.19 Service Responsiveness – Account Termination
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| User Account Termination |
| Within 1 business day after final termination date/time or notification date1 |
| 100% |
| 100% |
| Calculation Methodology |
| (Number of instances within performance target / total number of instances during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
| Clarifications |
| 1. Whichever date is later |
2.20 Incident Resolution – Closure
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Incident Closure Notice (communicated with the user via e-mail and/or phone (no VM), or in-person) |
| Elapsed time. Non-Automated incident closure communication to the end user prior to Incident Completion in the tracking system |
| 100% |
| 98% |
| Calculation Methodology |
| (Number of instances within performance target / total number of instances during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.21 End User Account Administration – Active Directory Creation
| Service Level |
| Service Measure |
| Performance Target |
| Minimum Performance |
| Creation of accurate and timely Active Directory User Data |
| Reported problems with records. The following fields are to be accurately created in the Active Directory system for each employee or contractor entry: Department, Logon ID, Last Name, First Name, Phone, Room and Company name. |
| 0 Problems Reported |
| 0 Problems Reported |
| Calculation Methodology |
| Total number of problems reported to and logged by the contractor |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.22 End User Account Information – Active Directory Maintenance
| Service Level |
| Service Measure |
| Performance Target |
| Minimum Performance |
| Maintaining Accuracy of Active Directory Data |
| Reported problems with records. The Contractor will ensure that all data in the following fields is maintained and kept up-to-date (based on any moves or changes) in the Active Directory system for each employee or contractor entry: Department, Logon ID, Last Name, First Name, Phone, Room and Company name. |
| 0 Problems Reported |
| ≤ 1 Problems Reported |
| Calculation Methodology |
| Total number of problems reported to and logged by the contractor |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.23 Software Installation – Basic Packaging
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Supported Enterprise-wide Software Packaging (for deployment) - Basic |
| Elapsed time to package within 5 Business Days after scheduling |
| 100% |
| 95% of the time with no single instance exceeding 10 days |
| Calculation Methodology |
| (Number of instances within performance target / total number of instances during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.24 Software Installation – Packaging/Deployment
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Supported Enterprise-wide Software Packaging/Deployment |
| Elapsed time to deploy within 3 Business Days of request |
| 100% |
| 95% with no single instance exceeding 14 days |
| Calculation Methodology |
| (Number of instances within performance target / total number of instances during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.25 Software Installation – Complex Packaging
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Supported Enterprise-wide Software Packaging (for deployment) - Complex |
| Elapsed time to package within 10 Business Days of request |
| 100% |
| 95% with no single instance exceeding 14 days |
| Calculation Methodology |
| (Number of instances within performance target / total number of instances during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.26 Software Installation – Enterprise-Wide Deployment, Complex and Basic
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Success rate of Enterprise-Wide Software Deployment for Basic and Complex |
| Rate of Success |
| 98% of active systems1 deployed within 7 days |
| 100% for active systems2 deployed within 90 days and active for at least 7 days in TEM |
| Calculation Methodology |
| (Number of software deployments without incident / Total Number of Software Deployments)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
| Clarifications |
| 1. Active systems are defined as systems communicating with TEM during the initial release period and having unlocked availability during the initial release period |
2. Active system defined as communicating with TEM during the 90 day period and having unlocked availability during the 90 day period
2.27 Response Time
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Contact End User to acknowledge receipt of Priority 1 Service Desk Trouble Ticket and schedule repair |
| Elapsed time between incident creation and when a contractor representative contacts the user regarding a resolution for an unresolved incident |
| ≤ 30 minutes 98% of the time |
| ≤ 30 minutes 95% of the time |
| Contact End User to acknowledge receipt of Priority 2-4 Service Desk Trouble Ticket and schedule repair |
| Elapsed time between incident creation and when a contractor representative contacts the user regarding a resolution for an unresolved incident |
| ≤ 2 hours 98% of the time |
| ≤ 2 hours 95% of the time |
| Calculation Methodology |
| (Number of instances per type within performance target / total number of instances per type during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Exceptions |
| During normal business hours |
| Performance Indicator |
| CPI |
2.28 Security and Vulnerability, and Anti-Virus Patch Management – Patch Management
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Security and Vulnerability, and Anti-Virus Patch Management |
| Patches must be successfully installed on the same day for all patches rated as Extremely Critical, within three (3) calendar days for all patches rated as Critical, within thirty (30) calendars days for all others patches rated as, after customer approval notification is sent to the contractor |
| 100% of active systems1 |
| 98% of active systems1 |
| Calculation Methodology |
| (Number of patches per type completed within performance target /total of all patches per type occurring during Measurement Interval)*100 = Performance % attained |
| Measurement Interval |
| Monthly |
| Exceptions |
| Extremely Critical, Critical, Important, and All Other to be defined by SEC. Need to adjust for machines that are not online for X period of time |
| Performance Indicator |
| CPI |
| Clarifications |
| 1. Active systems are defined as systems communicating with TEM (for Security and Vulnerability) or MCAfee (for Anti-Virus) during the initial release period and having unlocked availability during the initial release period |
2.29 Imaging – Desktop Update
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Enterprise-wide quarterly image update for the Desktop environment |
| Successful Imaging |
| 100% |
| 100% |
| Calculation Methodology |
| Successfully created image, approved/scanned by security, to include all up-to-date patches by the close of the last business day of each quarter |
| Measurement Interval |
| Quarterly |
| Reporting Period |
| Quarterly |
| Performance Indicator |
| KPI |
2.30 O&M – Tool Availability
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Enterprise-wide Availability of end user infrastructure tools (McAfee, Pointsec, eCopy, BigFix, Swimmage/SCCM, Casper, etc.) *Each tool measured individually and each associated KPI is to be reported individually* |
| Availability |
| 99.9% |
| 99.9% |
| Calculation Methodology |
| Availability(%) = 100% - Unavailability (%) |
Where Unavailability is defined as:
[(Sum of Unavailable Duration) / (Scheduled Time)]% Scheduled Time = (Total possible time in Measurement Interval – Maintenance Window time)
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.31 O&M – Infrastructure Updates (Major)
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Major updates to Enterprise-wide end user infrastructure tools and applications |
| The latest version of tools, only if new version is approved by the SEC, must be deployed within 10 months of release by the vendor |
| 100% |
| 95% |
| Calculation Methodology |
| (The number of tools upgraded to the latest version within the target time frame / Total number of upgrade releases)*100 = percent (%) attained |
| Measurement Interval |
| Annually |
| Exceptions |
| Version must be approved by the SEC |
| Reporting Period |
| Annually |
| Performance Indicator |
| KPI |
2.32 O&M – Infrastructure Updates (Minor)
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Minor updates to Enterprise-wide end user infrastructure tools and applications |
| The latest version of tools, only if new version is approved by the SEC, must be deployed within 6 months of release by the vendor |
| 100% |
| 95% |
| Calculation Methodology |
| (The number of tools upgraded to the latest version within the target time frame / Total number of upgrade releases)*100 = percent (%) attained |
| Measurement Interval |
| Annually |
| Exceptions |
| Version must be approved by the SEC |
| Reporting Period |
| Annually |
| Performance Indicator |
| KPI |
2.33 Adaptive Technologies Support – Deployment
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Deployment of approved adaptive technology |
| Completed within 5 business days once approval received from the Office of Disability and Accommodation if no equipment needs to be ordered. |
Completed within 10 business days once approval received from the Office of Disability and Accommodation if equipment needs to be ordered.
| Calculation Methodology |
| (Number of deployments completed within the target time frame / Total number of approved requests)*100 = Percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.34 NOC Response Time – Notifications
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Notification of Incident or Problem to SEC or Third Party providers |
| Time to notify |
| ≤5 minutes from start of incident, or notification from third party vendor |
| 95.0% |
| Calculation Methodology |
| (Number of events within performance target / total number of events during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.35 Data Center Operations Support – Priority 1
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Priority 1 tasks |
| Time to start tasks |
| < 1 hour |
100% of the time < 1 hour 95% of the time
| Calculation Methodology |
| (Total number of Tasks completed within the Performance Target / Total Number of Tasks)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.36 Data Center Operations Support – Priority 2
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Priority 2 tasks |
| Time to start task |
| < 4 hours |
100% of the time < 4 hours
| Calculation Methodology |
| (Total number of Tasks completed within the Performance Target / Total Number of Tasks)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.37 Data Center Operations Support – Priority 3
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Priority 3 tasks |
| Time to start task |
| < 24 hours |
100% of the time < 24 hours
| Calculation Methodology |
| (Total number of Tasks completed within the Performance Target / Total Number of Tasks)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.38 Data Center Operations Support – Priority 4
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Priority 4 tasks |
| Time to start task |
| < 72 hours |
100% of the time < 72 hours
| Calculation Methodology |
| (Total number of Tasks completed within the Performance Target / Total Number of Tasks)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.39 Hardware and/or Software Inventory – Accuracy
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Inventory Accuracy |
| Measures the accuracy of entries for equipment coming into and leaving the warehouse |
| 99.00% |
| 98.00% |
| Calculation Methodology |
| (Number of inaccurate entries / number of total entries)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.40 Inventory Disposal – Inventory Disposal
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| End-to-end Inventory Disposal |
| Successful disposal of inventory from ticket inception to inventory update in the system |
| 100% within 30 days |
| 98% within 30 days |
| Calculation Methodology |
| (Number of equipment disposals based on approved SF120s completed within the performance target / total of number of SF120s approved)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.41 Hardware and/or Software Inventory Accuracy – Capitalized Property
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Wall-to-wall inventory checks of all Capitalized property |
| Measures inventory of Capitalized property (equipment ≥ $50k in value or bulk purchase ≥ $300k in value) |
| 98% |
| 95% |
| Calculation Methodology |
| (Physical count or electronic discovery count (via asset tag) / total asset inventory)*100 = percent (%) attained |
| Measurement Interval |
| Annual |
| Performance Indicator |
| KPI |
2.42 Hardware and/or Software Inventory Accuracy – Accountable Property
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Wall-to-wall inventory checks of all Accountable property |
| Measures inventory of Accountable inventory (assets with a value ≥ $5,000 or any sensitive asset such as a laptop, smartphone, tablet, desktops, or any device carrying data) |
| 98% |
| 95% |
| Calculation Methodology |
| (Physical count or electronic discovery count (via asset tag) / total asset inventory)*100 = percent (%) attained |
| Measurement Interval |
| Annual |
| Performance Indicator |
| KPI |
2.43 Hardware and/or Software Inventory Accuracy – System Updates
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Timeliness of Updates in Asset Management System |
| Time to update equipment received, transferred, disposed in the system |
| One business day, 100% of the time |
| One business day, 95% of the time |
| Calculation Methodology |
| (Number of transactions completed within performance target / Total Number of transactions/requests received in the system)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.44 Recording – Status Reports
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Monthly Reporting of Asset Management Status (Issues, Resolutions, Consent to purchase (CTPs)) |
| Status report delivered during monthly meeting with SEC team |
| Completed by the 5th business day of the month |
| Completed by the 5th business day of the month |
| Calculation Methodology |
| Number of business days from the start of each month |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.45 Finance – System of Record
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Financial Reconciliation with System of Record |
| Reconcile System of Record and Asset Management Systems |
| Completed by the 5th business day of the month |
| Completed by the 5th business day of the month |
| Calculation Methodology |
| Number of business days from the start of each month |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.46 Service Availability – Infrastructure Availability
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Availability of all Infrastructure components and subcomponents supporting all SEC applications and services, to include all Infrastructure Primary Mission Essential Function (PMEF) components outlined in the Disaster Recovery Plan and referenced Contingency Plans (ISCP). Infrastructure component or subcomponents include all underlying Software, Hardware, and/or appliances that impact service availability |
| SLA applicable to provider-managed boundaries. All Infrastructure components and subcomponents are defined in the DR plan and ISCPs that will be provided post-award. |
| 99.990% |
| 99.500% |
| Calculation Methodology |
| (Total available hours by type / by total hours by type in measurement period)*100 = percent (%) attained |
(example: 24 hours x 21.16 days [average work days in a month] = "monthly available" to define if service level attained).
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.47 Physical Infrastructure Provisioning – Infrastructure Systems
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Provisioning of infrastructure systems and services to include, but not limited to, physical servers, storage, network and appliances, and databases |
| Time to provision is < 5 business days from receipt of HW at the target location |
| 100% of the time |
| 98% of the time |
| Calculation Methodology |
| (Number of requests/events accurately (no rework as a result of contractor error) completed within performance target /total of all requests/events occurring during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.48 Virtual Infrastructure – Infrastructure Systems
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Provisioning of infrastructure systems and services to include, but not limited to, physical servers, storage, network and appliances, and databases |
| Time to provision is < 3 business days from receipt of HW at the target location |
| 100% of the time |
| 98.0% of the time |
| Calculation Methodology |
| (Number of requests/events accurately (no rework as a result of contractor error) completed within performance target /total of all requests/events occurring during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.49 Planned Change – Implementation of Change
| Service Metric |
| Measure |
| Performance Target |
| Minimum Performance |
| Successful implementation of approved Changes in production environment |
| Per approved time an no unplanned outage occurring |
| 100% success rate |
| 95% |
success rate
| Calculation Methodology |
| (Number of requests completed within performance target /total of all requests occurring during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
2.50 Incident Report and Escalation – Time to Notify
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Mean time to notify government about any unplanned outage impacting user services |
| Response Time |
| <30 minutes, 100% of the time |
| <30 minutes, 100% of the time |
| Calculation Methodology |
| (Total time elapsed from notification to acknowledgment for all requests / total number of requests to respond)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.51 Backup – Completion
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Completion of Backups (Daily, monthly, annually) per schedule, backup windows and retention policy |
| Successful backup |
| 100% Per Schedule |
| 99.7% Per Schedule |
| Calculation Methodology |
| (Number of backups completed on schedule/total of all backups scheduled during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.52 Restore – Data and Database Restoration
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Ability to successfully restore requested data |
| Successful restoration of Databases and End User data |
| Contractor to suggest *** |
| Contractor to suggest *** |
| Calculation Methodology |
| Contractor to suggest *** |
| Measurement Interval |
| Contractor to suggest *** |
| Reporting Period |
| Contractor to suggest *** |
| Performance Indicator |
| CPI |
2.53 Infrastructure Vulnerability Management – Vulnerability Mitigation
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Timely and successful mitigation of identified infrastructure system and service vulnerabilities |
| Vulnerabilities associated with infrastructure systems and services must be successfully mitigated within five calendar days of the Vendor making a solution available for all vulnerabilities rated as Critical (Zero Day), within One (1) vulnerability cycle for severity 5 and 4 vulnerabilities and within two vulnerability cycles for Severity 3 and below vulnerabilities. |
| 100% |
| 100% |
| Calculation Methodology |
| (Number of patches per type completed within performance target /total of all patches per type occurring during Measurement Interval)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| CPI |
| Clarifications |
| Successful mitigation is determined by both the resolution of the vulnerability in subsequent system scans and includes sufficient testing and validation to ensure no post mitigation operational impact to production systems. |
2.54 eDiscovery – Response Time to Congress
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Response time to fulfill eDiscovery requests by Congress |
| Time to completion |
| < 3 working days 100% of the time |
| < 3 working days 95% of the time |
| Calculation Methodology |
| (Total number of eDiscovery request completed within 3 business days / Number of eDiscovery requests from Congress)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.55 eDiscovery – Response Time to FOIA
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Response time to fulfill eDiscovery requests by FOIA |
| Time to completion |
| < 5 working days 100% of the time |
| < 5 working days 95% of the time |
| Calculation Methodology |
| (Total number of eDiscovery request completed within 5 business days / Number of eDiscovery requests from FOIA)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.56 Resource Management – Skills Review
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| Skills review |
| Review |
| 100.00% |
| 100.00% |
| Calculation Methodology |
| (Number of position for which Contractor candidate resumes are reviewed by the SEC / Number of open positions filled by the Contractor)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.57 Resource Management – Filling Positions
| Service Metric |
| Measure |
| Performance Target |
| Minimum Performance |
| Time to fill open positions |
| Time to fill |
| <15 calendar days |
| <30 calendar days |
| Calculation Methodology |
| Number of calendar days to begin suitability on an identified Contractor resource from the time a position becomes open |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
2.58 Customer Satisfaction – End User Customer
| Service Metric |
| Measure |
| Performance Target |
| Minimum Performance |
| End User Customer Satisfaction |
| Survey |
| > 85% |
| 80% |
| Calculation Methodology |
| (Average score of all surveys / 5)*100 = percent (%) attained |
| Measurement Interval |
| Monthly |
| Performance Indicator |
| KPI |
| Clarification |
| Both parties will collectively define a survey that measures End User Satisfaction. Survey will measure various services on a scale of 1-5. Contractor will compile the results of the survey and report the average score across all services and surveys. The SEC currently has a satisfaction survey that is intends to continue using |
2.59 Customer Satisfaction – IT
| Service Level |
| Measure |
| Performance Target |
| Minimum Performance |
| IT Satisfaction |
| Survey completed by the IT Groups (as designated by the SEC) |
| > 85% |
| 80% |
| Calculation Methodology |
| (Average score of all surveys / 5)*100 = percent (%) attained |
| Measurement Interval |
| Quarterly |
| Reporting Period |
| Quarterly |
| Performance Indicator |
| KPI |
| Clarification |
| Both parties will collectively define a survey that measures End User Satisfaction. Survey will measure various services on a scale of 1-5. Contractor will compile the results of the survey and report the average score across all services and surveys. The SEC currently has a satisfaction survey that is intends to continue using |
3.0 Priority Levels
3.1 Incident Priority Levels
INCIDENT PRIORITY LEVELS
| Priority Level |
| Definitions |
| 1 – Critical |
| Significant problem affecting multiple users; a critical business function or entire application is inaccessible; multiple customers' work flow impacted |
| 2 – High |
| System operations are severely degraded; potential loss of critical business function is imminent; can impact one or multiple customers |
| 3 – Standard |
| Operation Performance of one system that is moderately impaired or may be needed, while most other business operations continue to function |
| 4 – Low |
| Problems typically affect a single user or a routine service request, does not impact core workflow |
3.2 Service Request Priority Levels
SERVICE REQUEST PRIORITY LEVELS
| Priority Level |
| Employee Level |
| Activity |
1 – Critical
Service request for an activity with a legitimate urgent deadline Service request for something with an immediate impact to productivity such as:
· Password reset
· Account unlock or re-enable
| 2 – High |
| VVIPs, VIPs |
| · Significant impact on productivity |
| 3 – Standard |
| All Others |
| · Most request by default will be priority 3 |
· No deadline or impact on immediate productivity
· Equipment deployment or software installation with minimal impact on daily productivity
· General questions
· How-to or procedural questions