Virginia Tech® home

IAM Architectural Group

IAM Architectural Group

The IAM Architectural Group will be an architecture and standards board for defining, reviewing, and approving IAM architecture at Virginia Tech.

Membership of the architectural group will consist of key representation of significant aspects of IAM functions and technical areas involved in IAM architecture and IT units that operate IAM services. Membership of the group shall be between 4-10 members.

Structure of the Group:

  • Chair: Identity Architect - Kevin Rooney
  • Members:
    • Executive Director SIS - Ryan McDaniel
    • Director of Middleware - Daniel Fisher
    • Test Engineering Manager - Brian Long
    • Middleware Technical Lead - Marvin Addison
    • Middleware Technical Lead - Dave Hawes
    • Middleware SME - Micheal Hosig
    • CCS Representative - TBD
    • Distributed IT Rep - TBD
    • Distributed IT Rep - TBD

 

Responsibilities:

  • Define, document, and maintain IAM Architectural Standards
    • Review and approve proposed changes to IAM Architectural Standards
    • Contribute to current and future-state architectural design artifacts
    • Consistency between sub-architectures
    • Identifying reusable components
  • Enforcement of Architecture Compliance:
    • Review and Approval of IAM architecture for projects and major initiatives.
  • Contributing to enterprise architecture
    • Flexibility of enterprise architecture:
      • To meet changing business needs
      • To leverage new technologies
    • Improving the maturity level of architecture discipline within the organization
    • Ensuring that the discipline of architecture-based development is adopted
    • Providing the basis for all decision-making with regard to changes to the architectures
    • Supporting a visible escalation capability for out-of-bounds decisions

       

Decisions:

  • Architectural changes to either IAM architectural standards or actual implementations will be reviewed and a decision made. Possible decisions include approval, approval of a variance with conditions, request for a change to the proposed architecture, or denial.

     

Artifacts (Maintained by the Identity Architect):

  • VT IAM Standards Document
  • Meeting Notes with a record of decisions made.
  • Current State and Future State architecture design diagrams

     

Proposal Components:

  • Proposed Change to Standards
    • Requestor
    • Proposed Change
    • Reason and rationale for the change
  • Project Proposal
    • Requestor
    • Systems in Scope
    • Change implementation team info
    • Description of architecture or description of architectural change.
    • Architectural Diagrams:
      • Data Structure
      • Infrastructure
      • Integrations