Senior Business Systems Analyst
for each section. Use - for lists. Use
for prose.
We must not repeat job title as heading. No Job ID/requisition numbers as headings; we can fold minor metadata into short
or drop it. The requisition ID can be placed in a short paragraph maybe under overview? But we can drop it as minor metadata. Probably better to include a short
with Requisition Id 17121? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short
with that info.
We need to preserve all substantive information. So we need to include overview description, duties, qualifications (basic and preferred), special requirements (clearance, WSAP, visa), benefits list. Also maybe "About ORNL" description.
We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should remove the equal opportunity employer lines, UT-Battelle E-Verify, etc. Also remove the instructions about accommodation email, file types, etc. Also remove the "This position will remain open..." etc. Also remove the "If you have difficulty using the online application system..." etc. Also remove the "ORNL offers competitive pay and benefits programs..." maybe keep benefits list but not the generic fluff? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the benefits list but can we keep the preceding sentence? It's somewhat generic but still part of benefits description. Might be okay. However we need to avoid boilerplate like "ORNL offers competitive pay and benefits programs to attract and retain individuals who demonstrate exceptional work behaviors." That's somewhat generic but still part of the posting. It's not explicitly listed as boilerplate; but it's not a list of benefits. Might be considered filler. Safer to keep only the list of benefits. The instruction: "Prefer a few substantive sections over many thin ones." So we can have sections: About the role (overview), Responsibilities, Requirements (maybe combine Basic and Preferred?), Qualifications (maybe separate?), Skills, Benefits. But we need to decide.
We have Basic Qualifications and Preferred Qualifications. Could combine into Requirements section? Or have Qualifications section with sublists? The instruction: use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate Requirements and Qualifications. Likely Requirements = basic qualifications, Qualifications = preferred qualifications? Or vice versa. Usually Requirements are mandatory, Qualifications are preferred. We'll follow that: Requirements = Basic Qualifications, Qualifications = Preferred Qualifications.
Skills: we could extract skills from duties? But we might not have explicit skills list; we could combine technical skills from duties into Skills section. However we need to avoid creating thin sections. If we don't have explicit skills list, maybe we omit Skills section. The instruction: include a section ONLY when the posting has real, specific content for it. So if we don't have a distinct skills list, we should not create Skills section. We could embed skills in Responsibilities or Requirements. So we will not include Skills.
Thus sections: About the role (overview), Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits.
We need to include overview paragraph(s). The overview includes: Requisition Id 17121 Overview The Enrichment Science and Engineering Division (ESED), within Oak Ridge National Laboratory’s Isotope Science and Engineering Directorate, is seeking a Senior Business Systems Analyst position in the Systems Administration Group under the Systems & Process Assurance (SPA) Section. ESED is one of four Divisions of the Isotope Science and Engineering Directorate (ISED) at Oak Ridge National Laboratory (ORNL). ESED serves the nation in two critical areas: advancing enrichment technologies and exploring enriched stable isotope production and applications. The division leverages an elite staff of scientists and engineers with the world-leading capabilities of Oak Ridge National Laboratory to deliver groundbreaking advancements with a variety of applications, from national security to life-saving medical treatments. The Business Systems Analyst position will support and enhance ESED’s Enterprise Resource Planning (ERP) environment. The successful candidate will provide analytical, technical, and development support for key business systems, focusing on ERP configuration and implementation, data integrations, reporting tools, and application development frameworks. This role partners closely with stakeholders across the division to ensure business systems are optimized, reliable, and aligned with organizational requirements.
We need to preserve all that. We'll put that in
maybe multiple paragraphs.
We also need to include the Requisition Id maybe as a short
before overview.
Now Responsibilities: list of duties from "Major Duties/Responsibilities". We'll convert each bullet into
- .
Requirements: Basic Qualifications list.
Qualifications: Preferred Qualifications list.
Benefits: list from "Other benefits include the following:" plus earlier list: medical and retirement plans, flexible work hours, on-site fitness, banking, cafeteria facilities, then list: Prescription Drug Plan, Dental Plan, Vision Plan, 401(k) Retirement Plan, Contributory Pension Plan, Life Insurance, Disability Benefits, Generous Vacation and Holidays, Parental Leave, Legal Insurance with Identity Theft Protection, Employee Assistance Plan, Flexible Spending Accounts, Health Savings Accounts, Wellness Programs, Educational Assistance, Relocation Assistance, Employee Discounts.
We should also include earlier mention: "ORNL offers competitive pay and benefits programs ... The laboratory provides a range of employee benefits, including medical and retirement plans and flexible work hours, to support the well-being of you and your family. Employee amenities such as on-site fitness, banking, and cafeteria facilities are also available for added convenience." That's substantive; we can include as a
before the list.
We must not include Pay or Schedule sections.
Now ensure we don't include boilerplate: remove EEO, equal opportunity, UT-Battelle E-Verify, accommodation email, file types, position open duration, etc. Also remove "ORNL is an equal opportunity employer..." etc. Also remove "If you have difficulty using the online application system..." etc. Also remove "This position will remain open for a minimum of 5 days..." etc. Also remove "We accept Word..." etc. Also remove "Resumes from third party vendors..." etc. Also remove "ORNL is an equal opportunity employer..." etc. Also remove "UT-Battelle is an E-Verify employer." Also remove "As a U.S. Department of Energy (DOE) Office of Science national laboratory, ORNL has an impressive 80-year legacy..." That's part of About ORNL; we might keep that as it's substantive about ORNL. However the instruction: "Prefer a few substantive sections over many thin ones." The About ORNL paragraph is somewhat generic but still part of the posting. Could be included in About the role or maybe as part of Benefits? It's about ORNL mission. Might be okay to keep in About the role section as background. But we already have overview; we could add a paragraph about ORNL mission. However the instruction says preserve ALL substantive information. So we should keep that paragraph. It's not boilerplate; it's describing ORNL. So we can include it in About the role section after the overview.
Thus About the role will contain: overview paragraph + ORNL mission paragraph.
Now we need to ensure we don't repeat the job title as heading. We'll not.
Now produce HTML fragment.
Let's craft:
About the role
Requisition Id 17121
The Enrichment Science and Engineering Division (ESED), within Oak Ridge National Laboratory’s Isotope Science and Engineering Directorate, is seeking a Senior Business Systems Analyst position in the Systems Administration Group under the Systems & Process Assurance (SPA) Section. ESED is one of four Divisions of the Isotope Science and Engineering Directorate (ISED) at Oak Ridge National Laboratory (ORNL). ESED serves the nation in two critical areas: advancing enrichment technologies and exploring enriched stable isotope production and applications. The division leverages an elite staff of scientists and engineers with the world-leading capabilities of Oak Ridge National Laboratory to deliver groundbreaking advancements with a variety of applications, from national security to life-saving medical treatments. The Business Systems Analyst position will support and enhance ESED’s Enterprise Resource Planning (ERP) environment. The successful candidate will provide analytical, technical, and development support for key business systems, focusing on ERP configuration and implementation, data integrations, reporting tools, and application development frameworks. This role partners closely with stakeholders across the division to ensure business systems are optimized, reliable, and aligned with organizational requirements.
As a U.S. Department of Energy (DOE) Office of Science national laboratory, ORNL has an impressive 80-year legacy of addressing the nation’s most pressing challenges. Our team is made up of over 7,000 dedicated and innovative individuals! Our goal is to create an environment where a variety of perspectives and backgrounds are valued, ensuring ORNL is known as a top choice for employment. These principles are essential for supporting our broader mission to drive scientific breakthroughs and translate them into solutions for energy, environmental, and security challenges facing the nation.
Then Responsibilities:
Responsibilities
- Provide analytical and technical support for the division’s business systems (ERP and custom solutions), including report development, system configuration, troubleshooting, and end‑user assistance.
- Translate organizational needs into system requirements, functional specifications, and technical solutions.
- Develop, optimize, and maintain SQL queries, stored procedures, and database integrations across Oracle or SQL-based platforms.
- Build and maintain dashboards, reports, and data models to support analytics and operational insights.
- Develop, maintain, and support Oracle APEX and other custom solutions, including applications, workflows, and dashboards.
- Utilize general programming or scripting skills to support automation, system enhancements, and integrations.
- Participate in and support Agile software development practices, including sprint planning, backlog refinement, iterative development, and documentation.
- Collaborate with cross-functional business units to evaluate processes, identify improvement opportunities, and deliver system enhancements.
- Support data governance, data quality, and ERP data architecture initiatives.
- Assist with ERP upgrades, system testing, documentation, and user training.
- Manage and support integration between ERP and other systems.
Requirements (Basic Qualifications):
Requirements
- BS Degree in IT, Computer Science, Engineering, Business, or related field and 8+ years of experience. An equivalent combination of education and experience may be considered.
- Hands-on experience with modern ERP systems, including implementation, configuration, and end-user support.
- Proven knowledge of engineering, manufacturing, supply chain, or business operations within an ERP environment (MRP, MPS, Planning, Scheduling, Inventory Management, BOM’s, Item Masters, etc.)
- Working knowledge of SQL, including writing queries in Oracle or SQL Server.
- Experience developing dashboards and reports using Power BI or comparable platforms.
- Demonstrated experience with general programming or scripting for automation or system customization.
- Experience developing applications or workflows using Oracle APEX or comparable platforms.
- Familiarity with Agile or iterative
for prose. We must not repeat job title as heading. No Job ID/requisition numbers as headings; we can fold minor metadata into short
or drop it. The requisition ID can be placed in a short paragraph maybe under overview? But we can drop it as minor metadata. Probably better to include a short
with Requisition Id 17121? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short
with that info. We need to preserve all substantive information. So we need to include overview description, duties, qualifications (basic and preferred), special requirements (clearance, WSAP, visa), benefits list. Also maybe "About ORNL" description. We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should remove the equal opportunity employer lines, UT-Battelle E-Verify, etc. Also remove the instructions about accommodation email, file types, etc. Also remove the "This position will remain open..." etc. Also remove the "If you have difficulty using the online application system..." etc. Also remove the "ORNL offers competitive pay and benefits programs..." maybe keep benefits list but not the generic fluff? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the benefits list but can we keep the preceding sentence? It's somewhat generic but still part of benefits description. Might be okay. However we need to avoid boilerplate like "ORNL offers competitive pay and benefits programs to attract and retain individuals who demonstrate exceptional work behaviors." That's somewhat generic but still part of the posting. It's not explicitly listed as boilerplate; but it's not a list of benefits. Might be considered filler. Safer to keep only the list of benefits. The instruction: "Prefer a few substantive sections over many thin ones." So we can have sections: About the role (overview), Responsibilities, Requirements (maybe combine Basic and Preferred?), Qualifications (maybe separate?), Skills, Benefits. But we need to decide. We have Basic Qualifications and Preferred Qualifications. Could combine into Requirements section? Or have Qualifications section with sublists? The instruction: use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate Requirements and Qualifications. Likely Requirements = basic qualifications, Qualifications = preferred qualifications? Or vice versa. Usually Requirements are mandatory, Qualifications are preferred. We'll follow that: Requirements = Basic Qualifications, Qualifications = Preferred Qualifications. Skills: we could extract skills from duties? But we might not have explicit skills list; we could combine technical skills from duties into Skills section. However we need to avoid creating thin sections. If we don't have explicit skills list, maybe we omit Skills section. The instruction: include a section ONLY when the posting has real, specific content for it. So if we don't have a distinct skills list, we should not create Skills section. We could embed skills in Responsibilities or Requirements. So we will not include Skills. Thus sections: About the role (overview), Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits. We need to include overview paragraph(s). The overview includes: Requisition Id 17121 Overview The Enrichment Science and Engineering Division (ESED), within Oak Ridge National Laboratory’s Isotope Science and Engineering Directorate, is seeking a Senior Business Systems Analyst position in the Systems Administration Group under the Systems & Process Assurance (SPA) Section. ESED is one of four Divisions of the Isotope Science and Engineering Directorate (ISED) at Oak Ridge National Laboratory (ORNL). ESED serves the nation in two critical areas: advancing enrichment technologies and exploring enriched stable isotope production and applications. The division leverages an elite staff of scientists and engineers with the world-leading capabilities of Oak Ridge National Laboratory to deliver groundbreaking advancements with a variety of applications, from national security to life-saving medical treatments. The Business Systems Analyst position will support and enhance ESED’s Enterprise Resource Planning (ERP) environment. The successful candidate will provide analytical, technical, and development support for key business systems, focusing on ERP configuration and implementation, data integrations, reporting tools, and application development frameworks. This role partners closely with stakeholders across the division to ensure business systems are optimized, reliable, and aligned with organizational requirements. We need to preserve all that. We'll put that in
maybe multiple paragraphs. We also need to include the Requisition Id maybe as a short
before overview. Now Responsibilities: list of duties from "Major Duties/Responsibilities". We'll convert each bullet into
before the list. We must not include Pay or Schedule sections. Now ensure we don't include boilerplate: remove EEO, equal opportunity, UT-Battelle E-Verify, accommodation email, file types, position open duration, etc. Also remove "ORNL is an equal opportunity employer..." etc. Also remove "If you have difficulty using the online application system..." etc. Also remove "This position will remain open for a minimum of 5 days..." etc. Also remove "We accept Word..." etc. Also remove "Resumes from third party vendors..." etc. Also remove "ORNL is an equal opportunity employer..." etc. Also remove "UT-Battelle is an E-Verify employer." Also remove "As a U.S. Department of Energy (DOE) Office of Science national laboratory, ORNL has an impressive 80-year legacy..." That's part of About ORNL; we might keep that as it's substantive about ORNL. However the instruction: "Prefer a few substantive sections over many thin ones." The About ORNL paragraph is somewhat generic but still part of the posting. Could be included in About the role or maybe as part of Benefits? It's about ORNL mission. Might be okay to keep in About the role section as background. But we already have overview; we could add a paragraph about ORNL mission. However the instruction says preserve ALL substantive information. So we should keep that paragraph. It's not boilerplate; it's describing ORNL. So we can include it in About the role section after the overview. Thus About the role will contain: overview paragraph + ORNL mission paragraph. Now we need to ensure we don't repeat the job title as heading. We'll not. Now produce HTML fragment. Let's craft:
About the role
Requisition Id 17121
The Enrichment Science and Engineering Division (ESED), within Oak Ridge National Laboratory’s Isotope Science and Engineering Directorate, is seeking a Senior Business Systems Analyst position in the Systems Administration Group under the Systems & Process Assurance (SPA) Section. ESED is one of four Divisions of the Isotope Science and Engineering Directorate (ISED) at Oak Ridge National Laboratory (ORNL). ESED serves the nation in two critical areas: advancing enrichment technologies and exploring enriched stable isotope production and applications. The division leverages an elite staff of scientists and engineers with the world-leading capabilities of Oak Ridge National Laboratory to deliver groundbreaking advancements with a variety of applications, from national security to life-saving medical treatments. The Business Systems Analyst position will support and enhance ESED’s Enterprise Resource Planning (ERP) environment. The successful candidate will provide analytical, technical, and development support for key business systems, focusing on ERP configuration and implementation, data integrations, reporting tools, and application development frameworks. This role partners closely with stakeholders across the division to ensure business systems are optimized, reliable, and aligned with organizational requirements.
As a U.S. Department of Energy (DOE) Office of Science national laboratory, ORNL has an impressive 80-year legacy of addressing the nation’s most pressing challenges. Our team is made up of over 7,000 dedicated and innovative individuals! Our goal is to create an environment where a variety of perspectives and backgrounds are valued, ensuring ORNL is known as a top choice for employment. These principles are essential for supporting our broader mission to drive scientific breakthroughs and translate them into solutions for energy, environmental, and security challenges facing the nation.
Then Responsibilities:Responsibilities
- Provide analytical and technical support for the division’s business systems (ERP and custom solutions), including report development, system configuration, troubleshooting, and end‑user assistance.
- Translate organizational needs into system requirements, functional specifications, and technical solutions.
- Develop, optimize, and maintain SQL queries, stored procedures, and database integrations across Oracle or SQL-based platforms.
- Build and maintain dashboards, reports, and data models to support analytics and operational insights.
- Develop, maintain, and support Oracle APEX and other custom solutions, including applications, workflows, and dashboards.
- Utilize general programming or scripting skills to support automation, system enhancements, and integrations.
- Participate in and support Agile software development practices, including sprint planning, backlog refinement, iterative development, and documentation.
- Collaborate with cross-functional business units to evaluate processes, identify improvement opportunities, and deliver system enhancements.
- Support data governance, data quality, and ERP data architecture initiatives.
- Assist with ERP upgrades, system testing, documentation, and user training.
- Manage and support integration between ERP and other systems.
Requirements
- BS Degree in IT, Computer Science, Engineering, Business, or related field and 8+ years of experience. An equivalent combination of education and experience may be considered.
- Hands-on experience with modern ERP systems, including implementation, configuration, and end-user support.
- Proven knowledge of engineering, manufacturing, supply chain, or business operations within an ERP environment (MRP, MPS, Planning, Scheduling, Inventory Management, BOM’s, Item Masters, etc.)
- Working knowledge of SQL, including writing queries in Oracle or SQL Server.
- Experience developing dashboards and reports using Power BI or comparable platforms.
- Demonstrated experience with general programming or scripting for automation or system customization.
- Experience developing applications or workflows using Oracle APEX or comparable platforms.
- Familiarity with Agile or iterative