Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Business rules management is a feature of Framework ECM that compares one or more fields against each other to enforce the full and complete capture of required data. The business rules functionality was developed to ensure jobs do not move forward through the system without having key dates and information entered. These dates and information are determined by the business and rules are created accordingly.

Benefits Of Business Rules Management

Business rules are typically used to compare two or more dates against each other. The design of the rules are usually that field A must occur before field B (e.g., Soil Report Ordered must occur before Soil Report Received). Business rules are not restricted to simple date field pairs. They can be designed to enforce the selection of an entity from a popup list, the selection of Yes or No Boolean fields, as well as a range of other fields used in Framework ECM.

Designing and implementing business rules ensure that jobs move through the system only once they have satisfied the minimum captured data requirements and ensure that activities are being completed in the correct order. This promotes a high level of data integrity and consistent and accurate reporting.

What To Do

Requirements

Before designing and implementing business rules there are a couple of things that should be in place:

  • If customised Framework ECM Overview screens (Pre-Administration, Administration, Construction & Maintenance) are in use, the rules should be designed based on the organisation's specific business processes.
  • Which staff member(s) will have the ability to override the business rules if the need arises. Typically a department manager would have the ability to override business rules if the exception meant that meeting the rule would be misleading or inappropriate. Other staff would need to make a compelling case in order to override the rules. This practice ensures that the integrity of the data is maintained.

Planning

Before implementing business rules, all staff members in the company should be notified that a change is being implemented. They should be provided with an explanation of what the business rules will do, why they are being put in place, and a firm date when they will be switched on.

The initial phase of the implementation should consist of all staff members having the ability to override the business rules. This will educate the staff of the rules that they are currently breaking and the types of messages they will see without preventing them from doing their job.

Once the initial phase is in place, all staff members should be notified that the ability to override the business rules will be switched off after a specified period. They should be given a firm date where they will no longer be able to override the rules and the instructions/procedures for speaking to a manager if they feel they need to override a rule after this date. It is likely that there will be data in the system that doesn't adhere to the new rules, these jobs will need to be back filled or run out once business rules are switched on.

Implementation

Business rules should be implemented gradually. It is best to switch on the rules for one department or major work flow stage at a time, starting with pre-administration and administration. Once satisfied that this area is set up correctly and the staff issues are solved, move on to the construction stage.

Due to the nature of the Business Rules design, Insula Software usually creates the rules. On-site training can be arranged if the management and creation of rules are to be handled in-house.

Ongoing Management

Business Rules should be reviewed anytime a screen or process change is made to ensure that the process is still being enforced correctly.


List of Business Rules Deployed with Framework (see attached PDF)

  • No labels