Planner II - Asset Data Mgmt

We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes: "The Role" description (maybe "About the role") – we can use

About the role

and then paragraph(s). Then "What You’ll Do" is responsibilities –

Responsibilities

with list of duties. Then "Qualifications" heading –

Qualifications

with list (maybe bullet). Then "What You’ll Bring" includes qualifications details – but we already have Qualifications. Actually "Qualifications" heading appears in posting: "Qualifications What You’ll Bring". So we can combine. Then "Skills" and "Abilities" maybe separate sections? The instruction: use headings for Skills, Benefits, Pay, Schedule if present. There's a "Skills" bullet list under Knowledge - Skills - Abilities. We could make a Skills section. There's no explicit Pay or Schedule specifics. There's mention of benefits: "What We Offer At Wells, we’re proud to support our employees with comprehensive benefits that enhance health, financial wellness, and include paid time off (PTO). Eligible employees may also receive an annual incentive bonus based on Company performance." That's benefits content. So we can include Benefits section. No explicit Pay or Schedule specifics, so omit those sections. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, About Us, etc. We should keep substantive info: company description maybe not needed? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" maybe considered boilerplate? It's descriptive but not required? It says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Us" is substantive about company but maybe not required for job posting? It's not about the role. Might be considered extra but still substantive. However typical job posting includes company overview; but instruction says remove boilerplate, but "About Us" might be considered boilerplate? Not sure. Safer to keep it? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About Us is not listed; it's not EEO. So we could keep it. But we need to decide sections: we have About the role, Responsibilities, Qualifications, Skills, Benefits. Could also include "About the company" but not in allowed headings list. The allowed headings list includes only those specific ones; we should not create other headings. So we should not add a heading for About Us. We could incorporate that info into a paragraph under About the role? But that would be mixing. Better to omit About Us entirely? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit About Us, we lose substantive info about company. However maybe it's considered not essential to the role; but still substantive. The allowed headings list is restrictive; we could still include a

without a heading for company overview. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we could have other headings? It says use h3 for section headings (e.g., ...). Likely they expect only those headings. Safer to stick to those. We can put company overview as a paragraph before the first heading? That would be outside any heading; maybe acceptable. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So we can output a series of elements: maybe a

for company overview, then

About the role

etc. We must not include duplicated lines. We'll need to extract responsibilities list from "What You’ll Do". That's a long paragraph with many duties separated by periods. We need to turn into

