Principal IT Analyst - Manufacturing Operations

We need to output HTML fragment with sections: About the role? The description includes "Job Description" intro, then responsibilities, qualifications, benefits, about Honeywell, about business unit, about us. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. No Pay or Schedule unless stated. There's mention of Hybrid schedule, but not specifics beyond hybrid and first 90 days onsite. That's schedule info. Should we include Schedule section? The posting says: "You will report directly to our Director, IT ERP Business Transformation and work out of our Houston, TX, or Atlanta, GA or Charlotte, NC location on a Hybrid schedule. Hybrid Work Schedule Note: For the first 90 days, New Hires must be prepared to work 100% onsite M-F". That's schedule info. So we can include a Schedule section with that content. Pay: not mentioned (no salary). So omit Pay. Benefits: yes. About the role: we have introductory paragraph describing role. Could be About the role. Responsibilities: list. Requirements/Qualifications: we have "YOU MUST HAVE" and "WE VALUE". Could split into Requirements (must have) and Qualifications (valued). Skills: maybe not separate; we could combine. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll include those with content. Skills: we could extract skills from qualifications: e.g., SAP S/4 PP/PP/DS, integration, manufacturing master data, documentation, testing, etc. Could make a Skills section. But we must not invent content; we can list skills that are explicitly mentioned. The posting mentions: "Strong understanding of production processes, shop-floor execution, and manufacturing systems." "Hands-on experience with SAP S/4 PP and/or PP/DS in a manufacturing environment." "Experience integrating SAP with MES, DCS, PLCs, or other production systems." "Bachelor’s degree..." etc. Also "Strong documentation, training, and communication skills." "Experience with structured testing methodologies". So we can put those in Skills. We need to preserve all substantive information; not invent. So we must include all details: location options, hybrid schedule, first 90 days onsite, reporting to Director, etc. Also mention travel up to 10%, relocation support may be provided. Also mention application period etc? That's boilerplate? Might be considered metadata; we can drop application instructions, but we can keep maybe as minor metadata in a short p. 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 p for things like job posting date, application period, etc. But we should remove cookie/navigation/legal/EEO etc. The "About Honeywell", "The Business Unit", "About Us" sections are descriptive but maybe not required? They are substantive about company. Should we include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep those as well. But we need to fit into headings; we could have an "About Honeywell" section but not in allowed headings list. The allowed headings are specific; we should only use those headings. So we need to map content to those headings. About Honeywell could go under About the role? Not exactly. Maybe we can treat "About Honeywell" as part of About the role? But that seems off. However the instruction says: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map all content into those sections. For company description, we could put under About the role? Or maybe we can create an "About Honeywell" section but that would deviate from examples. Safer to stick to given headings. We can put company info under About the role as a brief overview? But that might misrepresent. However we could include a short paragraph under About the role that includes role description and also company overview? Might be okay. Better: Use About the role for role description and company context. Responsibilities for responsibilities. Requirements for must-have. Qualifications for valued. Skills for skills. Benefits for benefits. Schedule for schedule. Pay omitted. We need to ensure we don't omit any substantive info: location options, hybrid schedule, first 90 days onsite, reporting to Director, travel up to 10%, relocation support may be provided, application period, job posting date. Those could be placed in a short p under About the role or maybe a separate meta section but we can fold into About the role as a short p. Let's craft:

About the role

As a Lead IT Analyst – Manufacturing Operations in PT, you will ensure that our SAP S/4 Manufacturing, Production Planning, and shop-floor integration solutions are optimized for performance, reliability, and alignment with business objectives. You will work directly with factories, operations leaders, and manufacturing SMEs to understand production requirements and translate them into scalable, compliant SAP S/4 solutions. You will play a pivotal part in driving the organization's technology strategies and projects, aligning them with business objectives. This role is critical to delivering end-to-end production execution and planning capabilities, integrating SAP with shop-floor systems (DCS, PLCs, MES), and ensuring material movements, capacity planning, and scheduling are correctly designed and deployed within SAP S/4. Your technical leadership will ensure the reliability, security, and scalability of our IT systems, ultimately enhancing our competitive edge and operational efficiency. You will report directly to our Director, IT ERP Business Transformation and work out of our Houston, TX, or Atlanta, GA or Charlotte, NC location on a Hybrid schedule. Hybrid Work Schedule Note: For the first 90 days, New Hires must be prepared to work 100% onsite M-F. Travel: up to 10% travel. Relocation support may be provided. Job Posting date: August 28, 2026. The application period for the job is estimated to be 40 days from the job posting date; however, this may be shortened or extended depending on business needs and the availability of qualified candidates.

