Facility Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to extract substantive content: About the University of Georgia (description), About The College/Unit/Department (Savannah River Ecology Lab description), Position Summary, Knowledge, Skills, Abilities And/or Competencies, Physical Demands, Duties/Responsibilities (list with percentages), maybe Minimum Qualifications, Preferred Qualifications, etc. Also "Advertised Salary Commensurate with experience" - that's placeholder, so we should NOT create Pay section because it's just "commensurate with experience" which is filler. Work Schedule: "8:00 am to 5:00 pm Monday thru Friday" - that's schedule info, we can include Schedule section. Benefits: "Benefits Eligible" and "Retirement Plan TRS or ORP" and "Employment Type Employee Benefits Eligibility Benefits Eligible Full/Part time Full Time". There's mention of benefits eligibility, retirement plan. That's substantive. So we can include Benefits section.
We must not include boilerplate like EEO, USG Core Values, etc. Also remove "Special Instructions to Applicants", "Location of Vacancy", "Posting Details", "Posting Number", "Working Title", "Department", etc. Those are metadata; we can fold minor metadata into a short
or drop it. Probably we can include a short paragraph with posting number and date? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include a
with posting number and date maybe. But we need to preserve ALL substantive information. Posting number and date might be considered metadata but not substantive? Might be considered minor. Safer to drop them? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Posting number and date are not substantive to the job description; they are administrative. Could drop. But we could include a short
at top: "Posting Number: S11952P; Posted: 04/22/2024." That's minor metadata; allowed.
We must not include application instructions (Special Instructions to Applicants, Contact Information? Actually contact info might be substantive? It's recruitment contact; maybe we can keep? The instruction says remove application instructions. Contact Information might be considered part of application instructions. Safer to drop.
We need to output only HTML fragment, no markdown.
Let's decide sections:
- About the University (maybe combine with About the College/Unit/Department as "About the Organization"? But instructions list headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those headings if content matches. We have "About the University of Georgia" and "About The College/Unit/Department". That's more about the organization, not the role. Could use "About the role" for position summary? Actually "About the role" could contain position summary and maybe description of unit. We'll put position summary under About the role.
- Responsibilities: we have duties/responsibilities list with percentages. Use
- each duty.
- Requirements: we have Minimum Qualifications and Preferred Qualifications. Could combine into Requirements section.
- Skills: we have Knowledge, Skills, Abilities And/or Competencies (list). Could be Skills section.
- Benefits: we have Benefits Eligible, Retirement Plan TRS or ORP.
- Schedule: we have work schedule.
- Pay: we have Advertised Salary Commensurate with experience - placeholder, so we skip Pay section.
We must not create sections with filler. So we will include About the role, Responsibilities, Requirements, Skills, Benefits, Schedule.
Now we need to extract content precisely.
About the role: Could include position summary and maybe description of unit? The position summary: "This position will serve as the interface with contractors who by agreement provide the facility services that the Department of Energy provides SREL through the course of our cooperative agreement with them. This position will also handle facility issues and planning and regularly reports to the SREL Assistant Director."
Also we have "About The College/Unit/Department": description of Savannah River Ecology Lab. Could be included under About the role as context. We'll combine.
We'll write a
for prose.
Responsibilities: list each duty with percentage. The posting repeats "Duties/Responsibilities" lines each with a duty and percentage. We'll extract:
- Plan and coordinate new construction, remodels, and installations with contractors and vendors. Supervise contractors who perform work for SREL and make sure that they perform work within the safety parameters expected by UGA and the Department of Energy. (25%)
- Serve as the direct manager of the SREL maintenance and facility department. This includes supervision of the maintenance personnel, overseeing their training and annual evaluations, and determining work and shift schedules. (20%)
- Responsible for interacting with our primary cooperator, the Department of Energy, and making sure that SREL is complying with the Functional Service Agreements (FSA’s) that define how both entities interact with each other. This position will also provide technical expertise to SREL management when the FSA’s are negotiated bi-annually. (15%)
- This position will be responsible for the upkeep and oversight of the SREL state vehicle inventory. Currently this inventory includes 33 state vehicles. This will include tracking mileage, scheduling maintenance, and keeping the vehicle sign out log up to date. (15%)
- Assist the facilities and maintenance mechanics with work related to the upkeep of the the SREL facilities. (15%)
- Oversee the facilities department budget. This includes monitoring department spending, approving related expenditures, and making annual budget requests to the Assistant Directors office. (10%)
We'll put each as
- with the percentage maybe in parentheses.
Requirements: Minimum Qualifications: "Requires at least a baccalaureate degree in the field. Please contact your Human Resources office for an evaluation of education/experience in lieu of the required minimum qualifications."
Preferred Qualifications: "HVAC/ Electrical knowledge with at least 5 years of related experience. 1 year management also experience required."
We'll combine into
- items.
Skills: Knowledge, Skills, Abilities And/or Competencies: list:
- Facility maintenance knowledge (Electrical, HVAC, Mechanical).
- General carpentry and renovation knowledge.
- Physical Demands (but that's separate). Actually Physical Demands is separate section; but we could include under Skills? Better to keep Physical Demands separate? The instructions didn't list Physical Demands as a heading option, but we could include as part of Skills or maybe as its own section? Since not listed, we could incorporate into Skills section as bullet. But we have Physical Demands details: "Work in outdoor climates with exposure to heat and cold. Lifting up to 40 lbs. Work from heights and climbing ladders. Driving as need to perform job duties." Also there are yes/no questions about driving, position of trust, etc. Those are not substantive? Might be considered metadata. We could include driving as part of Physical Demands.
We'll create a Skills section that includes both knowledge/skills and physical demands.
Benefits: "Benefits Eligible", "Retirement Plan TRS or ORP", "Employment Type Employee Benefits Eligibility Benefits Eligible Full/Part time Full Time". Also maybe "Benefits Eligible" is just a flag. We'll include: "Benefits eligible", "Retirement plan options: TRS or ORP", "Full-time employment".
Schedule: "Work Schedule: Additional Schedule Information 8:00 am to 5:00 pm Monday thru Friday". We'll output that.
Now we need to ensure we don't include boilerplate like EEO, USG Core Values, etc.
We'll output HTML fragment:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Schedule
8:00 am to 5:00 pm Monday through Friday
We might also include a short metadata paragraph at top: Posting Number: S11952P; Posted: 04/22/2024.
but not required. The instruction says preserve ALL substantive information; posting number is not substantive but minor metadata; we can drop. Safer to drop.
Now craft the content precisely.
About the role paragraph: Combine position summary and description of unit.
Position Summary: "This position will serve as the interface with contractors who by agreement provide the facility services that the Department of Energy provides SREL through the course of our cooperative agreement with them. This position will also handle facility issues and planning and regularly reports to the SREL Assistant Director."
About The College/Unit/Department: "The Savannah River Ecology Lab is a research unit of the University of Georgia, that conducts research on the Federal nuclear site known as the Savannah River Site."
We could also include brief about University of Georgia? Might be too much. But we can include a short sentence: "The University of Georgia is the state’s flagship university, ranked among the top 20 public universities." However that is from the boilerplate about the university; it's substantive? It's description of employer. Might be okay to include. But we need to avoid excessive boilerplate. The instructions say remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The university description is not boilerplate; it's substantive about employer. Could include.
We'll include a short paragraph: "The University of Georgia, chartered in 1785, is the state’s flagship university and ranked among the top 20 public universities in U.S. News & World Report. The Savannah River Ecology Lab is a research unit of UGA that conducts research on the Federal nuclear site known as the Savannah River Site."
Now Responsibilities list as above.
Requirements list: Minimum Qualifications and Preferred Qualifications.
We'll write:
- Minimum: At least a baccalaureate degree in the field (or equivalent education/experience as evaluated by HR).
- Preferred: HVAC/Electrical knowledge with at least 5 years of related experience; 1 year of management experience.
Skills list: Include knowledge, skills, abilities, and physical demands.
- Facility maintenance knowledge (electrical, HVAC, mechanical).
- General carpentry and renovation knowledge.
- Physical
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract substantive content: About the University of Georgia (description), About The College/Unit/Department (Savannah River Ecology Lab description), Position Summary, Knowledge, Skills, Abilities And/or Competencies, Physical Demands, Duties/Responsibilities (list with percentages), maybe Minimum Qualifications, Preferred Qualifications, etc. Also "Advertised Salary Commensurate with experience" - that's placeholder, so we should NOT create Pay section because it's just "commensurate with experience" which is filler. Work Schedule: "8:00 am to 5:00 pm Monday thru Friday" - that's schedule info, we can include Schedule section. Benefits: "Benefits Eligible" and "Retirement Plan TRS or ORP" and "Employment Type Employee Benefits Eligibility Benefits Eligible Full/Part time Full Time". There's mention of benefits eligibility, retirement plan. That's substantive. So we can include Benefits section. We must not include boilerplate like EEO, USG Core Values, etc. Also remove "Special Instructions to Applicants", "Location of Vacancy", "Posting Details", "Posting Number", "Working Title", "Department", etc. Those are metadata; we can fold minor metadata into a short
or drop it. Probably we can include a short paragraph with posting number and date? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include a
with posting number and date maybe. But we need to preserve ALL substantive information. Posting number and date might be considered metadata but not substantive? Might be considered minor. Safer to drop them? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Posting number and date are not substantive to the job description; they are administrative. Could drop. But we could include a short
at top: "Posting Number: S11952P; Posted: 04/22/2024." That's minor metadata; allowed. We must not include application instructions (Special Instructions to Applicants, Contact Information? Actually contact info might be substantive? It's recruitment contact; maybe we can keep? The instruction says remove application instructions. Contact Information might be considered part of application instructions. Safer to drop. We need to output only HTML fragment, no markdown. Let's decide sections: - About the University (maybe combine with About the College/Unit/Department as "About the Organization"? But instructions list headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those headings if content matches. We have "About the University of Georgia" and "About The College/Unit/Department". That's more about the organization, not the role. Could use "About the role" for position summary? Actually "About the role" could contain position summary and maybe description of unit. We'll put position summary under About the role. - Responsibilities: we have duties/responsibilities list with percentages. Use
- each duty.
- Requirements: we have Minimum Qualifications and Preferred Qualifications. Could combine into Requirements section.
- Skills: we have Knowledge, Skills, Abilities And/or Competencies (list). Could be Skills section.
- Benefits: we have Benefits Eligible, Retirement Plan TRS or ORP.
- Schedule: we have work schedule.
- Pay: we have Advertised Salary Commensurate with experience - placeholder, so we skip Pay section.
We must not create sections with filler. So we will include About the role, Responsibilities, Requirements, Skills, Benefits, Schedule.
Now we need to extract content precisely.
About the role: Could include position summary and maybe description of unit? The position summary: "This position will serve as the interface with contractors who by agreement provide the facility services that the Department of Energy provides SREL through the course of our cooperative agreement with them. This position will also handle facility issues and planning and regularly reports to the SREL Assistant Director."
Also we have "About The College/Unit/Department": description of Savannah River Ecology Lab. Could be included under About the role as context. We'll combine.
We'll write a
for prose. Responsibilities: list each duty with percentage. The posting repeats "Duties/Responsibilities" lines each with a duty and percentage. We'll extract: - Plan and coordinate new construction, remodels, and installations with contractors and vendors. Supervise contractors who perform work for SREL and make sure that they perform work within the safety parameters expected by UGA and the Department of Energy. (25%) - Serve as the direct manager of the SREL maintenance and facility department. This includes supervision of the maintenance personnel, overseeing their training and annual evaluations, and determining work and shift schedules. (20%) - Responsible for interacting with our primary cooperator, the Department of Energy, and making sure that SREL is complying with the Functional Service Agreements (FSA’s) that define how both entities interact with each other. This position will also provide technical expertise to SREL management when the FSA’s are negotiated bi-annually. (15%) - This position will be responsible for the upkeep and oversight of the SREL state vehicle inventory. Currently this inventory includes 33 state vehicles. This will include tracking mileage, scheduling maintenance, and keeping the vehicle sign out log up to date. (15%) - Assist the facilities and maintenance mechanics with work related to the upkeep of the the SREL facilities. (15%) - Oversee the facilities department budget. This includes monitoring department spending, approving related expenditures, and making annual budget requests to the Assistant Directors office. (10%) We'll put each as
- with the percentage maybe in parentheses.
Requirements: Minimum Qualifications: "Requires at least a baccalaureate degree in the field. Please contact your Human Resources office for an evaluation of education/experience in lieu of the required minimum qualifications."
Preferred Qualifications: "HVAC/ Electrical knowledge with at least 5 years of related experience. 1 year management also experience required."
We'll combine into
- items.
Skills: Knowledge, Skills, Abilities And/or Competencies: list:
- Facility maintenance knowledge (Electrical, HVAC, Mechanical).
- General carpentry and renovation knowledge.
- Physical Demands (but that's separate). Actually Physical Demands is separate section; but we could include under Skills? Better to keep Physical Demands separate? The instructions didn't list Physical Demands as a heading option, but we could include as part of Skills or maybe as its own section? Since not listed, we could incorporate into Skills section as bullet. But we have Physical Demands details: "Work in outdoor climates with exposure to heat and cold. Lifting up to 40 lbs. Work from heights and climbing ladders. Driving as need to perform job duties." Also there are yes/no questions about driving, position of trust, etc. Those are not substantive? Might be considered metadata. We could include driving as part of Physical Demands.
We'll create a Skills section that includes both knowledge/skills and physical demands.
Benefits: "Benefits Eligible", "Retirement Plan TRS or ORP", "Employment Type Employee Benefits Eligibility Benefits Eligible Full/Part time Full Time". Also maybe "Benefits Eligible" is just a flag. We'll include: "Benefits eligible", "Retirement plan options: TRS or ORP", "Full-time employment".
Schedule: "Work Schedule: Additional Schedule Information 8:00 am to 5:00 pm Monday thru Friday". We'll output that.
Now we need to ensure we don't include boilerplate like EEO, USG Core Values, etc.
We'll output HTML fragment:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Schedule
8:00 am to 5:00 pm Monday through Friday
We might also include a short metadata paragraph at top:Posting Number: S11952P; Posted: 04/22/2024.
but not required. The instruction says preserve ALL substantive information; posting number is not substantive but minor metadata; we can drop. Safer to drop. Now craft the content precisely. About the role paragraph: Combine position summary and description of unit. Position Summary: "This position will serve as the interface with contractors who by agreement provide the facility services that the Department of Energy provides SREL through the course of our cooperative agreement with them. This position will also handle facility issues and planning and regularly reports to the SREL Assistant Director." About The College/Unit/Department: "The Savannah River Ecology Lab is a research unit of the University of Georgia, that conducts research on the Federal nuclear site known as the Savannah River Site." We could also include brief about University of Georgia? Might be too much. But we can include a short sentence: "The University of Georgia is the state’s flagship university, ranked among the top 20 public universities." However that is from the boilerplate about the university; it's substantive? It's description of employer. Might be okay to include. But we need to avoid excessive boilerplate. The instructions say remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The university description is not boilerplate; it's substantive about employer. Could include. We'll include a short paragraph: "The University of Georgia, chartered in 1785, is the state’s flagship university and ranked among the top 20 public universities in U.S. News & World Report. The Savannah River Ecology Lab is a research unit of UGA that conducts research on the Federal nuclear site known as the Savannah River Site." Now Responsibilities list as above. Requirements list: Minimum Qualifications and Preferred Qualifications. We'll write: - Minimum: At least a baccalaureate degree in the field (or equivalent education/experience as evaluated by HR).
- Preferred: HVAC/Electrical knowledge with at least 5 years of related experience; 1 year of management experience. Skills list: Include knowledge, skills, abilities, and physical demands.
- Facility maintenance knowledge (electrical, HVAC, mechanical).
- General carpentry and renovation knowledge.
- Physical
- items.
Skills: Knowledge, Skills, Abilities And/or Competencies: list:
- Facility maintenance knowledge (Electrical, HVAC, Mechanical).
- General carpentry and renovation knowledge.
- Physical Demands (but that's separate). Actually Physical Demands is separate section; but we could include under Skills? Better to keep Physical Demands separate? The instructions didn't list Physical Demands as a heading option, but we could include as part of Skills or maybe as its own section? Since not listed, we could incorporate into Skills section as bullet. But we have Physical Demands details: "Work in outdoor climates with exposure to heat and cold. Lifting up to 40 lbs. Work from heights and climbing ladders. Driving as need to perform job duties." Also there are yes/no questions about driving, position of trust, etc. Those are not substantive? Might be considered metadata. We could include driving as part of Physical Demands.
We'll create a Skills section that includes both knowledge/skills and physical demands.
Benefits: "Benefits Eligible", "Retirement Plan TRS or ORP", "Employment Type Employee Benefits Eligibility Benefits Eligible Full/Part time Full Time". Also maybe "Benefits Eligible" is just a flag. We'll include: "Benefits eligible", "Retirement plan options: TRS or ORP", "Full-time employment".
Schedule: "Work Schedule: Additional Schedule Information 8:00 am to 5:00 pm Monday thru Friday". We'll output that.
Now we need to ensure we don't include boilerplate like EEO, USG Core Values, etc.
We'll output HTML fragment: