PLM Application Administrator

We need to output HTML fragment with sections: About the role? The posting includes a Position Summary, Responsibilities, Qualifications, Work Environment, Benefits. Also maybe "Employment Type", "Shift", "Work Status" are metadata; we should fold minor metadata into a short

or drop it. 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 paragraph with Employment Type, Shift, Work Status maybe. We must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. So we can have sections: Position Summary (maybe as About the role), Responsibilities, Qualifications, Work Environment, Benefits. Possibly also Skills? The qualifications include required and preferred; we could put under Qualifications. Skills maybe not separate. We must not create Pay/Schedule/Benefits unless posting actually states them. Benefits is stated, so include Benefits section. Pay not mentioned, so omit. Schedule not mentioned (though shift is 1st Shift, but that's maybe schedule? It says Shift: 1st Shift. That could be considered schedule info. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Shift is specific: 1st Shift. Should we create a Schedule section? The allowed headings include Schedule. Could we put shift info under Schedule? The posting says Shift: 1st Shift. That's a schedule detail. We could include a Schedule section with that info. However we also have Work Status: Hybrid. That could be under Schedule or maybe Work Environment? Probably schedule. But we need to decide. We must not invent or summarize away detail. So we need to preserve all substantive information. If we put shift info in a Schedule section, we need to include that detail. Also Work Status hybrid could be part of Schedule or maybe Work Environment? The posting includes "Work Status: Hybrid". That's about remote work. Could be part of Schedule or maybe a separate section like Work Arrangement but not in allowed headings. Since allowed headings include Schedule, we could put both Shift and Work Status there. But we also have Work Environment section describing office environment, occasional exposure, safety gear, ability to work from home up to 2X/week. That's also work environment details. So we could have Work Environment section for that. Thus we could have Schedule section for Shift and Work Status. However the instruction: Prefer a few substantive sections over many thin ones. Having both Schedule and Work Environment may be okay. We need to use

• for any list of duties/requirements/benefits. So Responsibilities list, Qualifications list (maybe split required and preferred), Benefits list. We need to use

  for prose. We must not include boilerplate like EEO etc. The posting ends with "#TacoComfortSolutions" maybe a tag; we can drop. Let's craft:

  About the role

  Position Summary: The PLM Application Administrator is responsible for the system configuration, reporting and data integrity of the product lifecycle management (PLM) / product data management (PDM) system. The role involves implementation of system enhancements including workflows, reports, dashboards, and interfaces for PLM, enterprise resource planning (ERP) and computer-aided design (CAD). They are responsible for procedures and continuous improvement of the PLM system. Measures of success: Create and update workflows and reports using the PLM program, meeting project schedule targets.Maintain operational readiness of the PLM system and integration with ERP and other programs.Develop training plans and conduct training for PLM usersManage feature integration projects for PLM system, meeting schedule and budget targets, including overseeing the deliverables of contractors and partners.

  But we could also keep Position Summary as prose. Then Responsibilities:

  Responsibilities

  • ... each bullet. We need to preserve all responsibilities text. The responsibilities paragraph is long with many sentences separated by periods. We'll split into list items each sentence or clause. Must not invent or summarize. We'll break at each sentence. Let's extract responsibilities sentences: "Administers, configures, and maintains the PLM system to support engineering and manufacturing processes." "Creates and implements workflows and forms within the PLM system." "Develops PLM system programming and code with high quality and performance." "Responsible for general data management within the PLM System and related business processes. Creates item types. Defines properties, relationships, and lifecycles." "Responsible for all day-to-day PLM activities. Oversees product data management tools, and all upgrades and future PLM modules and software integrations." "Supports all PLM users. Develops and conducts ongoing training for end users and critical stakeholders. Creates user guides and helps facilitate PLM tasks across functional departments." "Administers user roles, profiles, permissions, and group identities." "Supports the PLM implementation team that consists of internal business teams from Research and Development, Quality, Purchasing, Supply Chain, Operations, IT, and external consultants." "Serves as the primary point person between engineering and other key system stakeholders to ensure proper integration with the enterprise resource planning (ERP) and manufacturing execution system (MES). Coordinates UAT events." "Performs root cause analysis of software defects in the PLM environment and works with the appropriate technical teams to develop, test, and implement fixes to prevent recurrence." "Identifies, designs, and implements reports and analytics within the PLM System." "Identifies improvement opportunities based on the company's business needs and attains relevant stakeholder input. Maintains knowledge of emerging technologies and applicability related to PLM software. Follows best practices, standards, and documentation for PLM software usage." "Performs other duties as assigned." We need to ensure each bullet is a complete sentence; we can combine some. Now Qualifications: Required and Preferred. We'll have

    Qualifications

    maybe split into Required and Preferred as subheadings? But only allowed headings are the list; we could still use

    for Qualifications and then inside have

    for required and

    for list? But we need to use
    • for any list of duties/requirements/benefits. So qualifications list should be
      . We'll separate required and preferred maybe as two
      with headings

      or . But we cannot add extra headings not in list? The instruction only says use

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

      for section headings (list). Likely we should only use those headings for sections. Inside we can use

      and

      . For required vs preferred we could use

      with bold text. Thus:

      Qualifications

      Required:

      • Bachelor's degree in Computer Science, Information Technology, Engineering or related discipline; significant applicable experience may be accepted in lieu of degree
      • 5+ years of PLM administration experience
      • Proficient in C, C#, .NET, Perl, JavaScript scripting, jQuery, XML/AML, ASP.NET, HTML5 and SQL
      • Knowledgeable in SQL Server Administration
      • Proficient in Microsoft Office (Word, Excel, Teams, PowerPoint, etc.)
      • Knowledge of ERP systems and Engineering Change process
      • Excellent communication skills with the ability to interact with employees in a clear manner
      • Ability to work in teams

      Preferred:

      • Hands-on experience with Aras PLM Innovator performing configuration and customization integrations at the enterprise level
      Now Work Environment: we have a paragraph. Use

      Work Environment

      maybe not in allowed list but it's similar to "Work Environment" not listed. Allowed headings list includes "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". Work Environment is not listed. Should we avoid using it? The instruction: Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning examples, not exhaustive? It might be okay to use other headings but they gave examples. Safer to stick to those headings. We could incorporate work environment details into About the role or Responsibilities? But it's distinct. Could we put under "About the role"? Might be okay. However we need to preserve all substantive information. We could add a

      after About the role describing work environment. Or we could create a section "Work Environment" using

      even if not in list; risk of being considered not following instruction. The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the allowed headings; we should not invent others. So we should avoid Work Environment heading. Instead we can fold that info into About the role or Responsibilities? Probably About the role is appropriate: we can add a paragraph about work environment after the position summary. Similarly, Schedule: we have Shift and Work Status. We can create a Schedule section (allowed). We'll include shift and work status details. Benefits: allowed. Thus final sections: About the role (includes position summary and work environment), Responsibilities, Qualifications, Schedule, Benefits. We must not repeat job title as heading. Good. Now ensure we don't include any boilerplate like "#TacoComfortSolutions". Remove. Now craft HTML. Let's write:

      About the role

      Position Summary: The PLM Application Administrator is responsible for the system configuration, reporting and data integrity of the product lifecycle management (PLM) / product data management (PDM) system. The role involves implementation of system enhancements including workflows, reports, dashboards, and interfaces for PLM, enterprise resource planning (ERP) and computer-aided design (CAD). They are responsible for procedures and continuous improvement of the PLM system. Measures of success: Create and update workflows and reports using the PLM program, meeting project schedule targets.Maintain operational readiness of the PLM system and integration with ERP and other programs.Develop training plans and conduct training for PLM usersManage feature integration projects for PLM system, meeting schedule and budget targets, including overseeing the deliverables of contractors and partners.

      Work Environment: This position works primarily in an office environment using computers and technology. Verbal and auditory capability are required. Occasional exposure in production plant where large equipment and noise are prevalent. Safety gear is required in these areas. This position may work from home up to 2X/week if performance is in good standing. This position has no direct reports.

      Now Responsibilities list. Then Qualifications. Then Schedule:

      Schedule

      Shift: 1st Shift. Work Status: Hybrid.

      Then Benefits:

      Benefits

      ... each bullet from benefits paragraph. Benefits paragraph: "With nearly 1,000 people working at Taco worldwide, each with their own story, you will discover a sense of community and diverse, intelligent colleagues who help us innovate, create and explore. Taco employees benefit from a company that: Provides competitive salaries and benefitsOffers tuition reimbursement, career development, and on-site training programs in our learning centerBelieves in sharing profits with its employeesIs mindful about family, health and well-beingFosters conditions that allow people and communities