{ "examples": [ { "accent": "#6d20ff", "data": "talent-acquisition/data.csv", "description": "Inspired by the bright violet recruiting reference with a full application shell, compact KPI cards, stage-flow analysis, and a candidate work queue.", "expected": "KPI totals, stage charts, gender mix, role demand, and candidate records render from one application-level dataset and cross-highlight by source row lineage.", "folder": "talent-acquisition", "id": "talent-acquisition", "limitations": "Profile photography is replaced by safe initials and bundled icons so the example remains offline and Power BI portable.", "powerBiPackage": "core", "project": "talent-acquisition/project.hyperpbi", "referenceImages": [ 1, 3 ], "runtime": "talent-acquisition/runtime.json", "slug": "talent-acquisition", "specification": "talent-acquisition/specification.json", "summary": "A polished recruiting workspace with application flow, candidate mix, open roles, and recent applicants.", "tags": [ "recruiting", "workforce", "app-shell" ], "theme": "light", "title": "Talent Acquisition Command Center", "useCase": "Recruiting and workforce analytics" }, { "accent": "#1769aa", "data": "capital-project-controls/data.csv", "description": "A clean project-controlling canvas modeled after the white-and-blue reference, with precise status cards and earned-value visuals.", "expected": "Summary values use first-row semantics, monthly curves remain ordered, and cost composition traces back to cost-category rows.", "folder": "capital-project-controls", "id": "capital-project-controls", "limitations": "The example represents one selected project; use a report slicer or external filter to select other projects in Power BI.", "powerBiPackage": "core", "project": "capital-project-controls/project.hyperpbi", "referenceImages": [ 2 ], "runtime": "capital-project-controls/runtime.json", "slug": "capital-project-controls", "specification": "capital-project-controls/specification.json", "summary": "Project identity, commercial KPIs, earned-value gauges, development curves, and cost composition.", "tags": [ "projects", "construction", "finance" ], "theme": "light", "title": "Capital Project Controls", "useCase": "Construction and capital-program control" }, { "accent": "#ff704f", "data": "retail-sales-operations/data.csv", "description": "Combines the warm Productly visual language with portable semantic charts and a practical order work queue.", "expected": "Monthly revenue, category share, recent orders, and upcoming payments all resolve from logical views over one sparse retail dataset.", "folder": "retail-sales-operations", "id": "retail-sales-operations", "limitations": "The balance card is illustrative and does not initiate payments or connect to a financial institution.", "powerBiPackage": "core", "project": "retail-sales-operations/project.hyperpbi", "referenceImages": [ 4, 12 ], "runtime": "retail-sales-operations/runtime.json", "slug": "retail-sales-operations", "specification": "retail-sales-operations/specification.json", "summary": "A coral-and-navy retail dashboard with revenue trends, category mix, order detail, and settlement reminders.", "tags": [ "retail", "sales", "ecommerce" ], "theme": "light", "title": "Retail Sales Operations", "useCase": "Retail, ecommerce, and cash-flow monitoring" }, { "accent": "#6857e5", "data": "urban-mobility-command-center/data.csv", "description": "Adapts the compact violet mobility reference into a responsive Power BI map dashboard with analytical selection.", "expected": "Map points fit the dataset, status legend selection links to other components, and route summaries retain contributing Power BI row identities.", "folder": "urban-mobility-command-center", "id": "urban-mobility-command-center", "limitations": "Street tiles require the Maps PBIVIZ profile, declared OpenStreetMap WebAccess, and network access in the host.", "powerBiPackage": "maps", "project": "urban-mobility-command-center/project.hyperpbi", "referenceImages": [ 5 ], "runtime": "urban-mobility-command-center/runtime.json", "slug": "urban-mobility-command-center", "specification": "urban-mobility-command-center/specification.json", "summary": "A map-first fleet workspace with live status, demand, battery health, usage trend, and busy-route detail.", "tags": [ "mobility", "map", "fleet" ], "theme": "light", "title": "Urban Mobility Command Center", "useCase": "Fleet, micromobility, and route operations" }, { "accent": "#2eb7ee", "data": "patient-care-operations/data.csv", "description": "Translates the airy blue-and-mint healthcare reference into a safe, accessible operational workspace.", "expected": "Patient-level data drives aggregate KPIs, daily and departmental charts, and a selectable active-patient work queue.", "folder": "patient-care-operations", "id": "patient-care-operations", "limitations": "All people and clinical events are synthetic; the dashboard is not intended for diagnosis or real patient decisions.", "powerBiPackage": "core", "project": "patient-care-operations/project.hyperpbi", "referenceImages": [ 6 ], "runtime": "patient-care-operations/runtime.json", "slug": "patient-care-operations", "specification": "patient-care-operations/specification.json", "summary": "A calm clinical operations dashboard for alerts, patient demand, review mix, department load, and response queues.", "tags": [ "healthcare", "operations", "patients" ], "theme": "light", "title": "Patient Care Operations", "useCase": "Healthcare capacity and patient-flow analytics" }, { "accent": "#2596ff", "data": "digital-banking-overview/data.csv", "description": "Captures the midnight Paycent reference with neon accents and a safe CSS-rendered card that works offline.", "expected": "Account summary values, monthly debit/credit activity, category spending, and recent transactions render responsively from one source.", "folder": "digital-banking-overview", "id": "digital-banking-overview", "limitations": "The payment card is a decorative dashboard element and never exposes or processes real card credentials.", "powerBiPackage": "core", "project": "digital-banking-overview/project.hyperpbi", "referenceImages": [ 8 ], "runtime": "digital-banking-overview/runtime.json", "slug": "digital-banking-overview", "specification": "digital-banking-overview/specification.json", "summary": "A responsive dark banking workspace with balance cards, transaction history, spending mix, and account detail.", "tags": [ "banking", "transactions", "responsive" ], "theme": "dark", "title": "Digital Banking Overview", "useCase": "Personal banking and transaction analytics" }, { "accent": "#21d4fd", "data": "media-web-performance/data.csv", "description": "Blends the coral-framed monitoring reference and the dense website KPI wall into one practical growth dashboard.", "expected": "Summary metrics, daily trends, medium performance, bounce gauge, and live-location list render from explicit logical record types.", "folder": "media-web-performance", "id": "media-web-performance", "limitations": "Location data is shown as a portable ranked list; this Core-profile example intentionally avoids external map tiles.", "powerBiPackage": "core", "project": "media-web-performance/project.hyperpbi", "referenceImages": [ 7, 11 ], "runtime": "media-web-performance/runtime.json", "slug": "media-web-performance", "specification": "media-web-performance/specification.json", "summary": "A dark editorial command board combining media monitoring with website conversion, engagement, and audience KPIs.", "tags": [ "marketing", "media", "web-analytics" ], "theme": "dark", "title": "Media & Web Performance", "useCase": "Marketing, audience, and media monitoring" }, { "accent": "#04d9d2", "data": "industrial-network-telemetry/data.csv", "description": "Represents the futuristic HUD references using safe ECharts options and sanitized inline SVG rather than external raster artwork.", "expected": "Summary gauges, topology, ordered multiseries telemetry, and grouped node-health records render without network access.", "folder": "industrial-network-telemetry", "id": "industrial-network-telemetry", "limitations": "The topology is a schematic network map; advanced 3D surfaces and geographic basemaps are intentionally omitted from the Core package.", "powerBiPackage": "core", "project": "industrial-network-telemetry/project.hyperpbi", "referenceImages": [ 9, 10 ], "runtime": "industrial-network-telemetry/runtime.json", "slug": "industrial-network-telemetry", "specification": "industrial-network-telemetry/specification.json", "summary": "A deep-teal telemetry wall with neon gauges, network topology, waveform analysis, and node health.", "tags": [ "industrial", "telemetry", "network" ], "theme": "dark", "title": "Industrial Network Telemetry", "useCase": "Network, plant, and infrastructure telemetry" }, { "accent": "#0f766e", "data": "dynamic-gis-analytics/data.csv", "description": "A synthetic water distribution network pairs inline station geometry with on-demand pressure telemetry, operating assignments, and maintenance notes.", "expected": "Click each station to load different pressure readings. Hover or zoom its chart, expand the popup, page through the measurements, or refresh the station data.", "folder": "dynamic-gis-analytics", "id": "dynamic-gis-analytics", "limitations": "The local CSV is synthetic. Live details require HTTPS access to the public MiniUp Function. In Power BI, the Maps package and runtime WebAccess permission are required.", "powerBiPackage": "maps", "project": "dynamic-gis-analytics/project.hyperpbi", "referenceImages": [], "runtime": "dynamic-gis-analytics/runtime.json", "slug": "dynamic-gis-analytics", "specification": "dynamic-gis-analytics/specification.json", "summary": "Three Houston pressure stations open interactive, live API analytics in map popups.", "tags": [ "GIS", "utilities", "live-api" ], "theme": "light", "title": "Dynamic GIS Analytics", "useCase": "Water utility pressure monitoring" }, { "accent": "#3156a8", "data": "universal-dynamic-content/data.csv", "description": "A maintenance dispatcher browses a local asset queue while a responsive side panel and workload card fetch their component trees from MiniUp.", "expected": "Select P-204 or another asset to load its work plan in the side panel. Select High under Work priority to query the filtered workload, then click Refresh workload to repeat the live request.", "folder": "universal-dynamic-content", "id": "universal-dynamic-content", "limitations": "The local CSV is synthetic. Live details require HTTPS access to the public MiniUp Function. In Power BI, the Maps package and runtime WebAccess permission are required.", "powerBiPackage": "maps", "project": "universal-dynamic-content/project.hyperpbi", "referenceImages": [], "runtime": "universal-dynamic-content/runtime.json", "slug": "universal-dynamic-content", "specification": "universal-dynamic-content/specification.json", "summary": "Select a work order to open its live details, and query workload independently by priority.", "tags": [ "maintenance", "work-orders", "live-api" ], "theme": "light", "title": "Universal Dynamic Content", "useCase": "Maintenance dispatch and asset work orders" }, { "accent": "#54bcff", "data": "pump-station-monitoring/data.csv", "description": "Northbank Water's fictional booster station pairs four selectable centrifugal pump assemblies with pressure vessels, suction and discharge manifolds, and synthetic operating records. The spatial view, station KPIs, pressure trend, motor-load chart, and snapshot register all use the same source data.", "expected": "Choose Peak demand to flag P-103 and start the standby pump, or Maintenance to stop P-102. Select equipment in the scene or its keyboard-accessible list to filter the trend, motor-load chart, and register. Select a motor-load bar or snapshot row to highlight its pump. Select the same asset again or clear the scene selection to restore the linked views. All uses the newest snapshot for station KPIs and asset status and averages pressure across the available scenarios.", "folder": "pump-station-monitoring", "id": "pump-station-monitoring", "limitations": "The three operating scenarios are precomputed snapshots. The project works offline and uses procedural equipment geometry. In Power BI, include readingid as a categorical column and set numeric fields to Don't summarize to preserve distinct reading rows. Configure Power BI visual interactions to test the selected rows against a second visual.", "powerBiPackage": "core", "previewImage": "/images/pump-station-monitoring.webp", "project": "pump-station-monitoring/project.hyperpbi", "referenceImages": [], "runtime": "pump-station-monitoring/runtime.json", "slug": "pump-station-monitoring", "specification": "pump-station-monitoring/specification.json", "summary": "Explore a 3D booster station, rehearse changing duty conditions, and trace each pump to its operating history.", "tags": [ "3D", "utilities", "SCADA" ], "theme": "dark", "title": "Pump Station Monitoring", "useCase": "Water utility operations and equipment telemetry" }, { "accent": "#6eb5ff", "data": "groundwater-supply-distribution/data.csv", "description": "Ridgeway Water's fictional network collects groundwater from two wells, treats it, and pumps it through a distribution main to three residential areas. Select the Clearwell tank to inspect its water level, or change operating scenarios to watch its waterline and pipe flow update.", "expected": "Choose Remote well offline to turn its pump red and stop its pipe animation. The Clearwell level drops from 78% to 43% in the tank, KPI, and trend. Peak demand sets the level to 61%. Select the tank or another asset to filter the flow views and register. Use Pause flow to stop the moving markers. All uses the Normal flow snapshot and level trend and averages the flow history across scenarios.", "folder": "groundwater-supply-distribution", "id": "groundwater-supply-distribution", "limitations": "The scene illustrates precomputed operating scenarios and flow direction. Import readingid in Power BI and set numeric columns to Don't summarize to preserve row identities.", "powerBiPackage": "core", "previewImage": "/images/groundwater-supply-distribution.webp", "project": "groundwater-supply-distribution/project.hyperpbi", "referenceImages": [], "runtime": "groundwater-supply-distribution/runtime.json", "slug": "groundwater-supply-distribution", "specification": "groundwater-supply-distribution/specification.json", "summary": "Follow water from two wells through treatment and high-service pumping to three residential delivery points.", "tags": [ "3D", "groundwater", "distribution" ], "theme": "dark", "title": "Groundwater Supply & Distribution", "useCase": "Groundwater treatment and residential water distribution" }, { "accent": "#54bcff", "data": "scene3d-animation-studio/data.csv", "description": "A hands-on Three.js motion laboratory using synthetic booster-station readings. Configure RPM-driven cooling fans, moving actuators, alert pulses, scaling indicators and visibility animation in the Visual Inspector. Every object can be selected and linked to charts and tables.", "expected": "Normal duty spins three fans, Peak demand spins all four and pulses the P-103 warning beacon, and Maintenance stops P-102 so its status beacon blinks. Edit any object's Animations section to adjust RPM, axis, period and data fields.", "folder": "scene3d-animation-studio", "id": "scene3d-animation-studio", "limitations": "Scenario values and readings are synthetic. Animations are local rendering only, not SCADA control commands. Requires WebGL 2 and respects reduced motion and runtime animation budgets.", "powerBiPackage": "core", "previewImage": "/images/pump-station-monitoring.webp", "project": "scene3d-animation-studio/project.hyperpbi", "referenceImages": [], "runtime": "scene3d-animation-studio/runtime.json", "slug": "scene3d-animation-studio", "specification": "scene3d-animation-studio/specification.json", "summary": "Explore fan rotation, moving actuators, animated alarms, data-driven speed and Power BI selection.", "tags": [ "3D", "animation", "SCADA", "Three.js" ], "theme": "dark", "title": "3D Animation Studio", "useCase": "Interactive equipment animations and industrial digital twins" }, { "accent": "#72c9e8", "data": "multi-station-3d-explorer/data.csv", "description": "A fictional water utility operates two groundwater stations and a storage and repump facility. The station map and searchable register share one selection, and the reporting day updates measurements in place.", "expected": "Choose a station with the dropdown, searchable register, or map. The selected station appears in the profile and one 3D viewer. All map markers remain visible. Move the reporting-day slider to change pumpage, flow, equipment status, and tank levels while the layout and camera stay in place. Groundwater Station 02 has no pumpage or booster readings on October 7.", "folder": "multi-station-3d-explorer", "id": "multi-station-3d-explorer", "limitations": "The CSV combines three record types in the one Power BI Values table. Scene rows contain geometry, while Daily and Equipment rows contain separate synthetic readings. The history chart includes only days with a reading. Set identifiers, SceneJSON, and the reporting date to Text, and numeric columns to Don't summarize. No network is required. The district and station coordinates are fictional.", "powerBiPackage": "core", "previewImage": "/images/multi-station-3d-explorer.webp", "project": "multi-station-3d-explorer/project.hyperpbi", "referenceImages": [], "runtime": "multi-station-3d-explorer/runtime.json", "slug": "multi-station-3d-explorer", "specification": "multi-station-3d-explorer/specification.json", "summary": "Switch among three facilities in one 3D viewer and explore station-specific pumpage and equipment readings.", "tags": [ "3D", "utilities", "SceneJSON" ], "theme": "dark", "title": "Multi-Station 3D Explorer", "useCase": "Water utility facility exploration" }, { "accent": "#63b6e5", "data": "water-pump-station-digital-twin/data.csv", "description": "A fictionalized 3D water pump station with remote and local source wells, dual surface-water inlets, treatment indicators, five storage tanks, and six booster pumps. Eight simulated operating scenarios drive tank levels, pipe flow, cooling fans, alarms, linked trends, and equipment selection.", "expected": "Switch between all eight scenarios: Normal supply, Peak demand, Remote wells offline, Surface inlet unavailable, Booster maintenance, Low storage, Limited power, and Low distribution pressure. Tank fill, pump availability, fan rotation, animated flow, pressure and intake KPIs, linked charts, and the asset register change with the scenario. Selecting an asset cross-highlights associated records.", "folder": "water-pump-station-digital-twin", "id": "water-pump-station-digital-twin", "limitations": "Synthetic demonstration based on generalized process relationships, not a literal copy of a real infrastructure diagram. Operating values are invented and must never be used for live controls. The 3D engine supports up to 128 objects, respects reduced-motion preferences, and requires WebGL 2. In Power BI bind readingid as categorical and set numeric columns to Don't summarize.", "powerBiPackage": "core", "previewImage": "/images/water-pump-station-digital-twin.svg", "project": "water-pump-station-digital-twin/project.hyperpbi", "referenceImages": [], "runtime": "water-pump-station-digital-twin/runtime.json", "slug": "water-pump-station-digital-twin", "specification": "water-pump-station-digital-twin/specification.json", "summary": "Trace source-water intake, chemical monitoring, five ground storage tanks, and six booster pumps in interactive 3D.", "tags": [ "3D", "water", "engineering", "SCADA" ], "theme": "dark", "title": "Water Pump Station | Process Digital Twin", "useCase": "Water utility process visualization and engineering training" } ], "version": "1.0" }