Product & Support Info OPSCOM has world-class support. It is our mission to delight and educate our clients on best practices for using our product. Customer Support FAQ How do I launch a support ticket? The best way to launch a support ticket is to email  support@ops-com.com . This email is monitored Monday to Friday from 9 a.m. to 5 p.m. EST. What after-hours support do you provide? After hours support is limited to critical issues . Critical is defined as system outages or issues that threaten immediate work stoppage. This support is provided by email and is staffed by on-call personnel. Issues will be triaged within 15 minutes and a status notification will be sent to you within 1 hour for Critical issues. This notification will include an estimated time to resolution. The goal is to get you back up and running as quickly as possible with minimal impact on your organization. How are upgrades delivered? Upgrades, Hotfixes and new Releases will be assessed by our Project Management Team and rolled out to clients to ensure minimal impact. In most cases, rollouts will be transparent to clients. Release notes are always available on the Upcoming Release page.  Typically OPSCOM provides a monthly release of fixes and features. The Upcoming Release page is updated as items are added. We only do rollouts on certain days to ensure that we have a maximum coverage available to support users if issues arise. In the case of a large feature release, we may decide to stage this release to our clients and work directly with them to bring them up quickly and efficiently. What provisions do you have for training? New customers get one-on-one system training as per their contract. Extra training hours can be negotiated with your Sales Rep.  The wiki has a full complement of articles, FAQs and videos to help you going forward.  The self-guided training agenda is also helpful for learning the system and each client gets a preview environment to use for testing and training. The preview spaces are secured in the same manner as our production/live systems, though they exist in a testing environment. How is your support team structured? The support team is staffed with front line and escalation agents. Front line support agents help all customers with support issues by email and Premium support customers by telephone. They also have the ability to do screen sharing if the issues requires it. Escalation points help push fixes through development and manage the customer experience as well as provide guidance to our front line agents. Do you have online resources, self-help tools? Yes, we have a public wiki available that contains articles, FAQs, videos and webinars.  What hours is telephone support available? Telephone Support is available to our Premium customers Mon-Fri 9-5 EST. Standard Plus support clients have email support only during the same hours. How does your escalation process work? Issues are escalated when the front line staff has determined through working with the customer and testing that an item is a bug. The escalation manager will assess the bug's severity and the impact it is having on the client and enter the issue into JIRA. JIRA is the system we use to track development work. The issue will be linked through JIRA to the Help Desk conversation. The client will be advised on estimated time to resolution and the Development team will address the bug. Once addressed, it will be passed to the Quality Assurance team for testing. The client will be informed that the issue is addressed and available through the original Support ticket. Please note, depending on the severity of the bug and the availability of a workaround, fix times can range from one (1) day to many months. Product Information Sheets Welcome to our Information Gallery Feel free to download our .pdf files to help you better understand the many features and abilities of the  Operations Commander   platform. Why OPSCOM One System Handhelds ParkAdmin ViolationAdmin IncidentAdmin Text2ParkMe Temp Permits OPSCOM LPR OPSCOM Glossary of Terms Detailed Definitions   Primary Driver The designation of Primary Driver is put in place to identify the owner of a vehicle in most cases. A vehicle can be in the system under two user profiles however there should only be one primary driver. The Primary Driver will receive communication from the system such as violation notices. There is a nightly script that runs which will designate primary driver to any vehicle that has been added to the system.  If there is no Primary Driver on a vehicle when an appeal is launched, the person launching the appeal will be automatically designated as the Primary Driver. DNTT A DNTT Note ( Do Not Ticket or Tow) information is used to notify enforcement officers that a particular vehicle should not receive any violations in a particular lot, during a particular date and time.  Multiple Offences An administrator can add multiple Offences to a single Violation (ticket).  Spoiled   This is used to cancel a manual ticket if  an officer has started to write a manual violation and then VOIDS it. This could occur when an officer makes a mistake on the ticket or the person at fault comes back to their vehicle and moves it.  The violation is marked "Spoiled" as paper violations are incrementally numbered and must be accounted for. User Profile icon  This is the icon that is used to link back to the User Profile information Rollover A rollover is an action taken at the end of a  term/year, in which all assigned permits for a select group ( I.e  staff/faculty) are carried over to the next term/year.  This means that a faculty member with Permit A1 for the fall term, will continue to have Permit A1 in the winter term, as the permit was part of a  rollover .    Rollovers may be applied to all permits (in this case: parking) or to a selected group of permits.  Admins may choose to rollover permits (carry the permit to the next term) while automatically deducting the cost of the permit (or charging individuals – payroll  deduc tion  usually in the case of faculty) OR they can choose to not do any rollovers.    Rollover is an optional function and does not HAVE to happen, but makes the  assign ment  of permits much easier if a selected group of users (ex. Full time staff/faculty) continue to carry the same permit, rather that being reassigned a new permit every term.    Merge Users Merge Users is a process in OPSCOM that allows administrators to take two user profiles (usually one has been created in error) and merge (combine, blend) the two user profiles into one user. All user information including history with be merged to the new user.  Merge Vehicles Merge Vehicles is a process in OPSCOM that allows administrators to take two vehicles and merge them into one. This will correct vehicle duplicates that can be problematic for enforcement.  Common Lot   A Common Lot is not defined by user type, for example, a Bicycle lot. It doesn't matter if you're staff/faculty or student - you can park there if you have a bike, therefore it is a common lot.  Midnight List The Midnight list shows all permits and lockers that are reserved but have not been paid for. These items will be released back to available stock each day at midnight.  Lot Groups A lot group is a method to group similar lots. A lot may  ONLY  belong to 1 group. Lot groups exists to allow similar lots to be seen as 1 single entity for enforcement. For example: Lot 1, Lot 3, and Lot 5 are all student parking lots.  Lots 1, 3, & 5 may belong to  one lot group,  called "Student Lots". This allows officers to see that they are all student parking lots, essentially as a single entity.   Individually, these lots may have their own zones applied to them, but they may only belong to one lot group. RBAC- Role-Based Access Control Through RBAC, you can control what end-users can do at both broad and granular levels. You can designate whether the user is an administrator, a specialist user, or an end-user, and align roles and access permissions with your employees' positions in the organization. We utilize RBAC in OPSCOM to control access to functionality in the system.  Mobility (New Parking Lexicon) A term that is quickly growing more popular as a replacement to the Parking & Transportation Dept.  Many are rebranding as Mobility departments or referring to their Mobility Plan. Curbside Management (New Parking Lexicon) Curbside management in a new term cropping up in Parking and violations.  Seems to be pushed by the Smart City, Internet of Things groups.  It refers to street parking and management of the street real-estate.  Security Whitepaper As do many, we take security very seriously!  We understand that the data we have been entrusted with is data which our clients have also been entrusted with.  We always ensure that we go well above and beyond the requirements and standards for safe secure storage and handling of all data.  This white paper outlines in details some of the lengths which we go to ensure business continuity and respect for entrusted data. Executive Summary OperationsCommander (OPSCOM) is a cloud-based parking and security management platform. This platform has been developed in-house for over 15 years. Tomahawk Technologies Inc. is committed to maintaining a high level of information security, and its key priority is protecting customer information, and carefully maintaining the information security of OPSCOM. This Security Whitepaper gives an overview of the OPSCOM security features. OPSCOM is PCI SAQ D-SP 3.2.1 certified and is audited quarterly by a third-party to maintain this certification. We are also TX-RAMP Level 2 certified by the Texas Risk and Authorization Management Program (certificate ID TX1332619). The Texas Risk and Authorization Management Program provides a standardized approach for security assessment, certification, and continuous monitoring of cloud computing services that process the data of Texas state agencies. Risk analysis forms the foundation of our security program. Risk assessments are periodically performed and security is regularly discussed in weekly team meetings. Our security processes, roles, and responsibilities are clear and well defined. Everyone is aware of our responsibilities and obligations when protecting our clients data. We review our policies annually and ensure that all employees sign-off on them. OPSCOM is developed and maintained by inspired, skilled personnel who are committed to maintaining a high level of online security. OPSCOM has been designed to meet customers' strict security requirements and industry best practices. OPSCOM has a solid and secure foundation that is based on widely used security methods and protocols. It has been designed to protect data both in transit and at rest to ensure its confidentiality, integrity, and availability. Strict access control allows only authorized users to access the data. Operation and maintenance of OPSCOM follows documented processes. Continuous monitoring of information security and system performance ensures that all deviations and incidents can be responded to in a timely manner by trained and competent personnel in accordance with the incident response process. This document is designed to answer all your questions regarding the security and design of both OPSCOM and our supporting systems.  This information is now available by request from your Sales representative or from support@ops-com.comcom VPAT - Tomahawk Technologies & OperationsCommander Accessibility Conformance Report Revised Section 508 Edition - (Based on VPAT® Version 2.5Rev) Legal Disclaimer - This Voluntary Product Accessibility Template (VPAT) is provided for informational purposes only and does not constitute a legal binding claim of compliance. The information reflects the product as of the date of this report and does not cover subsequent changes or updates. While we strive for accuracy and compliance with applicable accessibility standards, we acknowledge that there may be instances of non-conformity. We encourage users to report any such instances to OperationsCommander so we can address them promptly. No liability is assumed for the accuracy of this document or the decisions made based on its content. This VPAT does not imply endorsement by any federal agency. Purpose The VPAT is a template used to document a product's conformance with accessibility standards and guidelines. The purpose of the Accessibility Conformance Report is to assist customers and buyers in making preliminary assessments regarding the availability of commercial "Electronic and Information Technology," also referred to as “Information and Communication Technology” (ICT) products and services with features that support accessibility. Legal Disclaimer This Voluntary Product Accessibility Template (VPAT) is provided for informational purposes only and does not constitute a legal binding claim of compliance. The information reflects the product as of the date of this report and does not cover subsequent changes or updates. While we strive for accuracy and compliance with applicable accessibility standards, we acknowledge that there may be instances of non-conformity. We encourage users to report any such instances to OperationsCommander so we can address them promptly. No liability is assumed for the accuracy of this document or the decisions made based on its content. This VPAT does not imply endorsement by any federal agency. Revision History Date of Change Notes August 13, 2024 Final Draft - SJ May 13, 2025 Review for Accuracy - SJ March 17, 2026 Review for Accuracy - SJ April 8, 2026 Update to WCAG 2.1 Level AA - CB Name of Product/Version: OperationsCommander - User Portal Platform: Web Report Date: March 2026 Product Description: OperationsCommander provides a cloud-based parking and enforcement management system. The online portal allows users access to manage their account, personal information, and vehicles. They can also appeal and pay violations and purchase permits. Contact Information: support@ops-com.com Evaluation Methods Used: Testing is based on knowledge of general product functionality Applicable Standards/Guidelines This report covers the degree of conformance for the following accessibility standard/guidelines: Standard/Guideline Included In Report Web Content Accessibility Guidelines 2.0 Level A (Yes) Level AA (Yes) Level AAA (Yes) Web Content Accessibility Guidelines 2.1 Level A (Yes) Level AA (Yes) Level AAA (Yes) Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 (Yes) Terms The terms used in the Conformance Level information are defined as follows: Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation. Partially Supports: Some functionality of the product does not meet the criterion. Does Not Support: The majority of product functionality does not meet the criterion. Not Applicable: The criterion is not relevant to the product. Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria. WCAG 2.1 Report Tables 1 and 2 also document conformance with Revised Section 508:  Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing Chapter 6 – 602.3 Electronic Support Documentation Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements . Table 1: Success Criteria, Level A Criteria Conformance Level Remarks and Explanations 1.1.1 Non-text Content (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Most of the content is text. Images that are used are decorative (e.g., brand/client logos). Images presenting the vehicle type are decorative and are placed next to the text description (including the vehicle type) of the vehicle. The real-time map parking doesn’t require the map as the interface to get a permit is text-based (appears next to the map; the map is only to see where the lots are). Content mostly complies except for: The chart on the real-time map page showing the percentage of available permits has no text alternative QR Code scanning does not have a text alternative Note: The primary users for QR code scanning and real-time permit availability are drivers who are expected to be visually interactive, an accessible alternative method is provided as users can access the same page to obtain the permit directly through the app. 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: No audio or video media is used on the website 1.2.2 Captions (Prerecorded) (Level A) Also applies to: Revised Section 508 501 (Web)(Software)  504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: No audio or video media is used on the website 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: Revised Section 508 501 (Web)(Software)  504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: No audio or video media is used on the website 1.3.1 Info and Relationships (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Semantic structure and labeling complies. ARIA roles are explicitly defined to enhance accessibility. 1.3.2 Meaningful Sequence (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Logical order is followed on all pages 1.3.3 Sensory Characteristics  (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: There are no instructions that rely solely on sensory characteristics 1.4.1 Use of Color (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Links, buttons, and other interactive elements are not identified solely by color. information conveyed through color is also available through text 1.4.2 Audio Control (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Website does not play any audio or video media 2.1.1 Keyboard (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: All pages and functionality can be accessed using a keyboard 2.1.2 No Keyboard Trap (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Pages that can be accessed using a keyboard can also be exited using the keyboard 2.1.4 Character Key Shortcuts (Level A) Web: Not applicable Web: No single-character shortcuts exist. All keydown bindings use .enter or .space. 2.2.1 Timing Adjustable (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: In app notifications (success or failure messages) have a timer with a button to dismiss before the timer ends. Prior warning is given when the user’s session times out. 2.2.2 Pause, Stop, Hide (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: The application does not include moving or blinking content that needs to be paused, stopped or hidden 2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Website does not contain any flashing content 2.4.1 Bypass Blocks (Level A) Also applies to: Revised Section 508 501 (Web)(Software) – Does not apply to non-web software 504.2 (Authoring Tool) 602.3 (Support Docs) – Does not apply to non-web docs Web: Supports Web: A “skip to main content” link is provided as the first focusable element on the page, allowing keyboard users to bypass repeated navigation (e.g., the side menu with multiple items) and move directly to the primary onboarding content. 2.4.2 Page Titled (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: All pages are titled appropriately  2.4.3 Focus Order (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Interactive elements in anis in an order that follows sequences and relationships within the content 2.4.4 Link Purpose (In Context) (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Links are only used in news items that are sent by the admins to the users. The admins choose the link description that will be displayed to describe the purpose of this link 2.5.1 Pointer Gestures (Level A) Web: Supports Swipers (touch) are hidden on desktop; stacked grid shows instead. Welcome/subscriptions pages have explicit Next/Prev/Skip buttons. 2.5.2 Pointer Cancellation (Level A) Web: Supports All actions fire on (click) (up event). Only mousedown found is non-destructive (markFieldTouched). 2.5.3 Label in Name (Level A) Web: Supports Visible button text matches aria-label values across the app. 2.5.4 Motion Actuation (Level A) Web: Not applicable No device motion, accelerometer, gyroscope, or shake detection found. 3.1.1 Language of Page (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Default browser language is used 3.2.1 On Focus (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Focus on input fields does not change context 3.2.2 On Input (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Submit buttons or dialogues are provided in areas where change of context may be initiated 3.3.1 Error Identification (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Fully complies 3.3.2 Labels or Instructions (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Placeholders and/or labels are used to describe input fields 4.1.1 Parsing (Level A) Also applies to: WCAG 2.1 – Always answer ‘Supports’ Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports For WCAG 2.0, WCAG 2.1, and the 508 standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata . 4.1.2 Name, Role, Value (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Form controls elements have label elements associated to them Table 2: Success Criteria, Level AA Notes: WebAIM Contrast Checker was used to test contrast ratios Criteria Conformance Level Remarks and Explanations 1.2.4 Captions (Live) (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: No audio or video content is used on website 1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: No audio or video content is used on website 1.3.4 Orientation (Level AA) Web: Supports No CSS orientation locks found. 1.3.5 Identity Input Purpose (Level AA) Web: Partially Supports Web: Any input collecting personal info (e.g., name, email, address) needs autocomplete so browsers/assistive tech can auto-fill. 1.4.3 Contrast (Minimum) (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: The website uses more than one color combination across different pages. The measured contrast ratios are as follows: page text: 17.74:1 buttons: 7.71:1 displaying active pages on navigation bar: 6.88:1 1.4.4 Resize text (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Text and components are responsive to different screen sizes and zoom levels 1.4.5 Images of Text (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: On the manage credit card page, text is used to display credit card info instead of an image, which allows accessibility tools to be used. Only images that might contain text are just decorative (brand/client logos) 1.4.10 Reflow (Level AA) Web: Supports Responsive grid with breakpoint sizing. Content reflows at 320px. 1.4.11 Non-text Contrast (Level AA) Web: Supports Focus outlines are 3px #1a73e8 on white (high contrast). Ionic toggle/button borders meet 3:1. 1.4.12 Text Spacing (Level AA) Web: Supports No fixed heights or overflow: hidden that would clip adjusted text. Uses rem/em units. 1.4.13 Content on Hover or Focus (Level AA) Web: Supports Popovers triggered by click/keyboard (not hover), dismissible, and persistent until closed. 2.4.5 Multiple Ways (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) – Does not apply to non-web software 504.2 (Authoring Tool) 602.3 (Support Docs) – Does not apply to non-web docs Web: Supports Web: Search functionality on pages and linking to all of the pages on the site from the home page 2.4.6 Headings and Labels (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Content is described in headings and labels 2.4.7 Focus Visible (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Elements do visibility show that they have received focus  3.1.2 Language of Parts (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: The language of each passage or phrase in the content can be programmatically determined when it differs from the default language of the page. 3.2.3 Consistent Navigation (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) – Does not apply to non-web software 504.2 (Authoring Tool) 602.3 (Support Docs) – Does not apply to non-web docs Web: Supports Web: Side navigation bar is consistent on all pages 3.2.4 Consistent Identification (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) – Does not apply to non-web software 504.2 (Authoring Tool) 602.3 (Support Docs) – Does not apply to non-web docs Web: Supports Web: Using consistent identification for components with similar functionality. 3.3.3 Error Suggestion (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Form validation is provided with DOM text 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) Web: Supports Web: Financial transactions have a mechanism for reviewing, confirming, and correcting information before finalizing the submission. 4.1.3 Status Messages (Level AA) Web: Partially Supports Web: Success toasts, loading states, and cart updates are currently invisible to screen readers. Table 3: Success Criteria, Level AAA Criteria Conformance Level Remarks and Explanations 1.2.6 Sign Language (Prerecorded) (Level AAA) Revised Section 508 – Does not apply Web: Supports Web: No media content is used 1.2.7 Extended Audio Description (Prerecorded) (Level AAA) Revised Section 508 – Does not apply Web: Supports Web: No media content is used 1.2.8 Media Alternative (Prerecorded) (Level AAA) Revised Section 508 – Does not apply Web: Supports Web: No media content is used 1.2.9 Audio-only (Live) (Level AAA) Revised Section 508 – Does not apply Web: Supports Web: No media content is used 1.3.6 Identify Purpose (Level AAA) Web: Partially Supports