Business Applications Administrator

We need to output HTML fragment with sections: only include sections that have real specific content. The posting includes salary, position summary, essential duties and responsibilities (list), required qualifications, additional requirements, preferred qualifications, condition of employment, knowledge/skills/abilities, cultural competence, physical demands, work environment, reporting relationship, representation, level of compensation, benefits, classification history, disclaimer, etc. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. The posting includes a "POSITION SUMMARY" which could map to About the role. It includes "ESSENTIAL DUTIES AND RESPONSIBILITIES" -> Responsibilities. It includes "Required Qualifications", "Additional Requirements", "Preferred Qualifications" -> could be Qualifications or Requirements. It includes "Knowledge Of", "Ability To" etc -> Skills. It includes "Level Of Compensation" and "SALARY" -> Pay. It includes "This position includes the following benefits..." -> Benefits. It does not mention schedule specifics (no schedule). So we should not include Schedule heading. We must not include headings with filler like "commensurate with experience". We have actual salary number. We need to preserve all substantive info, not invent or summarize away detail. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes EEO statement at end: "All employment open positions are made available on a nondiscriminatory basis..." That's boilerplate; remove. Also disclaimer maybe considered boilerplate? The disclaimer: "The preceding list is not exhaustive..." Might be considered boilerplate but it's part of job description; but it's generic. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The disclaimer might be considered legal boilerplate; but it's part of job description. However it's generic; maybe we should remove it as it's not substantive? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The disclaimer is not substantive detail about the job; it's a generic disclaimer. Likely we should remove it. Also classification history maybe not substantive? It's metadata; could be dropped. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Classification history is minor metadata; we could drop or put in a short p. Probably drop. We need to include sections only when posting has real specific content. So we will have:

  About the role

  with position summary paragraph.

  Responsibilities

  with
  • each duty.

    Requirements

    maybe combine Required Qualifications, Additional Requirements, Preferred Qualifications? But we have separate headings: Qualifications, Skills. The instruction list includes Qualifications and Skills as possible headings. We could put Required Qualifications under

    Qualifications

    , Additional Requirements maybe also under Qualifications or Requirements. Preferred Qualifications could be under Qualifications as well. Or we could have Requirements section for mandatory, and Qualifications for preferred? But we have both Required and Preferred. The instruction list includes Requirements and Qualifications as separate possible headings. We could use Requirements for mandatory (Required Qualifications + Additional Requirements) and Qualifications for preferred (Preferred Qualifications). However we also have Knowledge Of and Ability To which are skills; those could go under Skills. Thus:

    Requirements

    with Required Qualifications and Additional Requirements as list? The Required Qualifications is a paragraph: "Bachelor's degree in job related area or business-related computer science Two year's experience in computer system application support". Additional Requirements: list of items. We'll need to preserve all info. Could format as

    for the paragraph and

    for list. Similarly Preferred Qualifications as list under Qualifications. Skills: Knowledge Of and Ability To sections as list. Benefits: paragraph. Pay: paragraph with salary. We must not include Schedule. We must not repeat job title. We must output only HTML fragment. Let's extract details. Salary: "$127,880.00" appears twice: SALARY line and Level Of Compensation line. We'll include once. Position Summary: "The employee in this position implements, manages, and maintains the core Business, HR and Payroll applications of the district – to include system design, set-up, maintenance, troubleshooting, process evaluation and improvements, and system security. The Business Applications Administrator will work with all interested parties, such as technical support, vendors, end-users and staff, to ensure that the applications are functioning in such a way as to promote the district's core mission. They provide advanced levels of support with the integration of multiple applications and/or processes. They are able to manage highly complex projects involving multiple systems, user groups, and lasting several months; and ensure that the systems meet service level objectives." We'll keep that as paragraph. Essential Duties and Responsibilities: list items after "ESSENTIAL DUTIES AND RESPONSIBILITIES include the following." We'll capture each bullet (they are sentences separated by periods). We'll need to split into list items. Let's extract them: - Assumes lead role and subject-matter expert for mission-critical application of BusinessPLUS and communicates effectively with other technical staff and district level end users. - Determines and meets deadlines for the implementation of project timelines. - Develops, implements and monitors information systems policies and procedures for the purpose of ensuring data accuracy, system stabilization, security and regulatory compliance. - Collaborates with district personnel, vendors, and peers for the purpose of implementing, maintaining and troubleshooting data, systems and/or programs. - Acts as the primary district liaison to vendors. - Track incidents to closure and verify solutions provide required outcome. - Assess systems-level processes and leads effort to identify and implement new solutions. - Translates ideas into concrete action plans to implement significant change and/or improvements in the district. - Coordinate with Business Services and Human Resources staff to research, analyze, and troubleshoot application program problems and inefficiencies. - Effectively formulate recommendations for solutions and improvements. - Provides leadership and planning to training staff and end users, identifies training needs and provides training in multiple formats to users in virtually all positions of the district. - Develops and documents data models for the purpose of responding to user and administrative data needs, data relationships, system modification and customized reporting. - Leads effort to implement system upgrades, including developing proper test plans, ensuring adequate testing is performed, maintaining test records, and providing proper communication to affected parties. - Designs and creates a wide variety of technical and non-technical materials for the purpose of documenting processes, providing written reference and/or explaining new and existing functionality and flow of information. Ensures these materials are compliant with district, state and federal reporting requirements including but not limited to district policy, state RCW and WAC codes, and Family Educational Rights and Privacy Act (FERPA). - Assist school and department staff in the development, creation, documentation, and maintenance of reports using the various report-writing tools. - Researches solutions for the purpose of providing technical information on compatibility, new technologies, system errors, user problems and cross system communication. - Participates in meetings, workshops and seminars for the purpose of conveying and/or gathering information required to perform essential functions and improve performance, functionality and user experience. - Serve as a member of the Business Services team. - Perform related duties consistent with the scope and intent of the position. - Assists other personnel as may be required for the purpose of ensuring an efficient and effective work environment. We need to keep them as list items. Required Qualifications: "Bachelor's degree in job related area or business-related computer science Two year's experience in computer system application support". Might be two sentences? We'll keep as paragraph. Additional Requirements: list: - Experience with microcomputer and centralized online computer systems - Experience in computer-generated report writing and spreadsheet development - Experience in training and group facilitation - Or any combination of experience and education that has provided the required knowledge and abilities Preferred Qualifications: list: - Experience with BusinessPLUS - Progressive experience in finance - Successful experience with finance and human resource information systems applications - Experience with S275, F195, F196, and/or DRS reporting Condition Of Employment: "Criminal background clearance" and "Work Scheduled hours on a consistent basis". The latter is about schedule but not specific; we might ignore schedule as not specific. Condition of employment maybe not needed as a section; but we could include under Requirements? However instruction says only include sections when posting has real specific content. Condition of employment is specific but not a standard heading; we could fold into a short p under Requirements or maybe ignore as minor metadata. Probably we can include as a short p under Requirements? But we already have Requirements section; we could add a paragraph after list: "Condition of employment: Criminal background clearance. Work scheduled hours on a consistent basis." However the instruction says do not put Job ID/requisition numbers as headings — fold minor metadata into a short

    or drop it. This is metadata; we could drop. I'd drop condition of employment to keep sections minimal. Knowledge Of: list: - The principles, practices, and methods of computing systems - The analysis and design of relational database management - Report writers - The principles and practices of Finance and Human Resource operations procedures for information system documentation Ability To: list: - Plan and lead process improvement with technology - Troubleshoot and resolve problems related to database and software systems - Test and develop procedures for documentation - Function with minimum guidance - Effectively analyze data and issues and create action plans - Demonstrate good project management skills - Operate as part of a team executing projects - Organize and plan projects - Communicate effectively, verbally and in writing, with end users to resolve problems and express complex technical concepts in business terms - Demonstrate analytical, problem solving, and conceptual skills - Adapt to changing work priorities - Exercise initiative, make independent decisions, multi-task and follow through on assignments - Maintain effective working relationships with individuals and groups in a multicultural and diverse community - Abide by Federal Way Public Schools' Policies and Procedures - Perform the essential functions of the job with or without reasonable accommodations Cultural Competence: list: - Knowledge/awareness of own cultural identity and how this influences behavior, and desire to learn about the cultural identity of others. - Ability to establish and nurture an environment that promotes cultural competence and equitable treatment of staff, students, and patrons of the District. - Ability to understand and hold self and others accountable for promoting the Federal Way Public Schools' commitment to "Each Scholar: A Voice. A Dream. A Bright Future." - Ability to recognize that each person is a unique individual even as we celebrate their group cultural heritage. Physical Demands: paragraph describing demands. We could include under a section? Not in allowed headings list. Could we include as a paragraph under Requirements? Not appropriate. The instruction only lists specific headings; we should not create other headings. So we should omit Physical Demands and Work Environment as they are not in allowed headings list. However they are substantive. But the instruction says: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should only use those headings; we could still include other content under those headings if appropriate. Physical Demands could be placed under Requirements? Not really. Could be under Skills? Not. Could be under About the role? Not. Might be better to omit as they are not covered by allowed headings. However the instruction says "Prefer a few substantive sections over many thin ones." It doesn't forbid other headings, but says use h