Context (Level 0) Data Flow — AET

External actors

• Student

• Teacher

• Region/State staff (explicit “Region Log In” exists in CTE platform)

• FFA.org (AET credentials can be used to access FFA.org if profile has FFA ID)

AET system surfaces

• AET Web (theaet.com / www.theaet.com)

• AET Mobile Web (m.theaet.com)

• AET Authentication (auth.theaet.com)

• AET for CTE (cte.theaet.com)

Core data (logical)

• Identity/Profile (incl. linked accounts by email on mobile login; may include FFA ID)

• Program/Roster & Permissions (teacher/state roles implied by separate login paths)

• Record Book / WBL records (experiences/time/skills/etc.)

• Reporting outputs (dynamic reporting emphasized for CTE)

Level 1 Data Flow — Main Processes

1) Authenticate & establish session

• Student/Teacher visits AET Web or AET Mobile Web → submits credentials → AET Authentication validates → session established.

• Separate login fields exist for students (School ID + username) vs teachers (email) on the auth surface.

2) Capture record book / WBL activity

• Student enters activities via Web/Mobile → stored as record-book/WBL entries → later used for review and reporting.

3) Teacher oversight & program management

• Teacher reads student records, monitors progress, and pulls program-level views/reports (core AET purpose: “record book system for tracking experiences”).

4) CTE platform reporting & regional oversight

• Users access cte.theaet.com → track WBL time/skills in a flexible framework + “dynamic reporting” → produce documentation for stakeholders; includes Region Log In for area-level reporting/assistance.

5) Optional federation/connection to FFA.org

• AET indicates FFA.org access using AET credentials depends on having an FFA ID in the AET profile; FFA help docs describe logging into FFA.org via “The AET” option.