================================================================================================== (2JUU)
Comments (2JUV)
- Ref: Exhibit G: DRM Collaboration Process above (2JUW)
- Comment: The Collaboration Opportunities example in Exhibit G is not clear -The directional arrow in view 3 of Exhibit 6 appears to be going to the wrong way. It appears that Organization B is sending data to Organization A when the objective is to transfer data from Organization A to Organization B. (agency comment / compiled 2004.12.06) (2JUX)
- Ref: Exhibit G: DRM Collaboration Process above (2KGO)
- Comment: This exhibit should be improved by using more concrete examples of collaboration. (agency comment / compiled 2004.12.06) (2KGP)
- Ref: Exhibit G: DRM Collaboration Process above (2KH2)
- Comment: Cross-LoB data standards not addressed. DRM-I appears to ignore the critical issue of how many common data elements actually cross business domains. Other than ISO 11179, the document does not promote developing standards for concepts such as Address, Name, much less for higher level aggregate constructs such as Federal Employee, Financial Account, etc that most LoBs will have to deal with and that are part of most real world information exchanges. If such cross-LoB standardization is not addressed, it is probable that each LoB will develop its own definition of these aggregate data classes, which will result in costly incompatibilities. The DOI example of a data exchange mentions only recreation-unique data elements and is therefore very misleading. If the example included a financial account to be paid, and a federal employee to be contacted, the cross-LoB harmonization issue could be properly illustrated. For example, OPM could set standards for federal employee, or the Financial LoB could inform Acquisition, HR, and everybody else who needs to include financial data in their systems/ data exchanges what the name/ semantics/ syntax for financial transactions should be. Perhaps these ideas should be worked into Exhibit G DRM Collaboration Process. (agency comment / compiled 2004.12.06) (2KH3)