Operations
AuraScore 81/100

Academic Core Facility Shared Infrastructure Operational Brief

Synthesize equipment utilization, operational bottlenecks, and shared-use protocols into an actionable academic core facility operational brief.

Use this template when centralizing laboratory equipment and specialized research infrastructure across multiple academic departments. It structures cross-disciplinary utilization models, chargeback structures, and maintenance governance into an executive brief.

Template

Role: Principal Academic Research Operations Director with 15+ years managing core facility infrastructure across R1 research universities.

Context

  • Research Institution: {{institution_name}}
  • Covered Research Fields: {{research_disciplines}}
  • Current Baseline Utilization: {{current_utilization_rate}}
  • Critical Shared Instrumentation: {{equipment_portfolio}}
  • Target Operational Cost Reduction: {{budget_headwind_target}}
  • Governance & Safety Standard: {{compliance_framework}}

Task

Produce an exhaustive operational brief detailing the consolidation, scheduling governance, maintenance protocol, and chargeback model for shared core scientific infrastructure to maximize research throughput under fiscal constraints.

Method

  1. Analyze the current operational throughput across {{equipment_portfolio}} against {{current_utilization_rate}} to identify underutilized capital assets.
  2. Map scheduling frictions, booking downtime, and cross-departmental contention points among {{research_disciplines}}.
  3. Formulate an access prioritization matrix balancing funded principal investigators, postdocs, graduate students, and external industry partners.
  4. Structure a multi-tiered preventative maintenance schedule that minimizes research disruption while maintaining compliance with {{compliance_framework}}.
  5. Design an internal chargeback and cost-recovery framework targeted at meeting {{budget_headwind_target}} without discouraging pilot research.
  6. Specify standard operating procedures for technician staffing, onboarding, and safety training across multi-user environments.
  7. Establish key performance indicators for equipment uptime, mean time to repair, and cost-per-hour benchmarks.

Constraints

  • MUST ground all operational recommendations in verifiable facility data and realistic academic research schedules.
  • MUST include explicit risk mitigation steps for single-point-of-failure scientific instruments.
  • MUST NOT suggest full privatization of core assets or policies that block unfunded early-career exploratory research.
  • Total brief length must stay between 900 and 1300 words across all sections.

Output format

Present the brief using these exact markdown sections:

  1. Executive Summary (Max 150 words)
  2. Infrastructure Utilization & Bottleneck Diagnosis (Table + Narrative)
  3. Core Governance & Prioritization Policy (Numbered rules)
  4. Preventive Maintenance & Technical Staffing Blueprint (Detailed schedule)
  5. Cost-Recovery Model & Financial Sustainability (Bullet breakdown)
  6. Implementation Roadmap & Metric Milestones (90-day phased table)

Self-review

  • Did I incorporate all listed fields in {{equipment_portfolio}} and address {{research_disciplines}} specifically?
  • Is the cost-recovery strategy aligned with {{budget_headwind_target}} without breaching {{compliance_framework}}?
  • Are access rules explicit regarding peak vs. non-peak instrumentation hours?
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

business-strategy
business-operations
education-research
research operations
higher education
lab management