The reviewed record of science sign in
Pith

arxiv: 2607.06170 · v1 · pith:K67KTN4Q · submitted 2026-07-07 · cs.CE

The Documentation and Traceability Burden of the Indian EV Transition

Dawar Jyoti Deka , Nilesh Sarkar This is my paper

Reviewed by Pith T0 review T1 audit T2 compute T3 formal T4 kernel 2026-07-08 14:25 UTCglm-5.2pith:K67KTN4Qrecord.jsonopen to challenge →

classification cs.CE
keywords burdendocumentationevidenceindianbottleneckscompliancedocumentfailure
0
0 comments X

The pith

EV fires, subsidy fraud, and registration gaps share one root cause

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

This paper argues that India's electric-vehicle transition has created a heavy, growing, and previously unmapped documentation burden, and that the field's recurring compliance failures — from the 2022 e-scooter fire recalls to the FAME-II subsidy disputes to the Ola Electric registration gap — are not isolated incidents of negligence but four instances of a single breakdown pattern in the compliance-document lifecycle. The authors systematise this burden for the first time as an information-systems problem, organising it into two layers: an inherited automotive quality-document spine (PPAP packages, material certificates, control plans) that every car maker already carries, and an EV-acute regulatory stack (battery-safety test evidence, cyber-security records, software-update documentation with decade-long retention horizons) that electrification adds on top. The central object they introduce is a six-stage lifecycle model — Create, Submit, Verify, Approve, Record, Retrieve — through which every compliance artefact moves, with manual bottlenecks marked at Verify, Approve, and Retrieve, and a structural decoupling between an approval signature and the artefact it approves. Four documented failure cases are each pinned to a specific stage where the evidence chain broke: post-incident reconstruction across systems (Retrieve), conflicting agency conclusions from one evidence base (Verify), competing record systems holding different truths (Record), and off-specification test evidence approved anyway (Create and Approve). The paper also proposes an analytic lens called documentation exergy destruction, borrowed by analogy from thermodynamics, which classifies document families by the mandatory verification and record-keeping work they carry and explains why that work is systematically under-resourced: because it is mandatory, output-adjacent, and invisible in the finished product, it attracts neither talent nor tooling investment, and starved verification is precisely the condition under which the observed failures occur. Seven evidence-architecture requirements and a six-problem research agenda are derived from the lifecycle model and the failure cases.

Core claim

The paper's central claim is that four seemingly different compliance failures in the automotive and EV domain — the 2022 Indian e-scooter fire recalls, the FAME-II localisation subsidy dispute, the Ola Electric February 2025 registration gap, and the 2024 Japanese certification irregularities — are four instances of one underlying pattern: a breakdown at a specific stage of a six-stage compliance-document lifecycle where manual verification, approval, or retrieval is overwhelmed. The authors construct this lifecycle model inductively from the cases themselves and then use it to derive seven necessary architecture requirements (version anchoring, tamper-evidence, approval-to-artefact binding

What carries the argument

The six-stage compliance-document lifecycle model (Create/Generate, Submit/Exchange, Verify/Reconcile, Approve/Sign, Record/Retain, Retrieve/Reconstruct) with a Change/Revalidate return loop; the two-layer evidence-obligation structure (inherited quality spine + EV-acute regulatory stack); the documentation exergy destruction lens classifying document families along four dimensions (verification effort, reconciliation complexity, retention horizon, audit probability and consequence); seven evidence-architecture requirements (A1–A7) derived from the failure loci; and a six-problem research agenda (P1–P6) covering reconciliation accuracy, human-in-the-loop reliability, cross-party provenance,

If this is right

  • If the unification claim holds, any future compliance failure in the EV or automotive domain should be diagnosable as a breakdown at one of the six lifecycle stages, making the model a predictive rather than merely descriptive tool.
  • The seven architecture requirements (A1–A7) could serve as a procurement or audit checklist for OEMs evaluating evidence-management systems, shifting vendor selection from feature comparison to failure-prevention coverage.
  • The documentation exergy destruction lens, if operationalised quantitatively, could give OEMs and regulators a way to measure and compare the compliance burden across vehicle programmes, making under-resourcing visible and manageable for the first time.
  • The research agenda's call for a reconciliation-accuracy benchmark distinct from extraction accuracy could redirect the document-AI research community toward a problem that current benchmarks do not measure.
  • Machine-verifiable regulatory design (P6), if pursued by Indian regulators, could shift conformance checking from after-the-fact human reading to automatic verification at the point of artefact creation, fundamentally changing the economics of compliance.

Load-bearing premise

The paper's central structural claim depends on the assertion that the four failure cases are instances of one underlying lifecycle breakdown pattern rather than four domain-specific problems that share superficial similarity. The lifecycle model is constructed inductively from the cases themselves, and no independent validation — no fifth case predicted in advance, no quantitative fit measure, no counterexample analysis — is offered. If the cases are genuinely heterogeneous,

What would settle it

A fifth compliance failure case that cannot be cleanly mapped to any single stage of the six-stage lifecycle model, or a case that maps to multiple stages simultaneously in a way the model cannot disambiguate, would weaken the unification claim. Conversely, a case predicted in advance by the model and confirmed at the predicted lifecycle stage would strengthen it.

read the original abstract

The electric vehicle transition in India is usually told through batteries, cost and charging. Less visibly, it is a story about documentation. Electrification layers a new and fast growing burden of compliance evidence, type approval test reports, battery safety and thermal propagation records, cyber security and software update documentation, and supplier quality packages, on top of the evidence apparatus the automotive industry already carries, with retention horizons that now reach a decade past end of production. This burden is studied from the testing side but has never been systematised as an information systems problem, so its verification bottlenecks, architecture requirements and open questions remain unmapped. We close that gap for the Indian EV OEM with four contributions. These include a two layer systematisation of evidence obligations organised by artefact, producer, verifier, trigger and retention, a lifecycle model of the compliance document with manual bottlenecks and four observed failure loci marked, an analytic lens, documentation exergy destruction, that classifies document families and explains systematic under resourcing, and a research agenda spanning reconciliation accuracy, human in the loop reliability, cross party provenance, long horizon integrity, burden measurement and machine verifiable regulation. Three Indian failure cases and one Japanese ground the analysis.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

3 major / 7 minor

Summary. This manuscript systematises the compliance-document and traceability burden of India's electric-vehicle transition from an information-systems perspective. It organises evidence obligations into two layers (an inherited automotive quality spine and an EV-acute regulatory stack), presents four documented failure cases (three Indian, one Japanese), abstracts them into a six-stage compliance-document lifecycle model, proposes an analogical 'documentation exergy destruction' lens, and derives seven evidence-architecture requirements plus a six-problem research agenda. The regulatory mapping (Section 4, Table 2) is carefully sourced with snapshot-date caveats and contested-date notes. The failure cases (Section 5) are drawn from public records, with contested matters stated as contested and company positions given. The competing-interest disclosure (Erdős Systems) is transparent.

Significance. The paper addresses a genuine gap: the intersection of domain-specific automotive/EV compliance artefact chains, an information-systems and records lens, and an India-led compliance framing appears unoccupied in the surveyed literature. The two-layer evidence-obligation systematisation (Tables 1–2, Figure 1) is a useful reference for practitioners and researchers. The research agenda (Section 9) is well-scoped, with each problem stated as open and paired with a progress criterion. The exergy-destruction lens (Section 7) is honestly caveated as qualitative and analogical, and the document-family taxonomy (Appendix B, Table 5) makes it concrete enough to be testable. The lifecycle model, while inductively constructed, provides a serviceable organising framework for the domain.

major comments (3)
  1. Section 6, final paragraph: the claim that 'The four cases look like four different problems. The lifecycle model shows they are four instances of one' is an analytic assertion, not a tested hypothesis. The six-stage model is constructed inductively from the same four cases (Section 5 → Section 6), and no independent validation is offered — no fifth case predicted in advance, no quantitative fit metric, no counterexample analysis. Each case maps to a different lifecycle stage (A→Retrieve, B→Verify, C→Record, D→Create/Approve), which is consistent with the model but also consistent with mere re-description: any four failures in a six-stage pipeline will map to some stages. The concern is not that the model is wrong but that the paper does not distinguish 'one underlying pattern with four manifestations' from 'four heterogeneous problems that share a pipeline.' This matters because the unv
  2. Section 8: the architecture requirements A1–A7 are described as 'derived from the failures rather than from any product,' and the section states they are 'the conditions under which the four failures would not have occurred, read off the stages at which they occurred.' However, if the lifecycle model's unification is re-description rather than explanation (see preceding comment), the derivation force of A1–A7 weakens: they become a wishlist anchored to four anecdotes rather than requirements derived from a validated model. The paper should either (a) soften the derivation claim to acknowledge that A1–A7 are motivated by the cases rather than derived from a validated model, or (b) provide additional evidence for the model's explanatory power beyond fitting the four cases used to construct it. A counterexample analysis — a case where the model predicts a failure locus that is then verified
  3. Section 7: the exergy-destruction lens is introduced as an analogy that 'explains systematic under-resourcing' and 'reframes those failures' as 'the observable symptom of unmanaged destruction.' The lens is honestly caveated as qualitative and analogical, and the paper states it would survive its removal. However, the claim that the lens 'generates expectations that further cases can test' (Section 7, final paragraph) is not demonstrated. The document-family taxonomy (Table 5) classifies families along four dimensions, but the classification is asserted rather than derived from the analogy in a way that could not have been produced without it. The paper should clarify what specific predictions the lens generates that a simpler 'mandatory-but-under-resourced work' framing would not, or else reduce the claim for this section.
minor comments (7)
  1. Section 4, Table 2 note: the contested-date handling for AIS-189/AIS-190 and the ADAS suite is good practice. Consider adding a similar explicit note for the Battery Pack Aadhaar row, which is marked 'DRAFT' but whose 2027 target is mentioned only in the prose, not the table.
  2. Section 7: the exergy-destruction analogy would benefit from a brief note on where the analogy breaks down. For instance, thermodynamic exergy is conserved in reversible processes, whereas documentation effort has no analogous conservation law. The paper notes this ('not a conserved quantity') but a reader unfamiliar with thermodynamics may need the contrast stated more sharply where the term first appears.
  3. Figure 3: the 'M' marker for manual stages is defined in the caption but the visual distinction between manual and automated stages could be clearer (e.g., shading or colour rather than a letter marker). The approval-to-artefact decoupling cut is also hard to see at the resolution provided.
  4. Section 5, Case C: the paper states 'about 25,000' announced against 'roughly 8,600' VAHAN registrations. The exact figures (25,207 and 8,600) appear in Appendix C but not in the main text. Including the precise figures in Section 5 would strengthen the case.
  5. Table 5 (Appendix B): the destruction-class assignments are qualitative (High/Medium/Low). The paper could note that these are illustrative classifications awaiting empirical calibration, rather than validated scores. A brief note that the classification is a hypothesis to be tested, not a measurement, would strengthen the case.
  6. Section 9, P1: the claim that 'no benchmark exists' for compliance reconciliation is strong. A brief note on the search methodology (databases, keywords, date range) would allow verification.
  7. Reference [30] combines two sources (Electronics Media and Business Today) in a single citation. Separating these would improve traceability.

Simulated Author's Rebuttal

3 responses · 0 unresolved

