Control Systems Engineer

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include only sections with real content. We need to parse the posting. Content: Location: Greenwood, SC (maybe metadata). Not needed as heading. Paragraph about Lonza: "Today, Lonza is a global leader..." That's about the company; could be "About the role"? Actually "About the role" heading could contain description of role and company. We'll include a paragraph. Responsibilities: list of duties: "Responsible for developing, supporting, and maintaining integrated automation and control systems, including software testing, commissioning, validation support, project planning, and continuous improvement activities." Then "What you will do:" bullet list. We need to extract bullet points: after "What you will do:" we have sentences separated by periods? Let's parse: "Designs control systems, or designs modifications to existing control systems based on process diagrams, user requirements, functional requirements, Piping & Instrumentation Diagrams (P&ID), machine mechanical drawings. Collaborates effectively with global controls engineering team on development projects, standards development, selection and implementation of new technologies and automation systems. Supports, configures and replicates (including new releases and patching) PLC systems, SCADA, drive configuration, servo systems, and vision systems. Maintains software and hardware global configuration information, technical documentation, software backups, control software revision notes, knowledge base data records, generates FS (Functional Specification)/DS (Design Specification) documentation and supports cGMP validation process. Regularly communicates with Control Systems Manager on project progress and potential issues. Based on a rotating schedule provides after-hours support for plant operations. Effectively collaborates with plant personnel, provides technical guidance to electronics." We can treat each sentence as a list item. Requirements/Qualifications/Skills: The posting has "What We Are Looking For" with bullet-like sentences. List: "Bachelor's degree in Electrical Engineering, Mechatronics, Computer Science, Mechanical Engineering, or Robotics with an emphasis on automation. Strong communication skills with the ability to manage client expectations and effectively communicate project status, obstacles, and opportunities. Knowledge of electrical circuit theory, control circuit design, and the ability to interpret electrical wiring diagrams, P&IDs, and mechanical assembly drawings. Ability to safely troubleshoot control electrical wiring while maintaining personal and team safety. Intermediate software engineering knowledge, including software development lifecycle (SDLC), system requirements, and development/execution of test plans to verify software quality and fitness for use. Intermediate project management skills with the ability to develop accurate estimates for software-related project work. Programming proficiency (Siemens preferred), with a working knowledge of SCADA systems, drives and servo systems, PCs, Microsoft Office Suite, Microsoft Project, and the Windows operating system." We can categorize: Requirements (education, experience), Skills (technical). But we can just put under "Requirements" or "Qualifications". The instruction: use headings for sections like 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: we can include description of company and role overview (first paragraph after location). Could be "About the role". - Responsibilities: we have list. - Requirements: education, maybe also experience? We'll include education and maybe some baseline. - Qualifications: maybe similar to requirements; but we can combine. However we should avoid thin sections. Could combine education and experience under "Requirements". Then "Skills" for technical proficiencies. - Benefits: we have "What You Will Get" includes: agile career, inclusive workplace, compensation programs, medical/dental/vision insurance, link to benefits. So we have benefits content. - Pay: not specified (no salary). So we should NOT include Pay section. - Schedule: mention "Based on a rotating schedule provides after-hours support for plant operations." That's schedule info. So we can include Schedule section with that detail. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive info; not invent. We must remove boilerplate: EEO statement, reference, apply, etc. Also remove navigation/cookie etc. Not present. We need to output only HTML fragment. Structure:

About the role

Today, Lonza is a global leader in life sciences operating across five continents. While we work in science, there’s no magic formula to how we do it. Our greatest scientific solution is talented people working together, devising ideas that help businesses to help people. In exchange, we let our people own their careers. Their ideas, big and small, genuinely improve the world. And that’s the kind of work we want to be part of. Responsible for developing, supporting, and maintaining integrated automation and control systems, including software testing, commissioning, validation support, project planning, and continuous improvement activities.

But note: The sentence about responsibilities is also part of responsibilities; we might duplicate. Better to keep responsibilities separate. The "About the role" could be just the company description, not include responsibilities. Let's separate. Thus:

About the role

Today, Lonza is a global leader in life sciences operating across five continents. While we work in science, there’s no magic formula to how we do it. Our greatest scientific solution is talented people working together, devising ideas that help businesses to help people. In exchange, we let our people own their careers. Their ideas, big and small, genuinely improve the world. And that’s the kind of work we want to be part of.

Then responsibilities:

Responsibilities

