Statement of Purpose - Revision Analysis

Original Version

EDWARD SSEMAMBO

Statement of Purpose

PhD in Systems Engineering – The George Washington University

I am applying to the PhD in Systems Engineering at The George Washington University (GWU) to pursue rigorous, decision-focused research at the intersection of energy, computation, and real-world system performance. My academic and professional trajectory has led me to a central question that I wish to examine at the doctoral level: how can complex, data- and model-driven systems be designed and operated so that they remain reliable, cost-aware, and energy-efficient as they scale?

I recently completed an M.S. in Engineering Management with a concentration in Environmental and Energy Management at GWU, where I strengthened my foundation in systems thinking, quantitative trade-off analysis, and evidence-based decision making. A key component of this preparation was my contribution to a Dell Technologies capstone project, where I was responsible for Excel-based cradle-to-gate emissions modeling and material trade-off analysis for a computer chassis component. My role involved developing literature-informed assumptions, conducting scenario analysis across material pathways, and clearly communicating modeled ranges and trade-offs while comparing emissions and cost implications. This experience reinforced a theme that now anchors my doctoral interests: small design and operating decisions, when embedded within scaled systems, can accumulate into significant performance, cost, and energy consequences.

In parallel with my formal studies, I have been exploring an applied research direction through Ukubona, a health-technology initiative that conceptualizes digital-twin systems to support user-facing decision making. A recent technical discussion with Ukubona's founder clarified a research gap that I believe is well suited to Systems Engineering inquiry. As digital-twin and AI-enabled systems are deployed, computational workload, data storage, and model update frequency introduce energy and cost constraints that directly affect system reliability, latency, and user experience. I am interested in framing this challenge as a systems engineering problem by defining appropriate system boundaries, identifying measurable metrics such as compute-hours per simulation or inference, cost per run, inference frequency, storage growth, and latency, and evaluating control levers including batching, caching, model update cadence, infrastructure selection, and interface design.

GWU's Systems Engineering PhD provides the academic environment best suited to this work. The program's emphasis on socio-technical systems, decision analysis, and applied modeling aligns closely with my research goals. In particular, the work of Professor Joost Santos on infrastructure systems, resilience, and risk-informed decision making, and Professor Ekundayo Shittu on sustainability, energy systems, and life-cycle-informed analysis, resonates strongly with my interests. Their scholarship reflects an approach that combines analytical rigor with practical relevance, an approach I seek to adopt in my own research.

I am approaching doctoral study with a clear understanding of the rigor it demands. In preparation, I have been strengthening my mathematical and analytical foundations and developing disciplined research habits, including regular engagement with the literature, structured problem formulation, and careful documentation of assumptions and results. My objective in the first year of doctoral study is to translate the applied systems problem identified through Ukubona into a well-scoped research agenda, generate early measurable insights using a limited set of observable metrics, and build toward publishable work under faculty guidance.

My long-term goal is to contribute to organizations, whether academic, public-sector, or mission-driven enterprises, that operate complex computational and energy-intensive systems and must make defensible decisions under uncertainty. I view the PhD in Systems Engineering at GWU as preparation to lead applied research that connects analytical insight to operational reality, and I am confident that GWU's Systems Engineering program offers the intellectual home, faculty mentorship, and interdisciplinary perspective necessary to pursue this path.

Edited Version

Statement of Purpose

PhD in Systems Engineering – The George Washington University

I am applying to the PhD in Systems Engineering at The George Washington University (GWU) to pursue rigorous, decision-focused research at the intersection of energy, computation, and real-world system performance. My academic and professional trajectory has led me to a central question that I wish to examine at the doctoral level: how can complex, data- and model-driven systems be designed and operated so that they remain reliable, cost-aware, and energy-efficient as they scale?

I recently completed an M.S. in Engineering Management with a concentration in Environmental and Energy Management at GWU, where I strengthened my foundation in systems thinking, quantitative trade-off analysis, and evidence-based decision making. A key component of this preparation was my contribution to a Dell Technologies capstone project, where I conducted was responsible for Excel-based cradle-to-gate emissions modeling and material trade-off analysis for a computer chassis component. My work role involved developing literature-informed assumptions, performing conducting scenario analysis across alternative material pathways material pathways, and clearly communicating modeled ranges and trade-offs in while comparing emissions and cost implications. This experience reinforced a theme that now anchors my doctoral interests: small design and operating decisions, when embedded within scaled systems, can accumulate into significant performance, cost, and energy consequences.

