Uniform Hierarchical View for Technical Document Interpretation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Statutory reports in various technical file formats, such as XML, JSON, and CSV, are difficult for users to interpret and edit due to their complex syntax and hierarchical organization, leading to inefficiencies in review and submission processes.

Innovation Solution

A uniform hierarchical view is generated across different file formats, allowing users to view and edit technical documents in a standardized manner through metadata definitions and mappings, enabling searchable and editable interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If statutory reports are generated in technical file formats (XML, JSON, CSV), then the reports can be processed and submitted efficiently, but the reports become difficult for users to read and interpret

Engineering Contradiction:
Improvereport processing efficiencyVSAvoiduser interpretability
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary layer (visualizer interface and metadata definitions) between the technical file format and the user. This intermediary translates complex technical formats into human-readable hierarchical views while preserving the underlying data structure, allowing users to interpret reports without needing to understand the technical format syntax.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a visual copy or representation of the technical report data in a human-readable format. The uniform hierarchical view generates a visual representation that mirrors the structure and content of the original technical file, making it accessible to users while the original technical format remains intact for processing.

Inventive Principle:
Principle #26Copying

2Extent of automation

If statutory reports use complex technical syntax, then the reports can be structured for automated processing, but editing the reports becomes difficult for users

Engineering Contradiction:
Improveautomated processing capabilityVSAvoidediting difficulty
Core Design Contradiction:
Extent of automationVSEase of operation

Solution Approach 1:

The visualizer interface serves as an intermediary that presents data in an editable human-readable format while maintaining linkage to the original technical file. Users can edit data elements in the uniform hierarchical view, and changes are automatically propagated to the underlying technical format, enabling easy editing without losing automated processing capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system provides self-service functionality where the uniform hierarchical view automatically handles the conversion and synchronization between user-friendly display format and technical file format. When users make edits in the visual interface, the system automatically updates the underlying technical data without requiring manual intervention to maintain format compliance.

Inventive Principle:
Principle #25Self-service

3Loss of information

If statutory reports are searched in native technical file format, then only currently displayed data can be searched, but searching the entire data set becomes impossible

Engineering Contradiction:
Improvesearch scopeVSAvoidsearchability
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The uniform hierarchical view creates a complete visual copy of the entire technical report data set, making all data accessible for search operations. Unlike viewing the raw technical file where only displayed portions are searchable, the visualizer loads and presents the complete data hierarchy, enabling full-text search across all data elements regardless of their position in the original file.

Inventive Principle:
Principle #26Copying

4Stability of the object's composition

If technical documents are displayed in native format, then the original data structure is preserved, but the hierarchical organization becomes difficult to determine

Engineering Contradiction:
Improvedata structure integrityVSAvoidhierarchy detectability
Core Design Contradiction:
Stability of the object's compositionVSDifficulty of detecting and measuring

Solution Approach 1:

The visualizer interface acts as an intermediary that interprets and renders the hierarchical structure defined in the metadata definitions. It presents data in a nested, indented hierarchical view that visually communicates the organization and relationships between data elements, making the hierarchy detectable while the underlying technical file format remains unchanged.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The uniform hierarchical view uses visual formatting including color coding, indentation levels, and hierarchical grouping to distinguish different levels and types of data elements. These visual cues make the hierarchical organization immediately apparent to users while preserving the original data structure in the technical file.

Inventive Principle:
Principle #32Color changes

Data Source

PatentUS12061860B2Uniform hierarchical view over diverse data formats
Publication Date: 2024.08.13 SAP SE
  • US12061860B2 patent drawing
  • US12061860B2 patent drawing
  • US12061860B2 patent drawing

AI summary

Systems, methods, and computer-readable media are disclosed for generating uniform hierarchical views of technical documents irrespective of a file format for the technical document. Metadata definitions may be received that define a technical document hierarchy for the technical document. Based on the metadata definitions, technical data element may be mapped to the technical document hierarchy. The technical document may be generated, the technical document comprising the technical data elements. Based in part on the technical document and the metadata definitions, the uniform hierarchical view may be generated. The uniform hierarchical view may be populated with at least a subset of the technical data elements from the technical document. Once generated, the uniform hierarchical view may be displayed.