Product framing - DOI-ONRR/onrr.gov-site GitHub Wiki

Problem statement

Companies pay to produce natural resources on federal lands, Indian lands, and the Outer Continental Shelf. They need to access timely and accurate information to meet complex regulatory requirements. These requirements include reporting production and paying the required royalties and other revenues. The Office of Natural Resources Revenue collects, verifies, and disburses those revenues.

Native Americans and the public need to understand their revenues and ensure we meet our trust responsibilities. ONRR should provide access to resources and clear communication to help this understanding.

Our vision

We communicate the role of the Office of Natural Resources Revenue. We deliver trusted and easy to use information and customer service. This enables companies who lease federal and Indian lands to accurately report production and pay revenue due.

User types and scenarios

image

Reporters (payor/operator, large company, mom & pop company, 3rd party reporters, record title holder)

Logs on to systems, file reports, accesses old reports, submit payments, use reporting resources such as pricing info, handbooks, rules & regulations, reporter letters, reference lists & codes, etc

  • A new reporter comes to the site for the first time looking for how to get set up to start filing reports. They find a checklist of steps to take and the forms they need to fill out to gain system access. They also find a training class to sign up for and some videos to watch to get started.
  • The reporter has a OGOR report that is due next Friday and needs to file, so they go to onrr.gov to file the report. They have a question about the report, so they look for the contact information of the production representative at ONRR to call them.
  • The reporter needs to enter inventory adjustments to a past OGOR. They log onto the ONRR eCommerce portal to make these changes. The reporter refers to the production handbook to review how to report correctly.
  • The reporter receives a data request or an order to report and looks for procedures to respond to the letter and look at handbooks, well assignment lists, and their reports in Data Warehouse to determine whether they reported correctly.
  • The reporter has a 2014 report that is due next Friday and needs to file, so they go to onrr.gov to file the report. They have a question about the report, so they look for the contact information of the royalty representative at ONRR to call them.
  • The reporter needs to enter adjustments to a past 2014 for a different sales volume and sales value. They log onto the ONRR ecommerce portal to make these changes. The reporter refers to the reporting handbook and valuation guidance to review what the value should be and how to report correctly.
  • A royalty reporter is looking for an Indian Major Portion Oil Price for last month, so they go to onrr.gov to find a table. They need the most up-to-date price to calculate the royalty owed for the month.
  • The reporter has a P&R report that is due next Friday and needs to file, so they go to onrr.gov to file the report. They have a question about the report, so they look for the contact information of the royalty representative at ONRR to call them.
  • The reporter needs to enter adjustments to a past P&R. They log onto the ONRR ecommerce portal to make these changes. The reporter refers to the reporting handbook to review how to report correctly.

Subject Matter Expert

Content owners of specific webpages and responsible for managing content, updating data, requesting document updates, Indian outreach events etc.

  • An economist from the Market & Spatial Analytics team updates monthly NYMEX prices.
  • An employee from the Indian Outreach office posts new outreach events to the website.

Inquisitor

Someone wanting to learn about ONRR, new or prospective employee, interest in events/trainings, needing system access, troubleshooting error or compliance/enforcement actions after filing. ONRR customer service rep providing answers or sending information, or a journalist.

  • An internal employee from the Reference and Reporting Management (RRM) Production Team would like to prepare and conduct training for first time reporters. They use onrr.gov as a resource to guide reporters with instruction and other information.
  • A royalty team member gets a question from an industry reporter about how to report. The royalty team member goes to onrr.gov to find the answer and sends the reporter a link to the information.
  • A compliance representative notices an issue when conducting a review and notifies the reporter. Reporter contacts the rep and asks questions. Rep points the reporter to onrr.gov to information to answer the question.
  • Potential employee goes to onrr.gov to learn about the agency.
  • Journalist goes to onrr.gov to find out who is the contact for public relations to get a quote for an article.
  • Crude oil marketer goes to onrr.gov to download NYMEX prices to price oil.

