Incidence-Driven Analysis Workflow

AIM periodically polls the archive location for incident and intelligence information and displays the information for a single point of management in Incident and Intelligence Manager. The AIS incident-driven workflow occurs as follows (see Figure 5):

Figure 5: AIS Incident-Driven Workflow

:

1. A trigger event occurs and is detected on a device configured for and running AI-Scripts. An AI-Script is executed.
2. A tailored AI-Script builds a incident Juniper Message Bundle (JMB) with event and router data, and sends it to a designated AIM archive location.
3. AIM receives the incident JMB and displays it in Incident Manager. The incidents owned or flagged to a user displays in My AIM Home.
4. If the customer is enrolled in the AIS Base Service (Incident-Driven Online Service), incidents case IDs can be requested from JSS from Incident Manager to open a case with all relevant information for resolution.
5. JSS creates a case. Any attachments are uploaded from AIM to JSS.
6. JSS returns a case ID to AIM.
7. JSS engineers work on the case and reports case status to AIM.

For more information about using Incident Manager, see Using AIM Incident Manager.