PDCC Agency App overview
The government-facing workspace for acquisition teams: one place for daily work, acquisitions, contracts, market research, evidence, Studio views, the Scout companion and delegated administration.
All agency users
/pdcc/my-dayThe PDCC Agency App is the agency-facing side of PEEK's Procurement Data Command Center. Where the internal PEEK Administration Center is used by PEEK operators to provision customers and modules, the Agency App is where an agency's own people — contract specialists, contracting officers (COs), contracting officer's representatives (CORs), acquisition planners, market research analysts, budget reviewers, branch chiefs and agency administrators — do their acquisition work.
Everything in the app runs inside a single agency workspace (a tenant). The demonstration workspace is the CBP demonstration workspace, seeded with synthetic acquisition records plus roughly 9,900 real public CBP contract awards (FY2022–FY2026) from a USAspending snapshot.
What you can do
| Area | Where | What it is for |
|---|---|---|
| My Day | /pdcc/my-day | Your landing page: assigned reviews, evidence gaps, upcoming milestones, the ALIVE overview and Scout insights. |
| My Work | /pdcc/my-work | Every task, review, approval and handoff assigned to you; waiting-on-others, calendar, activity and My Automations. |
| Acquisitions | /pdcc/acquisitions/... | Requirements, Acquisition Actions (planning), Contracts & Orders and Market Research. |
| Team & Portfolio | /pdcc/portfolio | Scoped oversight for supervisors and leaders: workload, exceptions, briefs and decisions. |
| Studio | /pdcc/studio | Optional composed views built from approved components. |
| Reference | /pdcc/reference | The evidence library: versions, provenance, matching, gaps and authorized exports. |
| Scout | Docked companion (Alt+S) | Evidence-grounded assistance inside the record you are looking at. |
| Administration | /pdcc/admin/... | Delegated agency administration: users & access, policies & workflows, module settings, SI governance, connections, automations and access history. |
Three ideas that shape the whole app
- Authentication is not authorization. Signing in proves who you are. What you can see and do comes from approved agency assignments, data scopes and — for legal acts — verified authority such as a CO warrant or COR designation. See personas and perspectives.
- A persona never grants access. Switching your active persona or perspective changes which menus and work are emphasized; it never adds a record, a capability or an authority.
- Preparing is not executing. The app prepares packages, findings, reminders and drafts. Executing a modification, accepting a deliverable, filing a document or obligating funds happen only through the authorized official and the system of record, and each produces its own receipt.
How work flows through the app
Typical acquisition lifecycle
1. Requirement
A program originator defines the mission need in Requirements.
2. Market research
A research owner investigates the market (MR01–MR21) and a CO records the report decision.
3. Acquisition planning
A planner assembles SOW, IGCE and review into a versioned plan in Acquisition Actions.
4. Award link
An authoritative award is linked to the requirement and plan — linking is not award execution.
5. Contract intake
The contract team brings the award into managed work: documents, facts, team assignment, readiness.
6. Execution
Deliverables, surveillance, options, modifications, funding and invoices are managed against source evidence.
7. Closeout
Closeout readiness is tracked; official closeout stays in the system of record.
Where to go next
- New user? Start with signing in and first-use onboarding.
- Learn the vocabulary in key concepts and the glossary.
- Trying the demo? See demonstration personas for who to sign in as.
Related guides
Key concepts
Workspace, assignments, scopes, authority, evidence lanes, versions, receipts and the synthetic profile — the vocabulary used on every screen.
Personas and perspectives
How the active persona and work perspective shape menus, My Day and Scout — and why they never grant access or authority.
Modules: Core and optional
What Core always includes, what each optional module adds, and how the app keeps working when a module is absent or disabled.
Demonstration personas
Who to sign in as in the demonstration workspace, what each persona can do, and which pages show them best.