---
date: 2026-04-28
meeting: Enterprise Brain Scrum
source: Enterprise Brain Scrum - 2026_04_28 02_00 PDT - Notes by Gemini.txt
duration: ~7 minutes
---

# Enterprise Brain Scrum — 28 Apr 2026

**Date:** 2026-04-28 | **Time:** ~02:00 PDT | **Duration:** ~7 min  
**Source:** Full transcript (brief session — single speaker explaining context)

## Participants

**RG** — Rajashekar G Mannam  
_(No other speakers identified in transcript)_

---

## Act I — Tata Steel Project Context: EAF Construction (~00:00 – ~00:06)

RG delivered a brief but important domain briefing explaining the Tata Steel project that Enterprise Brain is being built to support. This appears to have been an explanation provided to another person (possibly to help a new team member understand the business domain).

**The project in plain terms:**

Tata Steel is undertaking a large, multi-year infrastructure project to replace existing furnaces with **Electric Arc Furnaces (EAF)**. The first step is dismantling existing equipment and clearing debris before new construction can begin. Due to the multi-year scope and scale, a large number of contractors are involved across different phases of the project.

**How contracts enter the picture:**

1. The Tata Steel finance department and executive leadership identify the need and obtain government approval.
2. For each activity or sub-phase, a **budget** is allocated (referred to as "F" — likely "forecast" or "funding allocation").
3. **Tenders (bids)** are submitted by contractors for each activity.
4. Tata Steel evaluates bids based on multiple criteria (cost, track record, relationships).
5. The selected contractor becomes the **awardee** — the entity that "got the contract." This committed value is what populates the "committed" column in the database.
6. **Risks** are tracked separately — these represent challenges flagged during the project lifecycle, and they are stored in the DB tables.

**Data model note:**

RG noted that only **6–10 tables** in the database are directly related to the core project management entities. The team had mapped out these relationships. Understanding which tables join to which is critical for generating correct SQL queries — especially when the source data (provided by Tata Steel) comes as pre-aggregated reports rather than normalised entity tables, requiring the team to reverse-engineer the underlying entity structure.

---

## Todos

_No action items were assigned in this session — it was a context-setting explanation, not a decision or planning meeting._