AMI Solutions Lead

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate like EEO, accommodation, etc. Also remove navigation/legal/EEO etc. Also remove duplicated lines. Keep substantive info. We need to parse the posting. Content: - Intro: IEM is looking for a Full Time- AMI Solutions Lead to join our team. This role serves as a liaison between business stakeholders and technical teams to deliver effective, integrated solutions. This role gathers and analyzes requirements, supports process improvements, and leads the functional design and integration of Oracle CC&B, AMI, and Meter Reading systems. The position also ensures alignment with business needs, supports testing and issue resolution, and maintains compliance with LUMA IT standards. - Primary Location: Live anywhere that meets personal office / at home work requirements in the United States including Puerto Rico. Work will take place either in the field, in an office environment, or personal office / at home and will depend on the need of the project. - Travel Requirements: This position will require some work to be conducted at a client site. Travel and other expenses are reimbursable in accordance with Federal Travel Regulations or DoD regulations. - Essential Functions (list of duties): - Gather, analyze, and document business and functional requirements using interviews, workshops, surveys, and document analysis. - Collaborate with clients, stakeholders, and internal teams to clarify requirements and ensure alignment with technical solutions. - Support business process analysis and functional design development, including creating process flows, use cases, and diagrams. - Serve as a liaison between business stakeholders and technical teams, translating requirements into actionable specifications. - Lead and support requirements validation, testing activities, and defect resolution to ensure solutions meet business needs. - Maintain requirements traceability matrices and a centralized repository for functional and design deliverables. - Serve as a Subject Matter Expert (SME) for Oracle CC&B, AMI, Meter Reading systems, and related platforms. - Provide knowledge transfer to technical teams on functional requirements and design decisions. - Ensure all deliverables comply with LUMA IT standards, policies, and procedures. - Perform other duties as assigned, including function- or project-specific responsibilities outlined in supplemental documentation. - Minimum Qualifications: - Experience: Five (5) years or more of experience as Business Analyst or related experience. - Three (3) to Five (5) years in Electric Utility experience. - Degree: Bachelor’s degree in information technology, Computer Science, Business Analysis or a related field. - Experience and Degree Substitution: An equivalent combination of training and experience may substitute for a degree. - Experience with SDLC methods and tools including but not limited to requirements gathering, design documentation, workshop facilitation, defect tracking and testing support. - Understanding of the typical business critical utility processes and their relationship to key systems (CIS, GIS, OMS, etc.). - Experience with MS Word, MS Excel, PowerPoint, Visio. - Preferred Qualifications: - Experience with CC&B, Outage Management Systems, Meter Data Management Systems and Geographical Information Systems. - Bilingual: Proficiency in written and oral communication (Spanish and English). - Valid Driver’s License. - Additional Location and Travel Information: - Internet Requirements: All personal office / at home work environments require the ability to maintain minimum Internet speeds of 25 Mbps upload and 3 Mbps download, as well as a ping rate of 100 ms or less during working hours, regardless of the type and number of devices using your Internet connection. You must also have account privileges and access to your Internet service provider account during working hours for the purposes of maintaining the Internet connection, if needed. - Office Locations: Often, these offices are either owned by the client we work with or by IEM. All candidates are expected to follow any rules and regulations of the office in which they are required to work for that project. - Benefits And More: - 10 paid Holidays - Vacation Pay - Sick Pay - 401 (K) plan with matching - Company paid STD and LTD - EEO etc (remove) - Reasonable Accommodation (remove) We need to map to sections: About the role (intro), Responsibilities (essential functions), Requirements (maybe Minimum Qualifications?), Qualifications (maybe Preferred Qualifications?), Skills (maybe experience with tools?), Benefits (benefits), Pay (none), Schedule (none). We should only include sections with real content. Pay and Schedule not present, so omit. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We have content for About the role (intro paragraph). Responsibilities (essential functions). Requirements (minimum qualifications). Qualifications (preferred qualifications). Skills (maybe experience with SDLC, tools, etc.) Could combine some. But we must not create thin sections. Let's see if we can combine. We could have: - About the role: intro paragraph. - Responsibilities: list of essential functions. - Requirements: Minimum Qualifications (experience, degree, etc.) - Qualifications: Preferred Qualifications (CC&B experience, bilingual, driver's license) - Skills: maybe experience with SDLC methods, tools, understanding of utility processes, MS Office, Visio. Could be separate but maybe we can incorporate into Requirements or Qualifications. However we need to avoid thin sections. If we put Skills as a separate section with list of specific skills (SDLC, tools, utility processes, MS Office, Visio) that is substantive. - Benefits: list of benefits. We must not include Pay or Schedule. We must not include boilerplate like EEO, accommodation, etc. We must not repeat job title. We must not include Job ID. We must not include navigation/legal etc. We need to output only HTML fragment, no /. Use

