10.46243/jst.2024.v9.i2.pp52-71 registered
Big Data and Robotic Process Automation: Driving Digital Transformation in the Telecommunications Sector
Resolves to https://jst.org.in/index.php/pub/article/view/1041
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2024.v9.i2.pp52-71
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 31be81a49206d049…
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
Big Data and Robotic Process Automation: Driving Digital Transformation in the Telecommunications Sector (PrincipalTitle)
Published 2024-02-24
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 09 · issue 02 · pages 52
Agents
- Raj Kumar Gudivaka (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2024.v9.i2.pp52-71
Abstract
The telecom industry is undergoing a change because to the combination of Big Data analytics and Robotic Process Automation (RPA), which boosts customer happiness, operational efficiency, and strategic decision-making. While big data analytics makes it possible to handle and analyse massive datasets in order to derive relevant insights, robotic process automation (RPA) automates repetitive operations, lowers error rates, and speeds up processes. This study highlights the combined influence of RPA and Big Data on the digital transformation of the telecoms industry by examining their synergistic interaction. Key obstacles are identified by the research, including the possibility of implementing RPA incorrectly, the significance of protecting data privacy, and the need for qualified staff to oversee these technologies. According to the study results, 65% of participants are aware of the risks involved in implementing RPA and stress the importance of thorough configuration and preparation. Furthermore, as noted by 55% of respondents, maintaining data privacy in multi-departmental settings can be challenging. The results highlight the potential for transformation that can arise from strategically aligning RPA with Big Data, but they also highlight the dangers that must be addressed in order to effectively leverage these technologies. For telecom businesses looking to maximise their use of RPA and Big Data to maintain their competitiveness in the quickly changing digital market, this paper offers insightful analysis and helpful suggestions.
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.2024.v9.i2.pp52-71 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Big Data and Robotic Process Automation: Driving Digital Transformation in the Telecommunications Sector (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Raj Kumar Gudivaka publisher: Longman Publishers published: 2024-02-24 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 09 · no. 02 · pp. 52 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-08-26 | 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) | 86 fields set · sha256 7d1d142c8de1… |
| 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.
