Acquisition Workspace
Define the mission need, structure requirements, discover the appropriate work breakdown, and preserve traceability for downstream acquisition products.
Step 1 — Acquisition Context
Create or update the shared parent record for this acquisition.
Step 2 — Agency / DARPA Context
Capture planning context without implying that a final instrument has been determined.
DARPA Acquisition Profile
Step 3 — Mission Need Discovery
Define the problem and required Government outcome before decomposing requirements into work.
Mission Need Summary
Step 4 — Requirement Discovery
Translate the Mission Need into distinct Government requirements. COR Essentials uses qualifying questions to prevent the requirement from becoming a premature preferred solution.
A. What must the Government obtain or accomplish?
Identify distinct outcomes, capabilities, services, products, or results. Use one requirement per line.
B. What form should the requirement take?
Select all that describe the nature of the requirement.
C. What must be measurable or verifiable?
Capture technical metrics, performance outcomes, acceptance criteria, demonstrations, or other evidence of success. One item per line.
D. What Government boundaries or responsibilities matter?
Identify Government-furnished information/equipment, Government dependencies, security/access boundaries, or Government-retained responsibilities.
E. What should be explicitly excluded?
Identify known exclusions or scope boundaries to reduce ambiguity and later cost growth.
Draft Requirements
Requirement Qualification
Generate a qualification card for each draft requirement. Qualify each requirement independently before COR Essentials allows the requirement set to drive WBS Discovery.
Step 5 — WBS / Task Discovery
Determine how the work is naturally organized before assigning resources and costs.
A. How is this effort naturally organized?
Select all structures that apply. COR Essentials will use these to create an initial work hierarchy.
B. What major bodies of work are required?
Enter one major work element per line. For DARPA R&D, these may be technical areas, research thrusts, phases, experiments, prototype activities, test events, or transition activities.
C. What demonstrates completion?
Enter major milestones or deliverables, one per line.
D. Are there important dependencies?
Describe sequencing or prerequisite relationships that could affect schedule or cost.
Recommended Structure
Complete the discovery questions to generate a recommended structure.
Step 6 — Requirement Structure Review
Review the requirement-to-work relationship before later resource estimating begins.
Requirements
Initial WBS / Work Structure
Structure Quality Check
Primary + Supporting Requirement Traceability
COR Essentials first compares each work element against the actual requirement statements to identify the strongest primary relationship, then identifies plausible supporting requirements. Recommendations remain advisory until explicitly applied.
Step 7 — Resource & Cost Discovery / IGCE Foundation
Estimate the resources required to perform each validated WBS element. Build 2.0 creates a WBS-linked IGCE foundation; it does not replace Contracting Officer judgment, certified cost/pricing analysis, or independent rate validation.
WBS-Linked Resource Estimates
Enter labor and non-labor resources against each work element. Loaded labor = hours × rate. Other direct costs may include travel, materials, software/licenses, equipment, subcontracts, and ODCs.
IGCE Roll-Up
Acquisition Library
Open a saved acquisition from corEssentials.acquisition.v1.