BUILDER Management Specialist NOAA

We need to output HTML fragment with sections: About the role? Actually we have "About GoldenWolf" and "About the Position". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have Benefits, Responsibilities, Requirements, Qualifications (maybe split into Required and Preferred), Pay (salary range), maybe Schedule (full-time 40 hrs/week). Also we have About GoldenWolf and About the Position - those could be considered "About the role"? The instruction says use headings like About the role, Responsibilities, etc. So we can have

About the role

containing the description about GoldenWolf and the position. Or we could split into About GoldenWolf and About the Position but they said use those example headings; we can still use About the role as heading and include both paragraphs. We must not include boilerplate like EEO, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the Equal Opportunity Employer paragraph, also "Why Join GoldenWolf?" maybe that's benefits? Actually "Why Join GoldenWolf?" includes bullet points: Fully remote position, Competitive compensation, Career growth opportunities, Professional development and training, Opportunity to support critical federal infrastructure projects, Collaborative and mission-focused team environment. Those could be considered Benefits or maybe we can include them under Benefits? But we already have Benefits section with list: 401(k) matching, Dental insurance, Health insurance, Paid time off, Vision insurance. Also there is "Paid federal holidays", "401(k) eligible on your first day", "PTO", "Health, Dental, and Vision insurance". Some duplicates. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all those benefit items. We should combine duplicates but preserve info. The list: Benefits: 401(k) matching, Dental insurance, Health insurance, Paid time off, Vision insurance. Then later: Comprehensive Benefits Offered: Paid federal holidays, 401(k) eligible on your first day, PTO, Health, Dental, and Vision insurance. Also "Why Join GoldenWolf?" includes Fully remote position, Competitive compensation, Career growth opportunities, Professional development and training, Opportunity to support critical federal infrastructure projects, Collaborative and mission-focused team environment. Those are not exactly benefits but could be considered under Benefits or maybe a separate section like "Why Join GoldenWolf?" but instruction only lists certain headings; we could treat them as part of Benefits or maybe as a separate section like "About the role"? However they said prefer a few substantive sections over many thin ones. So we could incorporate those into Benefits or maybe a "Why Join GoldenWolf?" as a subsection under Benefits? But we must not create headings not listed unless they have real specific content. The instruction says: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

for section headings (e.g. ...)" implying those are examples; we could still use other headings if needed, but better to stick to those. The "Why Join GoldenWolf?" could be considered part of Benefits or maybe under "About the role". But we have a lot of content: responsibilities, requirements, qualifications (required and preferred), pay, schedule (full-time 40 hrs/week, project duration one-year base period with potential option year, role contingent on award). So we need sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Possibly Skills? Not explicitly listed separate; but we have skills in requirements. Could combine. We must not repeat job title as heading. So no heading for "BUILDER Management Specialist". Good. We must not put Job ID/requisition numbers as headings; none present. We must output only HTML fragment. Let's extract content: About GoldenWolf paragraph: "GoldenWolf is a leading architecture, engineering, and facilities services firm specializing in federal projects across healthcare, defense, and infrastructure sectors. Our team delivers innovative and sustainable solutions that improve facility performance and operational readiness. We are committed to excellence, collaboration, and exceptional service for our clients nationwide." About the Position: "We are seeking a BUILDER Management Specialist to support the National Oceanic and Atmospheric Administration (NOAA) in maintaining, validating, and improving facility asset data within the BUILDER Sustainment Management System (SMS). This role ensures that BUILDER remains an accurate, reliable, and mission‑aligned enterprise asset management tool. The Specialist will work closely with Program Analysts, Facility Managers, and NOAA leadership to maintain data quality, coordinate assessments, develop work plans, validate inventories, and support capital planning." We can combine these two paragraphs under About the role. Responsibilities: list under Key Responsibilities with sub-bullets. We need to preserve all substantive information. The responsibilities are grouped into sections: BUILDER Data Maintenance & Updates, Development of Work Plans & Work Packages, Coordination with Facility Managers & Site Teams, Data Validation & Quality Assurance, Cost Book Review & Recommendations, BUILDER–Archibus Data Coordination. Each has multiple bullet points. We should output a

