FMS Acquisition Manager, Journeyman
or drop it. We could include a short paragraph with location and work arrangement maybe? But they said do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a
with location and work arrangement? Not sure if that's considered minor metadata. Probably we can include a short paragraph summarizing location and work arrangement. But they said preserve ALL substantive information; location and work arrangement are substantive? Might be considered metadata but still info. Safer to include a short
with location and work arrangement. We must not include cookie/navigation/legal/EEO etc. Remove EEO lines. Also remove "At COLSA, people are our most valuable resource..." maybe that's boilerplate? It's a culture statement; could be considered substantive? Might be okay to keep? It's not a standard section; but we could incorporate into a paragraph maybe under About the role? However they said preserve ALL substantive information; that statement is about culture, could be considered substantive. But we could include it in a
under About the role. We need sections: About the role (General Summary), Responsibilities, Requirements (or Qualifications), Benefits. We must use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not create Pay/Schedule sections unless posting actually states them. No specific salary, so omit Pay. No schedule details besides On Site: 100% maybe we could include Schedule? They said only if posting actually states them. It does state Work Arrangement On Site: 100%. That's schedule info. Could we make a Schedule section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Work Arrangement On Site: 100%. That's schedule info. So we could include a Schedule section with that detail. However they also said prefer a few substantive sections over many thin ones. Might be better to fold that into About the role paragraph. But it's specific. I'd include a short
under About the role that mentions location and work arrangement.
We must not repeat job title as heading. No job title given in snippet; we ignore.
Now extract content.
General Summary paragraph: "The candidate will demonstrate an understanding of DoD acquisition processes and analytical methods or techniques to gather, analyze, and evaluate information required by the US government (USG). Assist in drawing conclusions and devising solutions to problems relating to improvement of acquisition effectiveness and compliance; assist with developing and drafting acquisition documentation and assisting with quality control; assist with performing work measurement studies, program or operations efficiency reviews, cost studies, or workload change impact analyses; and rely upon and use automated management information systems in performing fact-finding, analytical, and advisory functions."
That's the summary.
Responsibilities: long list. Need to turn into
- items. We must preserve all substantive information; we can split by sentences or semicolons. We'll create list items each starting with a verb.
We need to be careful not to omit any. Let's parse responsibilities block:
"Support key acquisition events and reviews as needed such as System Requirements Reviews (SRR), Preliminary Design Reviews (PDR), Critical Design Reviews (CDR), Test Readiness Reviews (TRR), Technical Coordination Meetings (TCM), Functional Configuration Audits (FCA), Physical Configuration Audits (PCA), Production Readiness Reviews (PRR), and others as applicable.
Assist with establishing and maintaining databases and assist in the development and analysis of key program metrics.
Assist with tracking technical metrics and reporting status.
Apply an understanding of DoD and AF program/project analysis to assist with planning, organizing, completing, and presenting assessments of program/project activity, management concepts, analyses, studies, and procedures to the USG; Assist with performing analyses to support program strategy decisions and courses of action; Evaluate implications of existing or proposed projects, programs, processes, and policies/laws and recommend improvements to the USG.
Support the development, review, and approval processes for requirements document development and the Joint Capabilities Integration and Development System (JCIDS) process and staffing. Assist in translating user requirements documents such as the Capability Development Document (CDD), Capability Production Document (CPD), and Concept of Operations (CONOPS) into Request for Proposal (RFP) documentation for the directorate.
Support USG implementation of policies, processes, and tools for capability planning and development. Assist capabilities managers in arranging and supporting High Powered Teams (HPTs) for capabilities development. Assist in developing and implementing capability-based planning processes for AFMC. Assist in facilitating AFMC support to Capability Review and Risk Assessment (CRRA) and integrate AFMC/Air Force Space Command (AFSPC) capability-based planning activities and by providing input for Integrated Summits (I-SUMMITs).
Promote the use of Modeling Simulation & Analysis (MS&A) throughout the acquisition lifecycle process and foster the development and maintenance of common use MS&A tools useful to the divisions/groups/industry.
Assist in integration of intelligence information and infrastructure to ensure cross-enterprise capabilities planning and system acquisition.
Provide support for all aspects of program cost, schedule, and performance. Assist with Data Item Descriptions (DIDs), Contract Data Requirements Lists (CDRLs), data calls, and reviews. Support and assist in planning, organizing, and managing of general and critical aspects of the development, production, and/or deployment of the systems, subsystems, and equipment as well as the acquisition program management of the full life cycle requirements.
Develop and collect technical data and inputs for staff summary packages to support coordination and signature of all associated documents for milestone approval.
Assist in producing or supporting the development of draft documentation and presentation materials as requested or necessitated by programmatic limits based on cost, schedule, and performance.
Assist with developing, analyzing, reporting, and maintaining schedules and metrics that are needed to track program status. Assist with providing schedule analysis of overarching program Integrated Master Schedule (IMS) with knowledge of OEM-specific scheduling tools, or other tools mandated by the USG and integration techniques.
Interface and coordinate with lateral USG organizations, including but not limited to, headquarters, major commands, aircraft wings/squadrons, test agencies, and USAF Centers or other external agencies to accomplish assigned tasks. Assist with the resolution of programmatic issues including, but not limited to, interfacing/querying Air Staff, Air Force Major Command, and DoD personnel.
Assist with providing technical support, planning, coordination, and participation in integrated program reviews and conferences, including but not limited to, the following: executive, readiness, technical, budget, design, weapon system, requirement working groups, supportability, and management reviews.
Support DAG and PEG processes, including but not limited to, Execution Reviews, Monthly Acquisition Report (MAR), Defense Acquisition Executive Summary (DAES), Selected Acquisition Reports (SAR), other acquisition reports.
Participate in process improvement activities as members of, or advisors to, Integrated Product Teams (IPTs) and Product/Process Improvement Working Groups (PIWGs).
Assist the SAPMs and Defense Security Assistance Management System (DSAMS) and Security Assistance Manpower Requirements System (SAMRS) technical support personnel in all phases of the planning, development, coordination, and implementation of FMS, pseudo-FMS, Section 1206, and SDAF cases.
Be proficient in the use of FMS-specific software and Management Information System (MIS) applications.
Facilitate meetings as needed.
Create/Manage CDRLs.
Review Integrated Master Schedule (IMS).
Create PCN.
Create Work Requirements Definition (WRD).
Demonstrate an understanding of PWS, SOW, DIDs, CDRLs, & ASP.
Conduct Market Research, draft Early Strategy and Issues Session (ESIS), Acquisition Strategy Plan (ASP), Quality Assurance Surveillance Plan (QASP) and Virtual Staff Summary Sheet (vSSS)."
That's many items. We'll create
- for each sentence or clause. Might be long but okay.
Requirements/Qualifications: "Required Experience One of the following: BA/BS degree, and ten (10) years of experience in the respective technical/professional discipline being performed, three (3) of which must be in the DoD - OR-HS Diploma, and fifteen (15) years of directly related experience, five (5) of which must be in the DoD Ability to obtain and maintain a Secret security clearance; U.S. Citizenship required Demonstrate proficiency in the use of Microsoft Office Applications (Outlook, Word, Excel, PowerPoint, SharePoint, and Teams), & Adobe Acrobat Preferred Qualifications Prior FMS experience Knowledge of CCaR, PIIE, WAWF, FAR, and DFAR Demonstrate an understanding of Form 1067, and Form 206. Knowledge of Commercial Asset Visibility Air Force (CAV AF) system"
We need to separate Required Experience and Preferred Qualifications. Could make two subsections? But we only have h3 for section headings; we could have a single Requirements section with both required and preferred lists. Use
- for each.
We must not include boilerplate like "Applicant selected will be subject to a government security investigation..." that's part of requirements? It's a condition; we could include as a list item.
Also "COLSA Corporation is an Equal Opportunity Employer..." is EEO boilerplate; remove.
Also "This position will be posted for a minimum of 3 business days..." is boilerplate; remove.
Also "Learn about our employee-centric culture and benefits here: https://www.colsa.com/culture_benefits" is a link; maybe we can keep as part of Benefits? But it's a link to culture/benefits; we already have Benefits section; we could include that link as a
maybe. But they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This link is not exactly boilerplate; it's a reference to culture/benefits. Might be okay to keep as a
under Benefits? But we already have benefits list; we could add a
with that link.
But we must not invent or summarize away detail. Keep link.
Now Benefits: list: "Medical, Dental, Vision, Life Insurance, Short-Term Disability, Long-Term Disability, Accidental Death & Dismemberment, Supplemental Income Protection Programs, 401(k) with company match, Flexible Spending Accounts, Employee Assistance Program, Education & Certification Reimbursement, Employee Discount Program, Paid Time Off and Holidays."
Also maybe mention "comprehensive and customizeable benefits program". We'll include that as prose then list.
Now construct HTML.
We'll start with a
for location and work arrangement? Could incorporate into About the role paragraph: maybe add a sentence: "Located in Warner Robins, Georgia, this is an on-site, full-time position." That preserves info.
Thus About the role section:
About the role
... summary plus location/work arrangement.
Now Responsibilities: Responsibilities
... items.
Now Requirements: Requirements
... items.
Now Benefits: Benefits
COLSA offers a comprehensive and customizable benefits program which includes:
for prose. We must not create Pay/Schedule sections unless posting actually states them. No specific salary, so omit Pay. No schedule details besides On Site: 100% maybe we could include Schedule? They said only if posting actually states them. It does state Work Arrangement On Site: 100%. That's schedule info. Could we make a Schedule section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Work Arrangement On Site: 100%. That's schedule info. So we could include a Schedule section with that detail. However they also said prefer a few substantive sections over many thin ones. Might be better to fold that into About the role paragraph. But it's specific. I'd include a short
under About the role that mentions location and work arrangement. We must not repeat job title as heading. No job title given in snippet; we ignore. Now extract content. General Summary paragraph: "The candidate will demonstrate an understanding of DoD acquisition processes and analytical methods or techniques to gather, analyze, and evaluate information required by the US government (USG). Assist in drawing conclusions and devising solutions to problems relating to improvement of acquisition effectiveness and compliance; assist with developing and drafting acquisition documentation and assisting with quality control; assist with performing work measurement studies, program or operations efficiency reviews, cost studies, or workload change impact analyses; and rely upon and use automated management information systems in performing fact-finding, analytical, and advisory functions." That's the summary. Responsibilities: long list. Need to turn into
- items. We must preserve all substantive information; we can split by sentences or semicolons. We'll create list items each starting with a verb.
We need to be careful not to omit any. Let's parse responsibilities block:
"Support key acquisition events and reviews as needed such as System Requirements Reviews (SRR), Preliminary Design Reviews (PDR), Critical Design Reviews (CDR), Test Readiness Reviews (TRR), Technical Coordination Meetings (TCM), Functional Configuration Audits (FCA), Physical Configuration Audits (PCA), Production Readiness Reviews (PRR), and others as applicable.
Assist with establishing and maintaining databases and assist in the development and analysis of key program metrics.
Assist with tracking technical metrics and reporting status.
Apply an understanding of DoD and AF program/project analysis to assist with planning, organizing, completing, and presenting assessments of program/project activity, management concepts, analyses, studies, and procedures to the USG; Assist with performing analyses to support program strategy decisions and courses of action; Evaluate implications of existing or proposed projects, programs, processes, and policies/laws and recommend improvements to the USG.
Support the development, review, and approval processes for requirements document development and the Joint Capabilities Integration and Development System (JCIDS) process and staffing. Assist in translating user requirements documents such as the Capability Development Document (CDD), Capability Production Document (CPD), and Concept of Operations (CONOPS) into Request for Proposal (RFP) documentation for the directorate.
Support USG implementation of policies, processes, and tools for capability planning and development. Assist capabilities managers in arranging and supporting High Powered Teams (HPTs) for capabilities development. Assist in developing and implementing capability-based planning processes for AFMC. Assist in facilitating AFMC support to Capability Review and Risk Assessment (CRRA) and integrate AFMC/Air Force Space Command (AFSPC) capability-based planning activities and by providing input for Integrated Summits (I-SUMMITs).
Promote the use of Modeling Simulation & Analysis (MS&A) throughout the acquisition lifecycle process and foster the development and maintenance of common use MS&A tools useful to the divisions/groups/industry.
Assist in integration of intelligence information and infrastructure to ensure cross-enterprise capabilities planning and system acquisition.
Provide support for all aspects of program cost, schedule, and performance. Assist with Data Item Descriptions (DIDs), Contract Data Requirements Lists (CDRLs), data calls, and reviews. Support and assist in planning, organizing, and managing of general and critical aspects of the development, production, and/or deployment of the systems, subsystems, and equipment as well as the acquisition program management of the full life cycle requirements.
Develop and collect technical data and inputs for staff summary packages to support coordination and signature of all associated documents for milestone approval.
Assist in producing or supporting the development of draft documentation and presentation materials as requested or necessitated by programmatic limits based on cost, schedule, and performance.
Assist with developing, analyzing, reporting, and maintaining schedules and metrics that are needed to track program status. Assist with providing schedule analysis of overarching program Integrated Master Schedule (IMS) with knowledge of OEM-specific scheduling tools, or other tools mandated by the USG and integration techniques.
Interface and coordinate with lateral USG organizations, including but not limited to, headquarters, major commands, aircraft wings/squadrons, test agencies, and USAF Centers or other external agencies to accomplish assigned tasks. Assist with the resolution of programmatic issues including, but not limited to, interfacing/querying Air Staff, Air Force Major Command, and DoD personnel.
Assist with providing technical support, planning, coordination, and participation in integrated program reviews and conferences, including but not limited to, the following: executive, readiness, technical, budget, design, weapon system, requirement working groups, supportability, and management reviews.
Support DAG and PEG processes, including but not limited to, Execution Reviews, Monthly Acquisition Report (MAR), Defense Acquisition Executive Summary (DAES), Selected Acquisition Reports (SAR), other acquisition reports.
Participate in process improvement activities as members of, or advisors to, Integrated Product Teams (IPTs) and Product/Process Improvement Working Groups (PIWGs).
Assist the SAPMs and Defense Security Assistance Management System (DSAMS) and Security Assistance Manpower Requirements System (SAMRS) technical support personnel in all phases of the planning, development, coordination, and implementation of FMS, pseudo-FMS, Section 1206, and SDAF cases.
Be proficient in the use of FMS-specific software and Management Information System (MIS) applications.
Facilitate meetings as needed.
Create/Manage CDRLs.
Review Integrated Master Schedule (IMS).
Create PCN.
Create Work Requirements Definition (WRD).
Demonstrate an understanding of PWS, SOW, DIDs, CDRLs, & ASP.
Conduct Market Research, draft Early Strategy and Issues Session (ESIS), Acquisition Strategy Plan (ASP), Quality Assurance Surveillance Plan (QASP) and Virtual Staff Summary Sheet (vSSS)."
That's many items. We'll create
- for each sentence or clause. Might be long but okay.
Requirements/Qualifications: "Required Experience One of the following: BA/BS degree, and ten (10) years of experience in the respective technical/professional discipline being performed, three (3) of which must be in the DoD - OR-HS Diploma, and fifteen (15) years of directly related experience, five (5) of which must be in the DoD Ability to obtain and maintain a Secret security clearance; U.S. Citizenship required Demonstrate proficiency in the use of Microsoft Office Applications (Outlook, Word, Excel, PowerPoint, SharePoint, and Teams), & Adobe Acrobat Preferred Qualifications Prior FMS experience Knowledge of CCaR, PIIE, WAWF, FAR, and DFAR Demonstrate an understanding of Form 1067, and Form 206. Knowledge of Commercial Asset Visibility Air Force (CAV AF) system"
We need to separate Required Experience and Preferred Qualifications. Could make two subsections? But we only have h3 for section headings; we could have a single Requirements section with both required and preferred lists. Use
- for each.
We must not include boilerplate like "Applicant selected will be subject to a government security investigation..." that's part of requirements? It's a condition; we could include as a list item.
Also "COLSA Corporation is an Equal Opportunity Employer..." is EEO boilerplate; remove.
Also "This position will be posted for a minimum of 3 business days..." is boilerplate; remove.
Also "Learn about our employee-centric culture and benefits here: https://www.colsa.com/culture_benefits" is a link; maybe we can keep as part of Benefits? But it's a link to culture/benefits; we already have Benefits section; we could include that link as a
maybe. But they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This link is not exactly boilerplate; it's a reference to culture/benefits. Might be okay to keep as a
under Benefits? But we already have benefits list; we could add a
with that link. But we must not invent or summarize away detail. Keep link. Now Benefits: list: "Medical, Dental, Vision, Life Insurance, Short-Term Disability, Long-Term Disability, Accidental Death & Dismemberment, Supplemental Income Protection Programs, 401(k) with company match, Flexible Spending Accounts, Employee Assistance Program, Education & Certification Reimbursement, Employee Discount Program, Paid Time Off and Holidays." Also maybe mention "comprehensive and customizeable benefits program". We'll include that as prose then list. Now construct HTML. We'll start with a
for location and work arrangement? Could incorporate into About the role paragraph: maybe add a sentence: "Located in Warner Robins, Georgia, this is an on-site, full-time position." That preserves info. Thus About the role section:
About the role
... summary plus location/work arrangement.
Now Responsibilities:Responsibilities
- ... items.
Now Requirements:
Requirements
- ... items.
Now Benefits:
Benefits
COLSA offers a comprehensive and customizable benefits program which includes:
- for each.
We must not include boilerplate like "Applicant selected will be subject to a government security investigation..." that's part of requirements? It's a condition; we could include as a list item.
Also "COLSA Corporation is an Equal Opportunity Employer..." is EEO boilerplate; remove.
Also "This position will be posted for a minimum of 3 business days..." is boilerplate; remove.
Also "Learn about our employee-centric culture and benefits here: https://www.colsa.com/culture_benefits" is a link; maybe we can keep as part of Benefits? But it's a link to culture/benefits; we already have Benefits section; we could include that link as a
- for each sentence or clause. Might be long but okay.
Requirements/Qualifications: "Required Experience One of the following: BA/BS degree, and ten (10) years of experience in the respective technical/professional discipline being performed, three (3) of which must be in the DoD - OR-HS Diploma, and fifteen (15) years of directly related experience, five (5) of which must be in the DoD Ability to obtain and maintain a Secret security clearance; U.S. Citizenship required Demonstrate proficiency in the use of Microsoft Office Applications (Outlook, Word, Excel, PowerPoint, SharePoint, and Teams), & Adobe Acrobat Preferred Qualifications Prior FMS experience Knowledge of CCaR, PIIE, WAWF, FAR, and DFAR Demonstrate an understanding of Form 1067, and Form 206. Knowledge of Commercial Asset Visibility Air Force (CAV AF) system"
We need to separate Required Experience and Preferred Qualifications. Could make two subsections? But we only have h3 for section headings; we could have a single Requirements section with both required and preferred lists. Use