Showcase Smart Reporting as a core ARSAS capability

[masarray]

Summary

Promotes the implemented ARSAS Smart Reporting acquisition strategy as a primary product benefit for IEC 61850 FAT, SAT, commissioning, and troubleshooting.

Code-audit conclusion

The current runtime already implements the following per selected point and per independent IED session:

• immediate MMS reads while report setup is prepared;
• configured static Report Control Blocks first, including buffered and unbuffered paths;
• exact DataSet-member validation before report coverage is trusted;
• temporary association-scoped dynamic DataSet recovery with a suitable available URCB/RCB when writes are enabled and supported;
• bounded MMS polling for uncovered, rejected, unverified, or degraded points;
• report-behavior verification, including restoring polling when a real change is missed;
• value, quality, IED timestamp, report reason, sequence, and acquisition-source evidence.

Landing changes

• Adds a dedicated SEO-focused smart-reporting.html product page.
• Adds Smart Reporting to the website navigation and product footer.
• Promotes the capability directly on the homepage with a four-stage acquisition flow.
• Strengthens the Capabilities page reporting section and fallback explanation.
• Covers empty DataSets, no usable RCB, rejected dynamic writes, and degraded report delivery.
• Adds Schema.org SoftwareApplication and FAQ metadata for BRCB, URCB, dynamic DataSet, and polling searches.
• Adds the new page to the sitemap and static website validator.

Claim boundaries

• ARSAS does not auto-select every discovered signal; the engineer chooses the monitoring scope.
• Existing configured reporting is preferred.
• Dynamic writes are attempted only when enabled, supported by the IED, and permitted by the approved workflow.
• The implementation primarily creates a temporary DataSet and uses a suitable available URCB/RCB; this PR does not claim universal dynamic BRCB creation.
• Polling remains the non-blocking fallback.
• This is an implementation audit and product-documentation update, not a universal multi-vendor interoperability or formal conformance claim.

Validation

• Landing HTML, local links, SEO metadata, JSON-LD, sitemap, and branding
• Source, license, UX, GOOSE, SAS, and engine compatibility gates
• .NET restore and Release build
• Portable Windows publish and artifact upload

Runtime scope

No application or ARIEC61850 runtime code is modified by this pull request.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.