Operations Support Specialist, Lab Liaison

We need to output HTML fragment with sections: About the role? Actually the posting includes "Why Renovo?" intro, then "Summary:", then "What you will do:", then "Qualifications:", then "Education/Special Training:", then "Required Competencies:", then "Success Measures:", then "Safety Requirements:", then "Physical Requirements:", then "Classification:", then "Note:", then EEO statement (to be removed). We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to decide which sections correspond. We have content: "Why Renovo?" is about company overview; could be "About the role"? Actually "About the role" is typical heading for role description. The "Why Renovo?" is about company; maybe we can treat as "About the role"? But guidelines: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have summary of role: "The Lab Liaison owns the service transaction..." That's role description. Could be "About the role". Then responsibilities: "What you will do:" list of duties. That's Responsibilities. Then qualifications: "Qualifications:" list. That's Qualifications. Then education/special training: could be part of Qualifications or separate? Could be "Requirements"? Actually Requirements often includes qualifications and education. But we have separate "Education/Special Training". Could be part of Qualifications. We can combine. We have "Required Competencies:" which could be Skills. So Skills section. We have "Success Measures:" maybe not a standard heading; could be omitted or placed under Responsibilities? Probably not needed; but we need to preserve all substantive information. We could include a section "Performance Metrics" but not allowed headings. Only allowed headings list. So we need to fit into those headings. Could put success measures under Responsibilities or maybe under a generic section? But we must not create headings not in list. So we need to embed that info within existing sections, maybe under Responsibilities as bullet points. Similarly Safety Requirements and Physical Requirements could be under Requirements? Or maybe under Qualifications? But we have headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use Requirements for safety and physical requirements. Qualifications for experience/education. Skills for competencies. Responsibilities for what you will do. About the role for summary and why Renovo? Benefits, Pay, Schedule: not present, so omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills. We must not repeat job title as heading. No Job ID etc. We need to preserve all substantive information. Let's extract content. About the role: include "Why Renovo?" paragraph and Summary paragraph. Responsibilities: include "What you will do:" bullet list (the long list). Also include other duty paragraphs like "Escort is a standing expectation..." maybe part of responsibilities. Also include "Success Measures:" maybe as bullet under responsibilities? Could be separate but we can incorporate. Requirements: include Safety Requirements and Physical Requirements paragraphs. Qualifications: include Qualifications paragraph (2+ years experience etc) and Education/Special Training paragraph. Skills: include Required Competencies paragraph. We must use

