OFN Incident Workflow

Author: Paddy Murphy

The OFN Incident Workflow is used for OFN (Optical Fiber Networks) tickets and open imported iNOC tickets.

• Start state: New OFN Incident
• End state: Resolved Auto Close

Different forms are added depending on the type of OFN Ticket created; currently there are three different types. Logic for form addition is in the 'New OFN Incident' groovlet.

NetAce Auto Ticket - API POST - Ticket created by netace_auto

• OFN SNMP Trap
• OFN Information Form

Netace Manual Ticket - API POST - Ticket created by netace_manual

• OFN Information Form

IDMS Manual Ticket - Manually created in Ticketer by any user

• OFN Incident Report Form

OFN NOC Form added

OFN Field Tech Dispatch Form added

OFN RFO Form added

If an OFN ticket is in the “OFN Incident Resolved” or “RFO Issued” state for 24 hours is is automatically moved to the “Resolved Auto-Close” state. Logic is in the “OFN Auto Close” groovlet.

This form uses the new Ticketer tree component. Entity tree “Data Groovlet” populates the tree components and assigns labels. Default label name is Unknown,if a label has Unknown the information is not available. The tree component groovlet populates the Entity Field. Clicking on a label displays the relevant data.

The “OFN NOC Form” gathers general information that is common to all issue types. An additional “OFN Issue ..” form is added When the “OFN NOC Form” is saved; the logic for this is in the “OFN NOC FORM” on save groovlet. The following forms should be added when an issue type is selected are:

• Alarm Trap - No form added
• Hard Down - OFN Issue Hard Down
• Bounce - OFN Issue Bounce
• Errors - OFN Issue Errors
• Low Light Levels - OFN Issue Low Light Levels
• High Latency - OFN Issue High Latency
• IP related - OFN Issue IP related

The RFO (Reason for Outage) is used to gather information about the outage. The resolution drop down lists are dynamically populated depending what is chosen in the previous drop down list. The “RFO Root Cause” field is automatically populated depending on what resolution values are selected.This information in this form is used to generate a “OFN Reason for Outage” email.

The OFN email templates use the new iterated email feature; the Iterated email checkbox is used to enable this. It allows the relevant customers to be informed about their services that are impacted. The “Iterated Template Data” field must be filled in to use this feature; this returns a list of customers and what effected elements. The iterated email uses a customer to identify what services are impacted. As there is a potential for an issue to affect hundreds of customers an Aysnc Email feature was developed. Emails are queued in RabbitMQ before sending. This feature is enabled using the “Async Alarm” checkbox.

The affected customers can be viewed in the email preview recipients dropdown list. If there are no customers assigned the fallback email address is used; a user can change this before sending email.

We now have the ability to design email templates using HTML & CSS. OFN email templates use the OFN style. A new style can be added in Ticketer Admin using the “Email Styling Admin” controller. See example ONF email template preview above.

ExteNet QA Netace API