• Developing, supporting, and maintaining integrated automation and control systems, including software testing, commissioning, validation support, project planning, and continuous improvement activities.
• Designs control systems, or designs modifications to existing control systems based on process diagrams, user requirements, functional requirements, Piping & Instrumentation Diagrams (P&ID), machine mechanical drawings.
• Collaborates effectively with global controls engineering team on development projects, standards development, selection and implementation of new technologies and automation systems.
• Supports, configures and replicates (including new releases and patching) PLC systems, SCADA, drive configuration, servo systems, and vision systems.
• Maintains software and hardware global configuration information, technical documentation, software backups, control software revision notes, knowledge base data records, generates FS (Functional Specification)/DS (Design Specification) documentation and supports cGMP validation process.
• Regularly communicates with Control Systems Manager on project progress and potential issues.
• Based on a rotating schedule provides after-hours support for plant operations.
• Effectively collaborates with plant personnel, provides technical guidance to electronics.

But note we have schedule item in responsibilities; we might move schedule to separate section. However schedule content is "Based on a rotating schedule provides after-hours support for plant operations." That's schedule info. We could keep it in responsibilities or schedule. The instruction: include a section ONLY when posting has real, specific content for it. We have schedule content, so we can create Schedule section with that line. But we should not duplicate. Let's extract schedule line to its own section and remove from responsibilities. Thus responsibilities list without that line. Schedule section:

Schedule

Based on a rotating schedule provides after-hours support for plant operations.

Now Requirements: education.

Requirements

• Bachelor's degree in Electrical Engineering, Mechatronics, Computer Science, Mechanical Engineering, or Robotics with an emphasis on automation.

Skills: technical proficiencies.

Skills

• Strong communication skills with the ability to manage client expectations and effectively communicate project status, obstacles, and opportunities.
• Knowledge of electrical circuit theory, control circuit design, and the ability to interpret electrical wiring diagrams, P&IDs, and mechanical assembly drawings.
• Ability to safely troubleshoot control electrical wiring while maintaining personal and team safety.
• Intermediate software engineering knowledge, including software development lifecycle (SDLC), system requirements, and development/execution of test plans to verify software quality and fitness for use.
• Intermediate project management skills with the ability to develop accurate estimates for software-related project work.
• Programming proficiency (Siemens preferred), with a working knowledge of SCADA systems, drives and servo systems, PCs, Microsoft Office Suite, Microsoft Project, and the Windows operating system.

Benefits:

Benefits

• An agile career and dynamic working culture.
• An inclusive and ethical workplace.
• Compensation programs that recognize high performance.
• Medical, dental and vision insurance.
• The full list of our global benefits can be also found on https://www.lonza.com/careers/benefits.

We should not include Pay section. Check for any leftover boilerplate: EEO statement, reference, apply, etc. Remove. Now ensure we didn't miss any substantive info: The line "Every day, Lonza’s products and services have a positive impact on millions of people. For us, this is not only a great privilege, but also a great responsibility. How we achieve our business results is just as important as the achievements themselves. At Lonza, we respect and protect our people and our environment. Any success we achieve is no success at all if not achieved ethically. People come to Lonza for the challenge and creativity of solving complex problems and developing new ideas in life sciences. In return, we offer the satisfaction that comes with improving lives all around the world. The satisfaction that comes with making a meaningful difference." This is more company culture; could be included in About the role or maybe a separate section but we already have About the role with some description; we could add more to that paragraph. Let's incorporate that into About the role paragraph to preserve all substantive info. Thus About the role paragraph will be longer. Let's craft:

Today, Lonza is a global leader in life sciences operating across five continents. While we work in science, there’s no magic formula to how we do it. Our greatest scientific solution is talented people working together, devising ideas that help businesses to help people. In exchange, we let our people own their careers. Their ideas, big and small, genuinely improve the world. And that’s the kind of work we want to be part of. Every day, Lonza’s products and services have a positive impact on millions of people. For us, this is not only a great privilege, but also a great responsibility. How we achieve our business results is just as important as the achievements themselves. At Lonza, we respect and protect our people and our environment. Any success we achieve is no success at all if not achieved ethically. People come to Lonza for the challenge and creativity of solving complex problems and developing new ideas in life sciences. In return, we offer the satisfaction that comes with improving lives all around the world. The satisfaction that comes with making a meaningful difference.

That covers all. Now ensure we didn't duplicate any content elsewhere. Check responsibilities list: we removed schedule line. Good. Now ensure we didn't miss any responsibility like "Based on a rotating schedule provides after-hours support for plant operations." moved to schedule. Now check if any other schedule info: none. Now check if any pay info: none. Now check if any qualifications beyond education: maybe "Strong communication skills" etc are skills; we placed them under Skills. Now check if any "Qualifications" section needed: we could combine education and maybe some baseline under Requirements; but we have Requirements (education) and Skills (technical/soft). That's fine. Now ensure we didn't include any filler like "