Workflow Management Tool Support for Incident Command Systems

2006 ◽  
Author(s):  
M. Stoute ◽  
Jiacun Wang ◽  
D. Rosca ◽  
W. Tepfenhart ◽  
A. Milewski
Keyword(s):  
Workflow Management ◽  
Management Tool ◽  
Tool Support ◽  
Incident Command ◽  
Command Systems

Compiling Business Process Models into Executable Code

2011 ◽  
pp. 218-337
Author(s):  
Cesare Pautasso
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Workflow Management ◽  
Workflow Engine ◽  
Process Models ◽  
Management Tool ◽  
Business Process Models ◽  
Model Driven ◽  
Java Bytecode ◽  
High Level

Model-driven architecture (MDA), design and transformation techniques can be applied with success to the domain of business process modeling (BPM) with the goal of making the vision of business-driven development a reality. This chapter is centered on the idea of compiling business process models for executing them, and how this idea has been driving the design of the JOpera for Eclipse workflow management tool. JOpera presents users with a simple, graph-based process modeling language with a visual representation of both control and data-flow aspects. As an intermediate representation, the graphs are converted into Event-Condition-Action rules, which are further compiled into Java bytecode for efficient execution. These transformations of process models are performed by the JOpera process compiler in a completely transparent way, where the generated executable artefacts are kept hidden from users at all times (i.e., even for debugging process executions, which is done by augmenting the original, high level notation). The author evaluates his approach by discussing how using a compiler has opened up the several possibilities for performing optimization on the generated code and also simplified the design the corresponding workflow engine architecture.

ICS CONTRIBUTES TO THE NORTH CAPE OIL SPILL RESPONSE1

1997 ◽  
Vol 1997 (1) ◽  
pp. 737-742
Author(s):  
LT Tina M. Burke ◽  
LT John P. Flynn
Keyword(s):  
Oil Spill ◽  
Management System ◽  
Lessons Learned ◽  
Coast Guard ◽  
Management Tool ◽  
Incident Management ◽  
Incident Command System ◽  
Incident Command ◽  
The North ◽  
Oil Spill Response

ABSTRACT In recent years, the usefulness of the incident command system (ICS) has received much attention. Much of the oil industry and several government agencies involved in all types of emergency response have been using ICS for many years. In addition, the U.S. Coast Guard formally adopted the national interagency incident management system (NIIMS) ICS as the response management system of choice in February of 1996. The response to the tank barge North Cape grounding was a complex multiagency effort that brought with it many of the issues and problems responders face when dealing with crisis situations. This paper describes the ICS-based organization that was established to respond to the major North Cape oil spill, analyzes the organization compared to standard ICS, and discusses how the ICS framework and principles contributed to the success of the response. It also explains how closer conformity to standard ICS could have remedied many of the issues that later surfaced as lessons learned, resulting in improved response efficiency. The North Cape response provides a vivid example of how ICS is a helpful management tool that, if rigorously learned and applied in a widespread fashion, can greatly enhance the nation's oil spill response posture.

A workflow management tool for laboratory medicine

1998 ◽  
Vol 33 (3) ◽  
pp. 183-197 ◽  
Author(s):  
H.M.J. Goldschmidt ◽  
J.C.M. de Vries ◽  
G.G. van Merode ◽  
J.J.M. Derks
Keyword(s):  
Workflow Management ◽  
Laboratory Medicine ◽  
Management Tool

A Static Change Impact Analysis Approach based on Metrics and Visualizations to Support the Evolution of Workflow Repositories

2016 ◽  
Vol 13 (2) ◽  
pp. 74-101
Author(s):  
Gustavo Ansaldi Oliva ◽  
Marco Aurélio Gerosa ◽  
Fabio Kon ◽  
Virginia Smith ◽  
Dejan Milojicic
Keyword(s):  
Impact Analysis ◽  
New Technology ◽  
Workflow Management ◽  
The Body ◽  
Analysis Approach ◽  
Tool Support ◽  
Change Impact Analysis ◽  
Support Organizations ◽  
Change Impact ◽  
The Impact

