Technician- Automation I USA (D Crew)
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when posting has real specific content.
Let's parse the job description.
We have:
- Basic Job Functions: description of role, entry level Automation Technician controls position, support manufacturing, assist equipment implementation/startup, PLC/HMI programming, trouble-shooting/optimization, assigned to manufacturing schedule on a PM shift 6:00PM - 6:10AM, rotating 36/48 hour work week schedule, includes working every other Friday, Saturday and Sunday.
- Education/Experience: Minimum 2 years of manufacturing equipment electrical/electronic/controls experience. Associate/Bachelor’s degree in Electrical, Robotics, Industrial Controls, or Electronic Engineering (preferred). No Degree - Must have 5+ years verifiable experience in a related field, (i.e., Semiconductors, Automotive etc.).
- Required Skills/Competencies: list many bullet points.
- Essential Responsibilities: Primary Responsibilities: list many bullet points (some long). Then "Key Competencies:" with many bullet points (looks like generic competency framework). Then "Other duties as assigned." "Job description subject to change at any time."
- Reporting Relationships: This position will not have direct reports
- Travel: No travel is required.
- Estimated Salary Range: $26.97 - $38.97 Hourly US
- Physical Requirements: list many.
- Then other statements about background check, EEO statement.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO statement at end, also maybe "All candidates receiving an offer..." etc. Also "Job description subject to change at any time." maybe keep? It's not boilerplate but could be considered generic; but it's substantive? It's a statement about change; maybe we can keep but it's not a heading. We'll keep as a paragraph under maybe "About the role" or separate? The instruction: "Prefer a few substantive sections over many thin ones." So we can combine.
We need sections: About the role (maybe from Basic Job Functions). Responsibilities (from Essential Responsibilities). Requirements (Education/Experience). Skills (Required Skills/Competencies). Pay (Estimated Salary Range). Schedule (shift info). Benefits? Not mentioned. So we omit Benefits.
Physical Requirements maybe could be part of Requirements or a separate section? Not in list of allowed headings; but we could put under Requirements or maybe under "Qualifications"? The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Qualifications for education/experience. Requirements could be for skills? But we have both Skills and Requirements. Let's map:
- About the role: basic job functions description.
- Responsibilities: Essential Responsibilities (Primary Responsibilities) maybe also Key Competencies? But Key Competencies is a long list of generic competencies; could be considered part of Responsibilities or Skills. Might be too thin; but we can include as part of Responsibilities.
- Requirements: Education/Experience.
- Skills: Required Skills/Competencies.
- Pay: Estimated Salary Range.
- Schedule: shift info (PM shift 6:00PM - 6:10AM, rotating 36/48 hour work week, includes every other Fri/Sat/Sun).
We should not include sections with filler like "commensurate with experience". We have actual numbers for pay, schedule.
We need to output HTML fragment only, no /. Use for headings, - for lists,
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from those sections.
We need to be careful not to miss any details.
Let's extract content.
**About the role** (Basic Job Functions):
"The following is an entry level Automation Technician controls position where a successful candidate will be required to support manufacturing operations, assist with equipment implementation/startup, PLC/HMI programing, and trouble-shooting/optimization of manufacturing processes control systems. This position directly supports a manufacturing site, the successful candidate will be assigned to a manufacturing schedule on a PM shift is 6:00PM - 6:10AM. This results in a rotating 36/48 hour work week schedule, which includes working every other Friday, Saturday and Sunday."
We need to preserve that exactly? Slight punctuation: "PLC/HMI programing" maybe typo but keep. Also "programing" vs "programming". Keep as is.
We could split into sentences but keep as paragraph.
**Responsibilities** (Essential Responsibilities: Primary Responsibilities: list). Let's list each bullet.
From text:
"Primary Responsibilities:
Responsible for support of manufacturing facilities, including remote support of world-wide manufacturing facilities.
Responsible to troubleshoot, repair, problem-solve, and maintain all electrical control systems for manufacturing equipment.
Responsible to assist with coordination of new equipment installation and implementation; including of MES integration events.
Responsible for maintaining and updating of manufacturing process tool electrical drawings, ensuring the tracking of equipment changes is documented and drawings are kept current.
Responsible to implement new software changes/upgrades specified by the Controls Engineering Department
Responsible to identify, research, document and present solutions to control problems and continuous improvement projects
Responsible to interface with multiple departments within the organization.
Maintain effective communications levels and fosters team building.
Ensures adherence to all safety procedures and good housekeeping standards."
Then after that there is "Key Competencies:" with many bullet points. Those are also responsibilities? They seem like generic competency statements. We could include them under Responsibilities as well, but they are lengthy. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Key Competencies into Responsibilities section as a list.
We need to preserve all substantive information. So we should include those bullet points as well.
Let's extract Key Competencies bullet points:
"Takes responsibility for understanding client requirements, collecting data, delivering analysis and problem resolution. Identifies, evaluates and recommends options, implementing if required. Collaborates with, and facilitates stakeholder groups, as part of formal or informal consultancy agreements. Seeks to fully address client needs, enhancing the capabilities and effectiveness of client personnel, by ensuring that proposed solutions are properly understood and appropriately exploited.
Maintains awareness of opportunities provided by new technology to address challenges or to enable new ways of working. Within own sphere of influence, works to further organizational goals, by the use of emerging technologies and products. Contributes to briefings and presentations about their relevance and potential value to the organization.
Assists with the collection of safety assurance evidence, undertaking all work in accordance with agreed safety, technical and quality standards, using appropriate methods and tools. Documents the results of hazard and risk analysis activities.
Investigates and recommends components and subsystems that meet sustainability criteria.
Performs, analyses and documents evaluations according to a plan, excluding expert reviews.
Configures software and equipment and tests platform-specific versions of one or more software products. Reports the outcome of testing and identifies potential improvements to the process and to the software products according to agreed designs and standards.
Uses system management software and tools to collect agreed performance statistics. Carries out agreed system software maintenance tasks.
Identifies and resolves issues with applications, following agreed procedures. Uses application management software and tools to collect agreed performance statistics. Carries out agreed applications maintenance tasks.
Carries out agreed operational procedures of a routine nature. Contributes to maintenance, installation, and problem resolution.
Identifies and resolves network problems following agreed procedures. Uses network management software and tools to collect agreed performance statistics. Carries out agreed network maintenance tasks.
Initiates and monitors actions to investigate and resolve problems in systems and services. Assists with the implementation of agreed remedies and preventative measures.
Receives and handles requests for support following agreed procedures. Responds to requests for support by providing information to enable incident resolution and promptly allocates unresolved calls as appropriate. Maintains records and advises relevant persons of actions taken."
That's a lot. We'll keep them as list items.
**Requirements** (Education/Experience):
"Minimum 2 years of manufacturing equipment electrical/electronic/controls experience.Associate/Bachelor’s degree in Electrical, Robotics, Industrial Controls, or Electronic Engineering (preferred)No Degree - Must have 5+ years verifiable experience in a related field, (i.e., Semiconductors, Automotive etc.)."
We need to preserve spacing? We'll make a paragraph.
**Skills** (Required Skills/Competencies): list many bullet points.
Let's extract:
"Ability to work independently, manage multiple tasks and set priorities.
Ability to interpret data and make reasonable conclusions to assist in trouble-shooting process.
Good understanding/knowledge of reading electrical/mechanical drawings and suggest modifications as required.
Good understanding/knowledge of manufacturing processes and safety requirements.
Demonstrated proficiency and problem solving ability to trouble-shoot electrical/electronic control systems in manufacturing environment.
Competent in Autodesk AutoCAD drafting software to create electrical schematic and panel layouts.
Good understanding/knowledge programming/trouble-shooting of Rockwell Automation Logix platform PLC’s.
Good understanding/knowledge programming/trouble-shooting Rockwell Automation Human Machine Interfaces (HMI) utilizing FactoryTalk View ME; Proface HMI experience a plus.
Good understanding trouble-shooting at least two control network including ControlNet, DeviceNet, Profibus and/or Ethernet.
Basic understanding/knowledge of robotic systems including trouble-shooting, programming, safety.
Good understanding of computer hardware/applications and the Microsoft Office family.
Basic understanding of corporate Ethernet architectures and systems.
Proficient communications skills both verbal and written.
Basic understanding of SQL Database tables/queries.
Basic understanding of data collection processes and OPC protocols."
We'll keep as list.
**Pay**: "Estimated Salary Range: $26.97 - $38.97 Hourly US"
**Schedule**: from Basic Job Functions: "This position directly supports a manufacturing site, the successful candidate will be assigned to a manufacturing schedule on a PM shift is 6:00PM - 6:10AM. This results in a rotating 36/48 hour work week schedule, which includes working every other Friday, Saturday and Sunday."
We could extract schedule details: PM shift 6:00PM - 6:10AM, rotating 36/48 hour work week, includes every other Friday, Saturday and Sunday.
We'll put as paragraph.
We should not include sections like Benefits (none). Also we should not include Travel, Physical Requirements, Reporting Relationships, etc. Those are not in allowed headings; but we could possibly include them under Requirements or About the role? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples but we can use others? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not create headings for Travel, Physical Requirements, etc. We should incorporate that info elsewhere if possible, or drop it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot drop Physical Requirements etc. We need to include them somewhere. But we cannot create new headings outside the allowed list? The examples are not exhaustive; they say e.g., meaning for example. So we could use other headings if needed, but they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings where appropriate
- for lists,
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from those sections. We need to be careful not to miss any details. Let's extract content. **About the role** (Basic Job Functions): "The following is an entry level Automation Technician controls position where a successful candidate will be required to support manufacturing operations, assist with equipment implementation/startup, PLC/HMI programing, and trouble-shooting/optimization of manufacturing processes control systems. This position directly supports a manufacturing site, the successful candidate will be assigned to a manufacturing schedule on a PM shift is 6:00PM - 6:10AM. This results in a rotating 36/48 hour work week schedule, which includes working every other Friday, Saturday and Sunday." We need to preserve that exactly? Slight punctuation: "PLC/HMI programing" maybe typo but keep. Also "programing" vs "programming". Keep as is. We could split into sentences but keep as paragraph. **Responsibilities** (Essential Responsibilities: Primary Responsibilities: list). Let's list each bullet. From text: "Primary Responsibilities: Responsible for support of manufacturing facilities, including remote support of world-wide manufacturing facilities. Responsible to troubleshoot, repair, problem-solve, and maintain all electrical control systems for manufacturing equipment. Responsible to assist with coordination of new equipment installation and implementation; including of MES integration events. Responsible for maintaining and updating of manufacturing process tool electrical drawings, ensuring the tracking of equipment changes is documented and drawings are kept current. Responsible to implement new software changes/upgrades specified by the Controls Engineering Department Responsible to identify, research, document and present solutions to control problems and continuous improvement projects Responsible to interface with multiple departments within the organization. Maintain effective communications levels and fosters team building. Ensures adherence to all safety procedures and good housekeeping standards." Then after that there is "Key Competencies:" with many bullet points. Those are also responsibilities? They seem like generic competency statements. We could include them under Responsibilities as well, but they are lengthy. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Key Competencies into Responsibilities section as a list. We need to preserve all substantive information. So we should include those bullet points as well. Let's extract Key Competencies bullet points: "Takes responsibility for understanding client requirements, collecting data, delivering analysis and problem resolution. Identifies, evaluates and recommends options, implementing if required. Collaborates with, and facilitates stakeholder groups, as part of formal or informal consultancy agreements. Seeks to fully address client needs, enhancing the capabilities and effectiveness of client personnel, by ensuring that proposed solutions are properly understood and appropriately exploited. Maintains awareness of opportunities provided by new technology to address challenges or to enable new ways of working. Within own sphere of influence, works to further organizational goals, by the use of emerging technologies and products. Contributes to briefings and presentations about their relevance and potential value to the organization. Assists with the collection of safety assurance evidence, undertaking all work in accordance with agreed safety, technical and quality standards, using appropriate methods and tools. Documents the results of hazard and risk analysis activities. Investigates and recommends components and subsystems that meet sustainability criteria. Performs, analyses and documents evaluations according to a plan, excluding expert reviews. Configures software and equipment and tests platform-specific versions of one or more software products. Reports the outcome of testing and identifies potential improvements to the process and to the software products according to agreed designs and standards. Uses system management software and tools to collect agreed performance statistics. Carries out agreed system software maintenance tasks. Identifies and resolves issues with applications, following agreed procedures. Uses application management software and tools to collect agreed performance statistics. Carries out agreed applications maintenance tasks. Carries out agreed operational procedures of a routine nature. Contributes to maintenance, installation, and problem resolution. Identifies and resolves network problems following agreed procedures. Uses network management software and tools to collect agreed performance statistics. Carries out agreed network maintenance tasks. Initiates and monitors actions to investigate and resolve problems in systems and services. Assists with the implementation of agreed remedies and preventative measures. Receives and handles requests for support following agreed procedures. Responds to requests for support by providing information to enable incident resolution and promptly allocates unresolved calls as appropriate. Maintains records and advises relevant persons of actions taken." That's a lot. We'll keep them as list items. **Requirements** (Education/Experience): "Minimum 2 years of manufacturing equipment electrical/electronic/controls experience.Associate/Bachelor’s degree in Electrical, Robotics, Industrial Controls, or Electronic Engineering (preferred)No Degree - Must have 5+ years verifiable experience in a related field, (i.e., Semiconductors, Automotive etc.)." We need to preserve spacing? We'll make a paragraph. **Skills** (Required Skills/Competencies): list many bullet points. Let's extract: "Ability to work independently, manage multiple tasks and set priorities. Ability to interpret data and make reasonable conclusions to assist in trouble-shooting process. Good understanding/knowledge of reading electrical/mechanical drawings and suggest modifications as required. Good understanding/knowledge of manufacturing processes and safety requirements. Demonstrated proficiency and problem solving ability to trouble-shoot electrical/electronic control systems in manufacturing environment. Competent in Autodesk AutoCAD drafting software to create electrical schematic and panel layouts. Good understanding/knowledge programming/trouble-shooting of Rockwell Automation Logix platform PLC’s. Good understanding/knowledge programming/trouble-shooting Rockwell Automation Human Machine Interfaces (HMI) utilizing FactoryTalk View ME; Proface HMI experience a plus. Good understanding trouble-shooting at least two control network including ControlNet, DeviceNet, Profibus and/or Ethernet. Basic understanding/knowledge of robotic systems including trouble-shooting, programming, safety. Good understanding of computer hardware/applications and the Microsoft Office family. Basic understanding of corporate Ethernet architectures and systems. Proficient communications skills both verbal and written. Basic understanding of SQL Database tables/queries. Basic understanding of data collection processes and OPC protocols." We'll keep as list. **Pay**: "Estimated Salary Range: $26.97 - $38.97 Hourly US" **Schedule**: from Basic Job Functions: "This position directly supports a manufacturing site, the successful candidate will be assigned to a manufacturing schedule on a PM shift is 6:00PM - 6:10AM. This results in a rotating 36/48 hour work week schedule, which includes working every other Friday, Saturday and Sunday." We could extract schedule details: PM shift 6:00PM - 6:10AM, rotating 36/48 hour work week, includes every other Friday, Saturday and Sunday. We'll put as paragraph. We should not include sections like Benefits (none). Also we should not include Travel, Physical Requirements, Reporting Relationships, etc. Those are not in allowed headings; but we could possibly include them under Requirements or About the role? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples but we can use others? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not create headings for Travel, Physical Requirements, etc. We should incorporate that info elsewhere if possible, or drop it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot drop Physical Requirements etc. We need to include them somewhere. But we cannot create new headings outside the allowed list? The examples are not exhaustive; they say e.g., meaning for example. So we could use other headings if needed, but they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings where appropriate