Manager, Operations SCADA & OT

We need to output HTML fragment with sections: About the role? Actually we have "About The Company" and "Job Summary". The instructions: use

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

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We have FLSA Classification: Exempt Salary Range: $160,000 - $175,000 plus bonus and incentive stock options Location: Brooklyn, NY (Hybrid). That's pay and location. We need to include Pay section if posting actually states them. Yes, salary range is given. So we can have a Pay section with that info. Also location maybe part of a meta paragraph? Not required to have a location section; we can fold location into a short

  maybe under a meta paragraph. But we have to not repeat job title. We can include a short paragraph for metadata like "FLSA Classification: Exempt | Location: Brooklyn, NY (Hybrid)". That is minor metadata. We need sections: About the company? The instruction list includes "About the role" as example, but we have "About The Company" and "Job Summary". We could combine them into an "About the role" section? But we should preserve content. Perhaps we create sections: About the company (maybe not in list but we can still use

  About the company). The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings where applicable. We have responsibilities (list). We have qualifications (required education and experience, plus preferred). We have skills (core competencies). We have benefits (list). We have pay (salary range). We have maybe "About the role" could contain Job Summary and About The Company? The instruction says do NOT repeat the job title as a heading. So we can have an "About the role" section that includes the job summary and about the company. That seems appropriate. Thus sections: About the role (contains Job Summary and About The Company paragraphs). Responsibilities (list). Qualifications (maybe combine Required and Preferred? Could split into Required education and experience and Preferred education and experience). But we could have a Qualifications section with subparts? The instruction says use

  • for any list of duties/requirements/benefits. So for qualifications we can list required and preferred as separate
    maybe with headings inside? But we cannot add extra headings besides

    . Could we have

    with bold? Not allowed? Only allowed tags:

    ,

    • ,

      . We can use

      for prose. So we could have a

      that says "Required education and experience:" then a

      for list. Then another

      for "Preferred education and experience:" then another

      . That's okay. Skills: Core Competencies list. Use
      • . Benefits: list given. Use
        • . Pay: we have salary range plus bonus and incentive stock options. Use

          maybe. We also have FLSA Classification and location; we can put in a

          before sections. We must not include boilerplate like EEO etc. Remove those paragraphs at end: "Safety Sensitive Designation", "Reasonable accommodations...", "At NineDot Energy, we believe diverse perspectives..." etc. Those are EEO/boilerplate; remove. Also remove "NineDot Employee benefits include but are not limited to:" maybe we keep benefits list but remove that intro sentence? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The benefits list is substantive; the intro sentence is maybe not needed but could be considered part of benefits. We can keep it as a

          before the list, but it's not a list item. It's okay. We need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

          FLSA Classification: Exempt | Location: Brooklyn, NY (Hybrid)

          About the role

          About The Company: NineDot's name derives from the classic mathematical puzzle for sparking out-of-the-box solutions. As a leading community-scale, clean energy developer with a growing portfolio of projects across a range of technologies, NineDot Energy is creating innovative energy solutions that support a more resilient electric grid, deliver economic savings, address environmental justice and reduce carbon emissions. Our pipeline includes more than 1 GW of clean energy projects designed to strengthen local power grids and provide clean, reliable and resilient power to the communities we serve. With the backing of Manulife Investment Management and The Carlyle Group - two of the world's leading infrastructure investors - NineDot is continuing to expand its core battery energy storage pipeline, deliver enhanced products and services, explore new regions and consider potential acquisitions all to advance the decarbonization of New York's grid. This is an exciting opportunity to build a platform from the ground-up with a world-class team of developers and innovators.

          Job Summary: The Manager, Operations SCADA & OT serves as NineDot Energy's hands-on technical owner for SCADA and supports Operational Technology (OT) infrastructure across its growing portfolio of Battery Energy Storage Systems (BESS) and distributed energy assets. This is a hands-on technical leadership role with primary responsibility for the development, operation, maintenance, and continuous improvement of NineDot's Ignition SCADA platform. The Manager will work directly within Ignition while also managing external SCADA integrators, leading commissioning and testing, and establishing technical standards across the fleet. A key objective of this role is to lead NineDot's transition from individual site-level SCADA systems to a standardized, scalable enterprise SCADA platform that provides centralized monitoring, control, alarming, historian functionality, and operational visibility across the portfolio. The role will also provide technical ownership of supporting OT networks and telecommunications, implement practical OT cybersecurity controls, and provide SCADA and controls-related technical support to the O&M team.

          Responsibilities

          • SCADA / Ignition Ownership: Serve as NineDot's internal technical owner and subject-matter expert for the Ignition SCADA platform.Develop and modify Ignition screens, dashboards, templates, tags, alarms, trends, historian configurations, and related functionality.Troubleshoot the full SCADA data path, including Ignition gateways, scripts, databases, device connections, field controllers, site networks, communications, and backend applications.Administer SCADA software, firmware, configurations, backups, licensing, upgrades, and overall system health.Develop fleet-wide standards for SCADA architecture, visualization, alarming, naming conventions, data structures, and documentation.Lead the transition from individual site systems to a standardized enterprise SCADA platform.
          • Integrator Management & Commissioning: Serve as NineDot's technical lead for SCADA and controls integrators, maintaining sufficient internal expertise to independently troubleshoot and modify NineDot's systems.Develop technical requirements, scopes of work, standards, and acceptance criteria for new projects.Review integrator designs and deliverables, including points lists, control narratives, programming, screens, and system configurations.Lead or oversee FAT, SAT, point-to-point testing, alarm verification, functional testing, and end-to-end SCADA commissioning.Coordinate integration between BESS/EMS platforms, PLCs/RTACs, meters, relays, utilities, and NineDot SCADA systems.Ensure commissioning deficiencies are documented and resolved prior to operational turnover.
          • OT Networking, Telecommunications & Cybersecurity: Own and standardize the OT network architecture and connectivity supporting NineDot's SCADA environment, including IP addressing, remote access, network documentation, and communications with field equipment, utilities, and external systems.Configure and troubleshoot switches, routers, firewalls, VPNs, cellular gateways, and other OT network equipment.Manage telecommunications requirements and vendors across the project lifecycle, including contracts, service levels, renewals, billing, connectivity, and vendor performance.Implement and maintain practical OT cybersecurity controls, including user permissions, secure remote and vendor access, network segmentation, firewall rules, and system configurations.Maintain OT asset and configuration inventories and coordinate patching, vulnerability remediation, backups, and recovery activities.Work with NineDot IT and external cybersecurity resources where IT and OT responsibilities intersect.
          • O&M & Project Support: Provide advanced technical support and root-cause analysis for SCADA, controls, communications, alarms, and other OT-related issues, using historian, alarm, and event data as appropriate.Develop diagnostic tools, dashboards, trends, and alarms that improve O&M effectiveness.Support project design reviews and incorporate operating lessons learned into future designs and fleet-wide technical standards.Train O&M personnel on SCADA functionality, alarms, controls, and basic troubleshooting.Other duties as assigned.
          But the responsibilities list originally had bullet points with sub-bullets. We could keep each main heading as a list item and include the details inside that item as text. That's acceptable. Now Qualifications:

          Qualifications

          Required education and experience:

          • Bachelor's degree in Electrical Engineering, Controls Engineering, Computer Engineering, Automation Engineering, Computer Science, or a related technical field. Equivalent relevant experience may be considered.
          • 10+ years of progressively responsible experience with SCADA, industrial controls, automation, OT, power generation, utilities, renewable energy, or similar industrial systems.
          • Demonstrated hands-on experience developing, configuring, maintaining, and troubleshooting SCADA systems.
          • Experience developing HMI screens, tags, alarms, trends, historian configurations, scripts, and system integrations.
          • Experience commissioning SCADA and controls systems, including point-to-point and functional testing.
          • Working knowledge of industrial networking, TCP/IP, VPNs, firewalls, switches, routers, and telecommunications.
          • Experience managing SCADA/controls integrators and technical vendors.
          • Ability to read and interpret electrical one-lines, control schematics, network diagrams, points lists, and technical specifications.
          • Strong troubleshooting, communication, and project-management skills.

          Preferred education and experience:

          • Hands-on experience with Inductive Automation Ignition strongly preferred.
          • Experience with Ignition Perspective and/or Vision, Gateway administration, Tag Historian, alarming, scripting, and database integration.
          • Experience with Python/Jython, SQL, APIs, or similar technologies used in SCADA applications.
          • Experience with Modbus TCP/RTU, DNP3, OPC UA, MQTT, or similar industrial protocols.
          • Experience with PLCs, SEL RTACs, protective relays, utility meters, and other intelligent electronic devices.
          • Experience with BESS, solar PV, distributed energy resources, substations, or inverter-based resources.
          • Experience developing or supporting multi-site or enterprise SCADA architectures.
          • Familiarity with industrial