Database Realignment via Workspace Copying for Field Territories

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current data realignment processes in client-database server environments are costly and disruptive, often requiring downtime or leading to data loss and coverage issues due to the need for frequent redistribution of customer assignments among field representatives.

Innovation Solution

A method involving copying database tables to a workspace for offline modification, creating association rules for client access, and distributing these changes during synchronization, allowing realignment without interrupting database server operations or data integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If current data realignment processes are used to redistribute customer assignments among field representatives, then data ownership can be realigned, but database server downtime of several days is required and workflow is impeded

Engineering Contradiction:

Improvedata ownership realignmentVSAvoidworkflow continuity

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by creating a workspace copy of the database and preparing realignment changes in advance. The workspace contains a copy of the database schema and data, allowing realignment operations to be prepared and validated before being applied to the live database, thus avoiding downtime during the actual realignment execution.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The workspace acts as an intermediary between the current database state and the desired realigned state. All realignment operations are performed in the workspace first, then the validated changes are transferred to the live database. This intermediary layer allows realignment without interrupting database server operations.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If the system is updated while live without shutdown, then workflow continuity is maintained, but data loss and coverage issues arise such as customers being assigned to multiple field representatives or no representatives

Engineering Contradiction:

Improveworkflow continuityVSAvoiddata integrity

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system creates a copy of the database in the workspace environment. This copy contains all the data and schema needed to perform realignment operations without affecting the live database. Changes are tested and validated in the copy before being applied to the live system, ensuring data integrity while maintaining workflow continuity.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The workspace serves as a cushioning layer that protects the live database from potential errors during realignment. By performing all modifications in the workspace first and validating them against the realignment criteria, the system prevents data loss and coverage issues before they can affect the live database.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

3Adaptability or versatility

If frequent realignment is performed to maximize field representative efficiency, then customer assignment optimization is achieved, but the cost and disruption increase due to repeated downtime

Engineering Contradiction:

Improvecustomer assignment optimizationVSAvoiddowntime frequency

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system enables continuous realignment operations by performing all changes in the workspace without shutting down the database server. Multiple realignment operations can be prepared and executed sequentially or in parallel without interrupting business operations, allowing frequent optimization of customer assignments without the traditional downtime penalty.

Inventive Principle:

Principle #20Continuity of useful action

Solution Approach 2:

By preparing realignment changes in advance in the workspace environment, the system allows multiple realignment scenarios to be evaluated and validated before execution. This preliminary preparation enables frequent realignment operations to be performed quickly and efficiently when ready, minimizing the actual downtime required.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS7979390B2Software, systems, and methodologies for realignment of remote databases by a central database in support field representative territory assignments

Publication Date: 2011.07.12 PURDUE PHARMA LP

AI summary

A method for realigning a database server and a client database is provided. During realignment at least one table of the database server is copied to a workspace, and a set of records copied to the workspace is identified that are associated with the client. The set of records associated with the client are modified and can include a subset of records newly associated with the client. An association-rule is created that defines the modified set of records as accessible by the client and includes an effective time. The association-rule and the newly associated records are distributed to the client, preferably during database synchronization. At the effective time, the modifications to the workspace records are made effective on the server and activated on the client. Optionally, the association-rule and the newly associated records are distributed in response to receiving approval of the modified set of records.