LSPS is one of the most advanced BPMS available today. The possibilities are quite literally limitless due to the power, flexibility and intelligence built into the tool set allowing any business to bring their business processes to life.
But advanced does not mean complex. With 100% model-driven design, simple processes can be created, tested and deployed in minutes. When skilled developers wish to dig deeper, the Eclipse IDE and rich Java support ensures that applications can be tuned to very specific requirements.
With full support for standard BPMN, an existing model can be imported or designed in the tool, then automated with simple execution semantics, data integration and form design. Going a step further with Goal-Oriented BPMN, flexible business-driven processes can be built that are ideal for case-driven scenarios and where real-time analytical improvement of processes is a target.
The combination of classic BPMN and Goal-Oriented BPMN modeling allows the native creation of
- Conventional BPMN models
- Flexible Goal-Oriented BPMN models
- Dynamic/Adaptive Case Management models
Perfect for Integration
LSPS can be licensed and used to design and deploy complete process-driven solutions as any other BPMS, but what places LSPS into another league is its integration capabilities allowing independent software vendors (ISVs) to embed the LSPS engine within their own product offering.
With comprehensive support for web-layer, api-layer, and data-layer integration, LSPS is the perfect option to augment your software product with BPM capabilities.
Take a look at this example OEM customer case for more information.
A core facet of LSPS is goal-oriented intelligence. Every business has goals it wishes to achieve and/or maintain, and whether they are strategic or operational, goals can always be associated with at least one process sequence present within the business environment. LSPS allows these business goals to be directly represented within process models and to then be used to drive, track, and optimize process automation in real-time.
Goals can be used to represent business objectives, key performance indicators, resource management, user preferences, and much more. Moreover, as they can be used in every step from process concept to execution, it offers a key point of alignment and agreement for all stakeholders. This helps to strengthen collaboration and trust between business managers, analysts, IT specialists, and process users.
How does it work?
LSPS supports goal-oriented process modeling with GO-BPMN, an extension of the OMG standard Business Process Modeling Notation BPMN. Goal-Oriented BPMN enhances standard BPMN by allowing the process analyst to separate governance (goals) from procedure (plans): Goals describe what a process will do in terms of milestones and performance goals, while plans are modular snippets of workflow that describe the various ways in which each goal can be achieved.
The goal-oriented model allows the implicit specification of multiple agile paths to achieve a goal or combined goals. There are frequently several paths to achieve a process goal. Each path has a scenario in which it is the optimal solution. When multiple plans are available to achieve a goal, or combination of goals, the LSPS Process Engine dynamically creates an execution path that considers which plan alternatives are best suited to actual or changing business conditions. This results in the optimization of every business process in real-time.
What can it be used for?
Goal-Oriented model design provides native support for both structured and unstructured, case-oriented processes. Structured processes can benefit from the use of goals to align business objectives with the activity sequences that may used to achieve them. If flexibility is possible in the selection of an activity, then goals can also help optimize that choice according to key performance indicators.
Case-oriented processes are particularly well suited to goal-oriented design, as every case has a defined purpose and one or more work items that must be performed to complete the process. As work items and the particular methods to achieve them may not be defined in advance, the case process itself, or its owner, must determine when the purpose, or goal, has been reached. For example, a bank client-opening process will require compliance checks, but which checks are required and in which order will change over time according to the profile of the applicant. The goal remains the same, but the method can change for each instance of the process.
Powerful Web-Form Screenflow
LSPS has an integrated model view for designing both simple and complex Web forms and screenflow. Forms are bound to process activities and to the business data they utilize. They are then generated in real-time during process automation, meaning that their layout and content can change dynamically according to the current execution context.
A comprehensive library of form elements, spanning all commonly used input types and including secure fields, charts, and more, is available. Field validators are provided, as is field parameterization that allows the presence and location of a field on the form to by dynamically determined according to a variety of factors including context, user, rights, location, etc.
Some examples of model generated forms: