Operational Technology Analyst

We need to output HTML fragment with sections: h3 headings for sections that have real content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove application instructions. Must not include Pay/Schedule/Benefits unless posting actually states them. The posting includes benefits list, compensation, maybe schedule? Not schedule. So we include Benefits, Compensation (Pay). Also maybe "About the role" etc. The posting includes summary, responsibilities (What You'll Be Contributing), requirements (To Succeed In This Position, You Will Need). Also maybe "Qualifications". We'll map. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - Summary: "The OT Analyst supports..." That's about the role. Could be "About the role" or "Summary". Use "About the role" heading. - Responsibilities: "What You’ll Be Contributing" list of duties. Use "Responsibilities". - Requirements: "To Succeed In This Position, You Will Need" list of qualifications. Could be "Requirements" or "Qualifications". We'll use "Requirements". Might also separate "Skills" but we can combine. - Benefits: list of benefits. Use "Benefits". - Pay: compensation range. Use "Pay". - Schedule: not present, so omit. - Also maybe "Qualifications" separate from Requirements? But we can just have Requirements covering qualifications and skills. We must not create sections with filler like "commensurate with experience". Not present. We need to include all substantive info: company description? The first paragraph about Ash Grove family of companies etc. Should we include? It's substantive about company. Could be part of "About the role" or maybe a separate "About the company". But headings limited to given list; we could put under "About the role" or maybe not include a separate heading. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not limited to those? It says use those for section headings. Likely we should only use those headings. So we can put company overview under "About the role" or maybe not include a separate heading. But we need to preserve all substantive information. So we can include company description in a paragraph under "About the role". That seems fine. Also need to include "What’s next for you?" etc. That's more about opportunities; could be part of "About the role" or maybe "Benefits"? It mentions tuition reimbursement program etc. That's already in benefits list. The paragraph about stability and advancement opportunities could be under "About the role" or maybe a separate "About the company". But we can include under "About the role" as extra paragraph. Also need to include "What CRH Offers You" etc. That's more about CRH benefits; could be part of Benefits. But we already have benefits list from Ash Grove. The CRH section includes: Highly competitive base pay, Comprehensive medical, dental and disability benefits programs, Group retirement savings program, Health and wellness programs, An inclusive culture that values opportunity for growth, development, and internal promotion. This is also benefits. We should incorporate that into Benefits section, not duplicate but combine. Also need to include "About CRH" description. That's company info; could be under "About the role" or maybe we could add a separate "About the company" but not allowed heading. We'll incorporate into "About the role" paragraph. Also need to include EEO statements etc. Must remove boilerplate: EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we must remove the EEO statements, the "AI tools may be used..." etc. Also remove "Once you click apply now..." etc. Also remove "Thank you for your interest!" etc. Also remove "Ash Grove Cement, a CRH Company, is an Affirmative Action and Equal Opportunity Employer." etc. Also remove "CRH is an equal opportunity employer..." etc. Also remove "What’s next for you? We provide stability and advancement opportunities across North America. Use our tuition reimbursement program to help you meet your career goals." That's not boilerplate; it's substantive about opportunities. Keep. Also remove "The above duties and responsibilities are representative..." that's boilerplate? It's a generic disclaimer; might be considered boilerplate. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The disclaimer about duties representative might be considered legal boilerplate. Safer to remove? It's not explicitly listed but could be considered legal. I'd remove it to be safe. Also remove "The physical demands, working environment, and other conditions of employment listed in this document are representative..." etc. That's also legal boilerplate. Remove. Also remove "Reasonable accommodations may be made..." etc. That's also legal. Remove. Also remove "What CRH Offers You" maybe not boilerplate; it's benefits. Keep. Also remove "About CRH" description? It's company info; keep. Now we need to format lists with

• . For responsibilities list, we have many bullet points. We'll convert each line starting with a verb into
• . Ensure we keep all. Responsibilities list from "What You’ll Be Contributing": - Promote and follow all plant safety guidelines. - Provides day-to-day support for OT systems including SCADA, PLCs, HMIs, historians, and related plant-floor applications. - Diagnoses and troubleshoots system issues, working with plant operations, automation engineers, and vendors to resolve them. - Supports system upgrades, migrations, and deployments across sites. - Maintains accurate inventories and documentation of OT assets, network layouts, and system configurations across sites. - Keeps configuration records, diagrams, and standard operating procedures up to date as systems change. - Supports planning and execution of OT-related changes and projects, coordinating with plant operations to minimize disruption to production. - Participates in testing and validation of new systems, upgrades, or integrations before go-live. - Works with OEMs and third-party vendors on system implementations and support contracts. - Helps identify opportunities to standardize OT systems, configurations, and processes across multiple sites. - Supports the rollout of OT governance practices, templates, and best practices developed by the broader OT/IT team. - Provides input on tools and processes that improve reliability and reduce downtime. - Acts as a liaison between plant operations (MTS/OTS), automation engineering, and corporate IT teams. - Communicates clearly with non-technical stakeholders about system status, issues, and upcoming changes. - Supports training and knowledge-sharing with site teams on OT tools and processes. - Additional duties as assigned by supervisor We need to keep the verb forms as given; some start with "Promote", "Provides", etc. Keep as is. Now Requirements list from "To Succeed In This Position, You Will Need": - Ability to read, write and understand warning labels, instructions, signs, etc. - Minimum 2 Year - Associates Degree in Electrical/Industrial Engineering Technology, Computer Science, or related field required - 4 Year - BachelorsDegree in Electrical/Industrial Engineering Technology, Computer Science, or related field preferred (note missing space; keep as is) - Minimum 2 years of Experience supporting industrial/OT systems, automation, or plant IT environments. - Experience working with data - pulling, validating, and reporting on operational/process data. - Experience in manufacturing, cement, mining, or another heavy industrial sector. - Exposure to project management or change management processes in an industrial setting. - Working knowledge of SCADA, PLCs, HMIs, or historian systems. - Strong troubleshooting skills and ability to work through ambiguous, cross-system issues. - Good communication skills; able to work effectively with plant operators, engineers, and IT staff. - Ability to travel to plant/site locations. - Familiarity with industrial networking basics (Purdue Model, VLANs, network segmentation). - Up to 25% doemstic travel. (typo: domestic) We'll keep as is. Now Benefits list from "At Ash Grove Cement, people are our first priority. We offer a complete benefits package to include:" then list: - Company Benefits - Family Culture – We treat our team like family - Medical/Dental/Vision/Prescription - Generous Paid Time Off - 11 Paid Holidays per year - Retirement Plan - Opportunities for Internal Mobility - Professional Development Opportunities - Training Provided - Tuition Reimbursement Program - We'll assist with continuing education that aligns with your career goals - Employee Assistance Program - Company Paid Life Insurance - Short- & Long-Term Disability - Company Discounts on products, goods, services, electronics, automotive, travel & more! - Opportunities for Community Engagement - Potential Relocation Packages Also from "What CRH Offers You": - Highly competitive base pay - Comprehensive medical, dental and disability benefits programs - Group retirement savings program - Health and wellness programs - An inclusive culture that values opportunity for growth, development, and internal promotion We should combine and avoid duplicates. There's overlap: medical/dental/vision etc. We'll just combine all unique items. We need to output as
  • for each benefit. Now Pay: compensation range: "$86,000.00 - $105,100.00 USDEligible for yearly bonus". There's missing space before Eligible. We'll keep as is but maybe add a space. We should preserve exactly? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the text as given, but we can fix obvious typo? It's not a typo but missing space. Changing it would be altering. Better to keep as is: "$86,000.00 - $105,100.00 USDEligible for yearly bonus". That's the exact string. We'll output inside

    . Now we need to include sections only when posting has real specific content. We have About the role, Responsibilities, Requirements, Benefits, Pay. No Schedule. Now we need to output only HTML fragment, no /, no markdown fences. We'll structure:

    About the role

    ... company overview ... summary ... etc.

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Benefits

    • ...
    ...

    Pay

    $86,000.00 - $105,100.00 USDEligible for yearly bonus

    We need to ensure we include all substantive info from the posting: also the "What’s next for you?" paragraph and maybe the "At Ash Grove Cement, people are our first priority." Already captured benefits. The "What’s next for you?" we can include under About the role as a paragraph. Also the "At Ash Grove Cement, people are our first priority." is intro to benefits; we already have benefits list; we could include a short paragraph before the list: "At Ash Grove Cement, people are our first priority. We offer a complete benefits package to include:" but that's introductory; we can include as a

    before the

    . That's substantive. Also the "What CRH Offers You" we can incorporate into benefits list; maybe also include a paragraph before list: "What CRH Offers You:" but we can just add those items to the list. Also the "About CRH