Skip to main content

🚀 The Evolution of OPSCOM: Introducing Project Eevee & Project Butterfly

The OPS-COM platform is currently undergoing a strategic transformation to modernize workflows and increase system flexibility. Its primary purpose is to optimize permit and lot management through new hierarchical structures and automation, significantly reducing the administrative effort required to manage complex pricing tiers. This article is intended for OPS-COM administrators interested in the upcoming architectural improvements to the system.

Setup and Configuration

As this initiative represents a fundamental architectural shift currently in active development, there are no immediate setup steps required within your live environment.

Admin Side: Administrators do not need to configure any active settings. However, familiarizing your management team with the upcoming container hierarchies and automated logic will prepare your organization for a smooth operational transition.

User Side: End-users do not need to perform any setup. They will seamlessly benefit from the enhanced workflows and interfaces as the updates are iteratively deployed to the public portal.

Understanding the Platform Enhancements

The OPS-COM development team has identified three primary areas for platform enhancement to support increasingly complex organizational needs.

Strategic Improvement Areas

  • Dynamic Sales Windows: Moving beyond the current four-allocation-type limit to confidently support an unlimited number of overlapping and staggered sales windows.

  • Unified Lot Management: Transitioning away from fragmented "Virtual Lots" to a single, intuitive hierarchical view that automatically manages multiple price points and user types.

  • Automated Rollovers: Replacing manual renewal processes with an automated, subscription-style logic to streamline term-to-term permit rollovers.

Project Eevee The Proof of Concept

To ensure the new platform architecture is completely stable, the development team is utilizing the Lockers module as the initial proof-of-concept model, internally known as Project Eevee.

Project Eevee introduces a new organizational "Container" hierarchy. This structural change allows administrators to define a price once and have it apply intelligently across the entire inventory based on user type and specific timeframes.

The Container Hierarchy: The new organizational structure allows inventory to be nested intuitively, flowing from Region → Campus → Building → Floor → Unit.

Future Development Project Butterfly

Once Project Eevee is fully proven and optimized within the locker environment, the development team will initiate Project Butterfly. This phase represents a total reimagining of the existing parking permitting system, seamlessly integrating the efficiencies, automation, and hierarchical controls developed during the Project Eevee phase into your entire parking inventory.

Best Practices and Considerations

  • Engage in active participation: Administrators are highly encouraged to share insights and feedback to help shape the final functionality. As new features like the Grid Editor and the enhanced User Portal are selectively released, your feedback is invaluable to the development cycle.

  • Monitor official updates: Keep a close watch on the OPSCOM Community to provide input on proposed changes and accurately track the progress of the transition. Active community engagement ensures your organization's specific operational needs are considered during development.

Back to top