PLM/PDM System Analyst II

We need to produce HTML fragment with sections: Overview (maybe not a heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. The posting includes Overview, Responsibilities, Job Summary, Essential Duties, Personal Protective Equipment (PPE) Requirements, Qualifications (with subparts), Benefits & Perks, Where You'll Be, Who We Are, etc. We need to include sections only when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove things like "Check out the job description and apply now!" etc. Also remove the YouTube link? It's part of Responsibilities? Actually the line: "PLM/PDM Systems Analyst II https://www.youtube.com/watch?v=0tMgKm_71qs (by clicking this link you are being referred to an external site that is not part of Panasonic)" This seems like a stray link; we should remove it as it's not substantive? It's not part of job description; it's a link to a video. Probably remove. We need to keep: Overview paragraph(s), Responsibilities (list), Job Summary (maybe part of Overview?), Essential Duties (list), PPE Requirements (maybe a subsection under Responsibilities? Could be its own section? The instruction: include a section only when posting has real specific content for it. PPE Requirements is specific content, so we could include a section heading maybe "Personal Protective Equipment (PPE) Requirements". However the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It 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 as examples. Probably we should stick to those headings where applicable. PPE could be part of Responsibilities or Requirements? It's a requirement. Could be under Requirements. But we have a Qualifications section for education/experience. PPE is more like a requirement (safety). Could be under Requirements. However the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings. We need to map content. We have Overview: introductory paragraphs. Could be under About the role? Or we could just put Overview as a

without heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must have those exact headings, but we should use them for sections. Probably we should create sections: About the role (overview), Responsibilities, Requirements (maybe includes PPE?), Qualifications (education/experience), Benefits, maybe Skills? There's a Skills list in Qualifications (communication, etc). Could be under Skills section. But we have Qualifications already covering education/experience and also skills. Might split: Qualifications for education/experience, Skills for technical/soft skills. However the instruction says prefer a few substantive sections over many thin ones. So maybe combine. Let's decide sections: - About the role (overview paragraph(s)) - Responsibilities (list of duties) - Requirements (includes education, experience, PPE? maybe separate) - Qualifications (maybe same as Requirements? Could combine) But we need to avoid duplication. Better: Use sections: About the role, Responsibilities, Qualifications, Benefits. Also maybe Skills? But Qualifications can contain both education/experience and skills. Let's extract content: Overview paragraphs: "Do you want to join a team that's changing the world? Do you have a strong background as a PLM/PDM System Analyst? Then we're looking for you! Check out the job description and apply now! Put your skills to meaningful use, gain unique experience, and work with world-class team members with diverse backgrounds and expertise who share the same vision. Join the PECNA team today!" We should remove "Check out the job description and apply now!" and "Join the PECNA team today!" maybe as application instructions? It's a call to apply. According to instruction: remove application instructions. So we should remove those sentences. Keep the rest: "Do you want to join a team that's changing the world? Do you have a strong background as a PLM/PDM System Analyst? Then we're looking for you! Put your skills to meaningful use, gain unique experience, and work with world-class team members with diverse backgrounds and expertise who share the same vision." But "Then we're looking for you!" is also a call to action; maybe remove. Keep only descriptive: "Do you want to join a team that's changing the world? Do you have a strong background as a PLM/PDM System Analyst? Put your skills to meaningful use, gain unique experience, and work with world-class team members with diverse backgrounds and expertise who share the same vision." That seems okay. Responsibilities: The posting includes a heading "Responsibilities" then a link line (remove), then "Meet the Recruiter: Danielle Lomeli" (maybe metadata, remove). Then "Job Summary" paragraph. Then "Essential Duties" list (bullet points). Also there are other responsibilities like "Provides periodic operational support and maintenance". Actually the Job Summary includes some responsibilities. We need to preserve all substantive info. So we should combine Job Summary and Essential Duties into a list under Responsibilities. Let's extract Job Summary paragraph: "In this role, the PLM/PDM Systems Analyst will serve as a technical expert in the areas of infrastructure related to Product Lifecycle Management and integration to factory systems. The Engineer will identify methods and architect solutions to provide a high level of service to end-users of the application(s). This role will help build out, maintain, and troubleshoot a rapidly expanding application system and its infrastructure. The Analyst will work closely with other engineers and leadership to obtain regular feedback on design and execution. Additionally, the Analyst will provide periodic operational support and maintenance of the PLM/PDM systems." That's prose; we can keep as

under Responsibilities. Then Essential Duties list (each bullet). We need to preserve each bullet as

. List items: - Responsible for the maintenance, optimization, troubleshooting, upgrades, installation, and documentation of infrastructure related to Product Lifecycle Management (PLM) systems which includes PLM database management, project management systems, CAD and PDM systems - Administration of new and existing technologies, including the design, documentation, install, configuration, maintenance, integration, and testing related systems - Works collaboratively with business users on hardware, middleware, and application requirements - Collaborate with vendors, engineers, analysts, and leadership to ensure the integrity of databases, application software and data - Performs regular system monitoring, verifying the integrity, health and availability of all systems and key processes, reviewing application and system logs, and ensuring completion of scheduled jobs - Leads problem-solving efforts regarding system and service matters and if necessary, facilitates support with outside personnel, organizations, and/or vendors - Monitor tech-industry trends, and brings new ideas and innovative solutions - Develop new deliverables as needed based on operational requirements and following best practices for documentation and delivery - Perform hardware and application troubleshooting as related to manufacturing process - Configure and deploy devices and peripherals as necessary - Resolves issues, problems and questions on-site assigned from a ticketing system - Ensure compliance to all Panasonic policy and procedures Also there is a line: "The foregoing description is not intended and should not be construed to be an exhaustive list of all responsibilities, skills and efforts or work conditions associated with the job. It is intended to be an accurate reflection of the general nature and level of the job." This is boilerplate; remove. Now PPE Requirements: It's a subsection under Responsibilities? It says "Personal Protective Equipment (PPE) Requirements To ensure the health and safety in the workplace and for the protection of our employees, wearing PPE is a requirement for some roles at PECNA and may include equipment such as a full Tyvek suit, safety shoes, gloves, safety glasses, face mask, bump cap, and a full hazmat suit that includes a respirator. The foregoing description is not intended and should not be construed to be an exhaustive list of all responsibilities, skills and efforts or work conditions associated with the job. It is intended to be an accurate reflection of the general nature and level of the job." We should keep the PPE description (list of equipment). Remove the boilerplate sentence at end. So we could include PPE as part of Responsibilities or as its own section? Since we have limited headings, maybe we can include a subsection under Responsibilities as a

after the list. Or we could create a separate section "Requirements" for PPE. But PPE is a requirement, not a qualification. Could be under Requirements. However we already might have a Requirements section for education/experience. Might be better to have a section "Requirements" that includes both education/experience and PPE? But the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a Requirements section. Let's put education/experience and maybe also PPE under Requirements? But PPE is more like a condition, not a qualification. However we can still put it there. Alternatively, we could have a section "Requirements" for education/experience, and a separate section "Skills" for technical/soft skills, and keep PPE under Responsibilities as a note. But we need to avoid many thin sections. Let's think: we have Overview, Responsibilities, Qualifications (education/experience), Benefits. That's four sections. Could add Skills if we want to separate soft skills. But we can incorporate skills into Qualifications. Thus we will have:

About the role

Do you want to join a team that's changing the world? Do you have a strong background as a PLM/PDM System Analyst? Put your skills to meaningful use, gain unique experience, and work with world-class team members with diverse backgrounds and expertise who share the same vision.

Responsibilities

In this role, the PLM/PDM Systems Analyst will serve as a technical expert in the areas of infrastructure related to Product Lifecycle Management and integration to factory systems. The Engineer will identify methods and architect solutions to provide a high level of service to end-users of the application(s). This role will help build out, maintain, and troubleshoot a rapidly expanding application system and its infrastructure. The Analyst will work closely with other engineers and leadership to obtain regular feedback on design and execution. Additionally, the Analyst will provide periodic operational support and maintenance of the PLM/PDM systems.

• Responsible for the maintenance, optimization, troubleshooting, upgrades, installation, and documentation of infrastructure related to Product Lifecycle Management (PLM) systems which includes PLM database management, project management systems, CAD and PDM systems
• Administration of new and existing technologies, including the design, documentation, install, configuration, maintenance, integration, and testing related systems
• Works collaboratively with business users on hardware, middleware, and application requirements
• Collaborate with vendors, engineers, analysts, and leadership to ensure the integrity of databases, application software and data
• Performs regular system monitoring, verifying the integrity, health and availability of all systems and key processes, reviewing application and system logs, and ensuring completion of scheduled jobs
• Leads problem-solving efforts regarding system and service matters and if necessary, facilitates support with outside personnel, organizations, and/or vendors
• Monitor