Skip to main content
ION captures the labor time operators spend on run steps as check-in / check-out sessions, which feed cost and cycle-time estimates in Analytics and Dashboards. For how sessions open and close with step transitions and the availability rules, see the Overview. This page covers reviewing and editing that data.

​
Understanding and updating existing session data

To see how long you’ve been checked into a step, the total check-in duration per step, or to edit a check-in time, click the timer indicator on the step in run execution mode as shown in the video below. This opens the Checked-In Duration dialog, which lists each session’s check-in time, check-out time, and labor time. With the UpdateSession permission, you can also edit the check-in and check-out times. Watch: view and edit time-tracking session data An alternative method is to update session durations directly through the API. For step-by-step instructions, see API → Examples → Edit Time-Tracking Session Data. The Currently Clocked Into widget on the home page shows the steps you’re clocked into, and the status bar at the top lists all steps you’re checked into. Users who are checked in are highlighted green with a green checkmark next to their avatar and 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.