Feature Overview (aka. Goal Summary)

This feature builds on RHDHPLAN-311, which introduced a data summarization scorecard which can be added to the homepage, and data caching mechanism to collect data for display. This should be extended to be more configurable, and more actionable, taking users to see those entities which may need attention. The primary goal is to provide a "manager view"—a specialized dashboard or report—that displays Key Performance Indicators (KPIs) aggregated across multiple owned applications or components. This directly addresses the needs of personas like Engineering Managers and Product Managers who oversee the health and compliance of numerous services but currently lack a consolidated, high-level summary.

Specifically, this enables aggregation of data points (e.g., total number of bugs) from existing data sources across all entities associated with a specific owner (e.g., a Group in the Software Catalog). 

Goals (aka. Expected User Outcomes)

• Engineering Manager / Platform Engineer: I want to define, name, and view aggregated KPIs across all applications or components owned by my team/group, so I can quickly assess overall technical health, compliance, and risk without manually checking each service's individual scorecard. 

Requirements (aka. Acceptance Criteria):

1. KPI Configuration: As a Platform Engineer, I want the Scorecard configuration interface to include an option to create an "Aggregated KPI," so I can define metrics that sum or average results across multiple entities.
2. Customizable Name/Description: After creating a KPI for their needs, a Platform Engineer should be able to provide their own name or description so the metric can be easily understood by end-users.

Out of Scope (Optional)

• Real-Time Data Processing: Aggregated data will not be updated in real-time. The initial implementation will focus on scheduled batch processing.
• Complex Custom Aggregation Logic: Advanced statistical functions, custom scripting for aggregation, or cross-entity conditional logic (beyond simple SUM/AVERAGE/etc.) are out of scope for the initial release.
• New Data Source Integrations: This feature will leverage existing data sources already integrated with the RHDH Scorecard plugin; no new external tool integrations will be developed as part of this ticket.
• Providing a management UI for Scorecard. Configuration can rely on yaml until we start building a UI driven experience in a followup feature. 

Customer Considerations (Optional)

• Large Organization Scalability: Since RHDH serves large organizations, the aggregation mechanism must be performant and scalable to handle portfolios with hundreds or thousands of components without degrading overall RHDH performance during the scheduled refresh. Caching and efficient database queries are critical.
• Role Identification: Aggregation relies heavily on the Owner field/Group entities in the Software Catalog. Ensure that the Platform Engineer configuring the KPI has clear visibility into the Group-Component relationships to correctly scope the manager view.

Documentation Considerations

• Update the existing RHDH documentation clearly explaining how to create metrics and configure all available scorecards fields.