10.46243/jst.2022.v7.i05.pp60-72 registered
ANALYSIS, DESIGN AND STRUCTURAL ESTIMATION OF RCC STRUCTURE USING ETABS AND MICROSOFT EXCEL
Resolves to https://www.jst.org.in/index.php/pub/article/view/493
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v7.i05.pp60-72
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 4ff4b0deaab353ee…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
ANALYSIS, DESIGN AND STRUCTURAL ESTIMATION OF RCC STRUCTURE USING ETABS AND MICROSOFT EXCEL (PrincipalTitle)
Published 2023-07-18
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 7 · issue 5 · pages 60–72
Agents
- Kartik Ravikumar Kajagar Kartik Ravikumar Kajagar (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v7.i05.pp60-72
Abstract
Since India is a developing country, many new projects are being started on a daily basis that must be finished within a certain time frame. The main factors in project completion are design and implementation, which aid in the stability of the structure. In this dissertation, we describe our novel method to design utilising ETABS and Microsoft Excel. We start by designing the structure and simulating it in ETABS software using various loads and load combinations according to the IS codebook, then exporting to MS Excel and additional processing delivers the entire detailed and schedule drawings of the RCC structure. Following the design of structural elements, we must acquire the bar bending schedule in order to achieve structural estimation. So, after we have the bar bending schedule, we can calculate the quantity of steel and concrete required in the building, and then we can estimate the cement, sand, coarse aggregate, and bricks based on the concrete given. The outcome of our proposed strategy demonstrates that the procedure is very efficient, saving time and money. Normally, the design process takes many hours to complete, but with the aid of this proposed approach, efficient solutions may be obtained in just a few minutes
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.v7.i05.pp60-72 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | ANALYSIS, DESIGN AND STRUCTURAL ESTIMATION OF RCC STRUCTURE USING ETABS AND MICROSOFT EXCEL (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Kartik Ravikumar Kajagar Kartik Ravikumar Kajagar publisher: Longman Publishers published: 2023-07-18 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 7 · no. 5 · pp. 60–72 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 | 2024-02-16 | 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
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) | 85 fields set · sha256 2047afc7fe07… |
| 2 | 29 Sep 2026, 11:59 PM | 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.