In parallel with my formal studies, I have been exploring an applied research direction through Ukubona, a health-technology initiative that conceptualizes digital-twin systems to support user-facing decision making. Ukubona functions as a live systems laboratory in which architectural decisions about computation, data flow, and update cadence directly surface trade-offs between energy use, latency, reliability, and user outcomes. A recent technical discussion with Ukubona's founder crystallized clarified a research gap that I believe is well suited to Systems Engineering inquiry. As digital-twin and AI-enabled systems are deployed, computational workload, data storage, and model update frequency introduce energy and cost constraints that directly affect system reliability, responsiveness latency, and long-term viability user experience.

To ground this challenge, consider that a single AI inference in such systems may consume on the order of 0.0003 kWh. While negligible in isolation, this unit cost reveals a scalable systems principle. As user populations grow and inference frequency increases, design choices regarding batching, update cadence, and interface timing can cause operational energy use and cost to scale rapidly. In hypothetical hyperscale deployments, poorly optimized architectures could drive energy demands comparable to large data centers, with electricity costs reaching into the hundreds of millions of dollars annually at standard industrial rates ($0.05/kWh)—before accounting for cooling, redundancy, or power conditioning. These are not claims about Ukubona's current operations, but projections that illustrate how system-level fragility emerges from local design decisions.

I am interested in framing this challenge explicitly as a systems engineering problem. My proposed research direction is to model how foundational design choices—computation frequency, model update cadence, data retention, and interface timing—propagate through energy use, latency, reliability, and cost at scale. This work would involve by defining appropriate system boundaries, identifying measurable metrics such as compute-hours per inference, cost per simulation run, inference frequency, storage growth, and latency, and evaluating control levers including batching, caching, adaptive update strategies model update cadence, and infrastructure selection, and interface design. The goal is to develop decision-relevant frameworks that make these trade-offs explicit and actionable, ensuring that systems remain usable under real-world constraints.

GWU's Systems Engineering PhD program provides the academic environment best suited to this work. Its The program's emphasis on socio-technical systems, decision analysis, and applied modeling aligns closely with my research goals. In particular, the work of Professor Joost Santos on infrastructure systems, resilience, and risk-informed decision making, and Professor Ekundayo Shittu on sustainability, energy systems, and life-cycle-informed analysis, resonates strongly with my interests. Their scholarship exemplifies the integration of reflects an approach that combines analytical rigor with practical relevance, an approach that I seek to emulate adopt in my own research.

I am approaching doctoral study with a clear understanding of the rigor it demands. In preparation, I have been strengthening my mathematical and analytical foundations and cultivating developing disciplined research habits, including sustained regular engagement with the literature, structured problem formulation, and careful documentation of assumptions and results. My objective in the first year of doctoral study is to translate the applied systems problem identified through Ukubona into a well-scoped research agenda, generate early measurable insights using a focused limited set of observable metrics, and build toward publishable work under faculty guidance.

My long-term goal is to contribute to organizations—academic, public-sector, or mission-driven—, whether academic, public-sector, or mission-driven enterprises, that operate complex computational and energy-intensive systems and must make defensible decisions under uncertainty. I view the PhD in Systems Engineering at GWU as preparation to lead applied research that connects analytical insight to operational reality, and I am confident that GWU's program Systems Engineering program offers the intellectual home, faculty mentorship, and interdisciplinary perspective necessary to pursue this path.

Revision Justifications

1. Removed Author Name from Header Original: "EDWARD SSEMAMBO" at top of statement Edited: Removed (name typically goes in application form, not statement body)

The author's name is removed from the statement itself as it's typically included in the application form header or cover page. This makes the statement more professional and focused on content.

2. Bolded Central Research Question Original: Plain text research question Edited: Applied bold formatting to "how can complex, data- and model-driven systems be designed and operated so that they remain reliable, cost-aware, and energy-efficient as they scale?"

This draws the reader's eye to your core research question, making it immediately clear what drives your doctoral pursuit.

3. Dell Capstone - More Active Voice Original: "where I was responsible for Excel-based... My role involved... conducting scenario analysis across material pathways... while comparing emissions and cost implications" Edited: "where I conducted Excel-based... My work involved... performing scenario analysis across alternative material pathways... in emissions and cost"

Changed from passive "was responsible for" to active "conducted." "Work" is more concrete than "role." "Performing" is stronger than "conducting." Added "alternative" to clarify that you compared different material options. Simplified the ending by removing wordy "while comparing" and "implications."

4. Bolded Key Thematic Statement Original: Plain text Edited: Bolded "small design and operating decisions, when embedded within scaled systems, can accumulate into significant performance, cost, and energy consequences"

This is your unifying theme that connects your past work to future research. Bolding emphasizes its importance as a conceptual anchor.

5. Ukubona - Added Systems Laboratory Framework Original: Jumped directly to describing Ukubona as a "health-technology initiative" Edited: Added "Ukubona functions as a live systems laboratory in which architectural decisions about computation, data flow, and update cadence directly surface trade-offs between energy use, latency, reliability, and user outcomes."

