10.46243/jst.2022.v07.i07.pp27-35 registered
Designing Efficient HVAC Systems Best Practices for Optimization
Resolves to https://www.jst.org.in/index.php/pub/article/view/1070
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v07.i07.pp27-35
Registered 29 Sep 2026 via crossref · record version 2 · last change 30 Sep 2026, 12:00 AM · record sha256 00a4672cdc6ea914…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
Also as schema.org JSON-LD · Turtle · RDF/XML · DataCite XML · Crossref UNIXREF · Crossref UNIXSD — the formats of the DOI content-negotiation service, from this record (which carries what).
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Designing Efficient HVAC Systems Best Practices for Optimization (PrincipalTitle · en)
Published 2022
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 07 · issue 07 · pages 27–35
Agents
- SYED JUNAID UDDIN (author)
- MOHAMMED TAHER (author)
- RAZA AHMED KHAN (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v07.i07.pp27-35
Abstract · en
When it comes to developing technical solutions for different types of buildings that are energy efficient, this publication is seen as the most viable avenue. Starting with the first design calculations, this journey is initiated. As a building's components, the heat and mass balances provide the groundwork for making HVAC systems that are both efficient and affordable. In addition to calculating mass and heat, a thorough investigation of the building's geometric dimensions and thermal performance envelope is required. This research takes a look at a unique approach to calculating the heat load of HVAC systems. Improvements in the estimation of building heat losses are shown by the approach under consideration. The suggested technique is used to calculate transmission heat losses using the elemental approach. Various methods of accounting for the infiltration component are shown in the technique for determining ventilation heat losses. A method for integrating the many components of thermal energy use into a unified mathematical framework is laid forth. An analysis of the approach of optimising heat loads under harsh operating circumstances is presented. The study presents the results of calculations and additional methods for using correct methods in building design. As a conclusion, this article suggests a few things.
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2022.v07.i07.pp27-35 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Designing Efficient HVAC Systems Best Practices for Optimization (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: SYED JUNAID UDDIN author: MOHAMMED TAHER author: RAZA AHMED KHAN publisher: Longman Publishers published: 2022 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 07 · no. 07 · pp. 27–35 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2026-09-24 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
Cited by — in this registry
No record held in this registry cites this DOI.
Counts only records held in this registry; a citation from a work held elsewhere is not seen here. The list as JSON
Relations
The record states no relation, and no record held here states one with this DOI.
Funding
The record names no funder.
Each funder's page lists every work held here that names it. ROR IDs open at ror.org; Funder Registry IDs resolve at doi.org.
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 76 fields set · sha256 0a50b59449e3… |
| 2 | 30 Sep 2026, 12:00 AM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
Changes made at Crossref through DOI Doctor
Every deposit Smart Scholars' DOI Doctor made for this DOI, oldest first, with Crossref's own answer. Each fingerprint is the SHA-256 of its entry and of the fingerprint before it, so a change to any earlier entry changes every fingerprint after it.
| When | What changed | Crossref | Fingerprint |
|---|---|---|---|
| 27 Sep 2026, 02:07 | Licence added https://creativecommons.org/licenses/by/4.0/ | ● accepted by Crossref | f5528218c0e1… |
| 27 Sep 2026, 02:13 | Address updated from https://www.jst.org.in/index.php/pub/article/view/1070/930 to https://www.jst.org.in/index.php/pub/article/view/1070 | ● accepted by Crossref | 1f699481dd0d… |
| 27 Sep 2026, 02:34 | Read back: the DOI resolves to the new address | ● confirmed | bcb9c9d52aa7… |
3 entries · the last fingerprint bcb9c9d52aa71bf180939e116cd4e96b5288e4a27b71ac7327a2b55959c9244f · the history as JSON, each entry with the fingerprint before it, to check them yourself.



