Project Manager, VA Center for Care & Payment Innovation (CCPI) Pilot Coordination & Community of Practice Support

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, duplicated lines, navigation, etc. Also remove repeated "About Aptive" duplication? The posting includes "About Aptive" twice; we should include only once? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The duplicated lines are boilerplate; we can drop duplicates. The "About Aptive" content is substantive? It describes the company. Might be considered relevant but not required sections. We have sections: About the role (maybe we can put description of role). Responsibilities (list). Requirements (minimum qualifications). Qualifications (desired qualifications). Skills (maybe analytical, written, verbal communication). Benefits, Pay, Schedule: none given, so we should NOT include those sections. Also we might include a short paragraph for metadata like location? Not given. The posting includes location? Not explicit. It mentions based in Alexandria, Virginia for Aptive. Could include that as part of About the role? Probably not needed. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to include sections only when posting has real specific content. Let's extract: About the role: The first paragraph describes the role: "We seek an experienced Project Manager to support the Department of Veterans Affairs (VA) Veterans Health Administration (VHA) Strategic Planning Division (SPD)/Center for Care and Payment Innovation (CCPI). CCPI advances VHA as a center for the development of data-driven, value-based health care solutions that transform and improve Veteran care while reducing cost and administrative burden, and leads legislatively directed pilot initiatives. This role will serve as the Task Order (TO) Project Manager, the primary Contractor point of contact with SPD/CCPI and the Contracting Officer’s Representative (COR), supporting a portfolio of up to six concurrent pilots and associated CCPI program management activities, working closely with the contract-aligned Program Director, workstream leads, and Government leadership to ensure task order requirements are executed consistently and in accordance with VA standards and enterprise objectives." That's substantive. We'll put that in

  under

  About the role

  . Responsibilities: The section "Primary Responsibilities" then a paragraph describing responsibilities, then list of duties? It includes leading weekly status meeting, preparing reports, preparing scoping letters, facilitating sessions, maintaining repositories, collaborating, tracking scope changes, maintaining files, providing reporting. We can turn those into a
  • list. We need to capture all responsibilities: - maintaining the Government-approved Project Management Plan (PMP), Project Charter, integrated schedule, milestones, RAID Log, and Stakeholder Registry - developing and maintaining a Portfolio Management Dashboard that provides portfolio-wide visibility into status, milestones, risks, dependencies, decision points, and funding across all active pilots and workstreams - leading a weekly status meeting with the COR and producing a Weekly Task Report - preparing a semi-monthly budget and schedule tracker and a Monthly Progress Report covering budget, schedule, staffing, and performance - preparing scoping letters for emerging in-scope requirements, as requested by the Government - facilitating working sessions, stakeholder meetings, and decision-making forums - maintaining centralized repositories, action trackers, and risk/issue logs necessary to support program continuity and portfolio oversight - collaborating with the Program Director, Pilot Project Manager, Stakeholder Engagement & Communications Specialist, and Technical Writer/Editor to ensure coordinated execution across the SPD/CCPI portfolio and supports development of executive-ready briefing materials for SES leadership, governance bodies, and Congressional reporting - tracking approved scope changes - maintaining organized project files using version control and records management practices - providing Government customers with timely reporting on status, schedule, risks, issues, and performance metrics to support informed decision-making We'll list each as
  • . Minimum Qualifications: Bachelor's degree (BA/BS); Minimum four (4) years of experience successfully managing a large-scale, complex program encompassing multiple projects; Project Management Professional (PMP) certification, with a minimum of four (4) years' experience supporting a large corporation or government agency, preferably a large health care organization; Strong analytical, written, and verbal communication skills; Ability to obtain and maintain a VA Personal Identity Verification (PIV) credential and pass a VA background investigation; Must be authorized to work in the United States (no visa sponsorship). We can put these as
    • under

      Requirements

      (or Qualifications?). The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need separate sections for Requirements and Qualifications. Likely Requirements = minimum qualifications; Qualifications = desired qualifications. Skills maybe separate list of skills like analytical, written, verbal communication. But those are already in requirements. Could still create Skills section for those skills. However we must not create thin sections; we should prefer few substantive sections. But we have to follow headings list? It says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to include all. We should include only those with real content. So we can include About the role, Responsibilities, Requirements, Qualifications. Skills maybe covered already; but we could still include Skills if we have specific content. The posting mentions "Strong analytical, written, and verbal communication skills" which is a skill. Could also include other skills? Not much else. Might be okay to include Skills section with that. But we already have it in Requirements; duplicating might be redundant. Better to keep Requirements only and not create Skills unless we have additional skill specifics not covered. Since the instruction says prefer a few substantive sections over many thin ones, we can omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications. Now Qualifications (desired): Master’s degree; Eight (8) or more years of experience managing large-scale, complex programs or projects, preferably within a large health care organization; Experience supporting the Department of Veterans Affairs (VA) or Veterans Health Administration (VHA), particularly program/portfolio management, pilot or innovation programs, or value-based health care initiatives; Familiarity with federal health care environments and legislatively directed pilot programs, waiver processes, or enterprise transformation initiatives; Experience developing executive-level dashboards, status reporting, and portfolio-management tools for senior leadership, governance boards, or Congressional audiences; Additional relevant certification(s) (e.g., Lean Six Sigma, Change Management). We'll list as

      • . We must not include boilerplate like EEO, duplicated About Aptive, etc. We'll omit the About Aptive section entirely unless we consider it substantive. The instruction says preserve ALL substantive information; About Aptive describes the company, could be considered substantive. However it's duplicated; we can include once. But we don't have a heading for "About the company". Not in the list of headings. Could we include it under About the role? Probably not. The instruction says use those headings for sections; we could add a paragraph about the company under About the role? Might be mixing. Safer to omit About Aptive because not requested heading and we don't want to invent a heading. The instruction: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It might be okay to include other headings but they'd be non-standard. Safer to stick to given headings. So we omit About Aptive. Now produce HTML fragment:

        About the role

        ...

        Responsibilities

        • ...
        ...

        Requirements

        • ...
        ...

        Qualifications

        • ...
        ...
        Make sure to preserve all details exactly as in text. Let's copy the paragraphs verbatim. About the role paragraph: "We seek an experienced Project Manager to support the Department of Veterans Affairs (VA) Veterans Health Administration (VHA) Strategic Planning Division (SPD)/Center for Care and Payment Innovation (CCPI). CCPI advances VHA as a center for the development of data-driven, value-based health care solutions that transform and improve Veteran care while reducing cost and administrative burden, and leads legislatively directed pilot initiatives. This role will serve as the Task Order (TO) Project Manager, the primary Contractor point of contact with SPD/CCPI and the Contracting Officer’s Representative (COR), supporting a portfolio of up to six concurrent pilots and associated CCPI program management activities, working closely with the contract-aligned Program Director, workstream leads, and Government leadership to ensure task order requirements are executed consistently and in accordance with VA standards and enterprise objectives." We need to keep the slash and parentheses exactly. Responsibilities list: Let's extract each bullet as separate
      • . I'll write them: - Maintaining the Government-approved Project Management Plan (PMP), Project Charter, integrated schedule, milestones, RAID Log, and Stakeholder Registry - Developing and maintaining a Portfolio Management Dashboard that provides portfolio-wide visibility into status, milestones, risks, dependencies, decision points, and funding across all active pilots and workstreams - Leading a weekly status meeting with the COR and producing a Weekly Task Report - Preparing a semi-monthly budget and schedule tracker and a Monthly Progress Report covering budget, schedule, staffing, and performance - Preparing scoping letters for emerging in-scope requirements, as requested by the Government - Facilitating working sessions, stakeholder meetings, and decision-making forums - Maintaining centralized repositories, action trackers, and risk/issue logs necessary to support program continuity and portfolio oversight - Collaborating with the Program Director, Pilot Project Manager, Stakeholder Engagement & Communications Specialist, and Technical Writer/Editor to ensure coordinated execution across the SPD/CCPI portfolio and supporting development of executive-ready briefing materials for SES leadership, governance bodies, and Congressional reporting - Tracking approved scope changes - Maintaining organized project files using version control and records management practices - Providing Government customers with timely reporting on status, schedule, risks, issues, and performance metrics to support informed decision-making Check if any missing: The original also mentions "This includes leading a weekly status meeting with the COR and producing a Weekly Task Report; preparing a semi-monthly budget and schedule tracker and a Monthly Progress Report covering budget, schedule, staffing, and performance; and preparing scoping letters for emerging in-scope requirements, as requested by the Government." Already captured. Now Requirements list: - Bachelor's degree (BA/BS) - Minimum four (4) years of experience successfully managing a large-scale, complex program encompassing multiple projects - Project Management Professional (PMP) certification, with a minimum of four (4) years' experience supporting a large corporation or government agency, preferably a large health care organization - Strong analytical, written, and verbal communication skills - Ability to obtain and maintain a VA Personal Identity Verification (PIV) credential and pass a VA background investigation - Must be authorized to work in the United States (no visa sponsorship) Now Qualifications list: - Master’s degree - Eight (8) or more years of experience managing large-scale, complex programs or projects, preferably within a large health care organization - Experience supporting the Department of Veterans Affairs (VA) or Veterans Health Administration (VHA), particularly program/portfolio management, pilot or innovation programs, or value-based health care initiatives - Familiarity with federal health care environments and legislatively directed pilot programs, waiver processes, or enterprise transformation initiatives - Experience developing executive-level dashboards, status reporting, and portfolio-management tools for senior leadership, governance boards, or Congressional audiences - Additional relevant certification(s) (e.g., Lean Six