Remote Operations SCADA UI/UX Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. No Job ID. Remove boilerplate. We need to parse the posting. Key content: - Intro: EthosEnergy is seeking a Remote Operations SCADA/HMI Engineer to support development, maintenance, and standardization of SCADA applications within ROC. Description of ROC, etc. That's about the role. - Then list of responsibilities: bullet list under "Job Responsibilities" with subheadings: SCADA Application Development, Tag Mapping & Data Integration, HMI Graphics Development, Visualization Standards & Template Development, Customer Asset Onboarding, Operational Collaboration & Support. Each has bullet points. - Required Skills / Knowledge: Technical Skills list, Preferred Qualifications list, Preferred Knowledge list, Characteristics of a Successful candidate list. - Experience: bullet list of experience requirements. - Education Requirements: bullet. - Physical Requirements: description. - What We Offer: bullet list of benefits. - EEO statement to remove. We need to map to sections: About the role (intro paragraph). Responsibilities (the responsibilities bullet list). Requirements (maybe experience + education? Could combine). Qualifications (maybe preferred qualifications/knowledge). Skills (technical skills). Benefits (What We Offer). Pay and Schedule: not mentioned, so omit. We must not create sections with placeholder text. So only include sections with real content. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include all bullet points exactly as given (maybe rephrase? Must preserve info, not invent, but we can keep same wording). We should not omit any bullet. We need to decide grouping. Let's extract content. Intro paragraph(s): "EthosEnergy is seeking a Remote Operations SCADA/HMI Engineer to support the development, maintenance, and standardization of SCADA applications within our Remote Operations Center (ROC). EthosEnergy’s (EEOM) Performance Center provides 24/7 remote monitoring and operational support for power generation assets across North America, including gas turbines, combined cycle facilities, renewable energy assets, and battery energy storage systems (BESS). The successful candidate will work closely with the OT Manager, ROC Operators, Controls Engineers, and customer site personnel to develop and maintain operator graphics and SCADA applications using AVEVA System Platform. This role includes:" Then bullet list of responsibilities (the list after "This role includes:"): Actually they list bullet points after colon: "Developing and maintaining AVEVA System Platform applications Creating and managing SCADA objects and templates Mapping PI, OPC, historian, and DCS data points into ROC systems Recreating customer operational displays within the ROC environment Maintaining graphics and displays as customer sites evolve Standardizing operator interfaces across multiple facilities Creating reusable templates, graphic libraries, and visualization standards Supporting onboarding of new customer assets and technologies Troubleshooting data integration and communications issues" Then later they have "Job Responsibilities" with subheadings and bullet points. We need to include all responsibilities. The intro bullet list may be redundant with later detailed responsibilities. We should preserve all substantive information; we can combine but must not lose detail. Probably better to include the detailed responsibilities under "Job Responsibilities" headings. The intro bullet list is somewhat covered but we can still include as part of responsibilities. We'll create a Responsibilities section with subheadings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid subheadings inside, but we should follow typical structure: maybe just a single Responsibilities section with

  • items. However we have many bullet points grouped under subheadings; we could keep them as
    • and maybe include the subheading as part of
    • text? But that would lose structure. The instruction didn't forbid using headings inside, but they gave examples of section headings only. Safer to keep only top-level sections; we can embed subheadings as or just plain text inside
    • . But we must preserve all substantive information; we can include the subheading as part of the list item text. Thus Responsibilities section will have a
      with each bullet point from the detailed list, preserving the subheading text as part of the item. Let's extract all bullet points from the detailed responsibilities: Under "SCADA Application Development": - Develop, configure, and maintain SCADA applications using AVEVA System Platform and related technologies. - Create and maintain object templates, symbols, graphic libraries, dashboards, and reusable application components. - Configure alarms, trends, equipment status indicators, KPIs, and operational displays. - Support continuous improvement of ROC SCADA applications and monitoring tools. - Maintain application documentation, design standards, and object libraries. Under "Tag Mapping & Data Integration": - Configure and maintain tag mappings between customer systems and ROC applications. - Integrate operational data from PI System, OPC DA/UA, historians, DCS platforms, PLCs, and other industrial systems. - Validate data quality, scaling, equipment status, alarm conditions, and operational functionality. - Troubleshoot data communication issues and integration challenges. - Support commissioning and testing of new site integrations. Under "HMI Graphics Development": - Develop industrial operator graphics and displays used by ROC operators for real-time monitoring and operational support. - Recreate customer site operating displays within the ROC environment. - Ensure graphics accurately represent process conditions, equipment status, alarms, and critical operating information. - Maintain graphics as customer systems and site configurations change. - Support development of equipment-specific and site-specific visualizations. Under "Visualization Standards & Template Development": - Develop and maintain fleet-wide SCADA visualization standards for the EthosEnergy ROC. - Create reusable graphic templates, symbols, navigation frameworks, and object libraries to support rapid deployment across multiple customer sites. - Establish standards for: o Alarm presentation o Color usage o Equipment status indication o Trends and historical data displays o Screen layouts o Navigation structures o Operator workflow consistency - Standardize visual representation of common equipment including gas turbines, HRSGs, steam turbines, auxiliaries, renewable assets, and battery energy storage systems. - Collaborate with ROC Operators and Controls Engineers to continuously improve operator effectiveness and situational awareness. - Maintain governance and quality control processes for all ROC graphics and visualization deployments. Under "Customer Asset Onboarding": - Support onboarding of new generation, renewable energy, and battery storage assets into the ROC. - Review customer control system architectures and available data sources. - Participate in integration testing, commissioning, and validation activities. - Develop graphics, mappings, templates, and operational displays for newly onboarded facilities. - Ensure ROC displays align with customer operational requirements and existing site practices. Under "Operational Collaboration & Support": - Work directly with ROC Operators to improve monitoring effectiveness and operational awareness. - Collaborate with Controls Engineers, OT personnel, and customer SMEs to ensure accurate process representation. - Support troubleshooting of SCADA, HMI, communications, and data integration issues. - Assist with platform upgrades, migrations, and system enhancements. - Participate in continuous improvement initiatives supporting ROC operations. Now Required Skills / Knowledge: Technical Skills: - AVEVA System Platform / Wonderware - Industrial SCADA architecture - OPC DA / OPC UA communications - PI System or industrial historians - SCADA object modeling and template development - Industrial networking fundamentals - Alarm management concepts - Trend configuration and data visualization - Industrial HMI development - Tag mapping and data integration - Troubleshooting industrial communications Preferred Qualifications (list): - Experience with one or more of the following: - AVEVA OMI - AVEVA Historian - PI System Administration - Siemens T3000 - Emerson Ovation - GE Mark VI / Mark VIe - ABB control systems - Ignition SCADA - FactoryTalk View - GE iFIX - CIMPLICITY - Remote Operations Centers (ROC) - Power generation facilities Preferred Knowledge: - Power generation operations - Control narratives - P&IDs - Instrumentation diagrams - Industrial communication architecture - High Performance HMI principles (ISA-101) - Alarm management principles (ISA-18.2) - Operator situational awareness practices - Industrial Human Factors - Industrial cybersecurity awareness Characteristics of a Successful candidate: - Strong troubleshooting and analytical skills - Ability to work effectively with operators, engineers, and customers - Detail-oriented approach to SCADA application development - Strong organizational and documentation skills - Ability to manage multiple integration and development projects simultaneously - Strong verbal and written communication skills - Commitment to operational excellence, safety, and reliability Experience: - 5+ years of experience in SCADA, HMI, DCS, or industrial automation systems. - Experience developing industrial operator displays and SCADA graphics. - Experience with AVEVA System Platform / Wonderware or similar industrial SCADA platforms. - Experience with SCADA object development, template creation, and symbol libraries. - Experience mapping and troubleshooting industrial data points. - Experience integrating data from OPC, PI System, historians, PLCs, or DCS systems. - Experience supporting industrial facilities, utilities, power generation, manufacturing, oil & gas, or process industries. - Experience developing standardized graphics and reusable visualization components across multiple sites or assets. Education Requirements: - Bachelor’s degree in Electrical Engineering, Controls Engineering, Automation Engineering, Computer Engineering, Industrial Engineering - Equivalent industrial automation or SCADA engineering experience may be considered in lieu of formal education requirements. Physical Requirements: - Hybrid of office-based development and real-time collaboration with a Houston based 24/7 operations team - Direct interaction with live plant data and operational environments via cyber secure methods - Houston residence is preferred What We Offer: - Supportive company culture that values its employees - Comprehensive Medical, Dental, Vision & 401 K Plan - Paid Parental Leave, Time Off & Holidays - Extra money in your paycheck - Employee Referral Bonus - Personal Development & Career Succession Planning - Company sponsored Perks & Discount programs Now we need to map to sections. About the role: intro paragraph(s) before "This role includes:" maybe combine with that sentence? We'll include the paragraph up to "This role includes:" as prose. Could also include the bullet list after "This role includes:" as part of Responsibilities (makes sense). So About the role will be the introductory paragraph(s) before the bullet list. Let's extract that: "EthosEnergy is seeking a Remote Operations SCADA/HMI Engineer to support the development, maintenance, and standardization of SCADA applications within our Remote Operations Center (ROC). EthosEnergy’s (EEOM) Performance Center provides 24/7 remote monitoring and operational support for power generation assets across North America, including gas turbines, combined cycle facilities, renewable energy assets, and battery energy storage systems (BESS). The successful candidate will work closely with the OT Manager, ROC Operators, Controls Engineers, and customer site personnel to develop and maintain operator graphics and SCADA applications using AVEVA System Platform." That's the prose. We'll put that in

      . Now Responsibilities: we will list all bullet points from the detailed responsibilities (including the subheadings maybe as part of items). We'll preserve them exactly. We need to ensure we don't lose any bullet. We'll create a

      with each
      • containing the bullet text. We need to include the subheadings as part of the items? For clarity, we could include them as inside the
      • . That preserves info. Let's list each bullet: From SCADA Application Development: - Develop, configure, and maintain SCADA applications using AVEVA System Platform and related technologies. - Create and maintain object templates, symbols, graphic