Nuclear Regulatory Commission (NRC) Digital Strategy
View as HTML View as XML View as JSON
Generated 05-23-2013
1.2.2 Operationalize /developer page 05-23-2013
  • URL of page: Not yet available
2.1.2 Prioritized list of systems (datasets) 08-21-2012

  • System Name: Reactor Operating Status Reports
  • System Description: A web-based system that allows the NRC to report on the operating status and power output of commercial power reactors located within the continental United States
  • System Scope: both
  • Main Customer: General public and agency stakeholders
  • Unique Investment Identifier: 429-000002005

  • System Name: Power Reactor Daily Event Reports
  • System Description: A web-based system that allows the NRC to report on the daily events and activities occurring at commercial power reactors located within the continental United States

  • System Name: Operating Reactor Inspection Reports
  • System Description: A web-based system that allows the NRC to report on observations and findings of inspections occurring at commercial power reactors located within the continental United States
  • Unique Investment Identifier: 429-000001014

  • System Name: Part 21 (Component Defect Reports)
  • System Description: A web-based system that allows the NRC to report on licensed facilities, activities, or basic component that fail to comply with NRC regulations

  • System Name: Public Affairs Daily News Releases
  • System Description: A web-based system that allows the NRC to communicate with the public daily on our regulatory activities and events
  • Unique Investment Identifier: 429-000002070
