Atlas project production

Hero K12 Roster Export

Exports BJHS student, faculty, and schedule data into Hero K12 so the platform stays aligned to current SIS roster state.

Internal-only entry. Do not publish externally without review.

Type: System
Lifecycle: Active
Last touched: 2026-03-24
Visibility: Internal

Purpose

Exports BJHS student, faculty, and schedule data into Hero K12 so the platform stays aligned to current SIS roster state.

Current state

The enabled `Hero` job is batch-disabled and diff-enabled, which strongly suggests a separately scheduled operational sync. It generates `faculty.csv`, `students.csv`, and `studentschedules.csv` from dedicated SQL files and uploads them through the secure transfer path. The student SQL appears scoped to BJHS (`STU.SC IN(73,733)`), which is an important business-scope detail not previously documented in the registry. Current registry state: Production / Active / Medium. Student behavior or campus-management roster integration. Trigger / frequency: recurring BJHS-focused sync [validate exact scheduler]..

Next step

confirm if any additional sites use Hero and document support boundaries. Yes - confirm site scope, business owner, and exception handling for schedule mismatches.

Interfaces

Inputs

Aeries SIS student, faculty, and schedule data for BJHS.

Outputs

Hero K12.

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Not in scope.

Operational Adoption

Not in scope.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

Aeries SIS student, faculty, and schedule data for BJHS. remain the authoritative upstream inputs for this workflow.
Hero K12. should be treated as downstream copies, recipients, or operational consumers rather than the authoring system.

Safe handling

Protect credentials, generated files, logs, and any transient export artifacts.
Treat student identifiers, rosters, and related records as FERPA-restricted data.
Limit staff identity, employment, or account data to approved administrators and business owners.

Operational notes

Reliability posture

Integr8r diff behavior and minimum-line checks are present, but formal alerting and owner handoff are not documented. Failure impact: stale Hero rosters or delayed campus-management readiness. Manual fallback: manual vendor imports or roster corrections..

Observability

Integr8r diff behavior and minimum-line checks are present, but formal alerting and owner handoff are not documented.
Failure impact: stale Hero rosters or delayed campus-management readiness..
Manual fallback: manual vendor imports or roster corrections..

Security and privacy

secure vendor transfer with host-managed credentials. Classification: restricted student operational data. FERPA-relevant roster and contact data.

Dependencies

Upstream

BJHS SIS data quality and vendor ingest reliability.

Downstream

Hero K12.

Ownership

Owners

Technology Services, Josh Barton / Technology Services

Users

Technology Services, BJHS administration or behavior-support stakeholders

Hero K12 Roster Export

Operational Notes

Method: Aeries SQL exports plus secure file upload with diff-mode guarding.
Implementation: Integr8r job key Hero in Config/Config.ps1, backed by Hero/SQL/.
Trigger / frequency: recurring BJHS-focused sync [validate exact scheduler].
Failure impact / fallback: stale Hero rosters or delayed campus-management readiness. Manual fallback: manual vendor imports or roster corrections..
Related references: README.md, Config/Config.ps1, Hero/SQL/BOUSD-Hero-students.sql, Hero/SQL/BOUSD-Hero-faculty.sql, Hero/SQL/BOUSD-Hero-studentschedules.sql.

Registry Alignment

Mapped registry entry: INT-062
Registry clarified: The enabled Hero job is batch-disabled and diff-enabled, which strongly suggests a separately scheduled operational sync.
Validation gaps: confirm if any additional sites use Hero and document support boundaries.