Maintenance & Reliability Manager for Chemicals and Natural Resources

We need to output HTML fragment with sections: About the role? The posting includes "WHO WE ARE" (company description) and "THE WORK" (role description) and "HERE’S WHAT YOU’LL NEED" (requirements) and "BONUS POINTS IF YOU HAVE" (additional qualifications). Also compensation and benefits info. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: could be "THE WORK" description (lead delivery...). That's responsibilities. - Responsibilities: we can list bullet points from THE WORK. - Requirements: from HERE’S WHAT YOU’LL NEED (mandatory). - Qualifications: maybe BONUS POINTS IF YOU HAVE (preferred qualifications). Could also include education etc. - Skills: maybe list specific skills like RCM, FMEA, etc. But we can incorporate into requirements. - Benefits: we have benefits description: "Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off." - Pay: we have salary ranges per location. We need to include Pay section if posting actually states them. Yes, they have salary ranges per location. So we should include a Pay section with that info. Should we list all? Probably we can include a

with each location and range. Or we can summarize? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the salary ranges as given. Could present as a
• California: $94,400 to $293,800
etc. - Schedule: not mentioned besides travel up to 75% (travel requirement). That's not schedule like full-time/part-time. No explicit schedule. So we should not create Schedule section because no specific schedule info. - Also we have travel requirement: could be included under Responsibilities or a separate note. Could be a bullet under Responsibilities. - Also we have "Role Location Annual Salary Range" table. We'll include that in Pay. - Also we have "Accenture offers a market competitive suite of benefits..." that's Benefits. - Also we have "Compensation at Accenture varies depending on a wide array of factors..." that's more about Pay but we already have ranges. - Also we have "As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below." That's intro to Pay. - Also we have "We anticipate this job posting will be posted until 11/06/2026." That's metadata; we can drop or put in a short

maybe under a generic metadata? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short

for posting date. - Also we have "Requesting an Accommodation", "Equal Employment Opportunity Statement", etc. Those are boilerplate to remove. - Also we have "Other Employment Statements" etc. Remove. - Also we have "Visit us at accenture.com." That's part of WHO WE ARE; we can keep as part of About the role? Actually WHO WE ARE is company description; we could include an "About the company" but not required headings. We could incorporate into About the role? The instruction: Use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. "About the role" could include WHO WE ARE and THE WORK summary? But we already have Responsibilities for detailed duties. Maybe About the role includes a brief overview: "Lead delivery of maintenance and reliability engagements..." That's from THE WORK. We'll put that as a

under About the role. - Responsibilities: bullet list of duties from THE WORK. - Requirements: mandatory from HERE’S WHAT YOU’LL NEED. - Qualifications: bonus points. - Skills: maybe we can list specific technical skills: RCM, criticality analysis, FMEA, RCA, work management, EAM/APM deployment, etc. But we could also put them under Requirements or Skills. Since we have both Requirements and Skills headings, we need to decide distribution. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one? But we must use headings only when posting has real, specific content for it. We have both mandatory requirements and bonus qualifications; we could treat Requirements as mandatory, Qualifications as bonus. Skills could be derived from mandatory requirements (e.g., hands-on command of reliability practices). But we could also make a Skills section listing those specific practices. However that might be thin. Better to not create Skills if not enough distinct content. We'll see. We have mandatory requirements: 5+ years maintenance reliability experience in Chemicals and Natural Resources Industry and/or consulting; 5+ years leading delivery of consulting or industry programs; 2+ years industry context in sub-industries; 1+ years hands-on command of reliability practices (RCM, criticality analysis, FMEA, RCA, work management). Those are requirements. Bonus points: consulting experience with top-tier firm; Bachelor's degree or equivalent; experience deploying or operating EAM/APM platforms; experience managing workstream financials, scope, quality; ability to build business cases and present recommendations; full-lifecycle EAM or APM implementation experience; familiarity with relevant standards and codes; experience applying AI or advanced analytics to maintenance and reliability; strong communication and interpersonal skills; MBA or graduate degree. We could put those under Qualifications. Thus we may not need a separate Skills section. Benefits: we have description. Pay: we have salary ranges. Schedule: none. Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We also may include a short

for posting date metadata. Now format: Use

for each section heading. Use

