AESMP MSP PWS.docx
DOCX document 120 KB Posted
- Attached to
- AESMP
- Solicitation number
- W52P1J21R0003
About this file
This document includes a Performance Work Statement (PWS) and information about an upcoming federal contract opportunity. The PWS outlines requirements for a Managed Service Provider to perform Army Enterprise Service Desk operations, including staffing two full-service customer service centers, providing project management and ITIL services, migrating operations from the incumbent, and maintaining an Army-wide ITSM system. The opportunity notice states that the Army Contracting Command - Rock Island plans to issue a Request for Proposal in May 2021 for the AESMP task order. The RFP will be open for 45 days. Feedback on the PWS can be submitted to the provided email, but no questions will be answered. The opportunity involves the Department of the Army Materiel Command Joint Munitions Command.
View the file
Other files
Show all 40
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
ARMY ENTERPRISE SERVICE MANAGEMENT PLATFORM (AESMP)
MANAGED SERVICE PROVIDER TASK ORDER
PERFORMANCE WORK STATEMENT
Version Date: 29 December 2020
Table of Contents
| 1.0 | Introduction | 3 |
| 2.0 | Summary Scope | 3 |
| 3.0 | Place of Performance and Hours of Operation | 3 |
| 4.0 | Services to be provided by the Contractor | 4 |
| 5.0 | Staffing | 10 |
| 6.0 | Contractor Furnished Equipment | 16 |
| 7.0 | Government Furnished Equipment (GFE) | 16 |
| 8.0 Performance Requirements | 17 |
Introduction This task order will enable the Army to continue existing Army Enterprise Service Desk (AESD) operations, optimize service support processes for the Army, and support changes in ticket volume over the life of the task order.
Summary Scope The Contractor shall provide two full service (turnkey) customer service centers capable of supporting AESD’s mission, agents on-site at designed Government locations, functional management including resolver maintenance, and ongoing operational maintenance of the Army-wide Information Technology Service Management (ITSM) System provided on a Software as a Service (SaaS) basis for Government and Contractor use under a separate task order.
The turnkey operations shall include all staff, telephony support systems, Workforce Management Systems, and ITSM system support. Additionally, the Contractor shall provide project management, ITIL, and onboarding services. The Contractor shall integrate the telephony support systems and designated Government systems with the ITSM SaaS.
All these services are provided from the Contractor's United States-based facilities having network connectivity to the Army NIPR network and from Government furnished facilities at Ft. Huachuca, AZ; Ft. Shafter, HI; and Camp Humphreys, South Korea which have network connectivity to the Army NIPR/SIPR network.
The Contractor shall comply with processes defined in the Army Enterprise Service Management Framework (AESMF).
Place of Performance and Hours of Operation The work under this task order shall be performed at the following Government-provided NIPR/SIPR service desk sites augmented by approved contractor-provided NIPR sites and contractor-provided remote agents to meet required service levels.
| Facility Type |
| Location |
| NIPR/SIPR |
| Government-owned and contractor-operated |
| Ft. Huachuca, AZ |
| NIPR/SIPR |
| Ft. Belvoir, VA |
| NIPR/SIPR |
| Ft. Shafter, HI |
| NIPR/SIPR |
| Camp Humphreys, South Korea |
| NIPR/SIPR |
| Contractor-owned and operated |
| TBD |
| NIPR |
| TBD |
| NIPR |
| Remote |
| NIPR |
The Contractor shall operate AESD 24x7x365 from a primary Contractor location and provide a secondary Contractor location for Continuity of Operations Plan (COOP) in order to confirm continued operations in the event of problems at the primary site. In addition, the following three sites are required to support Government operations:
· Ft. Huachuca (up to 28 agent seats) (24x7x365 hours of operation)
· Ft. Belvoir (up to 12 agent seats) (24x7x365 hours of operation)
· Ft. Shafter (up to 22 agent seats) (24x7x365 hours of operation)
· Korea (up to 15 agent seats) (12x5x52 weeks per year hours of operation).
The Contractor shall provide personnel on a temporary basis at other designated Government locations as required in order to support on-boarding or other AESD planning activities as required by the Government.
All Contractor personnel providing services and managed capabilities may be considered Emergency Essential, regardless of assigned working location.
Services to be provided by the Contractor
The Contractor shall provide technical and management services including program management, technology management, information assurance, customer relationship management, workforce management, knowledge management, incident management, performance management, quality assurance/quality improvement, management reporting, contingency/disaster recovery, onboarding, and continuous service improvement.
The Contractor shall stand up AESD-Worldwide (AESD-W), AESD-Pacific (AESD-P), and AESD-Korea (AESD-K) operations and assume within six months of contract award the service and support responsibilities from the incumbent AESD contractor.
The Contractor shall migrate operations and any necessary data to the ITSM SaaS from: (1) the ITSM provided by the incumbent AESD contractor supporting NIPR enterprise services ticketing within six months of contract award; (2) the ITSM known as the ESMS provided by the Government supporting both NIPR and SIPR C4IM services ticketing within one year of contract award; and (3) the ITSM known as the SIF supporting SIPR enterprise services within one year of contract award. The migration shall include obtaining the Authority to Operate (ATO) for the ITSM application in accordance with the Department of Defense (DoD) Risk Management Framework described in DoD Instruction 8510.01 dated March 12, 2014, loading, maintaining, and optimizing Government information in the ITSM SaaS, training Government resolvers on use of the ITSM SaaS, and interfacing the ITSM SaaS with the telephony system and the following Government systems: EAMS-A/Single Sign ON (CAC Access), NETPLUS/TMS (Local Telephony), ARCYBER Data warehouse, DISA JRSS, NETCOOL, SPECTRUM, DCOD, and ARMS (Scheduling Application) and through transition to additional and replacement common services provided by cArmy.
Within 6 months of award, the Contractor shall configure asset discovery capabilities and migrate existing asset discovery processes in operation at the FT Detrick, Ft Drum, and FT Natick NECs. Upon successful implementation for those NECs, the Government will establish a schedule with the Contractor for the Contractor to incrementally onboard the remaining ARCYBER/NETCOM/Signal Commands/Brigades/NECs worldwide to the asset discovery capabilities in a 1 year period or less.
The Contractor shall provide Information Assurance (IA) services for AESD and its stakeholders. These IA efforts shall enable AESD to achieve its stated missions, goals, and objectives. These include maintaining the IA levels in accordance with DoD and Army policies and regulations; providing subject matter expertise in accordance with the Risk Management Framework (RMF), all aspects of populating and managing eMASS, including artifacts and documents; and other IA policies and regulations. The skill sets and experience levels shall be commensurate with the complexity and challenges of operating in a DoD environment.
The Contractor shall provide account administration and training of the Government-provided BOMGAR technology for use by AESD agents. The Contractor shall provide Systems Administration (SA) services for AESD and its stakeholders. These SA efforts shall enable AESD to achieve its stated missions, goals, and objectives, including system administration and vulnerability management for CAP and GFE within the security boundary for which the Contractor has access and privilege. This includes items, such as installation, upgrading, and monitoring software and hardware; maintaining operating systems, remote access tools (e.g., BOMGAR), security tools, web-servers, local and wide area networking; and troubleshooting software and hardware. Personnel shall have the required training and/or certifications necessary for the various hardware, software, and/or applications operating within the network environment.
The Contractor shall provide a working papers repository allowing unlimited Government Program Office access in accordance with the working papers contract deliverable.
The Contractor shall adjust staffing levels to address projected ticket volume ranges and SLAs/KPIs while providing support for the following services:
Enterprise Services and applications for users located worldwide:
· Defense Enterprise Email (DEE) for basic class users and the following Commands for other service classes and entitlements:
· NIPR (17 commands for Business Class and above) – AFC, AMC, ARCYBER, ARNORTH, ARSOUTH, ATEC, FORSCOM, IMCOM, NETCOM, RESERVES, SMDC, USACE, USAASC, USACIDC, USARPAC, USASOC, and USMA.
· SIPR (26 commands for Business Class and above) – AFC, AFRICOM, AMC, ARCENT, ARCYBER, ARNORTH, ARSOUTH, ATEC, EUCOM, FORSCOM, GUARD, HQDA, IMCOM, INSCOM, MEDCOM, NETCOM, RESERVES, SMDC, TRADOC, USAASC, USACE, USACIDC, USAEUR, USARPAC, USARAF, and USASOC.
· BlackBerry (BBv10)
· Defense Mobility Unclassified Capability (DMUC) (Supporting Android/iOS devices) (Purebred/Email+)
· Army Knowledge Online (AKO) and AKO-SIPR
· Enterprise Content Management Collaboration System (ECMCS)
· Army Contracting Command (ACC)
· Procurement Automated Data and Document System (PADDS)
· Office of the Deputy Assistant Secretary of the Army (Procurement) (ODASA (P)):
· Standard Procurement Systems (SPS)
· Virtual Contracting Enterprise (VCE)
· Federal Procurement Data System – Next Generation (FPDS-NG)
· Army Contract Writing System (ACWS) (Currently Onboarding)
· Web Emergency Operations Center (WebEOC)
· Army Data Center Consolidation Plan (ADCCP)
· Army Training Management System (ATMS)
· Army Endpoint Security System (AESS)
· Enterprise Computing Operations and Service Center (ECOSC)
· US Army Reserve Command, Secure Army Reserve Network (USARC SARNET)
· Office of the Administrative Assistant to the Secretary of the Army Migration (OAA)
· Installation Management Command, Moral, Welfare, and Recreation Systems Support Division (IMCOM MWR SSD)
· Army Futures Command (AFC)
· Enterprise Access Management Service-Army (EAMS-A)
· Army Food Management Information System (AFMIS)
· Unified Capabilities Soft Client Subscription Service (UC SCSS)
· Unified Capabilities (UC DoDIN Ops)
· Army Endpoint Management Solution (AEMS)
· Electronic Financial Liability of Property Loss (EFLPL)
· Task Management Tool (TMT)
· Reserve Component Automation System (RCAS)
· Defense Readiness Reporting System-Army (DRRS-A)
· Force Management System (FMS)
· CVR
· O365
· Army-wide ITSM SaaS access and maintenance
Command, Control, Computers, Communications, Information Management (C4IM) for the following command and installations:
· 93rd Signal Brigade, 7th Signal Command
| Mid-Atlantic RNEC: Aberdeen Proving Ground |
| NE RNEC: Ft. Drum |
| RNEC:Ft. Campbell |
| Adelphi (Currently Onboarding) |
| Ft. Devens |
| Ft. Knox |
| Carlisle Barracks |
| Ft. Dix |
| Stand-alone NECs |
| RNEC: Redstone Arsenal |
| Ft. Hamilton |
| Ft. Bragg |
| Detroit Arsenal |
| Natick SSC |
| Ft. Gordon |
| Rock Island Arsenal |
| Picatinny Arsenal |
| Ft. Benning |
| SW RNEC: Ft. Stewart |
| West Point |
| Ft. Buchanan |
| Ft. Jackson |
| RNEC: Ft. Eustis (JBLE) |
| Ft. Rucker |
| Ft. Lee |
· 106th Signal Brigade, 7th Signal Command
| West RNEC: Ft. Carson |
| NE RNEC: Joint Base San Antonio |
| Camp Hunter-Liggett |
| Ft. Polk |
| Camp Parks |
| Stand-alone NECs |
| Dugway Proving Grounds |
| Ft. Bliss |
| Ft. Huachuca |
| White Sands Missile Range |
| Ft. Irwin |
| Ft. Hood |
| Presidio of Monterey |
| Ft. Lewis (JBLM) |
Midwest RNEC: Ft. Riley
Ft. Leavenworth
Ft. Leonard Wood
Ft. McCoy
Ft. Sill
· 21st Signal Brigade, 7th Signal Command Stand-alone NECs
Ft. AP Hill
Ft. Belvoir
Ft. Detrick
Ft. Meade
Ft. Myer/McNair
· AESD Pacific (311th Signal Command/516th Signal Brigade)
| Hawaii |
| Japan |
| Ft. Shafter |
| Camp Zama |
| JB Pearl Harbor-Hickman |
| Sagami Army Depot |
| Schofield Barracks |
| Ft. Buckner/Torii Station |
| Wheeler Army Airfield |
| Guam |
| Alaska |
| Andersen Air Base |
| JB Elmendorf-Richardson |
| Kwajalein |
| Ft. Greely |
| Bucholz Army Airfield |
Ft. Wainwright
SW RNEC: Ft. Stewart
Ft. Jackson
Ft. Rucker
· AESD Korea (311th Signal Command/1st Signal Brigade Area NEC’s 1-4)
| Area I NECs |
| Area III NECs |
| Camp Casey |
| Camp Humphreys |
| Camp Red Cloud |
| K55/Osan Air Base |
| Camp Bonifas |
| K-51 Kwangju Airbase |
| Camp Hovey |
| Area IV NECs |
| Camp Stanley |
| Camp Walker |
| Camp Kang Sa Ri |
| K2/Daegu Air Base |
| Area II NECs |
| K8/Kunsan Air Base |
| Yongsan Garrison |
| Camp Henry |
| FEDE Compound |
| Camp Carroll |
| Camp Kim |
| Chinhae Naval Base |
| K16/Seoul Air Base |
| Pier 8, Busan |
| CP Tango |
| Busan Storage Facility |
Camp Mujuk
Camp Seongju
DLA DRMO
K-1 Gimhae Airbase
The Contractor shall provide Service Management Reporting in the form of dashboards and required deliverables as outlined in the contract. The interactive dashboards shall have the ability to filter, sort, summarize, and drill down for variable periods (such as daily, weekly, monthly, and annually) using real time and historical activity metrics and providing:
· Performance against all SLAs/KPIs
· Call volume analytics such as calls by queue and type; average handle time by call type; other call attributes captured by the call management system
· Email volume analytics such as emails by queue and type
· Ticket volume analytics such as tickets by origination, type, ticket status, mean time to restore (MTTR), VIP ticket handling
· Users/seats volume analytics such as by type, organization, new/total, active/inactive
· Integrations and interfaces analytics such as by name, type, and data volume.
The Contractor shall provide the necessary personnel and automation to facilitate Continual Service Improvement (CSI) in order to increase efficiency/ improve effectiveness through reduction in mean time to restore, standardization, technology insertion, process optimization, and strategies to move IT support resolution knowledge closer to users/less technical agents. The contractor shall facilitate process improvement support for, but not expressly limited to:
· Active Directory management services
· Enterprise service account management services
· Desktop Software Delivery to AESD-W
· Ad hoc CSI changes/recommendations
· Support to 7th Signal Command and CONUS
· Support to 311th Signal Command and the Pacific Theater
· Project Office Enterprise Email
· Defense Enterprise Email (DEE) Support, Defense Enterprise Provisioning Online (DEPO) The Contractor shall provide customer relationship management for all supported services and locations in order to establish and maintain positive customer relationships between the Contractor and the organizations supported by AESD.
The Contractor shall provide the Government with a monthly program review of Contractor performance in the past month against established SLAs/KPIs, projected business needs, and other supporting information as detailed in the contract deliverable #XXX.
The Contractor shall assist the Government Project Management Office (PMO) to initiate and document a strategic planning process aligned under the service strategy component. This must, at a minimum, provide 6, 12, and 24-month views of a strategic plan. The views shall encompass plans for technological evolution, process improvement, service migration and transition, ATO compliance, and cost performance optimization. The Contractor shall also conduct a quarterly review of the strategic plan while providing summary assessments as detailed in contract deliverable XXX of the past quarter of ongoing continuous improvement projects, onboarding actions, and system/service desk past performance information as obtained from monthly reports and dashboards.
As directed by the Government, the Contractor shall also use additional Government-provided ticketing or service management systems. The Contractor shall execute all AESD operations activities to the extent possible given the level of administrative rights and access afforded the Contractor in each Government-provided ticketing or service management system.
When directed by the Government after the initial ITSM training provided by the Contractor prior to implementation, the Contractor shall provide Government personnel with training on the configured ITSM SaaS in accordance with the recommended best practices of ITSM tool being provided by the ITSM SaaS provider.
When performing software or integration development such as configuration and integration of the ITSM SaaS with Government systems or addition of Government required functionality, the Contractor shall:
4.13.1 Build to the highest abstraction of cloud services in order to meet functional, technical, performance and cost goals. These services include commercial SaaS, Platform as a Service (PaaS), Database Management as a Service, and others to accelerate testing, accreditation and fielding to the Army.
4.13.2 The contractor must use microservices architecture and automation where technically and economically feasible.
4.13.3 Comply with publishing all application programming interface (API) information within the Enterprise Data Services Catalog (EDSC).
4.13.4 Work with Army Future Command (AFC)'s Command, Control, Communications, Computers, Cyber, Intelligence, Surveillance and Reconnaissance Center (C5ISR) to establish Cyber Security Service Provider (CSSP) services (as required by DoDI 8530 and as described by the DISA Cloud Computing Security Requirements Guide) for Army services hosted in commercial cloud.
4.13.5 Ensure that all new and existing applications, systems, or services deemed non-legacy shall expose their data and functionality through service interfaces (for example, OpenAPI specification).
4.13.6 Ensure that all service interfaces, without exception be designed to be consumable from external sources and must plan and design to be able to expose the interface to developers.
4.13.7 Ensure that all Army data assets are registered in the Army Enterprise Data Service Catalog (EDSC) and comply with Dublin Core Metadata Element Sets and International Standards Organization Metadata Registries requirements.
4.13.8 Ensure that All Army data sources are developed with built-in data exchange capabilities. Data mapping shall also be implemented to increase efficiency and ease of use of data assets as they are being translated or transformed. At a minimum, comply with the Global Force Management Data Initiative (found at Attachment XX); International Standards for dates; Geopolitical Entities, Names and Codes, Common (GENC); Joint Consultation, Command and Control Exchange Data Model (found at Attachment XX); or Resource Description Framework standards and schemas.
4.13.9 Ensure that all cloud-related costs/price, which include but are not limited to: Cloud Service Provider (CSP) costs, and cloud Operations and Maintenance (O&M) costs/prices are clearly identified and available for government reporting purposes.
Staffing
5.1 Staff To Be Provided
The Contractor shall provide qualified personnel in sufficient quantities to perform all tasks, including agents, project management, and support staff. The Contractor shall verify the staff has the appropriate clearances, qualifications, and skills required to perform the tasks. A secret clearance is required for all positions other than Entitlement Managers listed below. The Contractor shall provide recruiting, screening, hiring, training, and monitoring of staff for all tasks. The Contractor shall facilitate confidentiality of data and conduct security background checks for each employee before an employee receiving work. A Government representative will do the fingerprinting process; however, the Contractor shall facilitate the FBI fingerprinting requirements for each contracted employee.
The Contractor shall require its employees supporting AESD to be citizens or legal residents of the United States. However, local nationals are acceptable at the Korea help desk. Employees must have the ability to speak, read, and write English fluently (Korean required at Camp Humphreys and Japanese at Ft. Shafter). The Contractor's direct employment of any Korean-National labor for performance of this contract shall be governed by Republic of Korea (ROK) labor law and United States Forces Korea (USFK) regulations pertaining to the direct employment and personnel administration of Korean National personnel.
5.2 Staff Training and Certifications
The Contractor is responsible for training to maintain skills and certifications for their staff and shall verify that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DoDD 8140.01, Cyberspace Workforce Management. Contractor employees and sub-contractor employees performing work under this contract and who have access to Government information systems and networks shall create a user account and profile in the Army Training and Certification Tracking System website (ATCTS) at https://atc.us.army.mil, in the unit container managed by the COR.
The Contractor shall maintain training data in order to confirm compliance for all contractor personnel in ATCTS. Certificates of successful completion of IA training, Acceptable Use Policies (AUP), applicable baseline and computing environment certifications, and continuing professional education credits, as required by DoD 8570.01-M, shall be uploaded to the ATCTS and provided to the COR for continuous compliance monitoring and reporting.
The Contractor shall ensure that all employees IA certifications are released to the Department of Defense through the Defense Workforce Certification Application at https://www.dmdc.osd.mil/appj/dwc/index.jsp
Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.
5.3 Information Assurance Training and Documentation
All contractor personnel shall comply with the following mandatory and recurring training requirement for AESD training:
| Training |
| Requirement |
| DoD Cyber Awareness Challenge* |
| Annually |
| Derivative Classification* + |
| Bi-Annually |
| Cyber Security Fundamentals Training |
| One-time |
| Threat Awareness and Reporting Program * |
| Annually |
| Personally Identifiable Information (PII)* |
| Annually |
| Operation Security Awareness for Military Members, DoD Employees, and Contractors Course (GS130.16) |
| Annually+ |
| Anti-Terrorism Level 1 |
| Annually |
| Information Security Program Training |
| Annually |
*Training certificates shall be saved in PDF format and maintained by the Contractor.
+Training required only for personnel having SIPR access or any personnel performing derivative classification.
Contractor personnel shall comply with the following IA documentation requirements for ITSM SaaS accesses:
| Document |
| Requirement |
| PII Handling and Incident Response |
| Annually Review |
| AESD PII Purpose and Inventory |
| Annually Review |
| PEO EIS Cyber PII SOP |
| Annually Review |
| PII Acceptance Document |
| Annually |
| Acceptable Use Policy |
| Annually |
| Privileged Level Access Agreement |
| One-time (no expiration) |
In addition to the IA training/certification requirements above, Contractor personnel requiring SIPR access shall complete the following:
| Course |
| Requirement |
| Derivative Classification Training IS 103.06 |
| Initial and Annually Review |
| Marking Classified Information |
| Initial and Annually Review |
| Insider Threat Awareness Training |
| Initial and Annually Review |
5.4 Industry Training
Contractors shall, as required, use Army Skillport to complete the MD 100 Windows 10: Configuring Windows Devices Learning Program. Agents must complete the training and save the certificate.
Contractor personnel performing on this task order are required to obtain Information Assurance Technical (IAT) Level I Certification before beginning support of AESD. The following certifications meet this requirement per DoD 8140.01:
Certification
A+ Continuing Education (CE)
Cisco Certified Network Associate (CCNA)-Security
Network+ CE
Systems Security Certified Practitioner (SSCP)
Agents in Tier 1-2 and above are required to have the ITILv3 or above Foundations certification. If an agent from Tier 1-1 is promoted to a 1-2 position, that employee shall have 90 days from the date of promotion to attain the ITIL Foundations certification. Contractor shall be responsible for verifying the agent attains this certification.
The Contractor shall ensure that all Contractor personnel receive ITSM role training/certification applicable to their position as an agent, system administrator, or other ITSM maintenance position in accordance with the recommended best practices of ITSM tool being provided by the ITSM SaaS provider.
5.5 Other
Entitlement Manager positions shall have the following qualifications:
Qualification
Must be a U.S. Citizen
Must have a High School Diploma
Completed Trustworthiness/Public Trust investigation
6 months of experience
5.6 Key Personnel
The following roles are identified as Key Personnel for performance of all tasks. The Government requires one full time Program Manager, one full time Technical Capabilities Manager, and at least one full time Operations Manager (OPSMGR).
The Contractor shall provide complete resumes for key personnel supporting AESD in order to demonstrate alignment of individual skills and experience. In the event a position is vacated, the Contractor will submit a complete resume when they submit the application for a Common Access Card (CAC) for the person replacing the vacated position. Any key personnel position shall not remain vacant for more than 5 calendar days, the Contractor may propose a temporary substitute by providing a resume of the substitute personnel, if the substitute meets or exceeds the qualifications of the personnel being replaced. In addition, the Contractor will supply additional information requested by the Contracting Officer. Proposed permanent replacement personnel should have equal to or superior qualifications to those personnel being replaced. The Contracting Officer will notify the Contractor within 15 calendar days after receipt of the required information of the consent on replacement personnel. No change in fixed unit prices may occur because of key personnel substitution. A temporary substitute shall not be in place for longer than 30 business days, before a permanent replacement is found.
Core Competencies for Key Positions -- Key Position candidates, regardless of their particular subject matter expertise, shall have the following capabilities:
· The ability to communicate in both oral and written forms, demonstrating an ability to communicate effectively with all levels of staff, as well as clients.
· Familiarity with DoD security requirements as applied to their subject matter expertise.
· Experience working in an environment similar in size (or larger) and scope to AESD.
· Strong working knowledge of large, complex IT environments.
Program Manager (PM) – The Program Manager is defined as having responsibility for oversight of operational planning, establishment, execution, and evaluation of a multifaceted program/project typically consisting of a set of closely related sub-programs or associated activities. The PM should have the qualifications required in accordance with DoDD 8140.01, as well as the following qualifications:
· Help Desk Institute Support Center Director (HDI SCD) Certification
· ITIL v3 or higher Foundations and ITIL Operational Support and Analysis (OSA) Certified
· Secret Clearance
· Current Program Management Institute Program Management Professional (PMI PMP) Certification
· Oversees fiscal, operational, administrative, and human resources management of the program.
· Serves as principal point of representation and liaison with external constituencies on operational matters.
· Provides day-to-day technical/professional guidance and leadership, as appropriate, to AESD.
· The following experience is highly desirable:
Demonstrated excellence in planning, directing, and managing Call Center or sales efforts in a similar sized services organization to AESD Demonstrated successful management and supervision of employees of various labor categories and skills in efforts similar in size and scope to AESD Knowledge of industry accepted standards and best practices related to Call Center missions Demonstrated experience in a DoD IT environment Experience managing performance-based contract Task Orders and knowledge of Federal Acquisition Regulations (FAR) Demonstrated ability for oral and written communication with the highest levels of management Planning, directing, and managing IT projects/operations in an organization similar in size to AESD Knowledge of industry accepted standards and best practices related to Information Management operations, and Information Technology Service Management (ITSM) best practices.
Technical Capability Manager – The Technical Capability Manager is responsible for operational planning, implementation, and operation of technical capabilities provided by the Contractor for service desk use, such as the call management, workforce management, and ticketing systems. The Technical Capability Manager shall have the qualifications required in accordance with DoDD 8140.01, as well as the following qualifications:
· Secret Clearance
· ITIL v3 or higher Foundations or above certification
· ITIL Operational Support and Analysis certification
· CompTIA Security+ CE certification or equivalent
· At least 4 years overall DoD IT environment and RMF experience
· At least 4 years of IT Service Desk management or IT Service Desk operations experience
· At least 1 year of experience in planning, directing, and managing large scale
· IT operations in an organization similar in size to AESD
· Knowledge of industry accepted standards and best practices related to Information Management operations, and with ITSM best practices
· Familiarity with AR25-1 and AR25-2
· Experience with AESS/HBSS, SCCM, NESSUS ACAS, and POA&M submission
· An understanding of DoD culture and standards.
Operations Manager (OPSMGR) – The Operations Manager is responsible for service desk operations and acts as the contractor liaison between the Government PM/COR and the Contractor’s service desk workforce. Provide oversight of the locations, including CONUS and OCONUS. This individual will confirm that day-to-day activities are running efficiently and properly. The Operations Manager shall have the qualifications required in accordance with DoDD 8140.01, as well as the following qualifications:
· Secret Clearance
· ITIL v3 or higher Foundations certification
· ITIL Operational Support and Analysis certification
· Help Desk Institute Support Center Manager certification
· DoDD 8140.01 Baseline certifications, such as COMPTIA A+, Network+, or Security+
· At least 4 years overall IT Service Desk management or IT Service Desk operations experience
· At least 1 year of experience planning, directing, and managing service support operations in an organization similar in size to AESD
· Knowledge of industry accepted standards and best practices related to Information Management operations and with ITSM best practices
· Strong customer service skills and technical aptitude
· An understanding of DoD culture and standards
· Responsible for facilitating the timely process through which incidents and problems are managed. Includes problem recognition, research, isolation, resolution and follow-up steps
· Resolve less complex problems immediately, while more complex problems are assigned to second level support or supervisor (to the PM or the appropriate Army operations center), typically involving the use of problem management database and help desk system
· Provide guidance/training for less experienced personnel
· The following experience is highly desirable:
Planning, directing, and managing IT projects/operations in an organization similar in size to AESD Supervising employees in efforts similar in size and scope as referenced within the PWS.
Knowledge of industry accepted standards and best practices related to Information Management operations, and with ITSM best practices.
Contractor Furnished Equipment The Contractor shall configure and provide the following:
· United States-based primary and secondary COOP facilities
· Automated Call Director (ACD) call processing technology
· Phones and supporting standard office equipment such as copiers, fax machines, etc.
· Workforce management software system providing automated cost accounting linking individual agent labor, calls/contacts, and tickets to specific supported AESD services and providing detailed analytics for work queue analysis and optimized IVR/ACD/service management system configuration and integration
· Public Internet Connectivity subject to DoD firewalling and Information Assurance policies
· Functional management including resolver maintenance, and ongoing operational maintenance of the Army-wide fully IA accredited and configured ITSM SaaS including web-based portal with knowledge bases to support Tier 0 self-service and live agents.
Government Furnished Equipment (GFE)
The Government will provide the following:
· Sponsorship in order for the Contractor to obtain NIPR/SIPR access
· SIPR facilities, as required, to support SIPR-based operations for AESD
· Sponsorship in order for the Contractor to obtain telecommunications services to support AESD Operations using Government- provided toll free numbers and Video Teleconferencing technologies.
· Secure Host Baseline-Army for configuration of GFE desktop computers.
· NIPR connectivity to the AESD contact centers and contractor access to existing Government ticketing/workflow/knowledge management service management systems
· Technology to support the Contractor with obtaining and maintaining RMF compliance
· Laptop/Desktop computers for Agents, PMO, and SMS technicians, as required. GFE computers are to be configured and maintained by the Contractor for AESD Agents
· Provide and administer the BOMGAR server and provide the Contractor access to the BOMGAR remote tool and the ability to administer accounts and provide reporting.
· Access to cloud-based common services (such as EAMS-A, ACAS) with which AESD needs to interface for operations and compliance
8.0 Performance Requirements
The Performance requirements for AESD are specified as Service Level Agreements (SLAs) and Key Performance Indicators (KPIs). The following table summarizes the SLAs and KPIs for AESD to be tracked by user community:
| ITEM |
| NAME |
| TYPE |
| 1 |
| First Contact Resolution |
| KPI |
| 2 |
| Average Speed to Answer |
| SLA |
| 3 |
| Abandonment Rate |
| SLA |
| 4 |
| Response Time to an Inquiry Submitted via Web Form |
| KPI |
| 5 |
| Ticket Accuracy |
| SLA |
| 6 |
| AESD Customer Satisfaction |
| KPI |
| 7 |
| MSP Responsiveness |
| SLA |
In addition, the Contractor shall accumulate performance metrics at least by call, call type, ticket, ticket type, originating user community, and agent, where applicable, in order to provide visibility to the Government on general performance, SLA, and KPI compliance for the Contractor and the AESD Operations.
The Contractor shall provide the Government transparency for its current agent staffing levels and skills training for the ability to handle each call type and ticket type by user community. The Contractor shall accumulate metrics on: (1) the total hours used in support of each user community by call type, call volume, ticket type, and ticket volume; (2) how many on-hand agents are trained/cross trained to service each call type and ticket type by user community; and (3) what are the current training requirements for each call type and ticket type by user community in terms of hours per agent in order for the agent to either attain or maintain skills necessary to handle that call type or ticket type.
The Government and the Contractor shall review the structure of SLAs and KPIs quarterly in order to add, modify, or remove SLAs or KPIs for the support services being provided by the Contractor for AESD.
Projected ticket volumes shall be reviewed quarterly by the Government and the Contractor with Service Owners for any adjustments.
The Contractor shall provide the Government and AESD customers the capability to access a reporting dashboard unique to their organization. Generally, this dashboard consists of the AESD operational profile (the supported services and locations of AESD customers and AESD End Users), call/ticket volumes by supported service, SLA/SLA activity measurements by supported service, AESD functional capabilities profile, contact center locations, and real time views of call center technologies such as real time call queues and wait times being captured by the telephony system.
These standardized metrics and other ticketing and telephony information shall be available to the Government and AESD customers, and reviewed weekly as a measure of AESD operational performance and to identify AESD service improvements. Along with communication of AESD operational activity to customers, the ticketing and telephony information is used in the execution of the AESD QASP for monitoring the performance of the underlying AESD supporting infrastructure. Because of this continuous operations analysis, if AESD Government management identifies projects it feels will improve service, a change request may be provided to the Contractor for review.
The following business rules will be used in determining when tickets should and should not be created:
| Channel |
| Event |
| Result |
| Exceptions |
| Inbound Call |
| An inbound call is received with an inquiry, incident, problem, or service request |
| A ticket is generated |
| A ticket already exists for the incident, problem, service request, or other inquiry |
The user is calling to check status on an existing ticket The user is calling to provide additional information on an existing ticket The user is calling to further discuss an existing ticket The user is calling back because the initial call was disconnected
| An inbound call is received from a user related to a problem reported by other users |
| A ticket is generated |
| A ticket for the specific user already exists for the problem |
Outbound Call
| An outbound call is placed in response to a web form request for call-back |
| A ticket is generated |
| A ticket already exists for the incident, problem, service request, or other inquiry |
| An outbound call is placed in response to a web chat request for call-back |
| A ticket is generated |
| A ticket already exists for the incident, problem, service request, or other inquiry |
| An outbound call is placed in response to a voicemail request for call-back |
| A ticket is generated |
| A ticket already exists for the incident, problem, service request, or other inquiry |
| An outbound call is placed in response to a user request for a call-back |
| A ticket is generated |
| A ticket already exists for the incident, problem, service request, or other inquiry |
| An outbound call is placed in response to a user request for a call-back related to a problem reported by other users |
| A ticket is generated |
| A ticket for the specific user already exists for the problem |
| Web Chat |
| A request to initiate a Web Chat session is received |
| A ticket is generated |
| A ticket already exists for the incident, problem, service request, or other inquiry |
The web chat is initiated for the purpose of checking status on an existing ticket The web chat is initiated for the purpose of providing additional information on an existing ticket The web chat is initiated for the purpose of further discussing an existing ticket The web chat is initiated for the purpose of complaining or complimenting The web chat is initiated because the initial session was disconnected or lost
| A request to initiate a Web Chat session is received and the session is related to a problem reported by other users |
| A ticket is generated |
| A ticket for the specific user already exists for the problem |
| Web form |
| Web form is received with an inquiry, incident, problem, or service request |
| A ticket is generated |
| A ticket already exists for the incident, problem, service request, or other inquiry |
| Web form is received related to a problem reported by other users |
| A ticket is generated |
| A ticket for the specific user already exists for the problem |
Detailed definitions of SLAs and KPIs are as follows:
1: First Contact Resolution
1. SLA SUMMARY
| 1A. TASK AREA |
| Sub-Task 1 - Army Enterprise Service Desk Operations |
| 1B. PERFORMANCE CATEGORY |
| Responsiveness |
| 1C. ITEM # |
| 1 |
| 1D. SLA NAME |
| First Contact Resolution |
2. SLA OVERVIEW
| 2A. SLA DESCRIPTION |
| Measures the efficiency and timeliness of AESD operations as indicated by the proportion of inbound calls and web tickets to the AESD, which are resolved on the First Contact. |
| 2B. RATIONALE |
| Incentivizes staffing of AESD with qualified AESD personnel to facilitate maximum customer satisfaction. |
| 2C. PERFORMANCE PERIOD |
| This SLA is in effect on a continuous basis, 24 hours per day, 7 days per week, without interruption throughout the period of performance. |
3. SLA MEASUREMENT
| 3A. MEASUREMENT INTERVAL |
| The Measurement Interval is 1 month. |
| 3B. MEASUREMENT PERIOD |
| The Measurement Period begins at 00:01 on the first day of the month and ends at 24:00 on the last day of the month.. Zulu time is used for the 24-hour period of measurement. |
| 3C. SOURCE OF MEASUREMENT DATA |
| The source of measurement data is weekly reports from the ticketing system used. |
| 3D. METHOD OF MEASUREMENT |
| SLA attainment is measured by: |
1. A customer contacts AESD via phone or web portal
2. The incident is resolved within the Service Desk
3. If resolved on the First Call, the Agent asks the customer whether the incident has been resolved
4. If the customer responds in the affirmative, the Agent asks if the ticket can be resolved
5. If the customer responds in the affirmative, the Agent resolves the ticket In the Ticketing System
6. This incident is considered resolved on the First Contact
7. If resolved on the First Contact, the Agent resolves the ticket and a message is sent to the customer that the ticket is resolved. If the customer does not respond or re-open the ticket, the ticket is considered resolved on First Contact.
| 3E. TIMING OF MEASUREMENT |
| SLA attainment is calculated after the end of the Measurement Interval. |
| 3F. METHOD OF GOVERNMENT SURVEILLANCE |
| Subject to random or planned audit by the Government or its third party designee. |
| 3G. ASSUMPTIONS/ CONDITIONS |
| 1. After resolution of the ticket, the ticketing system will automatically send the customer an email confirming their ticket has been resolved. |
2. The ticket will include the ticket number and instructions to the customer on how to contact the Service Desk to re-open their ticket, if the incident is not resolved, or if the incident should re-occur before the ticket auto closes.
3. Warm transfers where the incident is resolved by Tier 1-2 are considered Resolved on the First Contact.
4. Tickets escalated to Tier 1-2 or external resolver groups and addressed through call-back are Unresolved on the First Contact.
5. Tickets that result in a callback by any Tier are considered Unresolved on the First Contact.
| 3H. EXCEPTIONS |
| 1. Tickets generated during downtime of the Ticketing System due to a network outage or network performance degradation outside the control of AESD are excluded from the calculation. |
2. New/Existing Onboarded Services that use AESD-W agents as a pass-through (log and route) will be excluded from the FCR calculation.
3. Contacts that occur during the following periods are excluded from the Numerator and Denominator for calculation purposes:
a. Ticketing System downtime approved by the Government (e.g., for scheduled maintenance)
b. Ticketing System downtime due to events outside AESD control and approved as such by the Government
c. Failure of Monitoring Tools.
4. Tickets that result in immediate escalation due to process, policy, or other factor outside of AESD control that does not allow AESD the opportunity to resolve are excluded from the calculation.
4. SLA CALCULATION
| 4A. CALCULATION |
| (NUMERATOR) Number of Successful Instances during 24 hour Measurement Interval ÷ (DENOMINATOR) Total number of Instances opened during 24 hour Measurement Interval = (RESULT) Service Level (%) Attained. |
| 4B. INSTANCE |
| Contact to the AESD. |
| 4C. NUMERATOR |
| Number of tickets resolved on the First Contact during the Measurement Interval. |
| 4D. DENOMINATOR |
| Total number of Contacts during -monthly Measurement Interval. |
| 4E. SUCCESS CRITERIA |
| A successful Call instance is a ticket resolved on the First Contact, wherein the customer agrees that the issue has been resolved. For web tickets, a successful Contact instance is a ticket resolved on first contact, wherein the customer does not re-open the incident. |
| 4F. DEFINITIONS |
| Total number of Contacts during Measurement Interval - Contacts received by the AESD for which AESD has the capability to resolve. |
5. PERFORMANCE OBJECTIVE
| 5A. HOLD HARMLESS PERIOD |
| 1. AESD is responsible for SLA Attainment of Responsibility plus 30 calendar days. |
| 5B. MINIMUM SERVICE LEVEL OBJECTIVE |
| 10% for local NEC services user community. |
15% for the 311th NEC services user community.
75% for the other user communities.
| 5C. SERVICE LEVEL OBJECTIVE TIMEFRAME |
| The Minimum Service Level Objectives in cell 5B is effective as of AOR. |
6. SLA ADMINISTRATION
| 6A. REPORTING FREQUENCY |
| 1. Reporting to commence at AOR. |
2. Daily reporting of results from:
a. Prior day
b. Prior week ending yesterday
c. Prior month ending yesterday
d. Prior quarter ending yesterday
e. Prior year ending yesterday.
3. Weekend and Holiday reporting on next business day.
4. Monthly reporting of SLA attainment and root cause of SLA failures at the Monthly PMR.
| 6B. NOTES AND COMMENTS |
| None. |
2: Average Speed to Answer
1. SLA SUMMARY
| 1A. TASK AREA |
| Task 1 – AESD Operations |
| 1B. PERFORMANCE CATEGORY |
| Responsiveness |
| 1C. ITEM # |
| 2 |
| 1D. SLA NAME |
| Average Speed to Answer |
2. SLA OVERVIEW
| 2A. SLA DESCRIPTION |
| Measures the efficiency and timeliness of AESD operations as indicated by the proportion of inbound calls to AESD, which are answered by an Agent in less than the specified timeframe. |
| 2B. RATIONALE |
| Incentivizes staffing of AESD with qualified AESD personnel to facilitate maximum customer satisfaction. |
| 2C. PERFORMANCE PERIOD |
| This SLA is in effect on a continuous basis, 24 hours per day, 7 days per week, without interruption throughout the Task Order period of performance. |
3. SLA MEASUREMENT
| 3A. MEASUREMENT INTERVAL |
| The Measurement Interval is monthly. |
| 3B. MEASUREMENT PERIOD |
| The Measurement Period begins at 00:01 on the first day of the month and ends at 24:00 on the last day of the month. |
| 3C. SOURCE OF MEASUREMENT DATA |
| The source of measurement data is ACD used by AESD. |
| 3D. METHOD OF MEASUREMENT |
| SLA attainment is measured by: |
1. Querying the ACD for call statistics
2. Determining how many calls were answered by an Agent in less than the Minimum Service Level Objective (Successful Calls) during the Measurement Interval
3. Counting the total number of calls received during the Measurement Interval (Total Calls).
| 3E. TIMING OF MEASUREMENT |
| SLA attainment is calculated after the end of the Measurement Interval. |
| 3F. METHOD OF GOVERNMENT SURVEILLANCE |
| Subject to random or planned audit by the Government or its third party designee. |
| 3G. ASSUMPTIONS/ CONDITIONS |
| None. |
| 3H. EXCEPTIONS |
| Calls abandoned within the minimum SLA objective goal are not counted None. |
4. SLA CALCULATION
| 4A. CALCULATION |
| (NUMERATOR) Number of Successful Instances during Measurement Interval ÷ (DENOMINATOR) Total number of Instances during Measurement Interval = (RESULT) Service Level (%) Attained. |
| 4B. INSTANCE |
| Call to AESD. |
| 4C. NUMERATOR |
| Number of successful Calls during Measurement Interval. |
| 4D. DENOMINATOR |
| Total number of Calls during Measurement Interval. |
| 4E. SUCCESS CRITERIA |
| A successful Call is one to AESD that is answered by an Agent in the specified timeframe or less from the time the caller selects an option. |
| 4F. DEFINITIONS |
| None. |
5. PERFORMANCE OBJECTIVE
| 5A. HOLD HARMLESS PERIOD |
| AESD is responsible for SLA attainment at AOR plus 30 calendar days. |
| 5B. MINIMUM SERVICE LEVEL OBJECTIVE |
| 85% in less than 90 seconds for local NEC services user community. |
80% in less than 300 seconds for the other user communities.
| 5C. SERVICE LEVEL OBJECTIVE TIMEFRAME |
| The Minimum Service Level Objectives in cell 5B is effective as of AOR. |
6. SLA ADMINISTRATION
| 6A. REPORTING FREQUENCY |
| 1. Reporting to commence at AOR Daily reporting of results from: |
a. Prior day
b. Prior week ending yesterday
c. Prior month ending yesterday
d. Prior quarter ending yesterday
e. Prior year ending yesterday.
2. Weekend and Holiday reporting on next business day.
3. Monthly reporting of SLA attainment and root cause of SLA failures at the Monthly PMR.
| 6B. NOTES AND COMMENTS |
| None. |
3: Abandonment Rate
1. SLA SUMMARY
| 1A. TASK AREA |
| Task 1 – AESD Operations |
| 1B. PERFORMANCE CATEGORY |
| Responsiveness |
| 1C. ITEM # |
| 3 |
| 1D. SLA NAME |
| Abandonment Rate |
2. SLA OVERVIEW
| 2A. SLA DESCRIPTION |
| Measures the efficiency and timeliness of AESD operations as indicated by the proportion of inbound calls to AESD in which the caller disconnects before speaking to an agent. |
| 2B. RATIONALE |
| Incentivizes staffing of AESD with qualified AESD personnel to facilitate maximum customer satisfaction. |
| 2C. PERFORMANCE PERIOD |
| This SLA is in effect on a continuous basis, 24 hours per day, 7 days per week, without interruption throughout the Task Order period of performance. |
3. SLA MEASUREMENT
| 3A. MEASUREMENT INTERVAL |
| The Measurement Interval is monthly. |
| 3B. MEASUREMENT PERIOD |
| The Measurement Period begins at 00:01 on the first day of the month and ends at 24:00 on the last day of the month.. |
| 3C. SOURCE OF MEASUREMENT DATA |
| The source of measurement data is ACD used by AESD. |
| 3D. METHOD OF MEASUREMENT |
| SLA attainment is measured by: |
1. Querying the ACD to determine how many calls were disconnected before the caller spoke to a live agent
2. Counting the number of calls disconnected before the caller spoke to a live agent (Abandoned Calls)
3. Counting the total number of calls received during the Measurement Interval (Total Calls).
| 3E. TIMING OF MEASUREMENT |
| SLA attainment is calculated after the end of the Measurement Interval. |
| 3F. METHOD OF GOVERNMENT SURVEILLANCE |
| Subject to random or planned audit by the Government or its third party designee. |
| 3G. ASSUMPTIONS/ CONDITIONS |
| None. |
| 3H. EXCEPTIONS |
| Calls abandoned within the minimum SLA objective goal are not counted. |
4. SLA CALCULATION
| 4A. CALCULATION |
| (NUMERATOR) Number of Unsuccessful Instances during Measurement Interval ÷ (DENOMINATOR) Total number of Instances during Measurement Interval = (RESULT) Service Level (%) Attained. |
| 4B. INSTANCE |
| Call to AESD. |
| 4C. NUMERATOR |
| Number of unsuccessful Calls during Measurement Interval. |
| 4D. DENOMINATOR |
| Total number of Calls during Measurement Interval. |
| 4E. SUCCESS CRITERIA |
| An Unsuccessful call is one that is abandoned before an Agent picking up. |
| 4F. DEFINITIONS |
| Abandoned Call – A call during which a caller selects an option from the Voice Response Unit and hangs up the call before the call is answered by a live Agent. |
5. PERFORMANCE OBJECTIVE
| 5A. HOLD HARMLESS PERIOD |
| AESD is responsible for SLA attainment at AOR plus 30 calendar days. |
| 5B. MINIMUM SERVICE LEVEL OBJECTIVE |
| Less than 15%. |
| 5C. SERVICE LEVEL OBJECTIVE TIMEFRAME |
| The Minimum Service Level Objectives in cell 5B is effective as of AOR. |
6. SLA ADMINISTRATION
6A. REPORTING FREQUENCY
1. Reporting to commence at AOR.
2. Daily reporting of results from:
a. Prior day
b. Prior week ending yesterday
c. Prior month ending yesterday
d.…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .