Jobs · Information Technology · Wisconsin

IT Systems Administrator (On-site)

Tanis Brush · Delafield, WI · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Tanis Brush" intro, then "Position Summary", then "Key Responsibilities", then "Required Qualifications", "Preferred Qualifications", "Physical Requirements and Work Environment", "Decision-Making Authority", "Benefits". Also maybe "Performance Metrics". We need to use

for section headings. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Candidate must reside or will be relocating to Wisconsin. Position does not include a relocation bonus." That's maybe not boilerplate but could be considered location requirement; but it's not a standard heading; we can keep as paragraph maybe under a section? There's no heading for location; we could embed in a paragraph under "About the role" or similar. However we need to decide sections: we have content for About the role? The intro "About Tanis Brush" and "Position Summary" could be combined into an "About the role" section. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings if content exists. We have content for About the role (company description + position summary). Responsibilities (Key Responsibilities). Requirements (maybe Required Qualifications). Qualifications (Preferred Qualifications). Skills? Not explicit; maybe we can skip. Benefits present. Pay and Schedule not present, so omit those sections. Also we have Performance Metrics, Physical Requirements and Work Environment, Decision-Making Authority. Those could be placed under appropriate headings? The instruction list includes only those example headings; but we can add other headings if needed? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those headings; but we can also include other sections if they have real content, but better to map to those. However we have content like Performance Metrics, Physical Requirements, Decision-Making Authority. Could we incorporate them into existing sections? For example, Performance Metrics could go under Responsibilities or Requirements? Might be better to create a section "Performance Metrics" as its own heading, even though not in example list; but instruction says "use

for section headings (e.g. ...)" meaning those are examples, not exclusive. So we can add other headings as needed. But they also say "Prefer a few substantive sections over many thin ones." So we should avoid too many sections. Maybe combine Performance Metrics into Responsibilities or Requirements. Physical Requirements could be a short paragraph under About the role or maybe under Responsibilities? Decision-Making Authority could be under Responsibilities as well. Let's think. We need to preserve all substantive information. So we need to include performance metrics, physical requirements, decision-making authority somewhere. We could create sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Additional Information (maybe). But better to follow the pattern: About the role, Responsibilities, Requirements, Qualifications, Benefits, and maybe a section "Other Details" for physical requirements, decision-making, performance metrics. However they said prefer few substantive sections over many thin ones. So maybe we can incorporate those details into existing sections: e.g., under Responsibilities we can add a bullet for performance metrics? But performance metrics are not responsibilities; they are metrics. Could be under Requirements? Not ideal. Alternatively we can create a section "Performance Metrics" as its own heading, and also "Physical Requirements and Work Environment" and "Decision-Making Authority". That would be three extra sections, making total maybe 7 sections. That's okay if each is substantive. Let's see content length: Performance Metrics is a list of metrics with targets. Physical Requirements is a paragraph. Decision-Making Authority is a paragraph. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Performance Metrics, Physical Requirements, Decision-Making Authority. But we need to avoid headings with filler text. All have real content. Now we need to strip boilerplate: The EEO statement at end, also the duplicated lines about "At Tanis Brush, great people make great products..." and the inclusive employer statement. That's boilerplate/EEO; remove. Also remove "Candidate must reside or will be relocating to Wisconsin. Position does not include a relocation bonus." This is location requirement; not boilerplate but maybe we keep as a short paragraph under About the role or Physical Requirements? It's about location; could be under About the role as a note. We'll keep it. Also remove "Our benefits are designed to help employees..." maybe keep as part of Benefits section. Now we need to format using

for each section heading, then content:

