U.S. General Services Administration Introducing CORE.GOV The FEA’s Component Center A governmentwide collaborative COMPONENT ORGANIZATION & REGISTRATION.

Slides:



Advertisements
Similar presentations
Financial Management Service Holden Hogue March 12, 2009 Standardizing, Consolidating, and Optimizing Budget & Financial Management Business Processes.
Advertisements

SmartER Semantic Cloud Sevices Karuna P Joshi University of Maryland, Baltimore County Advisors: Dr. Tim Finin, Dr. Yelena Yesha.
Connecting People With Information DoD Net-Centric Services Strategy Frank Petroski October 31, 2006.
June 3, E-Gov and the Federal Enterprise Architecture Presentation to the Ontolog Forum Marion A. Royal November 06, 2003.
Office of the Chief Information Officer EFCOG Annual Meeting Fred Catoe (IM-32) U.S. Department of Energy.
1 How Semantic Technology Can Improve the NextGen Air Transportation System Information Sharing Environment 4th Annual Spatial Ontology Community of Practice.
U.S. Department of Agriculture eGovernment Program eLearning Pre-Implementation Approach May 2003.
IRS XML Standards & Tax Return Data Strategy For External Discussion June 30, 2010.
1 Data Strategy Overview Keith Wilson Session 15.
U.S. ENVIRONMENTAL PROTECTION AGENCY Reusable Component Services RCS Update Presentation to Enterprise Architecture Team 09/11/2012 John Harman,
Embedding Records Management into Agency Processes The FEA Records Management Profile Laurence Brewer, CRM National Archives and Records Administration.
SOA – Development Organization Yogish Pai. 2 IT organization are structured to meet the business needs LOB-IT Aligned to a particular business unit for.
Proposed EA Assessment Framework 2.0 Chief Architect’s Forum (CAF) Dick Burk Chief Architect and Director of Federal Enterprise Architecture Program, OMB.
ISO as the metadata standard for Statistics South Africa
Web 2.0 for Government Knowledge Management Everyone benefits by sharing knowledge March 24, 2010 Emerging Technologies Work Group Rich Zaziski, CEO FYI.
History, Charter & Challenges Facing the XML Community of Practice (xmlCoP) Owen Ambur, Co-Chair Emeritus xmlCoP/XBRL CoP March 20, 2007.
FEA DRM Management Strategy 11 October 2006 “Build to Share”
Transforming the Business of Government Through Shared Services JOHN SINDELAR Deputy Associate Administrator United States General Services Administration.
PROJECT NAME: DHS Watch List Integration (WLI) Information Sharing Environment (ISE) MANAGER: Michael Borden PHONE: (703) extension 105.
ET.Gov Joint AIC Meeting February 17, 2005 EmergingTechnology.gov Overview and Status Owen Ambur Co-Chair, XML CoP This document is confidential and is.
Update on SFA’s Modernization Project Steve Hawald Chief Information Officer Student Financial Assistance U.S. Department of Education “We Help Put America.
Larry L. Johnson Federal Transition Framework.
Introduction to IT Governance Support System (ITGSS)
Save time. Reduce costs. Find and reuse interoperability solutions on Joinup for developing European public services Nikolaos Loutas
Service Oriented Architecture (SOA) at NIH Bill Jones
FEA Data Quality Profile – Progress Report July 12, 2007 Presented to Federal Data Architecture Subcommittee (DAS)
1 Emergency Management Standards EM- XML Consortium & EM Technical Committee Presentation to Steve Cooper March 18,2003.
Page 1 Federal Information and Records Managers (FIRM) Council 2007 OMG Government Domain Task Force National Archives and Records Administration.
Recommendations to Committee on Technical Architecture Sub-Committee on Web, Social Media and Mobile Governance Jeff Jorgenson March 21st, 2012.
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
U.S. Department of Agriculture eGovernment Program Design Approach for usda.gov April 2003.
E-government models Lecture 8.
NIEM Information Exchange Package Documentation (IEPD) Mini Kanwal NIEM Technical Advisor Department of Homeland Security September, 7 th 2006.
FEA DRM Management Strategy Presented by : Mary McCaffery, US EPA.
Tuning Emerging Technologies…Making Them Play Together: From Stovepipes to Wind Chimes! Jim Disbrow, Project Manager Susan Turnbull, Co-Chair, ET Subcommittee.
U.S. Department of Agriculture eGovernment Program Select-Level Business Cases USDA Enabler’s Gameboard and Upcoming Schedule.
1 DAS Annual Review June 2008 “Build to Share” Suzanne Acar, US DOIAdrian Gardner, US National Weather ServiceCo-Chair, Federal DAS
EGovOS Panel Discussion CIO Council Architecture & Infrastructure Committee Subcommittee Co-Chairs March 15, 2004.
Service Component Registry and Repository (SCRR) April 26, 2007 Lico Galindo 2007 Exchange Network National Meeting.
Federal Enterprise BOF Rick Murphy Chief Architect, Blueprint Technologies June 7, 2004.
1 - 12/5/2015 Building the Business Case for eProcurement January 29, 2002 Mary Mitchell Office of Electronic Government GSA Office of.
Strategic Markup Language (StratML) XML CoP
Cartographic Users Advisory Council The National Spatial Data Infrastructure and the Geospatial One Stop E-Gov Initiative May 3, 2002 John Moeller Staff.
Project Initiation at The Regence Group 12/19/2015John Garrigues1.
User-Driven Integrated Statistical Solutions: Government for the People by the People Open Forum on Metadata Registries Santa Fe, New Mexico January 20,
“Provide best value for customer agencies and taxpayers” 1 Software Asset Management Fred Allen - SAM Program Manager General Services Administration Interagency.
U.S. Department of Agriculture eGovernment Program Integrated eGovernment Reporting May 2004.
HHS CEA Executive Briefing HHS Enterprise Performance Life Cycle (EPLC) and Program/Project Manager (PM) Certification NIH PM Forum September 12, 2007.
OASIS ebXML Registry Standard Open Forum 2003 on Metadata Registries 10:30 – 11:15 January 20, 2003 Kathryn Breininger The Boeing Company Chair, OASIS.
HP-PPM Work Plan Configuration Options Project & Time Management Version 7 Implementation Project\Work Plan and Time Management\Work Plan Configuraiton.ppt.
Federal Enterprise Architecture (FEA) Architecture Plus Meeting December 4, 2007 Kshemendra Paul (Acting) Chief Architect.
Environmental Public Health Tracking Network (EPHTN): Enterprise Architecture (EA) Ray Buckner Environmental Health Tracking Branch Division of Environmental.
Building a BA Center of Excellence Gain Momentum...Produce Results!
1 Data Warehouse Assessments What, Why, and How Noah Subrin Technical Lead SRA International April 24, 2010.
Metadata Schema Registries: background and context MEG Registry Workshop, Bath, 21 January 2003 Rachel Heery UKOLN, University of Bath Bath, BA2 7AY UKOLN.
Government-wide Talent Development November 20, 2014.
International Planetary Data Alliance Registry Project Update September 16, 2011.
Managing Enterprise Architecture
IPDA Registry Definitions Project Dan Crichton Pedro Osuna Alain Sarkissian.
Introduction to the GEOSS Registries: Components, Services, and Standards Doug Nebert U.S. Federal Geographic Data Committee June 2007.
Sample Fit-Gap Kick-off
Transforming the Business of Government Through Shared Services JOHN SINDELAR Deputy Associate Administrator United States General Services Administration.
Core Task Status, AR Doug Nebert September 22, 2008.
About The Federal Data Architecture Subcommittee (DAS) 2008
Metadata in the modernization of statistical production at Statistics Canada Carmen Greenough June 2, 2014.
CAF Quarterly Meeting Measuring the Value of an EA Practice
Request for Change and Release of Funds
FFEL Business Process and Data Standardization
Introduction to SOA Part II: SOA in the enterprise
Presentation transcript:

