01
AvailableInteractive product tour
A self-guided walkthrough of the reference portfolio, site analysis, incidents, and reporting workflow.
Enterprise evaluation center
Inspect the product, methodology, and operating model before you buy.
ArraySignal separates implemented capabilities from evaluation paths and future direction. Use this center to assess technical fit without relying on unqualified claims.
Product tour →
Walk through the reference workflow
Methodology →
Review analytical definitions
Implementation →
Understand onboarding gates
Data readiness →
Assess telemetry inputs
Buyer resources
Twenty concrete evaluation capabilities.
Availability labels are deliberate. Planned items are product direction, not contracted functionality.
Review capability →
02
AvailableSolar Fault Atlas
Explainable guides for the deterministic fault categories ArraySignal evaluates.
03
AvailableAnalysis methodology
Transparent definitions for expected production, coverage, confidence, health, and modeled loss.
04
AvailableSample report library
Clearly labeled reference deliverables for evaluation and internal alignment.
05
AvailableImplementation guide
A practical CSV-first onboarding path with responsibilities and acceptance gates.
06
AvailablePortfolio readiness assessment
An interactive, privacy-conscious checklist for evaluating telemetry readiness.
07
AvailableData requirements
Required and optional fields, units, timestamps, and quality expectations.
08
AvailableProcurement center
One place for architecture, security, operations, privacy, and evaluation material.
09
In evaluationShareable impact scenarios
Modeled scenarios remain available in the impact calculator; exportable scenarios are under evaluation.
10
AvailableReference benchmark center
Synthetic reference sites support workflow evaluation without implying customer performance.
11
AvailableWorkflow-specific evaluation
Evaluation paths for investigation, loss analysis, portfolio ranking, and data quality.
12
AvailableIntegration directory
Current CSV capabilities and honestly labeled future connector paths.
13
AvailableIntegration request workflow
A protected contact route for documenting source-system and backfill requirements.
14
AvailableGuided demo chapters
A chaptered product narrative with keyboard-accessible controls and sample context.
15
PlannedRelease subscription
Subscription delivery will be enabled after an email preference service is configured.
16
PlannedTechnical webinar center
Reserved for real scheduled or recorded engineering sessions; no fabricated events are published.
17
AvailableSolar analytics glossary
Plain-language definitions for the operational and analytical terms used in the product.
18
AvailableMedia and brand kit
Approved brand language, product facts, and contact routes without invented awards.
19
AvailableAccessibility statement
Documented interaction standards, reduced-motion support, and a protected feedback route.
20
PlannedVerified customer proof
The publishing framework is ready, but no testimonials or outcomes appear without permission and evidence.
Operational workflows
Evaluate the decision workflow, not just the dashboard.
Fault investigation
Move from a qualified deviation to evidence, probable cause, confidence, and a recommended inspection action.
Loss analysis
Keep actual, expected, missing, and modeled values distinct while estimating potential energy and revenue impact.
Portfolio ranking
Rank sites using impact, severity, confidence, and data coverage instead of alert count alone.
Data quality
Surface missing intervals, invalid readings, duplicate timestamps, and uncertainty without silently discarding them.
Reference benchmark center
Comparable workflows without invented customer evidence.
The five reference plants and their history are synthetic demonstration data. They test healthy, incomplete, underperforming, and fault-oriented states; they are not market benchmarks.
2022–2027
Reference daily history
5 sites
Commercial PV scenarios
Explicit
Sample and uncertainty labels
0 claims
Unverified customer outcomes
Application architecture
Implemented as independently testable, persistence-neutral domain contracts. Production persistence and provider adapters remain separate concerns.
- 01Canonical tenant-scoped asset model
- 02Equipment hierarchy traversal
- 03Vendor-neutral telemetry adapter contract
- 04Validated ingestion state machine
- 05Idempotent import ledger contract
- 06Composable data-quality rules
- 07Versioned expected-model registry
- 08Timezone-aware analysis provenance
- 09Versioned fault-rule registry
- 10Non-overlapping loss attribution
- 11Domain event and outbox contract
- 12Background-job queue port
- 13Portfolio priority read model
- 14Role and permission policy engine
- 15Tenant-scoped audit log contract
- 16Notification preference model
- 17Versioned report pipeline
- 18Integration availability registry
- 19Versioned API contract
- 20Organization-scoped feature flags
Infrastructure and operations
Implemented controls are documented separately from adoption paths that still require provider configuration or operating history.
- 01Development, preview, and production isolation
- 02Infrastructure-as-code adoption path
- 03Migration validation gate
- 04Backup and point-in-time recovery procedure
- 05Disaster-recovery runbook
- 06Database connection-budget guidance
- 07Durable job infrastructure adapter path
- 08OpenTelemetry instrumentation boundary
- 09External error-monitoring adapter boundary
- 10Structured centralized logging policy
- 11Public health and readiness endpoints
- 12Synthetic journey monitoring plan
- 13Service-level objectives
- 14Dependency and static security scanning
- 15Software supply-chain controls
- 16Secret lifecycle and rotation procedure
- 17Application-layer abuse protection
- 18Performance and load-test plan
- 19Data retention and deletion policy
- 20Cost and capacity alerting plan
Accessibility
Designed for keyboard, touch, and reduced motion.
Interactive controls use semantic labels and visible focus states. Animations honor reduced-motion preferences, and charts retain textual context.
Evidence policy
Customer proof must be permissioned and verifiable.
Until approved customer evidence exists, ArraySignal uses explicitly labeled reference data and does not publish fabricated logos, testimonials, savings, awards, or ratings.
Explore your portfolio
Bring a real operating question to the conversation.
We’ll discuss telemetry coverage, portfolio priorities, and a practical evaluation scope—without presenting sample estimates as guaranteed outcomes.