Attachment1-ServicesRequirementsSummary-ServiceDesk-4-26-2018.docx
DOCX document 58 KB Posted
- Attached to
- IT Tool for Customer Service (ITSM)
- Solicitation number
- 127604-18-R-0004
About this file
Attachment 1: Services Requirements Summary
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Forest_Service_ITSM_RFI-4-26-2018.docx | DOCX document |
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
Attachment 1: Services Requirements Summary 127604-18-R-0004
IT Tool for Customer Service
Request for Information
Attachment 1: Services Requirements Summary
127604-18-R-0004
April 26, 2018
The following document includes a high-level overview of the services aspect of the help desk activities of the Service Desk. As discussed in the RFI, these are services provided by a SourceAmerica/AbilityOne contractor. For the most part, these are not IT solution requirements, but services that are dependent on the IT solution and that the IT solution must help facilitate. These are not all Service Desk requirements for the IT solution, but specific to what agents are required to do in resolving help desk-type incidents.
1.0 Services Requirements
The proposed solution must be able to support the following:
1.1. Telephony – The IT solution must integrate with a telephony system, which enables calls to be routed from an end user to the service desk and potentially to a separate service desk (e.g., a higher tier, HR, Finance) for resolution. This may include multiple numbers to reach the Service Desk.
1.2. Incident Management – The Service Desk agents will manage incidents through the IT solution. The IT solution must enable end users and Service Desk technicians to create tickets and report incidents. The IT solution must use standardized method and procedures for efficient and prompt response, analysis, documentation, management, and reporting of all incidents. The IT solution must be capable of automatically (i.e., no re-keying of information) sending and receiving incident information from other IT Service Management systems in use at USDA.
1.3. Knowledge Management – In addressing incidents, the Service Desk agents and users will be dependent on knowledge documents/knowledge articles that reside in the IT solution. The IT solution must include an easily edited; searchable database of knowledge documents and other self-service information; and available to end-users.
1.4. Operational/Project Management – The Service Desk contractor must follow an agreed-upon operational management plan for various tiers of support. The Service Desk contractor must provide the Government with reoccurring IT solution reports that include root cause analysis and agreed-upon system generated metrics, participate in reoccurring status meetings, and provide on-going communication and project support.
1.5. Entitlement – The Service Desk contractor must use the IT solution to validate end users are entitled to services from the Service Desk.
1.6. Transition Services – The Service Desk contractor, and the IT solution contractor, must be flexible to support the transition of existing help desks/contact centers to the Service Desk.
1.7. Continuity of Operations and Disaster Recovery (COOP/DR) – The Service Desk contractor must have redundancies to resume immediate support in the event of a COOP/DR event.
1.8. Proactive Enterprise IT Monitoring – Using the IT solution, the Service Desk contractor must provide proactive monitoring of the entire IT environment to identify and mitigate potential challenges before they become incidents.
2.0 Select Definitions
The following select definitions are provided to help RFI respondents understand current terminology used within USDA.
| Term |
| Definition |
| Service Desk Agent or Customer Service Representative (CSR) |
| An employee or subcontractor of the Service Desk Contractor responsible for direct support of the Customer. |
| Customer or End User |
| Any authorized and entitled USDA or Agency/Customer employee, contractor, or other individual, including members of the general public determined to be entitled to support through the Service Desk. Customers are generally end users but also include Service Desk technicians from the various support organizations. |
| Customer Support |
| The sum of the various tiers of support plus request fulfillment related processes and continued integration of business needs related to information technology. |
| IT Solution |
| Combination of services and/or tools that provide IT Service Delivery system functionality, workflow processing, knowledge management, incident/problem correlation, etc. |
| Knowledge Document (KD) |
| Electronic documents provided by USDA or any of its agencies and/or generated by the Service Desk Contractor, generally of two types: |
· Self Help Procedures – instructions describing a self-help path to incident/problem resolution, if available.
· Resolution Procedures – instructions describing one or more troubleshooting/diagnostic processes, repair processes and/or processes for execution of a software or hardware function.
· Routing Procedures – instructions detailing the individual, workgroup, website, phone number or other entity to whom the incident shall be escalated in the event the Resolution Procedure is ineffective or unavailable.
| Service Level Agreement (SLA) |
| A formal negotiated agreement between two parties describing agreed-upon performance requirements to meet specific business objectives. It is an agreement that exists between service recipients and their service providers and records the common understanding about services, priorities, responsibilities, guarantee, etc. with the main purpose to agree on the level of service for which payment is being rendered. An SLA will typically specify the levels of availability, serviceability, performance, operation or other attributes of the service such as billing and is tied to contract disincentives in case of failure to meet the SLA. |
| Service Level Objective (SLO) |
| A formal negotiated agreement between two parties. It is an agreement that exists between a service recipient and their service provider and records the common understanding about services, priorities, responsibilities, guarantee, etc., with the main purpose to agree on the level of service expected. An SLO will typically specify the levels of availability, serviceability, performance operation or other attributes of the service. Unlike an SLA, no contract disincentive for failure to perform is assessed. An SLO may become an SLA and will then become subject to the SLA definition. |
| Ticket |
| A ticket is an incident or problem represented in the Incident Management System. |
| Warm Transfer |
| Call or chat transfer technique that enables a three-way conversation and then a warm handover to another agent. This allows the original agent to pass along background information about the caller’s situation. |
image1.png image2.png
File details come from the government source that posted it.