{ "id": "R40150", "type": "CRS Report", "typeId": "REPORTS", "number": "R40150", "active": false, "source": "EveryCRSReport.com, University of North Texas Libraries Government Documents Department", "versions": [ { "source": "EveryCRSReport.com", "id": 414952, "date": "2010-06-04", "retrieved": "2016-04-07T01:38:32.133763", "title": "A Federal Chief Technology Officer in the Obama Administration: Options and Issues for Consideration", "summary": "In November 2007, Senator Barack Obama announced his intention, if elected President, to appoint a federal chief technology officer (CTO). He also identified several specific areas of responsibility of the CTO including transparency of government operations, computer and network security (sometimes referred to as cybersecurity), identification and adoption of best technologies and practices by federal agencies, and interoperability of emergency communications technologies for first responders. \nOn April 18, 2009, President Obama appointed Virginia Secretary of Technology Aneesh P. Chopra to serve in the newly created position of federal chief technology officer. In announcing the appointment, the President indicated that Mr. Chopra would undertake roles beyond what might be considered traditional CTO responsibilities. As the President described them, these roles include promoting technological innovation to help the United States create jobs, reduce health care costs, protect the homeland, and address other national goals. Mr. Chopra serves as assistant to the President and chief technology officer, as well as associate director for technology in the White House Office of Science and Technology Policy. Under a provision of Executive Order 13500, issued on February 5, 2009, he also serves as a member of the White House Domestic Policy Council in his capacity as assistant to the President and CTO.\nThe CTO may face a variety of challenges in executing the mission envisioned by the President. Among the early challenges will be negotiating domains of responsibilities within the White House and with executive branch agencies that have overlapping missions. Some commentators have expressed concerns about the impact the creation of a CTO might have on existing offices and agencies with respect to the allocation and coordination of authorities and responsibilities. Other commentators have asserted that a high-level CTO could serve as an advocate for technological innovation and foster increased knowledge sharing among federal agencies to more effectively implement information technology solutions to meet disparate mission requirements. Mr. Chopra\u2019s appointment as both CTO and associate director for technology at OSTP may address, in part, questions related to mission alignment, coordination, and integration. Since assuming his dual roles, Mr. Chopra has publicly engaged in discussions covering a wide range of technology policy-related areas, including research and development, innovation, open government, government performance, education, science and engineering workforce, health care information technology, broadband, patent reform, and net neutrality.\nCongress faces President Obama\u2019s appointment of Mr. Chopra and the President\u2019s stated plans for the federal CTO. There is currently no formal position description for the CTO. Accordingly, the official duties of the CTO remain largely undefined. Congress may elect to provide a statutory foundation for the CTO, define the roles and authorities of the CTO, authorize and appropriate funds, provide for oversight, and address other aspects of the position.", "type": "CRS Report", "typeId": "REPORTS", "active": false, "formats": [ { "format": "HTML", "encoding": "utf-8", "url": "http://www.crs.gov/Reports/R40150", "sha1": "6710691adb51db307e556ba1e1ac2adea1ad14d9", "filename": "files/20100604_R40150_6710691adb51db307e556ba1e1ac2adea1ad14d9.html", "images": null }, { "format": "PDF", "encoding": null, "url": "http://www.crs.gov/Reports/pdf/R40150", "sha1": "ae307db83b7db0034196e7fd3a43b77b8040c9a6", "filename": "files/20100604_R40150_ae307db83b7db0034196e7fd3a43b77b8040c9a6.pdf", "images": null } ], "topics": [] }, { "source": "University of North Texas Libraries Government Documents Department", "sourceLink": "https://digital.library.unt.edu/ark:/67531/metadc627235/", "id": "R40150_2010Jan07", "date": "2010-01-07", "retrieved": "2015-06-15T14:46:40", "title": "A Federal Chief Technology Officer in the Obama Administration: Options and Issues for Consideration", "summary": "This report presents President Obama's vision for the chief technology officer (CTO) position. It also discusses the potential scope of the position's duties, articulates organizational precedents and challenges for the CTO, reviews some of the activities undertaken by Aneesh Chopra during his tenure as CTO, and identifies issues Congress may choose to consider if it opts to exert oversight or to develop legislation to create the position and/or office of the CTO.", "type": "CRS Report", "typeId": "REPORT", "active": false, "formats": [ { "format": "PDF", "filename": "files/20100107_R40150_5876cfef749b17f64c1b39f6ed210836fd74b45f.pdf" }, { "format": "HTML", "filename": "files/20100107_R40150_5876cfef749b17f64c1b39f6ed210836fd74b45f.html" } ], "topics": [ { "source": "LIV", "id": "Executive departments", "name": "Executive departments" }, { "source": "LIV", "id": "Executive reorganization", "name": "Executive reorganization" }, { "source": "LIV", "id": "Presidential appointments", "name": "Presidential appointments" }, { "source": "LIV", "id": "Technology", "name": "Technology" }, { "source": "LIV", "id": "Technology policy", "name": "Technology policy" } ] }, { "source": "University of North Texas Libraries Government Documents Department", "sourceLink": "https://digital.library.unt.edu/ark:/67531/metadc795406/", "id": "R40150_2009Jan21", "date": "2009-01-21", "retrieved": "2016-01-13T14:26:20", "title": "A Federal Chief Technology Officer in the Obama Administration: Options and Issues for Consideration", "summary": "This report addresses issues related to the potential scope of duties and authorities of a CTO, as well as other issues Congress may choose to consider if it opts to exert oversight or to develop legislation to create the position and/or office of a CTO.", "type": "CRS Report", "typeId": "REPORT", "active": false, "formats": [ { "format": "PDF", "filename": "files/20090121_R40150_9c869412bb55a4cbf156f590e7a17bf86e0f00f5.pdf" }, { "format": "HTML", "filename": "files/20090121_R40150_9c869412bb55a4cbf156f590e7a17bf86e0f00f5.html" } ], "topics": [ { "source": "LIV", "id": "Executive departments", "name": "Executive departments" }, { "source": "LIV", "id": "Executive reorganization", "name": "Executive reorganization" }, { "source": "LIV", "id": "Presidential appointments", "name": "Presidential appointments" }, { "source": "LIV", "id": "Technology", "name": "Technology" }, { "source": "LIV", "id": "Technology policy", "name": "Technology policy" } ] } ], "topics": [ "National Defense", "Science and Technology Policy" ] }