Organizational Workflow Diagram

From GM-RKB
Jump to navigation Jump to search

An Organizational Workflow Diagram is a process model of an organizational workflow (where each step follows without delay or gap and ends just before the subsequent step may begin).



References

2021

  • (Wikipedia, 2021) ⇒ https://en.wikipedia.org/wiki/workflow Retrieved:2021-6-16.
    • A workflow consists of an orchestrated and repeatable pattern of activity, enabled by the systematic organization of resources into processes that transform materials, provide services, or process information. It can be depicted as a sequence of operations, the work of a person or group, [1] the work of an organization of staff, or one or more simple or complex mechanisms. From a more abstract or higher-level perspective, workflow may be considered a view or representation of real work. [2] The flow being described may refer to a document, service, or product that is being transferred from one step to another. Workflows may be viewed as one fundamental building block to be combined with other parts of an organization's structure such as information technology, teams, projects and hierarchies.
  1. See e.g., ISO 12052:2006, ISO.org
  2. See e.g., ISO/TR 16044:2004, ISO.org

2021

  • (Wikipedia, 2021) ⇒ https://en.wikipedia.org/wiki/workflow#Examples Retrieved:2021-6-16.
    • The following examples illustrate the variety of workflows seen in various contexts:
      1. In machine shops, particularly job shops and flow shops, the flow of a part through the various processing stations is a workflow.
      2. Insurance claims processing is an example of an information-intensive, document-driven workflow.
      3. Wikipedia editing can be modeled as a stochastic workflow.
      4. The Getting Things Done system is a model of personal workflow management for information workers.
      5. In software development, support and other industries, the concept of follow-the-sun describes a process of passing unfinished work across time zones. [1] # In traditional offset and digital printing, the concept of workflow represents the process, people, and usually software technology (RIPs raster image processors or DFE digital front end) controllers that play a part in pre/post processing of print-related files, e.g., PDF pre-flight checking to make certain that fonts are embedded or that the imaging output to plate or digital press will be able to render the document intent properly for the image-output capabilities of the press that will print the final image. # In scientific experiments, the overall process (tasks and data flow) can be described as a directed acyclic graph (DAG). This DAG is referred to as a workflow, e.g., Brain Imaging workflows. [2] [3] # In healthcare data analysis, a workflow can be identified or used to represent a sequence of steps which compose a complex data analysis. # In service-oriented architectures an application can be represented through an executable workflow, where different, possibly geographically distributed, service components interact to provide the corresponding functionality under the control of a workflow management system. [4]
      6. In shared services an application can be in the practice of developing robotic process automation (called RPA or RPAAI for self-guided RPA 2.0 based on artificial intelligence) which results in the deployment of attended or unattended software agents to an organization's environment. These software agents, or robots, are deployed to perform pre-defined structured and repetitive sets of business tasks or processes. Artificial intelligence software robots are deployed to handle unstructured data sets and are deployed after performing and deploying robotic process automation.

2021



  1. Follow-the-sun process
  2. Brain Image Registration Analysis Workflow for fMRI Studies on Global Grids, Computer.org
  3. A grid workflow environment for brain imaging analysis on distributed systems, Wiley.com
  4. Service-Oriented Architecture and Business Process Choreography in an Order Management Scenario: Rationale, Concepts, Lessons Learned, ACM.org