IAM in Service Catalog
|Customers||Identify customers and their business needs: who needs the groups, when do they need them, for how long, and for what business reasons (email, sharing, access control, etc.).|
|Application Use||Identify what applications the customers needs to use with the groups.|
|Membership (Business Definition)||Define the desired group membership(s) – who's included and who isn't – in business terms and business rules used by the customer to describe the group membership(s).|
|Business Process||Identify the business process (e.g. student registration, course enrollment, employment, research administration) that masters data that matches the desired group membership(s).|
|System of Record||Identify the authoritative system of record where the institutional data is defined and mastered.|
|Business Domain||Identity the business domain(s) from UW Data Map.|
|Subject Area||Identify the subject area(s) from UW Data Map.|
|Type||Define the group type. Do the reference groups represent a simple group, a role, or a permission?|
|Home Group||Choose a home group that aligns with the UW Group Naming Plan and the business domain of the related institutional data.|
Define the group IDs and subgroup IDs that customers need to identify and reference. Some business processes master data that can be used for IDs.
Since the membership only includes Seattle branch, shouldn't the ID represent that it's not all first year students? e.g.
Define user-friendly display name values for contexts where groups are searched, listed, or selected by display name. Some business processes master data that can be used for display names.
Since the membership only includes Seattle branch, shouldn't the display name represent that it's not all first year students?
UW Seattle First Year Students 2016
UW First Year Students 2016
|Lifecycle Policy (Creation)|
Define when the groups will be created. Some reference groups are created or "pre-provisioned" automatically. Other reference groups are created only by customer request.
How long does this 2016 group need to exist?
|Lifecycle Policy (Deletion)|
Define when the groups will be deleted.
How long does this 2016 group need to exist?
Define the direct memberships of the groups and subgroups.
Since the membership only includes Seattle branch, shouldn't the membership definition represent that it's not all first year students?
UW Seattle students admitted for their first year for Summer or Autumn 2016: students enrolling in college directly after graduating from high school, regardless of the number of credits they are "transferring" to the UW (via AP, IB, Running Start, College in the High School, etc.)
Define how membership exceptions are managed, both additions and deletions.
|Membership (Grace Period)|
Define the grace period on membership, if needed.
|Membership (Opt-in)||Define the opt-in policy for the membership, if needed.|
|Membership (Opt-out)||Define the opt-out policy for the membership, if needed.|
Define the contact address.
Define descriptions that help potential customers understand fit for purpose and use, including lifecycle policy, membership policy, data quality standards, appropriate use guidelines, access control policy, ownership, and contact information. Some business processes master data that can be used for descriptions.
Since the membership only includes Seattle branch, shouldn't the description represent that it's not all first year students?
UW Seattle students admitted for their first year for Summer or Autumn 2016: students enrolling in college directly after graduating from high school, regardless of the number of credits they are "transferring" to the UW. This group is updated nightly from the Student Database. It is available for appropriate business purposes in support of programs designed for UW students. Access to the membership is controlled because it contains a limited amount of student information that falls under the protections of FERPA. See http://www.washington.edu/students/reg/ferpafac.html for more information about use of FERPA-protected information. Please contact firstname.lastname@example.org for questions about using this group.
|More Information||Define where additional information for customers will be located.|
|Application Settings (Exchange)|
Define the status and settings for use in UW Exchange.
|Application Settings (Google)|
Define the status and settings for use in UW Google Apps.
|Data Custodian||Identify the responsible data custodian(s).|
Determine the appropriate UW data classification (Public, Restricted, Confidential).
|Access Control Policy||Decide and document the access control policy including membership viewer control, sender control, appropriate use guidelines, terms and conditions of use, etc.|
|Membership Viewer Control||Define the membership viewer control, including exceptions to the access control policy.|
|Sender Control||Defined the sender control, including exceptions to the access control policy.|
Identify the service that will be used as the data source for provisioning. It may or may not be the same as the system of record.
Master: Student Database (SDB)
Define the technical definition of the memberships in terms used by the data source and its data elements, as well as any additional filtering.
SELECT DISTINCT sr_adm_appl.system_key, sr_adm_appl.appl_qtr,
|Provisioning||Define a provisioning model for data integration and reconciliation that ensures the groups are created in accordance with their lifecycle policy and managed in accordance with their data quality standards.|
|De-Provisioning||Define a de-provisioning model that ensures the groups are deleted in accordance with their lifecycle policy.|
|Monitoring||Define a monitoring solution that helps identify incidents and problems, particularly those that impact availability and reliability.|
|Data Quality Standards|
Define data quality standards under normal operations, including data validation rules, timeliness of updates, defined error rates, integrity monitoring, and reliability. The standards will depend on the business process, system of record, data source, provisioning and de-provisioning models, monitoring, and operations.
|Internal Documentation||Define what internal documentation will be developed and where it will be maintained.|
|Customer Documentation||Define what customer documentation will be developed and where it will be maintained.|
|Communication Plan||Define the communication plan to inform audiences about the new reference groups.|
|Request Fulfillment||Define how requests will be fulfilled. For example, standard requests for information, access to memberships, membership exceptions, email settings, design changes, etc.|
|Incident Management||Define how incidents will be handled.|