We thank the referee for a careful and constructive report. The referee's three major comments all target the same underlying concern: the paper's inductive lifecycle model (Section 6) is constructed from four cases (Section 5) and then used to derive architecture requirements (Section 8) and motivate an analytic lens (Section 7), without independent validation that the model explains rather than merely re-describes. We agree this is the paper's weakest link and will revise all three sections to address it. Specifically: (1) we will add a fifth-case prospective analysis (the Daihatsu 2023 certification scandal, already cited but not mapped) and a counterexample analysis to test the model's predictive power beyond the construction set; (2) we will soften the derivation language for A1–A7 from 'derived from' to 'motivated by' while noting that the requirements are necessary conditions anchored to specific failure loci, not claims of sufficiency; and (3) we will clarify what specific predictions the exergy-destruction lens generates beyond a simpler framing, or reduce the claim accordingly. We disagree with none of the referee's substantive points; the question is the degree of revision at each.

read point-by-point responses

  1. Referee: Section 6, final paragraph: the claim that the four cases are 'four instances of one' is an analytic assertion, not a tested hypothesis. The model is constructed inductively from the same four cases, and no independent validation is offered. Each case maps to a different stage, which is consistent with the model but also consistent with mere re-description.

    Authors: The referee is correct that the model is inductively constructed from the four cases and that the unification claim is not independently validated in the current manuscript. We accept this criticism. In the revised manuscript we will take two steps. First, we will add a prospective fifth-case analysis: the Daihatsu certification scandal (December 2023, 174 irregularities across 64 models, already cited as reference [82] but not mapped to the lifecycle). This case was not used to construct the model, and we will show in advance which lifecycle stage the model predicts the failure should map to (Create/Generate and Approve/Sign, the same locus as Case D), then verify whether the public record confirms this. Second, we will add a counterexample analysis: we will identify a candidate case — the Tesla Autopilot NHTSA investigations — and ask whether the model predicts a failure locus that is then observed, or whether the model fails to accommodate the case, which would bound its scope. Third, we will soften the Section 6 unification claim from 'the lifecycle model shows they are four instances of one' to language that acknowledges the model is an inductive organising framework whose explanatory power is tested prospectively by the fifth case and bounded by the counterexample, not proven by the construction set. We will not claim more validation than these steps provide. revision: yes

  2. Referee: Section 8: if the lifecycle model's unification is re-description rather than explanation, the derivation force of A1–A7 weakens. The paper should either soften the derivation claim or provide additional evidence for the model's explanatory power.

    Authors: The referee's logic is sound: if the model is re-description, then A1–A7 inherit that weakness. We will take option (a) from the referee's comment and soften the derivation language. Specifically, we will change 'derived from the failures rather than from any product' and 'the conditions under which the four failures would not have occurred, read off the stages at which they occurred' to language stating that A1–A7 are motivated by the cases and anchored to specific lifecycle stages and failure loci, not derived from a validated model. We will retain the claim that each requirement is a necessary condition for preventing the specific failure it addresses (e.g., A3 is necessary to prevent the approval-decoupling failure of Case A), because that claim is local to the case and does not depend on the model's global unification. But we will not claim that A1–A7 are jointly sufficient or that they follow from a validated model. We will also add a sentence noting that the fifth-case prospective analysis (from our response to Comment 1) provides partial evidence for the model's explanatory power, and therefore for the requirements anchored to the stage it predicts. revision: yes

  3. Referee: Section 7: the claim that the exergy-destruction lens 'generates expectations that further cases can test' is not demonstrated. The document-family taxonomy is asserted rather than derived from the analogy in a way that could not have been produced without it. The paper should clarify what specific predictions the lens generates beyond a simpler 'mandatory-but-under-resourced work' framing, or reduce the claim.

    Authors: We partially accept this comment. The referee is right that the current manuscript does not demonstrate a prediction from the lens that a simpler framing could not produce. We see two candidate predictions that the exergy-destruction framing generates and that 'mandatory-but-under-resourced work' does not, and we will add them explicitly. First, the lens predicts that failures will cluster in high-destruction document families (Table 5) rather than being uniformly distributed across all mandatory work — because destruction concentrates where verification effort, reconciliation complexity, retention horizon and audit consequence are simultaneously high. A simpler framing predicts under-resourcing everywhere; the lens predicts it differentially and identifies where. Second, the lens predicts that destruction is structurally irreducible (it can be reduced by better process design but never driven to zero), which implies that no amount of resourcing eliminates the failure mode entirely — only changes its threshold. This is a different policy prediction than 'invest more in compliance.' However, we acknowledge that these predictions are not yet tested in the manuscript. We will therefore reduce the claim from 'generates expectations that further cases can test' to 'generates two specific predictions that distinguish it from a simpler framing, which further cases can test,' and we will state the predictions concretely. If the referee finds even this insufficient, we are prepared to reduce the section further to a classificatory framework with the predictive claims removed. revision: partial

Circularity Check

0 steps flagged

No significant circularity found; the paper is an inductive systematisation with no fitted parameters, no self-cited load-bearing theorems, and no predictions that reduce to inputs by construction.

full rationale

The paper is a systematisation and analysis paper, not a derivation or prediction paper. Its central structural claim — that four failure cases are instances of one lifecycle model — is constructed inductively from the cases themselves (Section 5 → Section 6), which is standard methodology for this genre of work. The lifecycle model (six stages, four failure loci) is not a fitted model with parameters tuned to reproduce the cases; it is a descriptive framework, and the paper makes no quantitative prediction that could be circularly forced by its inputs. The exergy-destruction lens (C3) is borrowed from thermodynamics as an explicitly qualitative analogy (Section 7: 'The borrowing is explicitly analogical, an analogy and not an identity'), with no fitted parameters, no normalisation choices, and no self-cited results that force the conclusions. The architecture requirements A1–A7 (Section 8) are derived from the lifecycle model's failure-loci mapping, but this derivation is logical (necessary conditions for the failures not to recur), not mathematical, and does not reduce to a fit. The competing-interest disclosure (Erdős Systems) is transparent and does not create a circularity. The companion paper is referenced for future development, not as load-bearing support for the present claims. No step in the paper's argument chain reduces, by construction or by self-citation, to its own inputs.

Axiom & Free-Parameter Ledger

0 free parameters · 4 axioms · 2 invented entities

The paper introduces no free parameters (no fitted constants, no hand-tuned numbers). It relies on four axioms: three domain assumptions (the cases are instances of one pattern, the literature intersection was empty, the regulatory snapshot is accurate) and one ad-hoc-to-paper construct (the exergy-destruction analogy). Two invented entities are introduced: the exergy-destruction lens and the six-stage lifecycle model. Both are analytic constructs rather than physical entities; the exergy lens has a falsifiable handle (predicts which families fail first) but it has not been independently validated in this paper.

axioms (4)
  • domain assumption The four failure cases (2022 fires, FAME-II dispute, Ola registration gap, Toyota certification) are instances of one underlying lifecycle breakdown pattern rather than four domain-specific problems.
    Section 6: 'The four cases look like four different problems. The lifecycle model shows they are four instances of one.' This is the inductive foundation for the unification claim and the architecture requirements derived from it.
  • domain assumption The intersection of domain-specific automotive/EV evidence artefacts, an information-systems lens, and an India-led compliance framing was previously empty.
    Section 2: 'The intersection is therefore empty. No work occupies the centre... We searched for one; if it existed, this paper would be an extension rather than a systematisation.' Supported by the nearest-neighbour survey (Appendix D) but ultimately an assertion about absence.
  • ad hoc to paper Documentation exergy destruction is a valid analogical transfer from thermodynamic exergy, preserving the structural property of mandatory, irreducible, minimisable dissipation.
    Section 7: 'The borrowing is explicitly analogical, an analogy and not an identity.' The authors state they take the structure, not the mathematics. The axiom is that the structural analogy holds and generates testable predictions about which document families fail first.
  • domain assumption The regulatory position stated is accurate as of the snapshot date (3 July 2026).
    Section 4: 'Regulatory position stated as of the snapshot date, 3 July 2026.' The paper notes a delta sweep found no reversals. This is a temporal assumption: the regulatory landscape moves, and the systematisation is only as current as the snapshot.
invented entities (2)
  • Documentation exergy destruction independent evidence
    purpose: An analytic lens that classifies document families by the mandatory verification and record-keeping work they carry, explaining systematic under-resourcing by analogy to thermodynamic exergy destruction.
    The lens generates falsifiable predictions: high-destruction families (PPAP Level 3, homologation packs, software-update record sets) should fail first when under-resourced. The classification in Table 5/Appendix B is the testable payload. However, no case in the paper was predicted in advance using the lens; the cases were classified post hoc. The lens is hypothesis-generating but not yet independently validated.
  • Six-stage compliance-document lifecycle model (Create/Generate, Submit/Exchange, Verify/Reconcile, Approve/Sign, Record/Retain, Retrieve/Reconstruct) no independent evidence
    purpose: A unifying model that abstracts four observed failure cases into instances of breakdown at specific stages of a single lifecycle.
    The model is constructed inductively from the four cases in Section 5. No independent validation (fifth case predicted, quantitative fit, counterexample analysis) is offered. It is an organising framework, not a validated theory.

pith-pipeline@v1.1.0-glm · 25059 in / 3442 out tokens · 498260 ms · 2026-07-08T14:25:06.739881+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Reference graph

Works this paper leans on

