Session Flow

Requested Session:

1. A session is created via API call to the central system with an autoStart value of false or undefined. This may also be done via a mobile app or other remote system.
2. The session is in the INITIALIZED status. The central system will then exchange communication with the station to start a charge.
3. The station acknowledges the request to start a charge. The session status changes to CONFIRMED.
4. The station starts the charge. The session status changes to ACTIVE. If the station denies the request or does not start a charge within two minutes of the session being created, the session status changes to DENIED.
5. The active session collects meter readings at regular intervals.
6. The station stops the transaction. The session enters the PROCESSING stage.
7. The central system calculates the total cost of the session using the meter readings collected during the ACTIVE stage.
8. The session is marked for Manual Review if it fails any of the validations or checks. Otherwise, it enters the SANITY CHECK stage.
9. In the SANITY CHECK stage, the session is validated for validity of the various components, such as the total session cost and energy. If the session fails any of the sanity checks, it is flagged for Manual Review.
10. In the MANUAL REVIEW stage, the session is manually reviewed by a support specialist to determine the cause of the failure and to correct the session's cost and energy values. Once the session has been reviewed, it transitions to the COMPLETE stage.
11. The session reaches the COMPLETE stage once it has been successfully processed and has passed all the validations and checks. This phase indicates that the session is ready to be billed.

Auto Start Session:

1. A session is created via API call to the central system with an autoStart value of true. This is typically done by the station itself.
2. The session is initialized in the ACTIVE state.
3. The active session collects meter readings at regular intervals.
4. The station stops the transaction. The session enters the PROCESSING stage.
5. The central system calculates the total cost of the session using the meter readings collected during the ACTIVE stage.
6. The session is marked for Manual Review if it fails any of the validations or checks. Otherwise, it enters the SANITY CHECK stage.
7. In the SANITY CHECK stage, the session is validated for validity of the various components, such as the total session cost and energy. If the session fails any of the sanity checks, it is flagged for Manual Review.
8. In the MANUAL REVIEW stage, the session is manually reviewed by a support specialist to determine the cause of the failure and to correct the session's cost and energy values. Once the session has been reviewed, it transitions to the COMPLETE stage.
9. The session reaches the COMPLETE stage once it has been successfully processed and has passed all the validations and checks. This phase indicates that the session is ready to be billed.