Strawberry can help organise irradiance forecasts, PV power estimates, live data, historical comparisons, and site planning. It turns the signed-in Solcast work in front of you into a bounded review, so the people responsible for the work can investigate exceptions, prepare a handoff, and keep the source evidence beside the decision.
A wrong site or interval can look like a real generation signal and lead to an avoidable scheduling decision.
01
The first Solcast pass should make the exceptions visible.
Review the Solcast forecast for the sites shown here.
Compare the next operating window with live and historical values, then flag sites that need an operator’s attention.
A narrow first pass turns a busy Solcast view into a queue that names what changed, what needs a decision, and what is safe to leave alone.
02
Solcast evidence needs a check before it becomes a conclusion.
Check whether this PV power forecast uses the right site assumptions and time interval.
Summarise uncertainty rather than presenting a single value as a guarantee.
The comparison keeps a plausible-looking Solcast result connected to the conditions and evidence that make it trustworthy.
03
A Solcast handoff should preserve the work behind the answer.
Prepare a planning note from the Solcast data for the operations team.
Include forecast range, comparison period, and the source view for each exception.
The Solcast receiving owner gets the relevant links, the boundary of the review, and the unresolved edges instead of a status note that has to be rebuilt.
04
The Solcast review should arrive when the decision still matters.
Every operating morning at 06:30, prepare the day-ahead solar forecast review before dispatch planning begins.
Day-ahead data belongs before the dispatch decision, while a historical comparison can follow after production is known. Keep this exact Solcast review as a named skill, then use a routine at that rhythm so the right people receive a fresh packet before the next decision window.
It can organise the signed-in Solcast views you choose into a source-aware review, surface exceptions, and prepare a clear packet for the person who owns the next decision.
It can work through the Solcast browser context you provide, but any consequential write should stay reviewable before it is completed.
Yes. Keep a proven Solcast review as a named skill, then schedule that specific check around the operational moment when fresh evidence is useful.
No. Solcast remains the system where its specialist work happens; Strawberry helps the responsible person inspect and move that work forward.
Solcast Strawberry