Demo listing. This page uses illustrative seed metadata to demonstrate the Atlas. Claims shown here are not verified product facts.
Baselinecast
Baseline and earned-value control tower
Locks WBS cost/schedule baselines, captures progress only from evidenced facts, computes CPI/SPI and drafts variance narratives that cite those facts.
Last verified 15 Sept 2026 · Updated 23 Sept 2026 · Metadata v5
Problem
Monthly EVM packs are assembled by hand from P6, Excel and Power BI that disagree, with progress percent typed from optimism.
Outcome
Trusted period packs — approved baseline, evidenced progress, deterministic indices and cited variance narratives.
Who uses it
- Finance Analyst
- Operations Analyst
- Portfolio Manager
- COO
Key capabilities
Approved baseline versions
IncludedWBS cost/schedule targets with reason, approver and before/after snapshot.
Domain:
baselinesEvidenced progress capture
IncludedProgress enters only via attested facts — never model-invented percent complete.
Domain:
progressDeterministic EVM metrics
IncludedCPI, SPI, PV, EV, AC and configured EAC from baseline + progress + actuals.
Domain:
metricsCited variance narratives
AI-assistedIncludedAI drafts that must cite fact ids; uncited sentences rejected.
Domain:
narrativesImmutable period packs
IncludedMonth-end snapshot of metrics, narrative and exports.
Domain:
period-packs
Typical workflow
Period controls close
Trigger: Project controls opens a reporting period against an approved baseline
Task
Stage 1: Confirm baseline version
Project controls manager
Task
Stage 2: Capture evidenced progress
Cost engineer
Automated
Stage 3: Compute EVM metrics
System
AI-assisted
Stage 4: Draft variance narrative
System
Human checkpoint
Stage 5: Approve period pack
Project controls manager
Task Automated AI-assisted Human checkpoint Decision
About this foundation
Baselinecast is the controls truth layer between execution tools and executive reporting. Progress percent is never generated by a language model — it enters only through ProgressCapture records with provenance. CPI, SPI and related metrics are deterministic computations; AI may only draft variance narratives from a closed fact pack. Crewspan supplies field facts; Awardbind emits commercial events; Quantspan prices the bid; Baselinecast owns baselines, EVM and period packs.
Related applications
- Mashroo
Government portfolio and program delivery management
- • Addresses the same problem: Poor Visibility, Fragmented Systems
- • Shared capabilities: Forecasting, Reporting, Decision Support
- OpsDeck Aviation
Airline operations disruption management
- • Addresses the same problem: Poor Visibility, Fragmented Systems
- • Shared capabilities: Forecasting, Monitoring, Decision Support
- Vantage Operator Control
Virtual asset operator control plane
- • Addresses the same problem: Weak Evidence, Fragmented Systems
- • Shared capabilities: Reporting, Evidence Management
- Aetherlab
Enterprise AI model lifecycle control plane
- • Addresses the same problem: Weak Evidence, Fragmented Systems
- • Shared capabilities: Monitoring, Evidence Management
- Awardbind
Construction commercial and award administration
- • Addresses the same problem: Weak Evidence
- • Shared capabilities: Reporting, Evidence Management
- SOC Pilot
Security operations alert triage and investigation
- • Addresses the same problem: Weak Evidence, Fragmented Systems
- • Shared capabilities: Monitoring
Period controls close
Trigger: Project controls opens a reporting period against an approved baseline
Task
Stage 1: Confirm baseline version
Project controls manager
Task
Stage 2: Capture evidenced progress
Cost engineer
Automated
Stage 3: Compute EVM metrics
System
AI-assisted
Stage 4: Draft variance narrative
System
Human checkpoint
Stage 5: Approve period pack
Project controls manager
Actors
Cost engineer, Project controls manager
Outputs
- Period pack
- CPI/SPI dashboard export
Evidence generated
- Progress provenance and narrative citations
Exceptions
- Unsupported progress claims are rejected
Task Automated AI-assisted Human checkpoint Decision
Included ships in the foundation · Configurable is switched or tuned per customer · Extension is customer-specific build scope · Planned is on the roadmap and not available today.
Approved baseline versions
IncludedWBS cost/schedule targets with reason, approver and before/after snapshot.
Domain:
baselinesEvidenced progress capture
IncludedProgress enters only via attested facts — never model-invented percent complete.
Domain:
progressDeterministic EVM metrics
IncludedCPI, SPI, PV, EV, AC and configured EAC from baseline + progress + actuals.
Domain:
metricsCited variance narratives
AI-assistedIncludedAI drafts that must cite fact ids; uncited sentences rejected.
Domain:
narrativesImmutable period packs
IncludedMonth-end snapshot of metrics, narrative and exports.
Domain:
period-packs
- Architecture class
- Domain-driven design, OpenAPI-first
- Bounded contexts
- 6
- API-first
- Yes — OpenAPI contracts are authoritative
- Identity
- Enterprise OIDC / SAML via the fazeZERO identity blueprint; tenant-aware role-based access.
- Multi-tenancy
- Tenant-aware
- Service boundaries
- 6 bounded contexts behind one API server.
- Integration approach
- Ports-and-adapters: every external system sits behind an adapter; OpenAPI contracts for inbound APIs.
- Eventing
- Integration events via transactional outbox.
- Storage abstraction
- Repository interfaces; DynamoDB or relational adapters.
- Deployment pattern
- Containerized API + web application; infrastructure as code per cloud profile.
- Architecture version
- 1.0
Approved domain names
- baselines
- progress
- metrics
- narratives
- period-packs
- identity
- Web Application
- API Server
- Application Services
- Domain / Generated Core
- Adapters
- Customer Systems
Generator source, templates and factory orchestration are proprietary and are not part of this listing.
Reference Adapter: shipped and tested · Previously Integrated: delivered before · Standard API Pattern: integrates via a documented pattern · Customer-Specific: built in your implementation.
Data
| Integration | Status | Direction | Method |
|---|---|---|---|
| Primavera P6 / MS Project | Standard API Pattern | inbound | File / API import |
ERP
| Integration | Status | Direction | Method |
|---|---|---|---|
| Cost / ERP actuals | Customer-Specific | inbound | REST API |
Deployment
- Deployment models
- Customer Cloud, Private Cloud
- Cloud profiles
- Azure Profile, AWS Profile
- Containerized
- Yes
- Regions
- GLOBAL, UAE, SAUDI ARABIA, US
Cloud profiles describe approved deployment patterns. They are not formal marketplace certifications.
Data handling
- Stores customer data
- Yes
- Data leaves customer environment
- Configurable
- Uses external AI provider
- Configurable
- Sends logs externally
- No
- PII expected
- No
- Data-residency support
- Yes
- Subprocessors required
- Determined during customer configuration
Identity & access
- Authentication
- OIDC, Entra ID, SAML
- Authorization
- Role-Based, Tenant-Aware
- Source availability
- Proprietary
Support
- Implementation
- Delivered by fazeZERO or a certified partner during the Solution Definition and AI Production Sprints.
- Production support
- Production support available under a separate support agreement.
- Contact
- support@fazezero.com
Badges
fazeZERO Verified
Listing metadata and published technical claims have been reviewed by fazeZERO.
Issued 23 Sept 2026
Evidence shows that this listing represents real engineering. Internal metrics are only published when fazeZERO has approved them for publication.
Build
Automated tests
Deployment validation
- Last verification
- 15 Sept 2026
- Release
- 1.0.0
- Architecture version
- 1.0
- Listing metadata version
- 5
- Last published
- 23 Sept 2026