A02.12 PWS IWR Enterprise Management Tool.docx
DOCX document 68 KB Posted
- Solicitation number
- W912HQ22S0016
About this file
This performance work statement describes operations and maintenance services required for the US Army Corps of Engineers Institute for Water Resources Enterprise Management Tool. Key details include:
The contractor shall provide regular maintenance, modifications, and data updates for the EMT system, which includes a project management tool and dashboard residing on AWS. Maintenance involves tasks like routine updates, bug fixes, and documentation. Modifications include new reports and views for management. Data updates involve monthly refreshes and quality assurance reviews. The contractor must be familiar with USACE business processes and systems. The base period of performance is 12 months with four optional one-year extensions. The contractor will participate in bi-monthly and quarterly meetings and provide required deliverables and documentation throughout the period of performance.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| A02.10 Questionnaire for IWR EMT O+M.docx | DOCX document |
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
IWR ENTERPRISE MANAGEMENT TOOL (EMT) OPERATIONS AND MAINTENANCE (O&M)
PERFORMANCE WORK STATEMENT (PWS)
1. BACKGROUND
The EMT is an Institute for Water Resources (IWR) tool for project, program, and enterprise management using Oracle, ColdFusion and JavaScript. The EMT is made up of two components, a Project Management Tool and a Dashboard. The current Project Management Tool has been operational since 2009 and the Dashboard since 2015.
The Project Management Tool is a planning tool used by project managers, budget/program analysts and the IWR Corporate Board. In addition to Project Management Plans (PMPs) for individual projects, the EMT is a repository of data for all IWR projects and is used to generate project and corporate level reports.
The Dashboard is a management tool used by the IWR Corporate Board for enterprise management. It provides a single location for management to view a general IWR profile and evaluate the overall performance of the organization using key indicators (travel, overhead, funding and manpower). The displays show trends with the ability to forecast U.S. Army Corps of Engineers (USACE) data as it relates to IWR and is available for management to have monthly In Progress Reviews.
2. SCOPE
The EMT is a fully operational system currently residing within the Corps network and operating within the Civil Works Business Intelligence (CWBI) Amazon Web Services (AWS) Cloud hosting environment. The work under this contract shall provide the regular operations and maintenance for the EMT to support IWR program and project management and its enterprise oversight and management.
The creation and maintenance of virtual private clouds, web application firewalls, reverse proxies, software installation, etc. will be the responsibility of a third-party cloud provider. However, work under this contract requires a detailed understanding of AWS generally and the configuration of these technologies specifically in order to maintain the EMT application and request revisions to the configuration. It also includes a need to understand security at every level. Technologies used include AWS Elastic Container Service (ECS), AWS Code Pipeline, AWS CodeCommit, AWS Elastic Container Repository, Docker, AWS Simple Email Service (SES), AWS Secrets Manager, AWS CloudWatch, AWS CloudTrail, AWS Simple Storage Service (S3), and AWS Relational Database Service (RDS) for Oracle 19c in the CWBI Govcloud environment.
The contractor must be familiar with USACE Project Delivery Business Processes (PDBP) and related guidance, US Army Corps of Engineers Financial Management System (CEFMS) II, Program and Project Management Information System (PROMIS), the USACE Enterprise Data Warehouse and Chief Information Office (CIO)/G-6 Information Technology (IT) requirements and guidance along with industry best practices.
3. GENERAL REQUIREMENTS
The following sub-sections provide details of various general requirements for this effort.
3.1 Non-Personal Services
The contractor shall provide strictly non-personal services and contractor employees are not subject to direct supervision and control by the Government. The contractor shall advise and support the Government but shall not make final decisions or certifications on behalf of the Government nor perform any inherently governmental functions. The contractor and its employees shall not represent the Government nor appear to represent the Government in performance of these contract services. Contractor personnel shall clearly identify themselves as contractor employees in all interactions during contract performance.
3.2 Place of Performance
All work under this contract will be performed at the contractor’s site.
3.3 Period of Performance
The period of performance (PoP) for the base contract is twelve (12) months. Four optional years are also included, which will be executed at the end of each subsequent year assuming funds are available.
3.4 Materials
All materials, minus expendable supplies, purchased by the contractor with funds from this contract and used as part of this contract, become and remain the property of the Government.
3.5 Travel
Two onsite visits to the Alexandria, VA office by the contractor’s primary Program Manager and local team member (if required).
4. PERFORMANCE REQUIREMENTS (TASK AREAS)
4.1 Regular EMT Operations and Maintenance Task Areas
The activities within this task area will be evaluated and prioritized by the IWR Project Manager and contracting officer representative (COR). Activities will reflect program requirements and resolution of user issues. The testing of all database and interface modifications will be performed on government furnished equipment (GFE). This requirement is designed to provide service for 12 months from the date of award.
4.1.1 Task 1. Routine Maintenance: The contractor shall provide regular maintenance to ensure the EMT operates on a continuous basis to include:
| • | Posting of revised web pages and related files after local revision and testing. Typical tasks include: |
| o | Maintaining ColdFusion Docker container image with web application |
| o | Deploying container locally in Docker and testing deployment locally prior to any push to AWS ECS |
| o | Deploying container to AWS ECS test environment and subsequent Quality Assurance (QA) |
| o | Deploying container to AWS ECS production environment and subsequent QA |
| o | Responding to vulnerabilities reported via container and website scans |
| o | Revising Docker container implementation based on needed revisions to address vulnerabilities or changes to the ColdFusion container images |
| o | Maintaining underlying JavaScript packages |
| o | Maintaining needed secrets for container deployment |
| o | Responding to revisions to the AWS ECS deployment task definitions |
| o | Creating of, responding to, and verification of Jira tickets |
| • | Assistance with modification of database tables |
| • | Resolution of minor operating bug fixes |
| • | Minor report and functionality revisions |
| • | Revisions to the EMT Control Panel |
| • | QA related to posting of revised files |
| • | Review EMT Dashboard files and operability |
| • | Improvements to EMT Dashboard display and export layouts |
| • | Improvements to EMT Project Management Tool display and export layouts |
| • | New data code updates |
| • | Resolving EMT user issues and assistance with monitoring implementation of new user registration |
| • | Modifying IWR performance measure parameters tracked in the EMT |
| • | Modifying required data format for display changes, such as revisions to EMT functionality when browser functionality changes, revisions to accommodate database or other platform updates or EMT CWBI configuration reviews |
| • | Examples of FY21 and FY22 work in this category include revisions or updates to: |
| o | Handling of existing and new fund appropriations to include Revolving Funds and revisions of associated reports |
| o | PMP Project Record and Project Status functionality |
| o | PM Tool Reports such as the Direct Funding by AMSCO report, Labor Hours by Supervisor Report and Budget Forecast Report |
| o | PMP Activities and Resources functionality |
| o | “All PMPs” and “Projects” functionality and display |
| o | Duplication and snapshot functionality in the PM Tool |
| o | PDF reporting related to browser changes |
| o | Software updates (jQuery, ColdFusion, etc.) |
| o | Deliverables and Milestones functionality and reporting |
| o | User access and login (ongoing) |
| o | Dashboard Data Displays and revisions to available reports and graphics |
4.1.2 Task 2. EMT Modifications: The contractor shall perform modifications to the EMT to provide management with required information views for management decisions to include both the Project Management Tool and Dashboard. This shall include Project Management Tool modifications to current reports and modules and generation of new reports. Dashboard modifications shall include performance measure target parameter changes and displays. Dashboard profile views display modifications, both graph and data, and some new views within the current data sets. The specific reports are TBD but shall include approximately 10 modifications and the development of 5 new reports. EMT Modifications will include:
· Information views for management decisions for the Project Management Tool
· Modifications to current reports and modules
· Generation of new reports
· Information views for management decisions for the Dashboard
· Performance measure target parameter revisions
· Performance measure display revisions
· Profile view display modifications, both graph and data
· New profile views (graph and data) within the current data sets
· Finalize functionality needed to move the EMT to CAC log-in. Possible tasks include creating new log-in procedures in the EMT App using communication with Test Keycloak Server, revising people management to integrate with Keycloak Server and submitting required tickets to facilitate the transition.
· Investigate ability to incorporate USACE data visualization services, such as Qlik Sense or Microsoft Power BI, for EMT Dashboard and reports in the Project Management Tool
· Examples of modifications made in FY21 and FY22 include:
· Revisions to functionality, specifically in the PMP Obligation Project Plan module and reporting related to new USACE carryout rules
· Revisions to functionality with Direct Funding by AMSCO report utilizing repositioned data for September reports
· Creation of a new earned value report
· Modifications to General Expenses (GE) 410 funding handling and reporting
· Refinements to organization structure in both the PM Tool and Dashboard
· Incorporating Projects without a P2 Number in the PM Tool
4.1.3 Task 3. Data Updates: The contractor shall support the Government team to refresh EMT data and production modules. The contractor shall perform regular quality assurance evaluations to ensure system integrity on a regular basis. The Project Management Tool is updated by the Government team mid-month and at the end of the month (approximately 15 files). The Dashboard is updated monthly using data updated for the Project Management Tool.
The Project Management Tool, Direct Funding Status by Army Management Structure Code (AMSCO), will be updated by the Government team within one business day of receiving notification of either data availability or data files while the complete Project Management Tool and Dashboard are updated within three business days.
The contractor shall make minor updates to underlying data structure, queries and views that are occasionally needed to support Project Management Tool and Dashboard reporting.
Contractor efforts related to this task shall include:
· Perform regular QA evaluations to ensure system integrity
· Provide QA review of the Project Management Tool mid-month and end of the month (within 1 day of data availability)
· Provide QA review of the Dashboard end of the month (within 1 day of data availability)
· Review Project Management Tool Direct Funding Status by Army Management Structure Code (AMSCO) report data within one working day of receiving notification of data availability
· Update queries and views that support Project Management Tool and Dashboard reporting
· Update underlying data structure that supports Project Management Tool and Dashboard reporting
· Assist the Government team with refreshing EMT data and production modules when needed.
· Examples of additional specific work handled under this task during FY21 and FY22:
· Evaluate data regarding repositioned funds data incorporation with the monthly update and its effect on current reports and schedules
· Data troubleshooting for both PM Tool and Dashboard
· Migrate data to the appropriate CWBI AWS database (i.e. Production, Test or Development)
· Appropriations structure review and revision for how data is pulled into the EMT
4.1.4 Task 4. Bi-Monthly In-Progress Reviews (IPRs) and Quarterly CWBI Sharing Sessions: The contractor shall participate in bi-monthly IPRs with the EMT Government team and in Quarterly CWBI Sharing Sessions. The IPRs shall be 1-hour in duration, and during the IPRs, the IWR Project Manager and COR will consult with the contractor to evaluate and prioritize specific EMT activities to be accomplished. Additional requests for updates and enhancements will be forwarded to the contractor by the IWR Project Manager for evaluation and addressed by the contractor during the bi-monthly IPRs through prioritization recommendations. The contractor shall prepare an agenda for each IPR to facilitate discussions. Additional reviews shall be conducted upon request from the IWR Project Manager or the contractor for new or major revision activities. Other ad hoc meetings, such as with the CWBI team, may be required on an as-needed basis. During those months, the ad hoc meetings take the place of the bi-monthly IPRs. For situational awareness, the contractor shall also attend Quarterly CWBI Sharing Sessions that are 1-hour in duration and hosted by the CWBI Program Office. These sessions cover topics specific to CWBI regarding Management, Data, Technical, Cybersecurity and Operational updates.
4.1.5 Task 5. Documentation: The contractor shall update, create, revise and/or maintain:
· Project Management Tool User Guide
· Project Management Tool and Dashboard report data loading and format parameters and process.
· EMT System Data Management Manual
· EMT System Management Manual
· Dashboard User Guide
· Dashboard Technical documentation
· EMT for documentation for CWBI in DI2E
· EMT ticketing information for CWBI in Jira
· Online help documents and pages
· Test plan documentation
· ASD STIG checklist review
4.2 Option Year 1 EMT Operations and Maintenance Task Areas
The activities within this task area will be evaluated and prioritized by the IWR Project Manager and contracting officer representative (COR). Activities will reflect program requirements and resolution of user issues. The testing of all database and interface modifications will be performed on government furnished equipment (GFE). This requirement is designed to provide service for 12 months from the date of award.
4.2.1 Task 1. Routine Maintenance: The contractor shall provide regular maintenance to ensure the EMT operates on a continuous basis to include:
| • | Posting of revised web pages and related files after local revision and testing. Typical tasks include: |
| o | Maintaining ColdFusion Docker container image with web application |
| o | Deploying container locally in Docker and testing deployment locally prior to any push to AWS ECS |
| o | Deploying container to AWS ECS test environment and subsequent Quality Assurance (QA) |
| o | Deploying container to AWS ECS production environment and subsequent QA |
| o | Responding to vulnerabilities reported via container and website scans |
| o | Revising Docker container implementation based on needed revisions to address vulnerabilities or changes to the ColdFusion container images |
| o | Maintaining underlying JavaScript packages |
| o | Maintaining needed secrets for container deployment |
| o | Responding to revisions to the AWS ECS deployment task definitions |
| o | Creating of, responding to, and verification of Jira tickets |
| • | Assistance with modification of database tables |
| • | Resolution of minor operating bug fixes |
| • | Minor report and functionality revisions |
| • | Revisions to the EMT Control Panel |
| • | QA related to posting of revised files |
| • | Review EMT Dashboard files and operability |
| • | Improvements to EMT Dashboard display and export layouts |
| • | Improvements to EMT Project Management Tool display and export layouts |
| • | New data code updates |
| • | Resolving EMT user issues and assistance with monitoring implementation of new user registration |
· Resolving or modifying functionality for CAC log-in and submitting tickets if needed related to Keycloak server issues
· Modifying IWR performance measure parameters tracked in the EMT
· Modifying required data format for display changes, such as revisions to EMT functionality when browser functionality changes, revisions to accommodate database or other platform updates or EMT CWBI configuration reviews
4.2.2 Task 2. EMT Modifications: The contractor shall perform modifications to the EMT to provide management with required information views for management decisions to include both the Project Management Tool and Dashboard. This shall include Project Management Tool modifications to current reports and modules and generation of new reports. Dashboard modifications shall include performance measure target parameter changes and displays. Dashboard profile views display modifications, both graph and data, and some new views within the current data sets. The specific reports are TBD but shall include approximately 10 modifications and the development of 5 new reports. EMT Modifications will include:
· Information views for management decisions for the Project Management Tool
· Modifications to current reports and modules
· Generation of new reports
· Information views for management decisions for the Dashboard
· Performance measure target parameter revisions
· Performance measure display revisions
· Profile view display modifications, both graph and data
· New profile views (graph and data) within the current data sets
· Continue efforts to investigate the ability to incorporate USACE data visualization services, such as Qlik Sense or Microsoft Power BI, for EMT Dashboard and reports in the Project Management Tool
4.2.3 Task 3. Data Updates: The contractor shall support the Government team to refresh EMT data and production modules. The contractor shall perform regular QA evaluations to ensure system integrity on a regular basis. The Project Management Tool is updated by the Government team mid-month and at the end of the month (approximately 15 files). The Dashboard is updated monthly using data updated for the Project Management Tool.
The Project Management Tool, Direct Funding Status by Army Management Structure Code (AMSCO), will be updated by the Government team within one business day of receiving notification of either data availability or data files while the complete Project Management Tool and Dashboard are updated within three business days.
The contractor shall make minor updates to underlying data structure, queries and views that are occasionally needed to support Project Management Tool and Dashboard reporting.
Contractor efforts related to this task shall include:
· Perform regular QA evaluations to ensure system integrity
· Provide QA review of the Project Management Tool mid-month and end of the month (within 1 day of data availability)
· Provide QA review of the Dashboard end of the month (within 1 day of data availability)
· Review Project Management Tool Direct Funding Status by Army Management Structure Code (AMSCO) report data within one working day of receiving notification of data availability
· Update queries and views that support Project Management Tool and Dashboard reporting
· Update underlying data structure that supports Project Management Tool and Dashboard reporting
· Assist the Government team with refreshing EMT data and production modules when needed.
4.2.4 Task 4. Bi-Monthly In-Progress Reviews (IPRs) and Quarterly CWBI Sharing Sessions: The contractor shall participate in bi-monthly IPRs with the EMT Government team and in Quarterly CWBI Sharing Sessions. The IPRs shall be 1-hour in duration, and during the IPRs, the IWR Project Manager and COR will consult with the contractor to evaluate and prioritize specific EMT activities to be accomplished. Additional requests for updates and enhancements will be forwarded to the contractor by the IWR Project Manager for evaluation and addressed by the contractor during the bi-monthly IPRs through prioritization recommendations. The contractor shall prepare an agenda for each IPR to facilitate discussions. Additional reviews shall be conducted upon request from the IWR Project Manager or the contractor for new or major revision activities. Other ad hoc meetings, such as with the CWBI team, may be required on an as-needed basis. During those months, the ad hoc meetings take the place of the bi-monthly IPRs. For situational awareness, the contractor shall also attend Quarterly CWBI Sharing Sessions that are 1-hour in duration and hosted by the CWBI Program Office. These sessions cover topics specific to CWBI regarding Management, Data, Technical, Cybersecurity and Operational updates.
4.2.5 Task 5. Documentation: The contractor shall update, create, revise and/or maintain:
· Project Management Tool User Guide
· Project Management Tool and Dashboard report data loading and format parameters and process.
· EMT System Data Management Manual
· EMT System Management Manual
· Dashboard User Guide
· Dashboard Technical documentation
· EMT for documentation for CWBI in DI2E (or current application used by CWBI)
· EMT ticketing information for CWBI in Jira
· Online help documents and pages
· Test plan documentation
· ASD STIG checklist review
4.2.6 Optional Task 1. EMT Modernization Phase 1: Modernize Dashboard – Modernize the EMT Dashboard by establishing it as its own microservice, including taking advantage of new cloud native tools available to the CWBI cloud. This will require data availability through a Representational State Transfer Application Programming Interface (REST API) service. This task will include project management, new system diagrams, new containerization, programming, quality assurance, documentation, and possibly design mockups.
4.2.7 Optional Task 2. Enhance CWBI Data Integration: Update CWBI data integration to include linking directly to CWBI data and reporting where allowed. This task may require additional data views in the database and updating of the monthly data update processes and, perhaps, underlying tables. This task includes designs illustrating any changes to data usage and how database table, view and query structure will change. It also includes project management, programming, quality assurance, and documentation.
4.2.8 Optional Task 3. Incorporate Qlik Sense or Microsoft Power BI: Based on the investigations done in Base Task 2, the contractor shall implement the functionality required to incorporate Qlik Sense or Microsoft Power BI displays in the EMT Dashboard and/or reports in the Project Management Tool. The Government team shall acquire required licenses.
4.2.9 Optional Task 4. Refine Functionality for second Engineer Reporting Organization Code (EROC)’s use of the EMT: The previous EMT contract included a task to expand the EMT for use by a second USACE EROC (HQUSACE Planning and Policy Division). The contractor shall assist with adding parameters and reviewing current parameters for the additional EROC, ensuring data and reporting provide expected outputs. The contractor shall assist with processing monthly data updates and associated reports. The contractor shall expand Dashboard functionality to add the additional EROC.
4.2.10 Optional Task 5. Mandatory USACE Software Updates: The contractor shall perform the required coding changes due to USACE changes to application versions that impact application design or functionality. The Government team shall acquire required licenses if applicable.
4.3 Option Year 2 EMT Operations and Maintenance Task Areas
The activities within this task area will be evaluated and prioritized by the IWR Project Manager and contracting officer representative (COR). Activities will reflect program requirements and resolution of user issues. The testing of all database and interface modifications will be performed on government furnished equipment (GFE). This requirement is designed to provide service for 12 months from the date of award.
4.3.1 Task 1. Routine Maintenance: The contractor shall provide regular maintenance to ensure the EMT operates on a continuous basis to include:
| • | Posting of revised web pages and related files after local revision and testing. Typical tasks include: |
| o | Maintaining ColdFusion Docker container image with web application |
| o | Deploying container locally in Docker and testing deployment locally prior to any push to AWS ECS |
| o | Deploying container to AWS ECS test environment and subsequent Quality Assurance (QA) |
| o | Deploying container to AWS ECS production environment and subsequent QA |
| o | Responding to vulnerabilities reported via container and website scans |
| o | Revising Docker container implementation based on needed revisions to address vulnerabilities or changes to the ColdFusion container images |
| o | Maintaining underlying JavaScript packages |
| o | Maintaining needed secrets for container deployment |
| o | Responding to revisions to the AWS ECS deployment task definitions |
| o | Creating of, responding to, and verification of Jira tickets |
| • | Assistance with modification of database tables |
| • | Resolution of minor operating bug fixes |
| • | Minor report and functionality revisions |
| • | Revisions to the EMT Control Panel |
| • | QA related to posting of revised files |
| • | Review EMT Dashboard files and operability |
| • | Improvements to EMT Dashboard display and export layouts |
| • | Improvements to EMT Project Management Tool display and export layouts |
| • | New data code updates |
| • | Resolving EMT user issues and assistance with monitoring implementation of new user registration |
· Resolving or modifying functionality for CAC log-in and submitting tickets if needed related to Keycloak server issues
· Modifying IWR performance measure parameters tracked in the EMT
· Modifying required data format for display changes, such as revisions to EMT functionality when browser functionality changes, revisions to accommodate database or other platform updates or EMT CWBI configuration reviews
· Maintain required Qlik Sense or Power BI functionality for EMT Dashboard and Project Management Tool (if incorporated with previous Optional Task)
4.3.2 Task 2. EMT Modifications: The contractor shall perform modifications to the EMT to provide management with required information views for management decisions to include both the Project Management Tool and Dashboard. This shall include Project Management Tool modifications to current reports and modules and generation of new reports. Dashboard modifications shall include performance measure target parameter changes and displays. Dashboard profile views display modifications, both graph and data, and some new views within the current data sets. The specific reports are TBD but shall include approximately 10 modifications and the development of 5 new reports. EMT Modifications will include:
· Information views for management decisions for the Project Management Tool
· Modifications to current reports and modules
· Generation of new reports
· Information views for management decisions for the Dashboard
· Performance measure target parameter revisions
· Performance measure display revisions
· Profile view display modifications, both graph and data
· New profile views (graph and data) within the current data sets
4.3.3 Task 3. Data Updates: The contractor shall support the Government team to refresh EMT data and production modules. The contractor shall perform regular QA evaluations to ensure system integrity on a regular basis. The Project Management Tool is updated by the Government team mid-month and at the end of the month (approximately 15 files). The Dashboard is updated monthly using data updated for the Project Management Tool.
The Project Management Tool, Direct Funding Status by Army Management Structure Code (AMSCO), will be updated by the Government team within one business day of receiving notification of either data availability or data files while the complete Project Management Tool and Dashboard are updated within three business days.
The contractor shall make minor updates to underlying data structure, queries and views that are occasionally needed to support Project Management Tool and Dashboard reporting.
Contractor efforts related to this task shall include:
· Perform regular QA evaluations to ensure system integrity
· Provide QA review of the Project Management Tool mid-month and end of the month (within 1 day of data availability)
· Provide QA review of the Dashboard end of the month (within 1 day of data availability)
· Review Project Management Tool Direct Funding Status by Army Management Structure Code (AMSCO) report data within one working day of receiving notification of data availability
· Update queries and views that support Project Management Tool and Dashboard reporting
· Update underlying data structure that supports Project Management Tool and Dashboard reporting
· Assist the Government team with refreshing EMT data and production modules when needed.
4.3.4 Task 4. Bi-Monthly In-Progress Reviews (IPRs) and Quarterly CWBI Sharing Sessions: The contractor shall participate in bi-monthly IPRs with the EMT Government team and in Quarterly CWBI Sharing Sessions. The IPRs shall be 1-hour in duration, and during the IPRs, the IWR Project Manager and COR will consult with the contractor to evaluate and prioritize specific EMT activities to be accomplished. Additional requests for updates and enhancements will be forwarded to the contractor by the IWR Project Manager for evaluation and addressed by the contractor during the bi-monthly IPRs through prioritization recommendations. The contractor shall prepare an agenda for each IPR to facilitate discussions. Additional reviews shall be conducted upon request from the IWR Project Manager or the contractor for new or major revision activities. Other ad hoc meetings, such as with the CWBI team, may be required on an as-needed basis. During those months, the ad hoc meetings take the place of the bi-monthly IPRs. For situational awareness, the contractor shall also attend Quarterly CWBI Sharing Sessions that are 1-hour in duration and hosted by the CWBI Program Office. These sessions cover topics specific to CWBI regarding Management, Data, Technical, Cybersecurity and Operational updates.
4.3.5 Task 5. Documentation: The contractor shall update, create, revise and/or maintain:
· Project Management Tool User Guide
· Project Management Tool and Dashboard report data loading and format parameters and process.
· EMT System Data Management Manual
· EMT System Management Manual
· Dashboard User Guide
· Dashboard Technical documentation
· EMT for documentation for CWBI in DI2E (or current application used by CWBI)
· EMT ticketing information for CWBI in Jira
· Online help documents and pages
· Test plan documentation
· ASD STIG checklist review
4.3.6 Optional Task 1. EMT Modernization Phase 2: Modernize Project Management Tool – Modernize the PM Tool, both reporting and project management plan functionality, to make it a standalone microservice taking advantage of new cloud native tools available to the CWBI cloud. This will require data availability through a REST API service. This task will include project management, new system diagrams, design mockups, new containerization, programming, quality assurance, and documentation.
4.3.7 Optional Task 2. Enhance CWBI Data Integration: Update CWBI data integration to include linking directly to CWBI data and reporting where allowed. This task may require additional data views in the database and updating of the monthly data update processes and, perhaps, underlying tables. This task includes designs illustrating any changes to data usage and how database table, view and query structure will change. It also includes project management, programming, quality assurance, and documentation.
4.3.8 Optional Task 3. EMT Branding and Layout – The contractor shall update the look-and-feel of the EMT to new USACE branding or other concepts. This task includes creation of design mockups, project management, programming, quality assurance, and documentation.
4.3.9 Optional Task 4. Refine Functionality for second Engineer Reporting Organization Code (EROC)’s use of the EMT: The previous EMT contract included a task to expand the EMT for use by a second USACE EROC (HQUSACE Planning and Policy Division). The contractor shall assist with adding parameters and reviewing current parameters for the additional EROC, ensuring data and reporting provide expected outputs. The contractor shall assist with processing monthly data updates and associated reports. The contractor shall maintain Dashboard functionality for the additional EROC.
4.3.10 Optional Task 5. Mandatory USACE Software Updates: The contractor shall perform the required coding changes due to USACE changes to application versions that impact application design or functionality. The Government team shall acquire required licenses if applicable.
4.4 Option Year 3 EMT Operations and Maintenance Task Areas
The activities within this task area will be evaluated and prioritized by the IWR Project Manager and contracting officer representative (COR). Activities will reflect program requirements and resolution of user issues. The testing of all database and interface modifications will be performed on government furnished equipment (GFE). This requirement is designed to provide service for 12 months from the date of award.
4.4.1 Task 1. Routine Maintenance: The contractor shall provide regular maintenance to ensure the EMT operates on a continuous basis to include:
| • | Posting of revised web pages and related files after local revision and testing. Typical tasks include: |
| o | Maintaining ColdFusion Docker container image with web application |
| o | Deploying container locally in Docker and testing deployment locally prior to any push to AWS ECS |
| o | Deploying container to AWS ECS test environment and subsequent Quality Assurance (QA) |
| o | Deploying container to AWS ECS production environment and subsequent QA |
| o | Responding to vulnerabilities reported via container and website scans |
| o | Revising Docker container implementation based on needed revisions to address vulnerabilities or changes to the ColdFusion container images |
| o | Maintaining underlying JavaScript packages |
| o | Maintaining needed secrets for container deployment |
| o | Responding to revisions to the AWS ECS deployment task definitions |
| o | Creating of, responding to, and verification of Jira tickets |
| • | Assistance with modification of database tables |
| • | Resolution of minor operating bug fixes |
| • | Minor report and functionality revisions |
| • | Revisions to the EMT Control Panel |
| • | QA related to posting of revised files |
| • | Review EMT Dashboard files and operability |
| • | Improvements to EMT Dashboard display and export layouts |
| • | Improvements to EMT Project Management Tool display and export layouts |
| • | New data code updates |
| • | Resolving EMT user issues and assistance with monitoring implementation of new user registration |
· Resolving or modifying functionality for CAC log-in and submitting tickets if needed related to Keycloak server issues
· Modifying IWR performance measure parameters tracked in the EMT
· Modifying required data format for display changes, such as revisions to EMT functionality when browser functionality changes, revisions to accommodate database or other platform updates or EMT CWBI configuration reviews
· Maintain required Qlik Sense or Power BI functionality for EMT Dashboard and Project Management Tool (if incorporated with previous Optional Task)
4.4.2 Task 2. EMT Modifications: The contractor shall perform modifications to the EMT to provide management with required information views for management decisions to include both the Project Management Tool and Dashboard. This shall include Project Management Tool modifications to current reports and modules and generation of new reports. Dashboard modifications shall include performance measure target parameter changes and displays. Dashboard profile views display modifications, both graph and data, and some new views within the current data sets. The specific reports are TBD but shall include approximately 10 modifications and the development of 5 new reports. EMT Modifications will include:
· Information views for management decisions for the Project Management Tool
· Modifications to current reports and modules
· Generation of new reports
· Information views for management decisions for the Dashboard
· Performance measure target parameter revisions
· Performance measure display revisions
· Profile view display modifications, both graph and data
· New profile views (graph and data) within the current data sets
4.4.3 Task 3. Data Updates: The contractor shall support the Government team to refresh EMT data and production modules. The contractor shall perform regular QA evaluations to ensure system integrity on a regular basis. The Project Management Tool is updated by the Government team mid-month and at the end of the month (approximately 15 files). The Dashboard is updated monthly using data updated for the Project Management Tool.
The Project Management Tool, Direct Funding Status by Army Management Structure Code (AMSCO), will be updated by the Government team within one business day of receiving notification of either data availability or data files while the complete Project Management Tool and Dashboard are updated within three business days.
The contractor shall make minor updates to underlying data structure, queries and views that are occasionally needed to support Project Management Tool and Dashboard reporting.
Contractor efforts related to this task shall include:
· Perform regular QA evaluations to ensure system integrity
· Provide QA review of the Project Management Tool mid-month and end of the month (within 1 day of data availability)
· Provide QA review of the Dashboard end of the month (within 1 day of data availability)
· Review Project Management Tool Direct Funding Status by Army Management Structure Code (AMSCO) report data within one working day of receiving notification of data availability
· Update queries and views that support Project Management Tool and Dashboard reporting
· Update underlying data structure that supports Project Management Tool and Dashboard reporting
· Assist the Government team with refreshing EMT data and production modules when needed.
4.4.4 Task 4. Bi-Monthly In-Progress Reviews (IPRs) and Quarterly CWBI Sharing Sessions: The contractor shall participate in bi-monthly IPRs with the EMT Government team and in Quarterly CWBI Sharing Sessions. The IPRs shall be 1-hour in duration, and during the IPRs, the IWR Project Manager and COR will consult with the contractor to evaluate and prioritize specific EMT activities to be accomplished. Additional requests for updates and enhancements will be forwarded to the contractor by the IWR Project Manager for evaluation and addressed by the contractor during the bi-monthly IPRs through prioritization recommendations. The contractor shall prepare an agenda for each IPR to facilitate discussions. Additional reviews shall be conducted upon request from the IWR Project Manager or the contractor for new or major revision activities. Other ad hoc meetings, such as with the CWBI team, may be required on an as-needed basis. During those months, the ad hoc meetings take the place of the bi-monthly IPRs. For situational awareness, the contractor shall also attend Quarterly CWBI Sharing Sessions that are 1-hour in duration and hosted by the CWBI Program Office. These sessions cover topics specific to CWBI regarding Management, Data, Technical, Cybersecurity and Operational updates.
4.4.5 Task 5. Documentation: The contractor shall update, create, revise and/or maintain:
· Project Management Tool User Guide
· Project Management Tool and Dashboard report data loading and format parameters and process.
· EMT System Data Management Manual
· EMT System Management Manual
· Dashboard User Guide
· Dashboard Technical documentation
· EMT for documentation for CWBI in DI2E (or current application used by CWBI)
· EMT ticketing information for CWBI in Jira
· Online help documents and pages
· Test plan documentation
· ASD STIG checklist review
4.4.6 Optional Task 1. Enhance CWBI Data Integration: Update CWBI data integration to include linking directly to CWBI data and reporting where allowed. This task may require additional data views in the database and updating of the monthly data update processes and, perhaps, underlying tables. This task includes designs illustrating any changes to data usage and how database table, view and query structure will change. It also includes project management, programming, quality assurance, and documentation.
4.4.7 Optional Task 2. Refine Functionality for second Engineer Reporting Organization Code (EROC)’s use of the EMT: The previous EMT contract included a task to expand the EMT for use by a second USACE EROC (HQUSACE Planning and Policy Division). The contractor shall assist with adding parameters and reviewing current parameters for the additional EROC, ensuring data and reporting provide expected outputs. The contractor shall assist with processing monthly data updates and associated reports. The contractor shall maintain Dashboard functionality for the additional EROC.
4.4.8 Optional Task 3. Mandatory USACE Software Updates: The contractor shall perform the required coding changes due to USACE changes to application versions that impact application design or functionality. The Government team shall acquire required licenses if applicable.
4.5 Option Year 4 EMT Operations and Maintenance Task Areas
The activities within this task area will be evaluated and prioritized by the IWR Project Manager and contracting officer representative (COR). Activities will reflect program requirements and resolution of user issues. The testing of all database and interface modifications will be performed on government furnished equipment (GFE). This requirement is designed to provide service for 12 months from the date of award.
4.5.1 Task 1. Routine Maintenance: The contractor shall provide regular maintenance to ensure the EMT operates on a continuous basis to include:
| • | Posting of revised web pages and related files after local revision and testing. Typical tasks include: |
| o | Maintaining ColdFusion Docker container image with web application |
| o | Deploying container locally in Docker and testing deployment locally prior to any push to AWS ECS |
| o | Deploying container to AWS ECS test environment and subsequent Quality Assurance (QA) |
| o | Deploying container to AWS ECS production environment and subsequent QA |
| o | Responding to vulnerabilities reported via container and website scans |
| o | Revising Docker container implementation based on needed revisions to address vulnerabilities or changes to the ColdFusion container images |
| o | Maintaining underlying JavaScript packages |
| o | Maintaining needed secrets for container deployment |
| o | Responding to revisions to the AWS ECS deployment task definitions |
| o | Creating of, responding to, and verification of Jira tickets |
| • | Assistance with modification of database tables |
| • | Resolution of minor operating bug fixes |
| • | Minor report and functionality revisions |
| • | Revisions to the EMT Control Panel |
| • | QA related to posting of revised files |
| • | Review EMT Dashboard files and operability |
| • | Improvements to EMT Dashboard display and export layouts |
| • | Improvements to EMT Project Management Tool display and export layouts |
| • | New data code updates |
| • | Resolving EMT user issues and assistance with monitoring implementation of new user registration |
· Resolving or modifying functionality for CAC log-in and submitting tickets if needed related to Keycloak server issues
· Modifying IWR performance measure parameters tracked in the EMT
· Modifying required data format for display changes, such as revisions to EMT functionality when browser functionality changes, revisions to accommodate database or other platform updates or EMT CWBI configuration reviews
· Maintain required Qlik Sense or Power BI functionality for EMT Dashboard and Project Management Tool (if incorporated with previous Optional Task)
4.5.2 Task 2. EMT Modifications: The contractor shall perform modifications to the EMT to provide management with required information views for management decisions to include both the Project Management Tool and Dashboard. This shall include Project Management Tool modifications to current reports and modules and generation of new reports. Dashboard modifications shall include performance measure target parameter changes and displays. Dashboard profile views display modifications, both graph and data, and some new views within the current data sets. The specific reports are TBD but shall include approximately 10 modifications and the development of 5 new reports. EMT Modifications will include:
· Information views for management decisions for the Project Management Tool
· Modifications to current reports and modules
· Generation of new reports
· Information views for management decisions for the Dashboard
· Performance measure target parameter revisions
· Performance measure display revisions
· Profile view display modifications, both graph and data
· New profile views (graph and data) within the current data sets
4.5.3 Task 3. Data Updates: The contractor shall support the Government team to refresh EMT data and production modules. The contractor shall perform regular QA evaluations to ensure system integrity on a regular basis. The Project Management Tool is updated by the Government team mid-month and at the end of the month (approximately 15 files). The Dashboard is updated monthly using data updated for the Project Management Tool.
The Project Management Tool, Direct Funding Status by Army Management Structure Code (AMSCO), will be updated by the Government team within one business day of receiving notification of either data availability or data files while the complete Project Management Tool and Dashboard are updated within three business days.
The contractor shall make minor updates to underlying data structure, queries and views that are occasionally needed to support Project Management Tool and Dashboard reporting.
Contractor efforts related to this task shall include:
· Perform regular QA evaluations to ensure system integrity
· Provide QA review of the Project Management Tool mid-month and end of the month (within 1 day of data availability)
· Provide QA review of the Dashboard end of the month (within 1 day of data availability)
· Review Project Management Tool Direct Funding Status by Army Management Structure Code (AMSCO) report data within one working day of receiving notification of data availability
· Update queries and views that support Project Management Tool and Dashboard reporting
· Update underlying data structure that supports Project Management Tool and Dashboard reporting
· Assist the Government team with refreshing EMT data and production modules when needed.
4.5.4 Task 4. Bi-Monthly In-Progress Reviews (IPRs) and Quarterly CWBI Sharing Sessions: The contractor shall participate in bi-monthly IPRs with the EMT Government team and in Quarterly CWBI Sharing Sessions. The IPRs shall be 1-hour in duration, and during the IPRs, the IWR Project Manager and COR will consult with the contractor to evaluate and prioritize specific EMT activities to be accomplished. Additional requests for updates and enhancements will be forwarded to the contractor by the IWR Project Manager for evaluation and addressed by the contractor during the bi-monthly IPRs through prioritization recommendations. The contractor shall prepare an agenda for each IPR to facilitate discussions. Additional reviews shall be conducted upon request from the IWR Project Manager or the contractor for new or major revision activities. Other ad hoc meetings, such as with the CWBI team, may be required on an as-needed basis. During those months, the ad hoc meetings take the place of the bi-monthly IPRs. For situational awareness, the contractor shall also attend Quarterly CWBI Sharing Sessions that are 1-hour in duration and hosted by the CWBI Program Office. These sessions cover topics specific to CWBI regarding Management, Data, Technical, Cybersecurity and Operational updates.
4.5.5 Task 5. Documentation: The contractor shall update, create, revise and/or maintain:
· Project Management Tool User Guide
· Project Management Tool and Dashboard report data loading and format parameters and process.
· EMT System Data Management Manual
· EMT System Management Manual
· Dashboard User Guide
· Dashboard Technical documentation
· EMT for documentation for CWBI in DI2E (or current application used by CWBI)
· EMT ticketing information for CWBI in Jira
· Online help documents and pages
· Test plan documentation
· ASD STIG checklist review
4.5.6 Optional Task 1. Enhance CWBI Data Integration: Update CWBI data integration to include linking directly to CWBI data and reporting where allowed. This task may require additional data views in the database and updating of the monthly data update processes and, perhaps, underlying tables. This task includes designs illustrating any changes to data usage and how database table, view and query structure will change. It also includes project management, programming, quality assurance, and documentation.
4.5.7 Optional Task 2. EMT Branding and Layout – The contractor shall update the look-and-feel of the EMT to new USACE branding or other concepts. This task includes creation of design mockups, project management, programming, quality assurance, and documentation.
4.5.8 Optional Task 3. Refine Functionality for second Engineer Reporting Organization Code (EROC)’s use of the EMT: The previous EMT contract included a task to expand the EMT for use by a second USACE EROC (HQUSACE Planning and Policy Division). The contractor shall assist with adding parameters and reviewing current parameters for the additional EROC, ensuring data and reporting provide expected outputs. The contractor shall assist with processing monthly data updates and associated reports. The contractor shall maintain Dashboard functionality for the additional EROC.
4.5.9 Optional Task 4. Mandatory USACE Software Updates: The contractor shall perform the required coding changes due to USACE changes to application versions that impact application design or functionality. The Government team shall acquire required licenses if applicable.
5. DELIVERABLES AND DELIVERY SCHEDULE
The table below identifies a set of deliverables that are required under this contract.
| Deliverable |
| Schedule |
| Task 1 (Base Year and All Option Years): Regular Maintenance tasks performed and/or user issues resolved |
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 .