Johns Hopkins University
Whiting School of Engineering
Research Intelligence
Expertise, funding, analytics, and strategy for the Whiting School of Engineering.
Open a workflow
Loading starting points...
Discover live opportunities or bring your own solicitation for faculty matching.
Expertise, funding, analytics, and strategy for the Whiting School of Engineering.
The dashboard combines datasets maintained by the WSE Office of Research and Translation (ORT), governed records from Hopkins enterprise systems, and selected external scholarly and funding-opportunity services. Each external publication source has a distinct role so identity evidence, catalog coverage, and citation-based metrics are not blended indiscriminately.
This page documents calculation definitions across the app. The underlying proposal, spend, sponsor, and gift figures load only for authorized internal users; the definitions below describe how those views are computed without exposing restricted values.
| Source | Provides | Coverage and cadence |
|---|---|---|
| WSE faculty roster and ORT reference datasets | Faculty roster, rank, department, center affiliations, bios, headshots, honors, expertise, and priority-area labels | Maintained release-by-release; currently -- active WSE-primary faculty (see Section 02) |
| OpenAlex | Author-ID-matched works, full-career faculty summaries, citations, h-index, and FWCI | Nightly automated refresh; 2017-present browser catalog plus full-career author summaries |
| DBLP | Reviewed computer-science conference and workshop proceedings that supplement the publication catalog | Nightly with the publication refresh; approved faculty PIDs only, deduplicated by DOI and title evidence |
| Semantic Scholar | Missing abstracts and paper-level provenance for already resolved OpenAlex or DBLP works | Nightly enrichment; does not replace OpenAlex citations, h-index, or FWCI |
| ORCID | Faculty identity verification, canonical researcher identifiers, and public JHU affiliation evidence | Nightly identity reconciliation; does not supply publication counts or impact metrics |
| Hopkins proposal records | Proposal submissions, asks, outcomes, pending pipeline, sponsors, and win rates | Restricted internal data refreshed through governed releases |
| Sponsored award and expenditure records | Awards, grant lifecycle, expenditures, sponsor relationships, and IO-level faculty and unit attribution | Restricted internal data refreshed through governed releases |
| Governed sponsor and gift reference feeds | Sponsor-code taxonomy and approved company gift or pledge details | Loaded only when an approved release feed is present; unavailable lanes remain hidden or explicitly disclosed |
| Grants.gov and SAM.gov | Grant, BAA, RFP, solicitation, and special-notice discovery for Opportunity Radar | Daily scheduled Cloudflare Worker writes normalized opportunity snapshots to R2 and preserves the last usable source data during transient failures |
Prepared but not currently active as live dashboard sources: the server-side Meltwater media-mentions integration awaits approved API entitlement and a service token; governed finance fund-source/F&A and commercialization feeds await source-owner approval and mapping. Reference datasets such as bios and award descriptions continue to be maintained independently.
The dashboard covers -- WSE-primary faculty. This is a deliberate subset of the broader WSE-affiliated population.
The Department of Environmental Health and Engineering (EHE) is a joint department between WSE and the Bloomberg School of Public Health (BSPH). Only WSE-primary EHE faculty are included in the roster; 39 BSPH-primary EHE faculty are excluded under a strict WSE-only policy. This brings EHE from a previous count of 69 down to 30. Other minor adjustments reflect retirements, departures, and corrections.
Department counts are derived from the current runtime faculty roster and shown in the filter sidebar. Centers (DSAI, ROSEI, INBT, LCSR, and others) are tracked separately as affiliations, not departments.
Faculty are mapped to WSE priority research areas from grants, publications, bios, center affiliations, and ORT review. Research is tagged against two overlapping classification schemes:
Expertise pages use these mappings for discovery and publication context. Financial area metrics use a separate IO-level attribution basis where available, so each financial dollar is assigned once while expertise membership can remain overlapping.
Home department is the primary academic department of record for each faculty member. Department views group faculty by home department, while center and institute views show faculty-level affiliations that can cross department lines.
The largest tracked WSE centers and institutes by faculty count are current center counts. Center faculty counts overlap by design because a faculty member can belong to several centers.
Center proposal and dollar summaries add each member's portfolio into that center context, so center totals overlap and do not sum to the school total. The former NTH grouping is reported under the Dean's Office rather than as a separate center.
The publication browser, Newsroom evidence, Collaboration Intelligence, and matcher context use a source-neutral catalog that combines OpenAlex works with conference proceedings from reviewed DBLP faculty profiles. Person-level career summaries and citation-based metrics remain OpenAlex-backed, while institutional-output views can separately highlight JHU-affiliated works.
Faculty remain searchable when a publication identity is incomplete. Only comparative publication-impact metrics are labeled under review when an OpenAlex record appears partial, stale, or below the minimum FWCI evidence threshold. DBLP and Semantic Scholar expand catalog evidence but do not make a faculty record eligible for OpenAlex impact ranking.
Honors and recognition views use the WSE Honorary Awards dataset. Recognitions are grouped by award type and displayed by faculty profile, award name, and recorded year where available.
Counts reflect recorded awards and may lag recent announcements or awards that have not yet been added to the source list.
Scorecard and Proposal Pipeline views organize proposal and award activity through the lifecycle from submission to pending decision, awarded outcome, and active spend. Dollar figures are shown in the relevant view context as proposal asks, awards, or expenditures, not as a single interchangeable measure.
Briefing, Scorecard, and Proposal Pipeline views use the same resolved-basis win-rate definition so PI, unit, center, sponsor, priority-area, and school views are comparable.
Win rate is additive only across mutually exclusive slices, such as departments by home unit and sponsors where source mapping is complete. Priority areas and centers overlap, so their win rates do not combine to the school rate and should not be summed or averaged.
Sponsor views show sponsor mix, concentration, and relationship depth across the funding portfolio. Sponsor groupings prefer source codes when available and fall back to name-based classification where codes are absent.
Corporate Engagement distinguishes direct awards from pass-through relationships. A company can appear as both a direct partner and a pass-through partner when corporate funding reaches WSE through a prime award.
Gift and philanthropy lanes are shown only when a governed per-company gift feed is loaded. Preview artifacts can illustrate the intended card layout, but live relationship totals should come from the runtime feed.
Priority-area analytics summarize rolling activity by school theme. L12M spend means expenditures over the trailing 12 months; trend compares the current period with a prior comparable period.
The "where this work happens" view uses faculty-activity rows. A PI appears under every department or center where they have non-zero activity, while per-location dollars use the activity at that location instead of duplicating the PI's full portfolio into every row.
Department Deep Dive combines two disclosed lenses: roster-attributed spend for faculty associated with the selected department wherever their awards are administered, and governed proposal metrics for the department record. Joint appointments can overlap across departments. Faculty momentum uses completed fiscal years, and award-runway signals include only lifecycle-active lead awards measured from the release snapshot.
The Metrics map compares faculty and units across funding, publication, sponsor, and portfolio signals. Axes are comparative within WSE rather than national benchmarks.
The BAA / RFP matcher runs server-side through the WSE AI Gateway. It first returns usable Top 10 matches, then opportunistically deep-reviews the top results. Scores and pitch language are decision-support signals that should be reviewed before external use.
Opportunity Radar is refreshed from Grants.gov and SAM.gov into R2 by a scheduled Cloudflare Worker. Grants.gov is the primary grant-opportunity source; SAM.gov is filtered to R&D-oriented BAA/RFP/solicitation notices using notice type, PSC/classification code, and R&D NAICS rules.
In production, the Cloudflare Pages app shell loads a broad data payload first. Internal analytics views request authenticated runtime data only after the user enters an authorized internal view. An inline HTML build is still generated for offline/internal review, but production data changes require rebuilding the R2 runtime snapshot and redeploying the app shell.
Each page displays a freshness indicator showing the data window in use. Internal analytics pages include their own freshness notes for data outside the broad expertise payload.
Operational telemetry is used only to understand whether the app is loading, which page categories are used, and whether browser errors occur. It records page and mode names, broad or restricted access class, and route flags such as whether a view includes an area, faculty, or grant detail.
Telemetry does not record search queries, BAA/RFP text, prompt text, model output, grant titles, faculty names, sponsor names, or email addresses. When enabled, the server replaces the authenticated user identity with a salted, truncated hash before writing an event.
Operational telemetry is disabled when the page is loaded with monitor=0. Approved production telemetry should use a 30-day retention target unless a shorter scoped export is needed for incident review.