Document Version Tracking via Embedded GUID and Fingerprint

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for ensuring the currency of distributed information are inefficient, relying on manual processes that burden information consumers and publishers, and do not guarantee the use of the latest version of documents.

Innovation Solution

A computer-implemented method using a global unique identifier (GUID) and fingerprint embedded in documents to track and verify the version of a master document, allowing automated verification of document currency and preventing the use of outdated copies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual processes are used to validate document freshness, then information consumers can check document currency, but the burden and complexity of validation increases significantly

Engineering Contradiction:
Improvedocument freshness validationVSAvoidvalidation process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The document itself carries its own version identification information (GUID, version number, timestamp) that automatically indicates its freshness. The system uses these embedded attributes to enable self-validation without requiring external manual processes or complex validation infrastructure.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system provides feedback to information consumers about document freshness through version numbers and timestamps embedded in the document metadata. This feedback mechanism allows consumers to immediately understand whether a document is current without requiring complex validation procedures.

Inventive Principle:
Principle #23Feedback

2Reliability

If publishers manually contact everyone to distribute updates, then document currency can be ensured, but time consumption and labor requirements increase

Engineering Contradiction:
Improvedocument currencyVSAvoidupdate distribution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The master document is pre-tagged with version identification information (GUID, version number, timestamp) at the time of creation. This preliminary action enables automatic version tracking and eliminates the need for publishers to manually contact recipients when updates are made.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The manual mechanical process of publishers contacting each recipient is replaced by an automated electronic system that uses version numbers and timestamps to automatically identify and distribute updated documents to interested parties.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If expiration dates are assigned to documents, then document freshness can be indicated, but false expiration warnings may occur when information remains actually valid

Engineering Contradiction:
Improvedocument freshness indicationVSAvoidvalid information rejection
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system changes the parameter used for freshness indication from a fixed expiration date to dynamic version numbers and timestamps. This allows the system to distinguish between documents that are technically expired by date but still valid in content, versus documents that are truly outdated, preventing false rejection of valid information.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS7742617B2Document genealogy
Publication Date: 2010.06.22 BENTLEY SYSTEMS INC
  • US7742617B2 patent drawing
  • US7742617B2 patent drawing
  • US7742617B2 patent drawing

AI summary

A computer-readable medium contains software that, when read by a computer, causes the computer to perform a method for tracing a document. The method includes: on the computer, generating a global unique identifier (GUID) for a master document; embedding the GUID in the master document; making a copy of the master document available for viewing on another computer, wherein the copy of the master document includes the embedded GUID; receiving a version verification request from the other computer about the copy, wherein the version verification request includes the GUID from the copy; and providing a latest version of the master document referenced by the GUID from the copy to the second computer in response to the version verification request.