for prose,

  • for lists. We need to preserve all substantive information: ensure we don't lose any details. Let's extract content. About Tanis Brush paragraph: "Tanis Brush is an industrial and abrasive brush manufacturer based in Delafield, Wisconsin, producing precision brushes for automotive, aerospace, data center, and general manufacturing customers. Alongside our manufacturing work, we are building the Tanis Digital Platform, a connected operating platform that brings product intelligence, workflow automation, and AI-assisted decision-making into how the business runs. This role is the operational foundation that platform depends on." Position Summary: "The Systems Administrator is the primary on-site administrator for Tanis Brush's core technology environment and is responsible for the reliable, secure day-to-day operation of systems used across the office and plant floor. The role independently administers Microsoft 365, Active Directory, Windows Server and Hyper-V infrastructure, endpoints, backups, network services, Global Shop Solutions ERP, shipping applications, and related business systems. The Systems Administrator evaluates technical and business requirements, compares alternative courses of action, and independently determines appropriate solutions based on business impact, operational risk, security, reliability, cost, and scalability. The role also provides hands-on end-user support as needed, drawing on the Chief Information Officer and outside vendors for architecture decisions, major investments, and specialized escalation." We can combine these into About the role section. Key Responsibilities: list of bullet points under headings: Systems Administration and End-User Support, Identity, Access, and Onboarding, Endpoint, Hardware, and Lifecycle Management, Business Application Administration and Support, Infrastructure, Security, and Business Continuity, Technical Judgment and Coverage. We need to turn each bullet into
  • . The headings within responsibilities are subheadings; but we only need
    • for any list of duties/requirements/benefits. We could keep subheadings as or just plain text inside
    • . Probably fine to include them as part of the
    • text. We must preserve all details. Let's extract each bullet: Systems Administration and End-User Support: - Independently administer and support the company's day-to-day technology environment, resolving operational issues and selecting appropriate technical solutions within established IT policies and standards. - Own intake, triage, prioritization, resolution, and follow-through for employee technology requests, using business impact, security risk, and production needs to determine priority. - Diagnose and resolve Level 1 and most Level 2 issues across workstations, applications, peripherals, connectivity, and plant-floor technology with minimal supervision. - Identify recurring support issues, determine root causes where practical, and implement or recommend corrective actions that improve reliability and reduce repeat incidents. - Provide user support and training for Microsoft Outlook, conference room equipment (Mersive Solstice), and other standard company technology. - Support VOIP phones and company mobile devices, including troubleshooting, email access, and multi-factor authentication enrollment. - Maintain accurate support records and document significant resolutions, recurring issues, and procedures for future use. Identity, Access, and Onboarding: - Administer Microsoft 365 user accounts, authentication settings, and related access within approved standards. - Administer Active Directory, including user accounts, group membership, and routine identity and access changes. - Evaluate and implement file share permissions and access requests in accordance with approved access and least-privilege practices. - Manage email distribution lists and other routine messaging access requirements. - Complete IT onboarding and offboarding for employees, including accounts, equipment, access, and orientation to company systems. Endpoint, Hardware, and Lifecycle Management: - Configure, deploy, maintain, and replace workstations and related endpoint equipment according to company standards. - Assess endpoint condition and business requirements and recommend equipment replacement, upgrades, or standardization when appropriate. - Maintain accurate IT device inventory and lifecycle records. - Administer and support office printers and coordinate service issues with the Managed Print Service Provider when vendor support is appropriate. - Manage routine printer consumables and support Zebra label printers used in business and production processes. - Support and troubleshoot plant-floor terminals, shop-floor PCs, barcode scanning equipment, and related production technology. - Coordinate hardware installation and replacement activities to minimize disruption to office, production, and shipping operations. - Evaluate hardware requirements, gather quotes, recommend appropriate solutions, coordinate approved purchases, and track deliveries. Business Application Administration and Support: - Administer and support Global Shop Solutions ERP, diagnosing user and system issues, resolving routine problems independently, and escalating specialized or vendor-level issues when appropriate. - Support UPS WorldShip, troubleshoot and resolve operational issues directly, and engage vendor support when specialized assistance is required. - Support FedEx Ship Manager, troubleshoot and resolve operational issues directly, and identify recurring application issues that warrant configuration changes, process improvements, or vendor escalation. Infrastructure, Security, and Business Continuity: - Perform Veeam backup verification and scheduled restore testing, document results, investigate failures, and take or recommend corrective action. - Independently perform routine administration and maintenance of Windows Server, Hyper-V hosts and virtual machines, network devices, and endpoints. - Plan and execute routine patching and updates for workstations, servers, and endpoint software, scheduling changes to minimize business disruption. - Support switches, wireless access points, and network connectivity, determine when vendor escalation is warranted, and coordinate specialized network or cabling work as needed. - Administer the company cybersecurity awareness and training program, including user enrollment, training campaign coordination, completion tracking, follow-up with overdue users, phishing simulation administration, and reporting of participation and results to the CIO. - Respond to employee-reported phishing alerts, suspicious emails, and routine security events; assess potential risk, provide timely guidance to users, take appropriate initial containment or remediation actions within established procedures, document material findings, and escalate confirmed or significant threats to the CIO or security provider. - Maintain technical documentation and runbooks, identify operational or security risks, and recommend improvements to system reliability, security, supportability, and business continuity. Technical Judgment and Coverage: - Exercise independent technical judgment in prioritizing routine IT work, selecting solutions within approved standards, determining appropriate vendor escalation, and coordinating maintenance activities; provide occasional weekend, early-morning, and after-hours support in line with production and shipping schedules. Performance Metrics: - Metric: Service and Issue Resolution - Target: 90% of standard support tickets resolved within one business day, measured monthly, while prioritizing critical issues based on business impact and risk. - Metric: Backup Testing and Recovery - Target: Complete monthly Veeam backup verification and quarterly restore testing with documented results and timely corrective action for identified issues. - Metric: ERP and Core System Reliability - Target: Maintain 99% Global Shop availability during business hours and resolve or appropriately escalate ERP and core system issues within one business day. - Metric: Systems Administration Ownership - Target: Within 90 days, independently administer assigned core systems and infrastructure, prioritize routine operational work, and resolve or appropriately escalate technical issues with minimal supervision. Required Qualifications: - 3-6 years in systems administration or IT operations/support, ideally in a manufacturing environment. - Hands-on Microsoft 365 and Active Directory administration experience. - Working knowledge of Windows Server, virtual

Similar jobs