Planview Senior Business Systems Analyst

We need to output HTML fragment with sections: h3 headings for sections present with real content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like cookie/navigation/legal/EEO etc. Must not include sections with filler like "commensurate with experience". Must include only sections where posting has real specific content. We need to parse the job description. Key sections: - Job Summary (the paragraph after JOB SUMMARY). That's a prose description. - Essential Responsibilities: includes many bullet-like items (Planview Portfolios Administration, Workflow & Automation Configuration, Preferred Knowledge, Demand, Project, and Portfolio Management, Planview Reporting & Analytics, Data Governance & Platform Quality, Multi-Product Planview Experience, Technical Administration Requirements, Release & Environment Management, Governance & Operating Model Support). These are essentially responsibilities. - Education: Required Bachelor's Degree... Substitutions None Preferred None. - Experience: Required 5 - 7 years in IS/IT. - Licenses and Certifications: Required None Preferred -Highly Desired list. - Language (Other Than English): None. - Travel Required: 0% - 25%. - Physical, Mental Demands and Working Conditions: includes many statements about position type remote, teaches/trains others regularly, travel regularly, works primarily out-of-office selling products/services (sales employees) never, physical work site required no, lifting categories. - Pay Range: Minimum $79,300.00, Maximum $127,100.00, plus description. - Also there is a disclaimer, compliance requirement, etc. Those are boilerplate legal; we should remove them per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the disclaimer, compliance requirement, etc. - Also there is "Highmark may apply..." etc. That's part of pay description; we can keep the pay description but maybe remove the part about Highmark? It's part of the posting; but it's not boilerplate? It's still part of pay description. We'll keep it. - Also there is "California Consumer Privacy Act Employees, Contractors, and Applicants Notice" - that's legal boilerplate; remove. Thus sections to include: About the role? The posting has "JOB SUMMARY". We can map to "About the role" heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those as examples; we likely should use those headings where appropriate. For job summary we can use About the role. For essential responsibilities we can use Responsibilities. For education and experience we can use Qualifications (or Requirements?). Usually Qualifications includes education and experience. Could split: Requirements (maybe experience) and Qualifications (education). But we have both education and experience. Could combine into Qualifications. But we need to follow instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications (combining education+experience+licenses), Skills (maybe from "Skills include" etc), Pay, Schedule (Travel Required?), Benefits? Not present. There's no explicit benefits section. So we skip Benefits. We also have "Physical, Mental Demands and Working Conditions" - could be part of Qualifications? Or maybe we could add a section "Working Conditions"? Not in the list of examples but we could still use h3 for any section heading; the instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those headings. However we have content that doesn't fit neatly: Physical demands etc. Could be omitted? But we must preserve ALL substantive information; we cannot drop it. So we need a section for it. Could use "Requirements" heading for physical demands? Or "Qualifications"? Might be okay to add a custom heading like "Working Conditions". The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, just that we should use h3 for section headings (the examples). So we can use any heading as long as it's h3. We'll include a section for Working Conditions. Similarly we have "Licenses and Certifications" - could be part of Qualifications. We also have "Skills include ..." under Technical Administration Requirements etc. There's a "Skills include Data mapping..." etc. Also earlier there is "Preferred Knowledge" etc. So we can gather skills. We need to output only HTML fragment, no markdown fences. We'll structure:

About the role

Job summary paragraph.

Responsibilities

• ... each bullet from essential responsibilities.

We need to capture all bullet points from Essential Responsibilities. The text includes many lines; we need to extract each bullet as separate

. The content includes headings like "Planview Portfolios Administration", then a list of sub-items (User, group, and role administration...). We need to preserve all substantive information; we can treat each line as a bullet. However we must not lose detail. Could group under headings but still as

. Probably easiest: each line that ends with a period or is a distinct item becomes