Then Responsibilities as ul. Then Requirements (must have) as ul. Then Qualifications (valued) as ul. Then Skills as ul (maybe combine some from qualifications but we can list distinct skill statements). Then Benefits as ul. Then Schedule as p (maybe we already included schedule in About the role; but we need a Schedule section per instruction. We could move schedule details to Schedule section and keep About the role without schedule duplication. But we must not duplicate content. We could keep schedule details only in Schedule section and remove from About the role. However About the role currently includes schedule note; we could move that to Schedule section and keep About the role without schedule. Let's do that. Thus About the role: role description, reporting, location, travel, relocation, posting date, application period. Schedule: hybrid schedule details. Let's extract schedule: "You will report directly to our Director, IT ERP Business Transformation and work out of our Houston, TX, or Atlanta, GA or Charlotte, NC location on a Hybrid schedule. Hybrid Work Schedule Note: For the first 90 days, New Hires must be prepared to work 100% onsite M-F." We'll put that in Schedule section. Now About the role will not include location/schedule; we can keep reporting and location? Actually location is part of schedule; we could keep location in About the role? But location is also schedule-related. Might be okay to keep location in About the role but then schedule section would be redundant. Better to put location in About the role? The instruction: "include a section ONLY when the posting has real, specific content for it". So we need Schedule section with schedule content. Location could be considered part of schedule but also part of role. I'd keep location in About the role (since it's about where you work) and schedule details in Schedule section. That avoids duplication. Thus About the role includes: role description, reporting to Director, work out of Houston, TX, or Atlanta, GA or Charlotte, NC location. Travel up to 10%, relocation support may be provided, job posting date, application period. Schedule section: Hybrid schedule note: For the first 90 days, New Hires must be prepared to work 100% onsite M-F. Now Responsibilities: list from "KEY RESPONSIBILITIES" bullet points. Requirements: "YOU MUST HAVE" bullet points. Qualifications: "WE VALUE" bullet points. Skills: we need to extract skill statements from the posting that are not already captured. Could list: Strong understanding of production processes, shop-floor execution, and manufacturing systems; Hands-on experience with SAP S/4 PP and/or PP/DS in a manufacturing environment; Experience integrating SAP with MES, DCS, PLCs, or other production systems; Bachelor’s degree in IT, CS, Engineering, Manufacturing, or related field; Proven experience supporting or delivering manufacturing system implementations, enhancements, or plant rollouts; SAP certifications in S/4 Manufacturing, PP, or PP/DS; Experience working directly with factory operations and production leadership; Strong understanding of manufacturing master data governance and data quality; Ability to translate complex production concepts into clear system designs and requirements; Strong documentation, training, and communication skills; Experience with structured testing methodologies in manufacturing environments. But some of these overlap with Requirements/Qualifications. However we can still list them under Skills; it's okay if some duplication? The instruction: preserve all substantive information; not invent. Duplication is okay if it's already present elsewhere? Might be considered repeating but not prohibited. However better to avoid duplication by only listing skills not already covered. But it's tricky. Perhaps we can omit Skills section if it would be mostly duplicate. But we need to follow heading list? Not required to include all headings; only include when posting has real specific content. If Skills would be mostly duplicate, we could still include but risk duplication. I think we can include Skills with distinct skill statements that are not already in Requirements/Qualifications. Let's see: Requirements (must have): - 8+ years of IT analysis experience with a focus on Manufacturing, Production Planning, or Factory Operations. - Strong understanding of production processes, shop-floor execution, and manufacturing systems. - Hands-on experience with SAP S/4 PP and/or PP/DS in a manufacturing environment. - Experience integrating SAP with MES, DCS, PLCs, or other production systems. Qualifications (valued): - Bachelor’s degree in Information Technology, Computer Science, Engineering, Manufacturing, or a related field. - Proven experience supporting or delivering manufacturing system implementations, enhancements, or plant rollouts. - SAP certifications in S/4 Manufacturing, PP, or PP/DS. - Experience working directly with factory operations and production leadership. - Strong understanding of manufacturing master data governance and data quality. - Ability to translate complex production concepts into clear system designs and requirements. - Strong documentation, training, and communication skills. - Experience with structured testing methodologies in manufacturing environments. Thus Skills could be empty; we could omit Skills section. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Benefits: we have paragraph about benefits; we can make ul list. Let's extract benefits list: employer subsidized Medical, Dental, Vision, and Life Insurance; Short-Term and Long-Term Disability; 401(k) match, Flexible Spending Accounts, Health Savings Accounts, EAP, and Educational Assistance; Parental Leave, Paid Time Off