Jobs · Information Technology · New Mexico

Senior/Principal Production Planning Control Specialist - Infrastructure & Asset Management

Sandia National Laboratories · Albuquerque, NM · 1 mo ago
Information Technology$87k–$169k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Sandia" (company description) but we should not repeat job title as heading. We need to include sections only when there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse content: - About the role: maybe the paragraph "We are seeking a Production Planning Controls Specialist to join our dynamic team. On any given day, you may be called on to:" followed by bullet list of duties. That's responsibilities. So "About the role" could be a brief description: maybe the first paragraph before list. We'll treat that as About the role. - Responsibilities: the bullet list items. - Requirements: maybe the "Qualifications We Require" section. - Qualifications: maybe "Qualifications We Desire" (desired qualifications). Could be separate but we can combine? The instruction: prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But we have headings list; we can include both if they have content. We'll include Requirements (mandatory) and Qualifications (desired). Also Skills: maybe list of desired skills (knowledge, expertise, etc.) could go under Skills. But we already have Qualifications We Desire includes many items; we could treat that as Skills. However we need to avoid duplication. Let's decide: - About the role: short paragraph. - Responsibilities: bullet list of duties. - Requirements: Bachelor's degree plus 5 years experience OR equivalent; Ability to obtain DOE Q-level clearance. - Qualifications: maybe we treat "Qualifications We Desire" as Qualifications section. - Skills: maybe we could extract specific skills like knowledge of Oracle E-business Suite, etc. But that overlaps with Qualifications We Desire. Could combine Qualifications and Skills into one section? But we have headings; we could include Qualifications (desired) and Skills (technical). However to avoid many thin sections, maybe combine Qualifications and Skills into one "Qualifications" section that includes both education/degrees and technical skills. But we already have Requirements separate. So we could have: - About the role - Responsibilities - Requirements - Qualifications (includes desired qualifications and skills) - Benefits: The posting mentions benefits in the "About Sandia" paragraph: "Some of the best tools... Flexible work arrangements... Generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance and amenities aimed at creating a solid work/life balance". Also "These benefits vary by job classification." So we have benefits content. - Pay: Salary Range $87,400 - $168,800. - Schedule: Not explicitly given; there is mention of flexible work arrangements includes 9/80 and 4/10 compressed workweeks, part-time work, telecommuting. That's schedule info. So we can include Schedule section with that. We must not include sections with filler like "commensurate with experience". We have actual content. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Posting Duration", "Security Clearance" details? Those are not in headings list; we could maybe drop them unless they fit into Benefits? Probably drop as not requested. Also remove "Eeo", "NNSA Requirements For MedPEDs", "Job ID", etc. We need to preserve all substantive information: So we need to keep the benefits description, flexible work arrangements, salary range, responsibilities, requirements, qualifications, etc. Let's extract: About Sandia paragraph: "Sandia National Laboratories is the nation’s premier science and engineering lab for national security and technology innovation, with teams of specialists focused on cutting-edge work in a broad array of areas. Some of the main reasons we love our jobs: Challenging work with amazing impact that contributes to security, peace, and freedom worldwideExtraordinary co-workersSome of the best tools, equipment, and research facilities in the worldCareer advancement and enrichment opportunitiesFlexible work arrangements for many positions include 9/80 (work 80 hours every two weeks, with every other Friday off) and 4/10 (work 4 ten-hour days each week) compressed workweeks, part-time work, and telecommuting (a mix of onsite work and working from home)Generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance and amenities aimed at creating a solid work/life balance* World-changing technologies. Life-changing careers. Learn more about Sandia at: http://www.sandia.gov These benefits vary by job classification." We need to separate About the role vs About Sandia? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "About the role" heading likely refers to description of the role, not company. But we have company description in About Sandia. Could we treat that as About the role? Might be okay. However we also have a paragraph "What Your Job Will Be Like" then bullet list. That could be About the role. The company description could be omitted? But we must preserve ALL substantive information; we cannot drop company description unless it's considered boilerplate? It's not boilerplate; it's substantive about Sandia. However the headings list does not include "About the company". But we could incorporate that into About the role section? Might be odd but acceptable. The instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not exclusive? Likely they expect those headings only. So we need to map content to those headings. Company description could go under About the role? Or maybe we can omit it because it's not directly about the role? But they said preserve ALL substantive information. So we need to include it somewhere. Perhaps we can put it under About the role as a preamble. That seems plausible. Thus About the role section will contain the Sandia description plus maybe the "What Your Job Will Be Like" intro sentence. Let's craft:

