Chemical Production Planner/Scheduler

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: Brief Description Production Planning: Develop and maintain short- and long-term production schedules in Microsoft Dynamics MRP. This is intended to drive the SIOP plan on a 24 month time horizon.Adjust schedules based on changes in demand, inventory levels or supply chain disruptions to ensure timely production with minimal downtime.Use planned production orders to firm and consolidate new production. Inventory Management Use Dynamics to actively monitor raw material, WIP, and finished goods inventory.Work directly with the Inventory Manager to ensure and maintain optimal inventory levels by analyzing sales, usage trends, and safety stock.Work directly with Procurment to ensure proper raw material supply and assist with providing forecasts to suppliers. Demand Forecasting Use planning parameters such as lead times, standard batch size and production cycle times to develop a supply plan that meets demand forecast and inventory targets. Resource Allocation: Leverage Dynamics to allocate production resources efficiently by assigning raw materials, equipment, resources and labor in coordination with the production manager to meet scheduling needs. Production Optimization Work directly with the Production Manager and Engineering team to seek opportunities to improve production efficiency, reduce costs, and enhance product quality by reviewing MRP generated data to identify bottlenecks, delays and efficiency improvements in batch sizing and backend processing capabilities. Monitor and develop KPIs Work with manufacturing to track and report schedule adherence, asset utilization and production delays that affect customer orders. Supply Chain Coordination Monitor raw material as well as purchased finished goods supply transactions using Dynamics PO tracking.Ensure timely raw material replenishment, proper lead times and monitor delivery dates directly within the system to eliminate production downtime. Confirming New Sales Orders Evaluate incoming sales orders against current inventory plus planned production and planned transfer orders. Confirm or adjust ship dates based on system availability through ATP and communicate feasible timelines to Customer Success team. Create Revised New Shipment Dates If orders have insufficient inventory to meet the original delivery date, work with the sales and customer service teams to provide updated delivery timelines, ensuring clear communication with customers regarding revised shipping schedules. Quality Control Work closely with quality control teams to ensure products are released in a timely manner to support sales orders. Then Requirements section: Required Skills/Abilities: list many bullet-like items separated by periods. Then Education And Experience: list many items. Then Physical Requirements: Reasonable accommodation... etc. Then Summary: As Chemical Production Planner/Scheduler, you will report directly to the Global Supply Chain Planner, ensuring the efficient and timely production of chemical products. Your responsibilities encompass a range of crucial functions that will utilize heavily on Microsoft Dynamics’ MRP system to plan, schedule, track and optimize production activities. Your responsibilities will support end-to-end production and supply chain visibility, contributing directly to operational excellence and customer satisfaction. We need to produce sections: About the role (maybe from brief description?), Responsibilities (list of duties), Requirements (maybe combine required skills/abilities and education/experience?), Qualifications (maybe education/experience?), Skills (maybe required skills?), Benefits (none given), Pay (none), Schedule (none). According to instruction: include a section ONLY when posting has real, specific content for it. So we should not include Benefits, Pay, Schedule if not present. Also we should not include sections with placeholder like "commensurate with experience". So we will include About the role, Responsibilities, Requirements, Qualifications, Skills maybe. But we need to avoid duplication. Let's decide mapping: - About the role: could be the brief description summary (first paragraph). Could also be the Summary at end. We need to decide. Better: Use "About the role" for the brief description overview (the first paragraph describing production planning etc). Then "Responsibilities" for the list of duties (the bullet-like items after brief description). Then "Requirements" for the Required Skills/Abilities list. Then "Qualifications" for Education And Experience. Then "Skills" maybe for required skills again? But we already used skills in Requirements. Could combine Requirements and Qualifications. However instruction: prefer a few substantive sections over many thin ones. So we could combine Required Skills/Abilities and Education/Experience into a single "Requirements" section, and maybe not have separate Qualifications or Skills. But we need to preserve all substantive info. We can put all under Requirements with subheadings? But we cannot add extra headings beyond the allowed list? 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, but suggests those are typical. Safer to stick to those headings. We can have multiple sections: About the role, Responsibilities, Requirements (including skills and education), maybe Qualifications not needed if we covered. But we could still have Qualifications for education/experience, and Skills for required skills. That would be three sections: About the role, Responsibilities, Requirements (maybe split into Skills and Qualifications). However that may be thin. Let's think: The posting has distinct sections: Brief Description (duties), Required Skills/Abilities, Education And Experience, Physical Requirements, Summary. Physical Requirements is also substantive (office, 8 hrs computer, location, travel). Should we include that? It could go under Requirements or maybe a separate section? There's no specific heading for Physical Requirements in allowed list, but we could fold into Requirements. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine Physical Requirements into Requirements. Thus we can have: - About the role: brief description (first paragraph). - Responsibilities: list of duties (the bullet-like paragraphs after brief description). - Requirements: combine Required Skills/Abilities, Education And Experience, Physical Requirements, Summary? Actually Summary is more about role; maybe we could add to About the role. But we must not repeat job title as heading. The Summary mentions "As Chemical Production Planner/Scheduler, you will report directly to the Global Supply Chain Planner..." That's substantive; we could include in About the role or Responsibilities? Probably About the role. Thus About the role: combine brief description and summary. Responsibilities: list of duties (the many bullet-like items). We'll format as

