Centralized Master Data Management System for Budget Standardization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing budget management systems face challenges in managing master data across multiple users from different backgrounds, leading to discrepancies and inefficiencies in the budget application process.

Innovation Solution

A centralized master data management system (CMDMS) is implemented, allowing multiple users to access and manage master data while controlling privileges based on user personas, and ensuring standardized budget application formats.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If a centralized master data management system is implemented to standardize budget application formats, then manufacturing precision of budget data is improved, but device complexity increases

Engineering Contradiction:
Improvebudget data standardizationVSAvoidsystem structure
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The system is divided into distinct functional modules including a master data management module that stores standardized budget templates and parameters, a budget application module that retrieves and applies these standards, and an authorization module that manages user privileges. This segmentation allows each module to handle specific aspects of data standardization independently, improving manufacturing precision while managing complexity through modular design.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A centralized master data repository acts as an intermediary between various budget application processes and the underlying data standards. This intermediary layer provides standardized budget templates, validation rules, and parameters to multiple users and systems, ensuring consistent data formatting without requiring each system to implement its own complex validation logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If user privileges are controlled based on personas to enhance information security, then reliability of data access control is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvedata access controlVSAvoiduser access management
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system implements self-service authorization where users automatically receive appropriate access privileges based on their assigned persona or role. When a user logs in, the system automatically retrieves their persona information and grants corresponding access rights to budget applications and master data, eliminating the need for manual permission configuration and reducing operational complexity while maintaining security.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses persona parameters as the foundation for dynamic access control. Instead of managing individual permissions for each user, the system defines access rules based on persona characteristics (such as department, role level, or functional area). When a user's persona changes, their access privileges automatically update according to the predefined rules for that persona, simplifying access management while maintaining reliability.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If multiple users from different backgrounds access the system, then adaptability of the system is improved, but manufacturing precision of budget data deteriorates

Engineering Contradiction:
Improveuser accessibilityVSAvoidbudget data consistency
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The master data management system provides universal budget templates and validation rules that can be applied across different user backgrounds and departments. The system retrieves appropriate standardized templates based on user persona and applies consistent validation logic regardless of which user submits the budget application, ensuring data precision is maintained while accommodating diverse user needs through a unified interface.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12339982B2Centralized master data management system and method
Publication Date: 2025.06.24 RAKUTEN SYMPHONY INC
  • US12339982B2 patent drawing
  • US12339982B2 patent drawing
  • US12339982B2 patent drawing

AI summary

A centralized master data management system (CMDMS) includes a memory having instructions; and processing circuitry coupled to the memory, and being configured to execute the instructions, causing the processing circuitry to cause a graphical user interface (GUI) to be output by a user interface (UI), the GUI includes a first user input field configured to receive a first user input identifying an administrator to log in to the CMDMS; in response to a successful log in to the CMDMS, obtain master data from the memory, the master data being associated with the administrator; update the GUI to include a list of region configuration profiles (RCPs) managed by the administrator; and one or more functional elements, wherein each functional element trigger a respective action in response to being selected by the administrator; and authorize a user, within a predefined region, to be able to create and submit budget applications.