Attachment J1 - SLA for My Talking Books (RealSAM).xlsx
XLSX spreadsheet 11 KB Posted
- Solicitation number
- 2027-NLS-0066
- Issued by
-
Library of Congress
About this file
This is a Service Level Agreement (SLA) template for RealSAM Dialog licenses supporting the My Talking Books Smart Speaker project at the Library of Congress. The document establishes performance standards and operational requirements for the sole-source RealSAM Dialog system, which must meet all IT information security requirements mandated by the Library of Congress. The SLA defines service availability targets, response times, and performance metrics that the contractor must maintain during production operations. The agreement outlines uptime commitments, incident response procedures, and escalation protocols to ensure continuous system functionality for the My Talking Books application. The SLA also specifies monitoring and reporting requirements, including metrics tracking and documentation obligations to demonstrate compliance with established service levels. Additional provisions address maintenance windows, support availability, and procedures for addressing service failures or performance degradation. This sole-source procurement is supported by a previously posted and signed Justification and Authorization (J&A), indicating this opportunity is not open to competition and has been justified as a sole-source acquisition based on the specific requirements of the My Talking Books Smart Speaker project.
View the file
Other files
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
SLAs
Attachment J1 - SLA for My Talking Books (RealSAM) August 20, 2026
| SLA for My Talking Books (RealSAM) | ||||
| ID # | ATTRIBUTE | MEASURE | HOW MEASURED | TARGET |
| Availability | ||||
| 1 | Technical Help Desk Function | Availability – services available during business hours which are: |
Monday through Friday 9am through 5pm eastern time
| excluding weekends and federal holidays, and planned system outages | Direct measurement | 98.6%/month | |||
| Communications | |||||
| 2 | Staff Alert period from change event < 8 business hours | The period of time between a completion event, change, or failure event and the communication message sent by contractor to alert the appropriate NLS staff. Communications can be provided via electronic mail, mobile messaging, or voice telephony | Direct measurement | 98.6%/month | |
| 3 | Staff Alert period from severe failure < 8 business hours | Direct measurement | 98.6%/month | ||
| 4 | Staff Alert period from staff shortage < 8 business hours | Direct measurement | 98.6%/month | ||
| 5 | Staff Alert period from completion < 8 business hours | Direct measurement | 98.6%/month | ||
| Performance | |||||
| 6 | Request response time period < 24 business hours | Period of time between the Help desk request and the communication message sent by contractor to respond to the appropriate customer. Communications can be provided via electronic mail, mobile messaging, or voice telephony | Direct measurement | 98.6%/month | |
| 7 | Resolution time period for a request < 72 business hours | The total period of time between the NLS Help desk request from ticket creation to Incident resolution and restoration of service to the user. Service may be restored either by a workaround or by a permanent solution | Direct measurement | 98.6%/month |
Page &P of &N
File details come from the government source that posted it. Updated .