for headings,

• for lists,

  for prose. We need to preserve all substantive information. Let's extract. About the role: "IEM is looking for a Full Time- AMI Solutions Lead to join our team. This role serves as a liaison between business stakeholders and technical teams to deliver effective, integrated solutions. This role gathers and analyzes requirements, supports process improvements, and leads the functional design and integration of Oracle CC&B, AMI, and Meter Reading systems. The position also ensures alignment with business needs, supports testing and issue resolution, and maintains compliance with LUMA IT standards." We could keep as a paragraph. Responsibilities: list each essential function. Requirements (Minimum Qualifications): list each bullet. Qualifications (Preferred Qualifications): list each bullet. Skills: maybe list: Experience with SDLC methods and tools (requirements gathering, design documentation, workshop facilitation, defect tracking, testing support); Understanding of typical business critical utility processes and their relationship to key systems (CIS, GIS, OMS, etc.); Experience with MS Word, MS Excel, PowerPoint, Visio. Benefits: list: 10 paid Holidays, Vacation Pay, Sick Pay, 401(K) plan with matching, Company paid STD and LTD. We also have location and travel info: Primary Location, Travel Requirements, Internet Requirements, Office Locations. Should we include those? They are substantive. Where to put? Could be part of About the role or a separate section like "Location & Travel". But headings list only includes specific headings; we could add a section like "Location and Travel" but not in the prescribed list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should fit location/travel info into existing sections, maybe About the role or Responsibilities. Could add a paragraph under About the role covering location and travel. Or we could create a "Location and Travel" section but that might deviate. Safer to incorporate into About the role or Responsibilities. We have Primary Location, Travel Requirements, Internet Requirements, Office Locations. That's substantive. We can add a paragraph after the intro about location and travel. Thus About the role section could have multiple paragraphs: intro, location/travel details. We must not include boilerplate like "Equal Employment Opportunity" etc. Now craft HTML. Structure:

  About the role

  IEM is looking for a Full Time- AMI Solutions Lead to join our team. This role serves as a liaison between business stakeholders and technical teams to deliver effective, integrated solutions. This role gathers and analyzes requirements, supports process improvements, and leads the functional design and integration of Oracle CC&B, AMI, and Meter Reading systems. The position also ensures alignment with business needs, supports testing and issue resolution, and maintains compliance with LUMA IT standards.

  Primary Location: Live anywhere that meets personal office / at home work requirements in the United States including Puerto Rico. Work will take place either in the field, in an office environment, or personal office / at home and will depend on the need of the project. Travel Requirements: This position will require some work to be conducted at a client site. Travel and other expenses are reimbursable in accordance with Federal Travel Regulations or DoD regulations. Internet Requirements: All personal office / at home work environments require the ability to maintain minimum Internet speeds of 25 Mbps upload and 3 Mbps download, as well as a ping rate of 100 ms or less during working hours, regardless of the type and number of devices using your Internet connection. You must also have account privileges and access to your Internet service provider account during working hours for the purposes of maintaining the Internet connection, if needed. Office Locations: Often, these offices are either owned by the client we work with or by IEM. All candidates are expected to follow any rules and regulations of the office in which they are required to work for that project.

  Then Responsibilities:

  Responsibilities

  • Gather, analyze, and document business and functional requirements using interviews, workshops, surveys, and document analysis.
  • Collaborate with clients, stakeholders, and internal teams to clarify requirements and ensure alignment with technical solutions.
  • Support business process analysis and functional design development, including creating process flows, use cases, and diagrams.
  • Serve as a liaison between business stakeholders and technical teams, translating requirements into actionable specifications.
  • Lead and support requirements validation, testing activities, and defect resolution to ensure solutions meet business needs.
  • Maintain requirements traceability matrices and a centralized repository for functional and design deliverables.
  • Serve as a Subject Matter Expert (SME) for Oracle CC&B, AMI, Meter Reading systems, and related platforms.
  • Provide knowledge transfer to technical teams on functional requirements and design decisions.
  • Ensure all deliverables comply with LUMA IT standards, policies, and procedures.
  • Perform other duties as assigned, including function- or project-specific responsibilities outlined in supplemental documentation.
  Then Requirements (Minimum Qualifications):

  Requirements

  • Five (5) years or more of experience as Business Analyst or related experience.
  • Three (3) to Five (5) years in Electric Utility experience.
  • Bachelor’s degree in information technology, Computer Science, Business Analysis or a related field.
  • An equivalent combination of training and experience may substitute for a degree.
  • Experience with SDLC methods and tools including but not limited to requirements gathering, design documentation, workshop facilitation, defect tracking and testing support.
  • Understanding of the typical business critical utility processes and their relationship to key systems (CIS, GIS, OMS, etc.).