ERP System Administrator

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. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate. We need to parse the posting. Key info: - FLSA STATUS: Exempt (maybe not needed) - DEPARTMENT: ERP Team - SUPERVISOR: LaDonna Roberts - DIRECT REPORTS: None But these are minor metadata; we can fold into a short

or drop. Probably include a short paragraph with that info. - Position Summary: paragraph about Trexon, role description. - Minimum Qualifications: includes Education, Experience, Knowledge, etc. - Job Responsibilities: bullet list under headings: User & Security Administration, Support & Break/Fix, Enhancement & Solution Deployment, Ticketing & Project Management, Environment & Server Administration, Documentation & Training, Other Responsibilities..., Internal and External Relationships. - Physical Requirements: maybe not needed as it's boilerplate? It's not boilerplate but it's generic; but we might include if it's substantive? It says physical demands etc. Might be considered boilerplate; but we can drop as it's not specific to role? It's generic but still part of posting. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Physical Requirements is not exactly that but could be considered boilerplate. Safer to drop? The instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Physical Requirements is not listed, but it's often generic. However we can keep if we think it's substantive. But we have to avoid filler like "commensurate with experience". Physical Requirements includes specifics: sit for extended periods, low noise. That's specific enough. Might keep as a section? There's no heading for Physical Requirements in allowed headings list; we could fold into Responsibilities or maybe a separate section 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 only use those headings. So we cannot create a Physical Requirements heading. So we need to incorporate that info elsewhere, maybe under Responsibilities as a bullet? Or we could drop it if not fitting. Probably drop as not fitting headings. - Salary Transparency: $100,000 - $105,000 USD. That's Pay section. - Benefits: Not mentioned explicitly. So we should not create Benefits section unless posting states them. It doesn't mention benefits. So omit Benefits. - Schedule: Not mentioned. Omit. - About the role: we can use Position Summary as About the role. - Responsibilities: we have Job Responsibilities. - Requirements: maybe Minimum Qualifications? Could be Requirements. But we also have Qualifications separate? The instruction lists both Requirements and Qualifications as possible headings. We need to decide what to put where. Typically Requirements = mandatory qualifications; Qualifications = preferred? But we have Minimum Qualifications (education, experience) and also Knowledge, Skills etc. We could treat Requirements as the mandatory items (education, experience, ITAR, etc.) and Qualifications as preferred? However the posting lumps many as required. Let's parse: Minimum Qualifications section includes: Education: Associate’s degree ... or combination. Must be a U.S. Person as defined under ITAR. Experience: 4+ years hands-on Epicor ERP administration experience (E10/Kinetic strongly preferred) required. Experience in managing data loads for new Epicor implementations required. Data Management Tool (DMT). Experience with pipeline orchestration such as Apache Airflow (or similar) is a plus. Experience with user security, menu maintenance, and multi-company administration required. Experience in a manufacturing/engineer-to-order or configure-to-order environment required. Familiarity with hosted or managed Epicor environments in GCCH is preferred. Proficiency reading, troubleshooting, and deploying BAQs, UBAQs, BPMs, dashboards, Application Studio customizations, SSRS reports, DMT solutions, and Power BI (hands-on development a strong plus) required. Project management experience with ERP module implementations preferred. Working understanding of ITAR and CMMC 2.0 compliance in an ERP context required. Knowledge: Working knowledge of BAQs — with the ability to read, troubleshoot, and deploy is required. Familiarity with Epicor customizations and Application Studio is required. Skills: Strong SQL and REST API integration skills; scripting and automation (Python, PowerShell), Git-based version control, and ERP automation are a plus. Strong troubleshooting, end-user support, and written and verbal communication skills are required. Ability to multi-task in a fast-paced environment while being a self-starter who begins tasks and works effectively on their own initiative to complete them is required. Familiarity with the PDCA Cycle (Plan, Do, Check, Act) is preferred. Thus many items are required, some preferred. We could create a Requirements section for the required items, and a Qualifications section for preferred/pluses. But the instruction says "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one section? But they gave both as possible headings; we need to decide. We could output:

About the role

...

Responsibilities

...

Requirements

...

Skills

...

Pay

$100,000 - $105,000 USD