2.2.2 Make 2+ systems (datasets) available via web APIs with metadata tags 05-23-2013

  • Name of system: Not yet available
  • Description of system: The NRC uses web analytics to determine the most requested official agency information to further enhance the delivery of that information via mobile solution and web API's. Additional inputs to identify, scope, and prioritize other opportunities are obtained by reaching out to stakeholders across functional, programmatic, and geographic areas. The opportunities are prioritized using the following factors: strategic alignment, opportunity scope, efficiencies generated, solution complexity, development time, enterprise applicability, and implementation costs. The top mobile opportunities will be implemented by the agency. The NRC has leveraged our existing IT/IM processes and governance structure to ensure that the Digital Government Strategy (DGS) is addressed when considering new or modernized digital services. The DGS has been added as a requirement in the NRC’s Project Management Methodology (PMM) to ensure the solution architecture complies with the OMB policies. Future Plans will be noted in the agency’s Enterprise Roadmap. OMB reviewed and endorsed the NRC’s prioritized list of systems and proposed customer engagement approach [Milestone 2.1]. (For details, see Taking the Next Step, http://www.nrc.gov/public-involve/open/digital-government/roadmap.html#next-step. Customer feedback and related NRC responses are available in comments on the related Blog posting, http://public-blog.nrc-gateway.gov/2012/08/22/taking-the-next-step-building-a-21st-century-digital-government/#comments.) On October 22, 2012, the NRC confirmed that these systems (data feeds) are targeted to be made available via web APIs by May 23, 2013. In addition, on October 31, we published an article, entitled “Digital Government and Technology Enhancements,” in the NRC Reporter (our staff newsletter) to provide staff with an update on the status of the NRC’s Digital Government program and an overview of the work being done to leverage our current infrastructure. The article also invited staff to share their thoughts on systems (data feeds) that should be given priority to be made available via web APIs. Staff ideas will aid in development of our plan for future activity. On December 4, 2012, we responded to a request for comments on the draft Open Data policy. Implementation instructions for 12-month agency deliverables have been deferred to January 2013. On February 11, 2013, we released an API for Web-Based ADAMS (WBA), which is ahead of the May 23, 2013 deliverable date.
  • Description of system: OMB reviewed and endorsed the NRC’s prioritized list of systems and proposed customer engagement approach [Milestone 2.1]. (For details, see Taking the Next Step, http://www.nrc.gov/public-involve/open/digital-government/roadmap.html#next-step. Customer feedback and related NRC responses are available in comments on the related Blog posting, http://public-blog.nrc-gateway.gov/2012/08/22/taking-the-next-step-building-a-21st-century-digital-government/#comments.) On October 22, 2012, the NRC confirmed that these systems (data feeds) are targeted to be made available via web APIs by May 23, 2013. In addition, on October 31, we published an article, entitled “Digital Government and Technology Enhancements,” in the NRC Reporter (our staff newsletter) to provide staff with an update on the status of the NRC’s Digital Government program and an overview of the work being done to leverage our current infrastructure. The article also invited staff to share their thoughts on systems (data feeds) that should be given priority to be made available via web APIs. Staff ideas will aid in development of our plan for future activity. On December 4, 2012, we responded to a request for comments on the draft Open Data policy. Implementation instructions for 12-month agency deliverables have been deferred to January 2013.
  • Description of system: OMB reviewed and endorsed the NRC’s prioritized list of systems and proposed customer engagement approach [Milestone 2.1]. (For details, see Taking the Next Step, http://www.nrc.gov/public-involve/open/digital-government/roadmap.html#next-step. Customer feedback and related NRC responses are available in comments on the related Blog posting, http://public-blog.nrc-gateway.gov/2012/08/22/taking-the-next-step-building-a-21st-century-digital-government/#comments.) On October 22, 2012, the NRC confirmed that these systems (data feeds) are targeted to be made available via web APIs by May 23, 2013. In addition, on October 31, we published an article, entitled “Digital Government and Technology Enhancements,” in the NRC Reporter (our staff newsletter) to provide staff with an update on the status of the NRC’s Digital Government program and an overview of the work being done to leverage our current infrastructure. The article also invited staff to share their thoughts on systems (data feeds) that should be given priority to be made available via web APIs. Staff ideas will aid in development of our plan for future activity. On December 4, 2012, we responded to a request for comments on the draft Open Data policy. Implementation instructions for 12-month agency deliverables have been deferred to January 2013. On February 11, 2013, we released an API for Web-Based ADAMS (WBA), which is ahead of the May 23, 2013 deliverable date.
  • Description of system: The NRC uses web analytics to determine the most requested official agency information to further enhance the delivery of that information via mobile solution and web API's. Additional inputs to identify, scope, and prioritize other opportunities are obtained by reaching out to stakeholders across functional, programmatic, and geographic areas. The opportunities are prioritized using the following factors: strategic alignment, opportunity scope, efficiencies generated, solution complexity, development time, enterprise applicability, and implementation costs. The top mobile opportunities will be implemented by the agency. The NRC has leveraged our existing IT/IM processes and governance structure to ensure that the Digital Government Strategy (DGS) is addressed when considering new or modernized digital services. The DGS has been added as a requirement in the NRC’s Project Management Methodology (PMM) to ensure the solution architecture complies with the OMB policies. Future Plans will be noted in the agency’s Enterprise Roadmap. OMB reviewed and endorsed the NRC’s prioritized list of systems and proposed customer engagement approach [Milestone 2.1]. (For details, see Taking the Next Step, http://www.nrc.gov/public-involve/open/digital-government/roadmap.html#next-step. Customer feedback and related NRC responses are available in comments on the related Blog posting, http://public-blog.nrc-gateway.gov/2012/08/22/taking-the-next-step-building-a-21st-century-digital-government/#comments.) On October 22, 2012, the NRC confirmed that these systems (data feeds) are targeted to be made available via web APIs by May 23, 2013. In addition, on October 31, we published an article, entitled “Digital Government and Technology Enhancements,” in the NRC Reporter (our staff newsletter) to provide staff with an update on the status of the NRC’s Digital Government program and an overview of the work being done to leverage our current infrastructure. The article also invited staff to share their thoughts on systems (data feeds) that should be given priority to be made available via web APIs. Staff ideas will aid in development of our plan for future activity. On December 4, 2012, we responded to a request for comments on the draft Open Data policy. Implementation instructions for 12-month agency deliverables have been deferred to January 2013. On February 11, 2013, we released an API for Web-Based ADAMS (WBA), which is ahead of the May 23, 2013 deliverable date. This API also provided access to the Part 21 Reports API and the Operating Reactor Inspection Reports API. Sample API queries for these interfaces are as follows: •ADAMS API Sample Query (http://adams.nrc.gov/wba/services/search/advanced/nrc?q=(mode:sections,sections:(filters:(public-library:!t),properties_search_any:!(!(DocumentType,ends,'Enforcement+Action','')),single_content_search:'Gamma+Knife'))&qn=New&tab=content-search-pars&s=PublishDatePARS&so=ASC) •Part 21 Reports API Sample Query (http://adams.nrc.gov/wba/services/search/advanced/nrc?q=(mode:sections,sections:(filters:(public-library:!t),properties_search:!(!(DocumentType,ends,'Part+21+Correspondence',''),!(AuthorAffiliation,infolder,NRC/NRR,'')),single_content_search:'safety+valve'))&qn=New&tab=content-search-pars&s=$size&so=DESC) •Operating Reactor Inspection Reports API Sample Query (http://adams.nrc.gov/wba/services/search/advanced/nrc?q=(mode:sections,sections:(filters:(public-library:!t),properties_search:!(!(DocumentType,infolder,'inspection+report',''),!(DocketNumber,infolder,'05000',''),!(AuthorAffiliation,infolder,NRC/NRR,'')),single_content_search:'safety+valve'))&qn=New&tab=content-search-pars&s=$size&so=DESC) On May 15, 2013, we published our Web API For Developers (http://www.nrc.gov/developer.html) page, which includes a Developer's Guide (http://www.nrc.gov/site-help/developers/wba-api-developer-guide.pdf) for all three APIs listed above.
5.2.1 Develop wireless and mobile inventory 11-23-2012

  • Bureau/Component: Nuclear Regulatory Commission
  • Inventory Status: completed
7.1.2 Prioritized list of systems (datasets) 08-21-2012

  • System Name: Public Meeting Feedback System
  • System Description: A web-based system that allows the NRC to collect public meeting feedback from meeting attendees
  • System Scope: external
  • Main Customer: General public and agency stakeholders
  • Unique Investment Identifier: N/A

  • System Name: Top 5 Most-Accessed Agency Web Pages
  • System Description: A web-based system that allows the NRC to communicate with the public on our regulatory activities and events
  • System Scope: both
  • Unique Investment Identifier: 429-000002070

  • System Name: Regulatory Information Conference (RIC)
  • System Description: The NRC plans to implement the agency’s first mobile solution for the 2013 RIC, which will be held on March 12 – 14. This solution will allow RIC attendees to access the conference agenda and download conference publications from their own mobile devices. The solution will also enhance the attendees’ information access experience by incorporating the use of quick response (QR) codes throughout the conference facility (for details, see p. 2 of the NRC’s Customer Service Plan, http://www.nrc.gov/public-involve/open/customer-service/nrc-customer-service-plan.pdf).

  • System Name: Bring Your Own Device (BYOD)
  • System Description: Web-based access to NRC email, calendaring, and contacts on personally owned mobile devices.
  • System Scope: internal
  • Main Customer: NRC staff
  • Unique Investment Identifier: 1012A-J1500 (ITISS)
7.2.1 Report on services 05-23-2013

  • Service Name: Not yet available

  • Service Name: To provide customers with the opportunity to comment on proposed choices of services to optimize for mobile use, we will use our social media facilities (http://www.nrc.gov/public-involve/open/social-media.html). We have used Twitter and Blog posts in the past, to advise customers of specific initiatives and to solicit their feedback. For example, we used this approach to obtain feedback as we worked to publish the Addendum to our Open Government Plan and in developing our Customer Service Plan. Provided OMB with prioritized list of services and proposed customer engagement approach on August 6, 2012. Invited the public to Tell Us Your Thoughts (http://www.nrc.gov/public-involve/open/digital-government/your-thoughts.html)through the NRC Blog, a web-based comment form, traditional mail, email, phone, or fax. Engaged customers with a Blog posting (http://public-blog.nrc-gateway.gov/2012/08/22/taking-the-next-step-building-a-21st-century-digital-government/) and related “tweet” on August 22, 2012. Also used our RSS Feeds (http://www.nrc.gov/public-involve/listserver.html#rss) on August 15 and 22, 2012, to notify site visitors of the opportunity to provide feedback. In addition, on October 31, we published an article, entitled “Digital Government and Technology Enhancements,” in the NRC Reporter (our staff newsletter) to provide staff with an update on the status of the NRC’s Digital Government program and an overview of the work being done to leverage our current infrastructure. The article also invited staff to share their thoughts on services that should be given priority to be optimized for mobile use. Staff ideas will aid in development of our report on services.

  • Service Name: OMB reviewed and endorsed the NRC’s prioritized list of services and proposed customer engagement approach [Milestone 7.1]. (For details, see Taking the Next Step, http://www.nrc.gov/public-involve/open/digital-government/roadmap.html#next-step. Customer feedback and related NRC responses are available at http://public-blog.nrc-gateway.gov/2012/08/22/taking-the-next-step-building-a-21st-century-digital-government/#comments, in connection with the related Blog posting, http://public-blog.nrc-gateway.gov/2012/08/22/taking-the-next-step-building-a-21st-century-digital-government/.) On October 22, 2012, the NRC confirmed that these customer-facing services are targeted to be optimized for mobile use by May 23, 2013. The NRC will also publish a plan for improving additional existing services by the scheduled date. Then, on January 23, 2013, we added mobile services in support of the 2013 Regulatory Information Conference (RIC, http://www.nrc.gov/public-involve/conference-symposia/ric/) to the list of mobile services previously identified to be available by May 23, 2013. We also augmented the list to include services to support web-based staff access to email, calendaring, and contacts using personally owned mobile devices. This replaced the existing item to provide a mobile optimization for the top 5 most-accessed agency web pages. Also, on October 31, we published an article, entitled “Digital Government and Technology Enhancements,” in the NRC Reporter (our staff newsletter) to provide staff with an update on the status of the NRC’s Digital Government program and an overview of the work being done to leverage our current infrastructure. The article also invited staff to share their thoughts on services that should be given priority to be optimized for mobile use. Staff ideas will aid in development of our report on services. In addition, on December 4, 2012, we responded to a request for comments on the draft Open Data policy. Implementation instructions for 12-month agency deliverables have been deferred to January 2013.