Shipboard Controls Technician

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes responsibilities, required qualifications, desired qualifications, physical requirements, overview, why work at Noblis, total rewards, compensation (salary range). Also schedule info: typical schedule 10-hour days Mon-Fri, 8-hour Sat, overtime straight time, may shift. So we have schedule content. Pay: posted salary range. Benefits: total rewards section mentions health, life, disability, financial, retirement benefits, paid leave, professional development, tuition assistance, work-life programs. So we can include Benefits section. Also maybe "About the role" could be overview? The posting includes mission description at start: "Noblis MSD's mission is to support...". That could be About the role. Also there is an Overview section about Noblis. Could combine. But we need to avoid duplication. We'll create sections: About the role (mission description), Responsibilities, Requirements (maybe combine required qualifications?), Qualifications (desired qualifications?), Skills (maybe desired qualifications?), Benefits, Pay, Schedule. Must not repeat job title. Must not include boilerplate like EEO, legal, etc. Remove navigation, cookie, etc. Also remove duplicated lines. Must preserve all substantive info. We need to decide what goes where. Let's extract substantive content: - Mission/support description: "Noblis MSD's mission is to support the Naval Sea Systems Command (NAVSEA) and Naval Surface Warfare Center Philadelphia Division (NSWCPD) in enabling research, development, test and evaluation, acquisition, engineering, systems integration, in-service support, and fleet engineering with cybersecurity, comprehensive logistics, and life-cycle savings. We are seeking an Engineering Technician based in Norfolk, Virginia, to support U.S. Navy machinery control and shipboard systems for Arleigh Burke-class destroyers. The candidate will provide waterfront support for the installation, checkout, troubleshooting, testing, and verification and validation (V&V) of modernized Machinery Control Systems (MCS). This is a primarily onsite position supporting work aboard ships and at shipyards and naval stations. When the employee is not aboard ship, the waterfront work environment may include shared trailer workspace. This is not a remote position, although limited remote work during ship-installation downtime may be approved on a case-by-case basis. During active ship availabilities, the typical schedule is 10-hour days Monday through Friday and an 8-hour day on Saturday. Hours worked beyond the standard 40-hour workweek are compensated at straight time. Work schedules may shift based on ship installation and test requirements." That includes schedule info; we might separate schedule later. - Principal Duties And Responsibilities list (bulleted). We'll put under Responsibilities. - Required Qualifications: list. - Physical Requirements: list. - Desired Qualifications: list. - Overview about Noblis: maybe "About the company" but not required. Could be omitted if not needed. But we have "Overview" and "Why Work at Noblis" and "Total Rewards". Those contain substantive info about benefits, culture. We'll include Benefits section from Total Rewards. Also maybe "About the role" could be the mission description. - Pay: posted salary range. - Schedule: we have schedule details. We must not create sections with filler like "commensurate with experience". We have actual schedule and pay. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Not include Job ID. We must output only HTML fragment. Let's structure:

  About the role

  Noblis MSD's mission is to support the Naval Sea Systems Command (NAVSEA) and Naval Surface Warfare Center Philadelphia Division (NSWCPD) in enabling research, development, test and evaluation, acquisition, engineering, systems integration, in-service support, and fleet engineering with cybersecurity, comprehensive logistics, and life-cycle savings. We are seeking an Engineering Technician based in Norfolk, Virginia, to support U.S. Navy machinery control and shipboard systems for Arleigh Burke-class destroyers. The candidate will provide waterfront support for the installation, checkout, troubleshooting, testing, and verification and validation (V&V) of modernized Machinery Control Systems (MCS). This is a primarily onsite position supporting work aboard ships and at shipyards and naval stations. When the employee is not aboard ship, the waterfront work environment may include shared trailer workspace. This is not a remote position, although limited remote work during ship-installation downtime may be approved on a case-by-case basis.

  Then schedule maybe separate.

  Responsibilities

  • Troubleshoot machinery control systems using test equipment, system documentation, and electrical schematics.
  • Provide shipboard test and V&V support for all variants of fielded systems.
  • Support shipboard installation, checkout, and testing of MCS software and hardware.
  • Trace signals and diagnose or isolate electrical failures and system anomalies.
  • Use electrical and diagnostic test equipment, including digital multimeters, oscilloscopes, and signal generators, to support system testing and troubleshooting.
  • Develop, edit, review, and implement test procedures and other technical documentation.
  • Review technical documentation for fielded and future system configurations.
  • Provide clear, documented status updates and maintain accurate records of testing, troubleshooting actions, and findings.
  • Act as a liaison between the Norfolk waterfront test team and technical leads in Philadelphia.
  • Provide field observations and technical input to support improvements to future MCS installations.
  • Participate in special projects and other program support activities as required.

  Requirements

  We could combine Required Qualifications and Physical Requirements? But better separate: Required Qualifications (education/experience/clearance etc.) and Physical Requirements. However we have only headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put Required Qualifications under Requirements, Desired Qualifications under Qualifications, and maybe Skills under Skills (some overlap). But we need to avoid thin sections. Let's think. We have Required Qualifications (Bachelors degree OR HS + 6 years experience, ability to read schematics, DoD Secret clearance, US citizenship, passport, ability to work onsite, extended hours, travel 30-50%). That's substantive. Physical Requirements is also substantive; could be part of Requirements or separate. But we have no heading for Physical Requirements; we could include under Requirements as a sublist? But we must use
  • for any list. Could embed two lists under Requirements heading: one for qualifications, one for physical. That's okay. Desired Qualifications list could go under Qualifications heading. Skills could be maybe derived from desired qualifications (experience with VME, PLC, etc.) but we already have desired qualifications. Could combine. But we must not create headings with filler. If we put Qualifications heading and put desired qualifications list, that's fine. If we also put Skills heading, we need content; maybe we can extract skills from desired qualifications: experience with VME, PLC, network troubleshooting tools, HyperTerminal, PuTTY, Wireshark, MS Office, technical writing, Navy shipboard experience, ability to work independently, etc. That's substantive. So we can have Skills section. Thus we have: - Requirements: Required Qualifications + Physical Requirements (maybe two lists) - Qualifications: Desired Qualifications - Skills: Specific skills list (maybe extracted from desired qualifications) But there is overlap; risk of duplication. Better to combine: Requirements = Required Qualifications; Qualifications = Desired Qualifications; Skills = maybe we can skip if too thin. But we have many desired qualifications that are skills; we could treat them as Skills and omit Qualifications heading. However the instructions say we can include sections only when posting has real specific content. It does have desired qualifications; we could put them under Qualifications. Skills could be omitted if we think it's redundant. But we have also "Experience tracing signals..." etc. Those are skills. Could be under Skills. Let's decide: We'll have: - About the role - Responsibilities - Requirements (Required Qualifications + Physical Requirements) - Qualifications (Desired Qualifications) - Benefits - Pay - Schedule That seems reasonable. Skills omitted. Now we need to format lists. For Requirements: we need two lists? Could combine into one list with items covering both qualification and physical. But that may mix categories. Better to have two separate lists under same heading, each preceded by a brief

    maybe. But instructions: Use

    • for any list of duties/requirements/benefits. It doesn't forbid multiple lists under same heading. So we can have:

      Requirements

      Required qualifications:

      ...

      Physical requirements:

      ...
      That's fine. Now Benefits: from Total Rewards: health, life, disability, financial, retirement benefits, paid leave, professional development, tuition assistance, work-life programs. Also award programs, etc. We'll capture. Pay: posted salary range: USD $53,280.00 - USD $83,320.00 /Yr. Schedule: typical schedule 10-hour days Mon-Fri, 8-hour Sat, overtime straight time, may shift. Now we must ensure we don't include boilerplate like EEO, legal, etc. Also remove duplicated lines. Also remove navigation etc. Now produce HTML. Let's craft. Check for any leftover boilerplate: The posting includes "Overview Overview Noblis and our wholly owned subsidiaries..." That's about company; we didn't include. That's okay. "Why Work at Noblis" also not included. "Total Rewards" we used for Benefits. "Commitment to Non-Discrimination" etc removed. Now ensure we preserve all substantive information: Did we miss any? Let's verify. From responsibilities list we captured all. From required qualifications: Bachelors degree OR HS + 6 years experience, ability to read schematics, DoD Secret clearance or ability to obtain, US citizenship, valid US passport or ability to obtain, ability to work primarily onsite in Norfolk, ability to work extended hours, off-hours, weekends, ability to travel approx 30-50% of time. Did we include all? We'll list. Physical requirements: we need to capture all points: standing/walking extended periods on uneven wet slippery surfaces, climb vertical ladders stairs steep inclines while carrying tools/equipment, work in confined spaces with limited ventilation/restricted movement including crawling through narrow passageways and working overhead or below-deck areas, manual dexterity/grip strength to operate hand/power tools, manipulate controls, handle materials up to 50 lbs regularly, occasional heavier with assistance, ability to bend stoop kneel crouch reach overhead repeatedly, adequate vision to read manuals identify color-coded systems detect safety hazards, hearing capability to perceive warning signals alarms verbal communications in noisy environments with or without hearing protection, work in varying environmental conditions extreme temps high humidity direct sunlight exposure to weather elements, stamina to work extended shifts, balance/coordination to maintain stability on moving vessels, capability to respond quickly to emergency situations including evacuating confined spaces moving to emergency stations, reasonable accommodations may be available. We'll include as list items. Desired qualifications list: Experience tracing signals and diagnosing or isolating cause of electrical failures and anomalies. Experience with grounded and ungrounded electrical systems. Knowledge of basic electrical principles (current, voltage, resistance) and application in circuit troubleshooting. Knowledge of fundamental concepts, practices, procedures associated with industrial control systems. Experience with VME systems. Experience with PLC systems. Basic knowledge of network troubleshooting tools and techniques. Experience using HyperTerminal, PuTTY, or equivalent serial interface. Experience using W