Structural and Civil Engineering Curriculum

Civil Sys

Module from the Structural and Civil Engineering Curriculum curriculum.

Module 10 - Civil Systems · Learning Objectives · 1. Design paved roads for H-20 loading per AASHTO · 2. Size stormwater drainage for 10-yr 24-hr storm (local) · 3. Separate oily water sewer (OWS) from sanitary from stormwater · 4. Specify chain-link fencing per IPE-EP-4-10-1 · 5. Apply ADA accessibility for office buildings per IPE-EP-4-6-2 · Sewer System Separation (API 2610)

System	Flow	Treatment	Notes	Typical Pipe	Ref
Oily water sewer (OWS)	Process drains, pump glands	API separator + DAF	Contaminated	8-12 in concrete or HDPE	API 2610
Storm (rainwater)	Paved and process areas	Gravity to catch basin	First-flush to OWS	12-24 in	API 2610
Sanitary	Office and wash rooms	Septic or POTW	Domestic only	6-8 in PVC	Local code
Chemical (acid/caustic)	Spot drains	Neutralization	Dedicated	Fiberglass or specialty	Special
Fire water	Hydrants	Storage + pumps	Per NFPA 24	Ductile iron	NFPA 24

Source: Structural_Civil_Engineering_Curriculum_v1.xlsx · Sheet: Civil Sys

© 2026 Inflection Point Engineering, LLC. All rights reserved. The content of this page — including calculation methods, reference data, written analysis, interactive tools, and source code — is the intellectual property of Inflection Point Engineering, LLC and is protected under applicable copyright, trademark, and trade secret laws. Unauthorized reproduction, redistribution, modification, or derivative use in whole or in part is prohibited without prior written consent.

Disclaimer. This material is provided for informational and educational purposes only and does not constitute professional engineering advice. Calculations, reference data, and methodologies are based on published standards and accepted engineering practice but are not a substitute for engineering judgment, site-specific analysis, or review by a licensed Professional Engineer. Inflection Point Engineering, LLC makes no warranties, express or implied, regarding the accuracy, completeness, or fitness for a particular purpose of any content presented here, and shall not be liable for any direct, indirect, incidental, or consequential damages arising from its use. Users assume all risk associated with applying this content to real-world design, operations, or decisions.