<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Changing In-Flight Business Processes Using PNMsoft's HotChange® Technology</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Eli Stutz</string-name>
          <email>elis@pnmsoft.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Head of Knowledge</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Collaboration</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>PNMsoft</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>James Luxford</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>PNMsoft</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>PNMsoft Ltd.</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>Customer Service, HR Processes, Financial Processes, Quality Assurance and Tax Compliance.</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Governments, Ministries, Departments and Agencies. Processes include Customer Onboarding</institution>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2014</year>
      </pub-date>
      <abstract>
        <p>PNMsoft Sequence is an iBPMS (Intelligent Business Process Management Suite). This demonstration will show how PNMsoft Sequence's HotChange® technology enables BPM customers to change processes which are already being run in the production environment. HotChange® enables modifications to all aspects of a process including: flow, business rules, form fields, new activities, permissions, devices, and integration with external systems. Customers using HotChange® are better able to compete, as they can more quickly adapt their business critical processes to real world conditions and a changing marketplace. This demo will be of major interest to attendees interested in Process Improvement, Change Management and Intelligent Business Operations.</p>
      </abstract>
      <kwd-group>
        <kwd>PNMsoft's Sequence Kinetics is an Intelligent Business Process Management Suite (iBPMS)</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Maturity</title>
      <p>elements such as webforms, messages and integration activities. A UX Studio enables rapid
creation of web forms which are used in Sequence Kinetics workflows. End users operate processes
in Flowtime, Sequence Kinetics’s SharePoint Runtime interface. Employees and managers can
also operate and monitor processes in ProcessTO GO, Sequence’s mobile BPM environment.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Significance to the BPM Field</title>
      <p>Sequence Kinetics® is built on PNMsoft’s unique HotChange® technology. Like the concept of
HotSwap for controlled change of hardware components of high-end servers without any
downtime, so too is HotChange ® for BPM Software. Super users can reconfigure instances of
business processes and introduce changes. New instances will be initiated without causing major
disruption to the business. Sequence Kinetics HotChange ® technology permeates all levels of
our platform providing the ability to modify, integrate and distribute their business process
applications without having to halt these processes as they continue to run in production, yet
maintain full governance and control of the change deployment. Once a change to a process has
been made, the super user has the option to either apply to inflight processes, or leave running
processes with their previous version (multiple active versions in runtime).3 We will
demonstrate the following features and aspects of HotChange ® in our demo.
2.1</p>
      <sec id="sec-2-1">
        <title>The HotChange® Sweet Spot</title>
        <p>Organizations will a high frequency of business process change, and a high level of Human
collaboration on processes will benefit most from HotChange ®.
2.2</p>
      </sec>
      <sec id="sec-2-2">
        <title>Trend of Business Change</title>
        <p>We observe a higher frequency of process change among our clients (10% - 15% increase in
number of process changes per year). There is also an increasing need for control over business
processes, to comply with regulation and other control mechanisms. In 2013 and 2014, 15%
20% of our clients’ processes were related to compliance as compared to 10% in past years.
To answer the need for both change and control, HotChange® includes Change and Control
layers:
A workflow can be rewound to a predetermined time without rewinding content and history.
Each user activity can be defined as having rollback enabled, or disabled, with customisable
rollback notifications and recipients. This feature can help users correct procedural mistakes.
2.4</p>
      </sec>
      <sec id="sec-2-3">
        <title>Versioning</title>
        <p>HotChange ® technology and in memory execution promotes ease of change. Admins can
manage as many versions of a process as they require and maintain control of these versions.
Admins can control which version is live at any point in time without halting or interfering with
existing instances of the process. Sequence Kinetics provides a wizard-based tool to transfer
version between environments. Using HotChange ®, organizations can significantly cut down on
the overhead due to process changes, especially as the number of processes and changes
increase.
A client in the Utilities industry has an existing service delivery process which enables a service
agent to reach a client location, assess his utility requirements, and complete an online form
which starts a provisioning sub-process to provide the service. Some of the problems with this
process include difficulty in finding the location, completion of the provisioning form on mobile
device, and also changing government regulation regarding safety issues. We will demonstrate
how HotChange® enables the company to adapt to these conditions without removing the
process from production, creating a mobile enabled process that uses Google Maps, and can be
modified to fit government regulations.</p>
        <p>Specifically, the demo will show how mobile forms can be created using the same data source in
one click, and how integration with rich media such as Maps can be quickly added to forms with
very little client side coding. We will show examples of how changes to the process rules due to
new regulation can be made without “derailing” the process. The demo will also show how a
standard BPM suite without HotChange® technology would take several times as much time to
cope with the number of changes to the process, integration and devices, which a comparison
of resolution times between both solutions.</p>
      </sec>
      <sec id="sec-2-4">
        <title>Business Benefits</title>
        <p>HotChange® provides the following benefits for organizations with high frequency of change:
 Rapid, cost-effective automation of mission critical processes.
 Accurate and rapid migration of existing processes.
 High flexibly to meet changing business needs.
 Better visibility for management with visual dashboards and reports.
 Ability to integrate key processes with other business systems.
 Ability to optimise and improve processes over time.
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Screencasts</title>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>