Red Pineapple Standard Operating Procedure (SOP) Template, v0.2Prepared by: Thinking problem management! TOC o "
u Title of SOP PAGEREF _Toc210571211 h 2Dates PAGEREF _Toc210571212 h 3Issue date PAGEREF _Toc210571213 h 3Effective date PAGEREF _Toc210571214 h 3Document history PAGEREF _Toc210571215 h 3Approvals PAGEREF _Toc210571216 h 3Description PAGEREF _Toc210571217 h 3Purpose and background PAGEREF _Toc210571218 h 3Scope PAGEREF _Toc210571219 h 3Definitions PAGEREF _Toc210571220 h 4Operations PAGEREF _Toc210571221 h 6Maintenance PAGEREF _Toc210571222 h 6Projects PAGEREF _Toc210571223 h 8Business justification and project request form PAGEREF _Toc210571224 h 8Project Lite methodology (mini projects) PAGEREF _Toc210571225 h 8Large projects PAGEREF _Toc210571226 h 8Fulfilment PAGEREF _Toc210571227 h 10Example - Video conferencing PAGEREF _Toc210571228 h 10Quality and targets PAGEREF _Toc210571229 h 10Vital functions affected by this SOP PAGEREF _Toc210571230 h 12Lessons learned PAGEREF _Toc210571231 h 12Record and Document Management PAGEREF _Toc210571232 h 12References PAGEREF _Toc210571233 h 12Standards PAGEREF _Toc210571234 h 12Images PAGEREF _Toc210571235 h 12Diagrams PAGEREF _Toc210571236 h 13Equipment, hardware and software lists PAGEREF _Toc210571237 h 13Labelling and naming standards PAGEREF _Toc210571238 h 13Checklists PAGEREF _Toc210571239 h 13Installation PAGEREF _Toc210571240 h 13Configuration PAGEREF _Toc210571241 h 13Testing PAGEREF _Toc210571242 h 14Financial PAGEREF _Toc210571243 h 14Budget exception / deviation PAGEREF _Toc210571244 h 14Risk PAGEREF _Toc210571245 h 14The CRAMM Risk management methodology PAGEREF _Toc210571246 h 15Meerkat Risk Methodology PAGEREF _Toc210571247 h 17Information Security PAGEREF _Toc210571248 h 18Physical security PAGEREF _Toc210571249 h 18Service Continuity PAGEREF _Toc210571250 h 18Risk evaluation and control PAGEREF _Toc210571251 h 19Business impact analysis PAGEREF _Toc210571252 h 19Develop continuity strategies PAGEREF _Toc210571253 h 19Emergency response and operations PAGEREF _Toc210571254 h 19Developing and implementing the BCP PAGEREF _Toc210571255 h 19Awareness and training program PAGEREF _Toc210571256 h 19Maintaining and exercising the BCP PAGEREF _Toc210571257 h 20Standards and guidelines PAGEREF _Toc210571258 h 20Escalations PAGEREF _Toc210571259 h 20Roles and responsibilities PAGEREF _Toc210571260 h 20The Uberfingers team leaders dashboard PAGEREF _Toc210571261 h 21Shifts PAGEREF _Toc210571262 h 21Training PAGEREF _Toc210571263 h 22Monitoring requirements PAGEREF _Toc210571264 h 22Change PAGEREF _Toc210571265 h 22Stakeholders PAGEREF _Toc210571266 h 22Request for change PAGEREF _Toc210571267 h 23Apply for testing PAGEREF _Toc210571268 h 23Configuration management database PAGEREF _Toc210571269 h 23Impact and risk assessment PAGEREF _Toc210571270 h 23Change Advisory Board (CAB) PAGEREF _Toc210571271 h 23Installation in testing PAGEREF _Toc210571272 h 23Test installation review PAGEREF _Toc210571273 h 23Testing in progress PAGEREF _Toc210571274 h 23Operational acceptance phase PAGEREF _Toc210571275 h 24Ready for live PAGEREF _Toc210571276 h 24Implementation in live PAGEREF _Toc210571277 h 24Go Live acceptance PAGEREF _Toc210571278 h 24Live PAGEREF _Toc210571279 h 24Integration with Service Desk PAGEREF _Toc210571280 h 24Change types PAGEREF _Toc210571281 h 24Vendors PAGEREF _Toc210571282 h 25Review and evaluation of vendors PAGEREF _Toc210571283 h 25Maintenance PAGEREF _Toc210571284 h 26Warranty PAGEREF _Toc210571285 h 26Handling Incidents and Troubleshooting procedures PAGEREF _Toc210571286 h 26The Expanded Incident Lifecycle PAGEREF _Toc210571287 h 26Service review PAGEREF _Toc210571288 h 26Meetings PAGEREF _Toc210571289 h 27Previous period PAGEREF _Toc210571290 h 27Performance review PAGEREF _Toc210571291 h 27Current issues PAGEREF _Toc210571292 h 27Peripheral issues PAGEREF _Toc210571293 h 27Grading of service desk interaction PAGEREF _Toc210571294 h 28Grading of service desk escalation PAGEREF _Toc210571295 h 28Checklist for SOP PAGEREF _Toc210571296 h 29Addendum PAGEREF _Toc210571297 h 29Service catalogue PAGEREF _Toc210571298 h 29Title of SOPDatesIssue date
DescriptionPurpose and backgroundScope< Example - The principal goal of this document is to ensure effective and efficient communications, coordination, and decision-making between the operational areas and the business units, particularly in regard to service (including task, changes, deviations and reporting). Clear communication is essential to provide quality services to business unit customers.The nature of our business now requires an increased ability to work across areas, generating requirements that, by their nature, are best met at the corporate level. The shift in how information and knowledge are generated, used and managed when coupled with the competition for limited budgets dictates a more strategic approach to providing information infrastructure services across the enterprise. There are a number of specific drivers for approaching IT systems more strategically. These include:Improving the enterprises’ IT infrastructure to meet the vision and strategic plan.Positioning the IT infrastructure to support corporate applications such as enterprise risk management and integrated messaging.Ensuring availability of integrated services across areas.Supporting a robust collaborative program and management environment.Achieving reduced cost of services to IT customers.Improving security.Delivering consistent, quality services to IT customers.Fundamental concepts involved in providing and receiving quality IT services include classes of service with varying levels of service delivery and restoration priorities. Additionally, services are supported by technical architectures with varying degrees of redundancy and survivability, depending on the class of service. We operate a service desk, with primary responsibility for particular classes of service. We also operate multiple availability management areas and coordinate the escalation and support activities of numerous service providers, carriers and manufacturers. The processes governing these areas are critical to successful operation and management of services. The procedures and responsibilities defined in this document are applicable to IT operational areas and customers. They refer to all types and classes of services. Refer to the Addendum for the Services Catalogue, which contains a full description of classes of service.>Definitions< This section should highlight and define frequently used terms and provide additional and/or relevant information needed in order to use and understand this SOP><24 X 7 - Time period that extends for 24 hours each day of the week.><8 X 5 - Time period that extends for a typical 8 hour work day Monday through Friday.>OperationsOverview of Infrastructure operationsMaintenanceProjectsBusiness justification and project request formsProject Lite methodology (mini projects)When operational projects are small in scope, then a full blown methodology is an overkill, and a small or mini version would be better, a so called “lite” methodology. Large projectsIntentChoose a well-skilled and respected project leader. Project leaders do not make operational or technical decisions but rely on the team.Recruit the right project team and ensure that team members are competent.Adopt tools and techniques that can manage complexity (sound management practices).ScopeDetermine deliverables and encourage business unit user involvement.Feasibility study. Determine if the project is possible and finance creatively. Use multiple funding resources.Value analysis including benefits. Settings goals and expectations. The expectations should be realistic.Top management review/decision. Sell the project to decision makers (based on project benefits).PlanningLook for existing similar projects that have succeeded and use these as a baseline for modelling.Business unit user requirements. Understand and improve (business) processes before you apply technology. Make certain that the requirements are clearly stated.Prototyping and test plan. Use prototypes to ensure understanding and agreement about design.Accounting plan. Provide schedules on expenditure.Resource planning. Make optimal use of vendors.ExecutionSystems development. Use industry standards. Choose a capable pilot site.Inspections. Abide by pre-determined standards.Integration with Change management.Systems acceptance testing and audits. Integrate with related processes and practices.Implementation. Match the technology to the job.Documentation. Provide simplistic and clear instructions/guides.Training development. Make sure all Business Unit users are trained thoroughly.Management review and approval. Review and evaluate performance (compare system’s actual operational performance to expected benefits.ControlCommunication of information around the project is constant. The project manager ensures that communication occurs effectively, clearly & in a timely manner between the team leaders, team members & stakeholders. Going "
for any significant amount of time is simply not allowed.Simplicity encompasses all factors of the project being completed and described in the simplest possible terms. All activities must contribute a measurable value to the project. Measuring the value of a project is the role of the stakeholders & the project manager and is done by asking what the value of specific tasks or deliverables is.Continuous feedback is the primary tool for defining & sustaining projects.Change is part of any realistic IT project as requirements evolve over time. Dealing with the consequences of change or discarding the outcome when the decision is proven inadequate requires courage. The stakeholder understanding of the requirements will change over time as the project progresses. Stakeholders may change their point of view, which in turn will change the goals and success criteria of the project.Humility: The best project managers acknowledge they don’t know everything. The stakeholders, project participants and customers all have there our area of expertise and add value to the project. An effective approach is to assume that everyone involved with the project has equal value & therefore should be treated with respect.Incremental Change. Make the project milestones smaller. The project can still be considered a failure even when the team delivers a working system to customers. Part of fulfilling the needs of the stakeholders is to ensure that the system is robust enough to be extended over time. The pressure to get it right the first time can overwhelm the best project manager. Instead of futilely trying to develop an all encompassing project plan from the start, put a stake in the ground by developing a small portion of the system, or even a high–level model of a larger portion of the system, and evolve this portion over time. Or simply discard it when you no longer need it in an incremental manner.Closure (Post-mortem)Post-implementation refinement.Post-implementation review and audit.Metrics analysis.FulfilmentExample - Video conferencingPlanningClear purpose of conferenceUnderstand deliverablesDetermine number and length of sessionsAgree on contentTechnical pre-setupChecklistsISDN numbers.Names of sites.Names of participants.Mobile phone numbers of participants for backup.Technical troubleshooting: Sound, video, dial tones, feedback, batteries & cameras.Address bookSession protocolIntroductions & formalities (location, time, weather).Focus of conference & procedural information (muting)."
Talk naturally, at an even pace, with expression and clarity (emphasize pitch, tone, volume pausing and pacing)."
Remember that an animated, energetic, enthusiastic presence is critical when motivating, holding attention & emphasizing points.Look at the camera, not the screen.Share tasks across the sites & encourage participation.Do not talk for more than 30 minutes without a breakAfter the session email participants, thanking them for their participation & include opinions & issues.Room setupClothing: Wear shades of blue or gray. Avoid green, red or orange.Sounds & movements: Avoid tapping on the desk, shuffling papers & whispering to other participants. Avoid rocking in your chair or moving from side to side. Use hand and arm movements.Speaking & eye contact: Position the camera above the monitor.Look directly at the monitor & create the perception that you are addressing the remote participant as if they were in the same room.Manage motion & sound delay: Allow for delays as interruptions in a video conference are different for remote participants as opposed to local participants.Quality and targets. 10) within x minutes, and will start diagnosing with x minutes. Incidents that affect a single user will be responded to within x minutes, and will start diagnosing in x minutes. Updates will be given every x minutes.>Number of errors found, Customer satisfaction with features and benefits.>Reduction in service costs, Improved coordination with internal and third parties, Highly motivated service team members.>Vital functions affected by this SOPLessons learnedRecord and Document ManagementReferencesStandardsPCI Data Security StandardImagesNameRowCabinetPositionPatching, , , Asset bar codesDiagramsEquipment, hardware and software listsLabelling and naming standardsChecklistsExamplesAir handling units checklistConceptual Architecture ChecklistData centre operations checklist - useful softwareDMZ checklistElectrical checklists from the US ArmyFCAPS checklistHVAC checklistInfrastructure business case checklistInfrastructure maturity checklistInfrastructure risk assessment checklistITIL implementation checklistNetwork architecture documentation checklistSOX checklist (Ernst and Young)Standby generator checklistSwitch security checklistSystems design checklistTechnical design checklistThird party assessment checklistVirtual meeting checklistVirtual teams checklistInstallationConfigurationTestingFinancialBudget exception / deviationsRiskThe CRAMM Risk management methodologyInterview the stakeholders; value the data and infrastructure by the impact/cost resulting from loss of Confidentiality, Integrity, or Availability; and by replacement cost. Consider the impact of the following attributes:Confidentiality -- impact of or sensitivity to disclosure to non-authorized parties, e.g., “employees,” “contractors,” etc. Use confidentiality requirement categories of public (0), restricted (1-5), confidential (6-9), and secure (10).Integrity -- impact of unknown or unauthorized modification e.g. “data input errors,” etc. Use integrity requirement categories of low (1-3), moderate (4-7), high (8-9), and very high (10). Availability -- impact of the asset being unavailable for various time frames, e.g., “less than 15 minutes”, “1 hour”, “1 day”, etc. Use availability requirement categories of low (1-3), moderate [OK to recover in days] (4-6), high [hours] (7-8), very high [minutes] (9), and mandatory [cannot be down] (10).For each of the above, have the stakeholders choose a category, then a value within the category. For example, for Integrity, have them choose first from low, moderate, high and very high. Then, if they chose moderate, in this case, ask them to rank the impact on a scale of 4 to 7. Identify any existing measures already in place to control risks.Review and agree deliverables. Determine how likely each risk is by asking questions of support personnel, experts and others using prepared questionnaires to try and asses the likelihood that the identified risks could actually occur. Consider hackers (internal and external), viruses, failures (applications and infrastructure), disasters, and adverse issues (people, process or procedure). Create a column for each threat. Use a categories of none (0), low (1-4), moderate (5-7), high (8-9), and very high (10).Calculate the Risk entry by multiplying the Impact by the Vulnerability. Based on the risk score (impact X vulnerability) assign a label of low (1-33), medium (34-67), or high (68-100). Update for each item. This is an agreed list of the most vulnerable areas and is then agreed to by the business.Review and agree deliverables. Begin to identify and select countermeasures for those items with the highest risk level. Consider countermeasures and ways to mitigate the threats. Focus on the higher-level threats first, but don't overlook quick, easy or cheap fixes to lower level threats. Implement countermeasures for low level as well as high level threats. Give precedence to those countermeasures that: protect against several threats protect high risk assets apply where there are no countermeasures already in use are less expensive to implement are more effective at preventing or mitigating threats prevent threats rather than detecting or facilitating recovery can be implemented quickly, easily and inexpensively (even for low risk)Meerkat Risk MethodologyThe following is a scaled down version of CRAMM, known as Meerkat Risk Methodology: Risk impact (Mark with a X) Dashboard designation = IEvaluate the data and information that is directly effected by the incidentConfidentiality (Information is accessible only to those authorized)SecureConfidentialRestricted*PublicIntegrity (Safeguarding the accuracy and completeness of information)Very highHighModerate*LowAvailability (Authorised users have access to information when required.)MandatoryVery highHighModerate*LowRating Taking into account the above please rate the Risk impactCriticalMajorModerateLowRisk vulnerability (Rate as either low, moderate, high or major) Dashboard designation = VRate the vulnerability in the following categories of the information or data that is affected by the incidentLossErrorFailure*Rating Taking into account the above please rate the Risk vulnerabilityCriticalMajorModerateLowCountermeasures Dashboard designation = CMWhat measures are in place to mitigate any risks identified with the information or data affected by the incidentRating Taking into account the above please rate the Risk CountermeasuresCriticalMajorModerateLowThe risk ratings are then aggregated into a dashboard. The dash board calculation is performed by assigning the ratings a value:Critical = 4Major = 3Moderate = 2Low = 1The maximum score is 12 so the risk management dash board value is that combined aggregated ratings score worked out as a percentage of 12.Risk Management Example (84%)ImpactVulner.Counter442Information SecurityPhysical securityMaintenance and access scheduleThis table is stored in a plastic sleeve attached to the cabinet door in the data centre.When this table is full this sheet needs to be filed and another template printed.Date stampPersonReference and detailsService ContinuityRisk evaluation and controlDefinitions of threats, risks and assetsRisk assessment and managementCompliance issuesCritical component failure analysisRisk areas: Security and sitesBusiness impact analysisBusiness process matrix, time window for recovery & critical success factorsOutputs, deliverables, activity categorisation and key performance indicatorsReview of documentation, questionnaires and interviews.Financial JustificationDesigning an Impact Matrix and Simplified Impact AnalysisDevelop continuity strategiesVital materials and back-up.Business continuity strategy, recovery options and timescalesContractual arrangements for recovery servicesLateral and creative thinkingInsuranceEmergency response and operationsTypes of emergenciesCoordination with authoritiesPublic relations, media management and crisis communicationCommunication with stakeholdersSalvage and restorationDeveloping and implementing the BCPPlan Introduction & identify teams.Roles and responsibilitiesTasks, Actions and FunctionsAlternative Locations (Standby Locations)Contact Details for Internal & External ContactsResource requirementsAudit trail, reporting processes and requirementsDocument configuration and version controlInterim measuresAwareness and training programEstablishing objectives and components of the awareness programDeveloping the training methodologyAcquiring or developing training aids including external training opportunitiesMaintaining and exercising the BCPBusiness continuity plan, audit and reviewExercise strategy and methodsExercise checklistPost exercise reportingStandards and guidelinesAdopt standards on disaster/emergency management and business continuity programs.Measured compliance with standards.EscalationsRoles and responsibilitiesThe Uberfingers team leaders dashboardShiftsDescription of shiftExample - This is for shift work for the data centre located at 1984 Pineapple Avenue. The shift duties will comprise operator duties during the day and standby during the nights.Shift workExample - The shift period is 6 days on and 2 days off. The shift starts at 08h00 on day 1 for a period of 8 hours (16 hours standby) and finishes at 08h00 on day 7. The 2 days off commences at 08h00 on day 7 and finishes on day 9 at 08h00 when the next shift starts.PaymentExample - Payment for shift will be made at 1984 Pineapple on completion of shift. DutiesExample - The care duties are as follows:Server backupMonitoring day end processesWagesExample - The employee will be remunerated at Rx per day for on shift days and receive no remuneration for off shift days. Standby work will be remunerated at Rx per hour.OvertimeExample - No overtime is calculated or remunerated.Work on SundaysExample - No extra remuneration for a Sunday is calculated.Public holidaysExample - No extra allowances are made for a public holiday. A public holiday can be substituted for an off shift day.TransportExample - The employee will receive Rx for transportation for each shift.ClothingExample - The employer is not required to provide any uniforms or clothing.Meal intervals and breaksExample - The employee shall be granted a 1/2 hour break after not more than 5 hours of work on any day that she works. The employee will prepare her own meals and the employer will provide pause facilities. A break of 3 hours per shift can be taken upon mutual agreement of a suitable time.LeaveExample - 1.5 days leave per month is available after which any other leave taken will be unpaid.Sick leaveExample - The employer shall grant the employee who is absent from work through incapacity, one working day's sick leave on full pay in respect of every 5 shifts completed for which he/she has been employed by such employer. Any additional sick leave will be unpaid.NoticeExample - The employer or the employee shall give the other 2 shift's notice to terminate this agreement, which notice must be given on or before the 1st day of the shift.TrainingMonitoring requirementsChangeStakeholdersRequest for changeChange requestor initiates process and role players in change identified.Standards and quality criteria established for the raising of changes.Change evaluation and assessment process.Apply for testingAll upgrades or growth procedures should be fully validated in the lab environment prior to first application in the field.Collect all data necessary for further evaluation of RFC.Develop deployment plan.Deployment manager initiates process for testing change.Configuration management databaseExtend CMDB by new Configuration Items (CI) & relations that are inherent to the new change.Defines relevant CIs and their relation to other CIs (logical and physical interdependencies).Impact and risk assessmentAssessment of impact and risk on technical level.Assessment of impact and risk on business level.Change Advisory Board (CAB)Functions and purpose of change management has been communicated within the enterpriseApproval of changeConduct final assessment of requested change and issue approval/denial.Installation in testingPre-installation MeetingPerforms installation as described in Deployment PlanAttend and support the installationTest installation reviewReview installation of testingFeedback on testing installationFormal declaration of testing phaseTesting in progressConduct a pre-defined set of basic integration tests (as defined by the Deployment Management)Conduct functional testConduct user acceptancePrevention of interference with existing live systemsOperational acceptance phaseAcceptance testing checklist and operations readiness signoffService integrated into existing productive environmentReview test resultsReady for liveVerify all tests completedService desk informed and trainedCustomers informedFormal declaration of liveImplementation in liveImplementation performed as described in deployment plan.Support and supervision of implementation.Go Live acceptanceSuccessful integration in live environmentDecide back-out strategiesQuality assuranceReview implementationLiveServices provided to customersSLA measured and achieved.Integration with Service DeskIntegration with incident managementIntegration with problem managementChange typesChange Request DescriptionAuthorized byExampleStandardCommon, accepted procedurePre-approvedResetting passwords, adding a security patch to a serverMinorLow impact, small amount of resources neededSenior team members, ManagersFixing a minor bug in an applicationSignificantPossible adverse impact, some risk, more resources needed to implementManagersInstalling a new software application requested by Business UsersMajorRisk of change adversely affecting users or infrastructure, major effort required to build and implementBusiness Unit headsReplacement of a production server running applicationsEmergencySignificant impact if not implemented immediately, requires quick decision makingTeam leaderA core router is malfunctioning and must be replacedVendorsReview and evaluation of vendorsThe following evaluation provides a means of assessing a vendor’s current performance. The vendor score consist of four sections each with a maximum score of 4. The maximum possible score is thus 16 and the vendor score is represented as a percentage of this maximum possible score.Each section scores as follows: (0) Unacceptable, (1) Low, (2) Average, (3) High and (4) ExceptionalThe four sections are: Support, Delivery, Operations and Financial and the criteria evaluated as described.SupportAssessment of service and support, respond to support calls on first contact, resolves issues during support calls, reports defects before customer discovers them, provides patches and fixes that work, and provides accurate documentationDeliveryAssessment of account team, provide clear points of contact for sales, support and service related issues, responds to questions in a timely fashion, understands company’s specific needs and requests.OperationsAssessment of technical quality, deliver products that perform as expected, deliver maintenance services that meet requirements, assessment of innovation, communicates information regarding new product timeframes, and provides unique technologies, features, capabilities.FinancialAssessment of procurement process, meets process deadlines, meets requested customization to product or service, estimates statement of work accurately, assessment of billing and reconciliation, deliver accurate invoices, resolves invoice discrepancies quickly.NameServices providedEvaluationRating (x%) ((a+b+c+d) / 12))SupportDeliveryOper.Fin.Maintenance WarrantyHandling Incidents and Troubleshooting proceduresThe Expanded Incident LifecycleIncidenthh:mmDetectedhh:mmDiagnosedhh:mmRepairhh:mmRecoverhh:mmRestorehh:mmWorkaroundhh:mmResolutionhh:mmOpportunisticKnownProgressService deskStakeholdersEscalation: Problem managementIT customersWorkaroundhh:mmResolutionhh:mmStakeholdersEscalation: Problem managementWorkaroundhh:mmResolutionhh:mmIT customersStakeholdersEscalation: Problem managementWorkaroundhh:mmResolutionhh:mmService deskIT customersStakeholdersEscalation: Problem managementWorkaroundhh:mmResolutionhh:mmHot ticketPotential majorDeclaration / planProgressNormal operationsHot lineNotification / feedbackService deskStakeholdersEscalation: Problem managementIT customersService deskStakeholdersEscalation: Problem managementReporthh:mmMetricsRiskOutageClass.AnalysisRiskOutageClass.RiskOutageService reviewMeetingsPrevious periodPerformance reviewCurrent issuesPeripheral issuesGrading of service desk interactionService desk interaction gradingReference: 55540470%ItemDescriptionPoints1Did the agent correctly greet the caller and identify themselves?☼2Was the IT customer shown empathy?☼3Was a reference number supplied?4Was the agent able to correctly identify the issue and service being used by the IT customer?☼5Was the interaction correctly recorded in the service desk database?☼6Was a suitable workaround supplied or alternatively correctly escalated?☼7Did the agent use language that was understandable to a business person?☼8Did the agent keep any commitments that were made9Was the interaction in conformance to the SLA time periods?10Was any value add information or assistance provide by the agent?☼Total Points7Grading of service desk escalation2nd line escalation gradingReference: 55561460%ItemDescriptionPointsClassification1User information correctly captured and logged☼2Configuration item correctly recorded and service identified3Type of call correctly assigned☼4Urgency, Impact and Priority correctly assessedDescription5Description within call is fully described and it understandable in business terms☼Actions6Detail added during expanded incident lifecycle7Regular updates and follow ups☼8Correct and detailed closure (escalation – SLA)9Correct technical documents attached (or described)☼Times10Start and end times recorded☼Total Points6Checklist for SOPHave you addressed all the following:WhoWhy?What?When?How?Where?AddendumService catalogueStandardsIBM Essential infrastructure standards table