TRM Evaluation Activities Cycle 1- Feb 2006

1. TRM Evaluation ActivitiesCycle 1- Feb 2006 IAC support to the AIC Reference Model Maintenance Process

2. Summary Chart • PDF/PDFA = Approve (Later cycle should Investigate with More Thorough Analysis of Content Management, e.g., other formats such as TIFF, use cases, relationship to Records Mgmt Profile) • - X3D Graphics = Approve • - Satellite Network Communications = Investigate with More Thorough Analysis • - Eliminate Platform Dependent/Independent in Service Platform and Component Framework = Approve • - Reorganize data related items into a Data Management Area = Investigate with More Thorough Analysis • Additional SOA/XML/Web Services Standards need to be added= Investigate with More Thorough Analysis

3. Review of Point Solutions to New Categories • Quick Review of Point Solutions- Minimal Impact • Two Items: • PDF & PDF/A • X3D Graphics • Detailed Evaluation of new categories: Satellite Network Communications and consider broader review for Content Management • Categories: • Service Access and Delivery • Service Platform and Infrastructure • Component Framework • Service Interface and Integration • Recommendations: Approve, Approve with modifications, Disapprove, Investigate with more thorough analysis. Request clarification and refinement.

4. TRM Evaluation Check List 1. Is the proposed change something that the government or industry has already built a community around? Does it have a respective governing body or working group (e.g., OASIS, Federal Community of Practice, ET.gov) 2. What is the industry status of this proposed technology (e.g. emerging, mature, and legacy)? 3. Is the proposed change proprietary to a single vendor? 4. What benefits will the government receive by adopting the proposed change (e.g. Will it serve to increase information sharing capabilities)? 5. What is the degree of impact that the proposed technology will have (e.g. government-wide, LOB initiative, your organization)? 6. Do multiple vendors supply products that embed/enable this proposed technology component? 7. Does this change align to one or more approved or planned investment requests? If so, identify the investments and whether they are E-Gov, cross-agency, or intra- agency? Evaluation will go through initial review of not more than 5 days followed by more detailed review. Interactions with government Point of contact is vital to the process.

5. Focus? • What are the relationship to other models? Lines of business? • 3D for Graphics • Content and Record Management • Add PDF and PDFa • Also consider TIFF and other standards • How does this fit with the Record Management profile and what is being done within Industry?

6. PDF & PDF/A TRM Evaluation Check List 1. Is the proposed change something that the government or industry has already built a community around? Does it have a respective governing body or working group (e.g., OASIS, Federal Community of Practice, ET.gov) • PDF is an open format that has been adopted by the Enterprise Content Management consortium. The ECM Association is AIIM: http://www.aiim.org/ There are multiple versions PDF 1.4 is the most common along with PDF/A, PDF/X & PDF/E It is represented within ISO as 140005.1 & ISO 15489 Information and Documentation Record Management. 2. What is the industry status of this proposed technology (e.g. emerging, mature, and legacy)? It can work on multiple platforms Microsoft, Unix, Macintosh. 3. Is the proposed change proprietary to a single vendor? It started out with Adobe but has been presented to open standards groups. A large number of vendors (1800+) offer PDF-based solutions including tools to create, plug-in, training support and a variety of other support tools. 4. What benefits will the government receive by adopting the proposed change (e.g. Will it serve to increase information sharing capabilities)? The PDF can be used to deliver documents and forms on portals and web sites. The PDF/A can be a primary method of archiving information. It is device independent. It can be reliably and consistently be rendered without regard to the hardware and software platform. It is self-contained, meaning it contains all the necessary information for rendering. It is self-documenting- meaning it contains its own description. Provides transparency. The biggest weakness is the technical protection where there is no encryption and passwords.

7. PDF & PDF/A TRM Evaluation Check List 5. What is the degree of impact that the proposed technology will have (e.g. government-wide, LOB initiative, your organization)? PDF can fit in the front end with the citizens interface and for the backend for archiving but the portals and enterprise content management tend to have their own proprietary formats. PDF can also be a content exchange mechanism. 6. Do multiple vendors supply products that embed/enable this proposed technology component? A large number of vendors support PDF format but the exact formats and capabilities often differ. 7. Does this change align to one or more approved or planned investment requests? If so, identify the investments and whether they are E-Gov, cross-agency, or intra- agency? The situation and type of use of PDF needs to be clarified. Usage cases are needed within the TRM document to clarify their usage. It is recommended that PDF 1.4 and PDF/A be included in the TRM and that a series of content management use cases be developed for future update and relate to and end to end content management scenario. .

8. X3D Graphics: TRM Evaluation Check List 1. Is the proposed change something that the government or industry has already built a community around? Does it have a respective governing body or working group (e.g., OASIS, Federal Community of Practice, ET.gov) X3D Graphics it the next generation beyond VRML it is used for Medical, CAD, Simulation, Geospatial and many high end applications within the government. The Web3D Consortium has worked on the standard for a number of years culminating with the X3D ISO/IEC 19775 standard in Oct 2004. 2. What is the industry status of this proposed technology (e.g. emerging, mature, and legacy)? In the high end graphics market it is the standard. It can be used on a range of Unix, Microsoft, Macintosh platforms and is built into the high end scientific equipment. 54 application packages use it. 3. Is the proposed change proprietary to a single vendor? It was developed by a consortium and then presented to the international standards organization. 4. What benefits will the government receive by adopting the proposed change (e.g. Will it serve to increase information sharing capabilities)? This should clarify the graphical interfaces within specifications.

