16.1 Enhancements for Asset Management (TIPWeb-IT)

Frontline Education is pleased to announce the latest enhancements for Asset Management (formerly TIPWeb-IT), which includes MDM audit integration.

MDM Audit Verification

Asset Management version 16.1 introduces MDM Audit Verification, allowing districts to use activity data from their Mobile Device Management (MDM) system to automatically verify devices during an audit.

Instead of manually confirming every device, districts can now verify devices based on recent activity, reducing audit effort while maintaining full accountability and traceability.

Key Capabilities

• Automatically verifies devices during audit generation based on MDM Last Seen activity
• Devices with activity after a selected date are marked as "Verified."
• Reduces manual audit workload
• Uses real device activity as supporting evidence.

Initiate Audit

MDM Audit Verification is configured within the “Initiate Site Audit” screen.

Step 1: Enter Audit Details

1. Enter an Audit Name.
2. Select Audit For (Room, Staff, or Student).

Step 2: Define Your Audit Scope

Define your audit scope (Sites, Product Types, Rooms, Staff, Grades).

These selections determine which devices are included in the audit.

Step 3: Configure MDM Verification

Select a date.

• The date must be today or earlier (not a future date).
• This tells the system to verify automatically any device with MDM activity after this date.

Step 4: Select Eligible Statuses

Choose which devices are allowed to be automatically verified: Verified MDM Tags Status(es) for Room/Staff/Student.

Only devices in the selected statuses will be verified.

Example:  Status selected:

• In Use

Statuses excluded:

• Lost
• Stolen
• Pending Lost
• Pending Stolen
• Disposed

A device marked "Lost" may still report activity, but if “Lost” is excluded, it will not be verified.

Step 5: Add Modified Date Verification (Optional)

• Verifies devices based on recent updates
• Can be used alongside MDM verification

Step 6: Start the Audit

Click GO to initiate the audit.

The system evaluates every device included in the audit:

• Checks MDM Last Seen Date
• Compares it to the selected date
• Confirms the device status is eligible
• Evaluates Tag Modified Date (if enabled)

MDM verification is applied at the time the audit is initiated.

Site audits are created and all assets meeting the MDM criteria are marked verified.

Assets not meeting the MDM date criteria are moved to a state of “Missing.”

When the site audit is approved, reconciliation tasks for assets in a state of “Missing” are available for actions.

After the audit is reconciled, Audit History under each tag will reflect the audit state and the action taken.

Automatic Verification

When a Device Qualifies

A device is automatically verified when the initiate audit is submitted:

• Its MDM Last Seen Date is after the selected date, and
• Its status is included.

When verified:

• The device is marked "Verified."
• No manual action is required.

If the Device Does Not Qualify

The device remains "Missing" and must be reviewed manually.

Combined Verification (MDM + Modified Date)

If both verification options are enabled:

• If both conditions are true: Verified via MDM Last Seen Date and Modified Date.
• If only one condition is true: Verified by that method.
• If neither is true: Device remains "Missing."

Only one audit history record is created per device, even if multiple conditions apply.

Supported MDM Integrations

MDM Audit Verification is supported for the following integrations:

• Google Admin (Chrome devices)
• Jamf Pro (Apple devices)
• Mosyle
• Microsoft Intune

Each integration provides device activity data used for verification.

MDM Field Mapping: Last Seen Date

MDM Audit Verification relies on the "Last Seen" (device activity) field provided by each supported MDM integration.

This field is used during audit generation to determine whether a device qualifies for automatic verification.

The table below outlines how each supported MDM integration maps its activity field into Asset Management.

Data Normalization

To ensure consistency across integrations:

• All MDM activity timestamps are converted into a standard date format.
• Epoch-based timestamps (e.g., Mosyle) are converted to readable date/time values.
• Timezone handling is normalized based on system configuration.

Where to See Verification Results

Audit Details Screen

Displays all devices in the audit and their verification status.

Tag Information > Audit History

Each verified device includes:

• Verified By: System
• Verified Date
• Verified Notes:
  • Verified via MDM Last Seen Date
  • Or combined with Modified Date

Tag Information > Detail

Displays MDM data used for verification, including Last Seen Date.

Available Reports

Verification results are available in:

• Audit Detail Report (Audit Scan Complete): Displays verification results during an active audit.
• Closed Audit Detail Report: Displays final verification results after audit completion.

All verification activity is fully tracked and reportable, including:

• Automatically verified devices
• Manually verified devices
• Verification method used (MDM, Modified Date, or both)

Key Notes

• MDM verification date must be today or earlier.
• Future dates are not allowed because audits are only evaluated at initiation (or when location changes).
• Status selection directly controls which devices are verified.
• Devices must have a valid MDM Last Seen Date.
• Applies only to newly initiated audits.

Previous Releases

The following are release notes for prior releases.