• for any list of duties/requirements/benefits. So for responsibilities we need to turn the prose into list items? The instruction: "Use
  • for any list of duties/requirements/benefits, and

    for prose." So if there is a list, we should use ul/li. The "What you will do:" section is a list of duties (each sentence starting with a verb). We should convert each bullet into

  • . Also the success measures could be list. For qualifications, we have a paragraph describing experience etc; not a list but could be list? It's a paragraph with multiple sentences; we can keep as

    . For education/special training also paragraph. For skills (required competencies) we have a list of competencies each bolded; we can make

    • . For requirements (safety and physical) we have paragraphs; could keep as

      . Now we need to strip boilerplate: EEO statement, note about position description may be altered, classification FLSA maybe not needed? Classification is not in allowed headings; we could drop or put under Requirements? But classification is metadata; we can drop as per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. Classification is minor metadata; we can drop. Also remove "Note: This position description does not list every activity..." etc. Now produce HTML fragment. Let's craft. About the role:

      Why Renovo? Renovo Solutions is a nationwide healthcare and life sciences technology management company. We offer a range of opportunities for employees to grow within the company. With a presence in 40+ states and a growing international footprint, we provide comprehensive solutions for managing and maintaining the equipment our clients depend on. We prioritize investing in our employees’ development, offering various phases and advancement paths. Through ongoing training, mentorship programs, and a supportive work environment, we foster professional growth and promote from within. Join our team to make a difference while advancing your career with Renovo.

      Summary: The Lab Liaison owns the service transaction on instruments at an assigned Johnson & Johnson site under the Enterprise Laboratory Instrument Services (ELIS) program. A request comes in, this role takes it, checks what coverage the instrument carries, dispatches it to a Renovo engineer or to a vendor, tracks it, escorts the work, verifies it is complete and closes it out correctly. The role also carries intake. There is no separate service desk supporting North American sites in this program, so requests arrive here directly, from a laboratory, a walk-up, an email or the system. Triaging that intake and routing it correctly is part of the job, not an interruption to it. The role is deliberately laboratory-facing and on site. Escort is a standing expectation, not an occasional task, and much of the value comes from being physically present and known in the laboratories rather than working a queue from a distance. Lab Liaisons are typically assigned a set of laboratories, buildings or departments so ownership is clear. The role reports to the OSS Supervisor or OSS Lead where the assigned site runs those seats, and to the Site Operations Manager where it does not. It works alongside the Life Science Engineers on self-perform work, and the Lifecycle and Relocations Coordinator on assets entering, leaving or moving within the estate. Where a request concerns an asset changing shape rather than being serviced, it routes to Lifecycle and Relocations. Escort is a standing expectation of every role on this program, not a task assigned to a subset of the team. Anyone on site may be required to escort and host OEM and third-party personnel, confirm they meet site access, induction and safety requirements before entering a laboratory, remain with them while they work where the area requires it, and verify the work is complete and documented before they leave. Nobody on this program declines an escort because it is not in their job description.

      That's About the role. Responsibilities: Use
      • for list. We need to capture all duties from "What you will do:" plus other duty paragraphs (like escort expectation etc). But escort expectation already covered in About the role; we can still include but maybe duplicate. We'll include responsibilities list. List items: - Intake and triage: Receive service requests from laboratory staff by any route, including in person, email, phone and the system of record. Triage each request for urgency, scientific impact and instrument criticality, and set priority accordingly. Confirm the request is complete enough to act on, and gather what is missing rather than returning it. Route requests outside scope to the correct function, including Lifecycle and Relocations for asset changes, and confirm they land. Acknowledge the requester so nobody is left wondering whether the request was received. - Entitlement and dispatch: Check the coverage position of the instrument before dispatching: warranty, service contract, time and materials, or self-perform. Dispatch work to a Renovo engineer where the platform is self-performed, and to the OEM or third party where it is not. Raise service requests, quotes and purchase requisitions through the Sourcing and Payments team. Flag coverage that does not match how the instrument is actually used, in either direction. Escalate to the Site Operations Manager where entitlement is unclear or the quoted cost is disproportionate. - Scheduled maintenance coordination: Build and maintain the scheduled maintenance (SM) calendar for the assigned laboratories. Coordinate SM timing with laboratory staff so maintenance does not collide with critical scientific work. Manage deferments and cancellations, with the reason recorded and the compliance impact understood. Chase overdue and aging work orders rather than letting them accumulate. Escalate SM that cannot be completed within its compliance window. - Vendor coordination and invoice verification: Coordinate vendor visits around laboratory availability and scientific priority. Obtain and check the service report, and confirm it supports the invoice before approval. Query a service report that does not match the reported fault or the authorised scope, rather than passing it for payment. - Laboratory relationship: Maintain a visible daily presence in the assigned laboratories and be known by name to the staff working there. Take requests at the bench and give laboratory staff a straight answer on status and timing. Know the instrument base in the assigned area well enough to anticipate impact rather than react to it. Surface recurring problems, emerging needs and new equipment coming into the area to the Site Operations Manager. - Data and record accountability: Own accuracy of work order data for the assigned area, including status, completion data, vendor detail and cost. Keep asset location, status and coverage position correct in the system of record for the assigned area. Close work orders with complete data so reporting, invoicing and contractual key performance indicators hold up. Raise record discrepancies found in the laboratory rather than working around them. Provide accurate area data for audits, entitlement reviews and reporting cycles. - Quality, compliance and safety: Meet GxP and client quality system documentation requirements for all work coordinated. Support audits and quality reviews covering the assigned laboratories. Follow laboratory safety requirements including biological, chemical, electrical and cryogenic hazards. Exercise stop-work authority when work cannot be performed safely, and escalate rather than proceed. - Escort and vendor hosting, a standing expectation of every site-based role: Escort and host OEM and third-party personnel in client laboratories and equipment areas, on request and regardless of whose scope the instrument sits in. Confirm third-party personnel are inducted, badged, trained, and compliant with client site access and safety requirements before they enter a laboratory. Remain with third-party personnel while they work where the area, the hazard, or the client requires continuous accompaniment. Confirm the work performed matches what was authorised, and that the area is left clean, safe, and operational. Verify the service report or work record is complete before the third party leaves site, and route it for invoice verification. Escalate immediately where a third party arrives unannounced, without correct documentation, or attempts work outside the authorised scope. - Success Measures: Request acknowledgement and triage time; Scheduled maintenance completion against plan for the assigned area; Demand maintenance response and resolution time; Overdue and aging work order volume in the assigned area; Entitlement checked before dispatch, measured on sampled work orders; Vendor work verified and documented before invoice approval; Work order and asset record data accuracy; Deferments recorded with reason and compliance impact understood; Laboratory staff feedback on responsiveness and communication; Audit outcomes for the assigned laboratories. We could keep success measures as list items. Now Requirements: Safety Requirements and Physical Requirements paragraphs. We'll combine into a

        maybe two paragraphs. Safety Requirements: Abide by and follow Renovo safety policies, procedures, and injury and illness prevention expectations. Maintain a safe working environment for self and others when visiting customer sites, laboratories, offices, or operational environments. Follow applicable customer site safety requirements, OSHA guidelines, and laboratory or facility-specific procedures as required. Complete required safety training assignments on time. Physical Requirements: Regular