9. X3D Graphics: TRM Evaluation Check List 5. What is the degree of impact that the proposed technology will have (e.g. government-wide, LOB initiative, your organization)? There are many scientific, engineering, and medical applications where this is a common element. 6. Do multiple vendors supply products that embed/enable this proposed technology component? 54 have been identified but it is expected that many more will exist. 7. Does this change align to one or more approved or planned investment requests? If so, identify the investments and whether they are E-Gov, cross-agency, or intra- agency? The market where this standard is involved has not been addressed within the e-gov solutions but it is likely that the Federal Health Architecture and selected scientific communities can benefit by sharing their experiences with this and other 3D Graphics. Add to the TRM. .

10. Dept of Education Input • TRM • Explain whether the proposed revision is tightly aligned to a specific SRM Service Domain, Service Type, or Component or is cross-cutting in nature (i.e., could support multiple SRM Service Domains, Service Types, or Components). Cross-cutting. • How does the proposed revision affect existing elements of the SRM (e.g., specific Service Domains, Service Types, or Components)? See attached PowerPoint presentation.

11. Proposal Specifics from Dept of Ed • Goal 1: Eliminate two redundant and inappropriate terms: (1) Platform-Dependent and (2) Platform-Independent. • Goal 2: Rationalize and unify all technical terminology related to “Data Management” in a new area of the TRM. • Goal 3: Rationalize all business and policy terminology related to data in the SRM. These Goals are Admiral and Reflect the Interdependencies: Between each of the Reference Models What is missing in maintaining the Reference model is Why – this was Included- the situation that it is used in (Rationale)

12. Summary of TRM Changes • Delete/Revise Platform-Dependent/Platform-Independent • Move “Data Management” from Component Framework to its own new Service Area. See later slide for new structure. • Move Data Exchange to Data Management; Delete Data Interchange • Move all items from Interoperability to Data Management; Delete Interoperability.

13. Delete Move to DM Delete/Revise Storage Move to DM Delete From Page 58 Delete – handled elsewhere in DM

14. TRM Change Recommendations • The terms Platform Independent and Platform Dependent really are confusing and should be deleted as currently represented • The bigger question involves Data Management issues: • The question is whether there are Data Platform and Storage issues that are separate from the Models- Metadata and Data Services- Query and Exchange Issues that the DRM addresses? • The issues involve: • Performance • Scaleability • Types of Storage • Recovery and Resiliency • Data Management and Support Functions • Recommend that a task force prepare: Data Management System Issue update for the TRM and that it take into considerations the latest data management technologies and the improvements that have been made in management and resiliency and cost of storage. • Is the TRM really the Infrastructure Support Level and should include all elements? • This should be looked at as part of a Enterprise Transformation Infrastructure Task Force These further studies are things that the IAC can help with!

15. Data Management – New Area in TRM • Database Design (See spreadsheet for details) • Database and Metadata Design Tools • Database Connectivity and Interchange (See spreadsheet for details) • Data Exchange • SQL Connectors • Operational Database Systems (See spreadsheet for details) • Relational DBMS • Legacy and Pre-relational DBMS • Information Retrieval for Unstructured or Semi-Structured Data • Data Quality, ETL, and Data Profiling • Data Reporting and OLAP Tools • Other Operating DBMSs and Data Stores

16. Service Offering Life Cycle: TRM Has to be aligned with Some Service Offering approach such as this! Source: Global Information Grid, Core Enterprise Services, Draft, version 1.1a, dated July 9, 2003

17. Core Enterprise Services: Needs to be reviewed! • Collaboration Services • Storage Services • Discovery Services • Messaging Services • User Assistant Services • Enterprise Service Management Services • Information Assurance and Security Services • Mediation Services • Application Services

18. Components of Enterprise Architecture: Standards First Approach Service Oriented Architecture (SOA) Elements Need to be defined in consistent manner Events & Messaging (JMS WS-*) Event Analysis Event Correlation Monitoring and Mgmt Many organizations are defining their Target Architecture with SOA elements that are not in the TRM Security (SAML WS-Sec) Reliability Availability Scalability Event Mgmt Event Modeling Transport (SOAP/ HTTP) Description (WSDL,XSD) Basic SOA (Services) Registration Discovery (UDDI) Data Lifecycle Mgmt BP Simulation Analysis Metadata Mgmt ServiceOrchestration Link to SOA RM: OASIS showing Phased Approach Advanced SOA (Services Mgmt) Predictive Modeling Predictive Analytics Enterprise Architecture (Events + Services)

19. Components of an Enterprise SOA Infrastructure Assure Vendor Independence with Options: Sample of what needs to be done with Further Investigation

20. Components of an Enterprise SOA Infrastructure Recommend that companies place information into et.gov & government industry team classify and make full recommendation of periodic basis

21. Closing Thoughts… THANK YOU!!!!! (Moving Forward…..IAC can support further Reference Model Maintenance Activities)