A conceptual process to identify data commonalities across agencies (using the DRM) helps illustrate the context in which agencies use the DRM. The process uses an agency’s EA in combination with the DRM’s common approach to the categorization, exchange, and structure of data to share information. This section offers a potential collaboration process and the results of a pilot conducted by the Department of the Interior (DOI) to demonstrate how the DRM might be used. (2IX6)
Collaboration Opportunities (2IX7)
Collaboration opportunities can be identified through the DRM’s approach to the categorization, exchange, and structure of data. The process illustrated in Exhibit G lays out (at a conceptual level) the steps an agency might go through in its use of the DRM. (2IX8)
Exhibit G: DRM Collaboration Process (2IX9)
In this scenario: (2IXA)
1. Organization B determines that it has the need for a particular set of data that might be available from Organization A. (2IXB)
2. Organization A uses the DRM to categorize its data (using the BRM) into a business context. (2IXC)
3. Organization B identifies Organization A’s available data through its business context. (2IXD)
4. Organization A uses the DRM to publish the detailed structure of the actual data element (in support of the business context). (2IXE)
5. Organizations A and B determine if, in fact, the data produced by Organization A will meet the needs of Organization B. (2IXF)
6. Once Organizations A and B determine that the data can be re-used, the information exchange package is used to transmit the data. (2IXG)
Although the process illustrated in Exhibit G is simplistic in nature (and it will likely require a level of detail on the part of the organizations seeking to share data), it does provide a conceptual view to the steps an organization might take in order to use the DRM. (2IXH)
Department of the Interior (DOI) Pilot (2IXI)
The pilot conducted by DOI in Exhibit H provides a perspective on how the DRM might be used to improve the ability to share information and efficiently use IT investments. DOI’s pilot uses the DRM to share information regarding its recreational amenities in a common approach that can be easily interpreted and employed by many users. Users who wish to take advantage of DOI recreational information need only understand the DRM to understand and use DOI data properly. Exhibit H illustrates the DOI pilot and the use of the DRM’s common approach to the categorization, exchange, and structure of data. This diagram also describes the use of actual data models (schemas). These schemas represent a potential view of the implementation of an information exchange package. Future volumes of the DRM will define in more detail the relationship of schemas to the information exchange package. (2IXJ)
Exhibit H: Use of the DRM (2IXK)
The DOI pilot demonstrates the potential outcomes provided by the DRM. The pilot’s use of the DRM is described in the following sections. (2IXL)
Categorization of Data (2IXM)
DOI used the DRM to categorize data through the identification of activities performed within the recreational resource management and tourism sub-functions of the BRM. With the BRM categorization identified, DOI further identified a super type of “recreation area.” This super type is a more detailed categorization of the type of data consumed/produced through this business function. (2IXN)
Exchange of Data (2IXO)
Defining data in common terms related to the request of a public amenity enables it to be shared with other users. By using the DRM’s approach to the exchange of data, DOI identified a set of information (information exchange package) that directly supports the request for a recreational amenity. DOI used the DRM’s categorization approach to relate the information exchange package to a particular business context, and then made it available as a re-usable set of data. (2IXP)
Structure of Data (2IXQ)
After using the categorization approach to identify the subject area and super type, DOI used the DRM’s common approach to identify the data elements. The data element includes the data object (names of the recreational areas), data property (the types of recreation activities aligned with specific recreational areas), and data representation (specific value of the data element). (2IXR)
Potential Outcomes of the DOI Pilot (2IXS)
Information Sharing (2IXT)
Information sharing related to recreation areas is facilitated because users understand the categorization, exchange, and structure of the data needed to satisfy their business needs. In the pilot, DOI creates information about its recreation areas and the many activities available within them. An agency that wants to make a recreation amenity request would, for example, look in the BRM for a sub-function that describes the activity it is seeking (recreational management and tourism). Once the agency knows the subfunction, it can use the Federal Enterprise Architecture Management System (FEAMS) to identify investments currently supported by DOI that provide recreational-amenity management capabilities. With the investments identified, the agency can work with DOI to determine whether the functions and data supported by the investment meet its needs. Once this is confirmed, the information exchange package would be used to actually transmit the request from the agency’s systems to the DOI systems that manage recreational amenities. Once the DOI data is made available to multiple users, it increases the department’s ability share information. (2IXU)
Improved Effectiveness of IT Investments (2IXV)
The DOI pilot illustrates how an agency might improve the effectiveness of its IT investments by making the data produced by its investments available to others. The DRM’s common approach to data categorization, exchange, and structure provides a mechanism whereby an agency does not need to create a new investment when the data it requires is available from another source. Agencies engaged in the DOI pilot now have a common way to describe the business purpose of the data required by their uses and agencies participating in the DOI pilot can re-use the various existing IT investments to meet its business needs. (2IXW)
================================================================================================== (2JU0)
Comments (2JU1)
- Ref: http://colab.cim3.net/cgi-bin/wiki.pl?DataReferenceModel_09_2004/UseOfThe_DRM_VolIv1#nid2IX7 (2JVJ)
- Comment: It is not clear how the DRM will link with or tie into any current data sharing initiatives that are ongoing in the Federal government (i.e. promulgated or supported by OMB's current Interagency Council on Statistical Policy). (agency comment / compiled 2004.12.06) (2JVL)
- Ref: http://colab.cim3.net/cgi-bin/wiki.pl?DataReferenceModel_09_2004/UseOfThe_DRM_VolIv1#nid2IXN (2JXY)
- Suggest changing from: In the last sentence of the this paragraph: This super type is a more detailed categorization of the type of data consumed/produced through this business function. (2JXZ)
- Changing it to read: This super type is a more detailed categorization of the type of data consumed/produced through these business sub-functions. (agency comment / compiled 2004.12.06) (2JY0)
- Ref: http://colab.cim3.net/cgi-bin/wiki.pl?DataReferenceModel_09_2004/UseOfThe_DRM_VolIv1#nid2IXW (2JY1)
- Comment: Last sentence of this paragraph appears to mean "Agencies engaged in the DOI pilot now have a common way to describe the business purpose of the data required by their users and agencies participating in the DOI pilot can re-use the various existing IT investments to meet its business needs." and not their uses as it currently reads. (agency comment / compiled 2004.12.06) (2JY3)
- Ref: http://colab.cim3.net/cgi-bin/wiki.pl?DataReferenceModel_09_2004/UseOfThe_DRM_VolIv1#nid2IXU (2K0H)
- Comment: The Federal Enterprise Architecture Management System (FEAMS), mentioned in this paragraph, is used in the DOI Pilot to identify investments that DOI supports. We would like to see more. (2K0I)
- Suggested Action: The agencies require additional direction on how to implement the FEAMS database to identify performance of data involved in exchange information. Further, if the DOI example is meant to represent a “best of breed,” we suggest that relevant DOI documents be included in the appendix of Volume I. (agency comment / compiled 2004.12.06) (2K0J)
- Ref: http://colab.cim3.net/cgi-bin/wiki.pl?DataReferenceModel_09_2004/UseOfThe_DRM_VolIv1#nid2IXU (2K4S)
- Comment: The first sentence of this paragraph states that “Information sharing related to recreation areas is facilitated because users understand the categorization, exchange, and structure of the data needed to satisfy their business needs.” We believe that the categorization of data along LoB A’s functional hierarchy will not facilitate the identification by, and therefore sharing of, information with LoB B. Indeed, it may hinder this sharing, precisely because LoB B will first be required to understand the functional navigation path, or business, of LoB A, in order to identify LoB A’s data. It would seem more appropriate to describe LoB A’s data independent of function so that LoB B could discover the data directly. (agency comment / compiled 2004.12.06) (2K4T)
- Ref: http://colab.cim3.net/cgi-bin/wiki.pl?DataReferenceModel_09_2004/UseOfThe_DRM_VolIv1#nid2IXU (2K4U)
- Comment: The second sentence of this paragraph states that “In the pilot, DOI creates information about its recreation areas and the many activities available within them. An agency that wants to make a recreation amenity request would, for example, look in the BRM for a sub-function that describes the activity it is seeking (recreational management and tourism). Once the agency knows the subfunction, it can use the Federal Enterprise Architecture Management System (FEAMS) to identify investments currently supported by DOI that provide recreational-amenity management capabilities.” This paragraph appears to describe a way for organizations to share the functions/processes of other agencies. In the above example, an agency “wants to make a recreation amenity request”. The agency then searches for this “subfunction” within the BRM that “provide recreational-amenity management capabilities”. Therefore, this is the sharing of a process, not the sharing of decoupled data. Also of note, only the BRM is used here, and the DRM is not even mentioned. (agency comment / compiled 2004.12.06) (2K4V)
- Ref: http://colab.cim3.net/cgi-bin/wiki.pl?DataReferenceModel_09_2004/UseOfThe_DRM_VolIv1#nid2IX6 (2K1A)
- Comment: The document does not address how Discovery might be accomplished within the DRM framework. (agency comment / compiled 2004.12.06) (2K1B)
- Ref: http://colab.cim3.net/cgi-bin/wiki.pl?DataReferenceModel_09_2004/UseOfThe_DRM_VolIv1#nid2IXQ (2K4W)
- Comment: Defining data – A functionally oriented approach to defining data might lead to the creation of a data object called “Aircraft Owner”. In contrast, if this object were defined independent of the function of registering aircraft owners and their planes (or other related functions such as aviation medicine), the object would simply be “Person” or “Party” and it would have many subtypes (possibly including Aircraft Owner). (2K4X)
- Another example: Aircraft Operations Services and Surveillance Operations Services might be named in a functional classification. If these were defined independent of function, they would simply be “Service” or “Function” and they would be related to an organization and possibly other kinds of entities. (2K4Y)
- Another example: A functional orientation might lead to identifying and defining the following data objects: landing gear, fuselage, engine, components, etc. In contrast, if these were defined from a data standpoint, they would likely be named and defined as Aircraft Component or Aircraft Component Type, or more generally as Asset Component and Asset Component Type. (2K4Z)
- A functional orientation might lead to an object called “Assigned Aircraft” whereas a data oriented approach would view this as a relationship between two entities or objects: “Aircraft” and “Flight” (since it was defined as data about an aircraft assigned to a flight). (agency comment / compiled 2004.12.06) (2K50)
- Comment: Defining data – A functionally oriented approach to defining data might lead to the creation of a data object called “Aircraft Owner”. In contrast, if this object were defined independent of the function of registering aircraft owners and their planes (or other related functions such as aviation medicine), the object would simply be “Person” or “Party” and it would have many subtypes (possibly including Aircraft Owner). (2K4X)
- Ref: http://colab.cim3.net/cgi-bin/wiki.pl?DataReferenceModel_09_2004/UseOfThe_DRM_VolIv1#nid2IXR (2KGV)
- Comment: This paragraph confuses Object with its name. Also the phrase "data representation (specific value of the data element)" should be "data representation (specific value of the data property, such as the activity type)." the “Structure of Data” paragraph confuses Object with its name. Also the phrase “data representation (specific value of the data element)” should be “data representation (specific value of the data property, such as the activity type).” (2KGW)