• for lists. Use

  for prose. We must not include any extra HTML like or . Just the fragment. Let's craft. About the role:

  Lead delivery of maintenance and reliability engagements across one or more of the five sub-industries, owning workstreams and day-to-day client relationships. This role requires industry context in one or more of the following sub-industries: basic and petrochemicals, specialty chemicals, metals & mining, forest products, and building materials. Assess client reliability and asset management programs, define future-state improvements, and build the business cases (cost/benefit, KPIs, resource plans) that justify them. Apply reliability practices in the field: RCM, criticality ranking, FMEA, RCA, and work management (identification, planning, scheduling, execution). Deploy EAM and APM solutions and connect them to measurable reliability outcomes, working across process and technology. Translate asset and operational data into recommendations that operations and plant leaders can act on. Support origination: contribute to proposals, value propositions, and sales campaigns, and grow into an origination role. Manage engagement financials and quality for your workstreams, including forecasting and scope. Lead and develop consultants and engineers on your team, and drive workforce adoption and change management as part of delivery. Travel is required for this role and could vary up to 75%.

  That's a long paragraph but okay. Responsibilities: we could break into bullet list. However the above paragraph already covers many responsibilities. To avoid duplication, we could keep About the role as a brief overview and Responsibilities as bullet list of specific duties. But we must preserve all substantive information; not repeat. We could split: About the role short summary, Responsibilities bullet list with details. Let's craft About the role as a concise summary: "Lead delivery of maintenance and reliability engagements across one or more of the five sub-industries, owning workstreams and day-to-day client relationships." Then Responsibilities bullet list with the rest. But we need to ensure we don't lose any detail. Let's extract responsibilities from THE WORK: - Lead delivery of maintenance and reliability engagements across one or more of the five sub-industries, owning workstreams and day-to-day client relationships. - Assess client reliability and asset management programs, define future-state improvements, and build the business cases (cost/benefit, KPIs, resource plans) that justify them. - Apply reliability practices in the field: RCM, criticality ranking, FMEA, RCA, and work management (identification, planning, scheduling, execution). - Deploy EAM and APM solutions and connect them to measurable reliability outcomes, working across process and technology. - Translate asset and operational data into recommendations that operations and plant leaders can act on. - Support origination: contribute to proposals, value propositions, and sales campaigns, and grow into an origination role. - Manage engagement financials and quality for your workstreams, including forecasting and scope. - Lead and develop consultants and engineers on your team, and drive workforce adoption and change management as part of delivery. - Travel is required for this role and could vary up to 75%. We'll put those as
  • ...
  . Now Requirements (mandatory): - 5+ years of maintenance, reliability, and asset management experience in Chemicals and Natural Resources Industry and/or consulting. - 5+ years leading delivery of consulting or industry programs, with a track record of measurable results. - 2+ years of Industry context in one or more of: basic and petrochemicals, specialty chemicals, metals & mining, forest products, and building materials. - 1+ years of Hands-on command of reliability practices: RCM, criticality analysis, FMEA, RCA, and work management. We'll list as bullet. Qualifications (bonus points): - Consulting experience with a top-tier firm. - Bachelor's degree or equivalent (minimum 12 years) work experience. (If associate degree, must have a minimum of 6 years’ work experience) - Experience deploying or operating EAM and/or APM platforms (e.g., SAP, Maximo, IFS, AVEVA, GE, AspenTech). - Experience managing workstream financials, scope, and quality. - Ability to build business cases and present recommendations to operations and plant leadership. - Full-lifecycle EAM or APM implementation experience. - Familiarity with relevant standards and codes (e.g., ISO 55000, ISO 14224, API, SMRP body of knowledge). - Experience applying AI or advanced analytics to maintenance and reliability. - Strong communication and interpersonal skills, both written and verbal. - MBA or graduate degree. We'll list as bullet. Benefits: - Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. We'll put as

  maybe. Pay: We need to present the salary ranges per location. Could be a

  with each location. List: - California: $94,400 to $293,800 - Colorado: $94,400 to $253,800 - Connecticut: $94,400 to $253,800 - District of Columbia: $100,500 to $270,300 - Illinois: $87,400 to $253,800 - Maine: $80,400 to $216,200 - Maryland: $94,400 to $253,800 - Massachusetts: $94,400 to $270,300 - Minnesota: $94,4