Federal Information Archictecture and Integrated Retrieval
Federal agencies need to collect and organize data in a way that supports better retrieval to improve regulatory oversight and public use. One of the best ways to make that happen is to conceptualize the data holdings of each agency as a unique part of a single integrated Federal database. By placing data in standardized internet-accessible databases that are suitably organized and accessible through standard queries, data could be simultaneously retrieved from multiple agencies with a single query.
Each agency should have a "data jurisdiction" for the kinds of data they collect that they will then make available to other federal agencies, thus reducing redundancy and increasing quality and effectiveness.
One powerful way to accomplish that would be to rely on "master ID numbers" for important regulated entities. For example, there should be a master "Corporate ID Number" used by all federal agencies when they collect data from any company. A number already exists that could fulfill that purpose - the Federal "Employer ID Number, or EIN, used to collect and report Social Security taxes. A regulation should be issued to require that any corporate data reported to the federal government be tagged with its EIN.
Similarly, a "Federal Facility ID" should be created to uniquely identify any physical entity, such as an oil refinery. Such a number does not yet exist, but EPA is specially positioned to introduce such a number and make it widely available. Other agencies, including Homeland Security, Commerce, and Defense, require such a number and could rely on EPA to register and collect such data.
Such an architecture and retrieval mechanism would significantly improve agency regulatory oversight and improve government accountability. A study several years ago under the auspices of the National Academy of Public Administration showed that the Facility ID Number alone could save over $1 Billion a year.