About the role

Sandia National Laboratories is the nation’s premier science and engineering lab for national security and technology innovation, with teams of specialists focused on cutting-edge work in a broad array of areas. Some of the main reasons we love our jobs: Challenging work with amazing impact that contributes to security, peace, and freedom worldwide; extraordinary co-workers; some of the best tools, equipment, and research facilities in the world; career advancement and enrichment opportunities; flexible work arrangements for many positions include 9/80 (work 80 hours every two weeks, with every other Friday off) and 4/10 (work 4 ten-hour days each week) compressed workweeks, part-time work, and telecommuting (a mix of onsite work and working from home); generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance and amenities aimed at creating a solid work/life balance. World-changing technologies. Life-changing careers. Learn more about Sandia at: http://www.sandia.gov These benefits vary by job classification.

We are seeking a Production Planning Controls Specialist to join our dynamic team. On any given day, you may be called on to:

But we need to separate responsibilities list. Actually the "On any given day..." intro is part of responsibilities. So we could keep that as part of Responsibilities section intro. Thus About the role could just be the Sandia description (company). Then Responsibilities heading with the bullet list. Let's do:

About the role

Sandia National Laboratories is the nation’s premier science and engineering lab for national security and technology innovation, with teams of specialists focused on cutting-edge work in a broad array of areas. Some of the main reasons we love our jobs: Challenging work with amazing impact that contributes to security, peace, and freedom worldwide; extraordinary co-workers; some of the best tools, equipment, and research facilities in the world; career advancement and enrichment opportunities; flexible work arrangements for many positions include 9/80 (work 80 hours every two weeks, with every other Friday off) and 4/10 (work 4 ten-hour days each week) compressed workweeks, part-time work, and telecommuting (a mix of onsite work and working from home); generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance and amenities aimed at creating a solid work/life balance. World-changing technologies. Life-changing careers. Learn more about Sandia at: http://www.sandia.gov These benefits vary by job classification.

Then Responsibilities:

Responsibilities

  • Work with the equipment lifecycle team, production teams, and development staff to maintain up-to-date metrics and data to support risk assessments and investment plans.
  • Team with production floors, technical staff, project leads, and management to assess demand and make recommendations for equipment data and capacity needs.
  • Conduct risk assessments using established algorithms, continuously monitor changes to the factory and update inputs according to current and planned system needs.
  • Generate fiscal plans, presentations, and reports customized to various stakeholders to illustrate equipment and asset data, strategies, and execution plans.
  • Work across multiple missions areas to parse and curate information, collaborate on business operations improvement and process optimization. Support standardization across business groups.
  • Assist in developing and executing annual reporting.
  • Participate in inventory and conditions assessments.
Note: The intro sentence "On any given day, you may be called on to:" is not needed as separate; we can drop it as it's just intro. Now Requirements:

Requirements

  • A Bachelor's degree plus 5 years of relevant experience OR an equivalent combination of education and experience
  • Ability to obtain a Department of Energy Q-level clearance
Qualifications (desired):

Qualifications

  • Master of Business Administration OR an advanced technical degree in a discipline relevant to the organization
  • Knowledge and expertise in manufacturing operations and asset management
  • Experience with Oracle E-business Suite, Confluence, WordPress, Power BI, ServiceNow, Microsoft Project, and Microsoft Office, especially Excel and PowerPoint
  • Ability to effectively communicate (oral and written) across organizational boundaries with both technical staff and management
  • Demonstrated ability to successfully manage and complete competing programs and projects
  • Demonstrated ability to support multidisciplinary teams
  • Ability to organize, prioritize, and execute in a dynamic, high-pressure, schedule driven environment
  • Excellent customer service skills
  • Ability to work as part of a team
Benefits: we already included some benefits in About the role; but we also have a Benefits section maybe we can include the specific benefits list: "Generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance and amenities aimed at creating a solid work/life balance". Also flexible work arrangements. However we already put flexible work arrangements in About the role. To avoid duplication, maybe we move benefits to Benefits section and keep About the role just company description without benefits. Let's re-evaluate. We need to preserve all substantive info. If we put benefits in About the role, we still have them. But we also need a Benefits section if we want to follow heading list. However we could omit Benefits section if we already covered benefits elsewhere? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't say we must include all headings; we can

Similar jobs