Sapiens DECISION is majority owned by Sapiens International Corporation (NASDAQ & TASE: SPNS). We operate exclusively within the financial services sector, working with global organizations across the insurance, capital market, corporate and retail banking sectors.
Enterprise Business Decision Management Suite
Changing the way business makes decisions
Sapiens DECISION is a technology company that is leading the movement to digitally transform business operations by managing business logic with its decision management platform.
Features and Benefits
|Simplify Business Process Models||
Remove declarative information from business process models, and model them independently, leading to cleaner processes that are easier to maintain.
|Author once and run anywhere||Enjoy maximum freedom when it comes to authoring Business Logic to current and/or future execution environments. Once captured and tested, it can be authored to leading Business Rules Engines, or to the Sapiens DECISION Execution Server, Java libraries or custom SDK.|
|Know when you are done eliciting Business Logic||A top-down modeling approach to capturing Business Logic helps Business Analysts capture all relevant aspects related to each business decision worth-while to managing.|
|Business-friendly Glossary||Each community may have a glossary of terms (called fact type in Sapiens DECISION), and/or it may inherit glossary fact types from communities in the hierarchy. The fact types in the glossary is used to construct the logic used in the decision models, and each fact type in the glossary is supported by extensive meta data; the fact types in the glossary may be mapped to underlying data model(s), which provides the basis for Sapiens DECISION ability to translate the decision models into code.|
|Change Management and Traceability||Sapiens DECISION provides a comprehensive versioning for every asset under management – fact types, rule families, decisions, decision flows. No asset can be instantiated into the repository without a change request; there are two aspects of every change request in the system – the external request into the system (called a Business Change Request (BCR)), which may be for a minor change to a trivial piece of logic, or may encompass an entire program of change across the enterprise, or a single project), and the related internal change (Business Change Document (BCD)) that assigns work arising from a BCR into one or more BCD tasks. There can be many BCDs per BCR, and many BCD tasks per BCD. Every version is directly traceable to a BCD tasks, every BCD task is traceable to a BCD, and every BCD is traceable to a BCR, which in turn is traceable to external change documents. Every asset in the repository is traceable to every other asset related to it, including at the version level. Navigating across the repository to related assets is made easy through the links embedded in every asset throughout the modeling environment.|
|Testing||Sapiens DECISION has a comprehensive testing facility to enable the modeler to build and save test cases, and can auto-generate, on demand, large numbers of test cases. The tool is able to run the test cases and visually depict the test results. The tools graphical compare feature enables to the modeler to understand the result variations from multiple test executions, and do what-if case analysis of the logic. Thus comprehensive testing of the logic to be performed by the modeler before the assets are approved or moved into the deployment environments. The test cases generated by the testing module are also able to be used in the deployment environments for UAT testing.|
|Leverage a technology independent enterprise Busines Logic repository||Capture Business logic, organize and maintain in an enterprise-wide repository that allows maximum re-use regardless of the execution environment(s).|
|Stay in control of your content with strong governance||Proof regulatory compliance to non-technical audiences by exposing lineage of regulations and policies with rules that are executed in the various execution environments.|
|Federated repository for Business Logic||
The repository is federated (i.e. divided up into) Communities, so that the logic assets (the decisions, rule families, fact types, decision flows, etc.) can be divided between segments representing organizational elements. Each Community may have its own default settings, access rights, and user access rights and groups; communities are structured in a hierarchical fashion, so that they may inherit from higher communities. Within each community there are folder structures to further organize the assets of the repository. Communities may be structured to model the organizational or the process structure of the enterprise, or in fact both. The community schema enables Sapiens DECISION to manage logic across very large enterprises without compromise.
|Visual Decision Model Workbench||
This is the modeling environment of the tool where the modeler creates the decision models, the rule families, the flows and the fact types, and where the modeler may launch testing of the model. The workbench provides the modeler with every facility to traverse through the repository to any assets that is related to the assets of interest through the tools powerful linking and querying features. The modeler also has access in the modeling environment to third party tools that are integrated with Sapiens DECISION from within the models, for example to open process models within which the decision logic may be executed. The tool provides extensive validation and guidance in modeling the logic, ensuring that no asset is submitted by the modeler for approval without being validated against the principals of The Decision Model (TDM) in order to ensure that no models enter the repository with conflicts, gaps, or inconsistencies in the logic.
|Automatic Logic Validation||
Every piece of logic entered into the modeling environment is required to be validated at two levels by the system before it can be approved for versioning and submitted from the whiteboard (the working environment ) for approval to be placed into the repository. The two levels are at the rule family level (row, column and family logic), and at the decision level. The logic is validated against the 15 principles of The Decision Model (TDM), and the tool also provides the modeler with help and guidance in forming the some of the logic patterns.
|Deployment||One of the most distinctive of Sapiens DECISION’s many unique capabilities is its ability to transform the models in the repository into executable code. In fact not only can it do this, but it can build the code into fully deployable modules, directly into target execution environments. The transformation is performed by adapters, which support a wide range of business rules and procedural languages including IRL, Blaze, DRL and object Oriented languages such as Java (POJO). In addition, Sapiens Decision provides an Software Development Kit (SDK) that enables the user to develop their own adapters for languages that are not supported. Thus Sapiens DECISION can be fully integrated into the development cycle, where the business logic within the business requirements may be authored, then automatically generated directly into their target business systems. This dramatically collapses time, cost and risk of developing business systems.|
|White Paper||A Primer on The Decision Model|
|White Paper||Decision Modeling Methods|
|White Paper||System Transformation: Be Careful or You Will Not Get What You Asked For|
|White Paper||We already have a Business Rules Management System|
|White Paper||Adapting to Transformative Change|
|White Paper||Adapting to Regulatory Change|