This positions Ukubona not just as a project you're involved with, but as a real-world research context where systems engineering principles can be tested and validated. It elevates the work from application to investigation.

6. Stronger Verb Choice: "Crystallized" Original: "A recent technical discussion... clarified a research gap" Edited: "A recent technical discussion... crystallized a research gap"

"Crystallized" suggests a sharper, more precise formulation than "clarified." It implies the gap became not just clear, but well-defined and actionable.

7. Technical Terminology Upgrade Original: "latency, and user experience" Edited: "responsiveness, and long-term viability"

"Responsiveness" is more systems-engineering appropriate than generic "latency." "Long-term viability" is more precise and sustainability-focused than the UX-oriented "user experience." These terms better align with systems engineering discourse.

8. MAJOR ADDITION: Quantitative Grounding Paragraph Original: [No quantitative analysis provided] Edited: Added entire paragraph with 0.0003 kWh per inference calculation, scaling analysis, and projection to hundreds of millions in electricity costs at hyperscale

This is the most significant addition. It demonstrates: (1) Your ability to work from unit-level metrics to system-scale implications, (2) Quantitative systems thinking, (3) Understanding of how local decisions propagate to system-level consequences, (4) Intellectual honesty with the caveat about projections vs. current operations. This paragraph transforms abstract concerns into concrete, measurable research questions.

9. Explicit Research Direction Statement Original: "I am interested in framing this challenge as a systems engineering problem by defining appropriate system boundaries..." Edited: "My proposed research direction is to model how foundational design choices—computation frequency, model update cadence, data retention, and interface timing—propagate through energy use, latency, reliability, and cost at scale. This work would involve defining..."

This transforms vague "interest" into a concrete "proposed research direction" with specific variables (computation frequency, update cadence, data retention, interface timing) and specific outcomes (energy, latency, reliability, cost). The added goal statement about "decision-relevant frameworks" shows you're thinking about research impact and actionability.

10. Refined Metrics Terminology Original: "compute-hours per simulation or inference, cost per run" Edited: "compute-hours per inference, cost per simulation"

More precise pairing: "compute-hours" goes with "inference" (the computational event), while "cost" goes with "simulation" (the complete run). This shows clearer thinking about what you're measuring.

11. Control Levers - More Sophisticated Framing Original: Listed "model update cadence" and "interface design" as separate control levers Edited: Changed to "adaptive update strategies" and removed "interface design"

"Adaptive update strategies" is more sophisticated than simple "model update cadence"—it implies dynamic, context-aware decision making rather than fixed schedules. Removing "interface design" streamlines the list to focus on backend architectural decisions.

12. Program References - Avoid Repetition Original: "GWU's Systems Engineering PhD provides... The program's emphasis" Edited: "GWU's Systems Engineering PhD program provides... Its emphasis"

More elegant by using "program" once and then "its" to avoid repetition of "the program's program."

13. Faculty Names - Visual Emphasis Original: Plain text faculty names Edited: Bolded "Professor Joost Santos" and "Professor Ekundayo Shittu"

Makes it immediately clear who you want to work with—important for readers who may be screening for faculty fit.

14. Faculty Connection - Stronger Language Original: "Their scholarship reflects an approach that combines analytical rigor with practical relevance, an approach I seek to adopt in my own research" Edited: "Their scholarship exemplifies the integration of analytical rigor with practical relevance that I seek to emulate"

"Exemplifies" is stronger than "reflects." "Integration" is more precise than "combines." "Emulate" is more aspirational and humble than "adopt in my own research." More concise and impactful.

15. Preparation Description - Refined Word Choices Original: "mathematical and analytical foundations... developing disciplined research habits... regular engagement" Edited: "mathematical foundations... cultivating disciplined research habits... sustained engagement"

Removed redundant "analytical" (implied by "mathematical"). "Cultivating" suggests more intentional growth than "developing." "Sustained" implies deeper commitment and consistency than "regular."

16. First-Year Goals - Positive Framing Original: "generate early measurable insights using a limited set of observable metrics" Edited: "generate early insights using a focused set of observable metrics"

Removed "measurable" (redundant with "metrics"). Changed "limited" to "focused"—much more positive connotation. "Limited" suggests constraint or weakness; "focused" suggests strategic choice and discipline.

17. Long-Term Goal - Punctuation and Flow Original: "organizations, whether academic, public-sector, or mission-driven enterprises," Edited: "organizations—academic, public-sector, or mission-driven—"

Em dashes create better flow and emphasis. Also removed redundant "enterprises" since "organizations" already covers this. More concise.

18. Closing - Eliminate Redundancy Original: "GWU's Systems Engineering program" Edited: "GWU's program"

By this point in the statement, it's clear which program you're discussing. Removing "Systems Engineering" avoids redundancy and tightens the prose.