Jobs · Engineering · Oregon

SCADA Engineer - Lead Professional

WSP in the U.S. · Portland, OR · 4 wk ago
Engineering$102k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the job description. First paragraph: "This Opportunity WSP is currently initiating a search for an experienced SCADA Engineer – Lead Professional for our Boise, ID office. Candidates for our offices in Clarkston, WA; Portland, OR; San Diego, CA; Denver, CO; Salt Lake City, UT; and Ft. Lauderdale, FL will also be considered. Be involved in projects with our Electrical Studies, SCADA, and Protection (ESSP) team and be part of a growing organization that meets our clients' objectives and solves their challenges. WSP brings global expertise in power delivery, power generation, and program management, anchored by the acquisition of POWER Engineers, Inc. TRC Companies have now joined WSP, deepening our power practice and expanding our energy advisory and intelligent grid services. We are partnering with clients to shape how energy systems evolve around the world, and we need your help." That's about the role/overview. Could be "About the role". We'll put that in

About the role

with

containing that text. Next: "Provides technical leadership and subject matter expertise for the design, engineering, and commissioning of utility and commercial power projects. Responsibilities include the development and commissioning of transmission and distribution substations, power distribution and regulation systems, renewable energy facilities, and protection and control systems. Guides project teams, resolves complex technical challenges, and ensures designs meet industry standards for quality, safety, and functionality." That's responsibilities. We'll put

Responsibilities

with
  • items. List items: - Provide technical leadership and subject matter expertise for the design, engineering, and commissioning of utility and commercial power projects. - Develop and commission transmission and distribution substations, power distribution and regulation systems, renewable energy facilities, and protection and control systems. - Guide project teams, resolve complex technical challenges, and ensure designs meet industry standards for quality, safety, and functionality. We could also include "Your Impact" section? But we only include sections if real specific content. "Your Impact" is a heading but content is generic: "Candidates for this role will have familiarity, experience, or expertise with some of the items listed below. A willingness to learn in areas where you do not have experience and to teach others in areas where you do have experience is essential to being successful on our team." That's somewhat generic but still content. Could be considered "About the role" or maybe "Qualifications"? But we have separate sections for Requirements, Qualifications, Skills. The "Your Impact" seems like a mix of expectations. Might be better to treat as part of "Requirements" or "Skills". However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine "Your Impact" into "Requirements" or "Skills". But we need to preserve all substantive info. Let's extract the list of items under "Your Impact" that follow: Leadership, Data Acquisition, Networking, Communications, Working knowledge..., Applicable network and communication protocols..., Applicable Logic and Control Platforms..., Applicable Software..., Logic and Control Systems..., Exercise responsible and ethical decision-making..., Perform additional responsibilities as required by business needs. These are essentially responsibilities and required skills. Many are detailed tasks. Could be placed under "Responsibilities" as bullet points. But we already have responsibilities list. Could expand responsibilities with those items. However we must not invent or summarize away detail. We need to preserve all substantive info. So we should include those items as responsibilities or skills. Better approach: Have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Schedule not mentioned, so omit. Now we need to extract Requirements: "Bachelor’s Degree in Electrical Engineering (or equivalent experience). 7 to 10 years of relevant post-education experience as an electrical engineer providing design deliverables for capital projects in power generation, transmission, and distribution at a utility or commercial scale. Must be flexible to a variety of schedules to meet business needs and able to prioritize responsibilities and quickly adapt to change. Occasional travel may be required, depending on project-specific requirements. Proven track record of upholding workplace safety and ability to abide by WSP’s health, safety, drug/alcohol, and harassment policies." That's requirements. Qualifications: "Preferred Qualifications Engineer license. Master’s Degree in Engineering. Preference will be given to applicants with a proven history of completing similar projects in a consulting environment. Preference is also given to applicants with experience in mentoring others and in providing technical and commercial leadership in customer-focused engineering projects." That's qualifications (preferred). Could be under Qualifications. Skills: The list under "Your Impact" includes many specific technical skills: Leadership (coordinate, review and approve electrical infrastructure design plans...), Data Acquisition (prepare points lists..., assign and program data addressing..., develop HMI screens, travel to project sites...), Networking (design and configure network and communication paths for RTUs, Data Concentrators, IEDs, HMIs, etc.), Communications (specify and design communication networks including data security and availability; develop basic specifications for fiber optic, microwave, power line carrier, or radio communication paths; infrequent travel to project sites to troubleshoot and commission network and communication systems.), Working knowledge or awareness of applicable industry SCADA practices outlined in IEEE, IEC, ANSI, CIGRE, or NERC standards and regulations for design work. Applicable network and communication protocols: DNP, Modbus, and IEC 61850 specified protocols Experience with legacy SCADA protocols a plus. Applicable Logic and Control Platforms: SEL RTAC, NovaTech Orion, Eaton SMP. Applicable Software: Wonderware, AcSELerator RTAC, NovaTech NCD/Inkscape IEC 61850 System Configuration Tool experience a plus Familiarity with SCADA/EMS/ADMS software a plus. Logic and Control Systems: Develop, document, and implement logic and control schemes for remote and local operation of power system equipment, including Microgrid, Volt/VAR Control, Load Shedding, and other custom control applications. Develop programs on various platforms for implementation of these schemes and travel to project sites to test and commission control solutions. Exercise responsible and ethical decision-making regarding company funds, resources, and conduct, and adhere to WSP’s Code of Conduct and related policies and procedures. Perform additional responsibilities as required by business needs. These are skills and responsibilities. We could put them under Skills as bullet list. Benefits: "WSP Benefits WSP provides a comprehensive suite of benefits focused on providing health and financial stability throughout the employee’s career. These benefits include coverage related to medical, dental, vision, disability, and life; retirement savings; paid sick leave; paid vacation (or other personal time); paid parental leave; and paid time off for purposes of bereavement, voting, and/or attendance at naturalization proceedings." Pay: Compensation Expected Salary (all locations): $102,200yr - $195,800yr ... plus Colorado specific. We need to include Pay section with that info. Should we include both ranges? Probably include both: general range and Colorado-specific. We'll put in

    . Schedule: Not mentioned, so omit. Now we need to ensure we don't include boilerplate like "Disclaimer Relocation assistance is not available for this position." That's not a section heading but it's substantive? It's a detail about relocation assistance not available. Should we preserve? It's substantive info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that detail. Where to put? Could be under About the role or maybe a separate note. Since we have no specific section for relocation, we could include it in About the role paragraph. But we must not repeat job title. It's okay. Also we need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The text includes "Disclaimer Relocation assistance is not available for this position." That's not boilerplate; it's a specific disclaimer about relocation. Keep. Also there is a repeated "Expected Salary (all locations):" and "Expected Salary (Colorado only):" we need to keep both. Now produce HTML. Structure:

    About the role

    ... (including overview and relocation disclaimer)

    Responsibilities

    • ...
    • ...
    But we might merge responsibilities and skills? However we have separate sections for Skills. Let's decide: We'll keep Responsibilities as the high-level duties (provide technical leadership, develop/commission, guide teams). Then Skills as the detailed technical competencies list. Requirements: as above. Qualifications: as above (preferred). Benefits: as above. Pay: as above. Now we need to ensure we don't repeat content. Let's extract each piece. About the role paragraph: Combine first paragraph plus maybe "Your Impact" intro? Actually "Your Impact" heading is not a section we will use; its content is the list of skills. We'll move that to Skills. Thus About the role: "This Opportunity WSP is currently initiating a search for an experienced SCADA Engineer – Lead Professional for our Boise, ID office. Candidates for our offices in Clarkston, WA; Portland, OR; San Diego, CA; Denver, CO; Salt Lake City, UT; and Ft. Lauderdale, FL will also be considered. Be involved in projects with our Electrical Studies, SCADA, and Protection (ESSP) team and be part of a growing organization that meets our clients' objectives and solves their challenges. WSP brings global expertise in power delivery, power generation, and program management, anchored by the acquisition of POWER Engineers, Inc. TRC Companies have now joined WSP, deepening our power practice and expanding our energy advisory and intelligent grid services. We are partnering with clients to shape how energy systems evolve around the world, and we need your help. Provides technical leadership and subject matter expertise for the design, engineering, and commissioning of utility and commercial power projects. Responsibilities include the development and commissioning of transmission and distribution substations, power distribution and regulation systems, renewable energy facilities, and protection and control systems. Guides project teams, resolves complex technical challenges, and ensures designs meet industry standards for quality, safety, and functionality." But note that the last three sentences are actually responsibilities; we might want to move them to Responsibilities section to avoid duplication. However the instruction says preserve all substantive info; we can keep them in About the role but then also in Responsibilities would be duplication. Better to keep them only in Responsibilities. So About the role should stop before "Provides technical leadership..." Actually that sentence is more of a summary of the role. Could be considered part of About the role. But we also have Responsibilities section that will list detailed responsibilities. To avoid duplication, we could keep the summary in About the role and then list detailed responsibilities in Responsibilities. That's fine; not exact duplication but overlapping. However the sentence "Provides technical leadership and subject matter expertise for the design, engineering, and commissioning of utility and commercial power projects." is a responsibility. If we also list it in Responsibilities, it's duplicate. We could keep it only in Responsibilities and not in About the role. Let's decide: About the role will be the introductory paragraph up to "We are partnering with clients to shape how energy systems evolve around the world, and we need your help." Then Responsibilities will start with "Provides technical leadership and subject matter expertise..." etc. Thus About the role paragraph: "This Opportunity WSP is currently initiating a search for an experienced SCADA Engineer – Lead Professional for our Boise, ID office. Candidates for our offices in Clarkston, WA; Portland, OR; San Diego, CA; Denver, CO; Salt Lake City, UT; and Ft

Similar jobs