AMI Solutions Architect

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract content from posting. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove application instructions (none present). Keep substantive info. We need sections: About the role (maybe summary), Responsibilities (essential functions), Requirements (minimum qualifications?), Qualifications (preferred qualifications?), Skills (maybe technical skills), Benefits (benefits listed), Pay (none), Schedule (none). Since Pay and Schedule not specified, we should NOT include those sections. We need to preserve all substantive info, not invent. Let's parse. Posting: "IEM is looking for a Full Time – Solutions Architect to join our Critical Infrastructure team. The Solutions Architect will work closely with IT Leadership and other business units to align technology with business requirements. This position will support the AMI Project and play a key role in the AMI solution(s) requirements as part of the overall project. This position will collaborate with the IT department in supporting a variety of solutions to ensure coordination with the AMI project, design and integrate application systems, review existing systems to identify areas for improvement and monitor the outcome of new or upgraded systems on business operations. Additionally, this position will mentor Client`s Solutions Architects on utility industry and utility-systems knowledge, and transfer expertise in areas such as Meter-to-Cash, OMS, CIS, MDM, GIS, and regulatory frameworks like NERC CIP. 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 Once hired you will travel across the United States - Mainland or Puerto Rico to client sites as needed.Daily travel and other expenses are reimbursable in accordance with Federal Travel Regulations or DoD Regulations." Then "Essential Functions" list bullet points (actually sentences). Then "Minimum Qualifications" list. Then "Preferred Qualifications". Then "Additional Information" includes personal office requirements, office locations. Then "Benefits And More" list: 10 paid Holidays, Vacation Pay, Sick Pay, 401 (K) plan with matching, Company paid STD and LTD. Then EEO etc. We need to remove boilerplate: EEO, Reasonable Accommodation, etc. We need to keep travel requirements? It's substantive. Could be part of About the role or Responsibilities. Probably include in About the role. We need to keep location info: 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... That's location/travel. We need to keep "Benefits And More". We need to keep "Minimum Qualifications" and "Preferred Qualifications". Could map to Requirements and Qualifications sections. We need to keep "Skills": maybe list of technical skills from Minimum Qualifications (Java EE, IBM MQ, etc.) and Preferred Qualifications (GIS, etc.) Could be separate Skills section. But we must not create thin sections. We need to decide which sections to include. We have substantive content for: - About the role: description of role, collaboration, AMI project, mentoring, location, travel. - Responsibilities: Essential Functions list (many bullet points). Could be separate. - Requirements: Minimum Qualifications (degree, experience, specific tech experience). - Qualifications: Preferred Qualifications (additional experience, Spanish, etc.) - Skills: Could combine technical skills from both; but maybe we can incorporate into Requirements/Qualifications. However the instruction says use sections for Skills if there is real specific content. We have list of specific technologies; could be a Skills section. - Benefits: Benefits And More. Pay and Schedule: not present, so omit. We must not create sections with filler like "commensurate with experience". Not needed. We need to output only HTML fragment, using

for headings,

• for lists,

  for prose. We need to preserve all substantive info; do not invent or summarize away detail. Thus we need to copy the text exactly (or close) but formatted. We must not repeat job title as heading. Let's craft. First, About the role: combine the introductory paragraph(s) plus location/travel. Paragraph: "IEM is looking for a Full Time – Solutions Architect to join our Critical Infrastructure team. The Solutions Architect will work closely with IT Leadership and other business units to align technology with business requirements. This position will support the AMI Project and play a key role in the AMI solution(s) requirements as part of the overall project. This position will collaborate with the IT department in supporting a variety of solutions to ensure coordination with the AMI project, design and integrate application systems, review existing systems to identify areas for improvement and monitor the outcome of new or upgraded systems on business operations. Additionally, this position will mentor Client`s Solutions Architects on utility industry and utility-systems knowledge, and transfer expertise in areas such as Meter-to-Cash, OMS, CIS, MDM, GIS, and regulatory frameworks like NERC CIP." Then location/travel: "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: Once hired you will travel across the United States - Mainland or Puerto Rico to client sites as needed. Daily travel and other expenses are reimbursable in accordance with Federal Travel Regulations or DoD Regulations." We could combine into one

  or multiple

  . Use

  for prose. Now Responsibilities: list of Essential Functions. They are sentences starting with "Establishes integration standards..." etc. We'll put each as