• each. Requirements: combine Required Skills/Abilities (list), Education And Experience (list), Physical Requirements (list). We'll format as
  • each. We must not include Benefits, Pay, Schedule sections because no info. Now we need to ensure we preserve all substantive information. Let's extract. Brief Description text: "Production Planning: Develop and maintain short- and long-term production schedules in Microsoft Dynamics MRP. This is intended to drive the SIOP plan on a 24 month time horizon.Adjust schedules based on changes in demand, inventory levels or supply chain disruptions to ensure timely production with minimal downtime.Use planned production orders to firm and consolidate new production.Inventory Management Use Dynamics to actively monitor raw material, WIP, and finished goods inventory.Work directly with the Inventory Manager to ensure and maintain optimal inventory levels by analyzing sales, usage trends, and safety stock.Work directly with Procurment to ensure proper raw material supply and assist with providing forecasts to suppliers.Demand Forecasting Use planning parameters such as lead times, standard batch size and production cycle times to develop a supply plan that meets demand forecast and inventory targets.Resource Allocation: Leverage Dynamics to allocate production resources efficiently by assigning raw materials, equipment, resources and labor in coordination with the production manager to meet scheduling needs.Production Optimization Work directly with the Production Manager and Engineering team to seek opportunities to improve production efficiency, reduce costs, and enhance product quality by reviewing MRP generated data to identify bottlenecks, delays and efficiency improvements in batch sizing and backend processing capabilities.Monitor and develop KPIs Work with manufacturing to track and report schedule adherence, asset utilization and production delays that affect customer orders.Supply Chain Coordination Monitor raw material as well as purchased finished goods supply transactions using Dynamics PO tracking.Ensure timely raw material replenishment, proper lead times and monitor delivery dates directly within the system to eliminate production downtime.Confirming New Sales Orders Evaluate incoming sales orders against current inventory plus planned production and planned transfer orders. Confirm or adjust ship dates based on system availability through ATP and communicate feasible timelines to Customer Success team.Create Revised New Shipment Dates If orders have insufficient inventory to meet the original delivery date, work with the sales and customer service teams to provide updated delivery timelines, ensuring clear communication with customers regarding revised shipping schedules.Quality Control Work closely with quality control teams to ensure products are released in a timely manner to support sales orders." Note there are missing spaces after periods; but we can keep as is or add spaces for readability? We should preserve substantive info; we can add spaces for readability but not change meaning. Probably okay to keep as is but better to add spaces after periods for readability. However we must not invent content; adding spaces is fine. Now Responsibilities: Actually the brief description already includes many responsibilities. The list after brief description seems to be the same as responsibilities. The posting seems to have no separate responsibilities section; the brief description enumerates duties. So we could treat the brief description as About the role, and responsibilities maybe not needed separately. But we need to include Responsibilities section if we have specific content. The brief description already covers responsibilities; we could still have Responsibilities section with same content but that would duplicate. Better to treat About the role as overview, and Responsibilities as detailed list. However the brief description already is a list of duties; we could split: About the role = short overview (first sentence maybe). But the instruction: "Prefer a few substantive sections over many thin ones." So maybe we just have About the role (overview) and Responsibilities (detailed list). But we need to avoid duplication. Let's parse: The brief description includes many sentences each starting with a capitalized term (Production Planning, Inventory Management, Demand Forecasting, Resource Allocation, Production Optimization, Monitor and develop KPIs, Supply Chain Coordination, Confirming New Sales Orders, Create Revised New Shipment Dates, Quality Control). Those are responsibilities. So we could treat About the role as a short summary (maybe first two sentences?) but there is no explicit overview besides the first sentence: "Production Planning: Develop and maintain short- and long-term production schedules in Microsoft Dynamics MRP. This is intended to drive the SIOP plan on a 24 month time horizon." That's not a full overview. Better: Use About the role for the summary paragraph at the end: "As Chemical Production Planner/Scheduler, you will report directly to the Global Supply Chain Planner, ensuring the efficient and timely production of chemical products. Your responsibilities encompass a range of crucial functions that will utilize heavily on Microsoft Dynamics’ MRP system to plan, schedule, track and optimize production activities. Your responsibilities will support end-to-end production and supply chain visibility, contributing directly to operational excellence and customer satisfaction." That is a good overview. Then Responsibilities: the enumerated duties from the brief description. Then Requirements: combine Required Skills/Abilities, Education And Experience, Physical Requirements. Let's extract Required Skills/Abilities list: "Required Skills/Abilities: Excellent written and verbal communication skills.Excellent organizational skills and strong attention to detail. Excellent analytical skills.Excellent problem-solving and decision-making abilities.Clear and effective written and verbal communication skills.Proficient with Microsoft Office Suite or related software.Efficient time management and people management skills.Ability to collaborate with others and work independently.Ability to identify key details.Ability to troubleshoot and solve problems." Note duplicate "Excellent written and verbal communication skills." appears twice; we should preserve but could deduplicate? Instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicate is substantive? It's repeated; we could keep both but it's redundant. Probably better to keep as is but we could note duplicate; but preserving means we shouldn't remove info; removing duplicate could be considered summarizing away detail? It's not adding info, just removing redundancy. Might be okay but safer to keep both? However it's weird. I'd keep one instance to avoid weird