Regulatory Requirement Description Generator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprises face difficulty in compliance with regulatory content due to the increasing complexity and volume of regulatory documents, which lack clear identification of applicable requirements, leading to a burden in determining relevant regulations for their operations.

Innovation Solution

A computer-implemented method and system for generating regulatory content requirement descriptions, involving hierarchical analysis, conjunction classification, and summarization to extract and present applicable requirements in a clear and concise manner, using neural networks for classification and summarization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If regulatory content is made more comprehensive to cover all possible compliance scenarios, then the completeness of regulatory coverage is improved, but the complexity and volume of regulatory documents increases

Engineering Contradiction:
Improvecompleteness of regulatory coverageVSAvoidcomplexity of regulatory documents
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments regulatory documents into hierarchical levels (Level 1: high-level requirements, Level 2: detailed requirements, Level 3: specific conditions). This segmentation allows comprehensive regulatory coverage to be organized in a structured manner, making it easier for enterprises to navigate and apply only the relevant portions to their specific operations, thereby reducing the perceived complexity while maintaining completeness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary system (the computational method and processing system) that acts as a mediator between comprehensive regulatory content and enterprises. This intermediary automatically processes, analyzes, and extracts applicable requirements from the comprehensive regulatory documents, presenting only the relevant information to enterprises. This resolves the contradiction by maintaining comprehensive regulatory coverage in the source documents while delivering simplified, tailored information to users.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If regulatory documents are made more detailed to ensure precise compliance requirements, then the precision of compliance guidance is improved, but the difficulty in identifying applicable requirements increases

Engineering Contradiction:
Improveprecision of compliance guidanceVSAvoiddifficulty in identifying applicable requirements
Core Design Contradiction:
Measurement precisionVSDifficulty of detecting and measuring

Solution Approach 1:

The patent applies preliminary action by pre-processing regulatory documents into a structured hierarchical format with clearly defined levels and relationships before enterprises need to use them. The computational method pre-identifies and tags requirements at different levels, establishing the hierarchical structure in advance. This preliminary structuring makes it significantly easier for enterprises to later identify and extract only the applicable requirements for their specific operations, without having to manually analyze entire detailed documents.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces the manual mechanical process of analyzing detailed regulatory documents with an automated computational system. The processing system uses algorithms to automatically traverse the hierarchical structure, identify applicable requirements based on enterprise-specific parameters, and extract relevant information. This substitution of automated computation for manual analysis resolves the contradiction by maintaining detailed precision in the regulatory content while dramatically reducing the difficulty of identifying applicable requirements.

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

3Measurement precision

If enterprises manually review regulatory documents to determine applicable requirements, then the accuracy of requirement identification can be maintained, but the time and resources required increase significantly

Engineering Contradiction:
Improveaccuracy of requirement identificationVSAvoidtime for compliance analysis
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent enables self-service by allowing enterprises to independently determine their applicable regulatory requirements through automated processing. The computational method empowers enterprises to input their own operational parameters and receive customized extracts of applicable requirements without needing extensive manual review by compliance experts. This self-service approach maintains accuracy through structured processing while dramatically reducing the time and resources required compared to traditional manual review processes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent applies parameter changes by transforming the regulatory document structure into a computationally processable format with defined hierarchical parameters and relationships. The system changes the parameters of the regulatory content from unstructured text to structured data with identifiable levels, conditions, and requirements. This parameter transformation enables automated processing that maintains accuracy while reducing time consumption, as the system can efficiently query and extract requirements based on specific parameters rather than manual text analysis.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20230419110A1System and method for generating regulatory content requirement descriptions
Publication Date: 2023.12.28 INTELEX TECH ULC
  • US20230419110A1 patent drawing
  • US20230419110A1 patent drawing
  • US20230419110A1 patent drawing

AI summary

A computer-implemented method for generating regulatory content requirement descriptions is disclosed and involves receiving requirement data including a plurality of requirements including hierarchical information extracted from regulatory content. The method involves identifying parent requirements based on the existence of child requirements on a lower hierarchical level and generating requirement pairs including the parent requirement and at least one child requirement. The method also involves feeding each of the pairs through a conjunction classifier which has been trained to generate a classification output indicative of the pair being not a conjunction (NC), a single requirement conjunction (CSR), or a multiple requirement conjunction (CMR). The method involves generating a set of requirement descriptions based on the classification output generated for each parent requirement.