Incident and change processes with vendors
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
align incident and change processes between Larkspur and its vendors.
Planned topics
- Contracts set vendor response and resolution targets; Larkspur's internal severity levels need to map to them.
- Joint incident process: who declares, who communicates, the bridge call, evidence sharing, review.
- Change: vendors' release calendars and maintenance windows must feed Larkspur's change calendar.
- Test vendor escalation before you need it.
Draft outline details
Demonstration
a table mapping Larkspur severity 1-4 to vendor priority levels and response targets, plus a change-calendar overlay for the payment, CRM, and ERP vendors.
Check your understanding
Why map severity levels to vendor priorities?
Show answer
So a Larkspur severity-1 incident gets the vendor's fastest response, with no argument during the outage.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.