SAE J2293 establishes requirements for Electric Vehicles (EV) and the off-board Electric Vehicle Supply Equipment (EVSE) used to transfer electric energy to an EV from an electric utility power system (utility) in North America. This document defines, either directly or by reference, all characteristics of the total EV energy transfer system (EV-ETS) necessary to insure the functional interoperability of an EV and EVSE of the same physical system architecture. The ETS, regardless of architecture, is responsible for the conversion of AC electrical energy into DC electrical energy that can be used to change the storage battery of an EV, as shown.
The different physical ETS system architectures are identified by the form of the energy that is transferred between the EV and the EVSE, as shown. It is possible for an EV and EVSE to support more than one architecture.
This document does not contain all requirements related to EV energy transfer, as there are many aspects of an EV and EVSE that do not affect their interoperability. Specifically, this document does not deal with the characteristics of the interface between the EVSE and the utility, except to acknowledge the utility as the source of energy to be transferred to the EV.
The functional requirements for the ETS are described using a functional decomposition method. This is where requirements are successively broken down into simpler requirements and the relationships between requirements are captured in a graphic form. The requirements are written as the transformation of inputs into outputs, resulting in a model of the total system.
Each lowest level requirement is then allocated to one of four functional groups (FG) shown. These groups illustrate the variations of the three different system architectures, as the functions they represent will be accomplished either on an EV or within the EVSE, depending on the architecture. Physical requirements for the channels used to transfer the power and communicate information between the EV and the EVSE are then defined as a function of architecture.
The requirements model in Section 6 is not intended to dictate a specific design or physical implementation, but rather to provide a functional description of the system's expected operational results. These results can be compared against the operation of any specific design. Validation against this document is only appropriate at the physical boundary between the EVSE and EV