LN

PPM Workflow HubSurface 1 of 3

Resource Management · for L4–L6 people managers across GTO, GPO, LNNA, and Min Chen's data science org
Stage 3 — Concept Build
LexisNexis Embedded Innovation
Demo
9 direct reports + 2 open reqs across 4 active projects
Action needed 5 items to resolve ~15 min to clear
Sofia Park · 9 direct reports + 2 open reqs · Source: Workday roster + PPM resource summary

Needs your attention

Name Project allocations Total Audit
$
Finance view = Surface 4 (Budget Management)
Surface 1 is the resource manager's view — people-led, single-team scope. Finance partners support multiple managers across orgs and need a different shape: filterable cross-manager spend, budget benchmarks, and over-budget alerting. That JTBD lives on Surface 4, not here.
01
Per-manager × project spend
Filterable view of every manager's team allocation rolled up by project, with comparisons to forecast and budget targets. The view Kristin Willman generates manually for Eric today, productized.
02
Budget benchmarks per project
Each project's actual + forecast spend compared to its target budget at the C-code level. Replaces "intrinsically know or just assume what you should be targeting" with explicit benchmarks (Eric Platow 2026-05-01 email).
03
Over-budget alerting
Real-time push when a project crosses its target — distinct from the Type B weekly digest pattern used for resource changes. Budget exceptions need faster signal than weekly batch.
Coming in Surface 4 — pending Eric Platow session
Why Finance doesn't live on Surface 1 Surface 1's JTBD is "is my team set up right?" — answerable for one manager's team at a time. Finance's JTBD is "are my orgs on budget, and where do I need to ask questions?" — answerable across many managers' teams aggregated. Different JTBD, different surface. Same human (Matt) can use both, just for different questions. JTBD-by-hat separation locked in spec.md (Q6, 2026-05-11).

New project creation — indirect-first bundle

One indirect project + one or more derived directs per Kristin Willman 2026-05-26 · Generates FBDI CSV (Tier 1) · Fusion API write-back planned for Tier 2
No projects pending creation.
Use the form below to create a new project.
Bundle workflow — field map pending Kristin Willman validation
Current working assumption: each derived direct inherits Template family (Direct variant), Organization RC, Legal Entity, PM Email, and Attributes 1-9 from the indirect. User edits the deltas: project name (auto-suffixed by BU), BU/LE if direct goes to a different BU, ALLOCATION % (defaults to 1 per KW row 4). Confirm field-by-field at next Kristin session. Source: Kristin doc 2026-05-26; spec.md Open Question on bundle field map
OPEN QUESTION
Indirect project name. Each derived direct auto-suffixes with its BU (e.g., {name}-LNNA-US) per KW row 4 example. Free text — avoid trailing whitespace, leading zeros only on numeric IDs.
Enumerated Fusion values only — exact-match correctness is enforced at selection time.
Cascades from legal entity.
Enumerated Fusion templates only — no free-text mismatch risk.
Drives watcher-suggestion ranking below.
Cascades from PEO. Enumerated values only.
Auto-suggested with "I" suffix indicating indirect. Each derived direct gets a sibling ID with "A" suffix per Matt's rebuild scenario. Editable.
Watchers — financial-visibility access CONFIRM WITH SME — Monday
Three independent stakeholder pools per spec.md CA #116 — Senior leadership (L6+), Project management (Natalie Simberg's org), Finance / decision support. Suggested watchers ranked by PEO match to the project's executing org.
CONFIRM WITH SME — Monday Surface 3 inherits Surface 1's single-project-per-req default (Open Q #62). Jason / Matt / Eric to confirm at Monday session whether split-funded reqs are common enough to warrant a multi-project editor; ship as exception path until validated.
Direct projects derived from this indirect 0
Non-chargeback projects need at least one direct paired with this indirect (per Kristin Willman 2026-05-26 PMO scope doc). Each derived direct inherits the indirect's fields; you edit only the deltas (project name suffix, BU/LE if different, ALLOCATION %). Fill the indirect project fields above (template required) to enable adding directs.
No directs added yet for this indirect.
For chargeback projects: chargebacks are indirect-only — no directs needed (per Kristin 2026-05-26: "Chargebacks only have Indirect"). The chargeback signal in this form's data model is still being confirmed (see Open Question on Kristin's queue). When resolved, this Directs panel auto-hides for chargeback indirects. SIGNAL TBD
Required fields marked * · Bundle = 1 indirect + 0 direct(s)
FBDI preview · Tier 1 output Read-only · Regenerate by editing the form
✓ CSV downloaded · 0 project ready to upload to Fusion
File: —
Next step: open Fusion PPM → Batch Loader → upload this file. Validation runs in Fusion (exact-string match per legal entity / template / RC values).
▶ View CSV content (0 rows) 

            

            

              ⓘ
              Tier 2 production: direct Fusion API write replaces this manual upload step.
              PENDING FUSION API ACCESS
            

          

          
          

            ✓
            Uploaded to Fusion · — · audit recorded
          

          
          

        

      

    


    
    

      

        PPM Operations — forward intent. Additional PPM Ops sub-jobs shaped through discovery (Workday reconciliation, H1/H2 close, contractor management). Not yet built. The reclass + approved-allocation Fusion load is live above in the FBDI Load Queue.
      

      

    


  



















  

    

      
Audit record

      
Drill-down from digest item · immutable