IT Specialist (Systems Analysis)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes summary (about the role), duties (responsibilities), requirements (conditions of employment), qualifications (KSAs), education (no positive requirement), additional info (salary dependent on experience/education, probation, direct deposit, E-Verify, travel card, drug-free workplace, benefits mention). There's no explicit Pay or Schedule details (salary dependent on experience/education is not a specific number, so we should NOT create Pay section because it's not specific. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits: there is a line "Help Review our benefits" but no details; we should not create Benefits section because no specific benefits listed. So we may have sections: About the role (maybe from summary), Responsibilities (duties), Requirements (conditions of employment), Qualifications (knowledge/skill/abilities), Education (maybe we can include but it's just statement that there is no positive educational requirement; that is substantive? It says "Education There is no positive educational requirement for this position." That's specific content, so we can include Education section. Also maybe Additional information could be under "Additional Information" but not a standard heading; we could incorporate into Qualifications or Requirements? The instruction: prefer few substantive sections over many thin ones. We could combine additional info into Requirements or Qualifications? But it's about probation, direct deposit, E-Verify, travel card, drug-free workplace, commitment statements. Those are more like conditions of employment, maybe part of Requirements. However Requirements already includes conditions of employment (background check, E-Verify, Cyber Workforce qualifications, continuous learning). The additional info includes probation period, direct deposit, travel card, drug-free workplace, commitment statements. Those could be considered part of Requirements as well. But we should not duplicate. We could create a section "Additional Information" but not a standard heading; we are limited to the given headings list. We could put that info under Requirements as a list. Or we could create a separate section "Qualifications" for KSAs and "Requirements" for conditions. The additional info could go under Requirements as well.
Thus sections: About the role (summary), Responsibilities (duties list), Requirements (conditions of employment + additional info), Qualifications (knowledge/skill/abilities), Education (statement). Possibly Skills could be merged into Qualifications; but we have Qualifications heading already. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings exactly. We'll include About the role, Responsibilities, Requirements, Qualifications, Education. Not Skills separate.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The text includes many duplicated lines like "Help" etc. We need to strip those.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract substantive content.
Summary: "This position is assigned to the Nonappropriated Fund (NAF) Systems Branch (N6Q); supporting Fleet and Family Readiness Support Services (N94); Commander, Navy Installations Command (CNIC); Millington, TN. Incumbent serves as a Headquarters (HQ) IT Specialist (Systems Analysis) responsible for applying analytical processes to the planning, design, implementation, and maintenance of existing, of new and improved information systems to meet the business requirements of customer programs."
We'll put that in under
About the role
.
Responsibilities: list of duties. The duties list is long. We need to capture each bullet as - . The list includes many items separated by periods. We'll need to parse them into list items.
Let's extract duties from "Duties include but are not limited to:" then list.
I'll copy the duties text:
Provides higher level helpdesk support for the Enterprise Resource Planning (ERP) and business systems.
Cross-training colleagues as required or appropriate
Performing needs analyses to define opportunities for new or improved business process solutions.
Analyzes customer/user/process owner change requests and/or makes suitable alternative recommendations to business partners when applicable.
Consults with customers to identify and specify requirements.
Conducts as-is/to-be business process workshops, documenting results and creating gap-fit analyses.
Researches best practice ERP and business configuration solutions.
Translates customer business requirements into configured system prototypes.
Develops overall functional and systems requirements and specifications.
Conducts business process reengineering and documenting results.
Conducts feasibility studies and trade-off analyses.
Prepares business cases for the application of IT solutions.
Defines ERP and business systems scope and objectives.
Develops cost estimates for new or modified systems.
Assists with the integration of all systems components; e.g., procedures, databases, policies, software, and hardware.
Prepares functional specification for custom application developments.
Plans and manages ERP and business systems implementations.
Serves as a liaison between development teams and internal/external business partners.
Configures ERP and business systems to accomplish business functions.
Creates ERP and business systems requirements, configuration, and training documentation.
Plans and manages system testing.
Creates testing plans and testing case scenarios.
Plans and manages system data conversions.
Performs unit testing, integration testing, and regression testing.
Ensures integration between ERP systems and functional modules adheres to best practices.
Serves as acting Contracting Officer Representative (COR) or Technical Advisor (TA), as required.
Provides beginner and advanced ERP and business systems training to super-users, business process owners, end users, and peers.
Ensures the rigorous application of information security/ information assurance policies, principles, and practices to the systems analysis process.
We'll put each as
- .
Now Requirements: Conditions of employment plus additional info.
Conditions of employment list:
- Must pass all applicable records and background check.
- Must successfully pass the E-Verify employment verification check.
- Any discrepancies must be resolved as a condition of employment.
- Must earn and maintain appropriate foundational and residential qualifications from the DoD Cyber Workforce Qualification Matrix (described in DODM 8140) within nine (9) months.
- Must participate in a continuous learning program as described in DODM 8140.
- A minimum of 20 hours of Cyber Workforce related continuous professional development annually or what is required to maintain certification, whichever is greater.
Additional info (from "Additional information" paragraph):
- Salary is dependent on experience and/or education. (But we said not to create Pay section; we can include this as a note under Requirements? It's about salary, but it's not specific; maybe we should not include because it's vague. However the rule says: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state that salary is dependent on experience/education, but that's not a specific number; still it's stating something about pay. Should we include it? The instruction: "Prefer a few substantive sections over many thin ones." Including a vague salary statement may be thin. But we could include it as a paragraph under Requirements or Additional Information. However we are not creating a Pay section; we can keep the sentence in a
under Requirements or maybe under a generic section? The instruction says we can use only those headings; we could add a paragraph under Requirements that mentions salary dependency. That's okay.
- Some positions have special requirements.
- Selectee may be required to complete a one (1) year probationary period.
- Participation in Direct Deposit/Electronic Fund Transfer within the first 30 days of employment is required.
- We utilize E-Verify to confirm selectee's eligibility to work in the United States. (duplicate)
- This announcement may be used to fill additional vacancies within 60 days of issuance of selection certificate.
- For positions requiring travel more than twice per year, selectee may be required to obtain and maintain in good standing a Government-issued Travel Card for official government travel purposes.
- Executive Order 12564 requires a Federal workplace free of illegal drugs. According to the Executive Order, all Federal employees are required to remain drug free throughout their employment. Commander, Navy Installations Command is a Drug-Free Federal Workplace. The use of illegal drugs will not be tolerated, and use of or intoxication by illegal drugs will result in penalties up to and including removal from Federal Service.
- Candidates should be committed to improving the efficiency of the Federal government, passionate about the ideals of our American republic, and committed to upholding the rule of law and the United States Constitution.
- Help Review our benefits (boilerplate, ignore).
We need to avoid duplication: E-Verify appears twice; we can keep one.
We'll combine all these into a
under Requirements.
Now Qualifications: list of KSAs.
From "Qualifications" section:
- Knowledge of and skill in applying industry-standard and organizationally accepted business and systems analysis principles and methods.
- Knowledge of ERP and business systems life cycle management concepts and skill in their application to the organization's current and future systems.
- Knowledge of cost-benefit analysis methods sufficient to evaluate the feasibility of proposed new systems development projects.
- Knowledge of and skill in configuring ERP and business systems to achieve business requirements.
- Knowledge of and skill in understanding organizational business processes and operations.
- Ability to make business processes and operations recommendations for improvements.
- Knowledge of and skill in translating functional requirements into complete design specifications to satisfy changes in organizational requirements.
- Skill in collaborating with applications developers to isolate and solve design problems encountered during testing and implementation phases.
- Ability to communicate effectively both orally and in writing
We'll put each as - .
Education: "There is no positive educational requirement for this position." Also maybe mention that education is not required but can be considered? We'll just put that as
.
Now we need to ensure we don't include any boilerplate like "Help", "Review our benefits", duplicated lines, etc.
Also need to remove lines like "Help In order to qualify for this position, resumes must provide sufficient experience and/or education, knowledge, skills, and ability to perform the duties of the position." That's generic; maybe we can incorporate into Requirements? But it's basically saying resumes must show experience etc. That's generic; we could omit as it's not specific substantive detail beyond what's already covered. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. That sentence is somewhat generic but still part of the posting; it's about qualification evaluation. Might be considered boilerplate? It's not a standard EEO but it's about resume evaluation. Could be considered part of Requirements? However we already have Requirements list; we could add a bullet: "Applicants must demonstrate sufficient experience and/or education, knowledge, skills, and ability to perform the duties of the position." That is substantive. But the instruction says to remove duplicated lines; this line appears earlier: "In order to qualify for this position, resumes must provide sufficient experience and/or education, knowledge, skills, and ability to perform the duties of the position." It's not duplicated elsewhere. Might be worth keeping as a brief statement under Requirements.
Similarly "Applicant resumes are the key means for evaluating skills, knowledge, and abilities as they relate to this position therefore, applicants are encouraged to be clear and specific when describing experience." That's also generic advice; could be omitted as it's not substantive detail about the job. Might be considered boilerplate. I'd lean to omit generic advice.
Also "Help Review our benefits" is boilerplate; omit.
Now we need to output HTML.
Structure:
About the role
...summary...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
under
About the role
. Responsibilities: list of duties. The duties list is long. We need to capture each bullet asunder Requirements or maybe under a generic section? The instruction says we can use only those headings; we could add a paragraph under Requirements that mentions salary dependency. That's okay. - Some positions have special requirements. - Selectee may be required to complete a one (1) year probationary period. - Participation in Direct Deposit/Electronic Fund Transfer within the first 30 days of employment is required. - We utilize E-Verify to confirm selectee's eligibility to work in the United States. (duplicate) - This announcement may be used to fill additional vacancies within 60 days of issuance of selection certificate. - For positions requiring travel more than twice per year, selectee may be required to obtain and maintain in good standing a Government-issued Travel Card for official government travel purposes. - Executive Order 12564 requires a Federal workplace free of illegal drugs. According to the Executive Order, all Federal employees are required to remain drug free throughout their employment. Commander, Navy Installations Command is a Drug-Free Federal Workplace. The use of illegal drugs will not be tolerated, and use of or intoxication by illegal drugs will result in penalties up to and including removal from Federal Service. - Candidates should be committed to improving the efficiency of the Federal government, passionate about the ideals of our American republic, and committed to upholding the rule of law and the United States Constitution. - Help Review our benefits (boilerplate, ignore). We need to avoid duplication: E-Verify appears twice; we can keep one. We'll combine all these into a
- under Requirements.
Now Qualifications: list of KSAs.
From "Qualifications" section:
- Knowledge of and skill in applying industry-standard and organizationally accepted business and systems analysis principles and methods.
- Knowledge of ERP and business systems life cycle management concepts and skill in their application to the organization's current and future systems.
- Knowledge of cost-benefit analysis methods sufficient to evaluate the feasibility of proposed new systems development projects.
- Knowledge of and skill in configuring ERP and business systems to achieve business requirements.
- Knowledge of and skill in understanding organizational business processes and operations.
- Ability to make business processes and operations recommendations for improvements.
- Knowledge of and skill in translating functional requirements into complete design specifications to satisfy changes in organizational requirements.
- Skill in collaborating with applications developers to isolate and solve design problems encountered during testing and implementation phases.
- Ability to communicate effectively both orally and in writing
We'll put each as
- .
Education: "There is no positive educational requirement for this position." Also maybe mention that education is not required but can be considered? We'll just put that as
. Now we need to ensure we don't include any boilerplate like "Help", "Review our benefits", duplicated lines, etc. Also need to remove lines like "Help In order to qualify for this position, resumes must provide sufficient experience and/or education, knowledge, skills, and ability to perform the duties of the position." That's generic; maybe we can incorporate into Requirements? But it's basically saying resumes must show experience etc. That's generic; we could omit as it's not specific substantive detail beyond what's already covered. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. That sentence is somewhat generic but still part of the posting; it's about qualification evaluation. Might be considered boilerplate? It's not a standard EEO but it's about resume evaluation. Could be considered part of Requirements? However we already have Requirements list; we could add a bullet: "Applicants must demonstrate sufficient experience and/or education, knowledge, skills, and ability to perform the duties of the position." That is substantive. But the instruction says to remove duplicated lines; this line appears earlier: "In order to qualify for this position, resumes must provide sufficient experience and/or education, knowledge, skills, and ability to perform the duties of the position." It's not duplicated elsewhere. Might be worth keeping as a brief statement under Requirements. Similarly "Applicant resumes are the key means for evaluating skills, knowledge, and abilities as they relate to this position therefore, applicants are encouraged to be clear and specific when describing experience." That's also generic advice; could be omitted as it's not substantive detail about the job. Might be considered boilerplate. I'd lean to omit generic advice. Also "Help Review our benefits" is boilerplate; omit. Now we need to output HTML. Structure:
About the role
...summary...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications