MétaCan
Menu
Back to cohort
Record W2043365683 · doi:10.4271/2011-01-0866

Communication Requirements for Plug-In Electric Vehicles

2011· article· en· W2043365683 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueSAE technical papers on CD-ROM/SAE technical paper series · 2011
Typearticle
Languageen
FieldComputer Science
TopicReal-Time Systems Scheduling
Canadian institutionsChrysler (Canada)
Fundersnot available
KeywordsPlug-inComputer sciencePlug and playSpark plugAutomotive engineeringEngineeringAerospace engineeringOperating system

Abstract

fetched live from OpenAlex

<div class="section abstract"><div class="htmlview paragraph">This paper is the second in the series of documents designed to record the progress of a series of SAE documents - SAE J2836™, J2847, J2931, & J2953 - within the Plug-In Electric Vehicle (PEV) Communication Task Force. This follows the initial paper number 2010-01-0837, and continues with the test and modeling of the various PLC types for utility programs described in J2836/1™ & J2847/1. This also extends the communication to an off-board charger, described in J2836/2™ & J2847/2 and includes reverse energy flow described in J2836/3™ and J2847/3.</div><div class="htmlview paragraph">The initial versions of J2836/1™ and J2847/1 were published early 2010. J2847/1 has now been re-opened to include updates from comments from the National Institute of Standards Technology (NIST) Smart Grid Interoperability Panel (SGIP), Smart Grid Architectural Committee (SGAC) and Cyber Security Working Group committee (SCWG). These documents have been added to the NIST SGIP Catalogue of Standards and it is expected the others to be added upon publishing. Additional efforts have continued with the Smart Energy Alliance (SEP2) as we coordinate the Application Specification with this SAE document for PEV utility messages.</div><div class="htmlview paragraph">J2836/2™ and J2847/2 are intended to be published early 2011 and include the requirements for DC energy transfer to the PEV where the PEV communicates with the Electric Vehicle Supply Equipment (EVSE) that includes an off-board charger.</div><div class="htmlview paragraph">J2836/3™ and J2847/3 include the architecture and messages for reverse energy flow including the following four types that include specific architecture and communication requirements: Vehicle to Grid (V2G), Vehicle to Home (V2H), Vehicle to Load (V2L) and Vehicle to Vehicle (V2V). These also include options for either on-board or off-board energy conversion.</div><div class="htmlview paragraph">Two new sets of J documents have been added to the task force effort. J2931 includes the communication requirements and protocol variations, while J2953 captures the communication interoperability requirements. J2931 has four parts. J2931/1, J2931/2, J2931/3 & J2931/4 have been added to the suite of documents to capture the communication protocol, test criteria and other items that tie to the J2847 series of messages. J2953 has started to identify the interoperability requirements and approach for the multitude of PEV and EVSE manufacturers to insure communication interoperability.</div><div class="htmlview paragraph">The objective of these documents is to publish initial versions that allow the task force to move into the implementation phase that will continue with simulation, test and evaluation of the systems and then re-publish with updates. This provides a two-step approach to providing initial information and making it more complete as our progress continues. Initial publication also allows other groups and organizations to provide comments that will be addressed in the updated version as shown with J2847/1 noted above.</div></div>

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.970
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.002
Science and technology studies0.0000.000
Scholarly communication0.0000.002
Open science0.0040.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.036
GPT teacher head0.274
Teacher spread0.239 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it