{
  "id": "RS22194",
  "type": "CRS Report",
  "typeId": "REPORTS",
  "number": "RS22194",
  "active": false,
  "source": "EveryCRSReport.com, University of North Texas Libraries Government Documents Department",
  "versions": [
    {
      "source": "EveryCRSReport.com",
      "id": 340452,
      "date": "2005-07-15",
      "retrieved": "2016-04-07T19:38:50.015029",
      "title": "Federal Enterprise Architecture and Information Technology Management: A Brief Overview",
      "summary": "Congressional policymakers are concerned about potential inefficiencies and inefficacies in the\noperation of the federal government, particularly as it relates to decisions regarding information\ntechnology (IT) investments. These concerns have increased as federal IT spending has grown to\nmore than $60 billion annually. One approach being implemented to address this issue is the use of\nenterprise architecture (EA) planning across the federal government. An EA serves as a blueprint\nof the business operations of an organization, and the information and technology needed to carry\nout these functions. As an information technology management and planning tool, EA planning\nrepresents a business-driven approach to information technology management that emphasizes\ninteroperability and information sharing. The Federal Enterprise Architecture (FEA) was started in\n2002 by the Office of Management and Budget (OMB) and continues to be developed today. The\nFEA is composed of five reference models; Performance, Business, Service, Data, and Technical. \nEach of the reference models represent specific aspects of the FEA and provide a \"common\nlanguage\" for departments and agencies to use in developing common technology solutions. Some\nof the congressional oversight issues related to the FEA include, but are not limited to, ongoing\nupdates of the reference models, progress in aligning the EAs of individual departments with the\nFEA, and the role of the FEA in developing a second generation of e-government initiatives. This\nreport will be updated as events warrant.",
      "type": "CRS Report",
      "typeId": "REPORTS",
      "active": false,
      "formats": [
        {
          "format": "HTML",
          "encoding": "utf-8",
          "url": "http://www.crs.gov/Reports/RS22194",
          "sha1": "0fe58dfcfd520c40d6f7cf5ba5723325517d7474",
          "filename": "files/20050715_RS22194_0fe58dfcfd520c40d6f7cf5ba5723325517d7474.html",
          "images": null
        },
        {
          "format": "PDF",
          "encoding": null,
          "url": "http://www.crs.gov/Reports/pdf/RS22194",
          "sha1": "5e87f3df5c983b5c1debdb42a40ad49e0ca681b7",
          "filename": "files/20050715_RS22194_5e87f3df5c983b5c1debdb42a40ad49e0ca681b7.pdf",
          "images": null
        }
      ],
      "topics": []
    },
    {
      "source": "University of North Texas Libraries Government Documents Department",
      "sourceLink": "https://digital.library.unt.edu/ark:/67531/metadc818662/",
      "id": "RS22194_2005Jul14",
      "date": "2005-07-14",
      "retrieved": "2016-03-19T13:57:26",
      "title": "Federal Enterprise Architecture: A Brief Overview",
      "summary": null,
      "type": "CRS Report",
      "typeId": "REPORT",
      "active": false,
      "formats": [
        {
          "format": "PDF",
          "filename": "files/20050714_RS22194_add4d227e3cc5e4ca5a60568c16e2e8966f5cbf4.pdf"
        },
        {
          "format": "HTML",
          "filename": "files/20050714_RS22194_add4d227e3cc5e4ca5a60568c16e2e8966f5cbf4.html"
        }
      ],
      "topics": []
    }
  ],
  "topics": []
}