LN

PPM Workflow HubSurface 1

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
Needs your attention Illustrative — not sourced · pending Raleigh
Ranked exceptions across the managers you support — each with a one-line why, how long it's been open, and a route-to-action that closes the loop.
The spend rollup a traditional dashboard would lead with — here it's the drill-down behind the exceptions above, not the hero. Values are illustrative, not the confirmed capital-tracking baseline (PPM/Fusion doesn't hold it; the real source is the offline capital-tracking workbook, not yet inspected). The point: Matt's dashboard capabilities are incorporated and functional.
Budget by business unit
Project budget summary · click a row for L5 splits · click a header to sort
Project Business unit Budget owner Budget Forecast Variance
Why Finance is its own surface A resource manager asks "is my team set up right?" — one team at a time. A finance partner asks "across the managers I support, what's off, and who do I need to nudge?" — many teams at once, and may see more data than a project watcher (down to comp tiers) — pending a Finance access decision. Different job, different surface. The differentiator isn't a prettier dashboard — it's leading with what to act on and routing it to resolution. Full framing: spec §23.
For the October (Raleigh) onsite This is a starting point, not a finished answer — it leads with what to act on and routes each item to whoever can fix it. The question for the room: where does this break for your part of the business?

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