Controls Systems Engineer I to III

We need to output HTML fragment with sections: About the role? The posting includes Position Summary, Responsibilities (common to all levels), then level-specific responsibilities and qualifications. Also Starting Salary Range: $96,400.00 - $117,600.00 (maybe overall). Also each level has Starting Pay Range. We need to include Pay section only if posting actually states them. It does state Starting Salary Range and each level's Starting Pay Range. So we can include a Pay section with those ranges. However we need to avoid filler like "commensurate with experience". We have actual numbers. We need headings:

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• accordingly. We need to decide which sections to include based on content. We have Position Summary (could be About the role). Responsibilities (common to all levels). Also level-specific responsibilities could be under Responsibilities as subpoints? But we need to preserve all substantive info. Could create separate sections for each level? Not in allowed headings list. Could embed level-specific responsibilities under Responsibilities with subheadings? But only allowed headings are those listed; we cannot add custom headings like "Level I Responsibilities". However we could include them as part of Responsibilities section using

  or

  . The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. Likely we should stick to those headings only. So we can have About the role (position summary), Responsibilities (common to all + level-specific maybe as nested lists), Requirements (maybe qualifications), Qualifications (maybe preferred?), Skills, Benefits, Pay, Schedule. We have no explicit Benefits or Schedule info. There's no mention of benefits or schedule. So we should NOT include Benefits or Schedule sections because posting does not state them. So we omit those. We have Pay: Starting Salary Range and level-specific Starting Pay Range. So include Pay section. We have Requirements: maybe required qualifications. We have Required qualifications for each level. Could combine. We have Qualifications: maybe preferred qualifications. We have Skills: maybe skills like analytical, problem-solving, communication, etc. We need to preserve all substantive info; not invent or summarize away detail. Must not omit any substantive info. So we need to include all details: position summary, responsibilities common to all levels, level I responsibilities, level II responsibilities, level III responsibilities, qualifications required for each level, preferred qualifications for each level, physical requirements/working conditions, maybe also note about emergency response, attendance, etc. We must not include boilerplate like EEO etc. The text ends with "Physical Requirements / Working Conditions:" and then description. We need to keep that. We must not include application instructions, cookie/navigation/legal/EEO etc. The text does not have those except maybe at start "Thank you for your interest in the BWL...". That's not boilerplate? It's a greeting; could be considered introductory but not required to keep? It's not substantive job info; maybe we can drop it as it's not required. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The opening line is not boilerplate but it's a thank you note; could be considered fluff. Might be safe to keep? It's not substantive job info; but we could keep as part of About the role? Might be considered filler. Safer to omit it. We need to output only HTML fragment. Let's structure:

  About the role

  Position Summary ...

  Responsibilities

  • Common to all levels: ... (list each bullet)
  But we also need level-specific responsibilities. Could embed as sublists under each level within Responsibilities? Might be okay to have nested
  with headings? But we cannot add headings. Could use

  to label level then

  . Eg:

  Responsibilities

  Common to all levels:

  ...

  Level I Responsibilities:

  ...
  ... etc. That preserves info. Similarly for Qualifications: we have Required and Preferred for each level. Could do similar. Skills: maybe extract from responsibilities? But we can also create a Skills section summarizing skills like analytical, problem-solving, communication, etc. However we must not invent or summarize away detail; we can list skills explicitly mentioned: Strong analytical and problem-solving skills, Ability to communicate technical information effectively, Ability to manage multiple priorities, Basic understanding of computer networking, etc. Also for higher levels: Strong analytical, troubleshooting, problem-solving skills, Basic knowledge of industrial cybersecurity practices, Effective technical communication, ability to manage multiple priorities, etc. Also knowledge of industrial cybersecurity practices, etc. Also for Level III: Knowledge of industrial cybersecurity practices, Demonstrated technical leadership and ability to communicate complex technical information effectively, etc. Also Preferred skills: familiarity with major enterprise DCS platforms, project management experience, vendor management experience, familiarity with NERC CIP low-impact compliance standards, advanced knowledge of utility operations. We could put these in Skills section. Requirements: maybe the required qualifications (education, experience). Could be separate. But we have both Required and Preferred qualifications; we could put Required under Requirements, Preferred under Qualifications. Let's decide: - About the role: Position Summary. - Responsibilities: as described. - Requirements: Required qualifications (education, experience) for each level (maybe separate subpoints). - Qualifications: Preferred qualifications for each level. - Skills: skills mentioned (analytical, problem-solving, communication, etc.) - Pay: Starting Salary Range and level-specific Starting Pay Range. We must not include Benefits or Schedule. Now we need to ensure we preserve all substantive info: includes physical requirements/working conditions. Where to put that? Could be under Requirements? Or maybe a separate section? Not in allowed headings. Could put under Requirements as a note. Or maybe under About the role? Better to add a separate section? Not allowed headings. Could add a

  after Qualifications? But we must not invent headings. Could add a

  with the physical requirements under a generic heading? Not allowed. Perhaps we can include it under Requirements as a subsection using

  with bold label. That's okay. We must not omit any substantive info: includes "Must be able to provide continuous support and perform a primary assignment in support of an emergency response to operational-impacting events." etc. Also "Maintains predictable and reliable attendance." etc. Also "Performs other duties as assigned." Also "Physical Requirements / Working Conditions:" details. We need to include all. Now craft HTML. We'll need to escape any special characters? Not needed. Let's draft. First, About the role:

  The Controls Systems Engineer is responsible for supporting and advancing the design, implementation, operation, maintenance, troubleshooting, and lifecycle management of BWL Operations Technology (OT) control systems supporting electric, water, steam, and chilled water production facilities. The position works with Distributed Control Systems (DCS), Supervisory Control and Data Acquisition (SCADA), Programmable Logic Controllers (PLCs), industrial networks, instrumentation, and associated communication systems. Depending on the level, the Controls Systems Engineer will work under supervision, independently, or in a technical leadership capacity to support safe, reliable, efficient, and secure plant operations. The position collaborates with plant operations, maintenance, engineering, IT/OT, vendors, contractors, and other stakeholders to resolve operational issues, execute projects, maintain system reliability, and drive continuous improvement. The Controls Systems Engineer may be hired at Level I, II, or III based on the candidate's education, experience, technical proficiency, and demonstrated ability to perform the responsibilities associated with each level.

  Now Responsibilities: We'll have common to all levels list (many bullet points). Then level-specific. Let's extract common responsibilities bullet points from text: "Supports or performs the design, programming, implementation, modification, maintenance, troubleshooting, and upgrade of control systems, including DCS, PLCs, SCADA, instrumentation, and associated industrial communication and networking systems." "Supports the safe, reliable, efficient, and secure operation of control systems serving electric, water, steam, and chilled water production facilities." "Troubleshoots and debugs existing control systems and assists with identifying and resolving system performance, reliability, and operational issues." "Performs or supports engineering studies, data collection, operational analysis, and root cause investigations to identify opportunities for improved system performance and reliability." "Develops or supports control strategies and software changes that improve plant reliability, efficiency, maintainability, and operational performance." "Participates in or leads commissioning, startup, loop checks, functional testing, system testing, and validation activities, as appropriate to the position level." "Develops, reviews, updates, and maintains control system documentation, drawings, control narratives, procedures, standards, and technical records." "Supports the development of equipment, material, construction, and technical specifications related to control systems and associated equipment." "Supports or leads control system projects, including scope development, budgeting, design, procurement, implementation, commissioning, and project closeout, as appropriate to the position level." "Interfaces with plant operators, maintenance personnel, engineers, plant leadership, vendors, contractors, and other stakeholders to resolve control system issues and accomplish project and operational objectives." "Supports control system lifecycle management, including maintenance planning, system upgrades, obsolescence management, and evaluation of system reliability and supportability." "Supports the development, implementation, and continuous improvement of control system standards, procedures, engineering practices, and operational best practices." "Supports Operations Technology cybersecurity and applicable regulatory compliance activities, including NERC CIP requirements, as appropriate to assigned responsibilities." "Creates, reviews, or executes test procedures to verify proper operational functionality of control systems and modifications." "Analyzes operational data and performance indicators to identify trends, opportunities for optimization, and potential reliability improvements." "Participates in training and professional development activities to remain current with control systems, industrial automation, cybersecurity, utility operations, and emerging technologies." "Supports a culture of safety, reliability, accountability, and continuous improvement." "Adheres to all BWL policies, safety procedures, and applicable regulatory requirements." "Attends safety training and other required training as directed by the supervisor, BWL, or governmental agencies such as MIOSHA." "Must be able to provide continuous support and perform a primary assignment in support of an emergency response to operational-impacting events." "Maintains predictable and reliable attendance." "Performs other duties as assigned." Now level-specific responsibilities: Level I: "Support control system design, programming, configuration, testing, and implementation under the direction of experienced engineering staff." "Assist with engineering studies, data collection, troubleshooting, and root cause analysis of control system issues." "Assist with developing and implementing control strategies and software changes." "Participate in plant commissioning, loop checks, system testing, and startup activities." "Assist with updating drawings, control narratives, procedures, standards, and other technical documentation." "Support control system projects by completing assigned engineering tasks within established schedules and budgets." "Develop working knowledge of BWL plant operations, control system architecture, industrial networking, instrumentation, and OT cybersecurity." "Work with operators, maintenance personnel, and other engineers to identify and resolve control system issues." Level II: "Independently design and implement DCS and ancillary control system modifications to improve plant performance and reliability." "Perform control system troubleshooting and root cause analysis and implement corrective actions." "Lead scope development, project budgeting, technical specifications, and commissioning for assigned projects." "Serve as project lead for assigned control system capital projects." "Interface directly with vendors and contractors for control system upgrades, modifications, and equipment replacements." "Review and approve drawings, control logic, specifications, and technical documents within assigned areas of responsibility." "Analyze operational data and