Enterprise Data Platform

Appearance

Source Systems ​

The Source Systems area documents the systems EDP can collect from, the connector options available for each system, and the status of any prebuilt connector packages.

This section should help answer:

  • What systems are candidates for integration?
  • Who owns each source system?
  • What data can be collected?
  • What access, credentials, scopes, or service accounts are required?
  • Which connector options are available?
  • Is there a prebuilt connector or model package?
  • What raw, ODS, Data Vault, and Data Mart outputs does the integration support?
  • What operational risks, limits, or approval requirements apply?

Pages ​

  • AD: first documented source system for identities, groups, computers, organizational units, and memberships.
  • M365: cloud productivity, collaboration, licensing, usage, and service metadata source.
  • Google Workspace: cloud identity, collaboration, licensing, device, usage, audit, and administrative alert source.
  • Infinite Campus: SIS roster, student, enrollment, course, section, assignment, and academic context source.
  • Canvas LMS: learning management, course, enrollment, assignment, submission, grade, and activity source.
  • Follett Destiny: library, textbook, instructional material, resource, patron, checkout, fine, and fee source.
  • Apple Business Manager and Apple School Manager: Apple device enrollment, Managed Apple Accounts, Apps and Books, and education roster source.
  • KnowBe4: security awareness training, phishing simulation, user risk, and compliance evidence source.
  • Cisco Meraki Dashboard: cloud-managed network inventory, configuration, telemetry, licensing, client activity, and alert source.
  • ManageEngine ServiceDesk Plus: ITSM, service desk, ticket, asset, CMDB, SLA, and workflow source.
  • ManageEngine Endpoint Central: endpoint inventory, patch, software, configuration, compliance, and deployment source.
  • Common Systems: additional source-system categories and prioritization guidance.
  • Inventory: source system inventory and documentation template.
  • Connector Catalog: catalog of connector options, prebuilt packages, and implementation status.
  • Connector Standard: expectations for building repeatable, supportable connectors.

Documentation Principles ​

Every source system should have a clear owner, access model, integration pattern, sensitivity classification, expected refresh cadence, and support path.

Every connector should separate code, configuration, and secrets. A prebuilt connector should be deployable into a target environment by supplying credentials, endpoints, and environment-specific configuration rather than rewriting connector logic.