Attachment C - DLA Management 10 Questions.pdf

PDF 110 KB Posted

Attached to
SP4701-26-R-0002 -RFP-ERP Cloud Hosting and Subscription Licenses with Managed Services
Solicitation number
SP4701-26-R-0002
Issued by

About this file

This document is a management template containing ten standardized questions for incident response and post-incident reviews related to ERP Cloud Hosting and Subscription Licenses with Managed Services operations at the Defense Logistics Agency (DLA).

The ten questions serve as a framework for comprehensive incident documentation and analysis. They require identification of how incidents are discovered (through monitoring tools, verbal notification, or other means) and assessment of whether detection methods are adequate; description of what actually occurred; classification of incidents as outages or degradation with operational impact analysis; documentation of resolution actions, responsible parties, and timelines; explanation of incidents exceeding two-hour resolution times; identification of recent system changes or Engineering Change Requests (ECRs); root cause analysis and accountability; review of similar recent incidents; preventive measures and implementation schedules; and formal resolution statements from IT Service Management (ITSM) or DISA systems. The template includes placeholder fields for the INFOSPOT Point of Contact, Estimated Restore Time, Briefer for J6 Daily Scrum, and Ticket Number/Source. This document is marked as Controlled Unclassified Information (CUI) and constitutes source selection information under FAR 2.101 and 3.104.

View the file

Other files

Show all 17

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 C: DLA Management 10 Questions ERP Cloud Hosting and Subscription Licenses with Managed Services

CUI

Source Selection Information See FAR 2.101 & 3.104

INFOSPOT POC:

ESTIMATED RESTORE TIME:

BRIEFER FOR J6 DAILY SCRUM:

TICKET#/TICKET SOURCE:

BOTTOM LINE UP FRONT (BLUF):

1. How did we find out about the incident (verbal, phone, email, proactive monitoring tool) date/time notified? If not caught by a monitoring tool, why not and can we get the system instrumented to catch similar issues before an outage is caused?

2. What actually occurred?

3. Is/was it an outage or degradation (i.e. HAZCON), what is/was the operational impact to the users (what can they not do)?

4. What actions are/were taken by who to resolve the incident and what are the next steps and estimated timeline?

5. If outage/degradation took more than two hours to resolve, provide details, explain why.

6. Were there any recent changes/ECRs to the system?

7. What was the root cause of outage and who/what org is responsible for resolving? If root cause is unknown, why did we take the actions we took?

8. Are we aware of any similar incidents to this system/application recently?

9. What can/will we do to prevent reoccurrence and when will that be accomplished

10. If incident is "Resolved", provide ticket resolution statement from ITSM/DISA

ITSM/Etc: TBD.

File details come from the government source that posted it. Updated .