← All use cases

Machine learning · Decision support

Pine Yield Simulator

Turning agronomic data into yield predictions, planning scenarios and answers people can act on.

Python / DjangoCatBoost / scikit-learnLangChainAmazon BedrockAWS
RoleSolo developer · End to end
ContextGreat Giant Foods
DomainAgriculture & operations
DeliveryWeb application · AWS
Pine Yield Simulator — application preview
Pine Yield Simulator — application preview · Click to enlarge ↗

01 / THE CONTEXT

A real operational
problem.

The challenge

Harvest planning brings together agronomic parameters, changing field conditions and several versions of the forecast. Planners need to compare ML predictions with PPIC forecasts and actual harvests, then understand which assumptions drive the difference.

The solution

I built a single application that connects prediction, scenario analysis and reporting. Users can run individual or bulk predictions, inspect forecast performance, explore long-term production plans and ask an AI assistant to query data or execute real ML inference.

02 / THE PRODUCT

Built around the workflow.

01

ML yield prediction

Model 1 and Model 2 use CatBoost, alongside stage-specific Model 3 inference for NSFC/NSSC. Agronomic, crop, weather and NDVI inputs support prediction for different planning horizons.

02

What-if & target optimization

Change input parameters, compare the resulting prediction, scan sensitivity and search for settings toward a target yield. Recommendations are evaluated by the inference tools.

03

Agentic AI chatbot

A LangChain assistant on Amazon Bedrock calls prediction, data-query, historical benchmark and chart tools. It supports conversational analysis with persistent sessions and streamed responses.

04

LTP & bulk planning

Long-term planning scenarios, bulk input templates and downloadable prediction results connect model outputs to the planning workflow. Saved LTP state supports follow-up analysis.

05

BOD & yield trace reporting

Compare ML, PPIC and actual yield through BOD charts. Yield trace workflows produce slide previews, downloadable decks and monthly email recaps.

06

Data & model operations

Master data management, analytical data integration, a prediction API and operational model controls support ongoing delivery. SSO, application roles and cloud deployment complete the platform.

03 / CONVERSATIONAL AI

An assistant connected to the system.

Example request

“What can I change to improve the predicted yield for this location?”

The assistant retrieves the plot’s parameters, calls ML inference for the baseline and candidate changes, then explains the difference using historical context. Agronomic recommendations remain decision support for validation by the agronomy team.

01Retrieve plot parameters
02Run baseline inference
03Evaluate what-if changes
04Explain evidence & limits

04 / INSIDE THE APPLICATION

A closer look.

Captured from the application. These screenshots show the interface at the time of capture.

05 / UNDER THE HOOD

How the pieces connect.

Django serves the application and runs prediction through the Python inference layer. Analytical inputs come from curated data products, while PostgreSQL stores application state. LangChain connects the chat interface to Amazon Bedrock and application tools; inference and queries supply the numerical results.

Pine Yield Simulator — application, data and AI architecture
Pine Yield Simulator — application, data and AI architecture · Click to enlarge ↗
Container delivery — GitHub Actions, Amazon ECR and ECS Fargate
Container delivery — GitHub Actions, Amazon ECR and ECS Fargate · Click to enlarge ↗

Simplified architecture views for this case study; infrastructure identifiers and environment-specific configuration are omitted.

06 / MY CONTRIBUTION

Solo developer.
Full ownership.

I built Pine Yield Simulator as a solo developer: solution architecture, frontend and backend implementation, data integration, AI capabilities, deployment and ongoing application improvements.

The work spans the full application lifecycle, connecting business requirements to a usable interface and the services that run it. Operational data and domain input come from the business context.

Product & system designFull-stack implementationData & AI integrationCloud & CI/CD delivery

07 / WHAT THIS ENABLES

Engineering with
an operational purpose.

  • One workflow connects prediction, scenario exploration and management reporting.
  • Natural-language analysis makes model and historical data accessible through the same interface.
  • Bulk prediction, exports and reporting help move analytical results into planning reviews.
Explore the other case studyI-Smart Water Management

Image preview