OMG Homepage MDA Homepage CORBA Homepage MOF Homepage UML Homepage CWM Homepage XMI Homepage DDS Homepage OMG MARTE BPMN Homepage SysML Homepage banner



Government Domain Task Force (GovDTF)

GovDTF Document Library

Updates in Progress through the Salt Lake City TC Meeting, June 2011


Table of Contents


Charter


Adopted Technology

  • Model for Performance-driven Government Version Beta (MPG)
    This specification was adopted by the Board of Directors on 21 June 2010. The Beta Version was adopted through the MPG Finalization Task Force.
     
    • The MPG V1.1 Revision Task Force is accepting issues against the Version 1.0 specification. Resolution of these issues will result in the adoption of MPG V1.1.
    • To submit an issue, send an eMail to issues@omg.org.  Provide a brief Title for the issue as well as a brief (as possible) description of the issue.
       
  • Records Management Services Version 1.0
    RMS Version 1.0 was approved by the OMG Board of Directors in an eMail vote shortly after the Salt Lake City TC Meeting, June 2011
     
    • The RMS V1.1 Revision Task Force is accepting issues against the Version 1.0 specification. Resolution of these issues will result in the adoption of RMS V1.1.
    • To submit an issue, send an eMail to issues@omg.org.  Provide a brief Title for the issue as well as a brief (as possible) description of the issue.
       
  • Federal Transition Framework Version 1.0 
    The Formal Version 1.0 of the specification was adopted by the Board of Directors in its Santa Clara CA Meeting, 9-December-2008.
     
    • The FTF V1.1 Revision Task Force is accepting issues against the Version 1.0 specification.  Resolution of these issues will result in the adoption of FTF V1.1.
    • To submit an issue, send an eMail to issues@omg.org. Provide a brief Title for the issue as well as a brief (as possible) description of the issue.

Requests for Proposal

The leading dates are the dates each RFP was originally issued... not the date of any resulting specification.

20110624: The UML Profile for NIEM RFP was issued in the Salt Lake City TC meeting in June 2011 as OMG Document gov/2011-06-04 by the Domain Technology Committee. Click here for the project page.

The objective of this RFP is to provide a standard for modeling National Information Exchange Model (NIEM) artifacts (Model Package Documents - MPDs) with UML. MPDs include numbered releases, domain updates, and IEPDs (Please see Appendix A for the glossary of terms).

This RFP solicits proposals for the following which together shall comprise “NIEM-UML”:

  • UML profiles for modeling NIEM MPDs; a logical profile that will enable the development of Platform Independent Models for NIEM content, and a second profile that provides the parameters required to transform the logical model to NIEM conformant XML schema and MPD specifications (the Platform Specific Model)
  • A transformation from UML models that conform to the NIEM profiles (described above) to NIEM-conformant MPD artifacts
  • Optionally, a transformation from a NIEM-conformant XML schema set (as defined by the NIEM NDR) to a UML model that conforms to the profile(s)
  • A UML representation of the NIEM controlled vocabularies (reference namespaces) from which MPDs are constructed. This UML representation must conform to the profiles mentioned in the first bullet point.
  • Status:
    • Letters of Intent to submit are being received until 21-August-2011
    • The Voting List is Open for registration until 01-January-2012

20091211: The Records Management Services Version 2 RFP was issued in the Long Beach TC meeting in December 2009 as OMG Document gov/2009-12-05 by the Domain Technology Committee. Click here for the project page.

