Spreadsheet Model Template Segmentation for Version Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for managing spreadsheet models either become overly complex and costly due to version control and communication issues when using spreadsheet models, or they lack flexibility when using database-based approaches.

Innovation Solution

A system that separates the logic of spreadsheet models from their data, using a Model Template to deploy instances over a web-based Model Relationship Structure, allowing for flexible management, aggregation, and comparison of models through a command library that includes Spreadsheet and Structure Commands.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If spreadsheet models are stored and transmitted via email or shared spreadsheets, then flexibility and ease of use are maintained, but version control and communication costs become complicated and significant

Engineering Contradiction:
ImproveflexibilityVSAvoidversion control complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the spreadsheet model into two distinct parts: a template component that defines the structure, calculations, and logic, and data components that contain the actual values. This segmentation allows the template to be reused multiple times without version control issues, while data can be updated independently in each instance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a copying mechanism where a single template can be copied to create multiple instances. Each instance maintains references to the original template, automatically inheriting updates to the template structure and logic. This eliminates version control problems while preserving flexibility through the ability to create and manage multiple instances.

Inventive Principle:
Principle #26Copying

2Productivity

If database structures are used for better web access and aggregation, then scalability is improved, but flexibility and modeling power are greatly restricted

Engineering Contradiction:
ImprovescalabilityVSAvoidmodeling flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a template as an intermediary layer between the rigid database structure and the flexible spreadsheet modeling needs. The template contains the spreadsheet logic, calculations, and structure, while the database stores data for multiple instances. This intermediary allows users to leverage database scalability for data storage while maintaining spreadsheet-like flexibility through the template's calculation structure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The template design makes it universal and multi-functional, capable of being copied and instantiated multiple times with different data sets. The same template can serve different purposes by varying the input data, enabling both scalability through reuse and flexibility through adaptability to different scenarios.

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

3Adaptability or versatility

If spreadsheet models are created and managed individually, then modeling flexibility is maintained, but communication and maintenance costs increase significantly

Engineering Contradiction:
Improvemodeling flexibilityVSAvoidmaintenance cost
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

By segmenting the model into a reusable template and instance-specific data, the patent eliminates redundant maintenance work. Updates to the template automatically propagate to all instances, reducing maintenance costs while preserving modeling flexibility at the instance level through data customization.

Inventive Principle:
Principle #1Segmentation

4Reliability

If version control is implemented for spreadsheet models, then tracking changes is improved, but communication and maintenance costs become significant

Engineering Contradiction:
Improveversion controlVSAvoidcommunication cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The copying mechanism with template references provides inherent version control. When a template is updated, all instances automatically reflect the changes, eliminating the need for manual version control processes and reducing communication overhead while maintaining reliability through consistent updates.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9575950B2Systems and methods for managing spreadsheet models
Publication Date: 2017.02.21 SMARTORG
  • US9575950B2 patent drawing
  • US9575950B2 patent drawing
  • US9575950B2 patent drawing

AI summary

A method and computing device for managing models. The method and computing device receive a spreadsheet model, receive template management instructions on how to manage evaluations, create, from the spreadsheet model and the template management instructions, a model template, and deploy, in response to user action, an instance of the model template into a model relationship structure relating one or more spreadsheet model instances.