We could omit Qualifications if we put preferred items under Skills or Requirements with note (preferred). But better to separate: Requirements = mandatory; Qualifications = preferred/pluses. However we have many preferred items scattered; we could put them under Qualifications. Let's extract mandatory requirements: - Associate’s degree in Information Systems, Computer Science, or related technical field, or a combination of education and hands-on ERP/BI administration experience (3+ years). (Actually says 3+ years? It says "or a combination of education and hands-on ERP/BI administration experience (3+ years)". So that's a requirement. - Must be a U.S. Person as defined under ITAR (22 CFR 120.62). - 4+ years of hands-on Epicor ERP administration experience (E10/Kinetic strongly preferred) is required. - Experience in managing data loads for new Epicor implementations is required. Data Management Tool (DMT). - Experience with user security, menu maintenance, and multi-company administration is required. - Experience in a manufacturing/engineer-to-order or configure-to-order environment is required. - Proficiency reading, troubleshooting, and deploying BAQs, UBAQs, BPMs, dashboards, Application Studio customizations, SSRS reports, DMT solutions, and Power BI (hands-on development a strong plus) is required. (Note: Power BI hands-on development is a plus, but proficiency reading etc is required.) - Working understanding of ITAR and CMMC 2.0 compliance in an ERP context is required. - Working knowledge of BAQs — with the ability to read, troubleshoot, and deploy is required. - Familiarity with Epicor customizations and Application Studio is required. - Strong troubleshooting, end-user support, and written and verbal communication skills are required. - Ability to multi-task in a fast-paced environment while being a self-starter who begins tasks and works effectively on their own initiative to complete them is required. Preferred/pluses: - Experience with pipeline orchestration such as Apache Airflow (or similar) is a plus. - Familiarity with hosted or managed Epicor environments in GCCH is preferred. - Project management experience with ERP module implementations is preferred. - Proficiency ... Power BI (hands-on development a strong plus) is a plus (but we already listed proficiency required; hands-on development is plus). - Strong SQL and REST API integration skills; scripting and automation (Python, PowerShell), Git-based version control, and ERP automation are a plus. - Familiarity with the PDCA Cycle (Plan, Do, Check, Act) is preferred. We could also include Knowledge section? But we already covered knowledge in requirements. Thus we can have: Requirements (mandatory) as ul. Qualifications (preferred) as ul. Skills maybe separate? But skills overlap with required and plus. Could combine skills into Requirements/Qualifications. However the instruction gave Skills as a possible heading; we could put the technical skills (SQL, REST API, scripting, etc.) there. But we already have many skill-like items in requirements. To avoid thin sections, maybe we combine Requirements and Qualifications into one section called Requirements, and include both mandatory and preferred with notes. But then we lose Skills heading. Better to follow the instruction: Use headings only when posting has real specific content for it. We have content for About the role, Responsibilities, Requirements, Skills, Pay. We could also have Qualifications if we want to separate preferred. But we have content for both. Let's decide: - About the role: Position Summary. - Responsibilities: list of responsibilities. - Requirements: mandatory qualifications (education, experience, certifications, etc.) - Skills: technical skills (SQL, REST API, scripting, troubleshooting, communication, multi-task, etc.) plus maybe some preferred. - Pay: salary range. We could omit Qualifications section to avoid thin. Now we need to ensure we don't repeat job title. Not needed. We need to output only HTML fragment. Let's craft. First, About the role paragraph: combine the Position Summary text. Position Summary: "Trexon, an Amphenol company (NYSE: APH), is a designer and manufacturer of highly engineered, mission-critical interconnect solutions - including cable assemblies, connectors, and other components - serving customers across the defense, aerospace, space, and specialty markets. Operating several business units across manufacturing sites throughout the U.S., Trexon generates ~ $200M in annual revenue with ~ 900 employees and continues to scale as part of Amphenol Corporation, a global leader in interconnect and sensor solutions. Join an established, well-resourced ERP team and work alongside a dedicated application development function rather than as a lone administrator. You'll keep a business-critical Epicor platform healthy across multiple company instances that run manufacturing, finance, and quality for the entire organization — work that is directly visible to operations and leadership. It's a real opportunity to own a core system and grow into broader ERP and business-systems responsibility over time." We'll put that in

. Now Responsibilities: we have bullet points under headings: User & Security Administration, Support & Break/Fix, Enhancement & Solution Deployment, Ticketing & Project Management, Environment & Server Administration, Documentation & Training, Other Responsibilities..., Internal and External Relationships. We need to turn each into

items. Could keep the subheadings as part of the li text? Probably just list each responsibility as a li, maybe preserving the subheading as bold? But we cannot add extra tags beyond

• and

  . We can include the subheading text inside the li. Thus:

  • User & Security Administration: Provision, modify, and deactivate user accounts across all company instances; perform menu maintenance and maintain menu structure across companies; administer security groups, field/method-level security, and role-based permissions; manage user licenses and access assignments.
  • Support & Break/Fix: Serve as the first point of contact for end-user issues; triage, troubleshoot, and resolve day-to-day problems; proven ability to troubleshoot Epicor issues, perform root cause analysis, and deliver scalable solutions that improve operational efficiency; escalate complex development issues to the application development team.
  • Enhancement & Solution Deployment: Deploy customizations, BPMs, BAQs