Atlas project production

ASB Works Student Export

Sends current 9-12 student data into ASB Works so student activity or account records stay aligned without manual nightly imports.

Internal-only entry. Do not publish externally without review.
Type
System
Lifecycle
Active
Last touched
2026-03-24
Visibility
Internal

Purpose

Sends current 9-12 student data into ASB Works so student activity or account records stay aligned without manual nightly imports.

Current state

The enabled `ASBWorks` Integr8r job explicitly describes itself as a nightly upload of grades 9-12 Aeries student data. It generates `students.csv` from `BOUSD-ASBWorks-Students.sql` against `DB_Aeries_25` and uploads the result through the runner's secure transfer path. This is strong evidence of a live production export rather than only an inventory-listed connector. Current registry state: Production / Active / Medium. Student activities integration, finance-adjacent data export. Trigger / frequency: likely nightly batch on the Windows Integr8r host..

Next step

confirm exact ASB Works business owner and school-year cadence. Yes - confirm the specific ASB Works modules consuming the nightly file and the current business owner.

Interfaces

Inputs
  • Aeries SIS student data for grades 9-12.
Outputs
  • ASB Works.

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 data for grades 9-12. remain the authoritative upstream inputs for this workflow.
  • ASB Works. 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.

Operational notes

Reliability posture

Integr8r report details and file minimum-line checks provide runtime evidence, but formal alerting is not documented. Failure impact: stale student records in ASB Works and more manual reconciliation. Manual fallback: manual export and upload..

Observability

  • Integr8r report details and file minimum-line checks provide runtime evidence, but formal alerting is not documented.
  • Failure impact: stale student records in ASB Works and more manual reconciliation..
  • Manual fallback: manual export and upload..

Security and privacy

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

Dependencies

Upstream
  • Aeries data quality and vendor import expectations.
Downstream
  • ASB Works.

Ownership

Owners

Technology Services, Josh Barton / Technology Services

Users

Technology Services, ASB or student-activities stakeholders

ASB Works Student Export

Operational Notes

  • Method: Aeries SQL extract plus secure file upload.
  • Implementation: Integr8r job key ASBWorks in Config/Config.ps1, backed by ASBWorks/SQL/BOUSD-ASBWorks-Students.sql.
  • Trigger / frequency: likely nightly batch on the Windows Integr8r host.
  • Failure impact / fallback: stale student records in ASB Works and more manual reconciliation. Manual fallback: manual export and upload..
  • Related references: README.md, Config/Config.ps1, ASBWorks/SQL/BOUSD-ASBWorks-Students.sql.

Registry Alignment

  • Mapped registry entry: INT-059
  • Registry clarified: The enabled ASBWorks Integr8r job explicitly describes itself as a nightly upload of grades 9-12 Aeries student data.
  • Validation gaps: confirm exact ASB Works business owner and school-year cadence.