U.S. General Services Administration Introducing CORE.GOV The FEA’s Component Center A governmentwide collaborative COMPONENT ORGANIZATION & REGISTRATION ENVIRONMENT

U.S. General Services Administration Executive Summary A component is a “self-contained business process or service with predetermined functionality that may be exposed through a business or technology interface.” [Component Subcommittee] CORE.GOV provides a collaboration environment for component development, registration and reuse.  Business process components (e.g., pay.gov)  Technical components (e.g., XML schema, Web services)  E-Forms (e.g., SBA Business Gateway)  Federal Enterprise Architecture Management System (FEAMS)

U.S. General Services Administration Reuse AIC SC CIO OMB Compon ent Life Cycle AIC Subcommittees (AIC SC) Develop Capabilities Identify Gap Retire Publish Certify Submit for Certification AIC SC CIO OMB Approval Process AIC SC Recommend/ Mandate Entry to Life Cycle Component already under development Entry to Life Cycle Component already completed Entry to Life Cycle New component needed Exit from Life Cycle Component obsolete Component Lifecycle Process

U.S. General Services Administration The Problem Currently, there is a need for cross-agency tools to manage the component lifecycle.  Some agencies have tools under development, and other agencies have none  We have a huge gap between the registries that serve very technical solutions and registries that provide management capabilities of business processes  Many different and inconsistent definitions of a “component”  Low stakeholder participation to date

U.S. General Services Administration The Solution A Collaborative Environment that will:  Facilitate component development, accreditation, publishing, discovery, use and reuse  Reduce the proliferation of redundant registries/repositories  Apply a standardized component definition to the FEA  Provide a forum for evaluating and improving the component lifecycle process and presenting a unified lifecycle vision

U.S. General Services Administration  Provide the management capability for the entire component lifecycle  Become the government’s premier registry and repository of technical- and business-process components  Provide a library of approved components for use and enhancement  Provide the collaborative environment for continual development of the FEA reference models Vision

U.S. General Services Administration Benefits  Leverage tools and save money  Registry/repository of approved components for reuse and enhancement  Easy-to-use cataloguing system (i.e., “componentname.core.gov”  Consolidated entry point  Collaborative FEA and component development  Government scope and participation

U.S. General Services Administration The Process  Recommending components for registration  Certifying components  Publishing components  Searching for components  Collaborating with others on component development projects

U.S. General Services Administration Implementation  Phase I: Create a Collaborative Environment for Consolidated Component Registry/Repository  Phase II: Integrate Development Tools and Applications  Phase III: Federation with Other Registries/ Repositories  Phase IV: Operation and Maintenance

U.S. General Services Administration CORE.GOV Contact Information For more information, contact: GSALee Ellis Marion Royal SAICCloe Vincent Jay Bayfield CollabNetMike Kochanik

U.S. General Services Administration Thank You Marion A. Royal