T2 Parking System

Body

T2 Parking System – Missing Data Issue Resolution Process

Application Name: T2 Parking System
Department Owner: University Parking & Transportation
Primary Business Users: Parking Operations (UHCL), General Accounting (UHCL), UH System (UHS)
Last Updated: 11/19/25

1. Purpose

This article defines the support structure, responsibilities, communication channels, and escalation process for issues related to the T2 Parking System, with specific focus on missing automated entries, data feeds, and coordination among UHCL and UHS teams.

2. System Overview

T2 Parking System is used by UHCL for managing parking-related transactions, including:

  • Parking permits

  • Daily parking fees

  • Credit card transactions

  • Data feeds to UHS for posting to the General Ledger (GL)

UHS processes the data feeds and records the appropriate GL entries based on files provided by UHCL and T2.

3. Support Responsibilities

3.1 UHCL Parking Operations (Primary Functional Contact)

Primary Contacts:

  • Elisa Zavala – Parking Operations Coordinator

  • Robin Shannon – Parking Operations (Additional support)

Responsibilities:

  • Monitor T2 data for completeness

  • Identify missing T2 transaction files

  • Contact T2 Support when required

  • Forward T2-provided files to UHS contact for upload

  • Communicate status updates to UHCL Accounting and stakeholders

  • Ensure timely notification to involved parties for any missing or corrected entries

3.2 General Accounting (UHCL)

Primary Contacts:

  • Tanjina Rahman

  • Thinh Dang

Responsibilities:

  • Conduct monthly GL reconciliations

  • Identify discrepancies between bank statements and GL entries

  • Notify Parking Operations regarding missing T2 revenue entries

  • Confirm when missing entries have been processed and posted

  • Coordinate during month-end close to ensure timely resolution

3.3 UH System (UHS)

Primary Contact:

  • Christine Ross

Responsibilities:

  • Coordinate with UH System (UH) team responsible for T2 file uploads

  • Upload T2 files received from UHCL

  • Provide updates on processing status

  • Identify additional UH contacts familiar with the process for backup support

3.4 T2 Support

Purpose: Resolve technical issues with T2-generated files or missing transactional data.

How to Contact:

  • Parking Operations to confirm official support channel (email vs. ticketing system)
    (Pending confirmation from Elisa/Robin as requested in Sheeba’s summary email.)

Responsibilities:

  • Provide missing or corrected transaction files

  • Assist UHCL Parking Operations with T2 system issues

4. Data Feed Ownership

  • Data Feed Owner: UH System (UH)

  • UHCL Point of Coordination: Christine Ross

  • Feed Actions: UH uploads files received from UHCL Parking Operations into their systems for GL posting.

5. Issue Resolution Workflow

Scenario: Missing T2 Automated Entries (e.g., September 2025 Issue)

  1. General Accounting identifies missing GL entries during reconciliation.

  2. General Accounting notifies Parking Operations (Elisa + Robin).

  3. Parking Operations verifies missing data in T2.

  4. If the file is missing or incomplete:

    • Parking Operations contacts T2 Support to request missing files.

  5. T2 provides the corrected file.

  6. Parking Operations forwards the file to UHS (Christine Ross).

  7. UHS uploads the file and confirms successful processing.

  8. Parking Operations and Accounting verify GL entries.

  9. Parking Operations communicates closure to the full distribution list.

Important Notes from 2025 Incident:

  • Missing entries for 09/08/25 – 09/30/25 were corrected.

  • T2 provided the file on 10/27/2025.

  • UHS processed all files by 10/30/2025.

  • Communication delays led to duplicated troubleshooting efforts. Future issues must involve all parties promptly.

6. Communication & Escalation Expectations

6.1 Required Notification Group

For any T2-related issue, notify:

  • Parking Operations (Elisa, Robin)

  • UHCL General Accounting (Tanjina, Thinh)

  • UHS Contact (Christine Ross)

  • OCIO (Sheeba) only if technical/ownership direction is needed

6.2 Escalation Path

  1. Parking Operations → T2 Support

  2. Parking Operations → UH System (file upload)

  3. General Accounting → Parking Operations

  4. OCIO involvement only when:

    • Clarification of system ownership is needed

    • Process documentation or governance is required

    • Inter-departmental escalation is needed

7. Known Issues & History

Recurring Issue: Missing T2 Parking entries (annual occurrence)

  • The issue occurred in previous years as well.

  • Past resolution involved:

    • Margaret Mims

    • Andrew Hoang (UH Main Campus)

Potential Cause:

  • New academic year setup in T2 may require adjustments annually.

  • Need for documented yearly configuration checklist.

8. Action Items Identified

  • Parking Operations to confirm T2 support contact method (email vs. ticket system).

  • Christine Ross to provide UH contacts who can assist in her absence.

  • Accounting to maintain documentation of previous year issues for quicker resolution.

  • OCIO to update Application Inventory with support ownership and workflow details (this document).

9. Summary

The T2 Parking System involves multiple departments—Parking Operations, UHCL Accounting, UHS, and T2 Support. Timely communication among all parties is essential to avoid duplicated efforts and ensure accurate GL posting. This KB establishes ownership, processes, and escalation structures to streamline future T2-related issues.

Details

Details

Article ID: 7861
Created
Wed 11/19/25 2:20 PM
Modified
Thu 12/11/25 8:50 AM