Skip to content
POST/api/v1/health/dcma-decm

DCMA DECM Assessment

Run a DCMA DECM Tier 2 schedule compliance assessment.

Accepts a schedule payload (tasks + metadata), optional schedule history for retroactive date change detection, and assessment options. Returns check results grouped by EVM Guideline with overall pass/warning/fail status and prioritized remediation recommendations.

Request example

json
json
{
  "tasks": [
    {
      "id": "T1",
      "duration_days": 5
    }
  ]
}

Request fields from OpenAPI contract

Required fields and the optional fields that change this call are listed here. The shared task model stays on the task schema guide.

This table is generated from the endpoint schema in openapi.json.

FieldTypeRequiredDescription
tasksarray<unknown>RequiredTask list (minimum 2 tasks required)
tasks[].idstringRequiredUnique task identifier
status_datestring | nullOptionalProject status/data date (ISO 8601). Required for checks 06A212a, 06A506a/b/c. Skipped with informative message if absent.
target_finish_datestring | nullOptionalContract/target finish date (ISO 8601). Reserved for future Tier 3 use.
start_task_idsarray<string>OptionalTask IDs that legitimately have no predecessors (exempt from check 06A204b).
finish_task_idsarray<string>OptionalTask IDs that legitimately have no successors (exempt from check 06A204b).
schedule_historyarray<unknown>OptionalOptional historical snapshots for retroactive date change detection (checks 06A504a/b). Each snapshot requires snapshot_date + tasks.
schedule_history[].snapshot_datestringOptionalSnapshot date (ISO 8601)
schedule_history[].tasksarray<unknown>OptionalTask list at snapshot time
schedule_history[].tasks[].idstringOptionalUnique task identifier
schedule_history[].tasks[].duration_daysnumberOptionalTask duration in days
schedule_history[].tasks[].predecessorsarray<string | object | unknown>OptionalList of predecessor task IDs or dependency links. Supports: 'T1', 'T1FS+5 d', 'T2SS-2 d', or DependencyLink objects
schedule_history[].tasks[].namestring | nullOptionalTask name
schedule_history[].tasks[].resourcestring | nullOptionalResource assigned to task
schedule_history[].tasks[].resourcesarray<string>OptionalList of resources assigned (for multi-resource tasks)
schedule_history[].tasks[].percent_completenumberOptionalPercent complete (0-100)
schedule_history[].tasks[].physical_percent_completenumber | nullOptionalPhysical percent complete (0-100). Manual EVM entry by scheduler (MSP PhysicalPercentComplete). Authoritative for BCWP calculations. Captured separately from percent_complete on MSP imports.
schedule_history[].tasks[].planned_startstring | nullOptionalPlanned start date (ISO 8601)
schedule_history[].tasks[].planned_finishstring | nullOptionalPlanned finish date (ISO 8601)
schedule_history[].tasks[].actual_startstring | nullOptionalActual start date (ISO 8601)
schedule_history[].tasks[].actual_finishstring | nullOptionalActual finish date (ISO 8601)
schedule_history[].tasks[].baseline_startstring | nullOptionalBaseline start date (ISO 8601)
schedule_history[].tasks[].baseline_finishstring | nullOptionalBaseline finish date (ISO 8601)
schedule_history[].tasks[].constraint_typestring | nullOptionalConstraint type: ASAP, ALAP, SNET, SNLT, FNET, FNLT, MSO, MFO
schedule_history[].tasks[].constraint_datestring | nullOptionalConstraint date if applicable (ISO 8601)
schedule_history[].tasks[].task_typestring | nullOptionalTask type classification. Valid values: task (default), milestone, loe, summary, schedule_margin, planning_package, slpp, schedule_visibility. Drives DCMA check exclusions per PAM 200.1 § 3.2.
schedule_history[].tasks[].wbs_codestring | nullOptionalWBS code (e.g., '1.2.3')
schedule_history[].tasks[].organization_codestring | nullOptionalOrg/dept identifier for anomaly categorization (Progress Audit)
schedule_history[].tasks[].custom_field_mapobject | nullOptionalAll WBS/OBS-pattern custom fields discovered in this MS Project file, keyed by alias (e.g., 'CWBS', 'OBS'). Null for XER imports or when no matching aliases exist.
schedule_history[].tasks[].forecast_startstring | nullOptionalCurrent forecast start date (ISO 8601)
schedule_history[].tasks[].forecast_finishstring | nullOptionalCurrent forecast finish date (ISO 8601)
schedule_history[].tasks[].total_float_daysnumber | nullOptionalPre-computed total float in days. Auto-computed by CPM if absent.
schedule_history[].tasks[].baseline_duration_daysnumber | nullOptionalBaseline duration in days. Auto-computed from baseline dates if absent.
schedule_history[].tasks[].delay_categorystring | nullOptionalDelay attribution category. Valid values: owner, contractor, design, procurement, weather, force_majeure.
schedule_history[].tasks[].earned_valuenumber | nullOptionalEarned Value (BCWP) in cost units. Requires options.include_ev_validation.
schedule_history[].tasks[].budgeted_costnumber | nullOptionalBudgeted Cost of Work Scheduled (BCWS) in cost units.
schedule_history[].tasks[].approval_requiredboolean | nullOptionalWhether this task requires explicit approval before it can start.
schedule_history[].tasks[].approval_statusstring | nullOptionalApproval workflow state. Valid values: not_required, pending, approved, rejected.
scopestringOptionalScope of evaluation. 'schedule_only' (default) = 17 Tier 2 checks. 'guideline_6', 'full' = Tier 3 (not yet implemented).
optionsobjectOptionalRequest options for DCMA DECM assessment.
options.threshold_profilestringOptionalThreshold profile: 'dcma-decm-default' (default), 'dcma-decm-strict'.
options.custom_thresholdsunknown | nullOptionalPer-check threshold overrides (applied on top of selected profile).
options.include_detailsbooleanOptionalInclude violating task IDs and detailed evidence objects in each check result.

Response example

json
json
{
  "score": 92,
  "grade": "A"
}

Response fields from OpenAPI contract

This table is generated from the endpoint response schema in openapi.json.

FieldTypeRequiredDescription
statusstringRequiredTop-level result status — always present in every response.
metadataobjectRequiredAudit trail and processing context — always present, never null.
metadata.task_countintegerRequiredNumber of tasks in the submitted schedule
metadata.endpointstringRequiredEndpoint path e.g. /api/v1/health/score

Schema

json-schema
{
  "$ref": "#/components/schemas/BellatorResponse_DCMADECMData_"
}

Authentication

  • x-api-key header

Reference details

Operation ID
health_dcma_decm
Section
health
Tags
health
Playground link
/playground?endpoint=%2Fapi%2Fv1%2Fhealth%2Fdcma-decm&method=post

Was this page helpful?

Your feedback helps us improve docs, reference pages, and Playground flows.

Topic: DCMA DECM Assessment · Page: /docs/api-reference/health_dcma_decm

TermsPrivacyContact

Schedule analysis guidance. Not legal advice. You remain responsible for contract and agency compliance.