Indian MEP engineers deserve a vault, not another blog.

Walk into any MEP design office in India and you will find the same recurring problem — engineers spending hours hunting through scattered code books, vendor catalogues, scattered PDFs, and informal WhatsApp groups for a number that should be one click away. Younger engineers especially lose weeks of productive time to this friction in their first two to three years on the job. A senior engineer’s “back-of-envelope” rule of thumb often stays trapped in their head, never written down, never passed forward.

MEPVAULT exists to compress that friction. We codify what we use day-to-day on real projects — Indian climates, Indian codes, Indian tender realities — into searchable references and ready-to-use calculators. The aim is simple: make the next generation of MEP engineers technically stronger, time-efficient, and confident with the codes from the day they walk into their first job.

A consortium, not an author.

Articles published on MEPVAULT are reviewed by a small group of practising MEP consultants and design engineers active across hospitality, healthcare, commercial, and infrastructure projects in India. We deliberately do not surface individual contributor names on the public site. The reasoning is straightforward — the engineering content stands on its code references and calculation rigour, not on personality. Bylines that emphasise the author over the engineering invite either celebrity or controversy; both are useless to a working engineer trying to size a pump.

Where credit is due — vendor catalogue interpretations, project case studies, comparative analyses — we cite the source standard, manufacturer publication, or anonymised project context. Real-project anecdotes that appear in our “From the Field” notes are drawn from genuine consulting work and edited for confidentiality before publication.

• Code-anchored, not opinion-led. Every meaningful claim cites a clause number from a current code edition.
• Indian climate first. Composite, hot-humid, hot-dry, and warm-humid zones are the design context — not a generic North American baseline.
• Vendor-neutral. Where we name a vendor (Carrier, Trane, Daikin, Hitachi, Voltas, Blue Star, Mitsubishi Electric, Cummins, Grundfos, A.O. Smith, etc.) it is for engineering specificity, not endorsement.
• Calculation-first. A worked example beats a paragraph of prose. If a topic can be reduced to a calculator, it gets one.
• Errata are public. Reader-reported corrections receive a dated correction notice on the affected article. Technical accuracy is non-negotiable.

If you are a practising MEP engineer with original technical content to contribute — a case study from a recent project, a design heuristic that has held up across ten projects, a vendor selection table you have built and verified — write to us at admin@mepvault.com with the subject Article Suggestion. We do not publish promotional or vendor-funded copy. We do publish well-engineered, code-anchored, India-context original work from active practitioners.

If you have spotted an error in a published article or calculator, please report it the same way (subject: Correction). Reader-reported corrections account for a meaningful share of our editorial improvements.