Instrument and Controls Technician

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, maybe Skills, Benefits, Pay, Schedule only if present. The posting includes "About The Role" heading, then description. Then "Some Responsibilities Will Include". Then "Position Requirements". Then "Physical Requirements". Also "All Reworld positions require a candidate's ability..." is generic values, maybe not needed. Also "Pay Transparency" says pay rate and benefits according to CBA, but not specific numbers. According to rules: do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It says pay rate and benefits will be according to CBA for the role. That's not specific numbers, but it's still stating that pay and benefits are per CBA. Should we include Pay and Benefits sections? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that pay rate and benefits will be according to CBA. That's a statement, albeit vague. However also "Prefer a few substantive sections over many thin ones." Might be better to omit Pay/Benefits because it's not specific. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them in a generic way. But also "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')" The phrase "according to CBA for the role" is not filler? It's somewhat vague but still a statement. However they said "Prefer a few substantive sections over many thin ones." I'd lean to omit Pay/Benefits/Schedule because they are not specific. Also schedule: "Must be able to work on a rotating shift schedule and work overtime as needed including nights, weekends, and holidays." That's schedule info. That is specific: rotating shift schedule, overtime, nights, weekends, holidays. So we could include a Schedule section. Benefits: not specific beyond "benefits will be according to CBA". That's vague; maybe omit. Pay: also vague. So include Schedule. We need sections: About the role (already have heading "About The Role"), Responsibilities, Requirements (maybe combine Position Requirements and Physical Requirements?), Skills? Could embed skills within Requirements. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role, Responsibilities, Requirements, Schedule. Possibly also Skills if we want separate but not needed. We must not repeat job title as heading. No Job ID. We must preserve all substantive information. Remove boilerplate: "Who we are", "Our Vision", "Our Business", "Our Value", "All that we’re missing is you. Apply today!" Also remove "Our DEI Commitment", "Know Your Rights", "Attention Staffing Agencies & Search Firms". Also remove "Please note that Level, Title and/or Salary may be adjusted based on the applicant's experience or skills." That's maybe not boilerplate but it's about level/salary adjustment; could be considered meta but it's substantive? It's about adjustment; maybe keep? It's not a specific section; could be placed in a paragraph under Requirements? Might be considered filler but it's info. I'd keep it as a paragraph under Requirements maybe. Also remove "All Reworld positions require a candidate's ability to perform the duties and responsibilities of the role while upholding Reworld's Values, including (but not limited to) contributing to a safe and inclusive workplace, delivering results through trust, and building breakthrough capabilities." That's generic values; could be considered boilerplate but it's about values; maybe keep? It's not specific to role. Might be considered boilerplate; but it's about upholding values. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is values statement; not exactly EEO but could be considered generic. I'd remove it to keep focused. Also remove "Pay Transparency" section? It's about pay per CBA; we might keep as note under Schedule? But we decided not to create Pay section. Could include a short paragraph under Schedule or Requirements about pay per CBA. But rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay and benefits per CBA, but we are not making a Pay section; we could mention it in a paragraph elsewhere. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we just omit mention of pay/benefits entirely? But that would lose substantive info. The rule says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that info somewhere. Could add a

under Requirements or under a generic "Additional Information" but we shouldn't create a heading for it if not in list. Could add a paragraph after Requirements:

Pay rate and benefits will be according to the applicable Labor Union / Collective Bargaining Agreement (CBA).

