Permalink
Find file
Fetching contributors…
Cannot retrieve contributors at this time
166 lines (151 sloc) 11.6 KB
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Slash Digital Strategy Generator</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<!-- Le styles -->
<link href="assets/css/bootstrap.css" rel="stylesheet">
<style>
body { margin-top: 60px; margin-bottom: 60px; }
h1 { text-align: center; margin-bottom: 25px; }
h3, h4 {margin-bottom: 25px; }
#import-upload {display:none; text-align: center; }
#import-prompt {text-align: center; font-style: italic; }
#upload-form {margin: 0;}
.due { float:right; color: #aaa; margin-top: 7px; font-style: italic; }
.border-top { border-top: 1px solid #ccc; padding-top: 20px; }
footer { text-align: center; font-style: italic; color: #ccc;}
</style>
<link href="assets/css/bootstrap-responsive.css" rel="stylesheet">
<!-- Le HTML5 shim, for IE6-8 support of HTML5 elements -->
<!--[if lt IE 9]>
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
</head>
<body>
<div class="container">
<!-- ************ BEGIN BARE-BONES HTML; COPY STARTING HERE IF ADDING TO A CMS ************ -->
<h1>Digital Government Strategy Report for the Federal Communications Commission</h1>
<h2>2.1. Engage with customers to identify at least two existing major customer-facing services that contain high-value data or content as first-move candidates to make compliant with new open data, content, and web API policy.</h2>
<strong>Overall Status</strong>: completed<br />
<h3>2.1.1. Paragraph on customer engagement approach</h3>
<strong>Paragraph on customer engagement approach</strong>: The Federal Communications Commission uses the Federal Communications Bar Association, direct public engagement through social media, and targeted outreach in the form of workshops and meetings for new applications to provide significant feedback to its Digital Strategy, Web and new application development teams. For all of our new web based applications or retooling of web based applications, we commonly follow rules in the Administrative Procedures Act for announcing applications via Public Notice. Often times these Public Notices engage the public to seek comment on these new or retooled applications. Our approach has been successful in that we have received and taken into consideration significant feedback on new application architecture, design and enhancements.<br />
<h3>2.1.2. Prioritized list of systems (datasets)</h3>
<strong>System Name</strong>: Broadcast Public Inspection File<br />
<strong>System Description</strong>: For decades, the public file for each station has been kept at the station’s main studio in paper form (or more recently in electronic form at some stations) and made available during normal business hours. Relying on the advantages of current technology, however, the Commission has now changed its rules to require almost all of this public file information for television stations to be posted online at this site.<br />
<strong>System Scope</strong>: both<br />
<strong>Main Customer</strong>: Public<br />
<hr > <strong>System Name</strong>: License View<br />
<strong>System Description</strong>: Spectrum is a national resource. License View provides information on over 3 million FCC issued licenses for use of the nation's airwaves and other purposes.<br />
<strong>System Scope</strong>: both<br />
<strong>Main Customer</strong>: Public<br />
<hr ><h2>7.1. Engage with customers to identify at least two existing priority customer-facing services to optimize for mobile use.</h2>
<strong>Overall Status</strong>: completed<br />
<h3>7.1.1. Paragraph on customer engagement approach</h3>
<strong>Paragraph on customer engagement approach</strong>: The Federal Communications Commission uses the Federal Communications Bar Association, direct public engagement through social media, and targeted outreach in the form of workshops and meetings for new applications to provide significant feedback to its Digital Strategy, Web and new application development teams. For all of our new web based applications or retooling of web based applications, we commonly follow rules in the Administrative Procedures Act for announcing applications via Public Notice. Often times these Public Notices engage the public to seek comment on these new or retooled applications. Our approach has been successful in that we have received and taken into consideration significant feedback on new application architecture, design and enhancements.<br />
<h3>7.1.2. Prioritized list of systems (datasets)</h3>
<strong>System Name</strong>: fcc.gov<br />
<strong>System Description</strong>: The entire fcc.gov experience will be a mobile ready application this fall.<br />
<strong>System Scope</strong>: both<br />
<strong>Main Customer</strong>: Stakeholders and Public<br />
<hr > <strong>System Name</strong>: National Broadband map<br />
<strong>System Description</strong>: The National Broadband Map (NBM) is a searchable and interactive website that allows users to view broadband availability across every neighborhood in the United States. The NBM was created by the National Telecommunications and Information Administration (NTIA), in collaboration with the Federal Communications Commission (FCC), and in partnership with 50 states, five territories and the District of Columbia. The NBM is part of NTIA's State Broadband Initiative. The NBM is updated approximately every six months and was first published on February 17, 2011.<br />
<strong>System Scope</strong>: both<br />
<strong>Main Customer</strong>: Public<br />
<hr ><h2>4.2. Establish an agency-wide governance structure for developing and delivering digital services</h2>
<strong>Overall Status</strong>: in-progress<br />
<strong>Link to governance document</strong>: <br />
<h3>4.2.1. Goals</h3>
<strong>Goal</strong>: <br />
<strong>Measure</strong>: <br />
<strong>Target completion date</strong>: <br />
<h3>4.2.3. Set specified agency-wide policies and standards</h3>
<strong>Policy or standard</strong>: In general, the FCC makes public data its uses for policy decisions. A Public Notice seeking comment on its Data Innovation Initiative set in motion this practice.<br />
<strong>Overall Status</strong>: in-progress<br />
<hr ><h2>5.2. Develop an enterprise-wide inventory of mobile devices and wireless service contracts</h2>
<strong>Overall Status</strong>: completed<br />
<h3>5.2.1. Develop mobile device inventory</h3>
<strong>Link to inventory</strong>: held internally<br />
<h3>5.2.2. Develop wireless service contract inventory</h3>
<strong>Bureau/Component</strong>: Office of the Managing Director<br />
<strong>Mobile Device Inventory Status</strong>: in-progress<br />
<strong>Wireless Service Contract Inventory Status</strong>: in-progress<br />
<hr ><h2>8.2. Implement performance and customer satisfaction measuring tools on all .gov websites</h2>
<strong>Overall Status</strong>: not-started<br />
<h3>8.2.1. Implement performance measurement tool</h3>
<strong>Describe Implementation</strong>: Currently the FCC is investigating using several tools for this analysis, including ForeSee.<br />
<h3>8.2.2. Implement customer satisfaction tool</h3>
<strong>Describe Implementation</strong>: <br />
<h2>1.2. Ensure all new IT systems follow the open data, content, and web API policy and operationalize agency.gov/developer pages</h2>
<strong>Overall Status</strong>: in-progress<br />
<h3>1.2.1. Document policy for architecting new IT systems for openness by default</h3>
<strong>URL of policy</strong>: <br />
<strong>Describe policy</strong>: <br />
<h3>1.2.2. Operationalize /developer page</h3>
<strong>URL of page</strong>: http://www.fcc.gov/developers<br />
<h2>2.2. Make high-value data and content in at least two existing, major customer-facing systems available through web APIs, apply metadata tagging and publish a plan to transition additional high-value systems</h2>
<strong>Overall Status</strong>: in-progress<br />
<h3>2.2.1. Make 2+ systems (datasets) available via web APIs with metadata tags</h3>
<strong>URL of page</strong>: https://stations.fcc.gov/developer/<br />
<hr > <strong>URL of page</strong>: http://apps.fcc.gov/accessibilityclearinghouse/developers.html<br />
<hr > <strong>URL of page</strong>: http://www.fcc.gov/developers/census-block-conversions-api<br />
<hr > <strong>URL of page</strong>: http://www.fcc.gov/developers/fcc-content-api<br />
<hr > <strong>URL of page</strong>: http://www.fcc.gov/developers/consumer-broadband-test-api<br />
<hr > <strong>URL of page</strong>: http://apps.fcc.gov/cgb/form499/docs/index.htm<br />
<hr > <strong>URL of page</strong>: http://www.fcc.gov/developers/license-view-api<br />
<hr > <strong>URL of page</strong>: http://www.fcc.gov/developers/spectrum-dashboard-api<br />
<hr > <strong>URL of page</strong>: http://broadbandmap.gov/developer<br />
<hr ><h3>2.2.2. Publish plan on future activity</h3>
<h2>5.3. Evaluate the government-wide contract vehicles in the alternatives analysis for all new mobile-related procurements</h2>
<strong>Overall Status</strong>: in-progress<br />
<strong>Paragraph on policy</strong>: We are already in the process of acquiring new mobile device and service contracts, but will evaluate the new government wide contracting vehicles when they become available to determine whether additional efficiencies can be realized.
<br />
<h2>6.3. Ensure all new digital services follow digital services and customer experience improvement guidelines</h2>
<strong>Overall Status</strong>: in-progress<br />
<strong>Paragraph on policy</strong>: We will evaluate the new guidelines and develop an implementation plan as soon as the guidance is made available to agencies.
<br />
<h2>7.2. Optimize at least two existing priority customer-facing services for mobile use and publish a plan for improving additional existing services</h2>
<strong>Overall Status</strong>: completed<br />
<strong>URL of plan</strong>: <br />
<h3>7.2.1. Report on services</h3>
<p><em>Last updated August 8, 2012 at 1:43 pm</em></p>
<!-- ************ END BARE-BONES HTML; STOP COPYING HERE IF ADDING TO A CMS ************ -->
<footer>
Generator Version 1.1 </footer>
</div> <!-- /container -->
<!-- Le javascript
================================================== -->
<!-- Placed at the end of the document so the pages load faster -->
<script src="assets/js/jquery.js"></script>
<script src="assets/js/bootstrap-transition.js"></script>
<script src="assets/js/bootstrap-alert.js"></script>
<script src="assets/js/bootstrap-modal.js"></script>
<script src="assets/js/bootstrap-dropdown.js"></script>
<script src="assets/js/bootstrap-scrollspy.js"></script>
<script src="assets/js/bootstrap-tab.js"></script>
<script src="assets/js/bootstrap-tooltip.js"></script>
<script src="assets/js/bootstrap-popover.js"></script>
<script src="assets/js/bootstrap-button.js"></script>
<script src="assets/js/bootstrap-collapse.js"></script>
<script src="assets/js/bootstrap-carousel.js"></script>
<script src="assets/js/bootstrap-typeahead.js"></script>
<script>
$('#import-toggle').click(function(e){
e.preventDefault();
$('#import-upload').fadeToggle();
});
$('#import-upload').change( function(){ $('#upload-form').submit() });
//add multiple fields
$('.add').live( 'click', function(e) {
e.preventDefault();
var fields = $(this).siblings('.fields:first').clone().addClass( 'border-top' );
$.each( fields, function( key, field ) {
$(field).find( 'input' ).val('');
});
$(this).before( fields );
return false;
})
</script>
</body>
</html>