Control Systems Specialist/Engineer
ONEOK · Shawnee, KS · 1 mo ago
On-siteEngineering$100k–$150k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes "Job Summary", "Job Profile Summary", "Essential Functions And Responsibilities", "Education", "Work Experience", "Knowledge, Skills And Abilities", "Licenses and Certifications", "Strength Factor Rating - Physical Demands/Requirements", "Strength Factor Description - Physical Demands/Requirements", "Working Conditions/Environment", "Travel", "Driving". Also "Expected Salary Range". We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, equal opportunity, scam warning, etc. Also remove navigation/cookie etc. Also remove application instructions (none present). We need to preserve all substantive info.
We need to decide which sections to use.
- About the role: could contain Job Summary and Job Profile Summary (description of role). Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, but we should prefer those headings. However we could also add other headings if needed? The instruction: "Use
About the role
then paragraphs. - Responsibilities: Essential Functions And Responsibilities. - Requirements: could include Education, Work Experience, Licenses and Certifications, maybe Strength Factor? But Strength Factor is physical demands; could be part of Requirements or maybe separate? The allowed headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Requirements for education/experience/licenses. Qualifications maybe for knowledge/skills/abilities? But we also have Skills heading. We need to decide. We have Knowledge, Skills And Abilities section. That could go under Skills heading. Or we could put under Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which to include. We have content for: About the role (Job Summary + Job Profile Summary). Responsibilities (Essential Functions). Requirements (Education, Work Experience, Licenses and Certifications). Skills (Knowledge, Skills And Abilities). Pay (Expected Salary Range). Schedule? Not present; there is mention of on-call support with rotating shifts, up to 30% travel. That's schedule-ish but not explicit schedule like shift times. Could we put Schedule? The posting mentions "On-call support with rotating shifts." That's schedule info. Also travel up to 30% may be required. Could be considered Schedule? Might be better to put under Responsibilities? But we have a Schedule heading allowed; we could include schedule info there. However we must not create a Schedule section unless posting actually states them. It does state on-call support with rotating shifts. So we can include Schedule section with that info. Benefits: Not mentioned. So omit Benefits. We also have Working Conditions/Environment, Travel, Driving, Strength Factor etc. Where to put? Could be part of Requirements? Or maybe we can add a separate section like "Working Conditions" but not allowed headings. The allowed headings list is not exhaustive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, but we should prefer those headings. However we could also add other headings if needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also use other headings if needed? Safer to stick to those. However we have substantive info like Working Conditions, Travel, Driving, Physical Demands. Where to place? Could be part of Responsibilities? Not really. Could be part of Requirements? Possibly as "Working Conditions" but not allowed. Could we embed them in paragraphs under About the role or Responsibilities? The instruction: "Preserve ALL substantive information". So we need to include them somewhere. We could add a section like "Working Conditions" using Working Conditions
even though not in the list? The instruction says use those headings for section headings (e.g. ...). It doesn't forbid other headings, but says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That could be interpreted as you should use those headings when applicable; but you could also use other headings if needed. However to be safe, maybe we can incorporate those details into existing sections: e.g., Working Conditions could go under About the role or Responsibilities as extra paragraphs. Travel and Driving could go under Schedule (since schedule includes travel). Physical Demands could go under Requirements (as part of job requirements). Let's try.
Thus sections:
- About the role: Job Summary + Job Profile Summary + Working Conditions/Environment? Maybe we keep Working Conditions separate but we can add a paragraph after Job Profile Summary.
- Responsibilities: Essential Functions And Responsibilities.
- Requirements: Education, Work Experience, Licenses and Certifications, Strength Factor Rating/Description (Physical Demands). Also maybe include Knowledge? No that's Skills.
- Skills: Knowledge, Skills And Abilities.
- Pay: Expected Salary Range.
- Schedule: On-call support with rotating shifts, up to 30% travel may be required, Driving (company vehicle requiring applicable driver's license). Also maybe mention travel.
We must not include boilerplate like EEO etc. Remove those lines.
Now we need to format using for each section heading, then content: use
Working Conditions
even though not in the list? The instruction says use those headings for section headings (e.g. ...). It doesn't forbid other headings, but says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That could be interpreted as you should use those headings when applicable; but you could also use other headings if needed. However to be safe, maybe we can incorporate those details into existing sections: e.g., Working Conditions could go under About the role or Responsibilities as extra paragraphs. Travel and Driving could go under Schedule (since schedule includes travel). Physical Demands could go under Requirements (as part of job requirements). Let's try.
Thus sections:
- About the role: Job Summary + Job Profile Summary + Working Conditions/Environment? Maybe we keep Working Conditions separate but we can add a paragraph after Job Profile Summary.
- Responsibilities: Essential Functions And Responsibilities.
- Requirements: Education, Work Experience, Licenses and Certifications, Strength Factor Rating/Description (Physical Demands). Also maybe include Knowledge? No that's Skills.
- Skills: Knowledge, Skills And Abilities.
- Pay: Expected Salary Range.
- Schedule: On-call support with rotating shifts, up to 30% travel may be required, Driving (company vehicle requiring applicable driver's license). Also maybe mention travel.
We must not include boilerplate like EEO etc. Remove those lines.
Now we need to format using for each section heading, then content: use
for prose,
- for any list of duties/requirements/benefits.
We need to decide what content is list-like. The Essential Functions And Responsibilities is a long paragraph with many sentences separated by periods. Could be turned into list items for each responsibility. The instruction: Use
- for any list of duties/requirements/benefits. So we should break responsibilities into list items. Similarly, Knowledge, Skills And Abilities could be list. Education, Work Experience, Licenses could be list? Probably not necessary but could be list. We must preserve all substantive information, not invent or summarize away detail. So we need to keep the exact wording? We can rephrase slightly but must preserve meaning. Safer to keep sentences as is, maybe split into list items each starting with a verb. We need to be careful not to lose any detail. Let's extract sections. Job Summary: "The Control Systems Specialist/Engineer provides control system development and support of Programmable Logic Controller (PLC) and Human Machine Interface (HMI) systems. Commissions new facilities and troubleshoots and supports existing systems for ONEOK Refined Product & Crude operations. This job is safety-sensitive and subject to DOT and Pipeline Hazardous Materials Safety Administration (PHMSA) regulations." Job Profile Summary: "The incumbent works under limited supervision and performs a full range of responsibilities within the Controls Technology group. Although guidelines are established, the position requires the ability to deal with anomalies on a regular basis. Broad use and/or application of advanced principles/theories/concepts in applicable discipline plus a good working knowledge of other related fields. Compiles, examines or analyzes information and provides resolutions to a diverse range of moderate to complex problems/issues where an evaluation of identifiable factors is regularly required. Works under minimal supervision with little instruction on day-to-day work and only general instruction on new projects/assignments. Work is generally evaluated on completion to ensure objectives have been met. On-call support with rotating shifts. Up to 30% travel may be required. Title, grade, and wage will be commensurate with background, skills, and experience." Note: On-call support with rotating shifts and up to 30% travel also appear here; but we will move travel and on-call to Schedule section later to avoid duplication. However we must preserve all info; we can include them in both sections? Better to avoid duplication but still preserve. We could keep them in About the role (Job Profile Summary) and also mention in Schedule? That would duplicate. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but we should avoid unnecessary duplication? Not explicitly forbidden. However we should aim to not repeat. We could keep them in About the role and not duplicate in Schedule, but then Schedule would be missing that info. However Schedule section is optional; we only include if posting has real specific content for it. The posting does have on-call support with rotating shifts and up to 30% travel. So we need a Schedule section. We could move those sentences to Schedule and remove from About the role to avoid duplication. But then About the role would lose that info. However we could keep a brief mention? The instruction says preserve ALL substantive information; we can't omit. So we need to include that info somewhere. If we put it in Schedule, we still preserve it. It's okay to remove from About the role if we move it there. But we must ensure we don't lose any info. So we can cut those sentences from Job Profile Summary and place them in Schedule. Then About the role will have Job Summary + Job Profile Summary without those sentences. Let's see if any other info about travel appears elsewhere: Travel section later says "Travel Travel up to 30% may be required". So we have duplicate. We'll handle. Thus About the role content: Job Summary + Job Profile Summary (excluding the on-call/travel sentences). Let's extract Job Profile Summary without those two sentences. Job Profile Summary original: "The incumbent works under limited supervision and performs a full range of responsibilities within the Controls Technology group. Although guidelines are established, the position requires the ability to deal with anomalies on a regular basis. Broad use and/or application of advanced principles/theories/concepts in applicable discipline plus a good working knowledge of other related fields. Compiles, examines or analyzes information and provides resolutions to a diverse range of moderate to complex problems/issues where an evaluation of identifiable factors is regularly required. Works under minimal supervision with little instruction on day-to-day work and only general instruction on new projects/assignments. Work is generally evaluated on completion to ensure objectives have been met. On-call support with rotating shifts. Up to 30% travel may be required. Title, grade, and wage will be commensurate with background, skills, and experience." Remove "On-call support with rotating shifts." and "Up to 30% travel may be required." Also maybe remove "Title, grade, and wage will be commensurate with background, skills, and experience." because that is about Pay; we will move to Pay section. So we remove that too. Thus remaining: "The incumbent works under limited supervision and performs a full range of responsibilities within the Controls Technology group. Although guidelines are established, the position requires the ability to deal with anomalies on a regular basis. Broad use and/or application of advanced principles/theories/concepts in applicable discipline plus a good working knowledge of other related fields. Compiles, examines or analyzes information and provides resolutions to a diverse range of moderate to complex problems/issues where an evaluation of identifiable factors is regularly required. Works under minimal supervision with little instruction on day-to-day work and only general instruction on new projects/assignments. Work is generally evaluated on completion to ensure objectives have been met." Now About the role will have Job Summary + that. Now Responsibilities: Essential Functions And Responsibilities paragraph. Let's extract that block: "Designs and develops industrial control system solutions including Programmable Logic Controller (PLC) and Human Machine Interface (HMI) programs to address operational needs for new construction projects, maintenance projects or operational requests.Provide assistance and analysis regarding industrial control systems to commercial, operations and engineering.Investigates new technology, along with methods to reduce hardware costs and labor expenses as it relates to automation.Ensure compliance with company Cybersecurity efforts through evaluation, configuration and deployment of secure solutions for Operation Technology (OT) devicesProvides automation solution estimates to project managers, facility engineers, and others. Provide creative engineered designs for PLC programming. Provide project management and oversight for assigned projects, including expansion, regulatory and modification projects at ONEOK. Follow Project Life Cycle and OMS to ensure that all projects meet quality