Feature Reference

Monitoring and Alerting

The monitoring engine is the heart of Project Green. Agents deployed in customer environments continuously collect status data from devices and report it back to the platform. This data includes connectivity status, device health indicators, and operational metrics. The platform processes this data in near real time, giving users an up-to-date picture of their environment.

Alerting is built on top of the monitoring data. Alert rules define the conditions under which a notification should be generated, such as a device going offline, a metric exceeding a threshold, or a pattern of intermittent connectivity. Alerts are categorized by severity and can be routed to different users or teams based on the alert type and location.

The alerting system supports acknowledgment and resolution workflows, so teams can track the lifecycle of each issue from detection through remediation. Alerts can be resolved manually or automatically when the triggering condition clears. Historical alert data is retained for reporting and trend analysis.

Dashboard and Visualization

Dashboards provide a visual overview of the customer's monitored environment through configurable widgets. Each widget displays a specific piece of information, such as room health summaries, alert severity breakdowns, device status charts, or trend lines. Users can customize their dashboards by adding, removing, resizing, and rearranging widgets.

The platform supports multiple saved dashboard layouts, allowing users to switch between views tailored to different tasks or roles. For example, a daily operations dashboard might focus on active alerts and room status, while a weekly review dashboard might emphasize trends and historical metrics.

Widgets are interactive. Clicking on a data point in a widget typically navigates the user to a detailed view with more context. This drill-down capability means the dashboard serves as both a summary view and an entry point into deeper investigation.

Room and Device Management

Rooms and devices are the core organizational objects in the platform. Each room represents a physical space and contains one or more monitored devices. Rooms are organized into buildings and floors, creating a hierarchy that mirrors the customer's physical estate.

Device management includes the ability to add, remove, and reconfigure devices within rooms. Each device has a type, a connectivity status, and a history of alerts and status changes. The platform tracks device health over time, enabling customers to identify chronic issues and make informed decisions about maintenance and replacement.

Room health is derived from the status of its devices. A room with all devices online is healthy. A room with one or more devices offline or degraded shows a corresponding health indicator. This composite health model makes it easy for customers to monitor large numbers of rooms without checking each device individually.

Multi-Tenancy

Multi-tenancy allows a single platform instance to serve multiple customers or business units with full data isolation. Each tenant has its own set of rooms, devices, users, and configurations. Users in one tenant cannot see or interact with data from another tenant.

This feature is essential for managed service providers and AV integrators who operate the platform on behalf of multiple clients. It is also useful for large enterprises that want to keep data separate between divisions, regions, or subsidiaries.

Tenant management is handled by platform administrators who can create new tenants, assign users to tenants, and configure tenant-specific settings. The multi-tenancy model is designed to scale efficiently, so adding new tenants does not impact the performance or availability of existing ones.

API and Integrations

Project Green provides an API that allows external systems to access monitoring data, manage resources, and trigger actions programmatically. The API is useful for customers who want to integrate Project Green data into their existing IT management tools, build custom dashboards, or automate operational workflows.

Common integration scenarios include pushing alerts to IT service management platforms for ticket creation, sending notifications to team communication channels, and pulling monitoring data into enterprise reporting tools. The API is documented and follows standard REST conventions, making it accessible to developers with common web development skills.

The platform may also offer pre-built integrations with popular tools, reducing the development effort required for common use cases. Check the current integration catalog for available connectors and refer to the API documentation for custom integration work.

Reporting

The reporting feature provides structured views of monitoring data over defined time periods. Reports can cover topics such as device uptime, alert volume and response times, room utilization, and overall environment health. They are useful for periodic reviews, management updates, and SLA tracking.

Reports can typically be generated on demand or scheduled for automatic delivery. Scheduled reports are sent via email at the configured interval, such as weekly or monthly, ensuring that stakeholders receive regular updates without needing to log into the platform.

Report outputs may include charts, tables, and summary statistics. Some reports can be exported in common formats like PDF or CSV for sharing with people who do not have platform access. The reporting capabilities are designed to turn monitoring data into actionable business intelligence.