<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data Engineering | Shivam Vashishtha</title><link>https://www.shivamvashishtha.com/tag/data-engineering/</link><atom:link href="https://www.shivamvashishtha.com/tag/data-engineering/index.xml" rel="self" type="application/rss+xml"/><description>Data Engineering</description><generator>Wowchemy (https://wowchemy.com)</generator><language>en-us</language><lastBuildDate>Sun, 01 Feb 2026 00:00:00 +0000</lastBuildDate><image><url>https://www.shivamvashishtha.com/media/icon_hu016cb3b331e9522dbd920334fc7fb877_32429_512x512_fill_lanczos_center_3.png</url><title>Data Engineering</title><link>https://www.shivamvashishtha.com/tag/data-engineering/</link></image><item><title>Engineering Data Integration &amp; Validation</title><link>https://www.shivamvashishtha.com/project/grid-data-integration/</link><pubDate>Sun, 01 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.shivamvashishtha.com/project/grid-data-integration/</guid><description>&lt;p>&lt;strong>Context:&lt;/strong> Xcel Energy · Transmission Modeling&lt;br>
&lt;strong>Period:&lt;/strong> 2025–2026 · Engineering-data workflows&lt;br>
&lt;strong>Focus:&lt;/strong> Data Engineering&lt;br>
&lt;strong>Tools / methods:&lt;/strong> Python · Databricks · industrial data concepts&lt;/p>
&lt;h2 id="engineering-question">Engineering question&lt;/h2>
&lt;p>Power-system models, measurement systems, and engineering reference tables serve different purposes. Joining them requires careful treatment of identifiers, timestamps, units, and expected data quality.&lt;/p>
&lt;h2 id="my-work">My work&lt;/h2>
&lt;ul>
&lt;li>Worked with engineering datasets used to support transmission model checking.&lt;/li>
&lt;li>Supported data reconciliation and repeatable preprocessing workflows.&lt;/li>
&lt;li>Explored ways to make comparison and validation results easier for engineers to interpret.&lt;/li>
&lt;/ul>
&lt;h2 id="technical-approach">Technical approach&lt;/h2>
&lt;p>A robust pipeline validates schema, normalizes units, checks temporal alignment, and treats unmatched or stale records as first-class review results. Reference-data consistency should be examined separately from physical model validity.&lt;/p>
&lt;h2 id="engineering-considerations">Engineering considerations&lt;/h2>
&lt;p>Operational measurements and static planning models need not correspond to the same operating state. Apparent disagreement can arise from time alignment or reference-model differences rather than sensor malfunction.&lt;/p>
&lt;h2 id="evidence-and-maturity">Evidence and maturity&lt;/h2>
&lt;p>Engineering-data analysis and validation contributions; not a claim of a deployed real-time control system.&lt;/p>
&lt;h2 id="public-scope">Public scope&lt;/h2>
&lt;p>No plant tag, internal endpoint, operational timeseries, authentication detail, or source database is shown.&lt;/p></description></item></channel></rss>