Terry Gherman

Requests // Workflow in Action PUBLIC WEBSITE EMAIL or APP DESKTOP WEB REVIEW NOTIFICATION PRiM Requestor (Stakeholder) Interactions include: - Comments (custom or system notifications) - Files (FileData) RequestorID Encroachment Requests Class Location Decisions (Activities) DecisionID Interactions (activity stream) InteractionID ISSUE SUBJECT FORMS InteractionID High Consequence Area Pipeline Integrity ContactID InteractionID Endangered Species CROSSINGS WEBSITE Contact (Actors) WEB SUBMIT IDEAS FOR EXPANSION Environmental Issue Actors: Admins, Engineers, users per dept. Worker Safety Requestor (web credentials) = Contact (Requestor) ContactID Issue Relations EventID IssueID FeatureID Type IssueID ContactID Type IssueID ContactID Type Emergency Response Feature Which Features are effected by this Request? Customer Relations Admin connects Requestor’s Stakeholder ID to the Event A requestor cannot search for Stakeholders so web credentials are used for creating the first event PersonContacted Crossing Request IssueJEngagement Issue IssueID Engagement EngagementID Type To support the many types of Issues, along with each Issue’s disparate attributes, custom forms are built for each type. Type chosen dictates the form type that is used. Event To support complex Issues, multiple forms could be related to one Issue gather additional information. Type chosen dictates the workflow schema that is used FeatureID EventID Crossing Layer (Feature) Workflow Engine Schema Activities Transitions Actions Existing CORE Schema 1. see full CORE Schema for how Stakeholders are connected to Events 2. see full CORE Schema for how Parcels are connected to Events Actors Commands Timers How a Issue like Crossings connects. CLIENT–SPECIFIC CUSTOMIZABLE FORMS The Workers Who is resolving the request? GROUP ROC FORM The Event Why was the request started? The Requestor Who made the Request? This is an Issue Interest User (Actor) Where the Issue is located. InterestID UserID WEB FORM Event EventID InterestID Interest InterestID StakeholderID Stakeholder StakeholderID InterestID Interest InterestID FeatureID Feature InterestID IssueID OTHER APP FORMS Issue Issue Subject each Issue Subject record has one corresponding Issue IssueID SubIssueID IssueType Issue Type chosen dictates the workflow schema that is used Workflow Engine Schema Diagram E: CURRENT ROC MODEL CURRENT ROC STATIC FORM includes field only for a Purpose of Engagement (Engagement Type) S S S S InF InF F E E Event (Why?) S F Feature (Where?) I Events begin with why an engagement is needed. Features are where an Event or Issue is located. S S S S S S S InE I I I I I I I Stakeholder (Who?) Interest InF Feature Interest Table (Type = LO, LR, RO, RR) Issue Interest InE Event Interest Table (Type = Event) Stakeholders are who is met or reports an Issue. (What?) Issues are what is resolved using Events and Interactions. S InF F Group ROC S S Diagram F: ISSUE RESOLUTION MODEL CUSTOMER SPECIFIC DYNAMIC MODEL FORMS each connects to a Purpose of Engagement (Engagement Type) S S S S S S ENGAGEMENT TABLES Basic ROC InF S OPEN S U U S S U Ix Ix Ix Ix Ix Ix Ix Ix RESOLUTION TIMELINE I F Public Awareness Program U InF InI Group ROC S U E Project Engagement InE S S Damage Claim I Emergency Response S S I InI Notice of Hearing U F Web Forms + all other engagements OPEN S U Ix Ix S U U Ix Ix Ix RESOLUTION TIMELINE Each of these tables is designed to meet customer specific field attributes requirements. E Event (Why?) S F Feature (Where?) I Events begin with why an engagement is needed. Features are where an Event or Issue is located. Stakeholder (Who?) Ix Issue Interest InE Event Interest Table (Type = Event) Stakeholders are who is met or reports an Issue. (What?) Issues are what is resolved using Events and Interactions. Interaction (How?) Interactions communicate how Issues are resolved. Interest InI Issue Interest Table (Type = Issue) Interest InF Feature Interest Table (Type = LO, LR, RO, RR) CLOSE CLOSE Diagram G: GROUP ISSUE RESOLUTION MODEL TIMELINE RESOLUTION GROUP ISSUE MODEL S OPEN S S S S S Basic ROC InF S U Ix Ix Ix RESOLUTION TIMELINE GROUPED I InI ENGAGEMENT TABLES Ix U InF U Group ROC F Public Awareness Program E Project Engagement S InE GROUP InI GI InI I S Damage Claim OPEN SS S U Ix Ix SS S U SS S U Ix Ix Ix Ix RESOLUTION TIMELINE I Emergency Response Notice of Hearing Web Forms U + all other engagements F Each of these tables is designed to meet customer specific field attributes requirements. OPEN E Event (Why?) S F Feature (Where?) I Events begin with why an engagement is needed. Features are where an Event or Issue is located. S U Ix Ix RESOLUTION TIMELINE Stakeholder (Who?) Ix Issue Issue (What?) GI Group Group Issues combine Issues for group Interactions. Stakeholders are who is met or reports an Issue. (What?) Issues are what is resolved using Events and Interactions. Interaction (How?) Interactions communicate how Issues are resolved. GROUPED Interest InI Issue Interest Table (Type = Issue) Interest InF Feature Interest Table (Type = LO, LR, RO, RR) Interest InE Event Interest Table (Type = Event) CLOSE