Automated Time Tracking via File Event Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual tracking and recording of time spent on tasks by employees is prone to human error and is inefficient, affecting payroll, billing, and project management processes.

Innovation Solution

A system and method that automatically track time based on file events and timestamps, mapping these events to tasks, and generating reports to accurately record time spent on tasks, reducing administrative burdens and errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual time tracking is implemented, then employees can record time spent on tasks, but human error and inefficiency occur in recording and data entry

Engineering Contradiction:
Improveaccuracy of time trackingVSAvoidefficiency of time tracking process
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system enables self-service time tracking by automatically monitoring file access events and generating time records without requiring employee intervention. The event manager detects file open/close events and automatically maps them to tasks, eliminating manual recording while ensuring accurate time tracking data.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical manual process of filling out timesheets with an automated electronic system. The event manager uses computer-generated events from file access logs to automatically create time records, substituting human manual entry with automated event detection and processing.

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

2Productivity

If automated time tracking is implemented, then efficiency is improved, but system complexity increases

Engineering Contradiction:
Improveefficiency of time tracking processVSAvoidcomplexity of tracking system
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The event manager serves multiple functions: it detects file access events, maps files to tasks, generates time records, and interfaces with existing organizational systems. This multi-functionality consolidates what could be multiple separate complex components into a single versatile module, managing system complexity while maintaining automation benefits.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The event manager acts as an intermediary layer between the file system and the time tracking system. It receives standard file access events, processes them through mapping rules, and outputs standardized time records, simplifying the integration complexity by providing a clear interface between existing systems and the new automated tracking functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If manual data entry is required, then system simplicity is maintained, but errors occur in payroll and billing processes

Engineering Contradiction:
Improvesimplicity of system structureVSAvoidaccuracy of payroll and billing data
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system establishes feedback loops where time records generated from file events are automatically fed into payroll and billing systems. The event manager continuously monitors file access patterns and adjusts time records accordingly, providing ongoing verification and correction that eliminates manual entry errors while maintaining data accuracy across connected systems.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8438579B2System and method for time tracking
Publication Date: 2013.05.07 INTUIT INC
  • US8438579B2 patent drawing
  • US8438579B2 patent drawing
  • US8438579B2 patent drawing

AI summary

A method for tracking time, including obtaining a plurality of tasks; identify a first open event and a first close event associated with a first file; identifying a start idle event and an end idle event associated with the first file after identifying the first open event; generating a first open event time stamp for the first open event, a first close event time stamp for the first close event, a start idle event time stamp for the start idle event, and an end idle event time stamp for the end idle event; mapping the first file to a first task of the plurality of tasks; and presenting a report including the first task, the first open event time stamp, the first close event time stamp, the start idle event time stamp, and the end idle event time stamp.