Similarly schedule info we already have. Now let's extract content. About the role paragraph: "The Instrument & Controls Technician will be responsible for managing all phases of electrical and control equipment throughout the plant. This includes preventive, corrective, emergency, warranty service, etc. throughout the facility. Identifies, repairs, and documents electrical equipment malfunctions. Familiar with and have skills to troubleshoot DCS systems, PLC's, VFD, motor control circuits, transmitters, flow meters, level controls and burner management systems. Calibrates mechanical and electrical instrumentation, installs and tests new equipment in accordance with safety standards, conducts predictive analysis of electrical and instrumentation systems and equipment and update Preventive Maintenance System and work orders. Willing to perform other duties as assigned to assist the maintenance department. Must be willing to be on-call and work variety of shifts to meet plant needs." That's the About the role. Responsibilities: "Some Responsibilities Will Include Operating and maintaining the instrument and control test, calibration and repair areas and all equipment and tolls assigned.Helping to redesign instrumentation, control and electrical systems, as required.Monitors burning, as appropriate.Performs general work or other assignments necessary to ensure the safe, clean and efficient operation of the facility.Performs other duties as required. The successful candidate will be a safety conscious team player that takes pride in their work and workplace. They will work to learn new skills and be open to occasional cross discipline activities to progress the team goals." We need to split into list items. The text has no punctuation between items; we can separate by sentences. Let's parse: - Operating and maintaining the instrument and control test, calibration and repair areas and all equipment and tools assigned. - Helping to redesign instrumentation, control and electrical systems, as required. - Monitors burning, as appropriate. - Performs general work or other assignments necessary to ensure the safe, clean and efficient operation of the facility. - Performs other duties as required. - The successful candidate will be a safety conscious team player that takes pride in their work and workplace. - They will work to learn new skills and be open to occasional cross discipline activities to progress the team goals. We could keep as list. Requirements: "Position Requirements To be considered for this position, you must have 5 years or more of hands-on experience with electronic/electrical and pneumatic systems and equipment in an industrial environment. Energy from Waste experience or Power Plant experience desired.A High School Diploma or equivalent and/or formal technical training.Familiarity with Programmable Logic Controllers and Distributive Control Systems are also required.Ability to trouble shoot and diagnose instrumentation and controls with an understanding how they interact in the process.Ability to perform calibrations to pressure, flow, temperature and other sensing instrumentation (majority Rosemount).Proficient in the use of multimeters and smart calibrators.Ability to read electrical prints & P&IDs.Ability to trouble shoot OMRON PLC hardware.Ability to trouble shoot OMRON PLC logic utilizing OMRON software.Ability to trouble shoot Allen Bradly PLC hardware.Ability to trouble shoot Allen Bradley PLC logic utilizing Allen Bradley software (SLC 504).Ability to learn and fully utilize the user Operator Interface System “Citect” including the creation of graphic screens, writing ci-code, develop alarm & trend tags, etc.Ability to learn and troubleshoot Ethernet communication in the Plant Control System.Must be able to work on a rotating shift schedule and work overtime as needed including nights, weekends, and holidays." Physical Requirements: "Ability to walk, stand, sit, and climbAbility to lift/carry 50lbsAbility to work from heights and in confined spacesQualify to wear a full-face respiratorConsistently work in various weather condition" We could combine Requirements and Physical Requirements under a single Requirements section, or split into Requirements and Physical Requirements. The instruction list includes Requirements as a possible heading; we could have Requirements and maybe Physical Requirements as a subheading? But only allowed headings are those listed; we could use Requirements for both, but we could also add a separate heading "Physical Requirements" if we want, but not in list. Better to combine into Requirements section, listing both sets. We also have the note: "Please note that Level, Title and/or Salary may be adjusted based on the applicant's experience or skills." Could be included as a paragraph under Requirements. Also "All Reworld positions require a candidate's ability to perform the duties and responsibilities of the role while upholding Reworld's Values, including (but not limited to) contributing to a safe and inclusive workplace, delivering results through trust, and building breakthrough capabilities." Might be considered boilerplate; I'd remove. Now schedule: we already have schedule info in requirements (rotating shift schedule etc). But we could also create a Schedule section with that info. However we already have schedule info in requirements; we could move it to Schedule section to avoid duplication. The rule: preserve ALL substantive information; we can move it but not duplicate. Let's extract schedule info: "Must be able to work on a rotating shift schedule and work overtime as needed including nights, weekends, and holidays." We'll put that in Schedule section. Thus Requirements section will exclude that sentence. Now Benefits: we have statement about benefits per CBA. We'll add a paragraph after Schedule maybe under a Benefits section? But we said not to create Benefits unless posting actually states them. It does state benefits per CBA, but it's vague. However we could include a Benefits section with that statement. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits per CBA, so we could create Benefits section with that statement. Similarly Pay: "Pay Transparency This role is covered under a Labor Union / Collective Bargaining Agreement (CBA). The pay rate and benefits will be according to CBA for the role." That's both pay and benefits. So we could create Pay section with that statement, and Benefits section maybe redundant. But we could combine Pay and Benefits into one section? The instruction list includes Pay and Benefits separate. Might be better to have Pay section with that statement, and Benefits maybe omitted or combined. However the statement mentions both pay rate and benefits. So we could put that in Pay section, and not create Benefits section. Or we could create Benefits section with same statement. To avoid duplication, we can put in Pay section and note that benefits are per CBA. Thus we will have sections: About the role, Responsibilities, Requirements, Schedule, Pay. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include any extra text outside HTML. Let's craft. First, About the role:

  About the role

  then

  with the paragraph. Second, Responsibilities:

  Responsibilities

  then
  • items. Third, Requirements:

    Requirements

    then
    • items (including experience, education, familiarity, abilities, etc). Exclude schedule sentence. Fourth, Schedule:

      Schedule

      then

      with schedule sentence. Fifth, Pay