Systemize Community Hub
Release Management
PMW provides the ability to manage the deployment of product changes to ensure a smooth transition from development to production.
Parallel Development
Multiple changes can be made against a single production model and be deployed at different times. The tool supports these changes being made in isolation of each other but ensures that all changes are consolidated, and none are lost, by out of sequence deployment.
Distributed Teams
Teams of individuals can work together in a Workgroup regardless of physical location. PMW ensures that visual modelling changes are reflected to all members of a team.
Ring fenced changes
Workgroups enable teams to work on different changes without impacting other teams by isolating the work carried out in one workgroup from the changes made in another.
Merge & Unmerge
PMW notifies teams that will be impacted by a change in a workgroup to be issued first. Workgroups can choose to merge those changes for testing purposes.
Version Control
PMW supports versioning of production product models, different development branches from different teams and provides history for multiple development revisions within a delivery team.
Modelling problems are reported real-time
to enable a Modeller to easily identify and fix model issues in a timely manner.
Changes are not overwritten
PMW ensures changes are not overwritten through any out of sequence issuances.
Testing/Training Evironment
Users are provided with a separate, secure, testing/training environment to support training of other team members and ensure there is no impact to any live production environment.
Licensing
PMW operates under an electronic license to ensure secure access to the corporate product data. Key company data cannot be taken and replicated in other environments that are out of the company’s control.
User roles
PMW has pre-defined roles to support users accessing the relevant functionality of the tool. PMW Administrators maintain a user’s account role. A user can be defined as either a Viewer, a Mapper, a Developer, a Modeller or an Administrator.
Audit trails
PMW provides an audit for the key transactions issued by Modellers.
Systemize IT Support
The creators of the PMW software provide a range of services to manage products more efficiently and bring them to market more quickly. These services include Consultancy, Product Modelling, Requirements Capture and Analysis, Solution Delivery, Knowledge and Skills Transfer.
Online problem reporting
An online reporting tool is provided for any issues that cannot be resolved locally. Access is provided to a shared area where any reported problem, from any customer, can be seen.
Support SLAs
As part of the PMW License, Systemize-IT provides predefined service level agreements for fixes and ensures individuals are kept informed at all stages.
Future upgrades
All software updates are provided as part of the annual PMW license.
Multi-user collaboration
PMW enables multi-user collaboration from across the various business areas.
Real time visual modelling
ensures that everyone working, at the same time, can see real-time updates to any impacted Product Model.
Modelled components are catalogued
All modelled components are catalogued and added to a repository for later reuse.
Filtering of products on specified types
of modelling component allows consumers to focus on specific areas of interest. For example, Developers interested in calculations, business people interested in the overall product structure without the detail, or implementers focused on deploying the rules etc.
Obsolete content filtered
ensures that Modellers only see what is relevant.
Drag & Drop
Drag & Drop modelling of existing components from the in-built repository maximizes consistency and saves time.
Copy & Paste
Copy & Paste functionality allows Parts, and any child elements within that Part, to be copied and new versions created for use within other products.
On-line
On-line Help is provided and updated in line with each software release.
New types of versioning criteria
New types of versioning criteria can be created. For example, locations, customer segments, sales channels, type of manufacturer (brands), etc..
New types of business data
New types of business data can be added to support new kinds of marketable products being created.
New types of modelling components
New types of modelling components can be created to aid the readability / understanding of the product components being modelled. For example, Benefits, Coverages, Riders, etc. can all be extended to support the terminology and product architecture used with the organisation.
User defined mapping structures
User defined mapping structures can be created to handle any level of mapping information being captured about how a modelling component relates to other information / systems in the organisation.
PMW models specifications for agreements
The specification of an agreement is a template for what can be agreed between two parties. For example, products for insurance agreements, intermediary agreements, reinsurance agreements etc.
Modelled using 'Lego-block' approach
Supporting a full component-based requirements gathering approach.
Reuse of prebuilt components
PMW ensures that parts are available for reuse across any marketable product offered by the insurance company. The tool minimises duplication with validation of the modelled content and name matching of existing content.
Usage-Based Modelling
Two aspects to any modelled change:
- The modelling of the component itself,
- The determination of where the change applies (the usage of the change).
Impact Analysis
Impact Analysis for changes made to product parts means that the Modeller is informed of the consequences of a change to the marketable products offered by the insurance company.
'Where Used' functionality
within PMW allows a user to easily and quickly identify where an item has been used in a Product Model.
Complete history
Versioning provides a complete history of how the Product models evolve over time (during the development phase and across different issuances to production).
Change impact causes new versions
As changes are made to parts within the product hierarchy, the impact causes new versions of the complete product model to be created.
Versioning of whole product trees and individual components
PMW allows versioning of whole product trees and individual components.
Comparison of whole product trees & different versions of Parts
PMW makes the comparison of whole product trees and different versions of Parts easy.
Product Specification Reports
Product Specification Reports are produced as a PDF™ file that readers can download and share with other users / business partners, who may not have access to PMW. The report is configurable to constrain content and filter on specific information.
Supports
The Product Specification Report also details the changes between development revisions and different production versions. This delta supports the iterative development approach supported by many of todays ‘agile’ approaches.
Export to Downstream Solutions
Export to Downstream Solutions through XML Exports to specific target solutions.
Export to Data Repository
Export to Data Repository for adhoc reporting requirements.
Record mappings from the product models to other sources of data
PMW provides a configurable means to record mappings from the product models to other sources of data, e.g. data warehouse mappings, legacy system mappings, web Service mappings etc.
Import of Enterprise Domain Model (in XML form)
PMW can import knowledge of the enterprise domain model (or target solution data model) and, with the ability to define data views on the imported model, provides a complete picture of the information associated with policies created on a specific product revision. PMW supports the ability to import models defined in a UML/XMI format.
Validation and management of navigation paths for input/output for rules and calculations
With the expected inputs/outputs defined for rules and calculations, PMW supports Modellers specifying (via drag&drop from the assembled product model) the location for data to be passed to a rule or calculation at runtime. PMW provides real benefits to development and testing by ensuring the required data is available in all models at model definition time (and not execution time).