Manager, OT Architecture

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have info: Salary Range, Hours Of Work, teleworking, location, etc. We need to include Pay section if salary range present. Schedule section if hours of work present. Benefits? Not mentioned except teleworking eligibility; maybe we can include Benefits if teleworking considered benefit? But we should only include if posting actually states them. It says "This position is eligible for teleworking, which is currently one day per week." That's a benefit (telework). Could include Benefits section with that. Also location maybe not needed as heading; could be in a short paragraph under About the role? The instructions: do NOT repeat job title as heading; do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location, supervisor, dept/div, etc in a short paragraph under About the role or maybe a separate meta paragraph. But we should not create extra headings for those. We need sections: About the role (summary), Responsibilities (list), Requirements (maybe education+experience?), Qualifications (maybe required qualifications?), Skills (technical/leadership/behavioral), Benefits (telework), Pay (salary range), Schedule (hours). We must ensure we don't create sections with filler like "commensurate with experience". We have concrete data. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, qualifications, etc. That's a lot. We need to output as

• for any list of duties/requirements/benefits. For prose, use

  . So responsibilities list likely many items; we can make each responsibility as

• . Similarly for required qualifications: education, years experience, supervisory, etc. Skills: technical skills, leadership skills, behavioral skills, competencies. Could group them. We must not include boilerplate like EEO, etc. Remove those. We need to ensure we don't create sections with placeholder text. All sections we create have real content. Let's outline:

  About the role

  Summary paragraph: The Manager of Operational Technology (OT) Architecture leads the development, governance, and implementation of OT architecture standards that support the MTA's mission-critical systems. Reporting to senior leadership, this role provides technical direction and team management across all MTA agencies NYCT (DOS & DOB), LIRR, MNR, B&T, and MTAIT HQ—to ensure core OT platforms such as SCADA, signaling, PACIS, AFC/OMNY, CCTV, telemetry, station networks, fleet systems, tolling, and facility control systems are secure, resilient, and aligned with enterprise strategy. The role oversees individual contributors who design and support specialized OT/IT network infrastructure, reference architectures, device standard configurations, and modernization initiatives that reduce technical debt. The position works closely with capital planning, construction, vendors, and agency stakeholders to ensure OT network investments are strategically aligned, cost-effective, and compliant with MTA standards. This role ensures that the MTA's operational assets, including power, signaling, fare systems, video, tolling, and field device networks, are compliant, high-performing, and optimized for long-term reliability.

  Maybe also include location, supervisor, dept/div in a short p after summary? Could incorporate. But we need to preserve all substantive information: location (2 Broadway, New York, NY 10004), supervisor (Senior Director, Ent Network & OT Architecture), dept/div (Information Technology), hours of work, teleworking eligibility, note about MTA employees only, new hires eligibility after 30 days. Those are minor metadata; we can fold into a short p under About the role or maybe a separate meta paragraph but not as heading. We'll add a

  containing: Location: 2 Broadway, New York, NY 10004. Reports to Senior Director, Ent Network & OT Architecture. Department/Division: Information Technology. Hours of Work: 9:00 am - 5:30 pm (7.5 hours/day) or as required. This position is only open to MTA employees. Eligible for teleworking (one day per week). New hires eligible to apply 30 days after effective date of hire. That preserves. Now Responsibilities: we have a long list. We'll create

  • for each bullet. Need to capture all responsibilities sentences. The responsibilities section includes many sentences separated by periods. We'll break them into logical items. Let's list responsibilities from the text: - Architecture Review & Design Authority: Establishes and approves enterprise OT reference architectures, solution architectures, network designs, and engineering standards for SCADA, signaling, PACIS, AFC/OMNY, fleet systems, and other operational technologies, ensuring alignment with enterprise architecture, cybersecurity, resiliency, and interoperability standards. - Tiered Technical Oversight (T1/T2/T3): Provides Tier 3 architectural guidance for complex incidents and root-cause analysis, supports Tier 2 engineering escalations, establishes technical guidance for Tier 1 operational support, and recommends long-term design improvements to eliminate recurring operational issues. - Cybersecurity Framework & Zero Trust: Defines the OT security stack by applying NIST SP 800-82 Rev. 3 and IEC 62443; implements Zero Trust principles and threat countermeasures across industrial and transit environments, ensuring compliance with enterprise cybersecurity policies and regulatory requirements. - Transport & Wireless Integration: Leads the design and integration of complex transport mediums, including fiber, microwave, DAS, WiFi, LTE/5G, TETRA/UHF/VHF, and leaky coax. - Standards & Device Governance: Establishes and enforces OT/IT network standards, technical standards, configuration baselines, reference configurations, and infrastructure design patterns, and data center standards across all agencies to reduce technical debt. - Application & Payment Networks: Architects network requirements for AFC/OMNY, TVMs, payment gateways, and PCI DSS environments, and supporting network infrastructure ensuring secure and reliable customer transaction flows. - Technology Evaluation & Modernization: Evaluates emerging OT/IT technologies, industrial protocols (Modbus, DNP3, OPC UA), and wireless platforms; develops technology roadmaps to modernize the enterprise and improve system reliability. - Construction & Field Validation: Collaborates with construction and field engineering teams to validate architectural compliance, network acceptance testing, commissioning activities, and as-built documentation. - OT Lifecycle & Asset Management: Establishes lifecycle strategies for OT infrastructure, including technology refresh planning, firmware governance, configuration standards, lifecycle roadmaps, and end-of-support replacement planning. - Enterprise Systems Integration: Defines integration architectures between OT platforms, enterprise IT systems, cloud services, data platforms, and operational applications to ensure secure, scalable, and interoperable information exchange. - Project Leadership & Delivery: Provides architectural leadership for OT modernization initiatives, ensuring technical solutions meet business, operational, cybersecurity, schedule, and budget objectives. - Risk & Disaster Recovery: Develops architectural strategies supporting cybersecurity, disaster recovery, business continuity, and operational resilience. - Stakeholder & Agency Coordination: Builds strong relationships with engineering, operations, and capital delivery groups across NYCT, LIRR, MNR, and B&T. - Operational Transition: Governs the transition of approved OT architectures into production through architecture reviews, operational readiness assessments, documentation standards, and knowledge transfer. - Strategic OT Leadership: Collaborates with senior leadership to align OT network strategy with capital planning and modernization roadmaps. - Performance & Telemetry Analytics: Defines architectural standards for telemetry, network monitoring, performance analytics, and operational observability across OT environments. - Procurement & Contractor Oversight: Provides technical leadership for procurements, including technical specifications, vendor evaluations, proof-of-concept reviews, contract technical requirements, and contractor oversight. - Troubleshoots complex OT issues across SCADA, signaling, PACIS, AFC/OMNY, telemetry, video, wireless, and data center environments. - Analyzes multi-system event chains across integrated OT/IT platforms. - Provides unified architectural leadership across multiple agencies with diverse operational requirements. - Balances cybersecurity, system availability, safety, regulatory compliance, and operational continuity when introducing new technologies into mission-critical transit environments. - Determines enterprise OT architecture standards, technical approaches, platform selection, integration methodologies, and infrastructure design decisions for OT/IT networks, SCADA, signaling, PACIS, AFC/OMNY, wireless, and data center environments. - Applies a risk-based decision framework grounded in safety, cybersecurity, and operational continuity. - Oversees rigorous quality assurance processes to deliver reliability, performance, and safety objectives. - Oversees staff workload and quality of work, addressing performance issues when needed. - Performs other duties as assigned - Complies with all policies and standards - May be required to work hours outside regular work hours, as applicable - Observes the work performed by contractors, as applicable - Reviews invoices and approves them if the work has contractual standards, as applicable - Addresses performance issues with the contractor when possible, as applicable - Escalates issues to other parties when needed, as applicable We'll include all as
  • . Now Requirements: The posting has "Required Qualifications" section with Education, Minimum years, etc. We'll treat as Requirements. Required Qualifications: - Education: Bachelor’s Degree in Arts/Sciences (BA/BS). A combination of education and experience may be considered in lieu of a degree - Minimum 5 years of relevant OT/IT network experience required - Minimum 4 years in supervisory or management roles preferred We'll put these as
    • . Now Skills: The posting has Technical Skills, Leadership Skills, Behavioral Skills, Competencies. We'll combine into Skills section with subheadings? But we only allowed headings from list; we cannot add custom headings like "Technical Skills". However we could still include them as prose within Skills section, maybe using

      to describe each category. But we need to preserve all substantive information; we can list them as

      • under Skills, but we need to differentiate categories? Could just list each bullet as separate
      • irrespective of category. That would preserve info. Let's extract Technical Skills: - Expert knowledge of Cisco hardware/software and industrial networking. - Strong expertise in WiFi, LTE/5G, RF, and leaky coax. - Expert understanding of routing protocols (BGP, OSPF, ISIS), segmentation, and traffic engineering. - Deep experience with SCADA, signaling, PACIS, AFC/OMNY, and telemetry. - Expertise in NIST 800-82 Rev. 3, Zero Trust, and technical debt remediation. - Proficiency with Visio and architecture modeling tools (e.g., Abacus). Leadership Skills: - Expert leadership in leading change by developing inter/intra team communication and cohesiveness; sustainment of culture and supporting staff during organizational growth/changes. - Expert leadership in leading people by working with staff to develop systems to ensure consistent, high-quality project management discipline for all technology-related initiatives and endeavors. - Expert leadership in driving results by meeting organizational goals and customer expectations and making decisions that produce high-quality results by applying technical knowledge, analyzing problems, and calculating risks. - Expert leadership in business acumen by providing direction on evaluation, selection, implementation, and maintenance of information systems, ensuring appropriate investment in strategic and operational systems. - Expert leadership in building coalitions by internally and externally building partnerships with key stakeholders to help achieve the MTA’s mission or common goals through influence or negotiations. Behavioral Skills: - Demonstrated ability to lead teams, provide coaching, and direct feedback. - Expert in active listening, attention to detail, customer service, prioritization, and problem-solving skills. - Expert in working independently and strategically. - Expert in identifying and analyzing risks and developing effective mitigation strategies. - Expert technical knowledge and a diverse skill set to understand various technologies, systems, and potential risks. - Expert in critical thinking, problem-solving, and decision-making skills. - Expert in interpersonal, verbal, and written communication skills