The OMG adopted the Records Management Services specification (Beta-1: http://www.omg.org/spec/RMS/1.0/Beta1/) in June 2009. Provision for specifying context dependent Attribute Profiles was established, but specific instances were not. Additionally, no fine grained compliance points were defined. Compliant implementations are constrained to implement the specification in toto.

This RFP solicits proposals for the following:

  • The provision of one or more Attribute Profiles minimally supporting  DoD 5015.02 compliant Records Management Environments.

  • The addition of compliance points to subset service operations and profile attribution as it is affected by the subsetting. This will allow RMS to be provisioned on a scale that suits the business needs of diverse organizations.

  • Status:
    • The RFP LOI deadline has expired; however, the GovDTF anticipates re-opening it in its Minneapolis MN Plenary, 20100610.
    • The Voting List is OPEN and accepting membership. It will close 20100906.

20090626: The Model for Performance-Driven Government (MPG) formerly titled the Metamodel for Federal Segment Architecture RFP (OMG Document gov/2009-06-04) was Issued by the Domain Technology Committee during its Plenary at OMG's San Josι Costa Rica Technical Committee Meeting, 26-June-2009.

Building on the FEA Practice Guidance, the US Office of Management and Budget (OMB) has created the Federal Segment Architecture Methodology (FSAM) for use by Executive Branch agencies as a means of achieving more complete and consistent segment architecture products; expediting development of segment architectures; and enabling greater reuse of segment architectures. To further these goals, the OMB has defined the Enterprise Architecture Segment Report (EASR) as the standard format through which agencies report on their performance and progress developing segment architectures. Fundamental to both the FSAM and EASR is the Metamodel for Federal Segment Architecture (MFSA). The OMB and OMG have created a roadmap for working collaboratively to create this metamodel as an industry standard, enabling the development of commercial modeling tools and repositories capable of managing, querying, retrieving, and reporting segment architecture information. It is expected that such tools will also provide comprehensive enterprise architecture modeling and analysis capabilities for agencies that build segment architecture models represented using the MFSA.

  • Status: Current Version is the Version 1.0 Specification

    MPG Version 1.0 was approved by the OMG Board of Directors in an eMail vote shortly after the Salt Lake City TC Meeting, June 2011
     

  • MPG Version 1.0 Specification – Current Specification
    MPG Version 1.0 was approved by the OMG Board of Directors in an eMail vote shortly after the Salt Lake City TC Meeting, June 2011. The URL's will change when the OMG Technical Editor moves it to the Formal Specification directory.
    • Specification Manifest
      • dtc/2011-03-14 – An inventory of all documents related to the proposed specification.
    • Normative Files (except as indicated)
      • dtc/2011-03-13 – Textual Specification (The Beta 2 Document which will become the Formal 1.0 Document after the OMG Technical Editor moves it to the Formal Specification directory.)
      • dtc/2011-03-02 – MPG Platform Independent Model in XMI Format
      • dtc/2011-03-15 – Machine Consumable Files... a Zip File containing
        • MPG_example.xml – (NON-NORMATIVE)
          Description: Example instantiation of the MPG XSD
        • MPGMODEL.xsd
          Description: MPG XSD Platform Specific Model
        • BMMMODEL.xsd
          Description: MPG XSD Platform Specific Model taken from the Business Motivation Metamodel (BMM) which is used by MPG.
    • Non-normative Informational Files
      • dtc/2011-02-11 – Non-normative Representation of the Model for Performance-Driven Government (MPG) as UML Model in Native Sparx EA Format in a Zip Archive.
        A free viewer is available (click & scroll to the bottom of the page)
         
  • MPG Beta Specification

    • This specification was adopted by the Board of Directors on 21 June 2010.
    • Normative Files
    • Non-normative, Informational Files
      • gov/2010-03-04, MPG Model in Sparx Systems' Enterprise Architect Format
        A free viewer is available (click & scroll to the bottom of the page)
         
  • MPG Alpha Specification

    • This specification was approved by the Architecture Board in its Jacksonville FL Plenary meeting on 26-March-2010 and subsequently adopted by the Board of Directors on 21 June 2010
    • Normative Files
    • Non-normative, Informational Files
      • gov/2010-03-04, MPG Model in Sparx Systems' Enterprise Architect Format
        A free viewer is available (click & scroll to the bottom of the page)

20060630: The Records Management Services RFP (OMG Document gov/2006-06-11) was Issued by the Domain Technology Committee during its Plenary at OMG's Boston Technical Committee Meeting, 30-June-2006. (Originally named "MDA Models for Electronic Records Management Services", it is now referred to simply as "Records Management Services")

This RFP is based on the requirements defined by a Records Management Services Component Interagency Project Team (RMSC IPT). Information on this team and its work products is available on the project page, http://gov.omg.org/gov-rfp-rms.htm. The OMG status page (accessible to OMG members only) can be found here.

  • Status: Current Version is the Version 1.0 Specification

    RMS Version 1.0 was approved by the OMG Board of Directors in an eMail vote shortly after the Salt Lake City TC Meeting, June 2011
     

  • RMS Version 1.0 Specification – Current Specification
    RMS Version 1.0 was approved by the OMG Board of Directors in an eMail vote shortly after the Salt Lake City TC Meeting, June 2011
    • Specification Manifest
      • dtc/2010-12-17 – An inventory of all documents related to the proposed specification.
    • Normative Documents
      • dtc/2010-12-19 – Textual Specification: "Proposed Records Management Services Version 1.0 Specification"
      • dtc/2010-12-20 – OMG Model Interchange Format (XMI) File of the RMS Version 1.0 UML Model
      • dtc/2010-11-33 – Machine Consumable Web Service Definition Language Files (WSDL's). A "zip" file containing:
        • 0-Inventory.txt
          Description: Description of the following files.
        • Annotations.wsdl
          Description: WSDL file defining the operations of the Annotations service.
        • AttributeProfiles.wsdl
          Description: WSDL file defining the operations of the AttributeProfiles service.
        • Authorities.wsdl
          Description: WSDL file defining the operations of the Authorities service.
        • Categories.wsdl
          Description: WSDL file defining the operations of the Categories service.
        • Dispositions.wsdl
          Description: WSDL file defining the operations of the Dispositions service.
        • Documents.wsdl
          Description: WSDL file defining the operations of the Documents service.
        • ManagedRecords.wsdl
          Description: WSDL file defining the operations of the ManagedRecords service.
        • Parties.wsdl
          Description: WSDL file defining the operations of the Parties service.
        • Query.wsdl
          Description: WSDL file defining the operations of the Query service.
        • RecordAuthentications.wsdl
          Description: WSDL file defining the operations of the RecordAuthentications service.
      • dtc/2010-11-34 – Machine Consumable XSD Files Supporting RMS Information Exchange
        • 0-Inventory.txt
          Description: Description of the following files.
        • Annotation.xsd
          Description: XSD file supporting the exchange of Annotation data.
        • AttributeProfile.xsd
          Description: XSD file supporting the exchange of AttributeProfile data.
        • Authenticity.xsd
          Description: XSD file supporting the exchange of Authenticity data.
        • Category.xsd
          Description: XSD file supporting the exchange of Category data.
        • Disposition.xsd
          Description: XSD file supporting the exchange of Dispositions data.
        • Document.xsd
          Description: XSD file supporting the exchange of Document data.
        • ManagedRecord.xsd
          Description: XSD file supporting the exchange of ManagedRecords data.
        • Party.xsd
          Description: XSD file supporting the exchange of Party data.
        • Role.xsd
          Description: XSD file supporting the exchange of Role data.
        • RmsSet.xsd
          Description: XSD file supporting the exchange of any RMS data. This XSD imports all of the above XSD's, making any of their elements optional, and provides a container (root element) that is not part of the RMS Domain Semantics.
    • Informative Documents
      • dtc/2010-12-18 – The Report of the RMS-FTF. Includes
        • General Overview of the changes made.
        • RMS-FTF Membership and Voting Record in Each Resolution Ballot
        • Description of each Issue balloted, including its Resolution, and Disposition
      • dtc/2010-12-21 – Change-barred Version of the Proposed Specification
        • Each change from the original Beta-Version is marked and tagged with the issue resolution(s) that effected the change.
      • dtc/2010-12-22 – Non-normative Representation of the Proposed RMS Version 1.0 UML Model in Native Sparx EA Format in a Zip Archive.
  • RMS Beta 1 Specification
    • Beta 1 Specification – This is the official OMG page for the RMS Beta 1 Specification. This is the page to use if you wish to download a single file (e.g., the RMS.XSD). None of these files are zipped, so each file must be downloaded individually and accessing a large file such as the native Sparx EA model file (the originator of most of the other files) will take some time.
    • Beta 1 Artifacts bundled.
      • Normative Material
        • Textual Specification in PDF format – This is derived from the original Alpha Specification with submission boiler plate material removed, specification boiler plate added, and conversion to PDF. This is the document which is the starting place for the RMS Finalization Task Force. Issues are presumed entered against this document.
        • RMS Model in XML Model Interchange Format (XMI) This is the normative UML model of the RMS standard.
        • Machine Readable Artifacts in a ZIP file which includes:
          • Descriptive Material – A description of the zip contents in both MS Word and PDF formats.
            • 0-ReadMe.doc
            • 0-ReadMe.pdf
          • Web Services Definition Files (WSDLs)One WSDL file for each of the ten RMS Services. The name of the file is the name of the service.
            • Annotations.wsdl
            • AttributeProfiles.wsdl
            • Authorities.wsdl
            • Categories.wsdl
            • Dispositions.wsdl
            • Documents.wsdl
            • ManagedRecords.wsdl
            • Parties.wsdl
            • Query.wsdl
            • RecordAuthentications.wsdl
          • XML Schema Definition Files (XSDs)
            • RMS.xsd – An XSD which defines the import/export structure for RMS. This XSD is also the reference against which XQueries are defined for use in the RMS Query Service.
            • AttributeProfile.xsd – An XSD which defines the "meta-level" of attribute definition for the RMS AttributeProfiles Service. This is used to form XML documents to communicate attribute definitions between service consumers and providers.
      • Informative Material
        • RMS Model in Sparx EA Format in a ZIP file.
          A free viewer is available (click & scroll to the bottom of the page)
           
  • RMS Alpha Specification
    • This specification was approved by the Architecture Board in its Washington D.C. Plenary meeting on 27-March-2009. It passed the subsequent electronic vote to recommend for adoption by the Domain Technology Committee initiated in its plenary in Washington on 28-March-2009. The Board of Directors adopted the specification in its meeting in San Josι, Costa Rica on 23-June-2009.
    • Normative Files
      • http://doc.omg.org/gov/2009-03-03 – The textual specification. Modifications to the Records Management Services Specification Revised Submission, gov/2009-02-01, made in response to review comments made by the Architecture Board and the Government Domain Task Force
      • http://doc.omg.org/gov/2009-03-05 – The normative UML models in XMI format. A zip file of the RMS model in XMI v2.1 format. The RmsPim package is normative as specified in gov/2009-03-03.
      • http://doc.omg.org/gov/2009-03-10 – A zip file of the RMS machine-readable artifacts (WSDL and XSD files). These files are normative as specified in gov/2009-03-03. Supersedes gov/2009-03-04.
    • Non-normative, Informational Files
      • http://doc.omg.org/gov/2009-03-08 – Non-normative Sparx EA model from which the normative XMI, XSD, and WSDL files were generated. A free reader is available at http://www.sparxsystems.com/ under their product listing section.
      • http://doc.omg.org/gov/2009-03-09 – Records Management Services Specification Errata – Describes the differences between the original submission gov/2009-02-01 and gov/2009-03-03 which incorporates changes made in response to review comments made by the Architecture Board and the Government Domain Task Force. Supersedes gov/2009-03-06
      • http://doc.omg.org/gov/2009-03-07 – Records Management Services Specification Changes – A change-barred copy of gov/2009-03-03 describing its differences from gov/2009-02-01
         
  • Revised Submssion
    • gov/09-02-01: Records Management Services Specification Revised Submission – The RMS Revised Submission submitted by the Joint RMS Team consisting of CA, CSC, Lockheed Martin, and Visumpoint and supporting organizations. The machine readable files that are part of this submission are in gov/2009-02-02
    • gov/09-02-02: Records Management Services Specification Revised Submission Machine Readable Files – The WSDL and XSD's that are part of the RMS Revised Submission in gov/2009-02-01
    • gov/09-02-03: Records Management Services Native Model – An informative adjunct to gov/2009-02-01. The native format models used to produce the specification in Sparx EA V7.1 Format
    • gov/09-02-04: Records Management Services XMI – An informative adjunct to gov/2009-02-01. The XMI export of the models used to produce the specification in XMI 2.1 format
       
  • Initial Submissions: One initial submission was received
    • The specification, gov/2007-03-03 was submitted by a Joint Submission Team of the registered submitters and reviewed in the GovDTF plenary held 28-March-2007.
    • The Joint Submission Team is:
      • 88 Solutions
      • Model Drive Solutions (formerly Data Access Technologies)
      • CA (formerly Computer Associates)
      • IBM
      • CSC

20061208: The "Federal Transition Framework" RFP  (OMG Document gov/2006-12-02) was issued by the Domain Technology Committee during its Plenary at OMG's Washington DC Technical Committee Meeting, 8-December-2006.

Championed by the US President's Office of Management and Budget (OMB), this RFP is a follow on to the Federal Transition Framework WhitePaper. In the Related Document section of the project page there is additional information on the documents and background on which this RFP is based.

  • Status: The Formal Version 1.0 of the specification was approved by the Board of Directors in its Santa Clara CA Meeting, 9-December-2008.
  • Version 1.1 Specification
  • Version 1.0 Specification – The Latest Specification
    • The Formal Version 1.0 of the specification was approved by the Board of Directors in its Santa Clara CA Meeting, 9-December-2008
    • The Finalization Task Force expired without receiving an issue. Version 1.0 remains unchanged from the Beta version (formal/2009-02-01).
    • formal/2009-02-01– Formal Specification
    • gov/2007-09-04 – Machine Readable files (XMI/XSD's) plus additional materials including the Alpha Specification Text and non-normative material..
  • Beta Specification
    • formal/2009-02-01– Formal Specification
    • gov/2007-09-04 – Machine Readable files (XMI/XSD's) plus additional materials including the Alpha Specification Text and other non-normative material.
  • Alpha Specification
    • Adopted by the OMG Board of Directors in its Burlingame Meeting, December 2007
    • Specification: The complete specification is in a zip file at: gov/2007-09-04. This is a zip of all normative documents from the below listed Revised Submission with errata applied.
    • Though a completed work item. Background on the RFP can be found at http://gov.omg.org/gov-rfp-ftf.htm. The Official OMG Work in Progress Page can be found Here.
  • Revised Submission: A single Revised Submission was received consisting of six OMG documents
    • Documents
    • Submission Team
      • Adaptive
      • MEGA International
      • Model Driven Solutions
      • Telelogic AB
      • Troux Technologies
    • Based on GovDTF and AB review, an erratum was generated: gov/2007-09-03
    • A Finalization Task Force has been chartered for this specification. FTF-FTF Homepage
  • Initial Submissions:
    • 20070305: gpv/2007-03-03
      • Submission Team
        • Adaptive
        • MEGA International
        • Model Driven Solutions
        • Telelogic AB
        • Troux Technologies


Requests for Information

20070629: The Skills Management RFI was issued by the Domain Technology Committee during its plenary in Brussels, 29-June-2007

The GovDTF Roadmap was updated in Ottawa with work items suggested by response analysis. A Skills Management RFP was begun. (See http://gov.omg.org/gov-rfp-skills.htm)

 


Whitepapers

20110620: "Transforming Government IT With Architecture: Achieving Agility & Modularity"

On December 9, 2010 Vivek Kundra, CIO of the US Federal government, published the "25-Point Plan (the Plan) for Information Technology Management Reform." (http://cio.gov/documents/25-Point-Implementation-Plan-to-Reform-Federal%20IT.pdf } On the same day, William Lynn, Deputy Secretary of the Department of Defense, signed out the following report to the Armed Services Committee  entitled "A New Approach (the New Approach) for Delivering Information Technology Capabilities in the Department of Defense." (http://www.afei.org/WorkingGroups/section804tf/Documents/OSD_Sec_804_Report.pdf )

This whitepaper out lines how the architectural principles and disciplines can help achieve government's goals of Agility and Modularity in Government IT Acquisitions.

20090320: "OMG Value Proposition for Government Organizations"

The Object Management Group's (OMG) Government Domain Task Force (GovDTF) has been collaborating with government agencies around the world to produce specifications supporting governmental missions and goals designed to serve their citizens.

This whitepaper explores the value added to government agencies through the use of OMG’s Community Consensus Process and its Model Driven Architecture (MDA) approach to improving the efficiency and effectiveness of information technology capabilities and information sharing across all levels of government: national, regional, and local.

20060926: The "Federal Transition Framework Metamodel" Whitepaper was issued by the Task Force during its plenary in Anaheim, 26-September-2006.

This paper presents an introduction of the Federal Transition Framework to the OMG community, and conversely introduces the OMG to government agencies involved in the Office of Management and Budget's FTF. The paper documents a process to coordinate the separate life-cycle and governance processes of the two organizations.

 
 

Last updated on: 07/19/2011

Copyright © 1997-2014 Object Management Group, Inc. All Rights Reserved. For questions about the WEBSITE , please contact webmaster@omg.org For TECHNICAL questions, please contact webtech@omg.org This site is best viewed  with Netscape Navigator, Mozilla Firefox or Internet Explorer versions 6.0 or later or any browser
 capable of viewing JavaScript and CSS 2.0. The site is using
DHTML JavaScript Menu By Milonic.com.

Last updated on: 12/30/2013