YENRA - UTILITY COMPUTING EVIDENCE REVIEW
Source guide: https://yenra.com/utility-computing-research/
Prepared September 10, 2026. Save a copy; use one record per claim.
This worksheet supports technology evidence review, not investment advice.

Decision to make and deadline: _________________
Relevant workload / service requirements: ______
Claim in your own words: _______________________
Claim type: specification, benchmark, case study,
forecast, announcement, or other: ______________

SOURCE RECORD
Title / author / organization / URL: ___________
Publication date: _____________________________
Measurement date / period: _____________________
Product version / region / configuration: ______
Access date / archived evidence location: ______
Funding / sponsorship / participant perspective:
_______________________________________________

MEASUREMENT BOUNDARY
Metric definition / expression / unit: _________
Inputs / sample size / duration / repetitions: _
Baseline and why it is comparable: ______________
Correctness / failures / variation: ____________
Included costs and resources: __________________
Omissions / exclusions / uncertainty: __________
Forecast target year and category definition: __
Supporting raw data / methodology: _____________

FICTIONAL SAVINGS EXAMPLE - all amounts invented
Compute component: baseline $1,000, proposal $500 = 50% reduction.
Whole monthly baseline: $1,000 compute + $200 operations = $1,200.
Whole monthly proposal: $500 compute + $250 storage + $150 network
+ $200 operations = $1,100.
Monthly reduction: $100 / $1,200 = 8.33% (rounded).
One-time transition: $2,400.
First 12 months baseline: 12 x $1,200 = $14,400.
First 12 months proposal: 12 x $1,100 + $2,400 = $15,600.
Simple undiscounted break-even: $2,400 / $100 = 24 months.
Holds demand, prices, service quality, and risk fixed; excludes financing.
Separate capability improvements from the cost arithmetic.

APPLICABILITY
Which conditions match our workload? ___________
Which conditions differ? _______________________
Missing evidence that could change the decision:
_______________________________________________
Specific question or test to resolve it: ________
Owner / expected result / due date: ____________

CONCLUSION
Supported under these conditions / promising pending this test /
insufficient for this decision: ________________
Reason and scope: ______________________________
Version, pricing, workload, or evidence change requiring a review:
_______________________________________________
Metric reference: NIST SP 500-307
https://www.nist.gov/publications/cloud-computing-service-metrics-description