**Single Sign-On (SSO)** offers a streamlined and secure way for your organization's users to access OPSCOM. Instead of managing separate usernames and passwords for OPSCOM, users can log in once using their existing company or institutional credentials, gaining seamless access to various services, including OPSCOM. This simplifies the login experience and enhances overall security.
### What is Single Sign-On (SSO)? At its core, SSO is about simplifying access. Imagine having one key that opens multiple doors. With SSO, that key is your single set of login credentials (username and password) that grants you access to various online applications and websites. Many organizations use SSO to provide their employees or members easy and consistent access to all their digital tools. When OPSCOM is integrated into your SSO system, your users can access our services without needing to create or remember another distinct account. ##### How SSO Works in a Simple Way SSO acts like a central gatekeeper for your online services: 1. **You Request Access**: When you try to log in to an online tool or website (like your work email or a school portal), the system recognizes it's an SSO-enabled service. 2. **Redirection to SSO**: Instead of asking for your username and password directly, the website sends you to a dedicated SSO service – a trusted system specifically designed to handle logins for all your integrated applications. 3. **Your Single Login**: On this SSO service page, you'll enter your username and password. This is the *only* time you'll need to enter these details to access multiple integrated services. 4. **Verification**: The SSO service checks your login information. Once it confirms your identity, it creates a secure, temporary "digital pass" or token. 5. **Return to OPSCOM**: This "digital pass" is securely sent back to OPSCOM (or the original application you wanted to access). 6. **Access Granted**: OPSCOM recognizes and trusts this "digital pass," allowing you to immediately access your account and start using the system without any further login prompts. ##### Why Organizations Use SSO - **Convenience**: Users only need to remember one set of login details for multiple applications. - **Time-Saving**: Quick and effortless access to various services eliminates the need to repeatedly log in, improving productivity. - **Enhanced Security**: With fewer passwords to manage, users are less likely to create weak passwords, reuse them across sites, or write them down, which generally leads to stronger overall security. ### Key Considerations Before Setting Up SSO with OPSCOM Implementing SSO requires planning and coordination to ensure it aligns with your organization's specific needs and security protocols. - **Investment Required**: SSO is a **premium feature** within OPSCOM. There is a setup fee and recurring fees associated with its functionality. To begin the process and discuss pricing, please contact your Sales Representative or email [support@ops-com.com](mailto:support@ops-com.comcom). - **User Types and Access**: - Will certain groups of users (e.g., students, staff) use SSO, while others (e.g., the general public) continue to use a direct OPSCOM login? - Do you need different login methods for different user types? - **User Data Management**: - How do you prefer to get your user accounts into OPSCOM initially? - Do you want new user accounts to be created automatically "on the fly" when a user logs in via SSO for the very first time? - Do you need user information in OPSCOM to automatically stay synchronized with your main organizational system (Identity Provider) over time, or is a one-time import sufficient? - Which specific user details (like name, email, student ID) from your existing system do you want to be shared and synchronized with OPSCOM? Our Client Success team is ready to guide you through these important considerations and help tailor the SSO setup for your organization's success and seamless operation. # Custom Development Expectations ## Planning & Scope For clients wishing to pay for custom development, it is critical that a well thought out scope is developed with your Account Executive (AE). If you are designing the scope with the AE we consider you the project lead for your organization. It is important to provide us with workflow documentation, explanations of the problem you are trying to solve with your custom development and your ideal end result. There are 2 areas you need to consider: - Goals - Requirements ## Goals - What are You trying to do? What is the end goal or specific outcome you want. For example, you may wish to simplify the user experience or issue violations more efficiently. Provide us with as much detail as possible. ## Requirements Clearly, define all the processes you want in a step by step description. The following is a brief example: - Adding a user’s middle initial to their profile - Is this a mandatory field in the profile? - Will all Users be prompted to update their profiles? Will it be on next login? - What if they don’t have a middle initial? - Once instituted will the initial be required on reports? If so which ones? - Will it be required to be populated on violations? - Consider all aspects that the change will affect and address them. Our development team needs to understand the objectives to design you the best solution. It is not necessary to dictate the solution just to define the end result. Try to assume that you are explaining this to a person that doesn't understand any of the processes and are reading about this for the first time. Your scope documents will be supplied to Development through the Project Manager. You may get questions back that need to be answered before we can proceed. You may also get redirection in the plan so that the solution flows better than originally scoped. ## Shared Development If the custom development requested is deemed to be of enough benefit to other clients, the OPSCOM team may propose a reduced development rate or a shared development plan. In some cases, your account executive will be aware of other clients that may be interested in crowd-sourcing this development. ## Testing Your completed project will be deployed to your preview (testing) environment after internal testing is complete. We expect you to review the project to ensure you are happy with the way it is functioning and give us the OK to deploy it to Production. We expect that you will do the testing within 2 weeks of the deployment to Preview. If your testing takes longer than that, additional charges can be incurred and you may lose your spot in the schedule. ## Out of Scope Items Despite best efforts, sometimes something gets overlooked when scoping the project. These items will be considered Out of Scope and may cost additional time and money. Your Account Executive will work with you to develop new scope around these items and a new quote will be issued for the additional work. # Supported Browsers, Handhelds, and Printers ## Supported Browsers OperationsCommander recognizes that our users may use various Internet Browsers when working with our system. We aim for all visitors to have the best possible experience while using OPSCOM, however, we do recognize that it is impossible to develop applications that work identically, efficiently and effectively on all web browsers. We make best efforts to support support the latest versions of Internet Explorer, Firefox, Chrome, and Safari browsers. ## Mobile Devices and Tablets This site supports browsing from most Mobile or Tablet devices. Content is sized and displayed based on the screen resolution and other display attributes of your device. ### OPSCOM Ionic for iOS & Android - **OPSCOM Enforce** A refreshed and smoother admin enforcement app currently in beta testing with select clients, compatible with both iOS and Android. Not yet feature complete. [More details can be found here.](https://opscom.wiki/books/opscom-enforce-ios-android) ### OPSCOM Legacy (Android Only) - **OPSCOM Parking Enforcement** The ViolationAdmin component provides in-field remote data access from mobile devices and smartphones. Using an Android handheld and a Bluetooth printer creating tickets for parking infractions is quick and easy. Site patrols sync enforcement and parking data to the system through cellular or Wi-Fi networks. With this remote technology, the system can apply validation rules moments after a user makes a permit purchase on the cloud-based user portal or connected remote devices. [More details can be found here.](https://opscom.wiki/books/legacy-android-enforcement-app-OPSCOM-parking-enforcement) ### Minimum Handheld Requirements Not all Tablets or Mobile devices are supported for use with OPSCOM, as processing power and camera functions may vary. They must have at least the requirements listed below. Before committing to a device for use with OPSCOM, you are encouraged to perform your own testing to ensure you are happy with the perform on your preferred device. OPSCOM no longer supports versions of the Android operating system lower than 7. Clients with devices that do not support at least version 7 will continue to function, however, you will not be able to download this or future versions of OPSCOM. This means you cannot take advantage of new functionality in future releases. - OS Version - Minimum: - Android, Version 11.0 (Red Velvet; 2020) - iOS, Version 13.0 or later - Minimum Processing Power - Quadcore: 4X 1.2 GHz - Rear Camera: 8 MP Camera - Autofocus - Yes - LTE/4G and/or Wi-Fi Connectivity 11 LTE/4G or better is required if connecting with cellular providers and Wi-Fi is not available *(**required** for data sync)*.
#### Recommended Tablet Specifications - Samsung Galaxy Tab Active Pro Tablets with LTE & data plan, 8 or 10" - Samsung Galaxy Tab A 8 or 10” Tablet with LTE & data plan - iPad Wi-Fi + Cellular model - iPad mini Wi-Fi + Cellular modelThe Galaxy Tab Active Pro typically comes with its own heavy-duty rugged case. iOS tablets usually don’t, though, so keep that in mind—you may want to pick one up yourself!
#### Recommended Cellphones - Samsung Flagship Cellphones, S20 through S24 (OPSCOM Testing Devices) - Samsung XCover 4 & data plan - Any mid-range or better Android phone 22 While such devices are generally expected to work, they have not been tested and may display layout irregularities. As such, full functionality cannot be guaranteed.
### Supported Bluetooth Printers Below is a list of supported Bluetooth printer models. Other models and makes may require custom development to support them. The printer must use 3" printer rolls in order to be compatible with our layout design.| Printer Model |
|---|
| - Star Micronics SM-T300-DB50 3" Portable Printer or equivalent |
- Star Micronics SM-T301-DB50 Portable Printer with Magnetic Stripe Reader or equivalent
|
| - Zebra ZQ320+ Series Bluetooth Printer No label sensor - Outdoor edition - Charger sold separately |
| - Zebra ZQ620+ Series Bluetooth Printer No label sensor - Outdoor edition - Charger sold separately |
| - Zebra Charging Accessory Kit sold separately |
| - Zebra In Vehicle Charging Accessory Kit sold separately |
Sending email from OPSCOM is a key element of communicating with your clients. This communication may be outgoing messages related to purchases, notifications and even as part of the appeals process. These are important messages and you want them to get to your clients quickly, securely and without ending up in spam. This guide offers information on setting up your domain with our preferred mail partner, [Mailgun](https://www.mailgun.com/), to ensure your messages are delivered effectively. We selected Mailgun as our preferred email partner due to the ease of use of their APIs and their long standing success in the email space. That together with their tools to track and report on sent emails made them an ideal candidate for email management.
### Why is this so important? When you send emails from a properly configured domain, internet service providers (ISPs) can confirm that you are a legitimate sender. This process, which relies on DNS records like SPF and DKIM, ensures your emails are not marked as spam. Using your own domain also projects a professional image and builds trust with your clients, as the emails will appear to come from a trusted source (e.g., `parking@yourdomain.com`). Without this setup, emails sent from a non-`yourdomain.com` system may be marked as spam or carry an "on behalf of" header, which can make your brand appear less credible. ##### Why Do I See On Behalf Of in My Email Visit [https://help.mailgun.com/hc/en-us/articles/360012491394-Why-Do-I-See-On-Behalf-Of-in-My-Email-](https://help.mailgun.com/hc/en-us/articles/360012491394-Why-Do-I-See-On-Behalf-Of-in-My-Email-) for more information ### Setup Options for Your Organization OPSCOM offers a few different ways to configure your email sending with Mailgun. The recommended method is to allow our team to manage this for you, which ensures the best support and easiest setup. ##### Recommended: Configuring Your SubDomain on the OPSCOM Mailgun Account This method is the preferred option as it allows our support team to monitor email deliverability, track issues, and provide direct technical support for your email-sending needs. It simplifies the process for you while giving us the necessary access to ensure everything is working correctly.You will need your IT team to support you through this process.
**Part 1: Your Role (Client)** 1. Inform the OPSCOM team of the domain you want to use for email sending (e.g. yourdomain.com). 2. Our team will add your domain to our Mailgun account. We will then provide you with the specific DNS records you must add to your domain's settings. These records will include:| **Type** | **Hostname** | **Value** | **Notes** |
| TXT | **opscom**.<your\_domain> | v=spf1 include:mailgun.org ~all | add an SPF for Mailgun |
| TXT | **smtp.\_domainkey.opscom.<**your\_domain> | generated DKIM key | DKIM key used with Mailgun |
**Note:** Mailgun also recommends adding other records for email tracking, but these are not required for this specific setup with OPSCOM.
##### Option 2: Using Your Own Mailgun Account This method is for clients who wish to have full control over their own Mailgun account. This can be beneficial if you have other systems that use Mailgun and you want to consolidate them. 1. Create a Mailgun Account: Go to the Mailgun website and create a new account. 2. Add and Verify Your Domain: Follow Mailgun's instructions to add your domain and verify it by updating your DNS records. 3. **Find the API Key:** Once your domain is verified, find your **Private API Key** in the **API Security** section of your Mailgun dashboard. 4. **Send to Support:** Send your Private API Key toFor clients that cannot take advantage of our User Import APIs, our SFTP Managed User Import allows you to import users into our system through an encrypted SFTP client. Any users that have failed to be imported will be put into a .csv file and sent to you by email. This file will include important user information as well as the reason for failure. Note - This is a paid process you must contact OPSCOM to see if this is included in your service.
### Required System Settings Before you can use the Managed User Import you will need to have it set up on your system. 1. Hover over **System Configuration** and click **System Settings**. 2. On the General System Settings tab, locate the **Reply-to Admin Email Address** in the **System Emails section.** This is the system default email address that appears as the sender of system-level and task-automation email messages. 3. Click Save Settings. 4. Next, click the **Third Party** tab, and locate the **CSV User Import** section. 5. Enter an email address in the **Failed Import Email** box. This is the email that will be notified in the case of a failed import. Any failed file will include information about the user as well as why the user failed to be imported. This will allow you to correct any failures and attempt the import again. 6. OPSCOM will supply you with credentials to connect your SFTP client to the folder where the import file will be stored on the server. If you connect with a standard client, you will see an empty directory where you can drag and drop your import files. ### Importing Users ##### SFTP Manual Process OPSCOM will enable a system task to run at 5 minute intervals. There may be a pause of up to 5 minutes for the import process to complete. 1\. To begin drop a comma separated (CSV) file from your computer to the server.Please note that the **your CSV file must follow the required format** to be processed correctly. Refer to **[this wiki article](https://opscom.wiki/books/api-documentation/page/push-api-user-createupdate)** to find the exact syntax for the column headers you want to use. You will find this in the **Request Object Attributes** section. The column headers must match the exact value in the **PossibleNames** column or it will fail.
 2\. Once completed the file will be automatically moved to the .**bak** folder. This folder is created as part of the import process if the folder does not exist. 3\. An email will be generated containing users that failed the import, and it will be sent to the email in **System Settings**. The email will describe the reasons that users failed the import. # Server IP Addresses Depending on various client project requirements you or your I.T. department may require server IP addresses. For example, there may be IP restrictions or traffic routing requirements where an IP address is required. The IPs listed here are egress traffic. ## Development, Testing and Preview For development and preview sites, traffic will originate from one of these IP addresses. **208.124.170.242** **178.128.233.75** **134.122.33.16** **137.184.172.18** **137.184.172.19** ## Production, Staging and Beta For production and staging sites, traffic will originate from one of these IP addresses. **209.217.117.82** **209.217.117.84** **209.217.117.88** **159.203.14.67** **167.99.176.52** **167.99.176.218** ## SPF Records for Email Tomahawk mail servers and Mailgun mail service are used for email delivery. Tomahawk mail services are being phased out and replaced with Mailgun services The following is a sample TXT record from DNS. "v=spf1 include:spf.tomahawk.ca include:mailgun.org ~all" # Boot Management and Self-Release SystemThis article provides a comprehensive overview of the Boot Management and Self-Release System. This feature allows enforcement officers to apply a physical boot to a vehicle and enables the vehicle owner to pay their violation(s) and receive a release code via email to remove the boot themselves.
The self-release boot system is designed to increase operational efficiency, reduce administrative and labor costs, and provide a more convenient resolution process for end-users. ### Setup and Configuration To use the boot management system, an administrator must first enable and configure several settings within the admin portal. ##### System-Wide Settings - Go to **System Configuration**, then **System Settings**. - Locate the **Third Party** section. - Enable the **Universal Boot Enabled** checkbox to turn the entire feature on. - Configure the **Require Overdue Paid** checkbox. You can choose to require a user to pay only the violation associated with the boot **(Disabled)** or pay all overdue violations on their account **(Enabled)** before the release code is sent. This setting is deployed Off by default. ##### Boot Inventory Setup You must create an inventory of your physical boots before they can be assigned to violations. - Go to **System Configuration**, then **Violations**, and click on **Setup Boot Devices**. - Click **+** in the top right to **Add Booting Device**. - Enter a descriptive Name (e.g., "**Red Boot 01**") and the corresponding **Boot Release Code**. - Click **Save**. Repeat for all boots in your inventory. You can edit the name and release code value here at any time.Editing the **Release Code** value will only change the code that is stored in OPSCOM and sent to user for boot release. It must be obtained from the booting device's instructions *first* and updated as necessary.
##### Violation Type Configuration You must specify which violation types are eligible for booting. - Go to Violations, and click Offence Items. - Select the specific offence type you wish to make eligible for booting. - Enable the **Apply Boot** checkbox where required.The option to apply a boot on a violation will only appear if an offence item, with the Apply Boot flag enabled, is added to the violation. Apply Boot should only be enabled on a single offence item dedicated to applying a boot. Do not enable it on a regular offence item. When a boot is returned, the fine amount of all offence items on the current violation, with the Apply Boot flag, will be included in the deposit refund. The Apply Discount setting will be greyed out when Apply Boot is enabled to prevent calculation errors, as the boot refund does not consider discounts in its calculation.
- Click Save. When this offence type is selected during violation entry, the option to assign a boot will now appear. ##### Email Template Customization The email containing the release code and instructions is customizable. - Go to **System Configuration**, then **Content and Design**, and click **Email Templates**. - Locate and select the **Boot Release** email template. - Customize the content to include specific instructions for how the user should remove the boot and ***where they should return it**.* - Click Save. ### Using this Feature This section details the daily operational use of the boot management system, from issuing a booted violation to managing the boot's return. ##### Issuing a Booted Violation When issuing a violation for a boot-eligible offense, both on the handheld device and in the admin portal, the officer will see a new option. - During the violation entry process, select the ticket type **Boot Applied** - A dropdown called field, **Apply Boot**, will appear. - From the dropdown menu, select the boot being applied to the vehicle. The list will show available boots first. - Complete and save the violation as usual. The system now logs that the selected boot is In Use and linked to this violation.You MUST make sure you **do not assign an occupied boot to another vehicle.** If no boots are marked as ***Available***, the list will start with a title saying either ***Released*** or ***Issued***. **Issued** boots are currently occupied, while **Released** means that the code was sent to the user and payment received for the violation, but **the boot hasn't necessarily been returned**.
### The User Payment and Release Process Once a vehicle is booted, the user must pay the required violation(s) to receive the release code. - The user can pay via the online portal, either by logging into their account or using the [Guest Payment option](https://opscom.wiki/books/OPSCOM-user-portal/page/quick-easy-guest-payments). - When a violation with an associated boot is in the payment cart, a boot icon will be displayed next to it. - Upon successful payment, the system automatically sends the Boot Release Email to the user's provided email address. This email contains the release code and return instructions you configured in the template.A valid email address is mandatory to complete the payment. Logged-in users must have an email on file, and guest users will be required to enter one before checkout. (They do not need an account)
### Boot Device Report This report is your central hub for tracking the status of all your boots. To access it, go to **Violations**, and and click **Universal Boot Devices.** ##### Key Information Displayed - **Boot Identifier**: The name of the boot. - **Violation Ticket Number**: The linked violation. - **Status**: The current status of the boot (In Use, Released/Not Returned, or Returned). - **Date Created**: When the boot was assigned to the violation. And if applicable; - **Date Released:** When the payment was made and the code was sent. - **Date Returned:** When an admin marked the boot as physically returned. ##### Available Actions From the report, administrators can perform key actions: - **Mark as Returned**: When a user returns a boot, locate it in the report and click **Edit** button, and select **Return** from the *status* dropdown. This updates the boot's status to Returned, making it available for reuse. - **Manage Deposit Refund**: If the boot was issued with a deposit, you will have an option to Process Refund when marking the boot as returned. This initiates the standard refund process for the deposit amount. - **For example,** you may choose NOT to issue the refund of the boot deposit, if the boot is damaged, or was not returned in satisfactory condition. --- ### Best Practices and Considerations - Develop a Business Rule for Non-Returns: It's crucial to establish a clear policy for handling boots that are not returned. This may involve applying additional fines or fees to the user's account after a specified period. - Consider using the Boot as a Deposit functionality for high-risk situations. By adding a separate, refundable fee item to the violation, you create a financial incentive for the user to return the equipment promptly. - Keep Inventory Accurate: Regularly audit your physical boots against the Boot Management Report to ensure all information, especially release codes and statuses, is correct. - Clear Email Instructions: Ensure your Boot Release Email template provides simple, clear, and comprehensive instructions. Including photos or diagrams of the boot removal process and a map to the drop-off location can greatly improve the user experience and increase return rates. # PeopleSoft Integration for Payments and HoldsThis article outlines the OPSCOM **integration process with PeopleSoft**, designed for administrators at organizations using PeopleSoft for student and staff account management. The integration uses a scheduled SFTP data transfer to place or release account holds in PeopleSoft based on outstanding violation balances recorded in OPSCOM. This ensures that parking enforcement actions are reflected in the central institutional system.
### Setup & ConfigurationIf you want to use people soft integration, **you must contact [OPSCOM Support](mailto:support@ops-com.comcom)** and have them enable a setting for you on your system before you start. Once completed, continue with the steps below.
Peoplesoft Reports are sent by email on a regularly scheduled basis, so for this feature to work you will need to decide on an email address that will be used and monitored for PeopleSoft Holds reporting, then the System Task will need to be enabled to run automatically. - Go to **System Configuration**, and click **System Settings**. - Click on the tab labeled **Third Party** - Scroll to the bottom, and under **PeopleSoft Holds**, enter an email address in the box for **PeopleSoft Holds Notification Email** - Then navigate to the **Tools** menu, and click on **View System Task Logs**. Find PeopleSoft Holds Report and click on the checkbox to Enabled. Your report will run immediately and then schedule for the next frequency.The **PeopleSoft** report is delivered by email, so this is required for functionality.
The integration is an automated process that ***requires*** initial setup and **coordination between your organization and the OPSCOM support team**. The primary components are data mapping, and scheduling. 1. **Initial Consultation & Data Mapping** The first step is to define the data fields for the export. The standard process pushes key details required by PeopleSoft to create and manage holds. Common fields include: - Student/Staff ID - Total Amount Owed - User Type (Student, Staff, etc.) - Violation Type - Violation Date 2. **File Structure and Scheduling** The integration relies on two distinct files, which are generated and delivered on a mutually agreed-upon schedule (e.g., nightly). - **Holds Added File:** This file contains a list of all users with a new or updated outstanding balance. The amount provided is the final total owed and is intended to overwrite any existing hold value in PeopleSoft. - **Holds Released File:** This file contains a list of all users whose outstanding balance has been cleared ($0.00). This file signals PeopleSoft to release the account hold. 3. **Testing and Verification** Before going live, the OPSCOM team can provide a test account and sample data files. This allows your IT team to schedule testing, verify record uploads, and ensure the data mapping is correct within your PeopleSoft environment. ### Using this Feature Once configured, the PeopleSoft integration is a fully automated background process that requires no daily intervention from an administrator. ##### How it Works - On the configured schedule, OPSCOM generates the **Holds Added** and **Holds Released** files based on real-time user account data. - These files are automatically filed, and emailed to the designated email address configured earlier, in settings. The filename can be customized, but the field structure and file type (e.g., tab-separated `.txt`) must remain consistent. - Your internal **PeopleSoft** system must be configured to automatically retrieve and process these files from the emails, to update the account holds accordingly. - You can configure the body of the **PeopleSoft** reporting email under; - Go to **System Configuration**, then **Content and Designs**, and click on **Email Templates** - Select the template labeled **PeopleSoft Holds Report** --- ### Best Practices & Considerations - **Keep the System of Record Clear.** **The financial debt should remain exclusively within OPSCOM.** The integration's purpose is only to share an *indicator* of the debt with PeopleSoft to manage holds. This strategy eliminates the risk of fees being paid in two different systems and simplifies reconciliation. - **Establish a Consistent Schedule.** While the report schedule can be customized (e.g., daily, weekly), a daily overnight process is recommended to ensure holds are applied and released in a timely manner. - **Coordinate with your IT Team.** Successful implementation requires collaboration with your organization's PeopleSoft administrators to ensure files are processed correctly on your end. - **Understand Hold Triggers.** The integration is typically configured for violation-related debts only. Any unpaid violation, regardless of the amount, will result in a user being included in the **Holds Added** file.