Senior Program Analyst / Schedule Architect
Blue Water Thinking · United States · 1 mo ago
RemoteRemoteArt & Creative$115k–$130k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Blue Water Thinking" (company description) then "Job Description:" then responsibilities, qualifications, eligibility, compensation, benefits, etc.
We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections that have real specific content.
We must not repeat job title as heading. No Job ID etc.
We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove "Reasonable Accommodation for Applicants", "Our Commitment to Equal Employment Opportunity", "Applying for this Job:" etc. Those are boilerplate/EEO/application instructions, should be removed.
We need to keep: About Blue Water Thinking (company description) maybe as "About the role"? Actually "About the role" heading is for role description. The company description could be under "About the role" or maybe "About Blue Water Thinking". The instruction says use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections that have real specific content.
We must not repeat job title as heading. No Job ID etc.
We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove "Reasonable Accommodation for Applicants", "Our Commitment to Equal Employment Opportunity", "Applying for this Job:" etc. Those are boilerplate/EEO/application instructions, should be removed.
We need to keep: About Blue Water Thinking (company description) maybe as "About the role"? Actually "About the role" heading is for role description. The company description could be under "About the role" or maybe "About Blue Water Thinking". The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly.
We have:
- About Blue Water Thinking (company overview) -> could be "About the role" or maybe "About Blue Water Thinking". The instruction says "About the role" is an example; we can use that heading for company/role overview. We'll include that.
- Job Description: includes description of role and mandates. Could be part of "About the role" or separate "Job Description". But we only have allowed headings list; we could put role description under "About the role". We'll combine.
- Responsibilities: we have a big list. Use Responsibilities then - items.
- Minimum Qualifications: could be "Requirements" or "Qualifications". We'll use "Qualifications" heading for minimum qualifications. Possibly also "Preferred Qualifications" could be under same heading or separate? We could have "Qualifications" covering both minimum and preferred, but we need to preserve all info. Could split into "Minimum Qualifications" and "Preferred Qualifications" but those are not in the allowed list; but we could still use
for them? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings.
Thus:
- About the role: includes company overview and job description summary.
- Responsibilities: as given.
- Requirements: maybe includes Minimum Qualifications? Or we could put Minimum Qualifications under Requirements, and Preferred Qualifications under Skills? Or Skills could include preferred qualifications like certifications, experience with specific systems. Let's think.
We have sections: Minimum Qualifications, Preferred Qualifications, Eligibility (citizenship, clearance), Compensation (Pay), Benefits.
We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide mapping:
- Requirements: could contain Minimum Qualifications (education, experience, etc.)
- Qualifications: could contain Preferred Qualifications (certifications, etc.)
- Skills: could contain specific technical skills (Primavera P6, Microsoft Project, Power BI, SharePoint, etc.) but those are already in qualifications. Might be redundant.
Better: Use Requirements for Minimum Qualifications, Qualifications for Preferred Qualifications, Skills for technical/tool skills (maybe overlapping). But we must not invent headings with filler. If we put Skills but have no specific skill list beyond what's already in qualifications, we could still list them.
Alternatively, we could combine Minimum and Preferred under Qualifications and skip Requirements and Skills. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So maybe we just have About the role, Responsibilities, Qualifications (covering both min and pref), Benefits, Pay. That's four sections. That seems reasonable.
We must not include Schedule section because no schedule info (like work schedule). Not present.
Thus output:
About the role
... company overview and job description summary ...
Responsibilities
- ... each responsibility ...
Qualifications
... Minimum Qualifications ...
... Preferred Qualifications ...
Benefits
- ... benefits ...
Pay
Salary range: $115k-$130k ...
We need to preserve all substantive info. Let's extract.
Company overview paragraph: "About Blue Water Thinking Guided by our principles of value generation, continuous innovation, customer-centricity, and vested collaboration, Blue Water Thinking proudly supports our Federal clients in achieving their Agency goals. Founded by a decorated twenty-eight year Veteran of the United States Army, Blue Water Thinking understands and supports the mission of our Nation's war fighters, Veterans, their families and caretakers. Leveraging our executive team's military experience and private and public sector consulting expertise, Blue Water Thinking takes an integrated "one-team" approach and brings to bear best-fit solutions, thought leadership, and grit to meet our client's transformational needs. Fueled by our values of integrity, respect, professionalism, stewardship and customer service, the Blue Water Thinking team understands the power of the human connection, collaboration, humility and loyalty to one another, our clients and industry partners. Lastly, our formula for success is simple: Build something good, take care of our people, keep our clients satisfied, nurture our work ethic and reputation, build long-lasting partnerships, enjoy what we do and give back as much as possible."
Job Description paragraph: "Blue Water Thinking is seeking an experienced and dedicated Senior Program Analyst to serve as Schedule Architect and P6 Migration Lead, supporting the Integrated Healthcare Transformation (IHT) initiative at the Department of Veterans Affairs HEFP SEP program. The role carries three linked mandates: architect the target Primavera P6 enterprise environment that a 1,100+ project portfolio can sustain; map legacy data into logic-driven schedules without loss of existing data or functionality; and support federal program managers and field staff through the change, with adoption as a key deliverable. All work is advisory; final decision-making authority rests with the Government, and the incumbent does not draft procurement documents or perform inherently governmental functions."
We'll combine these into About the role paragraph(s). Could be two elements.
Responsibilities: list items as given. Need to extract each bullet.
Responsibilities section includes several subheadings: "Migration Architecture and Data Mapping", "Master Schedule Development, Integration, and Variance Analysis", "Coaching, Reporting, and Adoption". Under each there are sentences. We need to turn each sentence into
- items? The instruction: Use
- for any list of duties/requirements/benefits. So we should create a list where each duty is a list item. Could break down each sentence as separate
- . We'll preserve all content.
Let's extract duties:
From Migration Architecture and Data Mapping:
- Assess the legacy Microsoft Project Web Access environment and produce a defensible mapping of every legacy data element to its P6 destination, including activity codes, user-defined fields, WBS levels, calendars, or planned retirement, with rationale documented and Government-approved.
- Design the enterprise architecture, including EPS hierarchy, WBS standards, activity coding dictionary, calendar library, and UDF strategy sized for portfolio-scale reporting.
- Develop standardized fragnets and schedule templates by project archetype, including telecommunications room cutovers, data center relocations, elevator modernization, AHU/chiller replacement, and roof replacement.
- Convert milestone-dominant legacy records into activities with durations and logic while preserving genuine milestones and maintaining legacy reporting during parallel operations until the Government accepts the new reporting.
- Establish and routinely report schedule health criteria, including open ends, negative lag, constraint use, out-of-sequence progress, excessive float, and missing predecessors or successors.
From Master Schedule Development, Integration, and Variance Analysis:
- Build and manage master schedules with full traceability of program and project milestones defined by SEP federal program managers.
- Maintain schedule baselines, control baseline changes, and preserve audit trails of schedule revisions.
- Manage schedule data across design and construction projects spanning EHRM, recapitalization, and targeted infrastructure portfolios.
- Align the EHRM NRM Capital Integrated Schedule with the EHRMIO Integrated Master Schedule and coordinate with Oracle Health and VA stakeholders, including EHRMIO, OIT, OCFM, OAEM, and PCAC.
- Coordinate with VISN and VAMC engineering staff, site engineers, design and A/E firms, and general contractors to gather schedule events and establish dependencies.
- Analyze schedule data for critical path impact, downstream program effects, and schedule variance across deployment sites.
- Identify, quantify, and escalate schedule risks and support maintenance of the SEP risk register using recognized program risk management techniques.
From Coaching, Reporting, and Adoption:
- Coach and mentor federal program managers, SEP lead engineers, and field staff on schedule interpretation, including critical path, float, milestone movement, and overall program impacts.
- Develop training aids, job aids, bulletins, quick-reference guides, and SOPs, and provide recurring instruction through office hours, working sessions, recorded walkthroughs, and cohort training.
- Build and maintain Power BI and SharePoint reporting views that present P6 data in accessible terms and monitor adoption to identify areas requiring additional support or design improvements.
- Produce the weekly Capital Integrated Schedule and Risk/Event Report, support Capital Schedule and Variance Reports, and develop executive reporting showing milestone status and variance in clear, non-technical language.
Now Qualifications: Minimum Qualifications list:
- Bachelor’s degree (BA/BS) in Engineering, Construction Management, Project Management, Business, Information Technology, or a related field; equivalent experience may be considered in lieu of degree.
- 8+ years of professional scheduling experience supporting design and construction or capital infrastructure programs, including at least 3 years at a senior or lead level within a multi-project portfolio.
- Demonstrated experience converting a milestone-based, spreadsheet-based, or tracking-register system into a logic-driven CPM schedule, including responsibility for data mapping and conversion decisions.
- Expert-level experience with Oracle Primavera P6 Professional and EPPM, including EPS and WBS design, activity coding, calendar libraries, user-defined fields, global changes, baseline management, and multi-project master schedule administration.
- Working proficiency with Microsoft Project and Project Web App sufficient to interrogate, extract, and validate legacy scheduling data.
- Direct Department of Veterans Affairs experience, including VHA, VBA, OCFM, or VISN/VAMC engineering, with knowledge of VA capital project lifecycle, terminology, and governance.
- Demonstrated training, instruction, or mentoring experience with non-scheduler audiences.
- Proficiency with Power BI and SharePoint for schedule reporting.
- Strong analytical, written, verbal communication, and stakeholder-management skills.
- Ability to support organizational and process change constructively while maintaining positive customer relationships.
Preferred Qualifications:
- PMI Scheduling Professional (PMI-SP), AACE Planning and Scheduling Professional (PSP), or PMP certification.
- Prior experience supporting EHRM infrastructure, facility recapitalization, or targeted infrastructure programs.
- Hands-on experience with Microsoft Project-to-P6 enterprise migration, including data reconciliation and parallel-run validation.
- Experience with P6 API, XER/XML exchange, or Power BI connectivity to P6 data.
- Familiarity with VA-specific systems, including Capital Asset Database, Capital Asset Inventory, Strategic Capital Investment Portfolio (SCIP) tool, and Procure.
Eligibility:
Responsibilities then - items.
- Minimum Qualifications: could be "Requirements" or "Qualifications". We'll use "Qualifications" heading for minimum qualifications. Possibly also "Preferred Qualifications" could be under same heading or separate? We could have "Qualifications" covering both minimum and preferred, but we need to preserve all info. Could split into "Minimum Qualifications" and "Preferred Qualifications" but those are not in the allowed list; but we could still use
for them? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings.
Thus:
- About the role: includes company overview and job description summary.
- Responsibilities: as given.
- Requirements: maybe includes Minimum Qualifications? Or we could put Minimum Qualifications under Requirements, and Preferred Qualifications under Skills? Or Skills could include preferred qualifications like certifications, experience with specific systems. Let's think.
We have sections: Minimum Qualifications, Preferred Qualifications, Eligibility (citizenship, clearance), Compensation (Pay), Benefits.
We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide mapping:
- Requirements: could contain Minimum Qualifications (education, experience, etc.)
- Qualifications: could contain Preferred Qualifications (certifications, etc.)
- Skills: could contain specific technical skills (Primavera P6, Microsoft Project, Power BI, SharePoint, etc.) but those are already in qualifications. Might be redundant.
Better: Use Requirements for Minimum Qualifications, Qualifications for Preferred Qualifications, Skills for technical/tool skills (maybe overlapping). But we must not invent headings with filler. If we put Skills but have no specific skill list beyond what's already in qualifications, we could still list them.
Alternatively, we could combine Minimum and Preferred under Qualifications and skip Requirements and Skills. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So maybe we just have About the role, Responsibilities, Qualifications (covering both min and pref), Benefits, Pay. That's four sections. That seems reasonable.
We must not include Schedule section because no schedule info (like work schedule). Not present.
Thus output:
About the role
... company overview and job description summary ...
Responsibilities
- ... each responsibility ...
Qualifications
... Minimum Qualifications ...
... Preferred Qualifications ...
Benefits
- ... benefits ...
Pay
Salary range: $115k-$130k ...
We need to preserve all substantive info. Let's extract.
Company overview paragraph: "About Blue Water Thinking Guided by our principles of value generation, continuous innovation, customer-centricity, and vested collaboration, Blue Water Thinking proudly supports our Federal clients in achieving their Agency goals. Founded by a decorated twenty-eight year Veteran of the United States Army, Blue Water Thinking understands and supports the mission of our Nation's war fighters, Veterans, their families and caretakers. Leveraging our executive team's military experience and private and public sector consulting expertise, Blue Water Thinking takes an integrated "one-team" approach and brings to bear best-fit solutions, thought leadership, and grit to meet our client's transformational needs. Fueled by our values of integrity, respect, professionalism, stewardship and customer service, the Blue Water Thinking team understands the power of the human connection, collaboration, humility and loyalty to one another, our clients and industry partners. Lastly, our formula for success is simple: Build something good, take care of our people, keep our clients satisfied, nurture our work ethic and reputation, build long-lasting partnerships, enjoy what we do and give back as much as possible."
Job Description paragraph: "Blue Water Thinking is seeking an experienced and dedicated Senior Program Analyst to serve as Schedule Architect and P6 Migration Lead, supporting the Integrated Healthcare Transformation (IHT) initiative at the Department of Veterans Affairs HEFP SEP program. The role carries three linked mandates: architect the target Primavera P6 enterprise environment that a 1,100+ project portfolio can sustain; map legacy data into logic-driven schedules without loss of existing data or functionality; and support federal program managers and field staff through the change, with adoption as a key deliverable. All work is advisory; final decision-making authority rests with the Government, and the incumbent does not draft procurement documents or perform inherently governmental functions."
We'll combine these into About the role paragraph(s). Could be two elements.
Responsibilities: list items as given. Need to extract each bullet.
Responsibilities section includes several subheadings: "Migration Architecture and Data Mapping", "Master Schedule Development, Integration, and Variance Analysis", "Coaching, Reporting, and Adoption". Under each there are sentences. We need to turn each sentence into
- items? The instruction: Use
- for any list of duties/requirements/benefits. So we should create a list where each duty is a list item. Could break down each sentence as separate
- . We'll preserve all content.
Let's extract duties:
From Migration Architecture and Data Mapping:
- Assess the legacy Microsoft Project Web Access environment and produce a defensible mapping of every legacy data element to its P6 destination, including activity codes, user-defined fields, WBS levels, calendars, or planned retirement, with rationale documented and Government-approved.
- Design the enterprise architecture, including EPS hierarchy, WBS standards, activity coding dictionary, calendar library, and UDF strategy sized for portfolio-scale reporting.
- Develop standardized fragnets and schedule templates by project archetype, including telecommunications room cutovers, data center relocations, elevator modernization, AHU/chiller replacement, and roof replacement.
- Convert milestone-dominant legacy records into activities with durations and logic while preserving genuine milestones and maintaining legacy reporting during parallel operations until the Government accepts the new reporting.
- Establish and routinely report schedule health criteria, including open ends, negative lag, constraint use, out-of-sequence progress, excessive float, and missing predecessors or successors.
From Master Schedule Development, Integration, and Variance Analysis:
- Build and manage master schedules with full traceability of program and project milestones defined by SEP federal program managers.
- Maintain schedule baselines, control baseline changes, and preserve audit trails of schedule revisions.
- Manage schedule data across design and construction projects spanning EHRM, recapitalization, and targeted infrastructure portfolios.
- Align the EHRM NRM Capital Integrated Schedule with the EHRMIO Integrated Master Schedule and coordinate with Oracle Health and VA stakeholders, including EHRMIO, OIT, OCFM, OAEM, and PCAC.
- Coordinate with VISN and VAMC engineering staff, site engineers, design and A/E firms, and general contractors to gather schedule events and establish dependencies.
- Analyze schedule data for critical path impact, downstream program effects, and schedule variance across deployment sites.
- Identify, quantify, and escalate schedule risks and support maintenance of the SEP risk register using recognized program risk management techniques.
From Coaching, Reporting, and Adoption:
- Coach and mentor federal program managers, SEP lead engineers, and field staff on schedule interpretation, including critical path, float, milestone movement, and overall program impacts.
- Develop training aids, job aids, bulletins, quick-reference guides, and SOPs, and provide recurring instruction through office hours, working sessions, recorded walkthroughs, and cohort training.
- Build and maintain Power BI and SharePoint reporting views that present P6 data in accessible terms and monitor adoption to identify areas requiring additional support or design improvements.
- Produce the weekly Capital Integrated Schedule and Risk/Event Report, support Capital Schedule and Variance Reports, and develop executive reporting showing milestone status and variance in clear, non-technical language.
Now Qualifications: Minimum Qualifications list:
- Bachelor’s degree (BA/BS) in Engineering, Construction Management, Project Management, Business, Information Technology, or a related field; equivalent experience may be considered in lieu of degree.
- 8+ years of professional scheduling experience supporting design and construction or capital infrastructure programs, including at least 3 years at a senior or lead level within a multi-project portfolio.
- Demonstrated experience converting a milestone-based, spreadsheet-based, or tracking-register system into a logic-driven CPM schedule, including responsibility for data mapping and conversion decisions.
- Expert-level experience with Oracle Primavera P6 Professional and EPPM, including EPS and WBS design, activity coding, calendar libraries, user-defined fields, global changes, baseline management, and multi-project master schedule administration.
- Working proficiency with Microsoft Project and Project Web App sufficient to interrogate, extract, and validate legacy scheduling data.
- Direct Department of Veterans Affairs experience, including VHA, VBA, OCFM, or VISN/VAMC engineering, with knowledge of VA capital project lifecycle, terminology, and governance.
- Demonstrated training, instruction, or mentoring experience with non-scheduler audiences.
- Proficiency with Power BI and SharePoint for schedule reporting.
- Strong analytical, written, verbal communication, and stakeholder-management skills.
- Ability to support organizational and process change constructively while maintaining positive customer relationships.
Preferred Qualifications:
- PMI Scheduling Professional (PMI-SP), AACE Planning and Scheduling Professional (PSP), or PMP certification.
- Prior experience supporting EHRM infrastructure, facility recapitalization, or targeted infrastructure programs.
- Hands-on experience with Microsoft Project-to-P6 enterprise migration, including data reconciliation and parallel-run validation.
- Experience with P6 API, XER/XML exchange, or Power BI connectivity to P6 data.
- Familiarity with VA-specific systems, including Capital Asset Database, Capital Asset Inventory, Strategic Capital Investment Portfolio (SCIP) tool, and Procure.
Eligibility:
for them? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings.
Thus:
- About the role: includes company overview and job description summary.
- Responsibilities: as given.
- Requirements: maybe includes Minimum Qualifications? Or we could put Minimum Qualifications under Requirements, and Preferred Qualifications under Skills? Or Skills could include preferred qualifications like certifications, experience with specific systems. Let's think.
We have sections: Minimum Qualifications, Preferred Qualifications, Eligibility (citizenship, clearance), Compensation (Pay), Benefits.
We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide mapping:
- Requirements: could contain Minimum Qualifications (education, experience, etc.)
- Qualifications: could contain Preferred Qualifications (certifications, etc.)
- Skills: could contain specific technical skills (Primavera P6, Microsoft Project, Power BI, SharePoint, etc.) but those are already in qualifications. Might be redundant.
Better: Use Requirements for Minimum Qualifications, Qualifications for Preferred Qualifications, Skills for technical/tool skills (maybe overlapping). But we must not invent headings with filler. If we put Skills but have no specific skill list beyond what's already in qualifications, we could still list them.
Alternatively, we could combine Minimum and Preferred under Qualifications and skip Requirements and Skills. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So maybe we just have About the role, Responsibilities, Qualifications (covering both min and pref), Benefits, Pay. That's four sections. That seems reasonable.
We must not include Schedule section because no schedule info (like work schedule). Not present.
Thus output:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings.
Thus:
- About the role: includes company overview and job description summary.
- Responsibilities: as given.
- Requirements: maybe includes Minimum Qualifications? Or we could put Minimum Qualifications under Requirements, and Preferred Qualifications under Skills? Or Skills could include preferred qualifications like certifications, experience with specific systems. Let's think.
We have sections: Minimum Qualifications, Preferred Qualifications, Eligibility (citizenship, clearance), Compensation (Pay), Benefits.
We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide mapping:
- Requirements: could contain Minimum Qualifications (education, experience, etc.)
- Qualifications: could contain Preferred Qualifications (certifications, etc.)
- Skills: could contain specific technical skills (Primavera P6, Microsoft Project, Power BI, SharePoint, etc.) but those are already in qualifications. Might be redundant.
Better: Use Requirements for Minimum Qualifications, Qualifications for Preferred Qualifications, Skills for technical/tool skills (maybe overlapping). But we must not invent headings with filler. If we put Skills but have no specific skill list beyond what's already in qualifications, we could still list them.
Alternatively, we could combine Minimum and Preferred under Qualifications and skip Requirements and Skills. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So maybe we just have About the role, Responsibilities, Qualifications (covering both min and pref), Benefits, Pay. That's four sections. That seems reasonable.
We must not include Schedule section because no schedule info (like work schedule). Not present.
Thus output:
About the role
... company overview and job description summary ...
Responsibilities
- ... each responsibility ...
Qualifications
... Minimum Qualifications ...
... Preferred Qualifications ...
Benefits
- ... benefits ...
Pay
Salary range: $115k-$130k ...
We need to preserve all substantive info. Let's extract. Company overview paragraph: "About Blue Water Thinking Guided by our principles of value generation, continuous innovation, customer-centricity, and vested collaboration, Blue Water Thinking proudly supports our Federal clients in achieving their Agency goals. Founded by a decorated twenty-eight year Veteran of the United States Army, Blue Water Thinking understands and supports the mission of our Nation's war fighters, Veterans, their families and caretakers. Leveraging our executive team's military experience and private and public sector consulting expertise, Blue Water Thinking takes an integrated "one-team" approach and brings to bear best-fit solutions, thought leadership, and grit to meet our client's transformational needs. Fueled by our values of integrity, respect, professionalism, stewardship and customer service, the Blue Water Thinking team understands the power of the human connection, collaboration, humility and loyalty to one another, our clients and industry partners. Lastly, our formula for success is simple: Build something good, take care of our people, keep our clients satisfied, nurture our work ethic and reputation, build long-lasting partnerships, enjoy what we do and give back as much as possible." Job Description paragraph: "Blue Water Thinking is seeking an experienced and dedicated Senior Program Analyst to serve as Schedule Architect and P6 Migration Lead, supporting the Integrated Healthcare Transformation (IHT) initiative at the Department of Veterans Affairs HEFP SEP program. The role carries three linked mandates: architect the target Primavera P6 enterprise environment that a 1,100+ project portfolio can sustain; map legacy data into logic-driven schedules without loss of existing data or functionality; and support federal program managers and field staff through the change, with adoption as a key deliverable. All work is advisory; final decision-making authority rests with the Government, and the incumbent does not draft procurement documents or perform inherently governmental functions." We'll combine these into About the role paragraph(s). Could be twoelements. Responsibilities: list items as given. Need to extract each bullet. Responsibilities section includes several subheadings: "Migration Architecture and Data Mapping", "Master Schedule Development, Integration, and Variance Analysis", "Coaching, Reporting, and Adoption". Under each there are sentences. We need to turn each sentence into
- for any list of duties/requirements/benefits. So we should create a list where each duty is a list item. Could break down each sentence as separate
- . We'll preserve all content. Let's extract duties: From Migration Architecture and Data Mapping: - Assess the legacy Microsoft Project Web Access environment and produce a defensible mapping of every legacy data element to its P6 destination, including activity codes, user-defined fields, WBS levels, calendars, or planned retirement, with rationale documented and Government-approved. - Design the enterprise architecture, including EPS hierarchy, WBS standards, activity coding dictionary, calendar library, and UDF strategy sized for portfolio-scale reporting. - Develop standardized fragnets and schedule templates by project archetype, including telecommunications room cutovers, data center relocations, elevator modernization, AHU/chiller replacement, and roof replacement. - Convert milestone-dominant legacy records into activities with durations and logic while preserving genuine milestones and maintaining legacy reporting during parallel operations until the Government accepts the new reporting. - Establish and routinely report schedule health criteria, including open ends, negative lag, constraint use, out-of-sequence progress, excessive float, and missing predecessors or successors. From Master Schedule Development, Integration, and Variance Analysis: - Build and manage master schedules with full traceability of program and project milestones defined by SEP federal program managers. - Maintain schedule baselines, control baseline changes, and preserve audit trails of schedule revisions. - Manage schedule data across design and construction projects spanning EHRM, recapitalization, and targeted infrastructure portfolios. - Align the EHRM NRM Capital Integrated Schedule with the EHRMIO Integrated Master Schedule and coordinate with Oracle Health and VA stakeholders, including EHRMIO, OIT, OCFM, OAEM, and PCAC. - Coordinate with VISN and VAMC engineering staff, site engineers, design and A/E firms, and general contractors to gather schedule events and establish dependencies. - Analyze schedule data for critical path impact, downstream program effects, and schedule variance across deployment sites. - Identify, quantify, and escalate schedule risks and support maintenance of the SEP risk register using recognized program risk management techniques. From Coaching, Reporting, and Adoption: - Coach and mentor federal program managers, SEP lead engineers, and field staff on schedule interpretation, including critical path, float, milestone movement, and overall program impacts. - Develop training aids, job aids, bulletins, quick-reference guides, and SOPs, and provide recurring instruction through office hours, working sessions, recorded walkthroughs, and cohort training. - Build and maintain Power BI and SharePoint reporting views that present P6 data in accessible terms and monitor adoption to identify areas requiring additional support or design improvements. - Produce the weekly Capital Integrated Schedule and Risk/Event Report, support Capital Schedule and Variance Reports, and develop executive reporting showing milestone status and variance in clear, non-technical language. Now Qualifications: Minimum Qualifications list: - Bachelor’s degree (BA/BS) in Engineering, Construction Management, Project Management, Business, Information Technology, or a related field; equivalent experience may be considered in lieu of degree. - 8+ years of professional scheduling experience supporting design and construction or capital infrastructure programs, including at least 3 years at a senior or lead level within a multi-project portfolio. - Demonstrated experience converting a milestone-based, spreadsheet-based, or tracking-register system into a logic-driven CPM schedule, including responsibility for data mapping and conversion decisions. - Expert-level experience with Oracle Primavera P6 Professional and EPPM, including EPS and WBS design, activity coding, calendar libraries, user-defined fields, global changes, baseline management, and multi-project master schedule administration. - Working proficiency with Microsoft Project and Project Web App sufficient to interrogate, extract, and validate legacy scheduling data. - Direct Department of Veterans Affairs experience, including VHA, VBA, OCFM, or VISN/VAMC engineering, with knowledge of VA capital project lifecycle, terminology, and governance. - Demonstrated training, instruction, or mentoring experience with non-scheduler audiences. - Proficiency with Power BI and SharePoint for schedule reporting. - Strong analytical, written, verbal communication, and stakeholder-management skills. - Ability to support organizational and process change constructively while maintaining positive customer relationships. Preferred Qualifications: - PMI Scheduling Professional (PMI-SP), AACE Planning and Scheduling Professional (PSP), or PMP certification. - Prior experience supporting EHRM infrastructure, facility recapitalization, or targeted infrastructure programs. - Hands-on experience with Microsoft Project-to-P6 enterprise migration, including data reconciliation and parallel-run validation. - Experience with P6 API, XER/XML exchange, or Power BI connectivity to P6 data. - Familiarity with VA-specific systems, including Capital Asset Database, Capital Asset Inventory, Strategic Capital Investment Portfolio (SCIP) tool, and Procure. Eligibility: