ION Factory OS
  • Welcome to ION
  • Features
    • Procedures
      • Steps
        • Content
        • Datagrid
        • Fields
        • Attributes
      • Dependencies
      • Part-Procedure Relationship
      • Attributes
      • Standard Steps
      • Installation Requirements (Beta)
      • Nested Steps and Nested Standard Steps
      • Procedure Best Practices
    • Runs
      • Run Execution Overview
      • Runs And Step States
      • Batching Runs
        • Batching 2.0 Changes
      • Workcenter execution
      • Split Inventory on a Run
      • Redlines
      • Export run data
      • Scheduling runs
      • Time Tracking
      • Attributes
      • Outside Processing
      • Runs Best Practices
    • Parts Library
      • As-built Bill of Materials (aBOM)
        • Editing aBOM build requirements
        • aBOM Beta Changes
          • aBOM actions for developers
      • Inventory
        • Inventory status
        • Inventory splitting
        • Inventory merging
        • Inventory scrapping
        • Kitting
        • Inventory Movement Automations
      • Manufacturing bill of materials (mBOM)
        • mBOM versions
        • Made on Assembly (MOA)
        • Part Substitutes
        • Reference designators
      • Part Attributes
      • Part revision interchangeability
      • Supplier Part Numbers & Purchase Unit Conversions
    • Kitting and Inventory Fulfilment
      • Kit Statuses and Workflows
      • Inventory requests
      • Kitting and runs
      • Fulfilling Multiple Kits
      • Kanban Kitting
    • Purchasing
      • Purchase Orders
        • Types of Purchases
        • Purchase Order Approvals
        • Purchase Order FAQs
        • Supplier Part Numbers & Unit Conversions
        • PO Requirements, Terms, and Quality Clauses
      • Receiving/Inspection
      • Outside Processing
      • Consigned Parts
    • Barcode Labels
      • Templating
        • ION barcode minimum sizes
        • Sample templates
      • Printing
        • Configuring Zebra Browser Print
        • Server Based Barcode Printing (PrintNode)
      • Scanning
        • Scan barcodes from other systems
    • Quality
      • Issues
      • Further Actions - CAPA
      • Issues States, Dispositions, and Resolutions
      • Quality Best Practices
    • Tools
    • Locations
    • Attributes
    • Labels
      • Deleting labels
    • Notifications
    • Search
    • Settings
      • Role based access control
        • Full Glossary of ION Permissions
    • ION Actions
      • ION Actions examples for Quality
      • ION Actions examples for Runs and Procedures
      • ION ACTIONS examples for Supply Chain
  • Analytics
    • Inventory valuation
    • Part impact analysis
    • Users, Roles, Teams
    • Analytics FAQ
    • Data Connector
    • Data Products
  • Plans and Autoplan
    • Autoplan
    • Autoplan glossary
    • Preparing to use Autoplan
    • Clear to build reporting
    • Running Autoplan on a schedule
    • Firm and blocked plan items
    • Location constraints
    • Autoplan suggested suppliers and procedures
    • Reorder point
    • Plan input serial numbers
    • Applying a calendar
    • Plan Reservations
    • Independent schedules
    • Drive demand from kits
    • Drive demand below buy parts configuration
    • Group plan items with the same date
    • Manualy Changing Autoplan Status
  • API
    • How to create an App with ION
    • Access Tokens
    • About GraphQL
    • Interactive API explorer
    • API Keys
    • Examples
      • Notifications
      • Runs
      • Automatically updating fields in runs
      • Parts and Part Revisioning
      • mBOMs
      • Part Inventory and Kitting
      • aBOM (As-built Bill of Materials)
      • Edit time-tracking session data
    • Changelog
    • Webhooks
    • Pagination
  • Automations
    • Auto-checkout of Run Steps
    • Auto-Consumption of Lineside Inventory
    • Automatically Send Purchases to Suppliers
    • Set Close by Run Step on Issue Creation
    • Intent Management / Grade / Tier / Pedigree
      • Data Imprinting
      • ION Actions for Intent
    • Auto-Update mBOM Revision on Part Revision Update
    • Auto-approve part-procedure relationships
    • Purchase Order PDF and Versions
    • Auto Populate PO Line Attributes
    • Imprint Attributes from One Object to Another on a Desired Event
  • Integrations
    • Deploying Integrations and Automations
    • Arena
    • Cofactr
    • Datum
    • Duro
    • NetSuite
      • Purchasing in NetSuite, Receiving in ION
      • Work Order/Assembly Builds
    • Procurable
    • PDF Generator
    • Quickbooks
    • Ramp
    • Silkline Integration
    • Slack
    • Smartsheet
    • SOLIDWORKS
    • Teamcenter
  • Training
    • Standard Operating Procedures
      • Cycle Counting
      • Tool Utilization
    • Guided Flows
    • ION Sandbox
    • Chat Support for ION
  • Troubleshooting
    • Resetting your password
    • Resetting your Multi-Factor Authentication
    • You have no roles... error
  • Changelog
  • Adminstration
    • Security
      • Backups and Security FAQ
      • Single Sign-On (SSO)
        • Okta SAML connection setup
      • Export Control
      • Report Generator Disclaimer
    • Browser and Device Compatibility
    • Authentication
      • My company is new to ION, logging in for the first time.
      • I'm told I'm not authorized to access the application
      • My account has been deactivated
    • Login Page
  • Tickets Portal
