01Job intake
Bring in the documents
The team uploads the documents and drawings associated with a job, giving the review a shared starting point.
- Documents
- Drawings
Case study / Aerospace manufacturer
Understand the documents. Bring the specifications into view.
An aerospace manufacturer spent significant time reading documents, checking drawings and looking up specifications to understand the work ahead. Werkon built a custom application around that preparation process. A job-based review workflow brings document findings together, while a knowledge base lets the team add specification codes and rules. The focus is understanding the requirements before work begins.
The workflow
Understand what the job requires before moving forward.
The preparation work involved more than reading a single document. The team moved between documents, drawings and specification lookups to understand a job. The application was built around that review process, with processing results organized by job and a dedicated place for the specification codes and rules the team works with.
02Document analysis
Process the job
The application uses a job-based agent workflow to process the documents and bring the results together for the team to inspect.
- Processing
- Job results
03Review workspace
Review the findings
A job summary and detailed processing results support the review of what the documents contain and what needs closer attention.
- Summary
- Detailed results
04Knowledge base
Maintain the reference knowledge
The team can add specification codes and rules to the knowledge base, giving this reference information a dedicated place in the application.
- Specification codes
- Rules
Inside the application
Job findings and specification knowledge, in one application.
Explore the drawing-analysis workspace, the review report and the specification knowledge base. The team can maintain reference entries and configure the fields used to organize them. Select a screenshot to enlarge it. Identifying details have been removed.
- 01
Drawing analysis
The source drawing sits beside the structured analysis, so the team can compare extracted information with the document being reviewed.
Source drawing and structured analysis, side by side. Enlarge screenshot: Drawing analysis - 02
Review report
The job report brings together extracted information, missing references and points that need verification against the original documents.
A review report surfaces information gaps and a material-reading concern. Enlarge screenshot: Review report - 03
Knowledge base
Specification entries organize codes, sub-codes, values and notes in a searchable table, with controls to import or add entries.
Specification entries organized in a searchable knowledge base. Enlarge screenshot: Knowledge base - 04
Configurable fields
The team can configure the fields used for its reference knowledge, including required values, grouping and text or selection types.
Configurable fields define how reference knowledge is organized. Enlarge screenshot: Configurable fields
The delivery focus
Make the preparation work easier to follow.
The project addresses the time spent understanding documents, drawings and specifications before work begins. The delivery account establishes the workflow and knowledge-base capability. A measured before-and-after time comparison has not been supplied.
- Start with the actual bottleneck
- The team's difficulty was the effort required to read, check and look up information across a document pack. The application centers that preparation work.
- Give reference knowledge a home
- A dedicated knowledge base lets the team add specification codes and rules. It makes maintaining that information part of the application workflow.
- Keep the reviewer in the process
- The results workspace supports people reviewing the documents. Processing a file or finding a specification reference does not, by itself, establish which requirements apply to a job.
- Describe the delivered capability
- This case study documents a custom document-review application with a specification knowledge base. It makes no claim of automated engineering approval or a measured reduction in review time.
[ WORKFLOW / SYSTEMS AUDIT ]
THE FIRST ENGAGEMENT
Start with one real workflow
A Systems Audit is the usual starting point. If the opportunity is already clear, we can move directly into a focused build.
Show Us the WorkflowStart with the free automation readiness checklistOBSERVEQUANTIFYDECIDEBUILD
Continue with the work
Choose the next useful path.
Stay with the operating question. The technology can wait until the work is clear.