90 extracted references · 90 canonical work pages · 4 internal anchors

  1. [1]

    Amazon textract.https: //aws.amazon.com/textract/ , 2024

    Amazon Web Services. Amazon textract.https: //aws.amazon.com/textract/ , 2024. Accessed 2026-07-03

    work page 2024

  2. [2]

    Manmatha

    SrikarAppalaraju, BhavanJasani, BhargavaUrala Kota, Yusheng Xie, and R. Manmatha. Doc- Former: End-to-End Transformer for Document Understanding. InProc. IEEE/CVF ICCV 2021, pages 993–1003, 2021

    work page 2021

  3. [3]

    Arner, János Barberis, and Ross P

    Douglas W. Arner, János Barberis, and Ross P. Buckley. FinTech, RegTech, and the Reconceptu- alization of Financial Regulation.Northwestern Journal of International Law & Business, 37(3): 371–414, 2017

    work page 2017

  4. [4]

    Toyota’s safety tests do not meet UN Regulations: Japan Transport Ministry

    Asia News Network (The Japan News/Yomiuri). Toyota’s safety tests do not meet UN Regulations: Japan Transport Ministry. https://asianews .network/toyotas-safety-tests-do-not-mee t-un-regulations-japan-transport-ministr y/, 2024. 65 vs 50 degree pedestrian test. Accessed 2026-07-03

    work page 2024

  5. [5]

    SFIO raids Hero Electric, Benling, Okinawa for FAME subsidy misappropri- ation

    Autocar Professional. SFIO raids Hero Electric, Benling, Okinawa for FAME subsidy misappropri- ation. https://www.autocarpro.in/news/sfi o-raids-hero-electric-benling-okinawa-f or-fame-subsidy-misappropriation-123794 ,

    work page

  6. [6]

    Corroborated by Inc42

    Search operations reported December 2024; about Rs 297 crore. Corroborated by Inc42. Ac- cessed 2026-07-03. 10

    work page 2024

  7. [7]

    Production Part Approval Process (PPAP)

    Automotive Industry Action Group. Production Part Approval Process (PPAP). Technical report, AIAG, 2006

    work page 2006

  8. [8]

    AIS- 038 (Rev.2): Electric Power Train Vehicles of Categories M and N – CMVR Type Approval

    Automotive Research Association of India. AIS- 038 (Rev.2): Electric Power Train Vehicles of Categories M and N – CMVR Type Approval. Technical report, ARAI (for MoRTH), 2020

    work page 2020

  9. [9]

    AIS- 156: Specific Requirements for L Category Electric Power Train Vehicles

    Automotive Research Association of India. AIS- 156: Specific Requirements for L Category Electric Power Train Vehicles. Technical report, ARAI (for MoRTH), 2020. Amended through Amendment 4, December 2023

    work page 2020

  10. [10]

    AIS- 189: Cyber Security and Cyber Security Manage- ment System (modelled on UN Regulation No

    Automotive Research Association of India. AIS- 189: Cyber Security and Cyber Security Manage- ment System (modelled on UN Regulation No. 155). Technical report, ARAI (for MoRTH), 2023

    work page 2023

  11. [11]

    AIS- 190: Software Update and Software Update Man- agement System (modelled on UN Regulation No

    Automotive Research Association of India. AIS- 190: Software Update and Software Update Man- agement System (modelled on UN Regulation No. 156). Technical report, ARAI (for MoRTH), 2023

    work page 2023

  12. [12]

    Master integration with ERP, MES and QMS for compliance.https://www.av slifesciences.com/blog-post/master-integ ration-with-erp-mes-and-qms-for-complia nce-success, 2024

    AVS Life Sciences. Master integration with ERP, MES and QMS for compliance.https://www.av slifesciences.com/blog-post/master-integ ration-with-erp-mes-and-qms-for-complia nce-success, 2024. Accessed 2026-07-03

    work page 2024

  13. [13]

    Production part approval process (ppap): requirements and cycle.https://bangid .com/knowledge-base/manufacturing/what-i s-the-production-part-approval-process-p pap/, 2024

    Bang Design. Production part approval process (ppap): requirements and cycle.https://bangid .com/knowledge-base/manufacturing/what-i s-the-production-part-approval-process-p pap/, 2024. Level-3 cycle is complexity-dependent, not standardised. Accessed 2026-07-03

    work page 2024

  14. [14]

    RegTech – the application of modern infor- mation technology in regulatory affairs.Intelligent Systems in Accounting, Finance and Management, 27(4):161–167, 2020

    Michael Becker, Katja Merz, and Rüdiger Buchkre- mer. RegTech – the application of modern infor- mation technology in regulatory affairs.Intelligent Systems in Accounting, Finance and Management, 27(4):161–167, 2020

    work page 2020

  15. [15]

    John Wiley & Sons, 2nd edition, 1997

    Adrian Bejan.Advanced Engineering Thermody- namics. John Wiley & Sons, 2nd edition, 1997

    work page 1997

  16. [16]

    Analyses on standards and regulations for connected and automated vehi- cles: Identifying the certification roadmap.Trans- portation Engineering, 2023

    Meriem Benyahya, Anastasija Collen, and Niels Alexander Nijdam. Analyses on standards and regulations for connected and automated vehi- cles: Identifying the certification roadmap.Trans- portation Engineering, 2023

    work page 2023

  17. [17]

    Baumgartner

    KristinaBerger, Josef-PeterSchöggl, andRupertJ. Baumgartner. Digital battery passports to enable circular and sustainable value chains.Journal of Cleaner Production, 353:131492, 2022

    work page 2022

  18. [18]

    Safety cases and their role in ISO 26262 functional safety assessment

    John Birch, Roger Rivett, Ibrahim Habli, Ben Bradshaw, John Botham, Dave Higham, Peter Jesty, Helen Monkhouse, and Robert Palin. Safety cases and their role in ISO 26262 functional safety assessment. InComputer Safety, Relia- bility, and Security (SAFECOMP 2013), LNCS

    work page 2013

  19. [19]

    FAME-II: Hero Electric, Oki- nawa scooters claim no violation.https://www

    Business Standard. FAME-II: Hero Electric, Oki- nawa scooters claim no violation.https://www. business-standard.com/companies/news/fam e-ii-scheme-hero-electric-okinawa-scoot ers-claim-no-violation-123051001014_1.ht ml, 2023. Accessed 2026-07-03

    work page 2023

  20. [20]

    Business Standard. Ola Electric sales backlog: VAHAN registration scrutiny, February 2025.ht tps://www.business-standard.com/companie s/news/ola-electric-sales-backlog-vahan -registrations-scrutiny-february-2025-1 25032100174_1.html , 2025. 25,000 vs 8,600; RTO seizures. Accessed 2026-07-03

    work page 2025

  21. [21]

    Business Today. Hero Electric and Okinawa likely to get recovery notices over FAME-II subsidy.ht tps://www.businesstoday.in/latest/corpor ate/story/hero-electric-and-okinawa-lik ely-to-get-recovery-notices-over-fame-i i-subsidy-report-379397-2023-04-29 , 2023. Rs 10,000 crore scheme; 12-maker probe. Accessed 2026-07-03

    work page 2023

  22. [22]

    Hero Electric, Okinawa Autotech get clean chit in FAME scheme violation case

    Business Today. Hero Electric, Okinawa Autotech get clean chit in FAME scheme violation case. https://www.businesstoday.in/auto/story/ hero-electric-okinawa-autotech-get-clean -chit-in-fame-scheme-violation-case-427 163-2024-04-27, 2024. Accessed 2026-07-03

    work page 2024

  23. [23]

    Toyota apologizes for cheating on vehicle testing and halts production of three models

    CNBC (Associated Press). Toyota apologizes for cheating on vehicle testing and halts production of three models. https://www.cnbc.com/202 4/06/04/toyota-apologizes-for-cheating-o n-vehicle-testing-and-halts-production-o f-three-models.html, 2024. 3 June 2024; seven models. Accessed 2026-07-03

    work page 2024

  24. [24]

    Japan safety scandal: Toyota, Mazda halt some shipments as auto scan- dal widens

    CNN Business (Reuters). Japan safety scandal: Toyota, Mazda halt some shipments as auto scan- dal widens. https://www.cnn.com/2024/06/03 /business/toyota-mazda-halt-shipments-j apan-safety/index.html , 2024. Five makers named. Accessed 2026-07-03

    work page 2024

  25. [25]

    A comparative analysis of UN- ECE WP.29 R155 and ISO/SAE 21434

    Gianpiero Costantino, Marco De Vincenzi, and Ilaria Matteucci. A comparative analysis of UN- ECE WP.29 R155 and ISO/SAE 21434. InIEEE European Symposium on Security and Privacy Workshops (EuroS&PW), 2022

    work page 2022

  26. [26]

    Document AI: Benchmarks, Models and Applications

    Lei Cui, Yiheng Xu, Tengchao Lv, and Furu Wei. Document AI: Benchmarks, models and applica- tions.arXiv preprint arXiv:2111.08609, 2021

    work page internal anchor Pith review Pith/arXiv arXiv 2021

  27. [27]

    Marker: open-source PDF-to- markdown/JSON converter

    Datalab. Marker: open-source PDF-to- markdown/JSON converter. https://github .com/datalab-to/marker, 2024. Accessed 2026- 07-03

    work page 2024

  28. [28]

    Docling Technical Report

    Docling Team, IBM Research. Docling Technical Report. Technical report, IBM Research, 2024. Open source (MIT); arXiv:2408.09869. 11

    work page internal anchor Pith review Pith/arXiv arXiv 2024

  29. [29]

    Reliability and authenticity: The concepts and their implications.Archivaria, 39:5–10, 1995

    Luciana Duranti. Reliability and authenticity: The concepts and their implications.Archivaria, 39:5–10, 1995

    work page 1995

  30. [30]

    The long-term preservation of accurate and authentic digital data: The inter- pares project.Data Science Journal, 4:106–118, 2005

    Luciana Duranti. The long-term preservation of accurate and authentic digital data: The inter- pares project.Data Science Journal, 4:106–118, 2005

    work page 2005

  31. [31]

    India auto- motive regulatory developments, january to april 2026 (adas timeline reaffirmation; battery pack aadhaar draft)

    Electronics Media; Business Today. India auto- motive regulatory developments, january to april 2026 (adas timeline reaffirmation; battery pack aadhaar draft). https://www.electronicsmed ia.info/2026/04/07/indias-automotive-s ector-securing-indias-roads/ , 2026. Delta sweep for the six months before the snapshot. Ac- cessed 2026-07-03

    work page 2026

  32. [32]

    EN 10204: Metallic Products – Types of Inspection Documents

    European Committee for Standardization. EN 10204: Metallic Products – Types of Inspection Documents. Technical report, CEN, 2004

    work page 2004

  33. [33]

    Regulation (EU) 2023/1542 concerning batteries and waste batteries (battery passport, Article 77), 2023

    European Parliament and Council. Regulation (EU) 2023/1542 concerning batteries and waste batteries (battery passport, Article 77), 2023. Bat- tery passport applies from 18 February 2027

    work page 2023

  34. [34]

    Digital supply chain management agenda for the automotive supplier industry

    PooryaFarahani, ChristophMeier, andJörgWilke. Digital supply chain management agenda for the automotive supplier industry. InShaping the Dig- ital Enterprise, pages 157–172. Springer, 2016

    work page 2016

  35. [35]

    ColPali: Efficient Document Retrieval with Vision Language Models

    Manuel Faysse, Hugues Sibille, Tony Wu, Bilel Omrani, Gautier Viaud, Céline Hudelot, and Pierre Colombo. ColPali: Efficient document re- trieval with vision language models.arXiv preprint arXiv:2407.01449, 2024

    work page internal anchor Pith review Pith/arXiv arXiv 2024

  36. [36]

    Toyota halts sales of 3 cars after sub- mitting faulty data on pedestrian safety tests

    Fortune. Toyota halts sales of 3 cars after sub- mitting faulty data on pedestrian safety tests. https://fortune.com/asia/2024/06/03/to yota-halts-sales-3-cars-submitting-fau lty-data-pedestrian-safety-tests/ , 2024. Accessed 2026-07-03

    work page 2024

  37. [37]

    Actors, roles and value exchanges in the digital product pass- port ecosystem.Journal of Industrial Ecology, 2025

    Alexander Gieß and Frederik Möller. Actors, roles and value exchanges in the digital product pass- port ecosystem.Journal of Industrial Ecology, 2025

    work page 2025

  38. [38]

    Global battery alliance launches the world’s first battery passport proof of concept

    Global Battery Alliance. Global battery alliance launches the world’s first battery passport proof of concept. https://www.globalbattery.org/ press-releases/, 2023. Davos, 18 January 2023. Accessed 2026-07-03

    work page 2023

  39. [39]

    Document AI

    Google Cloud. Document AI. https://docs .cloud.google.com/document-ai/docs , 2024. Accessed 2026-07-03

    work page 2024

  40. [40]

    The journey to business process compliance

    Guido Governatori and Shazia Sadiq. The journey to business process compliance. InHandbook of Research on Business Process Modeling, pages 426–

    work page

  41. [41]

    2022 electric two-wheeler recalls: Okinawa 3,215; Pure EV 2,000; Ola 1,441 (total 6,656)

    Government of India, reply in the Lok Sabha. 2022 electric two-wheeler recalls: Okinawa 3,215; Pure EV 2,000; Ola 1,441 (total 6,656). Reported by The Week, https://www.theweek.in/news/ biz-tech/2022/07/20/manufacturers-recal ls-over-6-600-electric-two-wheelers.ht ml; corroborated by Saur Energy, 2022. Primary: government reply in the Lok Sabha. Accessed ...

    work page 2022

  42. [42]

    Hamilton

    David O. Hamilton. Records management in en- gineering firms.Journal of Management in Engi- neering (ASCE), 7(4):346–356, 1991

    work page 1991

  43. [43]

    M. A. Hannan, M. S. H. Lipu, A. Hussain, and A. Mohamed. A review of lithium-ion battery state of charge estimation and management sys- tem in electric vehicle applications: Challenges and recommendations.Renewable and Sustainable Energy Reviews, 78:834–854, 2017

    work page 2017

  44. [44]

    Are we done with business process compliance: State of the art and challenges ahead.Knowledge and Information Systems, 57(1):79–133, 2018

    Mustafa Hashmi, Guido Governatori, Ho-Pun Lam, and Moe Thandar Wynn. Are we done with business process compliance: State of the art and challenges ahead.Knowledge and Information Systems, 57(1):79–133, 2018

    work page 2018

  45. [45]

    Deriving ap- proval criteria for UN R155 cyber security type ap- proval.SAE Technical Paper 2024-01-2983, 2024

    Mario Hellstern, Bastian Langhanki, Richard Grun, Reiner Kriesten, and Eric Sax. Deriving ap- proval criteria for UN R155 cyber security type ap- proval.SAE Technical Paper 2024-01-2983, 2024

    work page 2024

  46. [46]

    From requirements to certification: A framework for compliant software update man- agement system implementation

    Jacqueline Henle, Christof Hohl, Stefan Otten, and Eric Sax. From requirements to certification: A framework for compliant software update man- agement system implementation. InIEEE Int. Conf. on Recent Advances in Systems Science and Engineering (RASSE), 2025

    work page 2025

  47. [47]

    Govt Committee Gives Clean Chit To Hero Electric, Okinawa Autotech In FAME Violation Case

    Inc42. Govt Committee Gives Clean Chit To Hero Electric, Okinawa Autotech In FAME Violation Case. https://inc42.com/buzz/govt-commi ttee-gives-clean-chit-to-hero-electric-o kinawa-autotech-in-fame-violation-case/ ,

    work page

  48. [48]

    Overcoming common PPAP chal- lenges that lead to OEM rejections.https://in tellaquest.com/overcoming-common-ppap-c hallenges-that-lead-to-oem-rejections/ ,

    IntellaQuest. Overcoming common PPAP chal- lenges that lead to OEM rejections.https://in tellaquest.com/overcoming-common-ppap-c hallenges-that-lead-to-oem-rejections/ ,

    work page

  49. [49]

    IATF 16949:2016 Quality Management System Require- ments for Automotive Production and Relevant Service Parts Organizations

    International Automotive Task Force. IATF 16949:2016 Quality Management System Require- ments for Automotive Production and Relevant Service Parts Organizations. Technical report, IATF, 2016

    work page 2016

  50. [50]

    ISO/IEC 17050: Conformity Assessment – Sup- plier’s Declaration of Conformity

    International Organization for Standardization. ISO/IEC 17050: Conformity Assessment – Sup- plier’s Declaration of Conformity. Technical report, ISO, 2004

    work page 2004

  51. [51]

    ISO 15489-1:2016 Information and documentation 12 – Records management – Part 1: Concepts and principles

    International Organization for Standardization. ISO 15489-1:2016 Information and documentation 12 – Records management – Part 1: Concepts and principles. Technical report, ISO, 2016

    work page 2016

  52. [52]

    A critical re- view of lithium-ion battery safety testing and stan- dards.Applied Thermal Engineering, 231:121014, 2023

    Joris Jaguemont and Fanny Bardé. A critical re- view of lithium-ion battery safety testing and stan- dards.Applied Thermal Engineering, 231:121014, 2023

    work page 2023

  53. [53]

    Supplier quality management for component introduction in the automotive industry.Procedia - Social and Behav- ioral Sciences, 221:423–432, 2016

    Cristina-Georgiana Lixandru. Supplier quality management for component introduction in the automotive industry.Procedia - Social and Behav- ioral Sciences, 221:423–432, 2016

    work page 2016

  54. [54]

    LlamaParse: generative-AI-native document parsing

    LlamaIndex. LlamaParse: generative-AI-native document parsing. https://docs.llamainde x.ai/en/stable/llama_cloud/llama_parse/ ,

    work page

  55. [55]

    Digital product passports: Aliteraturereviewandresearchagenda

    João Lopes and João Barata. Digital product passports: Aliteraturereviewandresearchagenda. InProcedia Computer Science (CENTERIS 2024), 2024

    work page 2024

  56. [56]

    Implementation challenges of the EU digital battery passport

    Elena Losa and Stein Torjesen. Implementation challenges of the EU digital battery passport. Cleaner Production Letters, 2025

    work page 2025

  57. [57]

    Thermal behaviour and thermal runaway propagation in lithium-ion battery systems: A critical review

    Sirshendu Mallick and Debashis Gayen. Thermal behaviour and thermal runaway propagation in lithium-ion battery systems: A critical review. Journal of Energy Storage, 62:106894, 2023

    work page 2023

  58. [58]

    Minesh Mathew, Dimosthenis Karatzas, and C. V. Jawahar. DocVQA: A dataset for VQA on docu- ment images. InProc. IEEE/CVF Winter Conf. on Applications of Computer Vision (W ACV), 2021

    work page 2021

  59. [59]

    Placing records continuum the- ory and practice.Archival Science, 1(4):333–359, 2001

    Sue McKemmish. Placing records continuum the- ory and practice.Archival Science, 1(4):333–359, 2001

    work page 2001

  60. [60]

    Azure AI document intelligence.https: //azure.microsoft.com/en-us/products/a i-services/ai-document-intelligence , 2024

    Microsoft. Azure AI document intelligence.https: //azure.microsoft.com/en-us/products/a i-services/ai-document-intelligence , 2024. Accessed 2026-07-03

    work page 2024

  61. [61]

    Battery Waste Management Rules, 2022, 2022

    Ministry of Environment, Forest and Climate Change, India. Battery Waste Management Rules, 2022, 2022. Extended Producer Responsibility; CPCB registration

    work page 2022

  62. [62]

    PM Electric Drive Revolution in Innovative Vehicle Enhance- ment (PM E-DRIVE) Scheme, 2024

    Ministry of Heavy Industries, India. PM Electric Drive Revolution in Innovative Vehicle Enhance- ment (PM E-DRIVE) Scheme, 2024. Outlay Rs 10,900 crore; effective October 2024; succeeded EMPS 2024 and FAME-II

    work page 2024

  63. [63]

    Notification G.S.R

    Ministry of Road Transport and Highways, India. Notification G.S.R. 659(E): amendment to Rule 124 of the Central Motor Vehicles Rules – con- formity of production for traction batteries, 2022. Effective 1 October 2022; type approval under Rule 126, AIS-049 (Rev.1)

    work page 2022

  64. [64]

    Amendment to AIS-156 and AIS-038 (Rev.2): additional battery safety requirements (phased mandatory from 1 December 2022 and 31 March 2023), 2022

    Ministry of Road Transport and Highways, In- dia. Amendment to AIS-156 and AIS-038 (Rev.2): additional battery safety requirements (phased mandatory from 1 December 2022 and 31 March 2023), 2022. Notified September 2022

    work page 2022

  65. [65]

    Draft Battery Pack Aadhaar System guidelines (battery traceability), 2025

    Ministry of Road Transport and Highways, India. Draft Battery Pack Aadhaar System guidelines (battery traceability), 2025. Office memorandum 17 September 2025; under stakeholder consulta- tion

    work page 2025

  66. [66]

    Draft Notification G.S.R

    Ministry of Road Transport and Highways, In- dia. Draft Notification G.S.R. 184(E): ADAS stan- dards AIS-162/184/186/187/188 for M2, M3, N2, N3 vehicles, 2025. Dated 20 March 2025; phase- in reaffirmed for 2027–2028 per a February 2026 ministry reply

    work page 2025

  67. [67]

    Expert committee (with DRDO/CFEES, NSTL, IISc, ARCI, IIT-Madras) probe into 2022 EV fires; show-cause notices to makers, 2022

    Ministry of Road Transport and Highways, India (reported). Expert committee (with DRDO/CFEES, NSTL, IISc, ARCI, IIT-Madras) probe into 2022 EV fires; show-cause notices to makers, 2022. Accessed 2026-07-03

    work page 2022

  68. [68]

    Moran, Howard N

    Michael J. Moran, Howard N. Shapiro, Daisie D. Boettner, and Margaret B. Bailey.Fundamentals of Engineering Thermodynamics. John Wiley & Sons, 9th edition, 2018

    work page 2018

  69. [69]

    A review of battery electric vehicle safety issues and regu- latory responses.World Electric Vehicle Journal, 2025

    Muhammad Naiek, Ratchagaraja Aungsuthar, Gavin Harper, and Trisha Hendrickson. A review of battery electric vehicle safety issues and regu- latory responses.World Electric Vehicle Journal, 2025

    work page 2025

  70. [70]

    Automotive cybersecurity: A survey on frameworks, standards, and testing and monitoring technologies

    Franco Oberti, Ernesto Abrate, Alessandro Savino, Filippo Parisi, and Stefano Di Carlo. Automotive cybersecurity: A survey on frameworks, standards, and testing and monitoring technologies. InIEEE International Symposium on On-Line Testing and Robust System Design (IOLTS), 2024

    work page 2024

  71. [71]

    Annual Report FY25 (statutory auditor BSR & Co

    Ola Electric Mobility Ltd. Annual Report FY25 (statutory auditor BSR & Co. LLP: material weak- ness in physical-verification controls at a sub- sidiary), 2025. Rs 362 crore not physically verified. Accessed 2026-07-03

    work page 2025

  72. [72]

    Stock exchange filing on February 2025 registrations and registration- vendor renegotiation, 2025

    Ola Electric Mobility Ltd. Stock exchange filing on February 2025 registrations and registration- vendor renegotiation, 2025. 19 February 2025. Accessed 2026-07-03

    work page 2025

  73. [73]

    Outlook Business. Why Ola Electric’s February sales figure doesn’t match govt records.https: //www.outlookbusiness.com/start-up/news /why-ola-electrics-february-sales-figur e-doesnt-match-govt-records, 2025. Bookings breakdown; 31 March restatement letter. Accessed 2026-07-03

    work page 2025

  74. [74]

    Baumgartner

    Christian Pohlmann, Marlene Popowicz, Josef- Peter Schöggl, and Rupert J. Baumgartner. Infor- mation requirements for an electric-vehicle battery 13 digital product passport.Cleaner Production Let- ters, 2025

    work page 2025

  75. [75]

    RD-TableBench: A benchmark for com- plex table extraction.https://reducto.ai, 2024

    Reducto. RD-TableBench: A benchmark for com- plex table extraction.https://reducto.ai, 2024

    work page 2024

  76. [76]

    Reducto: agentic document parsing

    Reducto. Reducto: agentic document parsing. https://reducto.ai , 2024. Accessed 2026-07- 03

    work page 2024

  77. [77]

    Vanesa Ruiz, Andreas Pfrang, Akos Kriston, Noshin Omar, Peter Van den Bossche, and Lois Boon-Brett. A review of international abuse test- ing standards and regulations for lithium ion bat- teries in electric and hybrid electric vehicles.Re- newable and Sustainable Energy Reviews, 81:1427– 1452, 2018

    work page 2018

  78. [78]

    Modeling control objectives for business process compliance

    Shazia Sadiq, Guido Governatori, and Kioumars Namiri. Modeling control objectives for business process compliance. InBusiness Process Manage- ment (BPM 2007), LNCS 4714, pages 149–164. Springer, 2007

    work page 2007

  79. [79]

    A high-assurance secure software update manage- ment system design based on UN R156.IEEE Access, 2024

    Jaewoong Seo, Jin Kwak, and Sooyoung Kim. A high-assurance secure software update manage- ment system design based on UN R156.IEEE Access, 2024

    work page 2024

  80. [80]

    A blockchain-based traceability mechanism for au- tomotive parts across the supply chain

    Wei Shen, Yang Guo, Jun Liu, and Ke Xue. A blockchain-based traceability mechanism for au- tomotive parts across the supply chain. InIEEE Int. Conf. on Data Science and Information Tech- nology (DSIT), 2024

    work page 2024

Showing first 80 references.