Learning Hub › Process Engineering
Chem-Eng Projects
This is the hub for process engineering projects: the general philosophy and discussion that applies across multiple process-engineering projects, with links out to each specific project’s own repo.
Projects
| Project | Description |
|---|---|
| WORK IN PROGRESS: MogasDebenz | Motor gasoline benzene removal. A process modification project aimed at reducing benzene in motor gasoline to comply with emerging regulatory limits. Start here if you are working on a design project. |
(Additional projects — e.g. a crude expansion project — will be listed here as they’re developed.)
All projects linked from here are fictional and illustrative, built for teaching purposes. They are not the actual history of any real company’s design discussions, technology choices, or regulatory timeline. Actual industry design discussions of this kind are typically closely guarded, both for competitive reasons and to maintain antitrust compliance between companies.
Wiki
The chem-eng-projects Wiki holds the general process-engineering philosophy, shared conventions, and cross-project reference material.
What Lives Here vs. What Lives in Each Project Repo
Here (chem-eng-projects) |
Each project repo (e.g. chem-eng-projects-MogasDebenz) |
|---|---|
| General process-engineering philosophy and discussion | Project-specific milestones and Issues |
| Cross-project conventions (e.g. how BFDs/PFDs are used, stakeholder-engagement approach) | All team communication and mock stakeholder conversations, captured in Issue threads |
| Landing page linking to all projects | Project-specific Wiki (job aids, model version changelog, and other knowledge capture) |
| The actual flowsheet model, PFDs, and deliverables for that project |
Each project repo is the complete working record for that project — not just its final deliverables, but the discussion, decisions, and knowledge capture that produced them. If something applies to how you approach any process-engineering project — not just one — it belongs in this repo’s Wiki. If it’s specific to one project’s design, schedule, deliverables, or history, it belongs in that project’s own repo.
Why Multiple Fictional Projects, One Shared Approach
Each project here is a self-contained fictional scenario, but they share a common teaching goal: that project success depends as much on stakeholder engagement and communication as on technical skill. Rather than duplicating that philosophy and the associated conventions (milestone structure, versioning format, GitHub-App persona setup) in every project repo, they’re documented once here and referenced from each project.
License: © 2026 William Docter and Second-Hand Tigers. This work is licensed under a Creative Commons Attribution 4.0 International License (CC BY 4.0). You may copy, redistribute, remix, and build upon this material, including for commercial purposes, provided you give appropriate credit to William Docter and Second-Hand Tigers and indicate if changes were made. The Second-Hand Tigers logo is not covered by this license. All rights in it are reserved.