Ongoing Maintenance and Seasonal Governance

Maintain the Country Context

Maintain the digital twin as the country’s agricultural reporting context changes. Review and update administrative boundaries, region names, crop classifications, season definitions, production history, and supporting local reference data when authoritative sources change.

Keep a record of the source, effective date, owner, and reason for a material update. This makes it easier to explain changes in Visual Explorer results and preserve continuity across reporting cycles.

Support Seasonal Readiness

Before and during each relevant agricultural season, review the configured crop list, season context, expected data availability, and local validation plan. Coordinate updates to crop or region priorities before users need to rely on the related data.

As new data becomes available, validate the region, crop, layer, and data-acquired date context in Visual Explorer. For Crop Production, also confirm that production, detected area, yield, yield category, history, and sub-region content are appropriate to the dataset and selected region.

Manage Changes and Corrections

Use a coordinated review when a material change affects user interpretation, including:

• an official boundary or hierarchy change;
• a new, renamed, or reprioritized crop;
• revised seasonal context or historical production information;
• new ground-truth observations or validation findings; or
• a coverage, quality, or availability issue in a displayed dataset.

Assess the effect on Visual Explorer before communicating the update. Where needed, explain the changed context to administrators and users, including the affected crop, region, layer, or data-acquired date.

Maintain Collaboration

Ongoing collaboration keeps the digital twin locally relevant. Government data stewards coordinate authoritative data and change information; GIS specialists maintain geographic quality; agronomists contribute seasonal and field context; and Oracle delivery teams coordinate validation and approved updates.

Review the data foundation regularly and agree follow-up actions for outstanding gaps, corrections, or future validation work.