JWCC / NATIVE DATA PLATFORM CAPABILITIES
Collect. Validate. Process.
See where the time goes.
The cloud underpinning of an established end state. Compare native services, identify integration work and third-party options, and locate instrumentation that narrows root-cause investigation.
ONE DATA CONTRACT · FOUR IMPLEMENTATIONS
Capability is one question.
Deployment eligibility is another.
No provider ranking is assumed. Each overlay identifies platform functions, engineering responsibilities and environment-specific evidence gaps.
01 / TECHNICAL END STATE
Follow the data. Inspect the platform.
02 / ISOLATE THE CONTRIBUTING HOP
Native diagnostics + owned spans + queue evidence
Measure different kinds of delay separately. A slow trace locates a symptom; correlate it with service diagnostics, load, errors and changes before declaring a cause.
Preset synthetic p95 summaries only; no raw observations are measured or calculated here. Three repeated current-window values illustrate the screening rule: all three above 2× baseline p95. This is a screening rule, not a statistical test, a provider benchmark or a production SLO. Do not sum p95s. Missing data is unknown, not zero.
03 / COVERAGE WITHOUT A SCORECARD
Native service, integration work, or third-party fill?
Compare a defined requirement—not the size of a product portfolio. “Unverified” never means “unsupported.” A capability gap and a Government-region availability gap need different remedies.
Authorization, governance and delivery boundaries
Native services and telemetry backends must match the exact cloud, region, SKU, feature and current authorization package. Public product documentation proves capability, not suitability for this deployment. Required controls, mission authorization and approved connections remain separate. IL2 is only for eligible non-CUI information. IL4 supports Moderate/High; IL5 addresses unclassified NSS/NSI and applicable AO-directed protection needs. The July 2025 revision history and current V1R7 IL5/CUI body wording differ: confirm categorization with the responsible AO, rather than treating every CUI case alike.
Existing IL5 delivery scope stays unchanged. IL6 remains a separately governed architecture option. Keep identity, keys, administrators, CI/CD runners, operational workflows, logs and OTel collectors local to their approved domain. A shared GSS may supply assessed common controls only within documented applicability. OpenTofu baseline deployment does not establish inheritance or authorization.
A catalog can classify and describe assets without validating the truth of observations. Purview sensitivity labels are not DoD classification authority. Pipeline validation checks schema, ranges, units, time, duplicates and provenance; contextual or human vetting remains outside this page. No automated classification promotion is implied.
This lower-to-higher example requires an approved cross-domain flow and applicable Raise the Bar requirements. Same-domain SIPRNet connectivity is a different path. CSO provisional authorization does not replace mission ATO, handling, release, transfer or mission acceptance decisions. End source trace context by default and start an independent IL6 trace. Only explicitly approved metadata may cross; never propagate baggage, payloads or trace headers automatically.
Foundations Plus alignment: GSS Foundations establishes boundary and common-control evidence; Dependency Mapping identifies paths and dependencies; Zero Trust Planning defines identities and access; AIOps Readiness defines instrumentation and acceptance baselines; EA & Operations defines ownership, support and incident/change workflows. These are advisory/design contributions, not cloud-service authorization or production implementation entitlements.
JWCC is the acquisition context. Apply current enterprise/component procurement direction, available offerings and task-order requirements; confirm support, consumption and third-party licensing separately. No successor closing or award date is asserted here. No restricted catalog, mission package or classified service catalog was reviewed.
Research sources and adoption notes
Public provider documentation reviewed 24 October 2026. Each provider overlay links directly to its capability evidence. Newly shown governance and observability products are candidates pending exact environment validation; none is presented as a blanket IL5/IL6 approval.
Instrumentation examples are representative Python SDK code for owned adapters/processors. They omit provider/exporter initialization, credentials, sampling configuration, retry policy and production error scrubbing. No telemetry is emitted by this page. Configure eligible domain-local backends and pin supported SDK/exporter versions.
The connected views share this illustrative workbench; the accepted predecessor remains linked as an archive. It contains fictional performance data and no client mission data.