Supervisor - Engineering - Model Maintenance

We need to output HTML fragment with sections: About the role? The posting includes a paragraph about ERCOT environment, then Job Summary, Job Duties, Additional Job Duties, Experience, Education, Certification, Work Location, Expected Salary Range. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to map content to these headings. We have: - About the role: could be the initial paragraph describing ERCOT environment and encouraging to join. That's about the role? Might be considered "About the role". We'll include. - Responsibilities: combine Job Duties Job Duties and Additional Job Duties (they are responsibilities). We'll list as

• . - Requirements: Experience Requires etc. Also maybe Education and Certification? Those could be Qualifications. The spec says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put Education, Certification, etc. Possibly Qualifications includes Education and Certification. Requirements could be experience. Skills maybe not present; we can omit if no specific skills listed. Benefits not present; we can omit. Pay: we have Expected Salary Range. Schedule: we have Work Location: hybrid 2 days per week (that's schedule? maybe schedule includes hybrid). We'll put Schedule section for hybrid work. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO statement at end; we must remove that. Also remove "The foregoing description reflects the minimum qualifications..." etc? That's boilerplate? It's generic but maybe considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The paragraph about "The foregoing description reflects the minimum qualifications..." is likely boilerplate legal disclaimer; we should remove it. Also the statement about employment-at-will etc. Remove. Also the EEO statement at end remove. We must keep: initial paragraph about ERCOT environment, Job Summary, Job Duties, Additional Job Duties, Experience Requires, Education, Certification, Work Location, Expected Salary Range. We must not repeat duplicated lines: there are duplicated responsibilities (some appear both in Job Duties and Additional Job Duties). We need to preserve all substantive information but avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicated lines: we should not repeat duplicated lines. So we need to deduplicate. Let's list duties: From Job Duties: - Responsible for hiring, coaching, training, and performance management of staff. - Frequently interacts with direct reports and functional peer groups. Interaction normally requires the ability to gain cooperation of others. - Provides direct supervision to professional individual contributors and/or skilled, support individual contributors. - Acts as an advisor to department and may become actively involved, as required, to meet schedules and resolve problems. - A small portion of time is normally spent performing individual tasks related to the department. - Typically has full responsibility for direct reports. - May provide input to budgeting and financial decisions that impact the department. - Requests approval for financial actions beyond a limited scope per policy. Additional Job Duties: - Responsible for the validation, generation and implementation of both Network Operations Model changes and case building. - Supports the development and activities associated with the Engineering Development Program (EDP) - Provides information and support as necessary to other ERCOT departments and to the various ERCOT stakeholder committees, working groups, and task forces - Responsible for hiring, coaching, training, and performance management of staff (duplicate) - Review and approve staff timesheets and leave requests - On-the-job training, career guidance and mentoring employees - Ensures training and evaluation of members of the Engineering Development Program (EDP) provides a competent coverage of the Network Modeling Process - Develops and implements innovative solutions that promote the continued evolution and success of the existing ERCOT modeling systems - Evaluates, recommends, and confirms the documentation of guidelines and operations procedures that ensure the accuracy of System Operations cases - Ensures the resolution of complex problems related to System Operations and ERCOT modeling systems providing modeling analysis, reports, and investigation/review both written and oral - Bears the accountability for that the Network Model being ready for use in the various operations applications whenever changes or updates to the model are made - Reviews contingencies, issues and recommendations that possibly affect or improve the modeling process - Validates the database and Market testing of the Operational models and associated market information - Verifies appropriate data to IT EMMS, IT MMS, System Planning, System Operations, and other ERCOT groups - Leads and/or represent ERCOT in technical committees and subcommittees - Serves as expert witness on ERCOT network modeling matters - Participates in development and administration of department budget and financial goals - Assists in establishing department goals and initiatives to implement them We need to combine and remove duplicates: hiring, coaching, training, performance management of staff appears twice; we keep once. Also "Provides information and support as necessary to other ERCOT departments..." etc. We'll create a Responsibilities
  with each distinct duty. Now Experience: "Requires minimum 5 years job related work experience and 1 year in a leadership role preferred in excess of degree requirements. Minimum years of job related experience can include time in leadership roles. Requires minimum of 5 years experience in system operations Prefer prior experience supervising or leading a team or projects". We'll combine. Education: "Bachelor's Degree : Electrical Engineering or related field (Required) Master's Degree : Electrical Engineering, Business Administration, or related field (Preferred) or a combination of education and experience that provides equivalent knowledge to a major in such fields is required" Certification: "NERC Certification as a Reliability Coordinator is preferred" Work Location: "WORK LOCATION: Taylor, TX hybrid 2 days per week." Pay: "Expected Salary Range $144,000 - $198,000" Schedule: maybe we treat hybrid as schedule? Could put under Schedule: hybrid 2 days per week. Or we could put under Work Location but spec only allows Schedule heading. We'll put Schedule: hybrid 2 days per week (Taylor, TX). Or we could include location in Schedule? The spec says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Schedule section for hybrid 2 days per week. Location maybe not needed but we can include location in Schedule or maybe we drop location? The instruction: preserve ALL substantive information. So we need to keep location Taylor, TX. We could put location in Schedule or maybe we create a separate section? Not allowed headings beyond those. Could embed location in Schedule paragraph: "Hybrid schedule: 2 days per week in Taylor, TX." That preserves both. Now Benefits: none, omit. Skills: none specific, omit. Qualifications: we can put Education and Certification under Qualifications. Now About the role: we need to include the initial paragraph about ERCOT environment and encouraging to join. Also maybe Job Summary? The Job Summary is a separate paragraph describing role leads validation etc. That could be part of About the role or Responsibilities? But we have Responsibilities separate. The About the role could be the introductory paragraph about ERCOT's environment and encouraging to join. We'll include that. Job Summary could be considered part of About the role? But we already have About the role; we could also include Job Summary under About the role as more detail. However we must not create filler. We'll combine the initial paragraph and Job Summary into About the role? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have About the role section containing the descriptive paragraphs about the role and environment. We'll include both the initial ERCOT paragraph and the Job Summary paragraph. Now we must not repeat job title as heading. No job title given explicitly; we won't add. Now produce HTML fragment:

  About the role

  At ERCOT, our diverse and dynamic work environment provides a platform on which employees can work together to build the future of the Texas power grid and wholesale market utilizing the latest technologies and resources. We encourage you to join our talented, dedicated workforce to develop world-class solutions for today and tomorrow’s energy challenges while learning new skills and growing your career. ERCOT is committed to fostering inclusion at all levels of our company. It is the cornerstone of our corporate values of accountability, leadership, innovation, trust, and expertise. We know that individuals with a wide variety of talents, ideas, and experiences propel the innovation that drives our success. An inclusive and diverse workforce strengthens us and allows for a collaborative environment to solve the challenges that face our industry today and in the future.

  This role leads validation, generation, and implementation of Network Operations Model changes and case building, ensuring the Network Model is accurate and ready for use across ERCOT's operations applications. The role helps drive innovative improvements to ERCOT's modeling systems, sets guidelines that ensure accurate System Operations cases, and resolves complex modeling and operations issues through analysis and reporting.

  Responsibilities

  • Responsible for hiring, coaching, training, and performance management of staff.
  • Frequently interacts with direct reports and functional peer groups; interaction normally requires the ability to gain cooperation of others.
  • Provides direct supervision to professional individual contributors and/or skilled, support individual contributors.
  • Acts as an advisor to department and may become actively involved, as required, to meet schedules and resolve problems.
  • A small portion of time is normally spent performing individual tasks related to the department.
  • Typically has full responsibility for direct reports.
  • May provide input to budgeting and financial decisions that impact the department.
  • Requests approval for financial actions beyond a limited scope per policy.
  • Responsible for the validation, generation and implementation of both Network Operations Model changes and case building.
  • Supports the development and activities associated with the Engineering Development Program (EDP).
  • Provides information and support as necessary to other ERCOT departments and to the various ERCOT stakeholder committees, working groups, and task forces.
  • Review and approve staff timesheets and leave requests.
  • On-the-job training, career guidance and mentoring employees.
  • Ensures training and evaluation of members of the Engineering Development Program (EDP) provides a competent coverage of the Network Modeling Process.
  • Develops and implements innovative solutions that promote the continued evolution and success of the existing ERCOT modeling systems.
  • Evaluates, recommends, and confirms the documentation of guidelines and operations procedures that ensure the accuracy of System Operations cases.
  • Ensures the resolution of complex problems related to System Operations and ERCOT modeling systems providing modeling analysis, reports, and investigation/review both written and oral.
  • Bears the accountability for the Network Model being ready for use in the various operations applications whenever changes or updates to the model are made.
  • Reviews contingencies, issues and recommendations that possibly affect or improve the modeling process.
  • Validates the database and Market testing of the Operational models and associated market information.
  • Verifies appropriate data to IT EMMS, IT MMS, System Planning, System Operations, and other ERCOT groups.
  • Leads and/or represents ERCOT in technical committees and subcommittees.