• items. We should split each duty into separate list items. Let's parse. Responsibilities text: "Establishes and maintains effective working relationships with asset data management vendors (e.g., Metanoia) to maximize system value and outcomes for Wells. Ensures the standardization and optimization of asset manuals, training materials, and related documentation in coordination with the Document Control team Develops and sustains internal partnerships to support the Management of Change (MOC) process and associated documentation. Provides oversight to ensure MOC activities are executed in accordance with established requirements, including timely documentation, approval, and implementation of changes. Partners with the Wells IT department to support the design, development, administration, and governance of reliability data systems and functional storage platforms. Coordinates maintenance and reliability data requirements with internal IT resources, leads efforts to develop an enterprise troubleshooting knowledge network utilizing available data sources, and evaluates and applies best-in-class solutions (including AI-enabled platforms) to improve the delivery of accurate, actionable information to plant-floor teams. Establishes, implements, and sustains the Work Order Quality Check review process across all Wells facilities. Collaborates with site planners to identify work order quality gaps, align on corrective actions, and drive consistent process adherence and continuous improvement. Reviews, organizes, and coordinates all incoming non-emergent work orders. Reviews for start and completion dates, work type, scope, priority, and estimates of man-hours. Uploads employee work schedule into Viziya utilizing input from maintenance supervisors. Compare and contrasts available labor force to the forecasted work demand and machine availability as well as material needs to develop a forecasted work schedule. Provides forecasted work schedule and collaborates with operations, maintenance and reliability teams to review and approve a work schedule for the following week. Plans schedules and prepares detailed repair type work orders. Includes materials, skilled labor, work plan, and asset availability. Responsible for establishing and resetting daily priorities of work as necessary for prompt completion of work assignments and adherence to schedules. Creates and enhances PM reference procedures and provides training on these documents. Create parts lists and kits for PM's and ensure that all items are on hand as needed by working with purchasing and inventory groups. Organize and manage the assignment of predictive documentation responsibilities associated with Planned Work. Plans and organizes regular equipment preventative and predictive maintenance functions for all fluid utilities assets and coordinates with Operations to manage the annuals/REOs for production-based equipment." We need to ensure each bullet is a distinct duty. Some sentences are fragments; we can keep as is. Now Qualifications section: The posting has "Qualifications What You’ll Bring". Then bullet list: "Certified Maintenance Planner. Associate’s degree in engineering or related field preferred, CMRP certification preferred. 3-5 years in a relative manufacturing industry as a maintenance planner. 5-10 years in the maintenance and or reliability field in an industrial setting. Oracle EAM, Viziya and or other maintenance planning platforms.Knowledge - Demonstrated knowledge of industrial manufacturing equipment and processes; proactive work planning and scheduling practices; and computerized maintenance management systems (CMMS), including Oracle EAM and related planning workflows. Knowledge of asset data standards, documentation controls, and work order data quality expectations.Skills - Strong proficiency with standard business software (e.g., Microsoft Excel and Word) and advanced capability in data management, analysis, and organization. Effective written and verbal communication skills, with the ability to influence stakeholders, collaborate across functions, and drive alignment to standardized processes. Proficiency with Oracle EAM or a comparable work order management/CMMS platform.Abilities - Ability to work independently with minimal supervision, while also leading through influence and partnering effectively in cross-functional teams. Demonstrated ability to adapt quickly to changing priorities, apply sound judgment, introduce and sustain new concepts and continuous improvement initiatives.Reports to – Sr Manager EEM/EAMDirect Reports – NoneIndirect Reports – None" We need to separate into Qualifications, Skills, Abilities maybe. But we have allowed headings: Qualifications, Skills. Could also include Abilities under Skills? Better to have separate sections: Qualifications, Skills, Abilities? But Abilities not in list but we could still use h3 for Abilities? 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 include Abilities as part of Skills? But we could also create a section "Abilities" as h3; it's not prohibited. However they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exclusive. So we can add Abilities. But we also need to avoid filler like "commensurate with experience". Not present. We need Benefits section: from "What We Offer". Content: "At Wells, we’re proud to support our employees with comprehensive benefits that enhance health, financial wellness, and include paid time off (PTO). Eligible employees may also receive an annual incentive bonus based on Company performance." We'll put that in

  • maybe as list items? Could be paragraph. We'll do
    • Comprehensive benefits that enhance health, financial wellness, and include paid time off (PTO).
    • Eligible employees may receive an annual incentive bonus based on Company performance.
    Now we need to exclude boilerplate: EEO/AA employer line, About Us, maybe "Wells Enterprises is a 2 billion company employing 4,000 employees..." That's About Us; we might keep as paragraph before headings? It's substantive but not under allowed headings. Could include as a

    before first heading. Let's keep it. Also "Learn more at www.wellsenterprisesinc.com." That's maybe navigation/link; could be considered boilerplate? It's a link; maybe remove. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more at ..." is navigation/link; could be considered navigation; better to remove. Also "#IND123" maybe a tag; remove. Now we need to ensure we don't repeat job title as heading. Not needed. Now produce HTML fragment. Structure:

    Wells Enterprises, a Ferrero company, is one of the largest ice cream manufacturers in the United States and the maker of well-loved brands including Blue Bunny, Halo Top, Bomb Pop, and Blue Ribbon Classics and today Trolli, Butterfinger 100grand, Baby Ruth, Nutella and Kinder Bueno. Wells Enterprises is a 2 billion company employing 4,000 employees, across 4 production plants and 2 main hub locations, Chicago and Le Mars. Guided by innovation, quality, and a people-first mindset, Wells is committed to delighting consumers and developing exceptional teams. As part of the Ferrero Group, Wells combines its strong U.S. heritage with Ferrero’s global standards of excellence, offering a unique opportunity to grow within a dynamic, values-driven, and international environment. At Wells, our people—and their experience—sit at the heart of our ambition.

    About the role

    This position is responsible for developing, implementing, and sustaining reliability asset data management systems and processes (e.g., Metanoia and Oracle EAM). The role ensures data is standardized, optimized, and maintained to support business reporting and emerging AI-enabled capabilities that enhance the effectiveness of the technical workforce. In addition, the position establishes and administers the work order quality review process to promote consistent data accuracy, completeness, and usability. Additionally, this position will be able to fill in or assist the planner group with standard planner responsibilities. Responsible for planning, scheduling, coordinating and assigning work for Tech Services teams. Ensures the on-time completion of work orders, the efficient use of resources, and the quality of the work order