Supply Chain Systems Project Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job description. Key parts: - Job Title: Supply Chain Systems Project Manager (not to be repeated as heading) - Working Pattern: Full Time - Working Location: Aiken, SC (but later location: Graniteville, SC? There's inconsistency: Working Location: Aiken, SC; later location: Graniteville, SC. Might be a mistake. We need to preserve all substantive info; we can include location info in a paragraph. - Relocation assistance will be provided if applicable. - Global Grade Level:10 (metadata, can be folded into short p) - Why Rolls-Royce? (section about company) Could be "About the role"? Actually "Why Rolls-Royce?" is more about company culture; could be placed under "About the role" or separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. We have: - What you will be doing? (list of duties) => Responsibilities. - Basic Requirements: (education/experience) => Requirements (or Qualifications). They differentiate Basic Requirements and Preferred Requirements. Could combine into Requirements (basic) and maybe Skills? But we have Preferred Requirements as separate list; could be under Requirements as well, or under Skills? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (basic) and maybe Qualifications (preferred) or Skills. But we need to avoid thin sections. Perhaps combine basic and preferred into Requirements (or Qualifications). Let's decide: Use "Requirements" for basic requirements, and "Preferred Qualifications" maybe not in list; but we can put preferred under "Requirements" as well, or under "Skills". Since they are preferences, maybe "Preferred Qualifications". But not in the given list; but we can still use "Qualifications" heading for preferred. The instruction says use those headings as examples, not strict list; we can use others if needed? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings; we shouldn't invent others like "Preferred Qualifications". So we need to map content to those headings. Thus: - About the role: could include the "Why Rolls-Royce?" paragraph and maybe description of role overview. - Responsibilities: the bullet list under "What you will be doing?" (the list of duties). - Requirements: basic requirements (education/experience, work authorization). Also maybe include "Global Grade Level:10" and relocation assistance? Could be minor metadata. - Qualifications: preferred requirements (SAP Ariba, PPAP, NWC reporting). Could also include skills like SAP Key User, etc. - Skills: maybe not needed if we covered in Qualifications. But we could include specific skills like SAP, Ariba, EDI, PPAP, NWC reporting, etc. However we already have them in Qualifications. To avoid thin sections, maybe combine preferred into Qualifications and skip Skills. - Benefits: the paragraph about benefits. - Pay: the pay range ($98,566 - $160,169-Annually). Also note about remote employees pay range variation; we can include that. - Schedule: maybe not provided; working pattern full time. Could include schedule? Not given. So we should not create Schedule section if no specific content. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to ensure we preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove closing date, job posting date? Those are metadata; could be folded into short p or dropped. 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 paragraph with metadata like Working Pattern, Working Location, Relocation assistance, Global Grade Level, Closing Date, Job Posting Date. But we need to avoid duplication. We must not repeat the job title as a heading. We must output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

About the role

At Rolls-Royce we are proud to be a business that has truly helped to shape the modern world and are committed to always being a force for progress; powering, protecting and connecting people everywhere. By joining Rolls-Royce, you’ll have the opportunity to create world-class power and propulsion solutions, pushing your problem-solving and ingenuity, to deliver real impact that puts safety first. You’ll be given responsibility and the opportunity to grow in our high-performance culture. This is Infinite Potential. And it’s your chance to really shine and contribute to one of the world’s most recognized brands and a beacon for engineering excellence.

Maybe also include a brief description of the role: "Serve as the primary SAP Key User for Supply Chain..." but that belongs to Responsibilities. Now Responsibilities:

Responsibilities

• Serve as the primary SAP Key User for Supply Chain, providing first-level system support, troubleshooting issues, and coordinating resolutions with IT
• Act as the key user for the Expeditors Portal, SAP Business Network (Ariba), and EDI, ensuring accurate data integration, supplier connectivity, and system performance
• Support supplier onboarding, electronic data exchange, and implementation projects while collaborating with internal teams, suppliers, and IT
• Prepare monthly Net Working Capital (NWC) reports and cash flow forecasts, analyze variances, and identify inventory reduction and cash flow improvement opportunities
• Coordinate supply chain activities for new product launches, monitoring supplier readiness, component availability, and production milestones

Now Requirements (basic):

Requirements

• Associate’s degree in Business Administration, Supply Chain, Logistics or a related field with 4+ years of experience, OR Bachelor’s degree in Business Administration, Supply Chain, Logistics or a related field with 2+ years of experience, OR Master's degree in Business Administration, Supply Chain, Logistics or a related field, OR in lieu of a degree 6+ years of professional experience in Supply Chain or logistics in a manufacturing environment
• Applicants must be authorized to work for any employer in the U.S without sponsorship. We are unable to sponsor or take over sponsorship of an employment Visa at this time.

We could also include relocation assistance and grade level as a short p after the list or within a paragraph. But we already used ul for requirements; we could add a paragraph after list for metadata. But we need to preserve all substantive info: Working Pattern: Full Time, Working Location: Aiken, SC, Relocation assistance will be provided if applicable, Global Grade Level:10. Also later location: Graniteville, SC (maybe actual location). There's inconsistency; we need to preserve both? The posting says Working Location: Aiken, SC and later Location: Graniteville, SC under Pay/Benefits section. Might be a mistake but we should include both as they appear. We could combine into a paragraph: "Working Location: Aiken, SC (position based in Graniteville, SC)." But that might be altering. Better to keep both statements as separate sentences. We can add a

after the Requirements list: "

Working Pattern: Full Time. Working Location: Aiken, SC. Relocation assistance will be provided if applicable. Global Grade Level: 10. (Note: Position location also referenced as Graniteville, SC.)

" But that adds interpretation. Maybe just include the statements as they appear: "Working Pattern: Full Time. Working Location: Aiken, SC. Relocation assistance will be provided if applicable. Global Grade Level: 10." And later we can add "Location: Graniteville, SC." as separate sentence. We need to avoid duplication; but it's okay. Now Qualifications (preferred):

Qualifications

• Experience leveraging SAP Business Network (Ariba) to strengthen supplier connectivity, data visibility, and end-to-end supply chain execution.
• Knowledge of PPAP and new product introduction processes, with the ability to support launch readiness, risk mitigation, and cross-functional alignment.
• Experience using Net Working Capital reporting and cash flow forecasting to identify improvement opportunities and support operational decision-making.

Now Benefits:

Benefits

Rolls-Royce provides a comprehensive and competitive Total Rewards package that includes base pay and a discretionary bonus plan. Eligible employees may have the opportunity to enroll in other benefits, including health, dental, vision, disability, life and accidental death & dismemberment insurance; a flexible spending account; a health savings account; a 401(k) retirement savings plan with a company match; Employee Assistance Program; Paid Time Off; certain paid holidays; paid parental and family care leave; tuition reimbursement; and a long-term incentive plan. The options available to an employee may vary depending on eligibility factors such as date of hire, and employment type.

We also have a paragraph about Business Unit Power Systems description; that seems like duplicated content from earlier "Why Rolls-Royce?" but more specific to Power Systems. It may be considered substantive; we could include it under About the role or as a separate paragraph. But we already have About the role with the generic Rolls-Royce description. The Power Systems description is additional detail about the business unit; we could incorporate it into About the role as extra paragraph. However we must not invent or summarize away detail; we need to preserve it. So we can add another

under About the role describing Power Systems. Thus About the role could have two paragraphs: first the generic Why Rolls-Royce?; second the Power Systems description. Let's capture that text: "The Business Unit Power Systems of Rolls-Royce provides world-class power solutions and complete life-cycle support under our product and solution brand mtu. Through digitalization and electrification, we strive to develop drive and power generation solutions that are even cleaner and smarter and thus provide answers to the challenges posed by the rapidly growing societal demands for energy and mobility. We deliver and service comprehensive, powerful and reliable systems, based on both gas and diesel engines, as well as electrified hybrid systems. These clean and technologically-advanced solutions serve our customers in the marine and infrastructure sectors worldwide." We need to ensure we don't duplicate the earlier similar paragraph (the one about Power Systems earlier in the posting). There's a similar paragraph earlier: "Power Systems is the Rolls-Royce business which provides world-class power solutions and complete life-cycle support under our product and solution brand mtu. Through digitalisation and electrification, we strive to develop drive and power generation solutions that provide answers to the challenges posed by the rapidly growing societal demands for energy and mobility. We deliver and service comprehensive, powerful and reliable systems, based on both gas and diesel engines, as well as electrified hybrid systems. These technologically advanced solutions serve our customers in the marine and infrastructure sectors worldwide. Our vision is to ensure that the quality and dynamism that shaped our history continues into our future. It’s a bold pursuit, and we never stop striving to go further, faster, and better. We lead progress, creating the technologies that move us forward. If you’re driven to grow, to learn, and to make a lasting difference, this is where you belong." That's also substantive. We could combine both but avoid duplication. The two paragraphs are similar but not identical; they both describe Power Systems. To preserve all substantive