Manager, Master Data & Governance

We need to output HTML fragment with sections for headings: 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 preserve all substantive info, not invent. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, etc. The posting includes a lot of description: intro about company, then "What You Will Contribute:" then duties etc. We need to parse. We need sections: - About the role: likely the introductory paragraph(s) describing role purpose. The posting includes "What You Will Contribute: The Manager, Master Data & Governance is responsible for establishing and leading the enterprise Master Data Management (MDM) and Data Governance program..." That's about role. Could be "About the role". We'll put that in

About the role

then

with that description. - Responsibilities: The job duties sections: ERP Transformation Leadership, Data Migration Leadership & Coordination, Master Data Management & Governance, Data Quality & Stewardship, Business Process & Organizational Alignment, Reporting & Analytics Enablement. Those are responsibilities. We'll list them as

• each bullet maybe summarizing each duty? But we must preserve ALL substantive information; we cannot summarize away detail. However we can keep the detailed text inside each
• . The instruction: Use
  • for any list of duties/requirements/benefits. So we need to turn each duty into list items. We can break each major duty heading into a list item containing the paragraphs under it. That preserves content. - Requirements: The posting includes "Education and Experience" and "Qualifications:" and "Competencies:" and "Working Conditions:" maybe these are requirements. We need to decide what goes under Requirements vs Qualifications vs Skills. The instruction says use headings for Requirements, Qualifications, Skills. We need to map content accordingly. We have: Education and Experience: Bachelor's degree ... required. 5+ years experience ... etc. Qualifications: Strong understanding of enterprise master data domains ... etc. (list of qualifications) Competencies: Execution, Aligning Performance for Success, Decision Making, Coaching, Delegation and Empowerment. Working Conditions: Work is performed in an office environment... etc. We could treat Education and Experience as Requirements. Qualifications as Qualifications. Competencies as Skills. Working Conditions maybe as Requirements or maybe as a separate section? Not listed in headings; we could fold into Requirements or maybe omit if not matching headings. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include Working Conditions under Requirements maybe as part of Requirements? But we have separate headings; we could add a section "Working Conditions" but not in allowed list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map Working Conditions into Requirements (maybe as part of Requirements). Or we could omit if not specific? It's specific, so include within Requirements. Benefits: The posting includes "Competitive Total Rewards at Badger Meter:" with details: Competitive Pay, Annual Bonus Eligible for Annual Pay Increases, Comprehensive Health, Vision, and Dental Coverage, 15 days Paid Time Off + 11 Paid Holidays, Two Ways to Save for Retirement..., Additional access to a certified financial planner..., Employer Paid benefits including..., Educational Assistance..., Voluntary benefits..., Health Savings Account (HSA) & Flexible Spending Account (FSA) options. That's benefits. Also Pay: they mention Competitive Pay, Annual Bonus Eligible for Annual Pay Increases. That's pay info. Could be separate Pay section. But we have both Benefits and Pay headings. We need to decide what goes where. The posting lumps pay with benefits. We could separate: Pay section includes "Competitive Pay, Annual Bonus Eligible for Annual Pay Increases". Benefits section includes the rest: health coverage, PTO, holidays, retirement, financial planner, employer paid benefits, educational assistance, voluntary benefits, HSA/FSA. Schedule: Not mentioned. So we omit Schedule section. We must not include boilerplate like EEO, legal, etc. Remove those paragraphs at end. Now produce HTML fragment. Structure:

    About the role

    ... (the description from "What You Will Contribute:" maybe also include earlier intro? The earlier intro about company is not about role; but we could include it as part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The earlier paragraphs about Badger Meter mission etc are substantive but not about role; but they are not under any heading. Should we include them? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The About the role section should contain role-specific content. The company overview may be considered generic but still substantive. However the instruction says "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." It doesn't forbid including company overview. But we have no heading for company overview; we could include it in About the role as part of description. That would preserve it. So we can combine the introductory paragraphs about Badger Meter mission with the role description. Thus About the role

    will contain: first paragraph(s) about Badger Meter mission, then "What You Will Contribute: ..." etc. Now Responsibilities: list each duty heading as

  • with its paragraphs. We need to extract each duty section: 1. ERP Transformation Leadership - paragraphs: "Lead enterprise master data strategy and governance activities supporting the ERP migration." - "Partner with ERP program leadership, business stakeholders, and implementation partners to define future-state master data models and governance processes." - "Develop and execute master data readiness plans, including data assessment, cleansing, standardization, enrichment, migration, validation, and cutover activities." - "Drive alignment of master data structures and business definitions with ERP platform best practices and future-state business processes." - "Facilitate cross-functional decisions regarding data ownership, standards, naming conventions, hierarchies, and governance requirements." - "Ensure master data risks, dependencies, and quality issues are identified and addressed throughout the ERP implementation lifecycle." - "Support testing, user acceptance activities, go-live readiness, and post-implementation stabilization efforts." - "Establish governance capabilities that support ongoing ERP operations following implementation." 2. Data Migration Leadership & Coordination - paragraphs: "Serve as the enterprise leader responsible for planning, coordinating, and governing all master data migration activities supporting the ERP transformation." - "Partner with business process owners, functional leads, technical teams, and implementation partners to define migration scope, priorities, dependencies, and success criteria." - "Establish and oversee data migration governance processes, including issue management, decision-making forums, escalation paths, and risk mitigation plans." - "Lead cross-functional efforts to identify, cleanse, standardize, enrich, and validate legacy data prior to migration." - "Coordinate data ownership and business accountability for conversion activities across Customer, Supplier, Material, Manufacturing, Location, and Financial master data domains." - "Together with the ERP solution integrator:" - "Develop and maintain the enterprise data migration strategy, roadmap, timeline, and readiness plans across all master data domains." - "Direct data mapping, transformation, reconciliation, and validation activities." - "Manage multiple migration cycles, mock conversions, dress rehearsals, and cutover activities to support project milestones and go-live readiness." - "Define and monitor migration quality metrics, reconciliation controls, and acceptance criteria to ensure data integrity throughout the conversion process." - "Facilitate business validation and sign-off processes for migrated data, ensuring readiness for deployment and operational use." - "Collaborate with project management, change management, testing, and training teams to align migration activities with overall program objectives." - "Establish post-go-live data stabilization and remediation processes to address conversion issues and support business adoption." 3. Master Data Management & Governance - paragraphs: "Develop and maintain enterprise-wide data governance policies, standards, procedures, and controls." - "Establish and lead governance councils, stewardship teams, and data ownership structures." - "Define responsibilities and accountability models for key master data domains." - "Implement governance workflows supporting the creation, approval, maintenance, and retirement of master data." - "Ensure compliance with corporate policies, internal controls, audit requirements, and regulatory obligations related to enterprise data." 4. Data Quality & Stewardship - paragraphs: "Develop and manage enterprise data quality programs, metrics, scorecards, and reporting." - "Establish monitoring processes to identify data quality issues and proactively drive corrective actions." - "Lead a network of business data stewards responsible for day-to-day data maintenance and governance activities." - "Facilitate root cause analysis and process improvements to prevent recurring data integrity issues." - "Promote data ownership and accountability throughout the organization." 5. Business Process & Organizational Alignment - paragraphs: "Collaborate with business leaders to ensure data governance practices support operational excellence and decision-making." - "Drive standardization of master data definitions, business rules, and data management processes across business units and locations." - "Support organizational change management efforts related to the ERP implementation and data governance adoption." - "Serve as a trusted advisor on master data strategy, governance practices, and data-related business decisions." 6. Reporting & Analytics Enablement - paragraphs: "Partner with Business Intelligence, Analytics, and ERP teams to improve the reliability and consistency of reporting data." - "Ensure master data supports enterprise reporting, performance management, regulatory reporting, and advanced analytics initiatives." - "Identify opportunities to leverage automation, workflow technologies, and governance tools to improve operational efficiency." Now Requirements: Education and Experience + Working Conditions. Education and Experience paragraph: "Bachelor's degree in Information Systems, Business Administration, Supply Chain Management, Engineering, Finance, Data Management, or a related discipline required.5+ years of experience in Master Data Management, Data Governance, ERP systems, Business Process Management, or related disciplines.Experience leading cross-functional business initiatives involving multiple departments and stakeholders.Experience supporting enterprise systems and business process transformation initiatives.Experience developing governance frameworks, policies, standards, and operating procedures." Note there is missing space after period; we keep as is. Working Conditions: "Work is performed in an office environment and requires the ability to operate standard office equipmentRequires prolonged periods of talking/listeningMust be able to sit for prolonged periods of time" We could combine into one

    under Requirements. Now Qualifications: The bullet list under "Qualifications:" includes multiple sentences. We'll put as

    • each. List: - Strong understanding of enterprise master data domains and governance principles. - Knowledge of ERP business processes including Finance, Procurement, Manufacturing, Supply Chain, Inventory, Sales, and Customer Operations. - Understanding of data quality management, stewardship programs, workflow controls, and lifecycle management processes. - Familiarity with SAP S/4HANA master data architecture and governance capabilities. - Experience with data migration, data cleansing, and data validation methodologies. - Working knowledge of reporting and analytics platforms such as Power BI. - Experience participating in or leading ERP implementation, migration, or transformation programs, with SAP S/4HANA implementation experience strongly preferred. - Experience with SAP Master Data Governance (MDG) or similar MDM platforms. - Manufacturing industry experience. - Experience managing data migration and conversion activities from legacy ERP systems. Now Skills: Competencies list. Competencies: Execution, Aligning Performance for Success, Decision Making, Coaching, Delegation and Empowerment. Each has a description. We'll put each as
    • with the full description. List: - Execution: Ensuring others contribute to organization strategies by focusing them on the most critical priorities; measuring progress and ensuring accountability