Filename Generation Unit for Job Type Identification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing file generation systems for job execution histories do not allow users to identify the type of job execution history from the filename, making it difficult to manage and retrieve specific job types.

Innovation Solution

A file generation apparatus that includes a filename generation unit to create filenames based on the type of job, enabling users to easily identify the type of job execution history from the filename.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If filenames are generated without job type information, then the file generation process is simple, but users cannot identify the type of job execution history from the filename

Engineering Contradiction:
Improvejob type informationVSAvoidfilename generation process
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The filename is segmented into multiple components: job type identifier, execution date, and sequence number. This segmentation allows the filename to convey specific information about the job execution history while maintaining a structured and manageable format.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The job type information is incorporated into the filename during the file generation process itself, rather than requiring subsequent processing or user interpretation. This preliminary action ensures that the filename immediately provides identifiable information about the job type.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If multiple execution history files are stored with generic names, then storage is straightforward, but retrieval of specific job types becomes difficult

Engineering Contradiction:
Improvefile retrievalVSAvoidtime to identify job type
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The filename acts as a visual indicator (analogous to color changes) that immediately distinguishes different job types. By embedding job type identifiers in the filename, users can quickly identify and retrieve specific job execution histories without opening each file.

Inventive Principle:
Principle #32Color changes

Solution Approach 2:

The filename serves as an intermediary between the stored execution history data and the user's retrieval needs. It provides a searchable and identifiable reference that mediates the process of locating specific job types within the stored files.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of information

If filenames do not include job type identifiers, then file management is simpler, but user understanding of file contents is reduced

Engineering Contradiction:
Improvefile content identificationVSAvoidfilename structure
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

Specific portions of the filename are assigned specific functions: the job type identifier portion provides local quality information about the file contents, while other portions handle temporal and sequential information. This localized information distribution optimizes both identifiability and organization.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The filename structure enables the file system to self-organize execution history files by job type without requiring external metadata or additional indexing systems. The embedded job type identifiers allow automatic sorting and retrieval based on file names alone.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10277772B2File generation apparatus, method for controlling file generation apparatus, and storage medium
Publication Date: 2019.04.30 CANON KK
  • US10277772B2 patent drawing
  • US10277772B2 patent drawing
  • US10277772B2 patent drawing

AI summary

A mechanism for enabling identification of an execution history of what type of job a generated file is from a filename of the file. The mechanism includes generating the file based on the execution history of the job, and generating the filename of the file based on the type of the job.