• for each duty. Could we keep subheadings inside li? Probably just list each duty as separate li, preserving the detail. Could also keep subheadings as strong text inside li. But instruction: use
  • for any list of duties/requirements/benefits. So we can make a flat list of all duties. However we might lose grouping but still preserve all detail. It's okay. Let's extract each duty: From BUILDER Data Maintenance & Updates: - Use database queries to identify, document, and purge corrupted historical records such as duplicate cost indices, zero-dollar valuations, and placeholder equipment. - Apply system validation rules and Archibus‑to‑BUILDER synchronization tools to resolve unrecorded repairs and maintain cross‑platform consistency. - Conduct routine desktop audits in alignment with established parent‑child asset hierarchies. - Use the DIGON Catalog of reports to proactively identify data gaps, anomalies, and incomplete inventory records. Development of Work Plans & Work Packages: - Utilize BUILDER’s Simulation Summary Report to model multi‑year funding scenarios and illustrate impacts on repair backlog. - Support development of annual and multi‑year work plans based on condition indexes, degradation curves, and organizational priorities. - Draft detailed work packages including scope narratives, recommended actions, quantities, and cost estimates. - Align work packages with standardized NOAA O&M budget categories and coordinate finalization with leadership and site teams. Coordination with Facility Managers & Site Teams: - Serve as primary liaison for contracted Facility Condition Assessments (FCAs), ensuring timely transmission of Government‑Furnished Information. - Engage monthly with Site Facility Managers to identify recent project completions, maintenance activities, and changes affecting NOAA BUILDER and Archibus datasets. - Collect and validate documentation such as as‑builts, updates, and quantity changes. - Update BUILDER to reflect completed projects, lifecycle replacements, and major maintenance actions. - Provide training or support on data requirements for BUILDER and Archibus updates. Data Validation & Quality Assurance: - Conduct QA/QC reviews of FCAs, component ratings, and system‑level data. - Validate inspection results for compliance with BUILDER standards. - Recommend corrective actions such as re‑inspections or data adjustments. - Maintain a log of data issues, resolutions, and improvement recommendations, formalizing findings into the Annual BUILDER Data Quality Assessment Report. - Support development and maintenance of Local Context Logs documenting mission‑critical functionality and qualitative factors affecting BCI metrics. Cost Book Review & Recommendations: - Identify cost items requiring refinement and develop written recommendations. - Support NOAA in implementing cost book modifications and track impacts on work plans and funding estimates. BUILDER–Archibus Data Coordination: - Serve as liaison between BUILDER and Archibus inventory processes. - Conduct monthly data‑matching reviews to document discrepancies, mismatches, and data drift, producing Monthly BUILDER–Archibus Synchronization Reports. - Support semi‑annual Reconciliation of Authoritative Data (RAD) process. - Recommend alignment strategies for asset identifiers, lifecycle statuses, and parent‑child hierarchy structures. - Prepare summaries documenting record‑matching status and needed corrections to maintain UNIFORMAT II hierarchy alignment. Now Requirements: "Education & Experience Bachelor’s degree and 3 years of relevant experience Expert knowledge of BUILDER SMS Understanding of facility condition assessments and lifecycle asset management Ability to interpret engineering drawings and as‑built documents Experience evaluating asset inventories and technical documentation" We need to list as
    • . Could combine into sentences. Required Qualifications: "NACI clearance (or ability to obtain) Strong analytical skills and communication capabilities Proficiency with Microsoft Office Skilled in preparing reports and presentations" Preferred Qualifications: "Proficiency in NOAA-specific BUILDER inventory hierarchy and terminology Ability to explain differences between FCI and BCI to non‑technical stakeholders Ability to translate BUILDER Repair Needs into financial metrics for reporting" We could combine Requirements and Qualifications sections? The instruction says use headings like Requirements, Qualifications, Skills. We have both Requirements and Qualifications (required and preferred). We could make a Requirements section for the education/experience and required qualifications, and a Qualifications section for preferred qualifications. Or we could merge. But better to follow instruction: have Requirements (education/experience) and Qualifications (required and preferred). However we also have Skills maybe covered. Let's decide:

      Requirements

      with
      containing: - Bachelor’s degree and 3 years of relevant experience - Expert knowledge of BUILDER SMS - Understanding of facility condition assessments and lifecycle asset management - Ability to interpret engineering drawings and as‑built documents - Experience evaluating asset inventories and technical documentation - NACI clearance (or ability to obtain) - Strong analytical skills and communication capabilities - Proficiency with Microsoft Office - Skilled in preparing reports and presentations

      Qualifications

      with
      containing preferred qualifications: - Proficiency in NOAA-specific BUILDER inventory hierarchy and terminology - Ability to explain differences between FCI and BCI to non‑technical stakeholders - Ability to translate BUILDER Repair Needs into financial metrics for reporting Now Benefits: we need to list all benefit items. Let's gather: From "Benefits:" line: 401(k) matching, Dental insurance, Health insurance, Paid time off, Vision insurance. From "Comprehensive Benefits Offered": Paid federal holidays, 401(k) eligible on your first day, PTO, Health, Dental, and Vision insurance. Note PTO is same as Paid time off. Health, Dental, Vision insurance duplicates. 401(k) eligible on your first day is similar to 401(k) matching? Actually 401(k) matching is a benefit; 401(k) eligible on first day is eligibility. We should keep both as separate items? They are distinct pieces of info. We should preserve all substantive information, not summarize away. So we list each distinct item. Also "Why Join GoldenWolf?" includes: Fully remote position, Competitive compensation, Career growth opportunities, Professional development and training, Opportunity to support critical federal infrastructure projects, Collaborative and mission-focused team environment. These could be considered benefits or maybe under About the role? But they are not strictly benefits like insurance. However we could include them in Benefits section as they are perks. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Benefits section definitely has content. So we can include all these items under Benefits. Thus Benefits list items: - 401(k) matching - Dental insurance -