Access Official Technical PDF

Share Summary:LinkedInEmail

Research data reporting is most useful when it helps decision-makers distinguish activity, commitments and actual spending. The University of Washington’s FY2017 Annual Report on Research provides a detailed example: it reports proposals, awards, direct expenditures and sponsored-project employment as separate views of a large, multi-source portfolio. For industrial automation leaders, the report’s practical lessons are about information design—clear definitions, consistent source categories and transparent methods—not about research funding as a direct model for plant operations.

Research data reporting starts with clear measures

The report presents three financial measures that answer different questions. Proposals describe requests for funding; awards record amounts associated with award letters received and processed during the fiscal year; and expenditures show funding spent during the year. In FY2017, the University of Washington reported 5,892 proposals requesting $4.91 billion, total awards of about $1.63 billion, and direct expenditures of about $1.03 billion.

These figures are not interchangeable. A proposal is not a confirmed award, and an award total is not the same as expenditure in a given year. Keeping the measures separate helps readers avoid treating pipeline activity, funding decisions and spending as though they represented the same stage of work. The same discipline is valuable in operational reporting: define what each metric counts and the time period it covers before comparing results.

Funding source analysis needs consistent categories

The FY2017 report divides funding and expenditure information into federal and non-federal sources, then provides detail by sponsor, school or college, and department. Federal sponsors accounted for about $1.03 billion of awards, or 63.48 percent of the total. Non-federal sponsors accounted for about $595 million, or 36.52 percent. A ten-year, $280 million foundation award explains much of the elevated non-federal award total in that year.

That context matters. Without it, a reader might interpret the year’s increase as a broad shift across all non-federal funding. The report makes the exceptional award visible alongside the underlying categories, allowing readers to interpret the total more carefully. In any complex reporting environment, a large one-time item or unusual timing effect can distort a headline figure unless it is identified and explained.

The report also shows that awards and spending can have different sponsor profiles. Federal direct expenditures were about $792 million in FY2017, while non-federal direct expenditures were about $229 million. These expenditure figures describe activity during the fiscal year, not the same measure as awards processed during that period. Comparing both views helps readers understand the portfolio from more than one angle.

Align data across the reporting lifecycle

One change described in the report was sourcing expenditure sponsor data from the electronic proposal system, SAGE. The stated purpose was to align sponsor information across proposals, awards and expenditures and to improve tracking of originating sponsors. This is a data-governance choice: when related reports use consistent source categories, it becomes easier to follow information across stages.

For industrial automation teams, the general principle is to define shared categories and identifiers across connected systems wherever practical. If different reports classify the same source or activity differently, comparisons become harder and reconciliation takes more effort. Consistent data structures do not remove the need to understand each metric, but they can make it clearer how records relate.

Make methodology and exceptions visible

The annual report notes methodological changes and provides appendices explaining definitions and data sources. It also documents known limitations. For example, expenditures with a “Not Applicable” sponsor type were attributed to projects established before SAGE was created in 2006. Rather than silently blending this history into the main sponsor categories, the report identifies the reason for the classification.

Historical comparisons also require context. The report explains that additional federal funding under the American Recovery and Reinvestment Act affected award levels in FY2010 and FY2011. It notes that the timing of federal sequestration affected FY2013 and FY2014 totals, and that a large foundation award influenced FY2017. These explanations help readers distinguish underlying patterns from changes caused by timing, policy or exceptional awards.

Reporting design matters, too. The report describes regrouping schedules, adding page headers and revising graphs to improve navigation and visualization. It also added guidance for recreating annual-report information using financial and research data cubes. Together, these changes support both readable summary views and access to the underlying data logic.

Practical lessons for technical decision-makers

Although the report concerns university-sponsored research, its reporting practices translate into useful questions for teams overseeing complex operations:

  • Are metrics defined clearly? Specify what is counted, the reporting period and whether a figure represents requests, commitments or actual activity.
  • Do categories remain consistent? Align source labels and identifiers across the systems and reports that track related processes.
  • Are exceptions explained? Flag one-time events, historical records and timing effects that could change how totals are understood.
  • Can readers trace the method? Document data sources, definitions and calculation rules so reports can be interpreted and reproduced.

These practices are relevant to industrial automation because operational decisions depend on information assembled across systems, teams and time periods. The report does not prescribe an automation architecture; its value is in demonstrating how disciplined definitions and transparent context make a complex portfolio easier to assess.

Conclusion

The University of Washington’s FY2017 report illustrates that reliable reporting involves more than publishing totals. It separates proposals, awards and expenditures, aligns sponsor data across reporting stages, and explains methodological changes and unusual influences on the results. For technical decision-makers, the practical takeaway is straightforward: build reports around clearly defined measures, consistent categories and traceable methods. That foundation makes complex information easier to compare and more useful for planning.

Access Official Technical PDF

About The Author