Powered by GitBook
On this page

Was this helpful?

  1. Features
  2. Runs

Time Tracking

PreviousScheduling runsNextAttributes

Last updated 10 months ago

Was this helpful?

ION automatically tracks the time users spend executing steps in runs to give teams an accurate representation of how much labor time was spent on each operation. In turn, that data can be used in our tool to help you determine cost estimates per assembly! To track time, an operator has to check in to start the capture of time and check out when they are finished working. Each check-in and check-out pair is called a session which can be edited as seen below.

Our goal is to make this as seamless as possible to ensure the least overhead for operators when performing work so that they spend most of their energy working while having confidence that ION is tracking their work accurately. To do this, we have a few automations and validations that are online and a few more we are considering:

  • When an operator first begins a step (step moves from TODO to In Progress) they are automatically checked into that step.

  • When an operator Completes a step, places a step on Hold, places a step in Redline, or Fails a step they are automatically clocked out.

  • Operators are prevented from being checked into a run step when the step is not Available to Work. Available to Work implies a run step is in TODO or In Progress, is not blocked by upstream run steps, and the parent step, if exists, is In Progress.

  • Future State: When an operator checks in while the run step is Available to Work and in the TODO status, the run step will be automatically moved to In Progress.

  • Future State: When editing any data in a run step while the run step is Available to Work and in the TODO status will automatically move the step to In Progress and check in the current operator.

Understanding and Updating Existing Session Data

If you want to understand how long you've been checked into a step, the total duration of check-in time per step or want to edit the time someone has been checked into a step, click on the gray checkmark in run execution mode as seen in the video below. If you have the permission to UpdateSession, then you can also edit the check-in time and the check-out time.

The Currently Clocked Into widget on the home screen shows what steps you're clocked into and the status bar at the top informs you of all steps you are checked into.

Users who are checked in are highlighted green and have a green checkmark next to their avatar and will appear on the step queue on the left.

Using a smart card badge for login authentication

Badge authentication can make it easy for multiple users to login via their badge and check into operations, buyoff steps, etc. Below is an example of badge authentication to Windows 10 hosts that has been successful by using the following technologies:

  • Smart card: Taglio PIVKey C910

  • Smart card reader: HID Omnikey 5422

  • Smart card certificate: Smart Card Logon

  1. Configure a Smart Card Logon certificate template on internal Windows Certificate Authority ADCS.

  2. Explicitly grant a predefined security group access to read/enroll via the template’s permissions.

  3. Write a PowerShell script to simplify the process of requesting a certificate (certreq), setting a pin on the badge PivKeyTool), and writing the certificate to the badge (certutil).

  4. After the PowerShell script completes successfully, the badge can then be used to login to a Windows 10 device.

  5. The user must insert/touch their badge to the reader, and input their pin.

  6. We’ve seen a successful authentication rollup from the OS to the browser (Chrome/Edge), which automatically authenticates the user to Azure AD. This helps the workflow immensely, as they can easily reach First Resonance ION soon after login.

Some improvements during your implementation may consider making the certificate request process easier, as well as implementing automated smart card certificate revocation on our CA to avoid users having multiple certificates on multiple badges.

An alternative method to update session durations is directly through the API. For step-by-step instructions, please visit the page within our manual.

API > Examples > Edit Time-Tracking Session Data
Analytics