Automated Submission Kernel for Electronic Document Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Manual construction of submission packages for electronic document submissions is inefficient and requires significant knowledge and effort, while custom application development for each submission type is burdensome and lacks scalability.
Innovation Solution
An automated system using a generalized submission engine that processes documents to derive required outputs, such as tables of contents and XML documents, based on submission preparation information captured in configuration, schema, and code, enabling efficient and scalable electronic submission preparation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual construction of submission packages is used, then submission requirements can be met with knowledge-based processing, but efficiency and scalability are poor
Solution Approach 1:
The system enables self-service automated submission package construction by using the submission requirements document itself as the source of processing rules. The kernel automatically extracts and applies formatting, organization, and content requirements without needing pre-programmed custom applications, allowing the system to serve itself across different submission types.
Solution Approach 2:
The system changes the parameter of automation extent by transitioning from manual to automated processing through dynamic parameter adjustment. The kernel reads submission requirements and automatically adjusts processing parameters such as document organization structure, formatting rules, and content selection criteria based on the specific submission type detected.
2Adaptability or versatility
If custom applications are built for each submission type, then submission preparation knowledge is captured and scaling is enabled, but development burden and maintenance complexity increase
Solution Approach 1:
The submission kernel provides universal multi-functionality by handling multiple submission types through a single standardized interface. Instead of requiring separate custom applications for each submission type, the kernel automatically detects the submission type from the requirements document and applies appropriate processing rules, making one system serve multiple purposes.
Solution Approach 2:
The submission kernel acts as an intermediary between the submission requirements document and the package construction process. It mediates by parsing the requirements document, extracting processing instructions, and translating them into automated construction actions, eliminating the need for direct custom application development for each submission type.
3Ease of operation
If manual construction is used, then flexibility in handling different submission requirements is maintained, but operator knowledge and effort requirements are high
Solution Approach 1:
The system extracts and applies submission requirements automatically without human intervention. The kernel reads the submission requirements document, self-determines the processing rules, and executes package construction autonomously, eliminating the need for operators to possess specialized knowledge of submission formats and requirements.
Data Source
AI summary
Preparing an electronic submission is disclosed. A document is received. Submission preparation information to be used by a submission kernel for processing is identified based at least in part on information from the document. The document is processed based at least in part on the submission preparation information to produce one or more derived document outputs.