Business Analyst
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include. The posting includes: About Us (company description), Job Description (position summary, responsibilities, etc.), What You'll Do (detailed duties), What You'll Need (requirements), Compensation, Benefits, plus some EEO etc which we should remove.
We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have About Us (company description) maybe not exactly "About the role". Could we use "About the role" for position summary? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. So we should map content to those headings.
We have:
- About the role: could include Position Summary and maybe On-site role location.
- Responsibilities: could be the "What You'll Do" sections (ERP Administration & Data Integrity, Reporting & Data Analytics, Business Process & Collaboration). Could also include some from Job Description.
- Requirements: "What You'll Need" required and preferred.
- Qualifications: maybe overlap with Requirements; but we could combine? They said prefer a few substantive sections over many thin ones. So maybe we just have About the role, Responsibilities, Requirements, Benefits, Pay. Qualifications and Skills maybe not needed separately if covered.
But we must not create sections with filler. So we need to ensure each heading has substantive content.
We have Pay: Compensation: $77,000 - 90,000 (DOE). That's specific, so we can include Pay section.
Benefits: described: medical, dental, vision, life insurance, disability insurance, 401K with employer match, PTO, paid holidays and a bonus program. That's substantive.
Schedule: Not mentioned explicitly; only "On-site role in Spokane, WA". No schedule details like full-time, hours. So we should not create Schedule section.
Qualifications: Could be separate from Requirements but we might combine into Requirements. Since they said prefer few sections, we can omit Qualifications.
Skills: Could be part of Requirements; we can omit.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
Now we need to format content.
About the role: include position summary, on-site location, maybe team description? The "About Us" is company description; maybe that belongs elsewhere but we could incorporate into About the role? The instruction says use headings e.g. About the role. So we can put company overview there? Might be okay. But we could also include "About Us" as a paragraph under About the role.
Let's extract substantive info:
About Us: Alliance Machine Systems International, LLC is a privately held company with over 35 years of history dedicated to providing corrugated box manufacturing machines and services to the changing industry. As the paperboard packaging industry's premier global supplier of productivity-enhancing process machinery and systems, we supply innovative designs, intelligent automation, and optimized workflow, coupled with highly responsive parts and service support. Our United States and Europe based engineering, manufacturing, sales and service operations provide a global support system covering the full product portfolio of Alliance, Serco, TEI, ASC, Pallmac, J&L and Tanabe machines. Barry-Wehmiller is a diversified global supplier of engineering consulting and manufacturing technology for the packaging, corrugating, sheeting and paper-converting industries. By blending people-centric leadership with disciplined operational strategies and purpose-driven growth, Barry-Wehmiller has become a $3 billion organization with nearly 12,000 team members united by a common belief: to use the power of business to build a better world.
That's company description. Could be placed under About the role.
Position Summary: The Business Systems Analyst supports the organization's Visual ERP environment and its data, reporting, and process infrastructure: supporting and training users, troubleshooting issues, and driving process improvement. This role emphasizes ERP administration and support today, with growth toward broader business analysis over time. This is a hands-on, detail-driven role. The person in this seat will spend most of their time in the data: running daily reconciliation checks, resolving anomalies in inventory, labor, and financial transactions, and helping departments and individuals understand how the ERP system functions and what the data is telling them. Deep SQL expertise is not required at hire — data fluency (understanding relationships, joins, and how transactional data flows through an ERP system) matters more, and query-writing skill will develop on the job, increasingly supported by AI-assisted tools. Our Team We empower organizational success through responsive ERP support, data analytics, and innovative solutions, striving to connect people and systems with empathy and integrity. Responsive — respond to requests promptly, with proactive communication throughout. Innovative — pursue creative, fit-for-purpose solutions and new tools. Empathy — listen first and understand the need behind every request. Integrity — ensure data is complete, accurate, and verified; hold to honest, transparent standards.
We can combine.
Responsibilities: list bullet points from "What You'll Do". Let's extract bullet-like sentences:
- Review a standing set of daily reconciliation queries across inventory, labor, and financial transactions, resolving anomalies before they compound.
- Investigate and address data issues (orphaned records, shipment discrepancies, transaction errors), using judgment on when to resolve directly vs. loop in the relevant department.
- Research and test ERP functionality to validate fixes, evaluate new features, and support process changes before rollout.
- Manage ERP user setup, access, and basic system administration, including user license management.
- Manage and oversee test databases, and coordinate with corporate teams (such as SQL DBAs), technical support, and service providers.
- Assist with configuration file updates and installing report software as needed.
- Provide both formal and informal training, for both individuals and groups, on Infor Visual ERP functionality, processes, and best practices.
- Support month-end close, including same-day resolution of time-sensitive costing anomalies and reconciliation items.
- Develop, maintain, and modernize reports across the team's toolset (Excel, SSRS, Gupta, Crystal Reports, Power BI, Synoptix).
- Write SQL Server queries to select, update, and insert records, using AI-assisted tools as needed.
- Provide data and information to corporate entities as needed.
- Collaborate with stakeholders across departments to define business processes requirements.
- Assist with existing process improvement projects, growing toward independent ownership over time.
- Support software implementation and upgrade efforts, including future assistance with data conversions and migrations.
- Create and maintain IT documentation, as well as process documentation for other departments.
- Serve as backup for other team members as needed, building toward full cross-coverage over time.
That's a lot; we can put as - .
Requirements: Required and Preferred.
Required:
- 1–5 years of experience supporting an ERP system (any industry — Visual ERP experience not required).
- Strong data fluency: comfort with relational database concepts, table relationships, and joins.
- Willingness to learn manufacturing operations and data (BOMs, work orders, routings, labor reporting); no prior experience required.
- Strong troubleshooting instincts, attention to detail, and comfort with a disciplined daily process.
- Ability to translate technical/data findings into plain-language explanations for non-technical stakeholders.
- Strong teamwork and collaboration skills; works closely, in-office, with other analysts daily.
- Sound judgment for prioritizing and multi-tasking across a substantial, ongoing project backlog.
Preferred:
- Experience with Infor Visual ERP specifically.
- Experience writing SQL queries (SQL Server) and/or working in SSMS.
- Experience with report-writing tools such as Power BI, SSRS, Power Query, Crystal Reports, or Gupta.
- Prior exposure to a manufacturing or product engineering environment.
We can list as
- for each.
Benefits: list bullet points.
- medical, dental, vision
- life insurance
- disability insurance
- 401K with employer match
- PTO
- paid holidays
- bonus program
We can combine.
Pay: $77,000 - 90,000 (DOE). We'll put in
.
Now ensure we don't include boilerplate like EEO, equal opportunity, M/F/D/V, E-Verify, pre-employment screening, etc. Remove.
Also remove duplicated lines like "At Barry-Wehmiller we recognize that people come with a wealth of experience..." That's EEO-ish; remove.
Also remove "Please let us know if you require reasonable accommodations during the interview process." That's application instruction; remove.
Also remove "Company: Alliance" maybe minor metadata; we can drop.
Now produce HTML fragment.
Structure:
About the role
... (company description + position summary + team values)
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Pay
$77,000 - 90,000 (DOE)
Make sure no extra whitespace? It's fine.
Now craft the About the role paragraph.
We need to include company description and position summary and team values.
Let's write concise but preserve all substantive info. Not to invent or summarize away detail. We need to preserve all substantive information; but we can combine sentences as long as we don't lose info. It's okay to rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Summarizing may be okay if we keep all details? Safer to keep original sentences but we can combine.
We'll include:
- Alliance Machine Systems International, LLC is a privately held company with over 35 years of history dedicated to providing corrugated box manufacturing machines and services to the changing industry. As the paperboard packaging industry's premier global supplier of productivity-enhancing process machinery and systems, we supply innovative designs, intelligent automation, and optimized workflow, coupled with highly responsive parts and service support. Our United States and Europe based engineering, manufacturing, sales and service operations provide a global support system covering the full product portfolio of Alliance, Serco, TEI, ASC, Pallmac, J&L and Tanabe machines. Barry-Wehmiller is a diversified global supplier of engineering consulting and manufacturing technology for the packaging, corrugating, sheeting and paper-converting industries. By blending people-centric leadership with disciplined operational strategies and purpose-driven growth, Barry-Wehmiller has become a $3 billion organization with nearly 12,000 team members united by a common belief: to use the power of business to build
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: About Us (company description), Job Description (position summary, responsibilities, etc.), What You'll Do (detailed duties), What You'll Need (requirements), Compensation, Benefits, plus some EEO etc which we should remove. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have About Us (company description) maybe not exactly "About the role". Could we use "About the role" for position summary? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. So we should map content to those headings.
We have:
- About the role: could include Position Summary and maybe On-site role location.
- Responsibilities: could be the "What You'll Do" sections (ERP Administration & Data Integrity, Reporting & Data Analytics, Business Process & Collaboration). Could also include some from Job Description.
- Requirements: "What You'll Need" required and preferred.
- Qualifications: maybe overlap with Requirements; but we could combine? They said prefer a few substantive sections over many thin ones. So maybe we just have About the role, Responsibilities, Requirements, Benefits, Pay. Qualifications and Skills maybe not needed separately if covered.
But we must not create sections with filler. So we need to ensure each heading has substantive content.
We have Pay: Compensation: $77,000 - 90,000 (DOE). That's specific, so we can include Pay section.
Benefits: described: medical, dental, vision, life insurance, disability insurance, 401K with employer match, PTO, paid holidays and a bonus program. That's substantive.
Schedule: Not mentioned explicitly; only "On-site role in Spokane, WA". No schedule details like full-time, hours. So we should not create Schedule section.
Qualifications: Could be separate from Requirements but we might combine into Requirements. Since they said prefer few sections, we can omit Qualifications.
Skills: Could be part of Requirements; we can omit.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
Now we need to format content.
About the role: include position summary, on-site location, maybe team description? The "About Us" is company description; maybe that belongs elsewhere but we could incorporate into About the role? The instruction says use headings e.g. About the role. So we can put company overview there? Might be okay. But we could also include "About Us" as a paragraph under About the role.
Let's extract substantive info:
About Us: Alliance Machine Systems International, LLC is a privately held company with over 35 years of history dedicated to providing corrugated box manufacturing machines and services to the changing industry. As the paperboard packaging industry's premier global supplier of productivity-enhancing process machinery and systems, we supply innovative designs, intelligent automation, and optimized workflow, coupled with highly responsive parts and service support. Our United States and Europe based engineering, manufacturing, sales and service operations provide a global support system covering the full product portfolio of Alliance, Serco, TEI, ASC, Pallmac, J&L and Tanabe machines. Barry-Wehmiller is a diversified global supplier of engineering consulting and manufacturing technology for the packaging, corrugating, sheeting and paper-converting industries. By blending people-centric leadership with disciplined operational strategies and purpose-driven growth, Barry-Wehmiller has become a $3 billion organization with nearly 12,000 team members united by a common belief: to use the power of business to build a better world.
That's company description. Could be placed under About the role.
Position Summary: The Business Systems Analyst supports the organization's Visual ERP environment and its data, reporting, and process infrastructure: supporting and training users, troubleshooting issues, and driving process improvement. This role emphasizes ERP administration and support today, with growth toward broader business analysis over time. This is a hands-on, detail-driven role. The person in this seat will spend most of their time in the data: running daily reconciliation checks, resolving anomalies in inventory, labor, and financial transactions, and helping departments and individuals understand how the ERP system functions and what the data is telling them. Deep SQL expertise is not required at hire — data fluency (understanding relationships, joins, and how transactional data flows through an ERP system) matters more, and query-writing skill will develop on the job, increasingly supported by AI-assisted tools. Our Team We empower organizational success through responsive ERP support, data analytics, and innovative solutions, striving to connect people and systems with empathy and integrity. Responsive — respond to requests promptly, with proactive communication throughout. Innovative — pursue creative, fit-for-purpose solutions and new tools. Empathy — listen first and understand the need behind every request. Integrity — ensure data is complete, accurate, and verified; hold to honest, transparent standards.
We can combine.
Responsibilities: list bullet points from "What You'll Do". Let's extract bullet-like sentences:
- Review a standing set of daily reconciliation queries across inventory, labor, and financial transactions, resolving anomalies before they compound.
- Investigate and address data issues (orphaned records, shipment discrepancies, transaction errors), using judgment on when to resolve directly vs. loop in the relevant department.
- Research and test ERP functionality to validate fixes, evaluate new features, and support process changes before rollout.
- Manage ERP user setup, access, and basic system administration, including user license management.
- Manage and oversee test databases, and coordinate with corporate teams (such as SQL DBAs), technical support, and service providers.
- Assist with configuration file updates and installing report software as needed.
- Provide both formal and informal training, for both individuals and groups, on Infor Visual ERP functionality, processes, and best practices.
- Support month-end close, including same-day resolution of time-sensitive costing anomalies and reconciliation items.
- Develop, maintain, and modernize reports across the team's toolset (Excel, SSRS, Gupta, Crystal Reports, Power BI, Synoptix).
- Write SQL Server queries to select, update, and insert records, using AI-assisted tools as needed.
- Provide data and information to corporate entities as needed.
- Collaborate with stakeholders across departments to define business processes requirements.
- Assist with existing process improvement projects, growing toward independent ownership over time.
- Support software implementation and upgrade efforts, including future assistance with data conversions and migrations.
- Create and maintain IT documentation, as well as process documentation for other departments.
- Serve as backup for other team members as needed, building toward full cross-coverage over time.
That's a lot; we can put as - .
Requirements: Required and Preferred.
Required:
- 1–5 years of experience supporting an ERP system (any industry — Visual ERP experience not required).
- Strong data fluency: comfort with relational database concepts, table relationships, and joins.
- Willingness to learn manufacturing operations and data (BOMs, work orders, routings, labor reporting); no prior experience required.
- Strong troubleshooting instincts, attention to detail, and comfort with a disciplined daily process.
- Ability to translate technical/data findings into plain-language explanations for non-technical stakeholders.
- Strong teamwork and collaboration skills; works closely, in-office, with other analysts daily.
- Sound judgment for prioritizing and multi-tasking across a substantial, ongoing project backlog.
Preferred:
- Experience with Infor Visual ERP specifically.
- Experience writing SQL queries (SQL Server) and/or working in SSMS.
- Experience with report-writing tools such as Power BI, SSRS, Power Query, Crystal Reports, or Gupta.
- Prior exposure to a manufacturing or product engineering environment.
We can list as
- for each.
Benefits: list bullet points.
- medical, dental, vision
- life insurance
- disability insurance
- 401K with employer match
- PTO
- paid holidays
- bonus program
We can combine.
Pay: $77,000 - 90,000 (DOE). We'll put in
.
Now ensure we don't include boilerplate like EEO, equal opportunity, M/F/D/V, E-Verify, pre-employment screening, etc. Remove.
Also remove duplicated lines like "At Barry-Wehmiller we recognize that people come with a wealth of experience..." That's EEO-ish; remove.
Also remove "Please let us know if you require reasonable accommodations during the interview process." That's application instruction; remove.
Also remove "Company: Alliance" maybe minor metadata; we can drop.
Now produce HTML fragment.
Structure:
About the role
... (company description + position summary + team values)
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Pay
$77,000 - 90,000 (DOE)
Make sure no extra whitespace? It's fine.
Now craft the About the role paragraph.
We need to include company description and position summary and team values.
Let's write concise but preserve all substantive info. Not to invent or summarize away detail. We need to preserve all substantive information; but we can combine sentences as long as we don't lose info. It's okay to rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Summarizing may be okay if we keep all details? Safer to keep original sentences but we can combine.
We'll include:
- Alliance Machine Systems International, LLC is a privately held company with over 35 years of history dedicated to providing corrugated box manufacturing machines and services to the changing industry. As the paperboard packaging industry's premier global supplier of productivity-enhancing process machinery and systems, we supply innovative designs, intelligent automation, and optimized workflow, coupled with highly responsive parts and service support. Our United States and Europe based engineering, manufacturing, sales and service operations provide a global support system covering the full product portfolio of Alliance, Serco, TEI, ASC, Pallmac, J&L and Tanabe machines. Barry-Wehmiller is a diversified global supplier of engineering consulting and manufacturing technology for the packaging, corrugating, sheeting and paper-converting industries. By blending people-centric leadership with disciplined operational strategies and purpose-driven growth, Barry-Wehmiller has become a $3 billion organization with nearly 12,000 team members united by a common belief: to use the power of business to build
- .
Requirements: Required and Preferred.
Required:
- 1–5 years of experience supporting an ERP system (any industry — Visual ERP experience not required).
- Strong data fluency: comfort with relational database concepts, table relationships, and joins.
- Willingness to learn manufacturing operations and data (BOMs, work orders, routings, labor reporting); no prior experience required.
- Strong troubleshooting instincts, attention to detail, and comfort with a disciplined daily process.
- Ability to translate technical/data findings into plain-language explanations for non-technical stakeholders.
- Strong teamwork and collaboration skills; works closely, in-office, with other analysts daily.
- Sound judgment for prioritizing and multi-tasking across a substantial, ongoing project backlog.
Preferred:
- Experience with Infor Visual ERP specifically.
- Experience writing SQL queries (SQL Server) and/or working in SSMS.
- Experience with report-writing tools such as Power BI, SSRS, Power Query, Crystal Reports, or Gupta.
- Prior exposure to a manufacturing or product engineering environment.
We can list as
- for each.
Benefits: list bullet points.
- medical, dental, vision
- life insurance
- disability insurance
- 401K with employer match
- PTO
- paid holidays
- bonus program
We can combine.
Pay: $77,000 - 90,000 (DOE). We'll put in
. Now ensure we don't include boilerplate like EEO, equal opportunity, M/F/D/V, E-Verify, pre-employment screening, etc. Remove. Also remove duplicated lines like "At Barry-Wehmiller we recognize that people come with a wealth of experience..." That's EEO-ish; remove. Also remove "Please let us know if you require reasonable accommodations during the interview process." That's application instruction; remove. Also remove "Company: Alliance" maybe minor metadata; we can drop. Now produce HTML fragment. Structure:
About the role
... (company description + position summary + team values)
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
$77,000 - 90,000 (DOE)
Make sure no extra whitespace? It's fine. Now craft the About the role paragraph. We need to include company description and position summary and team values. Let's write concise but preserve all substantive info. Not to invent or summarize away detail. We need to preserve all substantive information; but we can combine sentences as long as we don't lose info. It's okay to rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Summarizing may be okay if we keep all details? Safer to keep original sentences but we can combine. We'll include: - Alliance Machine Systems International, LLC is a privately held company with over 35 years of history dedicated to providing corrugated box manufacturing machines and services to the changing industry. As the paperboard packaging industry's premier global supplier of productivity-enhancing process machinery and systems, we supply innovative designs, intelligent automation, and optimized workflow, coupled with highly responsive parts and service support. Our United States and Europe based engineering, manufacturing, sales and service operations provide a global support system covering the full product portfolio of Alliance, Serco, TEI, ASC, Pallmac, J&L and Tanabe machines. Barry-Wehmiller is a diversified global supplier of engineering consulting and manufacturing technology for the packaging, corrugating, sheeting and paper-converting industries. By blending people-centric leadership with disciplined operational strategies and purpose-driven growth, Barry-Wehmiller has become a $3 billion organization with nearly 12,000 team members united by a common belief: to use the power of business to build
- for each.
Benefits: list bullet points.
- medical, dental, vision
- life insurance
- disability insurance
- 401K with employer match
- PTO
- paid holidays
- bonus program
We can combine.
Pay: $77,000 - 90,000 (DOE). We'll put in