An Overview is provided of past & present collaborative activities undertaken by the OMG, OMB, and other government agencies to improve the communication among the OMB and U.S. Federal Government Agencies. The overview will include the approach taken to assure independent but synchronized and mutually informed governance of the OMB and the OMG processes. The governance model serves as a template for government work in the OMG and was evolved from extensive collaborative work done by the National Archives and Records Administration in the OMG.
  

This presentation and discussion will trace the history of Federal EA practices and the rationale for the evolution of that practice. Challenges and successes will be explored with a focus on cross governmental information sharing needs. The driving need for standardized approaches, metamodels and tool sets for future Federal enterprise architecture needs will also be discussed.
  

In 2008, the OMB FEA PMO came to the Object Management Group's (OMG) Government Domain Task Force (GovDTF) asking that it formalize the EA Segment Report as an OMG metamodel specification. A similar specification had been developed through the GovDTF for the Federal Transition Framework (FTF). The GovDTF performed an analysis of the EA Segment Report and related data model. It concluded that the scope of the activity should be expanded to the formalization of a segment architecture metamodel of broader scope, encompassing elements of FEA including the CRM, FTF, and aspects of CPIC. A team comprised of representatives from the FEA PMO, agencies and the OMG vendor community was formed to develop the Metamodel for Federal Segment Architecture (MFSA) specification. This presentation describes the work of that team, the metamodel specification produced, its relationship to the Federal Segment Architecture Methodology, and its support of FEA PMO analysis and reporting objectives.
  

Mr. Thomas will provide an overview of the "as-is" in the interactions among the agencies and the OMB and discuss the "could-be", i.e., how the new environment could look when streamlined under an expanded portfolio of standards. This will "set the scene" for the panel discussion in which presenters and other panelists discuss what standards might be added to the OMB/OMG Collaboration Agenda to transform the "could-be" to "will-be".
 

Facilitator: 

John Butler
Everware-CBDI, Co-chair, Government Domain Task Force

Panelists:

Larry Johnson
TethersEnd Consulting, Co-chair, Government Domain Task Force
Bob Daniel
CTO, Government Sector, Troux Technology

- additional panelists TBD
  

As we fulfill our role as the nation's record keeper, the National Archives and Records Administration has long recognized the challenge presented by the wide variety and enormous volume of electronic records being created by the Federal government. We have been working for more than a decade to meet that challenge by developing leading-edge preservation systems that will protect and provide access to the records as we receive them.

However, we also understand another facet of the same problem: that our customers, the agencies of the Federal government, face comparable challenges as they endeavor to manage the electronic records they create and rely upon for their own business processes. Our work with OMG and the Records Management Services project is enabling us to explore and evaluate exciting and efficient new methods of managing such records based on the modularity and flexibility that can result when software is implemented as services.
  

A look backward as we move forward in the world of electronic records. 19 agencies came together to accomplish a mission that was thought to be impossible; agree upon requirements for electronic records. The rules, the players, the process and the ongoing outcome will be presented in order to understand how it happened and why it is still going.
  

Under contract to the National Archives and Records Administration (NARA), Larry facilitated the Joint Records Management Services Submission Team (JRMS) that produced the RMS standard. JRMS was a coalition of government, industry, and academic representatives. The presentation provides an overview of how the specification was defined using Model Driven Architecture. The specification began with the functional requirements produced by a 19 agency inter-agency project team facilitated by NARA. The modifications, extensions and elaborations required to produce a semantically precise specification are discussed.
  

The discipline of records management developed in the context of hard copy information technology. Its basic concepts and methods are deeply rooted in that technology; for example, assuming that a record is no different than the paper on which it is written. The new dimension opened up by digital technology forces a reassessment and reformulation of records management, starting with the very nature of records and aiming at maximizing the value that records management adds in the conduct of business.
  

The co-author of the DoD 5015.2 Records Management Specification will give us a view into upcoming changes in technology, standards, and best practices that will impact your records and information management programs. This discussion will conceptualize how changes in technology, practices, and standards can be used to streamline and improve your records management program. Get insight into:

• NARA’s big-buckets vs little buckets directive
• Records Management Services standards development
• The Impact of Information Governance
• The Impact of E-Discovery Requirements
• The Impact of Social Networks
• RMA interoperability requirements

The Records Management Services can be implemented via the use of a SOA framework. Melvin Greer’s session will discuss how a SOA framework can support the implementation of Records Management Services and how agencies can accelerate a lifecycle records management requirements capability with a high degree of flexibility and at a lower cost. This session will also discuss impact of adding the records management service to the agency Service Reference Model.
  

There are a number of services that are necessary for sucessful enablement of a services environment: Messaging, Discovery, Logging, Cross-environment dispatching, etc. CSC has developed such a framework of technology and implementation agnostic foundational services, called the SOAssure Foundation, and are using it as the basis for enabling services environments. It is our intention to connect OMG's Record Management Service as a part of this framework resulting in the offering a common gateway to records management service implementations from vendors that implement the enablement of the JRMS specification.
  

Facilitator:

John Butler
Everware-CBDI, Co-chair, Government Domain Task Force

Panelists:

Larry Johnson
TethersEnd Consulting, Co-chair, Government Domain Task Force
Kenneth Thibodeau
Director, Electronic Records Archives Program, National Archives and Records Administration
Victor Harrison
Director, Distinguished Engineering Group, CSC
Bill Manago
Director, Records Management Practice, CA
Melvin Greer
SOA Chief Architect, Lockheed Martin