Enterprise Asset Management Reporting Specialist
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. Must not omit details.
We need to extract duties list from description. The description is a paragraph with many sentences; we could break into bullet list items for each duty. But we must preserve all info; we can convert sentences into list items. That's acceptable as long as we don't lose info. Use
- for any list of duties/requirements/benefits. So we should turn the responsibilities into a list.
Similarly required skills list: bullet list.
Desired skills list: bullet list.
Benefits: maybe just a paragraph? But we can make a list with one item? Better to use
for prose if not a list. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So if we have a list of benefits, we use list; if just a statement, we can use
. Benefits: "W2 position with full benefits". That's a short statement; we can put in
.
Pay: we have a paragraph about salary ranges; we can put in
.
Schedule: "Estimated Duration: Ongoing". Could be
.
Now we need to ensure we don't repeat job title. Not included.
We must not include any markdown code fences. Just raw HTML.
Let's craft.
First, About the role: combine the introductory sentences before "JOB DESCRIPTION": "Must be a US Citizen Location - Any NASA Center W2 position with full benefits Estimated Duration: Ongoing Offer contingent on ability to successfully pass a background check and drug screen. Our salary ranges are determined by role, level, and location. The range displayed on each job posting reflects the minimum and maximum target for new hire salaries for the position across all US locations. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training." Actually that includes pay and benefits and schedule. But we separated those into sections. So About the role could be a brief summary: maybe the sentence after that: "We are seeking an Enterprise Reporting Specialist to administer NASA's Office of Strategic Infrastructure (OSI) Facilities and Real Estate Division (FRED) PowerBI Enterprise Reporting Platform..." That is the start of job description. So About the role could be that paragraph summarizing the role. Let's take the first sentence after the introductory boilerplate: "We are seeking an Enterprise Reporting Specialist to administer NASA's Office of Strategic Infrastructure (OSI) Facilities and Real Estate Division (FRED) PowerBI Enterprise Reporting Platform by developing custom and out-of-box reports, building advanced dashboards and KPIs, and managing secure data access through Row- and Column-Level Security (RLS)." That's a good summary.
We'll put that in
.
Then Responsibilities: list all duties from the description after that sentence. We need to capture all duties listed. Let's extract them:
- This role includes maintaining reporting infrastructure, administering Power BI / Data Gateway platform, conducting system upgrades and performance monitoring, and ensuring compliance with security and access-control policies.
- The position works closely with stakeholders to gather requirements, translate them into actionable reporting solutions, and provide end-user training while maintaining thorough documentation, operational guidelines, and troubleshooting procedures.
- Support NASA's Enterprise CMMS reporting server and report repository, ensuring optimal performance, availability, and secure integration with Power BI reporting environments.
- Build custom reports for end users as needed, including advanced analytics and visualizations.
- Develop creative methods of joining multiple, disparate datasets to produce meaningful insight.
- Optimize and maintain Power BI data models, including improving metadata, calculation groups, and model performance.
- Develop and deliver advanced dashboards, metrics, and analytical reports using Power BI, Tableau, SQL, and other enterprise reporting tools to support strategic decision-making and performance monitoring.
- Define, configure, and maintain KPIs aligned with organizational strategy and reporting requirements to measure the effectiveness of business decisions, ensuring consistent measurement across platforms.
- Demonstrate soft skills to work with a team of analysts in an ad-hoc environment to process information.
- Collaborate with team members to collect and analyze data.
- Partner with database administrators and the data manager to ensure robust data operations.
- Structure large data sets to find usable information (mapping).
- Design, develop, and modify data infrastructure to accelerate data analysis and reporting processes.
- Maintain data management plans and instructions for operating complex business systems.
- Evaluate the design, selection, and implementation of database changes by comparing them with business requirements and design documents.
- Map and join together siloed, disparate data sets using Python or Power BI DAX.
- Update data architecture and data models as needed to support evolving requirements.
- Implement and continuously improve Row- and Column-Level Security (RLS/CLS) across reporting environments (e.g., Power BI) to ensure secure, role-appropriate data access across facility organizations.
- Manage and maintain Power BI Data Gateway configurations to support secure hybrid connectivity for on-premises MAS/Maximo data sources.
- Perform necessary software installations, upgrades, patches, and configuration changes.
- Monitor system performance, conduct routine maintenance, and implement improvements for facility maintenance and operations reports and related reporting infrastructure.
- Manage user access, roles, and security settings following compliance policies across all reporting platforms.
- Work closely with stakeholders to gather reporting requirements and implement scalable solutions.
- Develop and maintain report documentation, including specifications, mappings, gateway configurations, and troubleshooting procedures.
- Provide end-user reporting support and training on Power BI and related reporting tools.
- Develop and maintain comprehensive documentation and standard operating procedures (SOPs) related to reporting workflows, tools, and operational guidelines.
That seems comprehensive.
Now Required Skills list:
- Bachelor's degree in Computer Science, Information Technology, or a related field (or equivalent experience).
- 6+ years of experience in Enterprise Asset Management Reporting and/or PowerBI reporting.
- Experience with application security, authentication methods, and role-based access controls.
- Familiarity with Windows and Linux operating systems.
- Strong troubleshooting and problem-solving skills.
- Experience with scripting and automation tools.
- Excellent communication and collaboration skills.
- Working knowledge of Power BI reporting environments, including data modeling, DAX, and publishing workflows.
- Hands-on experience with Power BI Data Gateway management for on-premises data access.
Desired Skills list:
- Experience with SQL Developer.
- Knowledge of Maximo database tables and structures.
- Experience with Maximo 7.6 and MAS-9 reporting capabilities.
- Experience with enterprise analytics environments, hybrid data integrations, and RLS/CLS management at scale.
- Experience using Tabular Editor for enterprise-level data model optimization and governance.
- Certifications in relevant technologies (e.g., Power BI, Azure, Maximo/MAS, ITIL).
Benefits: "W2 position with full benefits". Could also mention maybe "full benefits". We'll put that.
Pay: The paragraph about salary ranges.
Schedule: "Estimated Duration: Ongoing". Also maybe mention "Offer contingent on ability to successfully pass a background check and drug screen." That's not schedule but could be part of About the role? But we already used About the role for role summary. Could include that as part of About the role? But we already used About the role for role summary; we could incorporate the citizenship and background check into About the role as well. However we must not repeat job title. It's okay to include extra info in About the role. But we already used About the role for a summary; we could expand it to include citizenship, location, benefits, duration, background check. But then we would duplicate info in Benefits, Pay, Schedule sections. Better to keep About the role as the role description, and keep separate sections for Benefits, Pay, Schedule, and maybe also include citizenship etc in About the role? The instruction: "Prefer a few substantive sections over many thin ones." Having many sections may be okay if each has substantive content. We have About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. That's 7 sections. Could be okay.
But we must not create sections with filler. Each has real content.
Now we need to ensure we don't include any boilerplate like "EEO". Not present.
Now produce HTML.
Structure:
About the role
We are seeking an Enterprise Reporting Specialist to administer NASA's Office of Strategic Infrastructure (OSI) Facilities and Real Estate Division (FRED) PowerBI Enterprise Reporting Platform by developing custom and out-of-box reports, building advanced dashboards and KPIs, and managing secure data access through Row- and Column-Level Security (RLS).
Responsibilities
- ... each duty ...
Requirements
- ... each required skill ...
Skills
- ... each desired skill ...
Benefits
W2 position with full benefits.
Pay
Our salary ranges are determined by role, level, and location. The range displayed on each job posting reflects the minimum and maximum target for new hire salaries for the position across all US locations. Within the range, individual pay is determined by work location
for prose. We need to preserve all substantive information; do not invent or summarize away detail. Must not omit details. We need to extract duties list from description. The description is a paragraph with many sentences; we could break into bullet list items for each duty. But we must preserve all info; we can convert sentences into list items. That's acceptable as long as we don't lose info. Use
- for any list of duties/requirements/benefits. So we should turn the responsibilities into a list.
Similarly required skills list: bullet list.
Desired skills list: bullet list.
Benefits: maybe just a paragraph? But we can make a list with one item? Better to use
for prose if not a list. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So if we have a list of benefits, we use list; if just a statement, we can use
. Benefits: "W2 position with full benefits". That's a short statement; we can put in
. Pay: we have a paragraph about salary ranges; we can put in
. Schedule: "Estimated Duration: Ongoing". Could be
. Now we need to ensure we don't repeat job title. Not included. We must not include any markdown code fences. Just raw HTML. Let's craft. First, About the role: combine the introductory sentences before "JOB DESCRIPTION": "Must be a US Citizen Location - Any NASA Center W2 position with full benefits Estimated Duration: Ongoing Offer contingent on ability to successfully pass a background check and drug screen. Our salary ranges are determined by role, level, and location. The range displayed on each job posting reflects the minimum and maximum target for new hire salaries for the position across all US locations. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training." Actually that includes pay and benefits and schedule. But we separated those into sections. So About the role could be a brief summary: maybe the sentence after that: "We are seeking an Enterprise Reporting Specialist to administer NASA's Office of Strategic Infrastructure (OSI) Facilities and Real Estate Division (FRED) PowerBI Enterprise Reporting Platform..." That is the start of job description. So About the role could be that paragraph summarizing the role. Let's take the first sentence after the introductory boilerplate: "We are seeking an Enterprise Reporting Specialist to administer NASA's Office of Strategic Infrastructure (OSI) Facilities and Real Estate Division (FRED) PowerBI Enterprise Reporting Platform by developing custom and out-of-box reports, building advanced dashboards and KPIs, and managing secure data access through Row- and Column-Level Security (RLS)." That's a good summary. We'll put that in
. Then Responsibilities: list all duties from the description after that sentence. We need to capture all duties listed. Let's extract them: - This role includes maintaining reporting infrastructure, administering Power BI / Data Gateway platform, conducting system upgrades and performance monitoring, and ensuring compliance with security and access-control policies. - The position works closely with stakeholders to gather requirements, translate them into actionable reporting solutions, and provide end-user training while maintaining thorough documentation, operational guidelines, and troubleshooting procedures. - Support NASA's Enterprise CMMS reporting server and report repository, ensuring optimal performance, availability, and secure integration with Power BI reporting environments. - Build custom reports for end users as needed, including advanced analytics and visualizations. - Develop creative methods of joining multiple, disparate datasets to produce meaningful insight. - Optimize and maintain Power BI data models, including improving metadata, calculation groups, and model performance. - Develop and deliver advanced dashboards, metrics, and analytical reports using Power BI, Tableau, SQL, and other enterprise reporting tools to support strategic decision-making and performance monitoring. - Define, configure, and maintain KPIs aligned with organizational strategy and reporting requirements to measure the effectiveness of business decisions, ensuring consistent measurement across platforms. - Demonstrate soft skills to work with a team of analysts in an ad-hoc environment to process information. - Collaborate with team members to collect and analyze data. - Partner with database administrators and the data manager to ensure robust data operations. - Structure large data sets to find usable information (mapping). - Design, develop, and modify data infrastructure to accelerate data analysis and reporting processes. - Maintain data management plans and instructions for operating complex business systems. - Evaluate the design, selection, and implementation of database changes by comparing them with business requirements and design documents. - Map and join together siloed, disparate data sets using Python or Power BI DAX. - Update data architecture and data models as needed to support evolving requirements. - Implement and continuously improve Row- and Column-Level Security (RLS/CLS) across reporting environments (e.g., Power BI) to ensure secure, role-appropriate data access across facility organizations. - Manage and maintain Power BI Data Gateway configurations to support secure hybrid connectivity for on-premises MAS/Maximo data sources. - Perform necessary software installations, upgrades, patches, and configuration changes. - Monitor system performance, conduct routine maintenance, and implement improvements for facility maintenance and operations reports and related reporting infrastructure. - Manage user access, roles, and security settings following compliance policies across all reporting platforms. - Work closely with stakeholders to gather reporting requirements and implement scalable solutions. - Develop and maintain report documentation, including specifications, mappings, gateway configurations, and troubleshooting procedures. - Provide end-user reporting support and training on Power BI and related reporting tools. - Develop and maintain comprehensive documentation and standard operating procedures (SOPs) related to reporting workflows, tools, and operational guidelines. That seems comprehensive. Now Required Skills list: - Bachelor's degree in Computer Science, Information Technology, or a related field (or equivalent experience). - 6+ years of experience in Enterprise Asset Management Reporting and/or PowerBI reporting. - Experience with application security, authentication methods, and role-based access controls. - Familiarity with Windows and Linux operating systems. - Strong troubleshooting and problem-solving skills. - Experience with scripting and automation tools. - Excellent communication and collaboration skills. - Working knowledge of Power BI reporting environments, including data modeling, DAX, and publishing workflows. - Hands-on experience with Power BI Data Gateway management for on-premises data access. Desired Skills list: - Experience with SQL Developer. - Knowledge of Maximo database tables and structures. - Experience with Maximo 7.6 and MAS-9 reporting capabilities. - Experience with enterprise analytics environments, hybrid data integrations, and RLS/CLS management at scale. - Experience using Tabular Editor for enterprise-level data model optimization and governance. - Certifications in relevant technologies (e.g., Power BI, Azure, Maximo/MAS, ITIL). Benefits: "W2 position with full benefits". Could also mention maybe "full benefits". We'll put that. Pay: The paragraph about salary ranges. Schedule: "Estimated Duration: Ongoing". Also maybe mention "Offer contingent on ability to successfully pass a background check and drug screen." That's not schedule but could be part of About the role? But we already used About the role for role summary. Could include that as part of About the role? But we already used About the role for role summary; we could incorporate the citizenship and background check into About the role as well. However we must not repeat job title. It's okay to include extra info in About the role. But we already used About the role for a summary; we could expand it to include citizenship, location, benefits, duration, background check. But then we would duplicate info in Benefits, Pay, Schedule sections. Better to keep About the role as the role description, and keep separate sections for Benefits, Pay, Schedule, and maybe also include citizenship etc in About the role? The instruction: "Prefer a few substantive sections over many thin ones." Having many sections may be okay if each has substantive content. We have About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. That's 7 sections. Could be okay. But we must not create sections with filler. Each has real content. Now we need to ensure we don't include any boilerplate like "EEO". Not present. Now produce HTML. Structure:
About the role
We are seeking an Enterprise Reporting Specialist to administer NASA's Office of Strategic Infrastructure (OSI) Facilities and Real Estate Division (FRED) PowerBI Enterprise Reporting Platform by developing custom and out-of-box reports, building advanced dashboards and KPIs, and managing secure data access through Row- and Column-Level Security (RLS).
Responsibilities
- ... each duty ...
Requirements
- ... each required skill ...
Skills
- ... each desired skill ...
Benefits
W2 position with full benefits.
Pay
Our salary ranges are determined by role, level, and location. The range displayed on each job posting reflects the minimum and maximum target for new hire salaries for the position across all US locations. Within the range, individual pay is determined by work location
- for any list of duties/requirements/benefits, and