In ever-changing business environments, organizations continuously refine their processes to benefit from and meet the constraints of new technology, new business rules, and new market requirements. Workflow management systems (WFMSs) support organizations in evolving their processes by providing them with technological mechanisms to design, enact, and monitor workflows. However, workflows repositories often grow and start to encompass a variety of interdependent workflows. Without appropriate tool support, keeping track of such interdependencies and staying aware of the impact of a change in a workflow schema becomes hard. Workflow designers are often blindsided by changes that end up inducing side- and ripple-effects. This poses threats to the reliability of the workflows and ultimately hampers the evolvability of the workflow repository as a whole. In this paper, the authors introduce a change impact analysis approach based on metrics and visualizations to support the evolution of workflow repositories. They implemented the approach and later integrated it as a module in the HP Operations Orchestration (HP OO) WFMS. The authors conducted an exploratory study in which they thoroughly analyzed the workflow repositories of 8 HP OO customers. They characterized the customer repositories from a change impact perspective and compared them against each other. The authors were able to spot the workflows with high change impact among thousands of workflows in each repository. They also found that while the out-of-the-box repository included in HP OO had 10 workflows with high change impact, customer repositories included 11 (+10%) to 35 (+250%) workflows with this same characteristic. This result indicates the extent to which customers should put additional effort in evolving their repositories. The authors' approach contributes to the body of knowledge on static workflow evolution and complements existing dynamic workflow evolution approaches. Their techniques also aim to help organizations build more flexible and reliable workflow repositories.

Equity and Disasters: Reframing Incident Command Systems

2021 ◽  
Vol 111 (5) ◽  
pp. 844-848
Author(s):  
Eric Goralnick ◽  
Richard Serino ◽  
Cheryl R. Clark
Keyword(s):  
Incident Command ◽  
Command Systems

scholarly journals 4575 Implementing a Workflow Management Tool for Clinical Trials

2020 ◽  
Vol 4 (s1) ◽  
pp. 32-32
Author(s):  
Laura Nelle Hanson ◽  
Jennifer Weis ◽  
Sasa Andrijasevic ◽  
Sharon Elcombe ◽  
Rachel Hardtke ◽  
...  
Keyword(s):  
Mayo Clinic ◽  
Medical Center ◽  
Academic Medical Center ◽  
Workflow Management ◽  
Management Tool ◽  
Trial Management ◽  
Additional Time ◽  
Start Up ◽  
Study Staff ◽  
Study Process

OBJECTIVES/GOALS: A workflow management tool is essential in order to help support consistent processes with transparency in next steps of the study process. Prior to this tool, staff has relied upon extensive training and coaching on the study process. While resources and guidelines exist, it requires additional time for staff to identify these resources and allows for confusion and rework. Implementation of a systematic workflow management tool was identified as a critical need in order to support streamlined processes, improve transparency and support business continuity, and to accelerate the study process. METHODS/STUDY POPULATION: This effort was undertaken as part of the Protocol Lifecycle Management effort to implement a comprehensive clinical trial management system for clinical research studies. Mayo Clinic has designed a workflow management tool within the Velos eResearch system. The workflow manager is dynamic and will present specific activities based on the study design and responses to data entered on the ad hoc forms. A Workflow Build group contributed to the design of the workflow in order to reflect appropriate, current operational processes. The workflow was vetted and validated with research teams. In addition to designing activities, planned dates and target timelines were established for relevant workflows to help promote transparency in the study start-up timelines and allow study staff to identify overdue activities. Study status controls were designed in the workflow to protect study staff from inadvertently changing the status until appropriate activities are complete. RESULTS/ANTICIPATED RESULTS: A dynamic workflow has been designed and implemented in the Velos eResearch system to support Mayo Clinic research sites. This system will be implemented February 24, 2020 to all consenting studies. DISCUSSION/SIGNIFICANCE OF IMPACT: The implementation of this workflow management tool is critical to help support research operations in a large, academic medical center. Benefits to implementation are expected to include improved transparency in the study status and next steps, reductions in rework due to confusion in next steps, better understanding from new staff in the appropriate study process, and improved timelines for study start-up. As we prepare for the implementation of the Velos eResearch system at Mayo Clinic, the workflow management tool has been identified in training sessions as a positive benefit.

Sign in / Sign up

Export Citation Format

Share Document