ONRR’s Partners

STRAC auditors, sister agencies, IIMO & tribes, disbursement recipient, etc.

  • An allottee wants to attend an event or learn about what ONRR does for them.
  • A tribal leader wants to find out who to call with a problem they're having with one of their lessees.

Product goals

  • Industry can accurately report their production and pay their royalties due.
  • Industry is aware of laws, regulations, and policies that impact them.
  • Industry can get help troubleshooting problems they have when reporting or responding to compliance actions.
  • New industry reps can get help understanding how to report and pay.
  • Resource owners can ensure the trust responsibilities are being met.
  • Users can understand what ONRR does.

What we are not doing

  • Addressing issues with ONRR systems that are linked to from onrr.gov, such as eCommerce and Data Warehouse.
  • Replicating any data that is available on the Natural Resources Revenue Data portal.

Risks

Description How we might mitigate Criticality
Stale, inaccurate content.
  • Form a structure and content team with people from throughout ONRR to help with maintaining the content.
High
There are many people who are responsible for the content on the site and we need to ensure processes to keep the content up to date, consistent, accessible, and user-centered and to manage expectations for turnaround and vetting of content.
  • Create a content guide and review process.
High
Users not being able to find what they need.
  • Redesign the site to meet user needs.
High
A significant portion of the technical team members are term-limited or contractors, and the prospect of hiring new permanent, remote team members is unlikely.
  • Continue to train and pair with permanent ONRR team members to build their technical skills and confidence
  • Devise a long-term plan for ad-hoc technical support (contractors, etc).
  • Keep the scope of the site small but high-value, to minimize maintenance needs while demonstrating value to the org.
  • Continue to drive home the value of ONRR.gov to help build support for funding and staff.
  • Build the site to be sustainable and maintainable with minimal technical resources with a content management system.
High
Data Display team is short staffed and being pulled in several directions/having a lot of other responsibilities.
  • Positions need to be back-filled.
  • Taking on onrr.gov is taking resources from NRRD.
  • Team could also be pulled away to support FACA committees and other special projects.
High
The site doesn’t currently support version control, which hinders stakeholders from being able to review changes before going live, making it easy for errors to end up on the live site.
  • Put the site on GitHub to get version control.
High
Lack of version control makes it so that we can’t get historical states of the site, which puts the ability for FOIA requests to be fulfilled at risk.
  • Put the site on GitHub to get version control.
High
The site is not currently open source and on BSEE servers and needs to be moved to modern technology under ONRR control.
  • Make the site open source and get it in ONRR control.
Medium
Lack of IT support for in-house technology expertise, open source development, and agile/iterative processes.
  • Make sure our team is involved in other IT projects that affect our work (e.g. data governance)
  • Continue building alliances and relationships across silos.
  • Continue to seek creative compromises with IT.
Medium
Department and ONRR leadership priorities sometimes conflict with researched user needs, which affect design decisions.
  • Outreach and education about user-centered design.
  • Find creative ways to design for both.
  • Create content guide and review processes.
Medium
Silos at ONRR make collaboration challenging and could reduce support for the project.
  • Find small, low-risk opportunities to collaborate and build trust, and build upon those (e.g. trainings/brown bags, joint user research, etc)
  • Advocate to leadership for more collaboration opportunities across parts of the org.
Medium
User-centered design is challenging when it’s difficult to find users to participate in research when government legal requirements create barriers.
  • Constant cold emailing potential participants.
  • Finding groups where our potential users congregate to partner with.
Low
The site is linked to eCommerce and Data Warehouse and we have no control over those systems.
  • Open lines of communication with people who control those systems and share the feedback we’re getting from users.
Low
We don’t have a consistent way for stakeholders to request changes to the site. They currently come in via email, ServiceNow, and GitHub.
  • Outreach about GitHub and communication as people send things through other channels.
Low
⚠️ **GitHub.com Fallback** ⚠️