BRMS Staging Environment for Production Rollout

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of rollout systems and procedures for maintaining production environments in industries like banking and insurance leads to lengthy rollout processes, conflicting with the need for timely deployment and regulatory compliance, often requiring costly emergency fixes or disrupting ongoing changes.

Innovation Solution

Implementing a Business Rule Management System (BRMS) topology that allows for strategic maintenance by selectively executing batch files and transformation scripts in a staging environment, simulating future dates to test changes without following the standard rollout cycle, enabling quicker modifications and testing in an emergency fix environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If standard rollout procedures are followed to ensure production environment stability, then reliability is improved, but the rollout cycle time increases significantly

Engineering Contradiction:
Improveproduction environment stabilityVSAvoidrollout cycle time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by copying production data tables to a staging environment before actual rollout, and using date override tables to simulate future dates in advance. This allows testing and validation to be performed ahead of time in a controlled staging environment, so that when the actual rollout occurs, the production environment can be updated quickly with pre-validated changes, thus maintaining reliability while reducing rollout cycle time.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If standard rollout procedures are followed, then production environment protection is improved, but the speed of deployment deteriorates

Engineering Contradiction:
Improveproduction environment protectionVSAvoiddeployment speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies copying by creating a staging environment that replicates the production environment structure and copying data tables to this staging environment. Changes are first implemented and tested in the copied staging environment, then only validated changes are copied back to production. This allows rapid iteration and testing in the staging environment without risking production stability, thereby improving deployment speed while maintaining production protection.

Inventive Principle:
Principle #26Copying

3Productivity

If emergency fixes are implemented to accelerate deployment, then productivity is improved, but device complexity and costs increase

Engineering Contradiction:
Improvedeployment speedVSAvoidhardware and environment pipeline complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a staging environment as an intermediary between development and production environments. This staging environment serves as a mediator where changes can be tested with simulated future dates using date override tables, allowing validation without requiring complex emergency fix pipelines or parallel hardware environments. The intermediary staging environment simplifies the overall system architecture while enabling faster, safer deployments.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10437583B2Systems and methods for strategic maintenance of a production environment utilizing a business rules management system
Publication Date: 2019.10.08 THE TRAVELERS INDEMNITY
  • US10437583B2 patent drawing
  • US10437583B2 patent drawing
  • US10437583B2 patent drawing

AI summary

Systems, methods, and articles of manufacture provide for strategic maintenance of a production environment utilizing a Business Rules Management System (BRMS) topology by selectively executing batch files and transformation scripts to edit production tables in a staging environment and test the edited tables in an emergency fix environment utilizing an edited date override table.