Senior Logistician
Command Holdings, a Pequot Company · Baltimore, MD · 1 mo ago
On-siteManagement$59k–$74k/yrFull-time
We need to output HTML fragment with sections only if content present. Use .
Requirements (Basic Qualifications) list:
- Must be able to obtain DHS Suitability.
- Ability to pass a Tier 1 federal background investigation including fingerprinting, more information can be found here: https://www.dcsa.mil/Personnel-Vetting/Background-Investigations-for-Security-HR-Professionals/Start-a-Background-Investigation/Case-Types-Forms/
- Ability to act as team/contract lead.
- Understanding of the USCG, SBPL.
- Experience in logistics support of USCG maintenance and experience with the USCG Logistics Business Model.
- Experience utilizing FLS and NESSS.
- Familiarity with USCG software.
- Must be a U.S. citizen.
- Outstanding communication skills, influencing abilities, and client focus.
- Demonstrated proficiency in using all Microsoft Office applications.
- Professional proficiency in English is required.
- Ability to access federal facilities in compliance with Real ID. More information about Real ID can be found here: https://www.dhs.gov/real-id/about-real-id and at https://www.tsa.gov/travel/security-screening/identification.
- Applicants must be currently authorized to work in the United States on a full-time basis.
- CeLeen will not sponsor applicants for work visas for this position.
We may keep the URLs? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Should we keep the URLs? They are part of the requirement. Probably keep them as part of the list item text.
Qualifications (Preferred Qualifications) list:
- Bachelor's Degree.
- Active DHS Suitability.
- Five (5) years engaged in logistics support of Small Boat maintenance.
- A minimum of five (5) years of experience with the Coast Guard Logistics Business Model.
- Three (3) years of experience utilizing FLS and NESSS (preferred but not required).
- Previous experience in leading a team, including providing guidance and training for team members.
- Ability to coordinate with the SBPL ACMS section chief in case of fill gaps due to personnel shortage, surge in workload, or adding new asset types into the IT system.
Skills: we could extract from requirements: Outstanding communication skills, influencing abilities, client focus; Demonstrated proficiency in using all Microsoft Office applications; Professional proficiency in English is required; Ability to act as team/contract lead; Ability to access federal facilities in compliance with Real ID; Ability to coordinate with SBPL ACMS section chief (maybe more qualification). But we already have those in requirements/qualifications. To avoid duplication, maybe we create Skills section for those skill-based items not covered elsewhere. However risk of duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we split, we might duplicate content across sections, which is not summarizing away detail but repeating. Might be okay but could be considered duplication. Better to keep skills within Requirements or Qualifications. But we need to include Skills section only if posting has real, specific content for it. The posting does mention skills explicitly: "Outstanding communication skills, influencing abilities, and client focus." "Demonstrated proficiency in using all Microsoft Office applications." "Professional proficiency in English is required." Those are skills. We could create a Skills section with those items. However they also appear in Requirements list. To avoid duplication, we could move them from Requirements to Skills, but then we would lose them from Requirements. The instruction says preserve ALL substantive information; we can reorganize but not lose. So we could keep them in Requirements and also have Skills section? That would duplicate. Better to move them to Skills and remove from Requirements? But then we would lose the explicit mention that they are requirements. However they are still present in Skills section, so information preserved. The requirement list would then lack those items; but they are still present somewhere else. The instruction does not forbid duplication, but says preserve ALL substantive information; duplication is not losing info. It's okay to have duplication? Might be considered redundant but not violating. However they said "Prefer a few substantive sections over many thin ones." So maybe better to keep skills within Requirements or Qualifications and not create a separate Skills section unless there are distinct skill items not covered elsewhere. Since the skills are already covered, we could omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if we have any Schedule content: Travel 10-20% / Occasional travel. That's not schedule but travel. Could be considered schedule? Not exactly. We'll omit Schedule.
Now craft HTML.
We need
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse posting. We have description: "CeLeen, an operating firm of Command Holdings, is seeking a Senior Logistician to support the US Coast Guard Surface Forces Logistics Center (SFLC), Fleet Logistics Systems Support (FLSS), supporting the Small Boat Product Line (SBPL). The Senior Logistician may perform the following actions and analysis using data in the Fleet Logistic System (FLS) and applicable standards." Then "Responsibilities May Include, But Are Not Limited To" list items. We need to include About the role section: maybe a paragraph summarizing role. Responsibilities: list items. Requirements: list of basic qualifications. Qualifications: maybe preferred qualifications? The instruction says sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: Basic Qualifications -> Requirements. Preferred Qualifications -> Qualifications. Skills maybe from "Outstanding communication skills..." etc. Could be part of Requirements or Qualifications. But we need to follow instruction: include a section only when posting has real, specific content for it. So we need to see if we have content for each. We have: - About the role: we have introductory paragraph describing role. Good. - Responsibilities: we have list. - Requirements: we have Basic Qualifications list. - Qualifications: we have Preferred Qualifications list. - Skills: we have "Outstanding communication skills, influencing abilities, and client focus. Demonstrated proficiency in using all Microsoft Office applications. Professional proficiency in English is required." Also maybe "Ability to act as team/contract lead." Could be considered skills. We'll extract. - Benefits: we have list. - Pay: we have "Expected salary range: $59,000 - $74,000". So Pay section. - Schedule: we have "Travel 10-20% / Occasional travel." Also maybe work environment moderate noise etc. But schedule specifically maybe not given. Travel could be considered schedule? The instruction: include Schedule section only if posting actually states them. The posting mentions Travel 10-20% / Occasional travel. That's about travel, not schedule. No explicit schedule like full-time, shift, etc. So we may omit Schedule. Also we have Work Environment etc. Could be omitted as not a section. We need to remove boilerplate: EEO, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove repeated "CeLeen, an operating firm of Command Holdings, a Pequot company, is a tribally-owned firm..." etc. That's boilerplate about company; we should drop it as not substantive? The instruction: 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. The company description may be considered boilerplate? It's not exactly EEO but it's about the firm. Might be considered background but not required. However it's not a requirement/responsibility etc. Could be considered part of About the role? The About the role could include that CeLeen is an operating firm of Command Holdings etc. But we already have introductory sentence. The later paragraph about CeLeen being tribally-owned etc is likely boilerplate about the company; we can drop. Also remove "Please send your request to the Human Resources Team." etc. We need to keep all substantive info: responsibilities list, requirements list, preferred qualifications, skills, benefits, pay. Let's extract details. Responsibilities list (from text): - Assessing equipment interchangeability/substitution needs and the impact of Coast Guard, Navy, and OGA equipment and small boat support programs on SBPL support practices, recommending modifications as needed. - Applying the ten (10) elements of logistics, Reliability-Centered Maintenance principles, and applicable standards (MIL-P-24534, SAE JA1011, ABS RCM, MSG-3) to SBPL supported assets, and draft Equipment Integrated Logistics Support Plans. - Generating, maintaining, and analyzing maintenance standards, parts information, and allowance lists in FLS, FLS-MAM, and NESSS. - Supporting CORs and the ACMS section by maintaining, developing, and analyzing maintenance and supply records, and by reviewing MPC cover sheets and sign-off sheets against the current CG-LIMS-STIP. - Maintaining the FLS-MAM database: record maintenance performed at CCBP locations, update task statuses, run reports (e.g., MDLs, Configuration Reports), enter completed actions within 3 working days (escalating any delays with a corrective action plan), archive completed actions, ensure data/CIFD accuracy, and verify migration of maintenance and configuration changes from FLS. We need to keep each as
for each section heading. Inside each section, use
for prose,
- for lists.
About the role: we can have a paragraph: "CeLeen, an operating firm of Command Holdings, is seeking a Senior Logistician to support the US Coast Guard Surface Forces Logistics Center (SFLC), Fleet Logistics Systems Support (FLSS), supporting the Small Boat Product Line (SBPL). The Senior Logistician may perform the following actions and analysis using data in the Fleet Logistic System (FLS) and applicable standards."
That's it.
Responsibilities: heading
Responsibilities
then- with each responsibility.
Requirements: heading
Requirements
then- with each basic qualification.
Qualifications: heading
Qualifications
then- with each preferred qualification.
Benefits: heading
Benefits
then- with each benefit.
Pay: heading
Pay
thenwith salary range. We need to ensure we don't include any boilerplate like "CeLeen offers a competitive benefits plan including:" we can keep as intro sentence before list? The instruction: use
for prose. So we could have a
"CeLeen offers a competitive benefits plan including:" then
- . That's fine.
Similarly for responsibilities we could have intro sentence but we already have heading; we can keep just list.
Now check for any duplicated lines: we need to ensure we didn't inadvertently include duplicated lines like "CeLeen, an operating firm of Command Holdings, a Pequot company, is a tribally-owned firm providing management consulting services to U.S. government agencies." We omitted that.
Also removed EEO etc.
Now produce HTML fragment.
Let's list items precisely.
Responsibilities items:
1. Assessing equipment interchangeability/substitution needs and the impact of Coast Guard, Navy, and OGA equipment and small boat support programs on SBPL support practices, recommending modifications as needed.
2. Applying the ten (10) elements of logistics, Reliability-Centered Maintenance principles, and applicable standards (MIL-P-24534, SAE JA1011, ABS RCM, MSG-3) to SBPL supported assets, and draft Equipment Integrated Logistics Support Plans.
3. Generating, maintaining, and analyzing maintenance standards, parts information, and allowance lists in FLS, FLS-MAM, and NESSS.
4. Supporting CORs and the ACMS section by maintaining, developing, and analyzing maintenance and supply records, and by reviewing MPC cover sheets and sign