FEDADC PWS_N02i Final 2026.docx
DOCX document 83 KB Posted
- Solicitation number
- N0018926RFEDADC
About this file
This is a Performance Work Statement (PWS) for Fleet Enterprise Data Analytics and Digital Capability (FEDADC) Support Services to be provided to United States Fleet Forces Command (USFF) and subordinate commands. The FEDADC program requires comprehensive contractor support across 27 functional areas including data analytics, foundational data processing, analytics sustainment, data transformation, database management, cloud and distributed computing, technical and data architecture, data governance, emerging technologies assessment, data science lifecycle support, enterprise strategy development, analytic product development, data mining and exploration, AI/machine learning technologies, predictive and prescriptive modeling, AI governance, data visualization, UI/UX design, transformational methodologies, stakeholder engagement, project planning, program management, risk assessment, change management, strategic communications, training enablement, and application development.
The contract consists of a 12-month base period with four 12-month option periods and potential extension up to six additional months. Primary work locations are at USFF headquarters and subordinate commands in the Norfolk, Virginia area, with telework permitted at the COR's discretion. The contractor must provide specialized personnel across 21 labor categories ranging from entry-level Data Analysts to Senior Program Managers, all requiring active Secret security clearances and U.S. citizenship. Key deliverables include monthly progress and financial reports, quality control plans, enterprise data and AI strategies, data governance documentation, technical and data architecture documentation, MLOps lifecycle documentation, UI/UX research reports, training materials, interactive dashboards and visualizations, and an end-of-contract final report. Personnel must complete mandatory annual training including cyber awareness, PII protection, privacy act, anti-terrorism, OPSEC, suicide prevention, records management, counterintelligence awareness, security awareness, derivative classification, and CUI training, with travel costs reimbursable only when pre-approved and outside a 50-mile radius of the primary work location.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Sources Sought - N02i Enterprise Data Analytics.pdf | ||
| Sources Sought - N02i Enterprise Data Analytics.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PERFORMANCE WORK STATEMENT (PWS)
FLEET ENTERPRISE DATA ANALYTICS AND DIGITAL CAPABILITY (FEDADC)
1. Background:
Commander, United States Fleet Forces Command (USFF) is responsible for coordinating, establishing, and implementing integrated requirements and policies for manning, equipping, and training Fleet units, amphibious ready groups (ARG), expeditionary strike groups (ESG), carrier strike groups (CSG), expeditionary strike forces and Independent Deployers (ID). These requirements and elements are paramount in the execution of the Global Maritime Response Plan (GMRP), the Optimized Fleet Response Plan (OFRP), and in support of United States Navy (USN) policy, and unified commanders.
The Chief Data and Artificial Intelligence (AI) Office (CDAO) is responsible for creating strategic value by transforming data into a critical enterprise asset. The office leads the development of data-enabled strategies, defines the portfolio of data and analytics investments, and operationalizes high-priority initiatives to achieve key business outcomes. By developing integrated data products that provide visualization, predictive, and prescriptive analytics, the office equips senior leadership with the critical insights needed for informed and effective decision-making. To provide this decision space for our leaders, the CDAO establishes the IT management framework and development roadmaps necessary for successful data product integration. It is also responsible for fostering a data-driven culture by championing effective data management practices, ensuring alignment with data governance principles, and promoting a deeper understanding of analytics across the organization.
The intent of this enterprise solution is to clearly identify requirements, delineate responsibilities and provide consolidated synergistic solutions to prevent duplication of effort across the USFF domain. The purpose of this requirement is to provide highly skilled data analytics/data science contractor support services to implement the USFF CDAO and Fleet subordinate commands with solutions to the data requirements and strategy implementation.
The contractor shall support the USFF CDAO to develop and sustain advanced analytics, visualizations and data governance frameworks to enable improved decision-making by providing expertise in data mining, data engineering, data exploration, predictive/prescriptive modeling, and the ability to assimilate and integrate data from diverse sources. Furthermore, proactive assessment and recommendations for emerging technologies are critical for maintaining a competitive edge. A well-defined data strategy and robust project execution are essential for success. To achieve these goals, USFF CDAO requires expertise in a wide range of digital capabilities, data science tools and techniques, and modern data management practices. This includes proficiency in AI and machine learning technologies, cloud and distributed computing, and the development of mission-focused analytic products with intuitive stakeholder interfaces.
2. SCOPE:
This requirement provides an enterprise contract solution for support in the below functional areas:
2.1. Data Analytics
2.2. Foundational Data Processing and Provisioning
2.3. Analytics Sustainment Support
2.4. Data Transformation
2.5. Database Management
2.6. Cloud and Distributed Computing
2.7. Technical and Data Architecture
2.8. Data Management and Data Governance
2.9. Emerging Technologies Assessment and Recommendations
2.10. Data Science Lifecycle Support
2.11. Enterprise Data, Data Analytics, and Artificial Intelligence Strategy
2.12. Enterprise-Effecting and Mission-Focused Analytic Products
2.13. Data Mining, Wrangling, and Exploration
2.14. AI and Machine Learning Technologies
2.15. Predictive & Prescriptive Modeling
2.16. AI Governance
2.17. Data Visualization Design and Development
2.18. User Interface and User Experience (UI/UX)
2.19. Transformational Methodologies
2.20. Stakeholder and Customer User Interfaces and Experience
2.21. Project Planning and Execution
2.22. Program Management and Strategy
2.23. Risk Assessment and Mitigation
2.24. Change Management and Stakeholder Engagement
2.25. Strategic Communications Support
2.26. Training Enablement
2.27. Application Development
3. FUNCTIONAL AREA DESCRIPTIONS AND TASKS:
3.1. Data Analytics
The contractor shall collaborate with the government requirement owner to identify and prioritize data analytics use cases. Develop analytical models using advanced techniques such as machine learning and artificial intelligence to extract insights and patterns from structured and unstructured data. Perform data mining and statistical analysis to uncover hidden patterns, trends, and correlations. Conduct data driven root cause analysis to identify improvement opportunities in business processes. Conduct exploratory data analysis to identify data relationships and anomalies. Implement predictive and perspective analytics to support forecasting and decision making. Deliver functional domain expertise on command specific requirements and processes to deliver technical analytical inputs. Deliver technical experience within the DOW and DON enterprise analytic platforms. Sustain existing data analytic tools to ensure broad adoption of data analytic practices across the Fleet enterprise.
3.2. Foundational Data Processing and Provisioning
The Contractor shall establish and maintain robust, scalable data pipelines for extracting, transforming, and loading (ETL) data from diverse sources into a unified data environment. The Contractor shall identify and integrate new data sources, resolving data compatibility, accuracy, and timeliness issues through data transformation. All data integration processes shall be resilient, auditable, and designed to minimize data latency. The Contractor shall utilize Navy-approved enterprise service technologies for all data processing and provisioning.
3.3. Analytics Sustainment Support
The Contractor shall provide sustainment for all data analytics platforms, models, applications, and dashboards. Responsibilities include maintenance, updates, and optimization to ensure sustained operational availability, data integrity, and performance reliability.
3.4. Data Transformation
The Contractor shall assist in the design and implementation of data transformation processes to convert raw data into meaningful insights. Apply data enrichment, aggregation, and summarization techniques to positively improve outputs. Develop data transformation pipelines using industry leading tools and technologies. Support enablement efforts so ensure broad adoption of data transformation practices across the Fleet and supported commands.
3.5. Database Management
The Contractor shall design, implement, and maintain relational and non-relational databases to support data storage and analytics. This includes database optimization, performance tuning, capacity planning, and security management. The Contractor shall implement and regularly test data backup, recovery, archiving, and retention procedures to ensure data availability, comply with regulations, and optimize storage costs. Access controls shall be configured to protect data from unauthorized access, use, or disclosure. The Contractor shall utilize Navy-approved enterprise service technologies () for all database management.
3.6. Cloud and Distributed Computing
The Contractor shall leverage cloud and distributed computing to scale data processing and storage capabilities. Using Navy-approved enterprise cloud platforms (), the Contractor shall support data analytics, machine learning, artificial intelligence, and data visualization. All solutions shall be designed for scalability, high availability, and cost-effectiveness in the cloud environment.
3.7. Technical and Data Architecture
The Contractor shall assess the Fleet and supported commands technical and data architectures and make recommendations for improvements. Develop/design and maintain scalable, robust and comprehensive technical architectures for data analytic solutions that are aligned with command goals and technology strategy. The architectures shall define data models, flows, and integration patterns to support both batch and real-time processing, as well as a variety of analytical workloads. The Contractor shall ensure interoperability and compatibility with existing systems and platforms. Conduct performance testing and optimization of the technical and data architectures. The Contractor shall provide and maintain technical and data architecture documentation, to include performance testing reports, improvement recommendations, data dictionaries, data flow diagrams, and data lineage reports.
3.8. Data Management and Data Governance
The Contractor shall implement and enforce data management and governance policies covering data quality monitoring, metadata management, data lineage tracking, data ownership, access controls, and data retention. Contractor shall assist and the establishment of data governance frameworks, polices, and procedures. Assist in defining data standards, metadata management, and data lineage. Ensure data reporting to data catalog while ensuring data catalog compliance. Implement access controls and user roles to safeguard data confidentiality and integrity. Ensure compliance with all the Department of War (DOW), Department of the Navy (DON) CDAO and Chief of Naval Operations (CNO) governance frameworks policies, data privacy regulations, and security standards. The Contractor shall deliver a comprehensive Enterprise Data, Data Analytics, and Artificial Intelligence Strategy as a formal deliverable within 60 days of contract award.
3.9. Emerging Technologies Assessment and Recommendations
The Contractor shall proactively assess emerging technologies in data analytics, data science, and artificial intelligence, following a defined, auditable, and repeatable process. The Contractor shall deliver a quarterly report that analyzes the potential benefits, risks, and costs of these technologies and provides recommendations for their use in improving command business processes and achieving strategic goals. More frequent ad-hoc reports may be requested by the Government for notable or disruptive technologies.
3.10. Data Science Lifecycle Support
The Contractor shall provide end-to-end support for the data science lifecycle, from data acquisition and preparation through model deployment and monitoring. The Contractor will utilize an approved data science lifecycle management tool available on Navy-approved enterprise service technologies (). To ensure sustainment, the Contractor shall provide training and documentation that enables command personnel to maintain and enhance all delivered data science solutions.
3.11. Enterprise Data, Data Analytics, and Artificial Intelligence Strategy The Contractor shall develop and deliver a comprehensive Enterprise Data, Data Analytics, and Artificial Intelligence Strategy for USFF/BSO-60 within 90 days of contract award. Additionally, the contractor shall develop similar comprehensive Enterprise Data, Data Analytics, and Artificial Intelligence Strategy documents for commands supported under this contract and down to the Echelon III level when required. The Contractor shall ensure strategies developed for subordinate commands align with the overarching Fleet HQ approach. This strategy shall be informed by a Contractor-led data maturity assessment and align with the command's business goals and broader Navy governance policies. At a minimum, the strategy will include:
3.11.1. A vision for data management, analytics, and AI.
3.11.2. A technology and implementation roadmap.
3.11.3. A governance framework.
3.11.4. A target technology architecture.
3.11.5. A workforce skills development plan
3.12. Enterprise-Effecting and Mission-Focused Analytic Products The Contractor shall develop, secure, and deliver mission-focused analytic products by translating stakeholder requirements into scalable and reliable solutions that directly support the strategic goals of the Fleet and supported commands. The Contractor shall continuously monitor the performance of these products and implement all necessary modifications to ensure they remain relevant and effective throughout the period of performance.
3.13. Data Mining, Wrangling, and Exploration
The Contractor shall perform comprehensive data wrangling to correct, standardize, and enrich datasets for advanced analytical use. This shall include utilizing Exploratory Data Analysis (EDA) and data mining techniques (e.g., clustering, association rule mining) to uncover patterns, identify anomalies, formulate hypotheses, and transform data into a format suitable for complex modeling. The Contractor shall cleanse, transform, and integrate data from multiple sources to ensure data accuracy and consistency. Apply data wrangling techniques to handle missing data, outliers, and data inconsistencies. Develop and implement data quality rules and data visualization processes. Optimize data wrangling processes to improve efficiency and automation. Communicate any inconsistencies in data collection efforts to the appropriate government stakeholders. Support enablement efforts to ensure broad adoption of data analytic preparation practices across the Fleet and supported commands.
3.14. AI and Machine Learning Technologies
The Contractor shall develop, deploy, and manage AI and machine learning (ML) solutions to automate complex tasks and generate data-driven insights. The Contractor's responsibilities shall include:
3.14.1. Developing, deploying, training, and validating AI/ML models, including the use of Generative AI for applications such as synthetic data generation and automated summarization.
3.14.2. Managing the end-to-end model lifecycle (MLOps), including feature engineering, deployment, and continuous monitoring to ensure sustained performance.
3.14.3. Rigorously documenting all models, code, and processes using version control to ensure reproducibility and explainability.
3.14.4. Apply advanced techniques such as natural language processing, computer vision, and deep learning.
3.14.5. The Contractor will utilize Navy-approved enterprise service technologies () for all AI and ML activities.
3.15. Predictive & Prescriptive Modeling
The Contractor shall design and implement predictive models to forecast trends, behaviors, and events, providing data-driven foresight for proactive decision-making. The Contractor shall also develop prescriptive models that recommend optimal actions, leveraging simulation-based techniques (e.g., Monte Carlo, Discrete Event Simulation, Agent-Based Modeling) to quantify the impact of decisions. Optimize model performance and evaluate model accuracy using appropriate metrics. All modeling solutions shall be validated for accuracy and reliability and integrated into operational workflows to provide timely, actionable intelligence. Advise Fleet and supported command personnel on model development.
3.16. AI Governance
The Contractor shall assist in establishing governance frameworks for the ethical and responsible use of AI. Ensure transparency, fairness, accountability, and interpretability of AI models. Develop processes for model validation, bias detection, and algorithmic transparency.
3.17. Data Visualization, Design, and Development
The Contractor shall design, develop, and deliver interactive dashboards, reports, and visualizations that effectively communicate key performance indicators (KPIs) and actionable insights to stakeholders. All visualizations shall adhere to data visualization best practices for accuracy, clarity, and ethics. The Contractor shall enable users to explore and interact with data visualizations to gain actionable insights. The final products shall be user-friendly, visually appealing, and optimized for performance. The Contractor shall utilize Government-approved Business Intelligence (BI) tools and techniques, such as Qlik Sense, Tableau, and Power BI to execute visualization tasks and present complex data in a comprehensible and intuitive manner. The Contractor shall sustain existing data analytic tools to ensure functionality across the user base.
3.18. User Interface and User Experience (UI/UX)
The Contractor shall design and develop intuitive, accessible, and engaging UI/UX solutions. This process shall be informed by user research to understand stakeholder needs and preferences. Incorporate user-centered design principles to enhance the user experience of data analytic solutions. Conduct user research, personas development, and usability testing. Apply user feedback to improve the usability, intuitiveness, and effectiveness of the solutions. All UI/UX solutions shall comply with applicable laws and regulations for supporting users with disabilities.
3.19. Transformational Methodologies
The Contractor shall apply structured, repeatable frameworks (e.g., SAFe, Agile, Lean) to manage projects and accelerate delivery of technology initiatives. Through these methodologies, the Contractor shall work collaboratively with command stakeholders to define requirements, prioritize tasks, and iteratively develop solutions that ensure continuous improvement.
3.20. Stakeholder and Customer User Interface Experience
The Contractor shall apply Human-Centered Design (HCD) principles to create and improve user interfaces. The focus shall be on delivering a positive user experience, reducing user burden, and increasing service efficiency. All designs must meet defined usability and accessibility standards as verified through formal usability testing.
3.21. Project Planning and Execution
The Contractor shall develop and maintain a comprehensive project plan for each initiative, defining its scope, objectives, timelines, resources, and deliverables. The Contractor shall manage all projects to ensure they are completed on time, within budget, and to required quality standards. All project work shall be tracked in a Government-accessible project management tool. The Contractor shall provide a formal project progress report to Government leadership on a bi-weekly basis, or more frequently if requested for critical projects.
3.22. Program Management and Strategy
The Contractor shall provide program management support to ensure successful execution of the contract tasks and functions. Develop contract execution plans, schedules and resource allocation requirements. Monitor contract performance, progress, quality assurance, track milestones and manage risks. Conduct program reviews and status reporting when required.
3.23. Risk Assessment and Mitigation
The Contractor shall conduct continuous risk assessments to identify, analyze, and document potential risks to all projects. For each identified risk, the Contractor shall develop and implement a mitigation plan. The Contractor shall maintain a risk register detailing all identified risks, mitigation plans, and residual risks, and provide it as a component of the bi-weekly project progress report.
3.24. Change Management and Stakeholder Engagement
The Contractor shall develop change management strategies to facilitate smooth adoption of data analytics solutions and visualization tools. Identify and engage stakeholders to gather requirements and manage expectations. Conduct stakeholder analysis and develop tailored communication plans. Address resistance to change and provide training and support to users.
3.25. Strategic Communications Support
The Contractor shall assist in the development and execution of strategic communications plans to promote data analytics initiatives. Create engaging content, including presentations, articles and newsletters. Conduct awareness campaigns and workshops to foster a data-driven culture. Sustain existing communications tools to ensure functionality across the user base.
3.26. Training Enablement
The Contractor shall provide training sessions and workshops to Fleet and supported command personnel on data analytics tools, techniques, and best practices. Develop comprehensive training materials, including user guides, slick sheets, videos, and tutorials. Conduct train-the-trainer sessions to build internal capabilities. Capture lessons learned from training sessions as well as changes to policy/guidance, tools, technology improvements/enhancements, best practices, and will/shall update training materials to ensure they are kept up to date. Training may be on a one-on-one individual basis, small group, large group or command wide and be in the form of live, virtual or classroom setting.
3.26 . Application Development The Contractor shall design, develop, and deploy custom applications. These applications will integrate data from internal and external sources and feature web-based front-end interfaces with corresponding back-end databases. Development shall leverage modern technologies including, but not limited to, C#, .NET, JavaScript, HTML, CSS, JSON, T-SQL, and PowerShell.
4. Deliverables:
Contract deliverables are identified below. The deliverables matrix identifies specific deliverables necessary for the successful management and accomplishment of the contract and its requisite PWS. In addition, the contractor shall provide other deliverables and work products as described in the tasks/sub-tasks of Section 3 of this PWS. These deliverables shall be provided in accordance with the PWS and/or as required by the Government. The contractor shall deliver the following key deliverables:
| Item # |
| Deliverable Name |
| Description / Example |
| 4.1 |
| Monthly Progress, Status, and Management Report (MPSR) |
| Description and Guidelines: At a minimum the reports shall include the following information: |
1) Activities of the past month
(a) Summary of the action taken, and progress made on outstanding tasks for the past month, including travel, problems, issues and technical assistance log (as applicable) etc.
2) Routine teleconference/meeting/conference attendance
(a) Do not report on routine teleconferences, meetings and conferences in support of daily requirements/tasks.
3) Provide report in conjunction with roadmap/way ahead to address specific problem/issues
4) Activities of the next month
(a) A review of the work planned for the next month to meet task requirements, including projected travel, anticipated risk and/or issues
5) Management synergies and cost efficiencies
6) Resource status, constraints, number and forecast
Due Date: Submitted to the Contracting Officer’s Representative (COR) and Alternate Contracting Officer’s Representative (ACOR) no later than the 15th working day of each month
Medium of Delivery / Format: Electronic; Microsoft (MS) Word
| 4.2 |
| Monthly Financial Progress/Status Report (MFSR) |
| Description and Guidelines: At a minimum the reports shall include the following information: |
1) Total funds expended during the previous month; cumulative total to date and the remaining ceiling amount
2) Total labor funds expended by labor category, functional area and by funding activity
3) Current and forecasted funding burn rates
4) Total hours by individual, labor category, functional area and by funding activity
5) Total hours by labor category and command/functional areas for each training event/exercise from planning through execution. The purpose of this requirement is to obtain cost and level of effort data for each training event/exercise conducted.
6) Travel funds expended during the previous month; cumulative total to date and the remaining ceiling amount.
7) Travel funds expended by labor category, functional area and by funding activity during the previous month and cumulative total to date.
8) ODC funds expended during the previous month; cumulative total to date and the remaining ceiling amount in total and by funding activity
Due Date: Submitted to the COR and ACOR no later than the 15th working day of each month
Medium of Delivery / Format: Electronic; MS Word and MS Excel
| 4.3 |
| Trip Report |
| Description and Guidelines: A summary report submitted after any official travel, detailing the purpose, activities, outcomes, and action items. Report shall include a summary of timetables, accomplishments, significant discussions/events, contacts and action items |
Due Date: Submitted to the COR or Technical Assistant (TA) no later than 5 working days after the conclusion of the trip
Medium of Delivery / Format: Electronic; MS
| 4.4 |
| Quality Control Plan (QCP) |
| Description and Guidelines: A plan detailing the contractor's methods and procedures for ensuring all work products and services meet quality standards. The Contractor’s QCP shall demonstrate their approach to delivering and maintaining an effective quality control (QC) program that ensures services are performed in accordance with the PWS and its requisite attachments and references. At a minimum, the Contractor’s QCP shall address: |
1) Procedures to establish and comply with the Government’s baseline requirements.
2) Procedures for sustainment of event proficiency and resolution of identified capability deficiencies
3) Procedures to be implemented to ensure the following:
(a) Successful completion of tasks identified within the PWS
(b) Contractual requirements and deliverables are met and are provided in a timely manner
(c) Tasks are completed in a cost-efficient manner
(d) Contractor’s work force, level of effort and labor mix, is effectively managed to ensure that tasks are completed in an efficient and effective manner
(e) Tracking of labor hours expended in the correction or replacement of work that has not met contract requirements
(f) Lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations
Due Date: Submitted to the COR and ACOR no later than 10 business days after the contract period of performance start date
Submission Process:
1) The proposed QCP will be reviewed by the COR and either accepted or provided back to the Contractor with questions/corrections/comments, etc.
2) The Contractor shall provide the revised QCP back to the COR addressing all areas of the COR’s concern no later than five (5) business days following receipt from the COR
3) Once the QCP has been accepted, the COR will notify the Contractor of the acceptance of the deliverable
4) After acceptance of the QCP the Contractor shall receive the Contracting Officer’s acceptance in writing of any proposed change to his QC system
Medium of Delivery / Format: Electronic; MS Word
| 4.5 |
| Enterprise Data, Data Analytics, and Artificial Intelligence Strategy |
| Description and Guidelines: A comprehensive plan establishing the strategic framework, policies, and procedures for managing data as an enterprise asset. The plan shall include data stewardship roles and responsibilities, data security policies, and data access protocols. It will also establish the standards that mandate the creation and maintenance of the corresponding Data Quality & Definition Documentation. |
As a foundational component, the contractor shall research, identify, and deliver a Governing Publications List. This list must cite all current and applicable data governance, security, and management instructions from OSW CDAO, DON CDAO, and OPNAV that will govern all performance under this PWS. This list is subject to COR review and final approval before the Enterprise Data, Data Analytics, and Artificial Intelligence Strategy can be accepted.
Due Date: The proposed Governing Publications List shall be delivered to the COR for review no later than 60 business days after the contract period of performance start date and within 60 days for any command being supported under this effort. The final Enterprise Data, Data Analytics, and Artificial Intelligence Strategy shall be submitted to the COR and ACOR no later than 90 business days after the start date. The plan shall be reviewed and updated as needed, but at a minimum annually.
Medium of Delivery / Format: Electronic; MS Word or PDF format.
| 4.6 |
| Data Quality & Definition Documentation |
| Description and Guidelines: The tactical implementation of the standards defined in the Enterprise Data, Data Analytics, and Artificial Intelligence Strategy. This is a "living" deliverable with two key components: |
Data Quality Rules: A documented set of rules and standards implemented to cleanse, standardize, and ensure the accuracy and consistency of data and its associated Basis for Measurements (BFMs). Each rule must be clearly defined with the logic used and the data it applies to.
Data Dictionary: A repository that defines key data elements, including their business definitions, allowable values, formats, and sources.
Due Date: The initial version of the Data Quality & Definition Documentation shall be delivered within 60 days of contract period of performance start date and within 60 days for any command being supported under this effort. Updates must be delivered to the COR for review within 5 business days of implementation. The documentation as a whole will be reviewed and updated as needed, but at a minimum annually.
Medium of Delivery / Format: Electronic; a linked, shared repository (e.g., SharePoint, wiki, or a searchable MS Excel file) to facilitate its status as a living document.
| 4.7 |
| Technical and Data Architecture Documentation |
| Description and Guidelines: A collection of "living" documents detailing all systems, platforms, data models, and data flows, including data flow diagrams. A key component is the ETL & data pipeline documentation, which provides detailed outlines of data sources, transformation logic, dependencies, error handling, and operational procedures for each pipeline. The technical and data architecture documentation shall include, at a minimum, the following key input areas: |
1) Existing system design documents and data models
2) System performance and capacity requirements
3) Data security and compliance requirements
4) Source-to-target data mapping
5) Defined business rules and data transformation logic based on approved or in development BFMs
Due Date: An initial version shall be delivered 90 days after contract period of performance start and within 90 days for any command being supported under this effort. Updates shall be provided as needed with specific updates submitted concurrently with the deployment of each new or significantly modified product.
Medium of Delivery / Format: Electronic; MS Word, MS Visio (for diagrams), and a searchable, exportable format for the Data Dictionary (e.g. MS Excel). Pipeline documentation may be in MS Word or a native repository.
| 4.8 |
| Enterprise Data, Data Analytics, and AI Strategy |
| Description and Guidelines: The comprehensive strategy document that includes a data maturity assessment, technology roadmap, and workforce plan. USFF HQ/BSO-60 strategy due 90 days after contract award. Echelon III and other supported command strategies due 90 days from formal request submitted by COR. |
Medium of Delivery / Format: Electronic; MS Word
| 4.9 |
| Change Management and Communications Plan |
| Description and Guidelines: A unified strategic document for facilitating user adoption, managing stakeholder expectations, and promoting data initiatives. The plan shall identify key stakeholder groups, define key messages and communication channels, and provide a schedule of communication and engagement activities. Key Inputs: |
1) Project charter and vision
2) Stakeholder analysis
3) A summary of the project's goals and benefits
Due Date: Submitted to the COR and ACOR no later than 60 days after the contract period of performance start date and within 60 days for any command being supported under this effort. This plan should be updated as needed for major new initiatives that are planned.
Medium of Delivery / Format: Electronic; MS Word or MS PowerPoint.
| 4.10 |
| Data Continuity and Service Interruption Plan |
| Description and Guidelines: A formal plan that documents the contractor's procedures for responding to data loss incidents or platform service interruptions for all critical data stores. This plan is not for performing backups, but for outlining the processes to restore data and operations using the capabilities of the hosting providers (.). The plan must include, for each major data platform: |
1) A summary of the platform's native data recovery features (e.g., SharePoint recycle bin, versioning, platform-level snapshots).
2) The formal procedures and Points of Contact (POCs) for requesting data restoration from the platform owner (DON CDAO, PEO Digital).
3) A communications plan for notifying the COR and users of a data loss incident or service outage.
4) Contingency procedures for manual data reconstruction in the event that platform-native tools are insufficient.
Due Date: Submitted to the COR and ACOR no later than 120 business days after the contract period of performance start date and within 120 days for any command being supported under this effort. The plan shall be reviewed and updated at last annually and within 10 business days of a significant change in platform provider procedures.
Medium of Delivery / Format: Electronic; MS Word.
| 4.11 |
| MLOps Lifecycle Documentation |
| Description and Guidelines: Documentation covering the end-to-end model lifecycle, including feature engineering, deployment, and continuous monitoring plans. A key component of this deliverable is the validation report which includes the developed models (AI/ML, predictive, etc.) and accompanying reports that assess accuracy, performance, and bias/fairness. The MLOps Lifecycle documentation shall include, at a minimum, the following key input areas: |
1) The CI/CD pipeline design for model deployment
2) The strategy for monitoring models in production
3) Version control system repository details
4) A clear definition of the business problem to be solved
5) The curated dataset for model training and validation
6) Success criteria and performance metrics for the model
Due Date: Submitted concurrently with the delivery of each analytic model for review and acceptance. The overall MLOps process documentation should be established with the first production model deployment and updated for each subsequent model or significant process change.
Medium of Delivery / Format: Electronic; Model format (e.g., Pickle file, containerized application), a report in MS Word or PDF, and lifecycle documentation in MS Word or a shared code repository's documentation (e.g., a README file).
| 4.12 |
| UI/UX Research and Testing Reports |
| Description and Guidelines: A consolidated deliverable including findings from user research, persona development, and usability testing sessions. The report shall summarize the research methodology, participant demographics, key findings, and actionable recommendations. Key Inputs: |
1) User personas and journey maps
2) Wireframes, mockups, and interactive prototypes
3) Feedback and data from user interviews and usability testing sessions
Due Date: Submitted to the COR within 10 business days following the completion of each research or testing phase.
Medium of Delivery / Format: Electronic; MS Word or MS PowerPoint.
| 4.13 |
| Emerging Technology Assessment Report |
| Description and Guidelines: A quarterly (or ad-hoc) report performed by the contractor and validated for use by government personnel analyzing new technologies, their potential benefits, risks, and recommendations for adoption. Each assessment should include a high-level cost-benefit analysis and a clear recommendation (e.g., Adopt, Pilot, Monitor, or Ignore). The Emerging Technology Assessment Report shall include, at a minimum, the following key input areas: |
1) Market research and industry trend analysis reports
2) Vendor-provided product documentation and white papers
3) Results from any internal proofs-of-concept or pilot studies
Due Date: Submitted to the COR quarterly, no later than the last working day of each quarter. Ad-hoc reports shall be delivered as requested by the COR.
Medium of Delivery / Format: Electronic; MS Word or MS PowerPoint.
| 4.14 |
| Training Materials |
| Description and Guidelines: A complete set of training enablement content, including user guides, slick sheets, videos, tutorials, and workshop materials, tailored to specific user roles and skill levels. Training Materials shall include, at a minimum, the following key input areas: |
1) An understanding of the target audience and their skill levels
2) System documentation, including user manuals and process flows
3) Defined learning objectives for the training
4) Feedback from pilot training sessions or user acceptance testing (e.g. UI/UX Research and Testing Reports)
Due Date: All materials for a specific system or dashboard must be delivered at least 5 business days prior to any scheduled training session or go-live date of an analytic product.
Medium of Delivery / Format: Electronic; MS Word, MS PowerPoint, PDF, MP4 or other standard video formats.
| 4.15 |
| Interactive Dashboards and Visualizations |
| Description and Guidelines: The final, user-friendly data visualization products (e.g., Qlik, Tableau, Power BI dashboards). Delivery includes providing user access to the production dashboard and a brief user guide on its features, data sources, and intended use. Interactive Dashboards and Visualizations shall include, at a minimum, the following key input areas: |
1) A list of Key Performance Indicators (KPIs) and metrics
2) The defined target audience and their information needs
3) Access to the underlying data sources
4) Wireframes or mockups of the desired dashboard layout
5) Reference to the UI/UX Research and Testing Reports, Basis-for-Measurements, and Training Materials as appendices
Due Date: Delivered as developed, per the project schedule provided by the government for each individual dashboard or visualization.
Medium of Delivery / Format: Electronic; Access provided via the specified Business Intelligence tool (e.g., Tableau, Power BI, Qlik), and an extract of the application file for backup storage.
| 4.16 |
| End of Contract Final Report |
| Description and Guidelines: A comprehensive report delivered at the conclusion of the contract, summarizing all work performed, deliverables provided, and lessons learned. |
Due Date: Submitted to the COR no later than the 15 days prior to the end of contract performance.
Medium of Delivery / Format: Electronic; MS Word
5. PERSONNEL REQUIREMENTS AND LABOR CATEGORIES
The key to accomplishing the tasks in each functional area are the personnel assigned. As an umbrella program, the premise behind manning is “one team,” with each contractor’s primary role defined and secondary skills applied to promote efficiency and flexibility across the effort. It is envisioned that the Contractor will effectively manage its workforce across the program and the various commands including shifting resources to accommodate changes in schedules or high tempo requirements.
5.1. General Personnel Requirements:
5.1.1. Core Competency: All personnel proposed shall possess and be able to demonstrate significant knowledge, skills, and experience in the functional areas they are assigned to support. Currency in training, technical requirements, and relevant DOW/DON policies and guidance is a critical standard for successful performance under this PWS.
5.1.2. Educational and Experience Equivalency: To provide maximum flexibility in sourcing expert talent, the following equivalency standards shall be used. The Government places a strong emphasis on relevant, demonstrated professional experience.
5.1.3. Standard for Substitution: Professional experience may be substituted for educational requirements, and vice-versa. Experience must be directly relevant to the tasks outlined in the PWS to be considered for substitution.
5.1.4. Equivalency Scale:
5.1.4.1. A Bachelor’s Degree is considered equivalent to four (4) years of relevant professional experience.
5.1.4.2. A Master’s Degree is considered equivalent to six (6) years of relevant professional experience.
5.1.5. Application Example:
5.1.5.1. If a specific labor category requires a "Bachelor's Degree + 5 years of experience," a candidate can meet this requirement in the following ways:
5.1.5.1.1. With a Degree: Possesses a Bachelor's Degree and 5 years of relevant experience.
5.1.5.1.2. Without a Degree: Possesses 9 years of total relevant experience (5 years required experience + 4 years substituting for the degree).
5.1.6. Exception for Mandatory Degrees:
5.1.6.1. This substitution policy applies to all positions unless a specific degree (e.g., Ph.D. in a specific field) is explicitly cited as a mandatory, non-substitutable requirement for a particular labor category within this PWS.
5.1.7. Educational requirements and any commensurate documented experience / equivalencies in the field or additional required education elements are listed by position in the PWS.
5.1.8. Each candidate shall possess proven communications skills, orally and verbally at the junior management and senior executive level.
5.1.9. Any additional required/desired experience elements are outlined by position in the PWS.
5.1.10. All personnel are required to have, at a minimum, an active secret clearance. Any additional required clearance elements will be outlined by position in the PWS.
5.1.11. If the Contracting Officer and/or COR questions the qualifications or competence of any person performing under the contract, the burden of proof to sustain that the person is qualified shall be upon the Contractor.
5.2. Labor Categories.
5.2.1. General Requirements:
5.2.1.1. The Contractor is responsible for the selection, training, management and performance of the workforce provided to accomplish the tasks within this contract. The skills, knowledge and past experience of the various team members that demonstrate a high probability of success is the information that will be required by the Government for task evaluation. The objective is to define what work is required for the various tasks and allow the Contractor to determine how to efficiently use the available workforce to meet the performance objectives.
5.2.1.2. Minimum qualifications and any additional qualifications for the respective functional areas are listed below as well as the Education and Certifications, Experience, and necessary Skills.
5.2.2. Labor Category Descriptions and Requirements:
5.2.2.1. Data Analyst: Responsible for collecting, analyzing, and interpreting data to identify trends, patterns, and insights that can inform business decisions and improve performance. Works closely with stakeholders to understand their data needs and develop analytical solutions to meet those needs. Responsible for creating reports and visualizations to communicate findings to both technical and non-technical audiences. Collect and cleanse data from various sources. Analyze data using statistical techniques and data mining tools. Develop and maintain databases and data systems. Create reports and dashboards to visualize data and communicate findings. Identify trends and patterns in data and provide insights to stakeholders. Collaborate with stakeholders to understand data needs and develop analytical solutions. Document data processes and procedures. Ensure data quality and accuracy. Present findings to stakeholders in a clear and concise manner.
Skills and Experience: 2+ years of experience with data analysis, analytic tools, and techniques. Strong analytical and problem-solving skills. Excellent communication and presentation skills. Experience with SQL, Excel, data visualization tools (Tableau, Power BI), statistical analysis (basic to intermediate), data cleansing, data wrangling, communication, problem-solving, data quality management, data profiling tools, Metadata management, data modeling, data dictionaries, and data catalogs.
Education and Certifications: Bachelor's degree in a related field (e.g., Statistics, Mathematics, Computer Science, Economics).
5.2.2.2. Data Analyst – Mid Level: Responsible for performing data analysis, developing reports, and creating visualizations to support data-driven decision-making. Works independently and as part of a team to identify opportunities for improvement and provide actionable insights. Responsible for mentoring/leading junior analysts and contribute to the development of data analysis best practices. Collect, clean, and validate data from multiple sources, ensuring data integrity and accuracy. Perform exploratory data analysis to identify trends, patterns, and anomalies. Develop and maintain data models and databases. Create reports and dashboards using tools such as Tableau, Power BI, or similar. Conduct statistical analysis and develop predictive models using tools such as R or Python. Communicate findings and recommendations to stakeholders in a clear and concise manner. Collaborate with other analysts and developers to implement data solutions. Provide guidance on data analysis techniques. Document data analysis processes and procedures. Contribute to the development of data analysis best practices.
Skills and Experience: 4+ years of experience with data analysis, analytic tools, and techniques. Strong proficiency in R or Python, SQL, Excel, and multiple data visualization tools (e.g., Tableau, Power BI). Experience with statistical analysis and predictive modeling techniques. Strong analytical and problem-solving skills. Excellent communication and presentation skills.
Education and Certifications: Bachelor's degree in a related field (e.g., Statistics, Mathematics, Computer Science, Economics).
5.2.2.3. Data Analyst – Senior: Responsible for leading data analysis efforts, providing strategic direction and technical expertise to support data-driven decision-making across the organization. Assist in the design and implement data analysis solutions, mentoring junior analysts, and ensuring the quality and accuracy of data products. Works closely with stakeholders to understand their data needs and develop analytical strategies to meet those needs. Lead data analysis projects from inception to completion. Design and implement data analysis solutions to meet business needs. Develop and maintain data models, databases, and data pipelines. Create advanced reports and dashboards using tools such as Tableau, Power BI, or similar. Conduct advanced statistical analysis and develop predictive models using tools such as R or Python. Communicate findings and recommendations to executive leadership. Collaborate with other teams to integrate data analysis solutions into existing systems. Mentor junior data analysts and provide guidance on data analysis techniques and best practices. Develop and maintain data analysis standards and procedures. Ensure the quality and accuracy of data products. Identify and evaluate new data analysis tools and technologies.
Skills and Experience: 7+ years of experience in data analysis. Expert proficiency in R or Python, SQL and multiple data visualization tools (e.g., Tableau, Power BI). Extensive experience with statistical analysis and predictive modeling techniques. Strong leadership and mentoring skills. Excellent communication and presentation skills, including the ability to present complex information to executive audiences. Experience with data governance and data quality principles.
Education and Certifications: Bachelor's degree in a related field (e.g., Statistics, Mathematics, Computer Science, Economics).
5.2.2.4. Business Analyst: Responsible for supporting the translation of business and mission needs into technical requirements. Assist in gathering, documenting, and organizing information. Participate in the analysis of business processes and help ensure that the development team has a clear understanding of stakeholder needs. Assists in preparing for and documenting the outcomes of requirements elicitation sessions (e.g., interviews, workshops). Documents business requirements, user stories, and use cases as defined by senior team members. Creates basic process flow diagrams and other visual aids to support requirement clarity. Helps maintain project documentation, including action items, meeting minutes, and requirements traceability matrices. Participates in user acceptance testing (UAT) by executing test cases and documenting defects. Provides administrative and logistical support for stakeholder meetings and project activities. Assists in the creation of basic user guides and "how-to" documentation to explain system features to end-users.
Skills and Experience: 2+ years of experience in a business analysis, project coordination, or related role. Strong organizational skills, excellent written and verbal communication, attention to detail, and effective note-taking. Basic understanding of project lifecycle and software development concepts (Agile, Waterfall). Proficiency in Microsoft Office Suite (Word, Excel, PowerPoint, Visio). Exposure to collaboration tools like Jira, Azure Dev Ops, or MS Teams is a plus.
Education: Bachelor's degree in Business Administration, Management Information Systems, or a related field.
5.2.2.5. Business Analyst – Mid Level: Responsible for eliciting, analyzing, validating, and documenting the business and functional requirements for data analytics projects. Functions as the primary liaison between stakeholders and the technical team, ensuring that mission needs are clearly understood and translated into actionable specifications. Works independently on significant project components and contributes to improving business processes. Develops user-focused documentation and training material to ensure successful solution adoption. Leads requirements elicitation workshops and stakeholder interviews to uncover underlying business needs and objectives. Analyzes business processes and workflows to identify opportunities for improvement and automation. Authors clear, concise, and unambiguous business requirements documents (BRDs), user stories with acceptance criteria, and functional specifications. Develops detailed process models (using BPMN or similar notation), wireframes, and data flow diagrams. Facilitates requirements validation sessions and manages changes to the requirements baseline.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .