Operations Control Center Supervisor (OCC)

We need to output HTML fragment with sections: About the role? The description includes a summary and description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the posting. Content: - Description: "We are committed to building a workplace..." That's about culture, could be "About the role"? Actually "About the role" could be description of role. The summary: "The Operations Control Center (OCC) Supervisor is responsible for supervising 24/7 control-room operations, ensuring renewable energy assets operate safely, reliably, and efficiently while meeting grid, market, and regulatory requirements. The supervisor leads control-room operators, coordinates with field technicians, grid operators, maintenance teams, and management, and responds to operational events and emergencies. This role will require 5 days in office." That's a good summary for About the role. Responsibilities: The "Requirements" section in the posting actually lists many duties (Leads and mentors..., Responsible for adequate shift coverage..., Conducts shift briefings..., etc). Those are responsibilities. So we can put those under Responsibilities. Requirements: The posting has a "Requirements" heading with bullet-like sentences: "Leads and mentors control-room operators working rotating shifts." etc. Actually those are responsibilities. But the posting also has a "Qualifications" heading later. So we need to separate: Requirements maybe refers to mandatory experience? The posting has "Qualifications" section with education, years experience, etc. Also "Requirements" earlier includes many duty statements. According to instruction, we should use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. - About the role: summary paragraph. - Responsibilities: list of duties (the long list under "Requirements" heading in the posting). That includes leading operators, shift coverage, briefings, evaluations, overseeing operations, monitoring SCADA, maintaining procedures, coordination, emergency response, maintenance, logs, audits, safety, leadership, employee development, etc. Actually many of those are responsibilities. - Requirements: maybe the mandatory experience/education? But we have Qualifications for education and experience. The posting has "Qualifications" heading with education, years experience, etc. Also "Requirements" earlier includes duty statements; but we already used those for Responsibilities. So maybe Requirements could be things like "Domestic travel 5-15% required." or "Attends work regularly and punctually". However those are more like expectations. But we can put travel requirement under Requirements. - Qualifications: education, years experience, technical knowledge, leadership, operational, safety knowledge, functional competencies. - Skills: maybe we can extract from qualifications: Technical Knowledge, Leadership, Operational, Safety Knowledge, Functional competencies. Could be a separate Skills section. - Benefits: list of benefits under "RES offers benefits...". - Pay: salary range "$90,200 - $112,800" plus bonus eligibility. - Schedule: "This role will require 5 days in office." Also maybe shift work? Not given. So we can include schedule: 5 days in office (maybe also 24/7 shift coverage? but that's responsibility). We'll include schedule. We must not include boilerplate like EEO, drug-free workplace, background check, etc. Also remove duplicated lines. We must preserve all substantive information; do not invent or summarize away detail. Must not create sections with filler like "commensurate with experience". We have actual content. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

The Operations Control Center (OCC) Supervisor is responsible for supervising 24/7 control-room operations, ensuring renewable energy assets operate safely, reliably, and efficiently while meeting grid, market, and regulatory requirements. The supervisor leads control-room operators, coordinates with field technicians, grid operators, maintenance teams, and management, and responds to operational events and emergencies. This role will require 5 days in office.

Responsibilities

• Leads and mentors control-room operators working rotating shifts.
• Responsible for adequate shift coverage.
• Conducts shift briefings, handovers, and operational reviews.
• Evaluates operator performance and provide coaching/training.
• Complies with Employee Handbook, Code of Conduct and Company Policies & Procedures.
• Oversees day-to-day and 24/7 control-room operations for renewable generation and storage assets.
• Oversees real-time monitoring and control through SCADA, EMS, HMI, or other control platforms.
• Maintains operating priorities for abnormal conditions, equipment failures, communications issues, and grid events.
• Ensures appropriate response to alarms, trips, outages, curtailment instructions, and system disturbances.
• Maintains effective operating procedures and escalation protocols.
• Responsible for coordination with transmission/distribution system operators and balancing authorities.
• Ensures OCC is following dispatch instructions and manage generation according to grid requirements.
• Responsible for OCC supporting grid reliability, voltage/frequency control, curtailment, and restoration activities.
• Ensures compliance with applicable operating procedures and NERC compliance guidelines.
• Leads the control-room response to equipment failures, communications loss, severe weather, cyber/physical security events, and grid disturbances.
• Escalates significant events according to emergency procedures.
• Coordinates with field personnel and emergency-response teams.
• Conducts post-event reviews and identify corrective actions.
• Coordinates planned and unplanned maintenance with Project Managers and field teams.
• Manages real-time equipment outages and return-to-service activities.
• Ensures appropriate switching, isolation, and work-clearance procedures are followed.
• Ensures the maintaining of accurate operating logs, reports, and event records.
• Ensures procedures comply with company policies and applicable regulatory/grid requirements.
• Participates in audits, procedure development, and operational readiness exercises.
• Attends work regularly and punctually, as scheduled or expected.
• Coordinates with OCC Director and Manager to fulfill customer requests and needs.
• Supports OCC Director and Manager to onboard new operational assets.
• Supports OCC Specialist in developing and maintain tools for the OCC.
• Safety: Presents, supports, and leads-by-example with a safety and quality-oriented attitude; leads by example to show that safety is the most important function, ensuring that all employees follow safe practices while working; accountable to continually reinforce safe behaviors and correct “at risk” behaviors; adheres to and ensures all site team members understand standard operating procedures; leads and supports the site team in technical, quality and safety, utilizing system in place.
• Leadership: Fosters and demonstrates a workplace inclusive of creating opportunity, serving others, building trust, innovation, and exceeding expectations; manages one or more direct reports; participates in hiring and selection process to fill positions on the team; communicates regularly with direct reports on goals, accomplishments, and information on policies; demonstrates leadership and expertise in eyes of client group; employee development: provides tasks and assignments that challenge and stretch employees’ responsibilities; conducts regular discussions with employee(s) on personal development; comfortable with empowering others; conducts timely, effective performance reviews in accordance with RES guidelines.

But we have a lot; maybe we should split safety and leadership into separate sections? But we only have allowed headings; we could keep them within Responsibilities as list items; that's okay. Now Requirements: maybe include domestic travel requirement and maybe "Attends work regularly and punctually" but that's already in responsibilities. We could put travel under Requirements. Also maybe "Complies with Employee Handbook, Code of Conduct and Company Policies & Procedures." is also in responsibilities. We'll put Requirements: Domestic travel 5-15% required. Also maybe "This role will require 5 days in office." but that's schedule. We'll put Requirements as:

Requirements

• Domestic travel 5-15% required.

Qualifications: include education, years experience, technical knowledge, leadership, operational, safety knowledge, functional competencies. We need to preserve all detail; we can break into list items. Qualifications: - Highschool/ GED Required. - Associate’s degree in Electrical Engineering, Power Systems, Renewable Energy, Engineering Technology, or a related field, or equivalent operational experience preferred. - Bachelor’s degree in Electrical Engineering, Power Systems, Renewable Energy, Engineering Technology, or a related field, or equivalent operational experience preferred. - 5+ years power generation, renewable energy operations, utility operations, transmission/distribution experience required. - 5+ years Control Room Operations experience required. - 5+ years with SCADA, EMS, HMI, or other control systems experience required. - 5+ years with NERC Reliability Standards experience required. - Technical Knowledge: SCADA/EMS, electrical systems, renewable generation, BESS, grid operations, alarms/events, switching procedures. - Leadership: shift supervision, coaching, decision-making under pressure, cross-functional coordination. - Operational: outage management, emergency response, dispatch coordination, root-cause analysis, operational reporting. - Safety Knowledge: electrical safety, switching procedures, job hazard awareness, emergency procedures. - Functional competencies include attention to detail, collaboration, communication, continuous improvement, and managing vision & purpose. We'll put each as

. Skills: maybe we can extract from qualifications: Technical Knowledge, Leadership, Operational, Safety Knowledge, Functional competencies. But we already have them under qualifications; maybe we can create Skills section summarizing those. However we must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we create Skills section, we would be moving content from Qualifications to Skills, but still preserving. It's okay as long as we don't lose detail. But we need to decide if we need Skills section. The posting does not have a separate "Skills" heading; but we can create one if we have specific content. The qualifications already list skills. Could we just not include Skills section? The instruction: Prefer a few substantive sections over many thin ones. So maybe we omit Skills and keep qualifications as is. But we need to include Skills only if posting has real specific content for it. The posting does not have a separate Skills heading, but the qualifications contain skill details. However we could still create a Skills section and list those skill items; but that would be splitting qualifications. Might be considered inventing a section not present. Safer to not create Skills section unless there is explicit "Skills" heading. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid creating a section if the content exists elsewhere; but we must not invent heading that isn't in posting? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect us to use those headings if we have content. So we can create Skills section if we have skill-specific content. The posting does have skill-specific content under Qualifications. So we can move those to Skills. But then Qualifications would be left with just education and experience? That might be okay. Let's decide: We'll create Skills section with the bullet items: Technical Knowledge, Leadership, Operational, Safety Knowledge, Functional competencies. Qualifications will then contain education and experience requirements. Benefits: list as per posting. Pay: salary range and bonus eligibility. Schedule: 5 days in office. Now we need to ensure we don't include boilerplate: EEO, drug-free workplace, background check, equal opportunity, etc.