{"api":{"name":"api.sb","description":"Business-as-Code surface for Startups.Studio","home":"https://api.sb","docs":"https://api.sb/docs","version":"1.0.0"},"$context":"https://api.sb/$context","$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Ageneral-and-operations-managers-operations-review-package%3At-hsa%3Av1","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Ageneral-and-operations-managers-operations-review-package%3At-hsa%3Av1","canonical":"https://api.sb/founding-hypotheses/fh%3Ageneral-and-operations-managers-operations-review-package%3At-hsa%3Av1","pool":"https://api.sb/v1/founding-hypotheses"},"foundingHypothesis":{"id":"fh:general-and-operations-managers-operations-review-package:t-hsa:v1","lens":"HeadlessSaaS","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":1,"C7_magicLensFit":1,"C4_competitorHonesty":1,"C6_crossSlotCoherence":1,"C1_customerSpecificity":1,"C2_problemFrictionRealism":1,"C9_killCriteriaAttestability":1,"C3_approachEngineCoverability":1,"C5_differentiationLoservilleEscape":1},"upperRightLoserville":true},"cellRef":{"id":"work-contexts.org.ai/general-and-operations-managers-operations-review-package","stableHash":"wcc:general-and-operations-managers:operations-review-package:document:v1"},"problem":{"slotStatement":"Every month the ops analyst rebuilds the board-review packet by pulling SAIDI/SAIFI/CAIDI from the OMS, load and substation counts from SCADA historian exports, and capex-project status from the work-management system — and each source has drifted to a different reliability-definition version (IEEE 1366 major-event-day threshold recalculated annually, cause-code taxonomy updated after last year's PUC docket, territory-boundary shapefile re-cut after the last annexation), so last month's numbers silently stop matching this month's numbers and the board packet carries reliability figures the co-op cannot defend if the PUC asks which rule version produced them."},"approach":{"oneSentence":"A headless close-the-books service for the monthly ops packet that locks each metric to the exact IEEE-1366 threshold, cause-code taxonomy, and territory shapefile version in force on the reporting date, re-runs prior months against the pinned rule set whenever a definition changes, and hands the analyst a board-ready packet whose every figure carries a traceable record of the rule version that produced it."},"customer":{"icpShape":"VP of Finance (economic buyer who signs the PO) at a member-owned electric cooperative (CompanyType/company-type-member-owned-electric-cooperative) in the 40k–250k-meter range, where the buyer is the VP of Finance / CFO and the daily user is the Manager of Operations or Ops Analyst who assembles the monthly board-ops review packet from OMS, SCADA, AMI, GIS, and outage-cause spreadsheets.","beachheadShape":"EarlyMajorityWorkflow: G&T-affiliated distribution co-ops with 40k–150k meters running NISC or SEDC back-office plus a Milsoft/Survalent OMS, whose monthly operations review packet goes to both the member-elected board and the state PUC liaison."},"archetype":"startup-archetypes.org.ai/HeadlessSaaS-MarketplaceClearing","beachhead":"EarlyMajorityWorkflow: G&T-affiliated distribution co-ops with 40k–150k meters running NISC or SEDC back-office plus a Milsoft/Survalent OMS, whose monthly operations review packet goes to both the member-elected board and the state PUC liaison.","competitors":{"substitutes":[{"name":"Milsoft DisSPatch / OMS reliability reports","category":"incumbent","uncopyabilityReason":"Milsoft's reliability module computes SAIDI/SAIFI against whatever threshold and cause-code taxonomy are configured in the live OMS today; it has no temporal version store for rule definitions because its integration depth stops at the OMS boundary and does not reach the WMS, GIS annexation history, or SCADA historian. Rebuilding a cross-system rule-version ledger would require re-architecting the OMS schema and breaking its existing co-op install base — an integration-depth barrier it cannot clear in six months."},{"name":"NISC iVUE Analytics","category":"incumbent","uncopyabilityReason":"NISC is a member-owned cooperative itself selling a bundled CIS/AMI/GL stack; its pricing and release cadence are governed by an annual member-vote roadmap, and analytics features ship on a 12–18 month cycle set by a member advisory committee. This distribution-channel constraint means NISC structurally cannot push a rule-version-pinning module outside its cooperative release train within six months."},{"name":"Power BI / Tableau dashboards built by co-op IT","category":"AI-native horizontal","uncopyabilityReason":"Microsoft and Salesforce ship horizontal BI with generic Copilot summarization; they have zero corpus of FERC Form 861, RUS Form 7, and state-PUC reliability-docket rule histories, and their deployment mode assumes the customer owns the semantic model. The vertical-data-corpus barrier (historical IEEE-1366 interpretations, NRECA cause-code revisions, per-state PUC major-event definitions) cannot be assembled without years of co-op-specific regulatory ingestion."},{"name":"Ops-analyst-maintained Excel workbook with linked OMS/SCADA extracts","category":"manual-bridge"},{"name":"Contract reliability consultant who rebuilds the packet quarterly","category":"human alternative"}]},"studioThesis":"T-HSA","killThreshold":{"K":9,"M":35,"N":8,"rubricItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C7_magicLensFit","C8_lensFit","C9_killCriteriaAttestability"],"verdictPolicy":"all-load-bearing-pass-and-overall-ge-X","loadBearingItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C9_killCriteriaAttestability"],"verdictPolicyVerbatim":"KILL unless every load-bearing rubric item passes per workbook AND overall pass-rate ≥ 8/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Rule-version handling across months (live config overwrites history ↔ every metric pinned to the rule version in force on its reporting date)","yAxis":"Cross-system scope of the packet (single-system report e.g. OMS-only ↔ stitched across OMS + SCADA + WMS + GIS + AMI with reconciled territory and cause-code taxonomy)","winningQuadrant":"Per-period pinned rule versions stitched across all five co-op systems, so when the PUC or board asks 'why did last March's SAIDI change' the packet shows which definition moved and which figures were re-run under the old rule","loservilleEscape":true,"loservilleQuadrant":"Milsoft OMS reliability reports — single-system scope and live-config overwrite, so when the IEEE-1366 threshold is recomputed annually the prior months silently shift and the analyst cannot explain the delta to the board"}},"unmetRequirements":[],"pricingArchitecture":"custom-quote"},"actions":{},"options":{},"relationships":{"runtimeUnit":"https://api.sb/v1/runtime-units?startupRef=startup%3Afh%3Ageneral-and-operations-managers-operations-review-package%3At-hsa%3Av1","brand":"https://api.sb/v1/brands?startupId=startup%3Afh%3Ageneral-and-operations-managers-operations-review-package%3At-hsa%3Av1","listing":"https://api.services/listings?foundingHypothesisRef=fh%3Ageneral-and-operations-managers-operations-review-package%3At-hsa%3Av1","cell":"https://api.sb/v1/cells/work-contexts.org.ai/general-and-operations-managers-operations-review-package","thesis":"https://api.sb/v1/theses/T-HSA"},"meta":{"level":"L0","scopes":[]},"user":{"requestId":"a0575ae9e90e90ce","edgeLocation":"a0575ae9e90e90ce","geo":{"country":"US"},"ua":{"browser":"Claude"}},"references":{"total":0,"limit":25,"page":1,"links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Ageneral-and-operations-managers-operations-review-package%3At-hsa%3Av1/references"},"items":[]}}