. But we need to be careful not to split sentences incorrectly. Let's extract the Essential Responsibilities section text: "ESSENTIAL RESPONSIBILITIES Planview Portfolios Administration Demonstrated experience administering Planview Portfolios including User, group, and role administrationSecurity model configurationAccess provisioning and deprovisioningScreen, menu, and navigation configurationObject and attribute managementLookup and reference table administrationOrganizational structure managementFinancial structure administrationResource management configurationPortfolio hierarchy management Workflow & Automation Configuration Experience configuring and supporting Lifecycle managementScripted DialogsConditional logicAutomated notificationsApproval workflowsStage-gate processesDemand management workflowsProject intake processesGovernance checkpointsAutomated field updates Preferred Knowledge Lifecycle state transitionsBusiness rules configurationWorkflow troubleshootingWorkflow optimization Demand, Project, and Portfolio Management Strong understanding of Demand intake processesProject governancePortfolio managementStrategic planningResource capacity planningFinancial planning and budgetingCapital and operational expenditure trackingBenefit realization planningProgram management concepts Planview Reporting & Analytics Experience developing and maintaining Planview reportsExecutive dashboardsOperational dashboardsGovernance dashboardsPortfolio health reportingResource utilization reportingFinancial management reportingData quality reporting Preferred Power BI integrationExecutive KPI developmentData visualization Data Governance & Platform Quality Experience supporting Data quality initiativesField rationalization effortsConfiguration governanceReference data managementTaxonomy managementAudit reviewsCompliance reporting Responsibilities include Identifying unused data structuresReviewing obsolete fields and formsReducing technical debtMaintaining platform standardsSupporting governance processes Multi-Product Planview Experience Planview Enterprise Architecture (EA) Knowledge of Application inventoriesTechnology inventoriesBusiness capabilitiesCapability mappingArchitecture roadmapsInvestment planningApplication lifecycle management Planview AgilePlace Experience with Board administrationKanban configurationTeam workflowsValue stream managementMetrics and reportingWork item configuration Planview ProjectPlace Experience with Workspace administrationUser provisioningCollaboration featuresDocument managementBoard configurationReporting Technical Administration Requirements Integrations Experience supporting integrations between Planview and Microsoft Entra ID (Azure AD)JiraServiceNowSAPWorkdayPower BIMicrosoft TeamsSharePoint Skills include Data mappingAPI troubleshootingUser synchronizationIntegration monitoringError analysis Release & Environment Management Experience with Development environmentsTest environmentsProduction environmentsConfiguration migrationsRelease planningRegression testingSaaS release reviews Responsibilities include Evaluating quarterly Planview releasesImpact assessmentsRegression testing coordinationPromotion governanceRelease documentation Governance & Operating Model Support Experience participating in or supporting Platform governance boardsChange Advisory Boards (CAB)Enhancement intake processesPrioritization reviewsPlatform roadmapsStandards reviewsOperational reviews Preferred Understanding Of RACI modelsSaaS governance frameworksConfiguration management practicesService management processes" We need to split into sensible bullet items. Could treat each capitalized heading as a category and then list its sub-items as separate bullets. But we need to preserve all info; we can just output each sentence or clause as a bullet. Simplify: We'll create a

and for each distinct responsibility line we put
• . We'll try to capture the main bullet points as they appear separated by spaces and capital letters. Better approach: Recognize that the text uses capitalized headings without punctuation; we can insert line breaks before each capitalized word that starts a new heading (like "Planview Portfolios Administration", "Workflow & Automation Configuration", "Preferred Knowledge", "Demand, Project, and Portfolio Management", "Planview Reporting & Analytics", "Data Governance & Platform Quality", "Multi-Product Planview Experience", "Technical Administration Requirements", "Release & Environment Management", "Governance & Operating Model Support"). Under each heading there are details. We could output as nested lists? But instruction only says use
  • for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can keep flat. We'll produce
  • items that combine heading and its details as a sentence. For example:
  • Planview Portfolios Administration: Demonstrated experience administering Planview Portfolios including user, group, and role administration; security model configuration; access provisioning and deprovisioning; screen, menu, and navigation configuration; object and attribute management; lookup and reference table administration; organizational structure management; financial structure administration; resource management configuration; portfolio hierarchy management.
  Similarly for others. We'll need to convert the run-on text into proper sentences with semicolons. Let's extract each section. 1. Planview Portfolios Administration: Original: "Planview Portfolios Administration Demonstrated experience administering Planview Portfolios including User, group, and role administrationSecurity model configurationAccess provisioning and deprovisioningScreen, menu, and navigation configurationObject and attribute managementLookup and reference table administrationOrganizational structure managementFinancial structure administrationResource management configurationPortfolio hierarchy management" We need to add spaces before each capitalized term after "including". We'll produce: "Demonstrated experience administering Planview Portfolios including: user, group, and role administration; security model configuration; access provisioning and deprovisioning; screen, menu, and navigation configuration; object and attribute management; lookup and reference table administration; organizational structure management; financial structure administration; resource management configuration; portfolio hierarchy management." 2. Workflow & Automation Configuration: Original: "Workflow & Automation Configuration Experience configuring and supporting Lifecycle managementScripted DialogsConditional logicAutomated notificationsApproval workflowsStage-gate processesDemand management workflowsProject intake processesGovernance checkpointsAutomated field updates Preferred Knowledge Lifecycle state transitionsBusiness rules configurationWorkflow troubleshootingWorkflow optimization" Wait there is "Preferred Knowledge" after that; Actually the text seems to have "Preferred Knowledge" as a separate heading after Workflow & Automation Configuration. Let's re-evaluate: The original snippet: "Workflow & Automation Configuration Experience configuring and supporting Lifecycle managementScripted DialogsConditional logicAutomated notificationsApproval workflowsStage-gate processesDemand management workflowsProject intake processesGovernance checkpointsAutomated field updates Preferred Knowledge Lifecycle state transitionsBusiness rules configurationWorkflow troubleshootingWorkflow optimization Demand, Project, and Portfolio Management Strong understanding of Demand intake processesProject governancePortfolio managementStrategic planningResource capacity planningFinancial planning and budgetingCapital and operational expenditure trackingBenefit realization planningProgram management concepts Planview Reporting & Analytics Experience developing and maintaining Planview reportsExecutive dashboardsOperational dashboardsGovernance dashboardsPortfolio health reportingResource utilization reportingFinancial management reportingData quality reporting Preferred Power BI integrationExecutive KPI developmentData visualization Data Governance & Platform Quality Experience supporting Data