Materials Planner

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 that have real specific content. The posting includes summary (about role), essential duties and responsibilities, competencies (core competencies and job core competencies), summary of education, experience & certification (qualifications), required knowledge, skills & abilities (skills), pay (expected WA salary range), benefits (suite of comprehensive benefits). No schedule info. So we should have sections: About the role (maybe from Summary), Responsibilities (Essential Duties And Responsibilities), Qualifications (Summary Of Education, Experience & Certification), Skills (Required Knowledge, Skills & Abilities), Benefits, Pay. Possibly also Competencies could be part of Skills or Qualifications? But we have a Skills section for required knowledge, skills & abilities. Competencies could be included under Skills or maybe separate but not required heading. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include. We have content for About the role (summary), Responsibilities, Qualifications, Skills, Benefits, Pay. No Schedule. No Requirements separate (maybe qualifications covers). We'll not include Requirements if not distinct. We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include boilerplate like EEO etc. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement; we should drop that. We need to format using

for headings,

• for any list of duties/requirements/benefits, and

  for prose. We need to decide what is a list: Essential duties and responsibilities are many sentences each starting with a verb; could be turned into

  • . Similarly benefits list: healthcare (medical, dental & vision), life insurance, paid time off, and a 401(k) savings plan with company match. That's a list. Competencies maybe could be a list but not required heading; but we could include under Skills? However we have a Skills section for required knowledge, skills & abilities. We could also include competencies under Skills as a list? But better to follow instruction: use
    • for any list of duties/requirements/benefits. Competencies are not duties/requirements/benefits; they are competencies. Could be placed in a

      paragraph. Education/experience/certification is prose; could be a

      . Required knowledge, skills & abilities is a list; we can make

      • . Pay: we have a sentence about salary range; could be a

        . Benefits: list. About the role: summary paragraph. We must not include headings with filler text. Ensure we include all substantive info. Let's extract content: Summary: "The Materials Planner is responsible for developing and maintaining accurate Bills of Materials (BOMs) within the MRP system to support timely and cost-effective production of custom aircraft interiors. This role ensures material availability aligns with production schedules by translating engineering designs into material requirements, coordinating cross-functionally, and driving improvements in planning accuracy, lead times, and inventory efficiency." Essential Duties And Responsibilities: list of sentences: - Examines engineering drawings for inaccuracies in material/component specification, prior to or after formal engineering release, utilizing knowledge of basic engineering and manufacturing principles / techniques. - Reviews and evaluates engineering drawings, calculates quantities and types of material, parts, or other items required, determines “make versus buy” sub-assemblies and builds the Bill of Material in the MRP system. - Ensure data integrity within MRP to support accurate planning, procurement, and production execution. - Calculates material requirements based on production schedules, lead times, and demand forecasts. - Generates and manages purchase requisitions in alignment with production needs. - Monitors and tracks material deliveries to ensure alignment with aircraft modification schedules and production timelines. - Supports Engineering, Procurement, Ops, PM, Sales and other personnel to exchange information regarding material specifications, material lead times, substitutions, and costs, as required. - Works with Procurement to improve lead time from vendors and engineering for quality improvements. - Coordinates with Procurement and Stores to maintain adequate levels of parts and raw materials to manufacture the products. - Coordinates with Procurement when items are delayed to determine what materials are to be expedited. - Analyzes material costs and identify opportunities to optimize value and reduce waste. - Drives improvements in planning processes, material flow, and system utilization. - Supports resolution of material-related issues impacting production efficiency. - Other duties as assigned. Competencies: Greenpoint Core Competencies list (Adaptability, Communications, Dependability, Initiative, Teamwork, Work Quality) each with description. Job Core Competencies (Cooperation, Judgment, Planning and Organization) each with description. We could include these as a list under maybe Skills? But we already have Skills section for required knowledge, skills & abilities. Might be better to include a separate section for Competencies? Not in allowed headings list but we could still use

        for Competencies? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are examples; we could still use other headings but better to stick to those. Competencies could be placed under Skills or Qualifications. However the required knowledge, skills & abilities section already covers technical skills. Competencies are behavioral; maybe we can include them under Skills as part of a list? But they'd be mixed with technical skills; maybe better to include a separate section named "Competencies" but not in the list; risk of violating instruction? The instruction: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say you cannot use other headings, but suggests those are typical. Safer to include them under Skills as a sub-list? But we need to preserve all substantive info; we could include them as a

        • under Skills heading, but that would mix technical and behavioral. Might be okay. Alternatively we could create a section "Requirements" for education/experience/certification, and "Qualifications" maybe not needed. But we have both education/experience and required knowledge, skills & abilities. Could treat education/experience as Qualifications, and required knowledge, skills & abilities as Skills. Thus:

          About the role

          ...summary...

          Responsibilities

          • ... each duty...

          Qualifications

          Bachelor’s degree in Supply Chain, Engineering, Business, or related field, or equivalent combination of education and experience. 2–5 years of experience in materials planning, production planning, or supply chain within a manufacturing environment. Experience in aerospace or aircraft interiors preferred. Employees working on programs subject to International Traffic in Arms Regulations must qualify as a US Person which is defined as a US Citizen, a Permanent Resident who does not work for a foreign company, foreign government, foreign governmental agency or organization, or a political asylee for legal compliance purposes. This safety-sensitive position is covered by the Department of Transportation's (DOT) Drug and Alcohol Testing Program. Any applicant selected for this position will be subject to pre-employment drug testing. Persons occupying a "safety-sensitive” position will be subject to random drug and/or alcohol testing. Post-accident, reasonable cause, and return-to-duty tests may also be required based on specific circumstances.

          Skills

          • Demonstrated advanced expertise with Database software; Internet software, MRP software, Inventory and order processing systems; Project Management software; Spreadsheet software and Word Processing software.
          • Ability to read and interpret blueprints, engineering drawings and materials specifications.
          • Familiarity with the procurement of raw materials, standards, parts, and commodities, preferably related to VIP aircraft interiors.
          • In depth knowledge of MRP systems and logic, and familiarity with manufacturing flows and production planning
          • Ability to solve complex problems and deal with a variety of variables in situations where only limited standardization exists.
          • Ability to drive continuous improvement processes and standards.
          • Ability to work independently and cross-functionally as part of an established and growing team.
          • Strong communication and problem-solving skills.
          • Strong time management and organizational skills.
          • Ability to sit for extended periods of time, use hands to lift and/or move up to 10 pounds, occasionally lift and/or move up to 25 pounds and have close/color vision ability to adjust focus.
          • Ability to travel as required.
          • Ability to work outside of core business hours as required.
          We also need to include competencies? Could add as another list under Skills? But we already used Skills for technical. Could add a second
          under Skills for competencies? Might be confusing. Perhaps better to add a separate section "Competencies" using

          even though not in examples; risk but maybe acceptable. The instruction: "use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use h3 for section headings (giving examples). I'd say it's okay to use other headings as long as they are h3. However to be safe, we could incorporate competencies into Skills as a separate list labeled with a preceding

          like "Core Competencies:" then list. But that would break the rule of using

          • for any list of duties/requirements/benefits; competencies are not those, but still a list; we could still use
            • but it's okay. Better: after Skills list, add a

              Core Competencies: Adaptability – ..., Communications – ..., etc. But that would be a long paragraph; we could keep as

              • but it's still a list; the rule didn't restrict to only duties/requirements/benefits; it said use
                • for any list of duties/requirements/benefits. It didn't say you cannot use for other lists, but it's implied. Safer to use

                  for competencies. Thus after Skills, add a

                  containing the competencies descriptions. Then Benefits:

                  Benefits

                  • healthcare (medical, dental & vision)
                  • life insurance
                  • paid time off
                  • 401(k) savings plan with company match
                  Pay:

                  Pay

                  The expected WA salary range for this position is between $78,000.00 - $103,000.00 USD. Actual compensation will be determined based on experience, education, location, and other factors permitted by law.

                  We should also include About Greenpoint Technologies? That's boilerplate about company; maybe considered not essential? It's descriptive of company; could be considered part of About the role? But the summary already includes role description; the company description might be considered boilerplate but it's substantive about employer. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not explicitly listed as boilerplate to remove; it's about the company. Might be considered part of "About Greenpoint Technologies".