Guidelines for iData Definitions for FY18 OMB Performance Metrics
This template outlines the essential elements and purpose of an OMB iData definition. Each definition must provide:
 Transparency: The ability for anyone in the UA community—especially the Strategy, Planning and Budget office—
to easily and quickly understand the metric from an operational and technical perspective.
 Replicability: The ability for UA personnel to independently replicate the university’s metric, and to use the provided
code/methodology to drill down quickly to respond to external and internal information requests, on demand.
Questions? Please contact Arthur Hussey at 907-450-8193 or [email protected].
Example definition:
Notes on requirements & best practices for iData entries for OMB metrics:
Name: Summarize the functional definition into a few highly relevant words.
Functional definition: Write it so it is understood by layperson; precise and concise; gives a time when data is
available/calculated; tell what the data means and indicate why we use/need the data.
Source of definition: Choose from UA System for system wide definitions; UAA, UAF, UAS for university-specific
definitions.
Technical definition: Required if metric uses RPTP.DSDMGR, data from other RPTP schemas, or otherwise requires
calculations that are not fully described in functional definition. Describe how to locate, calculate and display data; document
calculation methods; note which parameters must be included; and when to run the calculation.
Data system: Indicate if the data is sourced from the RPTP.DSDMGR or other RPTP schemas. If external sources are used,
provide URL and date pulled. Files/screenshots, etc., can be attached to the definition if needed.
Time context: Note what time period the definition concerns, and describe: FY, Academic Year, Financial Aid Year, fixed
date/time, as of current day/time. UA Institutional Research, Planning & Analysis
N-154
May 2016