ERP Organizational Change Management Trainer job
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections have content.
Let's extract:
- About the role: Could include description of the role: "In partnership with the Office of the Chief Administrative Officer (CAO) and the Office of the Director of Finance, the Office of Innovation and Technology (OIT) is undertaking a major Citywide project to modernize core financial, grants, procurement, and supply chain business processes. This project (Optimize Procurement and Accounting Logistics Enterprise Resource Planning and Data Warehouse/Business Intelligence Tool, or “OPAL ERP and DW/BI project”) will replace the existing General Ledger and Procurement systems (i.e. FAMIS, ADPICS, ACIS, PHLContracts, etc.) that support these business processes and will enable the City to realize benefits such as reducing transaction processing time and effort, providing better access to information for reporting and analysis, and making it easier to onboard new employees into these functions. The Enterprise Resource Planning (ERP) Organizational Change Management Trainer is responsible for designing and delivering training for the OPAL ERP and DW/BI project. This role requires skills in change management, including the ability to create structured plans for implementing, communicating, and monitoring changes. The trainer should be proficient in conducting change impact assessments, stakeholder analysis, and readiness assessments. Additionally, the trainer must possess both technical and teaching skills to ensure that users can efficiently and effectively understand how to use the ERP and its supporting systems."
That's role description.
- Responsibilities: The "Essential Functions" section lists responsibilities: Training Program Design and Delivery, Change Management, Technical Expertise, User Support and Relationship Building. We can list as bullet points.
- Requirements: Might be qualifications? The posting has "Qualifications" section: Bachelor’s degree ... Minimum of five years relevant experience ... Experience with implementing ERP and/or DW/BI solutions is strongly preferred. Minimum of five years relevant experience as a technical trainer, training coordinator, or any other similar role. Proven work experience as an IT Trainer, Technical Trainer or similar role with Workday ERP, preferred but not required. Also maybe "Competencies, Knowledge, Skills And Abilities" could be Skills.
Thus we can have:
- Qualifications: bullet list of education and experience requirements.
- Skills: bullet list of competencies: Knowledge of Full Systems Development Lifecycle (SDLC). Ability to keep data confidential. Strong problem solving and analytic skill sets. Strong written and oral communication skills (including ability to present ideas in user-friendly, business-friendly, and technical language) and interpersonal skills with a focus on rapport-building, listening, and questioning skills. Strong meeting facilitation and interviewing skills. Meeting presentation and end user training delivery skills. Ability to work well with individuals at all levels within and outside the organization. Ability to work well under pressure in a fast-paced organization. Supervising, coaching and collaborating skills; and Hands on experience with learning management and training material development and delivery tools.
- Benefits: The posting includes a section "Discover the Perks of Being a City of Philadelphia Employee:" with bullet points: Comprehensive health coverage for employees and their eligible dependents; wellness program offers eligibility into the discounted medical plan; Employees receive paid vacation, sick leave, and holidays; Generous retirement savings options are available; Pay off your student loans faster - As a qualifying employer, City of Philadelphia employees are eligible to participate in the Public Service Loan Forgiveness program. Join the ranks of hundreds of employees who have already benefited from this program and achieved student loan forgiveness. Enjoy a Free Commute on SEPTA - Starting September 1, 2023, eligible City employees will no longer have to worry about paying for SEPTA public transportation. Whether you're a full-time, part-time, or provisional employee, you can seize the opportunity to sign up for the SEPTA Key Advantage Program and receive free Key cards for free rides on SEPTA buses, trains, trolleys, and regional rails. Unlock Tuition Discounts and Scholarships - The City of Philadelphia has forged partnerships with over a dozen esteemed colleges and universities in the area, ensuring that our employees have access to a wide range of tuition discounts and scholarships. Experience savings of 10% to 40% on your educational expenses, extending not only to City employees but in some cases, spouse and dependents too! Join the City of Philadelphia team today and seize these incredible benefits designed to enhance your financial well-being and personal growth!
Thus we have benefits content.
- Pay: The posting includes "Informations complémentaires Salary Range cannot exceed $90,000". That's a pay info: Salary Range cannot exceed $90,000. So we have pay info.
- Schedule: The posting includes "Work Setting: in-person (onsite)". That's schedule/setting. Also maybe "Effective May 22, 2023, vaccinations are no longer required..." but that's not schedule. So we can include schedule: In-person (onsite) work setting.
We also have other metadata: "The successful applicant will be required to submit to a fingerprint background check per CJIS policy." "The successful candidate must be a city of Philadelphia resident within six months of hire". That could be included maybe in Requirements or Qualifications? Could be separate but we can fold into a short p or maybe include in Requirements as additional requirement. However instruction: fold minor metadata into a short
or drop it. We could include a short paragraph after sections for such metadata. But we need to preserve all substantive information. So we should include that info somewhere, maybe as a paragraph after sections, not as a heading.
We also have description of company at start: "Description De L'entreprise A best-in-class city that attracts best-in-class talent, Philadelphia is an incredible place to build a career. From our thriving arts scene and rich history to our culture of passion and grit, there are countless reasons to love living and working here. With a workforce of over 30,000 people, and more than 1,000 different job categories, the City of Philadelphia offers boundless opportunities to make an impact. As an employer, the City of Philadelphia values inclusion, integrity, innovation, empowerment, and hard work above all else. We offer a vibrant work environment, comprehensive health care and benefits, and the experience you need to grow and excel. If you’re interested in working with a passionate team of people who care about the future of Philadelphia, start here. What We Offer Impact - The work you do here matters to millions. Growth - Philadelphia is growing, why not grow with it? Diversity & Inclusion - Find a career in a place where everyone belongs. Benefits - We Care About Your Well Being. The Office of Innovation & Technology (OIT) is the central IT agency for the City of Philadelphia headed by the Chief Information Officer (CIO). OIT oversees all major information and communications technology initiatives for the City of Philadelphia - increasing the effectiveness of the information technology infrastructure, where the services provided are advanced, optimized, and responsive to the needs of the City of Philadelphia’s businesses, residents, and visitors. OIT responsibilities include: identifying the most effective approach for implementing new information technology directions throughout city government; improving the value of the city’s technology assets and the return on the city’s technology investments; ensuring data security continuity; planning for continuing operations in the event of disruption of information technology or communications services; and supporting accountable, efficient and effective government across every city department, board, commission and agency."
That's a lot of company description. We could incorporate into "About the role" or maybe a separate "About the company" but not in allowed headings list. The allowed headings are only those eight. We could put company description in a paragraph before sections, as it's substantive. 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. Probably we should stick to those headings only. So we can put company description in a
before any headings.
Thus final HTML: start with a
containing company description (maybe trimmed to avoid duplication). Then
About the role
with paragraph describing role. Then Responsibilities
with - ... etc. Then
Requirements
maybe? Actually we have Qualifications and Skills separate. Could combine Requirements and Qualifications? But we have both sections available. We'll use Qualifications for education/experience, Skills for competencies. Requirements maybe we could omit if no distinct content besides qualifications. But we have "Qualifications" section; we could treat that as Requirements. However we also have separate "Qualifications" heading in posting. So we can map that to Qualifications section. And "Competencies, Knowledge, Skills And Abilities" to Skills section.
Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. Possibly also Requirements if we have extra like background check, residency, fingerprint etc. Those could be placed under Requirements as a list.
Let's extract those: "The successful applicant will be required to submit to a fingerprint background check per CJIS policy." "The successful candidate must be a city of Philadelphia resident within six months of hire". Also maybe "Effective May 22, 2023, vaccinations are no longer required for new employees that work in non-medical, non-emergency or patient facing positions with the City of Philadelphia. As a result, only employees in positions providing services that are patient-facing medical care (ex: Nurses, doctors, emergency medical personnel), must be fully vaccinated." That's also a condition. Also "The City of Philadelphia is an Equal Opportunity employer..." that's boilerplate EEO, we should remove. Also "If you believe you were discriminated against..." remove.
Thus we can include a Requirements section with bullet points: Fingerprint background check per CJIS policy; Must be a City of Philadelphia resident within six months of hire; Vaccination requirement: only required for patient-facing medical care positions (this role is non-medical, so not required). But we should not invent; we can state the vaccination policy as given. However it's a bit generic; but it's substantive. We'll include.
Now Benefits: we have list as above.
Pay: Salary Range cannot exceed $90,000.
Schedule: Work Setting: in-person (onsite).
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
Now we need to avoid
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections have content. Let's extract: - About the role: Could include description of the role: "In partnership with the Office of the Chief Administrative Officer (CAO) and the Office of the Director of Finance, the Office of Innovation and Technology (OIT) is undertaking a major Citywide project to modernize core financial, grants, procurement, and supply chain business processes. This project (Optimize Procurement and Accounting Logistics Enterprise Resource Planning and Data Warehouse/Business Intelligence Tool, or “OPAL ERP and DW/BI project”) will replace the existing General Ledger and Procurement systems (i.e. FAMIS, ADPICS, ACIS, PHLContracts, etc.) that support these business processes and will enable the City to realize benefits such as reducing transaction processing time and effort, providing better access to information for reporting and analysis, and making it easier to onboard new employees into these functions. The Enterprise Resource Planning (ERP) Organizational Change Management Trainer is responsible for designing and delivering training for the OPAL ERP and DW/BI project. This role requires skills in change management, including the ability to create structured plans for implementing, communicating, and monitoring changes. The trainer should be proficient in conducting change impact assessments, stakeholder analysis, and readiness assessments. Additionally, the trainer must possess both technical and teaching skills to ensure that users can efficiently and effectively understand how to use the ERP and its supporting systems." That's role description. - Responsibilities: The "Essential Functions" section lists responsibilities: Training Program Design and Delivery, Change Management, Technical Expertise, User Support and Relationship Building. We can list as bullet points. - Requirements: Might be qualifications? The posting has "Qualifications" section: Bachelor’s degree ... Minimum of five years relevant experience ... Experience with implementing ERP and/or DW/BI solutions is strongly preferred. Minimum of five years relevant experience as a technical trainer, training coordinator, or any other similar role. Proven work experience as an IT Trainer, Technical Trainer or similar role with Workday ERP, preferred but not required. Also maybe "Competencies, Knowledge, Skills And Abilities" could be Skills. Thus we can have: - Qualifications: bullet list of education and experience requirements. - Skills: bullet list of competencies: Knowledge of Full Systems Development Lifecycle (SDLC). Ability to keep data confidential. Strong problem solving and analytic skill sets. Strong written and oral communication skills (including ability to present ideas in user-friendly, business-friendly, and technical language) and interpersonal skills with a focus on rapport-building, listening, and questioning skills. Strong meeting facilitation and interviewing skills. Meeting presentation and end user training delivery skills. Ability to work well with individuals at all levels within and outside the organization. Ability to work well under pressure in a fast-paced organization. Supervising, coaching and collaborating skills; and Hands on experience with learning management and training material development and delivery tools. - Benefits: The posting includes a section "Discover the Perks of Being a City of Philadelphia Employee:" with bullet points: Comprehensive health coverage for employees and their eligible dependents; wellness program offers eligibility into the discounted medical plan; Employees receive paid vacation, sick leave, and holidays; Generous retirement savings options are available; Pay off your student loans faster - As a qualifying employer, City of Philadelphia employees are eligible to participate in the Public Service Loan Forgiveness program. Join the ranks of hundreds of employees who have already benefited from this program and achieved student loan forgiveness. Enjoy a Free Commute on SEPTA - Starting September 1, 2023, eligible City employees will no longer have to worry about paying for SEPTA public transportation. Whether you're a full-time, part-time, or provisional employee, you can seize the opportunity to sign up for the SEPTA Key Advantage Program and receive free Key cards for free rides on SEPTA buses, trains, trolleys, and regional rails. Unlock Tuition Discounts and Scholarships - The City of Philadelphia has forged partnerships with over a dozen esteemed colleges and universities in the area, ensuring that our employees have access to a wide range of tuition discounts and scholarships. Experience savings of 10% to 40% on your educational expenses, extending not only to City employees but in some cases, spouse and dependents too! Join the City of Philadelphia team today and seize these incredible benefits designed to enhance your financial well-being and personal growth! Thus we have benefits content. - Pay: The posting includes "Informations complémentaires Salary Range cannot exceed $90,000". That's a pay info: Salary Range cannot exceed $90,000. So we have pay info. - Schedule: The posting includes "Work Setting: in-person (onsite)". That's schedule/setting. Also maybe "Effective May 22, 2023, vaccinations are no longer required..." but that's not schedule. So we can include schedule: In-person (onsite) work setting. We also have other metadata: "The successful applicant will be required to submit to a fingerprint background check per CJIS policy." "The successful candidate must be a city of Philadelphia resident within six months of hire". That could be included maybe in Requirements or Qualifications? Could be separate but we can fold into a short p or maybe include in Requirements as additional requirement. However instruction: fold minor metadata into a short
or drop it. We could include a short paragraph after sections for such metadata. But we need to preserve all substantive information. So we should include that info somewhere, maybe as a paragraph after sections, not as a heading. We also have description of company at start: "Description De L'entreprise A best-in-class city that attracts best-in-class talent, Philadelphia is an incredible place to build a career. From our thriving arts scene and rich history to our culture of passion and grit, there are countless reasons to love living and working here. With a workforce of over 30,000 people, and more than 1,000 different job categories, the City of Philadelphia offers boundless opportunities to make an impact. As an employer, the City of Philadelphia values inclusion, integrity, innovation, empowerment, and hard work above all else. We offer a vibrant work environment, comprehensive health care and benefits, and the experience you need to grow and excel. If you’re interested in working with a passionate team of people who care about the future of Philadelphia, start here. What We Offer Impact - The work you do here matters to millions. Growth - Philadelphia is growing, why not grow with it? Diversity & Inclusion - Find a career in a place where everyone belongs. Benefits - We Care About Your Well Being. The Office of Innovation & Technology (OIT) is the central IT agency for the City of Philadelphia headed by the Chief Information Officer (CIO). OIT oversees all major information and communications technology initiatives for the City of Philadelphia - increasing the effectiveness of the information technology infrastructure, where the services provided are advanced, optimized, and responsive to the needs of the City of Philadelphia’s businesses, residents, and visitors. OIT responsibilities include: identifying the most effective approach for implementing new information technology directions throughout city government; improving the value of the city’s technology assets and the return on the city’s technology investments; ensuring data security continuity; planning for continuing operations in the event of disruption of information technology or communications services; and supporting accountable, efficient and effective government across every city department, board, commission and agency." That's a lot of company description. We could incorporate into "About the role" or maybe a separate "About the company" but not in allowed headings list. The allowed headings are only those eight. We could put company description in a paragraph before sections, as it's substantive. 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. Probably we should stick to those headings only. So we can put company description in a
before any headings. Thus final HTML: start with a
containing company description (maybe trimmed to avoid duplication). Then
About the role
with paragraph describing role. ThenResponsibilities
with- ... etc. Then
Requirements
maybe? Actually we have Qualifications and Skills separate. Could combine Requirements and Qualifications? But we have both sections available. We'll use Qualifications for education/experience, Skills for competencies. Requirements maybe we could omit if no distinct content besides qualifications. But we have "Qualifications" section; we could treat that as Requirements. However we also have separate "Qualifications" heading in posting. So we can map that to Qualifications section. And "Competencies, Knowledge, Skills And Abilities" to Skills section. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. Possibly also Requirements if we have extra like background check, residency, fingerprint etc. Those could be placed under Requirements as a list. Let's extract those: "The successful applicant will be required to submit to a fingerprint background check per CJIS policy." "The successful candidate must be a city of Philadelphia resident within six months of hire". Also maybe "Effective May 22, 2023, vaccinations are no longer required for new employees that work in non-medical, non-emergency or patient facing positions with the City of Philadelphia. As a result, only employees in positions providing services that are patient-facing medical care (ex: Nurses, doctors, emergency medical personnel), must be fully vaccinated." That's also a condition. Also "The City of Philadelphia is an Equal Opportunity employer..." that's boilerplate EEO, we should remove. Also "If you believe you were discriminated against..." remove. Thus we can include a Requirements section with bullet points: Fingerprint background check per CJIS policy; Must be a City of Philadelphia resident within six months of hire; Vaccination requirement: only required for patient-facing medical care positions (this role is non-medical, so not required). But we should not invent; we can state the vaccination policy as given. However it's a bit generic; but it's substantive. We'll include. Now Benefits: we have list as above. Pay: Salary Range cannot exceed $90,000. Schedule: Work Setting: in-person (onsite). Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to avoid