• . We need to preserve all details exactly as given. Let's copy them: - Establishes integration standards and technology platforms, ensuring efficiency and adherence to best practices for utility Meter-to-Cash processes. - Leads data strategies for the Client IT/OT organization, including but not limited to data lakes, data warehouses, Databricks, Azure frameworks, and data retention. - Implements utility-specific requirements and designs into production through standard industry practices. - Serves as a subject matter expert for the utility IT/OT application landscape in coordination with leadership. - Mentors internal Solutions Architects on utility industry operations and utility‑system frameworks, providing knowledge transfer across Meter-to-Cash processes, OMS, CIS, MDM, GIS, and regulatory requirements such as NERC CIP. - Maintains compliance of all technical architecture with Client IT standards and policies. - Supports the design, development, testing, and deployment of AMI systems and integrations to ensure alignment with Client architecture standards and requirements. - Supports the direction of Data Analytics platforms, tools, and associated technologies. - Recommend innovative design concepts and technologies. - Provide knowledge transfer to Client`s IT/OT resources on architectural best practices and decisions. - Reviews integration and solution implementation design documents. - Adheres to all organizational policies and procedures. - Executes other duties as assigned. Note: some start with capital verbs, some lower case "Recommend". We'll keep as is. Now Requirements (Minimum Qualifications): list: - Degree: Bachelor’s degree in Information Technology, Computer Science, or related area. - Experience: Five – Seven (5-7) years of IT Experience in a similar role. - Three – Five (3-5) years Electric Utility experience. - Experience with Java EE, IBM MQ, Relational Databases, Oracle SOA Suite 12.x (Orchestration, Mediation, BPEL), Azure DevOps, GitHub repositories, Azure Frameworks, Data Bricks, Data Lakes. - Experience with AMI technologies (ISM Band base Mesh Networks, Point to Multipoint licensed spectrum radio technologies, Private LTE) Utility application footprint and associated application landscape including AMI. - Hands-on experience with CC&B and Outage Management Systems (OMS). - Hands-on experience with AMI and Meter Data Management Systems (MDMS) solutions. - Mentor Client`s internal Solutions Architect on utility industry and utility-systems knowledge, and transfer utility industry and AMI/utility-systems knowledge (Meter-to-Cash, OMS, CIS, MDM, GIS, regulatory frameworks like NERC CIP). - Professional proficiency in English (verbal and written). We need to keep bullet points. Now Qualifications (Preferred Qualifications): - Extensive experience with IT infrastructure (Virtual Servers, VMware) and communications/connectivity infrastructure (VPN, APN, VLANs). - Strong knowledge of GIS technologies, including Hexagon (Octave) and ESRI. - Established success in leading or interfacing with Run Operations groups for operational systems. - Spanish language proficiency. Now Skills: Could be a separate section listing technical skills from both Minimum and Preferred. But we might duplicate. However we could create a Skills section that consolidates the specific technologies: Java EE, IBM MQ, Relational Databases, Oracle SOA Suite 12.x, Azure DevOps, GitHub, Azure Frameworks, Data Bricks, Data Lakes, AMI technologies (ISM Band base Mesh Networks, Point to Multipoint licensed spectrum radio technologies, Private LTE), CC&B, OMS, MDMS, GIS (Hexagon Octave, ESRI), IT infrastructure (Virtual Servers, VMware), VPN, APN, VLANs, etc. But we risk summarizing. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we create a Skills section that lists these items, we are not summarizing away detail if we list them exactly as they appear. However we might be extracting from Minimum and Preferred and listing them; that's okay as long as we don't lose any detail. But we need to ensure we don't omit any. Could be lengthy but okay. Alternatively we could avoid a separate Skills section and just have Requirements and Qualifications sections cover the skills. The instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine skills into Requirements and Qualifications, and not create a separate Skills section. That would reduce number of sections. We have About the role, Responsibilities, Requirements, Qualifications, Benefits. That's five sections. That's fine. We must not include Pay or Schedule. Now Benefits: list: - 10 paid Holidays - Vacation Pay - Sick Pay - 401 (K) plan with matching - Company paid STD and LTD We need to keep exactly as written. Now we need to strip boilerplate: EEO, Reasonable Accommodation, etc. Also remove "Additional Information" about personal office requirements? Actually that is substantive: personal office requirements (internet speed, etc.) and office locations. Should we keep? It's under "Additional Information". It's substantive. Should we include it somewhere? Could be part of About the role or a separate section like "Work Arrangements". But we only have predefined headings; we could put under About the role or maybe a separate section like "Work Arrangements" not in list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings only; we shouldn't create other headings. So we must fold that info into one of those sections. Where does it fit? Could be About the role (location/work arrangements) or Responsibilities (maybe not). Probably About the role includes location and work arrangements. So we can incorporate the personal office requirements and office locations into About the role paragraph. Thus About the role will include: primary location, work environment, travel requirements, personal office requirements (internet speed, etc.), office locations rules. Let's extract that text: "Additional Information Personal Office / At Home Locations: All personal office / at home work environments require the ability to maintain minimum Internet speeds of