Three-Layered System Blueprint Evaluation for Complex Project Decisions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current decision-making tools for complex systems and projects lack the ability to manage and relate large, complex sets of information and decisions, particularly in evaluating requirements, solutions, and deployments, leading to costly problems that arise during project lifecycle stages.

Innovation Solution

A three-layered system blueprint approach, comprising Business Blueprints, Solution Blueprints, and Deployment Blueprints, which allows users to create, evaluate, and revise blueprints using analytical modules, enabling strategic trade-offs and providing a consistent view across stakeholders.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If prior requirements and design tools are used to facilitate tactical decision-making, then detailed design capabilities are improved, but the ability to manage large complex sets of information and conduct strategic evaluations deteriorates

Engineering Contradiction:
Improvedetailed design capabilityVSAvoidinformation management capability
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent segments the complex system information into three distinct blueprint layers: Business Blueprints (capturing business requirements), Solution Blueprints (capturing technology solutions), and Deployment Blueprints (capturing deployment configurations). This segmentation allows decision-makers to evaluate each layer independently while maintaining their interrelationships, thereby managing large complex sets of information through structured division rather than attempting to handle all information simultaneously in a single tool.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a vertical dimension by organizing blueprints across multiple layers (Business, Solution, Deployment) rather than treating all requirements and designs in a single horizontal plane. This dimensional change enables strategic evaluation by allowing users to traverse between different abstraction levels and conduct trade-off analyses across layers, transforming the flat information management approach into a multi-dimensional evaluation framework.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Ease of operation

If independent isolated software tools are used for specific aspects of decision-making, then ease of operation for individual tasks is improved, but the ability to relate and evaluate associations between requirements, solutions and deployments deteriorates

Engineering Contradiction:
Improveindividual task facilitationVSAvoidassociation information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent merges previously independent isolated tools into an integrated blueprint evaluation system that maintains the specialized functionality of each tool type while adding the capability to relate and evaluate associations between Business, Solution, and Deployment blueprints. The system combines requirements management, solution evaluation, and deployment planning capabilities into a unified framework where associations between elements across different blueprints are automatically tracked and evaluated.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal blueprint evaluation system that can handle multiple types of evaluations (requirements satisfaction, solution compatibility, deployment feasibility) within a single integrated framework. This multi-functional system allows users to conduct various aspects of decision-making through a common interface that preserves association information across all evaluation types, eliminating the need for separate isolated tools for each evaluation aspect.

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

3Adaptability or versatility

If all analyses and evaluations are left to human users' cognitive processes, then flexibility in interpretation is improved, but productivity and objectivity of evaluations deteriorate

Engineering Contradiction:
Improveinterpretation flexibilityVSAvoidevaluation efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements automated feedback mechanisms that provide objective evaluation results to decision-makers. The system automatically analyzes blueprint associations, evaluates requirements satisfaction, assesses solution compatibility, and determines deployment feasibility, then feeds this analyzed information back to users. This feedback loop maintains interpretation flexibility by allowing users to consider multiple perspectives while dramatically improving productivity by eliminating manual cognitive analysis of large information sets.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary automated analysis layer between human decision-makers and the complex blueprint data. This intermediary system performs objective evaluations of associations between requirements, solutions, and deployments, providing structured analysis results that assist human judgment without completely replacing it. The intermediary maintains objectivity through automated evaluation while preserving adaptability by presenting results that users can interpret in context of their specific business needs.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9569737B2Methods and tools for creating and evaluating system blueprints
Publication Date: 2017.02.14 AWARE SOFTWARE
  • US9569737B2 patent drawing
  • US9569737B2 patent drawing
  • US9569737B2 patent drawing

AI summary

Method and tools for creating and evaluating a set of system blueprints pertaining to the delivery of a system or a project. Each blueprint is an architecture design/specification that enables analysis of each blueprint, families of blueprints and relationships between blueprint layers. A user can create various system blueprints based on data from existing databases containing requirements, solutions, and deployments of a system or project. After creating each blueprint, users may view the blueprint to visually detect problems and further revise the blueprint. In addition, for each type of blueprint, the user can evaluate the blueprint against various metrics and criteria related to requirements, solutions, and deployments and view the evaluation results.