Logistician IV - Product Support (BCL)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information.
Let's extract content.
First, company description: "Solutions Through Innovative Technologies, Inc. (STI-TEC) specializes in the delivery of professional business and information management services. STI-TEC offers government and commercial clients a comprehensive portfolio of services that identify, manage, distribute and improve business processes related to entities’ most valued resource, information. As a fast-growing solutions provider, established in 2000, total customer satisfaction has remained the cornerstone of our business. Our business model focuses on integrity, loyalty, and trust."
That's about the company; could be "About the role" or maybe "About the company". But heading "About the role" is expected. We'll put that content under About the role.
Then "Position Overview Recognized Industry Leader lifecycle Logistician supports cradle-to-grave development and sustainment. This support includes systems engineering, architecture development and decision making, integrated logistics planning and execution, acquisition assistance (including contracting, finance, and scheduling activities), and overall product support, throughout acquisition lifecycle efforts i.e., design, development, test, production, sustainment improvement modifications, and system disposition."
That's also role overview.
We can combine under About the role.
Now Responsibilities: The "Essential Job Function" list bullet points.
Let's list them:
- Provide technical support and programmatic assistance.
- Develop and deliver draft product support requirements documents to ensure product support considerations are incorporated into system acquisitions.
- Develop and refine the product support requirements, which includes working with Government cross-functional teams to develop accurate assumptions, capture data, and perform data analysis.
- Guide and conduct assessments to facilitate informed decisions on developing and maturing product support elements and adherence to statutory and regulatory directives.
- Implement and manage support functions required to field and maintain the readiness and operational capability of weapon systems, subsystems, and components.
- Oversee product support functions for fielded systems.
- Knowledgeable in the implementation and execution of the twelve (12) Product Support Elements (PSE).
- Provide personnel to manage military airlift cargo using the government transportation network and billing process.
- Contractor personnel must possess intimate knowledge of Financial and Air Clearance Transportation System (FACTS) and Defense Enterprise and Accounting Management System (DEAMS).
- Also provide product support to various space systems to include but not limited to: Development Security Operations (DevSecOps) rapid prototyping, and rapid fielding.
- Develop and maintain technical order management and maintenance activities (TOMA).
- The Contractor shall assist with the development of new technical order development strategies to align with changing Government system acquisition strategies.
We need to put these as
- .
Now Requirements: maybe "Minimum Qualifications" list:
- BA/BS in related field
- Holding or eligible for Active TS SCI
- Subject Matter Expert and Recognized Industry Leader
- 10+ years of experience with establishing product support strategies that align with acquisition strategies and identifying required infrastructures, processes, and procedures to maintain system capabilities.
- Experience with integrating system engineering quantitative design characteristics (reliability, maintainability, etc.) with the functional logistics/integrated product support elements to identify product support resources.
- Experience with integrating the 12 product support elements, procurement and budgeting strategy into logistics activities needed to sustain system fielding.
We could treat these as Requirements.
Qualifications: maybe overlapping; but we could treat Minimum Qualifications as Qualifications. However we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section maybe "Requirements". But we have headings list; we can include both if they have distinct content. However Minimum Qualifications is clearly qualifications. Could treat as "Qualifications". Then "Requirements" could be the essential job functions? But we already have Responsibilities for duties. Usually Requirements = qualifications. Let's decide:
- About the role: company description + position overview.
- Responsibilities: essential job functions list.
- Qualifications: minimum qualifications list.
- Skills: maybe specific skills like FACTS, DEAMS, TOMA, DevSecOps, etc. Could be extracted from responsibilities but we can list as Skills.
- Benefits: benefits list.
- Pay: salary range.
- Schedule: full-time, salary, exempt; alternate work schedules.
We must not invent content. Ensure we preserve all substantive info.
Let's extract Skills: from responsibilities we have knowledge of FACTS, DEAMS, TOMA, DevSecOps rapid prototyping and rapid fielding, technical order management, etc. Also "Knowledgeable in the implementation and execution of the twelve (12) Product Support Elements (PSE)". Also "Provide personnel to manage military airlift cargo using the government transportation network and billing process." That's more duty. But we can list skills as:
- Knowledge of Financial and Air Clearance Transportation System (FACTS)
- Knowledge of Defense Enterprise and Accounting Management System (DEAMS)
- Experience with Development Security Operations (DevSecOps) rapid prototyping and rapid fielding
- Technical order management and maintenance activities (TOMA)
- Implementation and execution of the twelve (12) Product Support Elements (PSE)
- Managing military airlift cargo via government transportation network and billing process
But some of these are also duties. However we can still list as skills.
We must not repeat same content verbatim across sections? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid repetition, but we should avoid duplication? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. If we list same content in both Responsibilities and Skills, that's duplication. Better to avoid duplication: assign each piece to one section.
Thus we can put the detailed duty list under Responsibilities. For Skills, we can extract specific systems knowledge that is not already covered as a duty? But the duty list includes "Contractor personnel must possess intimate knowledge of Financial and Air Clearance Transportation System (FACTS) and Defense Enterprise and Accounting Management System (DEAMS)." That's a requirement/skill. It's also a duty? It's more a requirement. Could be placed under Qualifications or Skills. To avoid duplication, we could move that to Qualifications/Skills and not list under Responsibilities. However the responsibility list includes that as a bullet. If we remove it from Responsibilities, we lose that substantive info. We need to preserve it somewhere. So we can keep it under Responsibilities as a duty, and not duplicate under Skills. Then Skills could be empty? But we must only include a section if there is real specific content. If we don't have distinct skills beyond those already listed, we could omit Skills section. That's okay: "Prefer a few substantive sections over many thin ones." So we can omit Skills if no unique content.
Similarly Benefits: we have list.
Pay: salary range.
Schedule: full-time, salary, exempt; alternate work schedules.
Now we need to ensure we don't include boilerplate like "STI-TEC adheres to federal, state, and local regulations." That's part of Pay section maybe but it's not boilerplate? It's a statement about compliance; could be kept under Pay. It's substantive? It's about adherence to regulations; maybe we can keep.
Also "Whether you’re an experienced professional, a veteran, a former military or civilian federal employee, or a recent graduate, STI-TEC has a career opportunity for you." That's generic fluff; maybe boilerplate? It's not EEO but could be considered filler. Might be considered boilerplate? It's not legal EEO but it's a generic statement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly those categories, but it's somewhat generic marketing. Might be considered filler but not explicitly prohibited. However to be safe, we could keep it under About the role? It's about opportunities. Might be considered part of company description. I'd keep it.
Also "Applicants selected may be subject to a U.S. Government security investigation and must meet eligibility requirements for access to classified information." That's important; keep maybe under Qualifications or Requirements.
"STI-TEC is an equal opportunity employer and values diversity. Employment is decided on the basis of qualifications, merit, and business need. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, disability, protected Veteran status, gender identity and sexual orientation. This policy applies to all terms and conditions of employment, including recruiting, hiring, placement, promotion, termination, layoff, transfer, leaves of absence, compensation and training." That's EEO boilerplate; must remove.
"If you need assistance or an accommodation due to a disability, you may contact us at [email protected] or you may call us at 1+918.583.9900." That's contact info; maybe not boilerplate but could be considered application instructions? It's contact for accommodation; could be considered application instructions? Might be removed as it's not substantive to job description. The instruction says remove application instructions. This is contact for accommodation; could be considered application instructions. Safer to remove.
"This job posting is to identify potential candidates for positions in order to respond to a request for proposal. This job posting, including but not limited to, qualifications, duties, compensation and benefits, is subject to change based on the terms and conditions of the awarded contract and is contingent on STI-TEC being awarded the contract." That's a disclaimer; maybe not boilerplate but could be considered legal? It's about posting subject to change. Might be considered boilerplate? Not explicitly listed but could be considered legal. Safer to remove.
Now we need to output HTML.
Let's craft sections:
About the role
Solutions Through Innovative Technologies, Inc. (STI-TEC) specializes in the delivery of professional business and information management services. STI-TEC offers government and commercial clients a comprehensive portfolio of services that identify, manage, distribute and improve business processes related to entities’ most valued resource, information. As a fast-growing solutions provider, established in 2000, total customer satisfaction has remained the cornerstone of our business. Our business model focuses on integrity, loyalty, and trust. Position Overview Recognized Industry Leader lifecycle Logistician supports cradle-to-grave development and
for prose. We need to preserve all substantive information. Let's extract content. First, company description: "Solutions Through Innovative Technologies, Inc. (STI-TEC) specializes in the delivery of professional business and information management services. STI-TEC offers government and commercial clients a comprehensive portfolio of services that identify, manage, distribute and improve business processes related to entities’ most valued resource, information. As a fast-growing solutions provider, established in 2000, total customer satisfaction has remained the cornerstone of our business. Our business model focuses on integrity, loyalty, and trust." That's about the company; could be "About the role" or maybe "About the company". But heading "About the role" is expected. We'll put that content under About the role. Then "Position Overview Recognized Industry Leader lifecycle Logistician supports cradle-to-grave development and sustainment. This support includes systems engineering, architecture development and decision making, integrated logistics planning and execution, acquisition assistance (including contracting, finance, and scheduling activities), and overall product support, throughout acquisition lifecycle efforts i.e., design, development, test, production, sustainment improvement modifications, and system disposition." That's also role overview. We can combine under About the role. Now Responsibilities: The "Essential Job Function" list bullet points. Let's list them: - Provide technical support and programmatic assistance. - Develop and deliver draft product support requirements documents to ensure product support considerations are incorporated into system acquisitions. - Develop and refine the product support requirements, which includes working with Government cross-functional teams to develop accurate assumptions, capture data, and perform data analysis. - Guide and conduct assessments to facilitate informed decisions on developing and maturing product support elements and adherence to statutory and regulatory directives. - Implement and manage support functions required to field and maintain the readiness and operational capability of weapon systems, subsystems, and components. - Oversee product support functions for fielded systems. - Knowledgeable in the implementation and execution of the twelve (12) Product Support Elements (PSE). - Provide personnel to manage military airlift cargo using the government transportation network and billing process. - Contractor personnel must possess intimate knowledge of Financial and Air Clearance Transportation System (FACTS) and Defense Enterprise and Accounting Management System (DEAMS). - Also provide product support to various space systems to include but not limited to: Development Security Operations (DevSecOps) rapid prototyping, and rapid fielding. - Develop and maintain technical order management and maintenance activities (TOMA). - The Contractor shall assist with the development of new technical order development strategies to align with changing Government system acquisition strategies. We need to put these as
- .
Now Requirements: maybe "Minimum Qualifications" list:
- BA/BS in related field
- Holding or eligible for Active TS SCI
- Subject Matter Expert and Recognized Industry Leader
- 10+ years of experience with establishing product support strategies that align with acquisition strategies and identifying required infrastructures, processes, and procedures to maintain system capabilities.
- Experience with integrating system engineering quantitative design characteristics (reliability, maintainability, etc.) with the functional logistics/integrated product support elements to identify product support resources.
- Experience with integrating the 12 product support elements, procurement and budgeting strategy into logistics activities needed to sustain system fielding.
We could treat these as Requirements.
Qualifications: maybe overlapping; but we could treat Minimum Qualifications as Qualifications. However we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section maybe "Requirements". But we have headings list; we can include both if they have distinct content. However Minimum Qualifications is clearly qualifications. Could treat as "Qualifications". Then "Requirements" could be the essential job functions? But we already have Responsibilities for duties. Usually Requirements = qualifications. Let's decide:
- About the role: company description + position overview.
- Responsibilities: essential job functions list.
- Qualifications: minimum qualifications list.
- Skills: maybe specific skills like FACTS, DEAMS, TOMA, DevSecOps, etc. Could be extracted from responsibilities but we can list as Skills.
- Benefits: benefits list.
- Pay: salary range.
- Schedule: full-time, salary, exempt; alternate work schedules.
We must not invent content. Ensure we preserve all substantive info.
Let's extract Skills: from responsibilities we have knowledge of FACTS, DEAMS, TOMA, DevSecOps rapid prototyping and rapid fielding, technical order management, etc. Also "Knowledgeable in the implementation and execution of the twelve (12) Product Support Elements (PSE)". Also "Provide personnel to manage military airlift cargo using the government transportation network and billing process." That's more duty. But we can list skills as:
- Knowledge of Financial and Air Clearance Transportation System (FACTS)
- Knowledge of Defense Enterprise and Accounting Management System (DEAMS)
- Experience with Development Security Operations (DevSecOps) rapid prototyping and rapid fielding
- Technical order management and maintenance activities (TOMA)
- Implementation and execution of the twelve (12) Product Support Elements (PSE)
- Managing military airlift cargo via government transportation network and billing process
But some of these are also duties. However we can still list as skills.
We must not repeat same content verbatim across sections? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid repetition, but we should avoid duplication? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. If we list same content in both Responsibilities and Skills, that's duplication. Better to avoid duplication: assign each piece to one section.
Thus we can put the detailed duty list under Responsibilities. For Skills, we can extract specific systems knowledge that is not already covered as a duty? But the duty list includes "Contractor personnel must possess intimate knowledge of Financial and Air Clearance Transportation System (FACTS) and Defense Enterprise and Accounting Management System (DEAMS)." That's a requirement/skill. It's also a duty? It's more a requirement. Could be placed under Qualifications or Skills. To avoid duplication, we could move that to Qualifications/Skills and not list under Responsibilities. However the responsibility list includes that as a bullet. If we remove it from Responsibilities, we lose that substantive info. We need to preserve it somewhere. So we can keep it under Responsibilities as a duty, and not duplicate under Skills. Then Skills could be empty? But we must only include a section if there is real specific content. If we don't have distinct skills beyond those already listed, we could omit Skills section. That's okay: "Prefer a few substantive sections over many thin ones." So we can omit Skills if no unique content.
Similarly Benefits: we have list.
Pay: salary range.
Schedule: full-time, salary, exempt; alternate work schedules.
Now we need to ensure we don't include boilerplate like "STI-TEC adheres to federal, state, and local regulations." That's part of Pay section maybe but it's not boilerplate? It's a statement about compliance; could be kept under Pay. It's substantive? It's about adherence to regulations; maybe we can keep.
Also "Whether you’re an experienced professional, a veteran, a former military or civilian federal employee, or a recent graduate, STI-TEC has a career opportunity for you." That's generic fluff; maybe boilerplate? It's not EEO but could be considered filler. Might be considered boilerplate? It's not legal EEO but it's a generic statement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly those categories, but it's somewhat generic marketing. Might be considered filler but not explicitly prohibited. However to be safe, we could keep it under About the role? It's about opportunities. Might be considered part of company description. I'd keep it.
Also "Applicants selected may be subject to a U.S. Government security investigation and must meet eligibility requirements for access to classified information." That's important; keep maybe under Qualifications or Requirements.
"STI-TEC is an equal opportunity employer and values diversity. Employment is decided on the basis of qualifications, merit, and business need. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, disability, protected Veteran status, gender identity and sexual orientation. This policy applies to all terms and conditions of employment, including recruiting, hiring, placement, promotion, termination, layoff, transfer, leaves of absence, compensation and training." That's EEO boilerplate; must remove.
"If you need assistance or an accommodation due to a disability, you may contact us at [email protected] or you may call us at 1+918.583.9900." That's contact info; maybe not boilerplate but could be considered application instructions? It's contact for accommodation; could be considered application instructions? Might be removed as it's not substantive to job description. The instruction says remove application instructions. This is contact for accommodation; could be considered application instructions. Safer to remove.
"This job posting is to identify potential candidates for positions in order to respond to a request for proposal. This job posting, including but not limited to, qualifications, duties, compensation and benefits, is subject to change based on the terms and conditions of the awarded contract and is contingent on STI-TEC being awarded the contract." That's a disclaimer; maybe not boilerplate but could be considered legal? It's about posting subject to change. Might be considered boilerplate? Not explicitly listed but could be considered legal. Safer to remove.
Now we need to output HTML.
Let's craft sections:
About the role
Solutions Through Innovative Technologies, Inc. (STI-TEC) specializes in the delivery of professional business and information management services. STI-TEC offers government and commercial clients a comprehensive portfolio of services that identify, manage, distribute and improve business processes related to entities’ most valued resource, information. As a fast-growing solutions provider, established in 2000, total customer satisfaction has remained the cornerstone of our business. Our business model focuses on integrity, loyalty, and trust. Position Overview Recognized Industry Leader lifecycle Logistician supports cradle-to-grave development and