Page 1 Federal Information and Records Managers (FIRM) Council FORUM @FOSE 2007 OMG Government...

Federal Information and Records Managers (FIRM) Council FORUM @FOSE 2007

OMG Government Domain Task ForceNational Archives and Records Administration

MDA Models for Records Management ServicesPopulation of CORE.gov

Melvin GreerSenior Research Engineer, Principal

Certified Federal Enterprise Architect

Copyright 2007 by Lockheed Martin

March 20, 2007

Objectives of this Session

Methods that encourage Industry incentive to invest in publicly available SOA components

Federal SOA…dependant on the discovery and reuse of registered and graduated

components

• Encourage and differentiate use of ET.gov / CORE.gov• Emphasize Community of Practice (CoP) role

OMG MDA, ET.gov / CORE.gov…an Integrated Process

Build RMSC

Discovery, Reuse, Governance

OMG

ET.gov / CORE.gov

Integrated Plan

Emerging Technology (ET) .gov …… or Component Organization and Registration Environment (CORE) .gov

• ET.gov facilitates the identification, discovery, and formation of communities of practice (CoP)

• CORE.gov a collaborative environment and component registry/repository where teams register processes, capabilities, case studies, best practices, documentation, and software components

Both are sponsored and run by CIO Council and GSA

RMSC in ET.gov

• Overall ET.gov Process

– Identification / Registration

– Subscription

– Stewardship

– Graduation

– Budgeting

– Acquisition

– Maintenance

– Retirement / Replacement

RMSC has been approved at

Stewardship…Graduation will lead to its population into

CORE.gov

Identification and registration

• Create an XML document which describes RMSC component, http://et.gov/component_search.aspx

Benefit – searchable, detailed component, owner, state information

Information regarding proposed components is registered, indexed, and made available for browsing and searching. Anyone may identify an ET

component

http://et.gov/component_search.aspx

Subscription

• 19 Agencies self-subscribed to RMSC component thereby forming community of practice (CoP), http://gov.omg.org/rms

Benefit - RMSC Community of Practice drives development, design, discovery, adoption and reuse of RMSC

Government employees and others subscribe to components of interest to them, thereby forming CoPs around those components.

CoP may use any collaborative environment around ET components, such as CORE.gov

http://gov.omg.org/rms

Stewardship

• The CIO Council's (CIOC) Emerging Technology Subcommittee agreed to accept stewardship of RMSC based upon the interest and commitment embodied in the RMSC CoP, http://et.gov/stage3.htm#cops

Benefit – CoP demonstrate to ET.gov and CORE.gov leadership that sufficient resources exist to determine RMSC technical viability and utility…and that real customers exists

The ET Subcommittee accepts stewardship of components for which sufficient interest exists, as evidenced by the CoPs forming around them.

http://et.gov/stage3.htm#cops

Graduation

• RMSC will "graduate" to become a relatively mature new service component

Benefit - the CIO Council's Governance Subcommittee can recognize the RMSC in the Service Component Reference Model (SRM) and catalog it in the Technical Reference Model (TRM) and apply the governance process for the Federal Enterprise Architecture (FEA) models.

The technical viability and utility of ET components are demonstrated, whereupon they become candidates for inclusion in CORE.gov for

Government-wide access.

OMG Government Domain Task ForceMDA Models for Records Management Services (RMS)

Approval Process (due complete March 2008)

– Revised Submission

– Final evaluation and selection by Task Force, recommendation to Architecture Board and Technology Committee

– Approval by Architecture Board, review by Technology Committee

– Technology Committee votes

– Board of Directors votes

RMSC Key Features

• Integrated OMG MDA and ET.gov process• Indexed and searchable at origin• CoP drives development with inward focus• Simultaneous review by ET and CORE leadership• Leverage FEA governance process

Benefit – Increase RMSC adoption and reuse

Way Ahead

• Refine development of CIM, PIM, PSM OMG models

• RMSC CoP– Confirm translation of RMS requirements document– Evaluate and Validate RMS Use Cases– Technical assumptions (Metadata, Persistence, Provenance)– Schedule Collaboration/Expedition Workshop– Collaborate with SOA CoP

• Determine which FEA artifacts will be required to guide the demonstration of the RMSC, and lead to its population into CORE.gov

Page 1 Federal Information and Records Managers (FIRM) Council FORUM @FOSE 2007 OMG Government...

Documents

Transcript of Page 1 Federal Information and Records Managers (FIRM) Council FORUM @FOSE 2007 OMG Government...