Remaining Items – Technical Assistance and Coordination Outcomes Database

PERFORMANCE WORK STATEMENT (PWS)

BACKGROUND

The three programs within the existing Remaining Items (RI) Technical Assistance and Coordination Outcomes (TACO) database (RI-TACOd) are the National Flood Risk Management Program (NFRMP), Floodplain Management Services (FPMS), and the Planning Assistance to States (PAS) programs. The RI-TACOd was developed in 2022 and directly supports these three programs. The tool serves as the primary mechanism to gather and record project/study proposals for the NFRMP, FPMS, and PAS programs. This includes collecting proposals, ranking/prioritizing for eligibility, selecting for funding, tracking and reporting progress, and project closeout. The database resides within the Amazon Web Services (AWS) GOV cloud, which is managed by USACE’s Civil Works Business Intelligence (CWBI) program. RI-TACOd uses AWS cloud-native tools and open-source technical solutions. The AWS tools and scripts provide users with the means to submit their information, and program managers with the ability to manage and evaluate the process throughout its lifecycle. With RI-TACOd already deployed, USACE has identified operation and maintenance (O&M) tasks that are necessary for the database to continue to thrive, as well as new development tasks to help advance the tool to its next phase of existence.

SCOPE

This task order is designed to provide Contractor support to the Government for maintenance and modernization of RI-TACOd. Activities within major task areas will be evaluated and prioritized by the NFRMP/FPMS/PAS program managers (referenced as the Project Delivery Team [PDT] within this PWS) in consultation with the Contractor. Activities will reflect program requirements, user issues, and available resource levels. Several major task areas are to be managed through this delivery order. The task areas are described in Section 4.

A description of general tasks includes the following:

· General database development, assistance, and maintenance for DynamoDB and/or PostgreSQL databases.

· Make changes to database schema as needed to match any changes to the fields (name changes or additions).

· Keep changelog of fields that renamed or added over time.

· General assistance, and maintenance with web-based data entry interfaces and report generation. The current interface uses ReactJS.

· General assistance in interfacing with customers and ensuring the Data Entry and Reporting system remains operational.

· Data must be made easily accessible to USACE for use in reporting tools such as Power BI, A Representational State Transfer (REST) web service should be developed or a direct connection to the data accessible in Power BI should be made available. Full instructions should be provided for end users to create a connection. General assistance with development of data services to ensure program data can be used within existing USACE tools (ex. Microsoft PowerBI).

· Develop a REST web service endpoint that provides geographic data in a GeoJSON format for use in ArcGIS Portal web maps.

· General assistance to program managers in multiple business areas; this may include compiling reports for the managers, attending meetings, and presenting at meetings.

· Delivering training to users, database administrators, program managers, and others on how to enter data and pull reports once the new tool is operational.

· Maintaining and enhancing system documentation.

· Coordinate with CWBI PMO to maintain cybersecurity compliance, risk management framework documentation, and remediating vulnerabilities.

USACE access approvals and associated paperwork must be completed by Contractor personnel within 10-business days from notice to proceed and/or within 10 business days of notification and instructions from the Government. As new staff join the team the development of new AWS capability to support RI-TACOd will be performed using Contractor assets. More specifically, the Contractor will utilize the GovDEV environment for development of code. Any code or application passed to the Government will be hosted on the test/demonstration server for USACE Program Manger review and approval prior to being deployed by USACE resources with virtual technical assistance of deploying the components from the Contractor. Ideally the Contractor will use continuous integration / continuous delivery pipeline with full infrastructure as code model to allow frequent automated deployments using Agile processes. The Government will host the testing and production cloud-based servers on the CWBI cloud environment. The Contractor will provide draft deliverables to the Government at the prescribed milestones and be available to the Government for any technical assistance needed to complete the loading of code in the test and production environments. All code and deliverables developed are the property of USACE. All code must be maintained in CWBI's GitHub repository to ensure it can be scanned by CWBI's Information System Security Office. This team would also be responsible for responding to any findings from those scans.

The Contractor shall provide appropriate oversight and Project Management for every task in this PWS to ensure consistent oversight and coordination. Activities will reflect program requirements, user issues, and available resource levels. For the duration of this contract every month and when a need arises, the PDT in consultation with the Contractor, will evaluate and prioritize specific activities to be accomplished within each of the major task areas. Additional requests for updates and enhancements will be provided to the Contractor from the USACE Program Managers (PgMs)/Contracting Office Representative (COR) (both will be included on each request for situational awareness). These new requests will be addressed by the Contractor in the normally scheduled meetings or as necessary.

The Contractor will work with the PDT to ensure technical accuracy, clarity and appropriateness of key software and documentations while balancing project tasks, deadlines, and on-time deliverables.

The Contractor’s personnel must demonstrate the capability and appropriate experience to successfully perform a project of this scope and magnitude. The Contractor’s personnel should be familiar with the USACE Civil Works (CW) Program, and knowledge of the CW NFRMP, FPMS, and PAS missions or similar missions is beneficial but not required. The Contractor shall have extensive technical knowledge of programming in database and web-based data entry and reporting solutions to make the necessary revisions to the relevant systems. In addition to these general skills and experience, the Contractor should also possess the following:

· Knowledge and experience in developing, maintaining and documenting changes to a relational database operated from a Government data center on Amazon Web Services (AWS cloud).

· Knowledge and experience of data entry and options to increase automation and efficiency.

· Knowledge and experience with documenting data systems and processes and creating reports for increased efficiency.

· Knowledge and experience in optimizing the performance of existing relational database applications, including procedures, functions, etc.

· Knowledge and experience with creating Representational State Transfer (RESTful) services utilizing common data dissemination formats.

· Knowledge and experience with making websites 508 compliant.

· Knowledge of database design with respect to user experience to enable a design that maximizes efficient data entry and minimizes user data entry errors.

· Maintain a clean, intuitive, and logical layout that is easy for users to navigate.

· Use a consistent and accessible design for all text, colors, and interactive elements.

· Knowledge and experience preparing geospatial services.

· Knowledge and experience delivering solutions that align with Agile methodology.

As the Contractor updates their staffing plan an update will be provided to the PDT to ensure the requirements of this PWS are continuing to be met. An updated QA/QC plan with the updated staffing plan may be requested.

In compliance with DoDI 8500.01 (2014) section 3.c.2, DoDI 8510.01 (2016) section 3.d, and USACE ER 25-1-112 (2014) section 7.1.3; all information systems (IS) and platform information technology (PIT) systems developed and/or supported under this contract shall comply with all Department of War (DoW), DISA, Army, and USACE cybersecurity and information technology (IT) requirements. This includes IS/PIT compliance with DISA security technical implementation guides (STIG) and being categorized IAW CNSSI 1253 using security controls developed IAW the risk management framework (NIST SP 800-53). STIG compliance shall include but is not limited to most current version of the DISA published Application Security and Development STIG and the internet access point (IAP) demilitarized zone (DMZ) STIG. Further, the Contractor shall comply with DFARS clause 252.204-7012 (Safeguarding Covered Defense Information and Cyber Incident Reporting) and implement NIST SP 800-171 requirements to protect covered defense information / controlled unclassified information.

General REQUIREMENTs The following sub-sections provide details of various general requirements for this effort.

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 assist 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.

Place of Performance All work will be performed at the Contractor’s site.

Period of Performance Comment by Kaplan, David A CIV USARMY CEHEC (USA): We need to specify for the modernization tasks if they will be 12 month or other. We do not have to have every task 12 months. If development needs done in 6, it should be 6; if it needs be 18 it can be 18. O&M is fine with 12 and 12. Development needs a quick thought here.

The period of performance includes base tasks with a 12-month period of performance, and several option tasks with a 12-month period of performance from date of award of the option.

Materials All materials, minus expendable supplies, purchased by the Contractor with funds from this contract and used under this contract, become, and remain the property of the Government.

All developed code will become property of the Government.

Travel

The Contractor shall attend a post-award meeting as detailed in Task 1A. The COR will coordinate with the Contractor to schedule the orientation The contractor shall provide services necessary to plan and schedule travel and travel will be reimbursed at actual cost in accordance with the Joint Travel Regulation and the limitations set forth in Revolutionary Federal Acquisition Regulation Overhaul (RFO FAR) 31.205-46, Travel Costs. The appropriate Government Official, Quality Assurance Personnel or Contracting Officer will approve travel. All invoices for travel shall be accompanied by supporting receipts. The Contractor shall not assess profit or fee against other direct costs and/or travel. Other than post-award meeting, there is no travel required for this contract. The Contractor shall be equipped to communicate and collaborate virtually with strong facilitation skills and necessary support tools.

Data Storage, Rights, and Ownership The Contractor shall physically maintain all data solely on equipment located within the legal jurisdiction of the United States IAW DFARS 239.7602-2(b). All data, including but not limited to documents, administrative data, support data, and billing data, transmitted via the system or maintained in the system must reside in data processing and storage equipment located in the United States or in data processing and storage equipment of which the operation and maintenance are subject only to the laws of the United States. Data transmitted must only be subject to disclosure pursuant to U.S. Federal law and not the laws of any other jurisdiction or foreign nation. All DoW information/data placed or created by DoW users in a Cloud Service Provider’s (CSP) Cloud Service Offering (CSO) is owned by the DoW, the Mission Owner, and/or their Information Owner. The CSP has no rights to the DoW’s information/data. For more information on data storage, data rights, and data ownership requirements refer to Section 5.2, Legal Considerations, in the DoW Cloud Computing Security Reference Guide (SRG).

The Government shall retain unlimited rights to all development and automation performed and all data, Infrastructure-as-Code (IaC) or Configuration as Code (CaC) or processes created under this contract. This would not include code, processes, or automation that USACE might subscribe to that are commercially available under Commercial Use Rights and/or Government Purpose Rights.

The Government shall retain unlimited rights of all user data/information/knowledge provided to, created/developed in, loaded/transitioned to, or hosted in/by the Contractor, CSP, tenant, multiple CSP, multiple tenants, CSO, vendor IT infrastructure, hosting environment, system(s). This includes rights to logs, scans, analytics, and other data, conducted by the Contractor, CSP, or tenant, on their IT infrastructure, hosting environment, system(s), or prototype process. The Government retains the right to request full copies of this data at any time.

Quality AssuranCe, Reviews and acceptance of work Completion of quality reviews by Contractor and review/approval of products by the PDT is critical to ensuring usable products are delivered and paid for. The requirements below are outlined to provide guidelines for clear communication, to ensure quality reviews are completed to ensure work can be accepted.

Quality Control (QC) The Contractor shall develop a quality control plan (QCP) and implement a quality control program to satisfy the specific requirements of this contract. An optimal QCP shall identify potential problem areas and evolve over the life of the contract. The Contractor shall provide the QCP to the KO and COR for approval no later than 30 calendar days after contract award. The Contractor shall update the QCP as required, either due to staff changes or as requested by the COR and provide copies to the KO and COR for approval.

Quality Assurance (QA)

The Government will monitor the Contractor's performance under this contract in accordance with the Government’s quality assurance surveillance plan (QASP). The QASP defines how the performance standards will be applied, the frequency of surveillance, and the acceptable quality levels (performance thresholds). The Government has the right to conduct inspections and performance evaluation at any time and at any place where contract performance occurs. If any aspect of the performance is not in conformance with the requirements of this contract, the Government has the right to issue to the Contractor a Contract Discrepancy Report (CDR). The Contractor shall explain in writing why performance was not in conformance with the requirements of the contract, how performance will be returned to conformance, and how recurrence of the problem will be prevented in the future. The Contractor shall complete and return the CDR to the Contracting Officer and COR within five workdays after receipt of the CDR. The Contractor shall maintain copies of all inspection and evaluation reports. Government review of contractor deliverables will be guided by the QASP. The QASP will be based on the requirements and acceptance criteria in the PWS and aligned with the design, implementation and testing plans in coordination with the contractor.

Quality Measures The measures below are included to ensure quality occurs throughout the contract delivery:

a. At each development task kick-off call the PWS will be reviewed and if needed, refined and further detailed between USACE and the Contractor to ensure the requirements are understood by the Contractor and that they will deliver what the PDT needs in terms of database functionality. During this review a deliverable schedule will be drafted.

b. Contractor shall ensure regression testing and internal quality reviews are complete prior to release of upgrades into USACE test environment. All workflow updates will be established in the USACE test environment (after Dev environment). and receive written approval from USACE PgM before changes are implemented in the production site. All PDT comments must be addressed and written confirmation of approval from the PgM or COR to move to production should be obtained prior to launch in production.

c. Deliver a monthly status report and invoice to the USACE COR. Monthly written status reports shall be submitted to the COR and PDT no later than the tenth day of the month following the subject month and accompany the monthly invoice. At a minimum, the status report should highlight work accomplished in the past month and what is planned for the next month as defined by the PWS tasks, to include any challenges and/or barriers in need of Government intervention. Status reports shall include a list of all team members actively supporting the contract tasks. Status reports should include analysis of help desk response and ticket resolution to demonstrate compliance with the PWS requirements including time from receipt to resolution of help desk tickets. Work completed can include a percentage of a task completed (if not fully complete within that billing period), as well as documentation of any deliverables accepted by the government. This document’s contents should be discussed during the bi-weekly status meeting following submission.

d. Provide a monthly Root Cause Analysis (RCA) report for persistent issues or issues affecting multiple modules. The RCA will help in identifying mission/customer impact. Conducting major post-mortem reviews can help the RI-TACOd to minimize or eliminate recurrence as well as identify some of the technology, expertise, or process-related inefficiencies. The RCA shall include the following:

· Business/Customer Impact

· Related Incidents

· Information collected from monitoring tools

· An action plan to resolve the root-cause of the outage

· Clearly defined problem scope/boundaries

· A review of historical data, trends, and sequences of events

· Identification of common symptoms

· Analysis of underlying processes, tools, and environmental factors

· Identification of potential root causes

· What went right?

· What went wrong?

· What could be done better?

· How to prevent problem reoccurrence

· Lessons learned

Compliant with applicable standards (All Statements)

Deliverables completed in accordance with Schedule (All statements) 95% of the time

Early identification of problems and/or corrective actions. Report to government within 2 days of discovery.

(All statements) 90% of the time

Operational/Effective (All statements)

PERFORMANCE requirements (tasks) While forecasted features and requirements are stated below, consistent with Agile and Sprint-based development, the features and requirements are subject to change based on Sprint planning during the period of the contract. The Contractor shall evolve solution capabilities to support Government prioritized features.

Task 1: Communications Task 1A: Communication with USACE Project Delivery Team The Contractor shall engage in Regular Communication with the PDT

a. The Contractor shall attend a one-day post-award meeting at a time that is agreeable by all parties in the Washington, D.C. commuting area or Kansas City community area or via webinar. It is assumed up to four (4) of the contractor’s staff may attend. The COR will coordinate with the Contractor to schedule the Post -Award Meeting within 60 days of NTP. Contractor shall provide agenda no less than one week prior to scheduled meeting. Contractor will provide meeting summary and due-outs within three business days of completed meeting.

b. The Contractor shall participate in one hour in-progress reviews (IPRs), via web-meeting utilizing a system compatible with USACE technology, on a bi-weekly basis to review current work, schedules, and prioritize tasks with the COR, and PDT. Meetings will include review of items submitted via the suggestion box to assist in cross-program prioritization of tasks. Contractor will provide meeting agenda and topics to include a list of all items currently being worked and their status at least 24 hours in advance of the scheduled meeting. The Contractor shall provide meeting notes no later than two (2) business days following each bi-weekly meeting that includes a list of attendees, meeting details, action items, and next steps.

c. The Contractor shall participate in one-hour check-ins with each program lead and PDT as needed (no more three a month) to discuss program needs or issues in detail, prioritize tasks, and determine any training or user guide update needs for the field.

d. The Contractor will coordinate with the appropriate program lead to schedule a one-hour task ‘kick-off’ call for each development task. Coordination with PgM on scheduling the kick-off call shall occur within 20 days of NTP. Contract will provide PgM with a draft deliverable schedule within 10 days following the task kick-off call. The deliverable schedule will be updated as needed in coordination with the PgM. Reference 3.7.3 (a) for additional details.

e. The Contractor shall meet with PDTs to review draft deliverables, view errors, or resolve other issues expediently, as needed.

f. The Contractor shall support up to four (4) virtual user training meetings a year (including reviewing PgM slides, providing screenshots and ensuring updated user guides are posted).

Task 1B: Documentation of Programs and Processes The Contractor shall maintain, validate, and/or upgrade existing documentation and create new documentation in conjunction with the PDT describing project management, reporting programming and processes, business rules, etc. for use in describing RI-TACOd. Examples of documentation needed are:

1. Project Management Plan

2. Maintained Quality Control Strategy (see 3.7.1 for initial deliverable details)

3. Updated User guides and training materials

4. Database Entity Relationship Diagram (ERD) (government furnished)

5. Design Document (government furnished)

6. O&M Plan

A Project Management Plan must be delivered within 45 days of contract award. The remaining documents must be continuously maintained, with each change documented in the change log. User guides should be reviewed and updated, at minimum, once a quarter to verify the manuals are aligned with the online system and that each business function includes the same components (workflow diagrams, input forms, and reports). Each of the documents described should be stored dynamically on the CWBI Hub within module documents and provided to the module team in two formats: 1) a PDF that can be passed to all involved as it is a universally readable format, and 2) the original editable format. The editable format will differ for each document, depending on its primary use (i.e., models will need to be done in a modeling software like Día, Vizio, etc. whereas a governance roadmap may be completed in Word).

Task 1C: Technical Correspondence, Ticket Tracking and Help Desk PDT comments, change requests, and O&M issues will be delivered to the Contractor via email, or in standard MS Office file type (xlsx, docx, etc.) or other file type as agreed. The Contractor shall use a Jira a ticket record creation and tracking system to record each item as a ticket and track its progress to completion. The Contractor Jira shall always be accessible to the PDT. Jira shall be maintained throughout the contract to ensure continuous accessibility. If the Contractor does not have a ticket system available, then the CWBI Jira tool can be used as an alternative.

The Contractor shall provide timely and responsive user assistance for all members of the USACE community relative to the RI-TACOd. Issues are reported either to PgMs or through the help desk email ri-tacod-help@usace.army.mil mailbox- contractor should establish a connection to this inbox in order to monitor incoming help desk tickets. All user assistance requests should be recorded in the ticket creation and tracking system to track completion and assignment. Each ticket should be responded to, at minimum, within 24 hours of receipt and recorded in the ticketing system. The Contractor shall be proactive in responding to users and provide daily status updates on the ticket if the ticket cannot be resolved within the first 24-hours of receipt.

Task 2: Module and Data Update Maintenance – O&M This task addresses general user interface and data management activities to maintain the RI-TACOd and modules in support of mission requirements of Civil Works Business Lines, CWBI Data Strategy, and DoW Data Strategy. Among other activities, this will include:

a. Refresh all production modules and perform regular quality assurance evaluations to ensure system integrity.

b. Maintain and provide minor enhancements to RI-TACOd as needed. Changes include edits to forms, establishing sub-pages within forms as needed to align new content with site formatting, and edits to existing documentation posted therein. Improve consistency of data formatting across all modules (i.e., any time financial information is entered or displayed, use $ symbol and ensure commas are included and use District 3-letter abbreviations rather than spelling out full District names in all cases). Improved left hand menu for consistency such as each programs circle either that programs designated color that is seen in the program module or the programs logo.

c. Provide general data maintenance, quality control and standardization. Review new software versions for improvements and determine impacts of potential software upgrades on system performance, e.g., AWS upgrades as required to maintain an Authority to Operate (ATO).

d. Ensure automatic pull, build, and data updates continue to occur from integrated AIS resources with no human interaction or manual publication necessary.

e. Analyze and provide documentation of existing AIS integration process, to include suggestions on increasing efficiency and clarity/simplicity.

f. Review metadata to ensure it remains up-to-date and accurate for use within the Civil Works Data Catalog.

g. Develop (within 45 days of NTP) and maintain a Data Management Plan and maintain compliance with an annual CWBI data checklist.

h. Maintain Confluence and RMF records to ensure CWBI ATO can be rapidly renewed.

i. Update user roles and permissions within each module to allow appropriate level of view, edit, review, deletion, and approval. This may require establishment of new roles and/or modification of permissions associated with existing roles.

j. Prepare data, form, and report updates based on requirements identified by the proponents and user groups of the business functions. During data entry period, this can include the addition of columns or rules to tables and the addition of fields to the database or web-based forms/reports.

Task 3: Modernize FPMS, PAS, and NFRMP Module: Overarching Enhancements Options- DEVELOPMENT In coordination with PDT guidance, the Contractor shall work to enhance and improve site navigation and functionally across all forms within the modules to allow for ease and shared understanding of site navigation. Enhancements to include, but not limited to:

Task 3A: Module enhancements for improved user navigation (Option)

a. Work list functionality/organization improvements- improve work list for improved user navigation (i.e. ability to organize work lists by tasks vs. project)

b. Improved data exportability such as ability to complete word/phase searches within each module and export all relevant fields into format such as Excel. Ability for districts to export financial data for all of their approved projects into Excel. Data exportability at all levels of the organization (i.e. make it easier for Districts/Divisions to export and/or view data relevant to their AOR).

Task 3B: Dashboard Enhancements (Option) Improve upon any existing dashboard features to highlight criteria of interest in each module based on PgM input.

Task 3C: Bulk Editing (Option) Establish or improve upon any existing Bulk Editing features. Bulk editing includes screens which provide the ability for PgMs to enter data for multiple records from one screen (such as quarterly approved amount, funding distribution, approval of records, etc.). The specific requirements and needs will vary for each program, but the primary intent is to streamline data that affects multiple records at the same time, so PgMs do not need to review each record, navigate to the appropriate screen, enter the data, save, and return to the menu multiple times in one session for similar actions.

Task 3D: Mail Service (Option) Develop methods for initiating mail service such as AWS SMS to provide notification of defined activities to users with roles to review, approve and/or otherwise act in response to another users’ activity within the module. Users should have the ability to mute email notifications via the user interface.

Task 4: Modernize Floodplain Management Services (FPMS) Modules- DEVELOPMENT Task 4A: FPMS Workflow Modifications and Enhancements (Option) The Contractor shall incorporate updates to improve the workflow for records in the FPMS modules to allow for smoother and more consistent development and processing of records to include, but not limited to:

a. Review roles involved in FPMS module and make changes as needed to streamline processes and minimize the potential for users to perform tasks not intended for them.

b. Implement new functionality to align with changes in required levels of record review and approval.

c. Improve ease of returning records to previous levels for corrections/revisions.

d. Add ability for Districts/Divisions to respond to SME review comments directly.

e. Improve ability of HQ FPMS PgM users to approve funding amounts for individual projects (all CCS codes), including approving annual amount and monthly breakdown of funds for distribution, as well as track distribution over the year and make changes to planned allocations if needed.

f. Enable clear export of SME required review list via template Excel spreadsheet for FPMS interagency proposals and enhance process for import of completed SME reviews from Excel spreadsheet.

g. Develop and implement new processes to move records between the FPMS interagency program and the FPMS base program as needed.

h. Support changes to project close-out for ALL FPMS projects to ensure appropriate information is imported into Silver Jackets module for projects that self-identify as being executed in coordination with a Silver Jackets team.

i. Minimize or eliminate the ability of users not in possession (during a workflow) of an individual record to make edits.

j. Facilitate or streamline moving of imported complete projects to ‘closed’ status within RI-TACOd to retain project information and allow access/viewability.

Task 4B: Improve User Experience Within FPMS Module (Option) The Contractor shall complete enhancements to the current user experience to streamline use of the module, to include, but not limited to:

a. Improve ease of navigation for users within forms and minimize number of required clicks.

b. Ensure instructions for individual tasks and/or actions are clearly identified and easier to find/more prominently visible on the screen.

c. Improve clarity of process for closing out projects.

d. Ensure that it is visually clear what stage of the workflow process individual records are in and who/what level of the organization is responsible for required action at that stage.

e. Refine worklist to more clearly articulate required tasks for users, such as by changing the worklist to group records in the same task or otherwise better communicate the action needed from the user.

f. Incorporate rating criteria for MSC and HQ-level proposal raters into the form in some manner so it is readily available as reviewers are evaluating and rating proposals.

Task 4C: FPMS Change Management (Option) The Contractor shall refine change-management processes in the FPMS modules to improve clarity as changes to existing records are made, reviewed, and approved, while maintaining a history of changes. Change management process could include, but is not limited to:

a. Ensure authors of changes are clear.

b. Add the ability to write justification for changes to milestones or budget

c. Enhance Change Management Logging: Ensure author and editor of records are captured within the database, along with the date of the change and content of edit, if applicable.

d. If records are moved from FPMS Interagency to FPMS Base Program or vice versa, maintain a record of any data that was included in the original record that would not be included, due to differences in forms between the two types of records, in the new record.

Task 4D: FPMS Data Export and Reporting Abilities (Option) The Contractor shall enhance ability for various export functions including but not limited to:

a. Create or enhance functionality for users at any level to export spreadsheet reports specific to their level (i.e., a District user could export all information relevant to that District, an MSC user could export all relevant from all Districts within the MSC, and HQ could export data from all Districts) for selected fields.

b. Create or refine a set of standard reports based on feedback from the FPMS PgM about what data is most regularly needed.

c. Enable filtering, within the RI-TACOd FPMS module, based on various data input fields.

d. Incorporate financial and scheduling data from USACE AIS outside of CWBI into forms and reports to complement and inform the dataset originating within RI-TACOd. This will require database, form, and report updates.

e. Improve quality/readability of exportable pdfs of records. Evaluate options to improve export processes, such as allowing batch exports of pdf files if feasible.

f. Make adjustments to exportable posters (pptx files) to enhance ability to pre-fill sections of the poster from specified text within the record.

g. For project records under FPMS Interagency or FPMS Base Program where the user selected a state/county/other boundary rather than important a specific latitude/longitude point for geospatial purposes, implement a method to associate a lat/long point (i.e., the centroid of the selected boundary) with the record for export purposes. This will enable easier geospatial mapping purposes outside of RI-TACOd.

Task 5: Modernize National Flood Risk Management Program (NFRMP) Module – DEVELOPMENT Task 5A: NFRMP Feature Enhancements (Option) The Contractor shall incorporate improvements to the NFRMP module to allow for enhanced program management and user experience to include, but not limited to:

a. Incorporate additional flexibility in Headquarters management such as ability to delete or archive records and document justification.

b. Enhance Change Management Logging: Ensure author and editor of records are captured within the database, along with the date of the change and content of edit, if applicable.

c. Complete form enhancements for ease of use and clarity, adding additional columns or text as directed by USACE PgM.

d. Enhance budget module to track all District & MSC budget change requests throughout the year, as well as amounts approved / denied by IWR/HQ per request. Include all requests / approvals / denials in budget report export.

Task 5B: NFRMP Data Dissemination and Reporting Abilities (Option) The Contractor shall enhance search and filter functions/defaults within NFRMP module and develop ability for various export functions including but not limited to:

a. Ensure all reports have export ability in standard formats such as Microsoft Excel, CSV, HTML, and PDF.

b. Improve the existing summary page export function for briefing and data calls (ex. Ppt) such as adding ability to pre-fill sections of the poster from specified text within the record.

c. Enhance budget dashboard and export report to show current and prior year budget requests and approved budgets; filterable by District / MSC, fiscal year, organizational code, and labor / travel.

d. Create report export in excel that includes raw data and processed pivot table to allow for filtering views. Modify existing budgeting and coordination records interfaces to allow for batch editing data or actions (such as approving multiple requests at once).

e. Enhance connection of FPMS/PAS closeout where SJ Team is identified for capturing NFRMP accomplishments.

f. Modify key word/phrase search & search results report export function so that any District or MSC user can search all approved coordination records, not just their own.

g. Enhance dashboard to show fields from records found with key word searches, with ability to further filter by fiscal year, district/MSC

h. Facilitate importing of Microsoft Access database entries into RI-TACOd NFRMP module in order to be able to access all past records so they are searchable, and can be exported from TACO (approximately 5 years of records)

TASK 6: MODERNIZE PLANNING ASSISTANCE TO STATES (pas) mODULE – DEVELOPMENT Task 6A: PAS New Projects in Scoping Status (Option) The Contractor shall modernize the workflow prior to PAS projects to include but not limited to:

a. Add a pre-step to the existing PAS workflow that would be called “Scoping”. Scoping would be for projects that are being developed but are not ready for review.

b. This form would need, but is not limited to, the following fields: draft project name, district POC, primary purpose, non-federal sponsor name, estimated total project cost, estimated total federal cost, whether the project planned to request an 8119 waiver and the estimated federal funding request date.

c. Once initiated the district should be able to edit any of these fields at any time.

d. Once the project was fully scoped it would go from the “Scoping” phase into the 8119 request phase that is the current first step in the workflow. Once it goes into this phase all data can still be edited.

e. If a scoping status project does not move forward it can be deleted by the district.

f. Add a report for scoping projects. The report would have one tab that would have rows for each project and one tab that would roll up the total federal cost by MSC and by month that funding was going to be requested.

Figure 1. Example format or combined "scoping" project repot.

Task 6B: HQ View PAS Projects All in One Place (Option) Contractor shall add an additional tab or view that is for HQ only that has all projects in it (scoping, active, and closed). HQ should be able to view, review and edit all projects within this tab.

Task 6C: Allow HQ to Bulk Push Ongoing Projects Back to Districts for Budget Updates (Option) Contractor shall enable the PAS module to include the ability for the PgM to enter a date when all projects in an approved status (that were not fully funded at that time) and approved/unfunded status to be pushed back to the districts worklist so that they could update their schedules and budgets. Once these projects are updated by districts, they would go through the MSC to HQ workflow for review.

Task 6D: Update PAS Project Poster (Option) Contractor shall update PAS project poster exports to a new format that is similar to the below example and should still be exported in a PowerPoint format. All fields should be filled from data within the RI-TACOd PAS project record, but all fields should still be editable. Pictures will be uploaded onto the power point slide once it is exported. Government will provide a PowerPoint template.

Figure 2. PAS Poster Export Example Task 6E: Fiscal Year PAS Report Export (Option) A federal fiscal year is October 1 – September 30. The Contractor shall develop reports that can export to Excel and include, but not limited to the following three tabs:

1) This tab will have roll up information that will be included in the PAS annual report.

a. Active Projects During FY – this will be all projects that started before the end of the FY (CW140) and didn’t end before the beginning of the FY (CW170).

b. Projects Initiated During the FY – This will be all projects with a CW140 milestone during the FY.

c. Breakdowns of number of projects that were active during the FY for any project question where the answers are multiple choice (ie primary purpose).

d. Breakdown of non-federal entities assisted. This should only be for projects active during FY. There should be a list of all nonfederal entities. Each nonfederal entity should have a number beside it that shows the number of projects they were listed on. So, if two different projects supported River City it would show River City 2.

2) Projects Completed in the FY: Projects with a CW170 milestone date during the FY (you can select the FY when exporting the report).

3) Projects Ongoing During the FY but not completed in the FY: Projects with a CW140 milestone before the end of the FY but with a CW170 milestone after the end of the FY. Projects in tab 2 should not also be included in tab 3.

Tabs 2 and 3 should have all data within each project record that meets that tab criteria, this should include latitude and longitude values broken out into different columns.

Task 6F: PAS Negotiations Updates and Reporting (Option)

a. Contractor shall update the PAS Negotiations Coordination page to include, but not limited to:

· Updates to forms for clarification per PgM guidance

· Ability to track if the coordination results in an outcome such as a Letter of Interest for a new PAS project, a new ‘other USACE project’, an effort with another federal agency, action by the state or local entity, etc.

· Addition of standard categories of coordination events (drop down option). Categories to be provided by PgM

· Ability to capture ‘Non-federal entity coordinated with’ as a field.

b. Contractor shall develop new PAS Negotiations Report to include but not limited to:

· Information from new fields in under a, budget information by quarter (requested amount, approved amount, and if distributed). Basic information such as district, total budget request, and other fields as identified by PgM.

optional Task 7: Module and Data Update Maintenance – O&M (1-year)

The Contractor provide 12 months of service encompassing, but not limited to:

· All communications and support identified in Task 1;

· All general O&M tasks as prescribed in Task 2;

· Any O&M tasks required to maintain operations of all datasets and functionalities incorporating O&M of any new deliverables accepted during a previous or current O&M period within this task order.

DELIVERABLES AND DELIVERY SCHEDULE

The Contractor shall provide reports and other print deliverables in publication quality format and provide web publishable versions of such deliverables. The table below identifies a set of deliverables that are required under this task order.

Deliverable Type Frequency and Quantity of Deliverables (including drafts)

‘kick-off’ call

4.1.2 Continuous maintenance and updates to:

· Updated User guides and training materials

· Maintained QCP

· Database Entity Relationship Diagram (ERD) (government furnished)

· Design Document (government furnished)

· O&M Plan

User guides - reviewed and updated, at minimum, once a quarter to verify the manuals are aligned with the online system and that each business function includes the same components (workflow diagrams, input forms, and reports).

All other documents must be continuously maintained

For O&M activities only, Contractor may invoice in equal increments, if invoicing monthly. For tasks with deliverables, the amount of work will vary month to month with task, invoices should only be based on the proportion of work completed within the invoicing period and cumulatively to the date of the invoice, i.e. 40% of the deliverable is complete, invoice should be approximately 40% of the price for that line item (task).

The Government has unlimited rights to all documents and materials produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the Contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

In compliance with Department of Defense Issuances (DoDI) 8500.01 (2014) section 3.c.2, DoDI 8510.01 (2016) section 3.d, and USACE ER 25-1-112 (2014) section 7.1.3; all information systems (IS) and platform information technology (PIT) systems developed and/or supported under this contract shall comply with all DoW, DISA, Army, and USACE cybersecurity and architectural requirements. This includes IS/PIT compliance with DISA Security Technical Implementation Guides (STIG) and being categorized IAW CNSSI 1253 using security controls developed in accordance with (IAW) the risk management framework (NIST SP 800-53). STIG compliance includes, but is not limited to most current version of the DISA published Application Security and Development STIG and the internet access point (IAP) demilitarized zone (DMZ)

STIG.

OVERNMENT FURNISHED PROPERTY (GFP)

GFP will be required. The Contractor shall be provided with laptops to access the USACE network and develop/test deliverables. These GFP will only be loaded with software approved by the USACE CIO/G-6 offices. The Contractor shall not use GFP for any work outside the scope of this PWS. The Contractor is responsible for all GFP during the performance of this PWS and upon termination the Contractor shall return all GFP to the Government.

This task order requires government laptop(s) to perform work. While the task order of performance is in effect, the contractor will maintain an inventory of all government laptops issued under the task order. Each inventory shall include the following information: laptop(s) identified by barcode(s), the task order number that the laptop is required to support, and the name of the contract staff member assigned to each laptop.

The inventory shall include the chain of custody for each laptop for the duration of the task order and shall be provided upon request by IWR Contracting Staff. Within 14 days of completion and acceptance of final services and/or deliverables under each task order, all GFE, including laptops, shall be returned to the government with notification to the IWR Contracts Program Team. Government laptops shall not be transferred to other contractor staff working on other task orders unless written permission is provided by the IWR Contracts Program Team or is specifically called for in the task order. The return of the GFE shall include coordination with the task order PM or COR.

If a CAC is required by contract personnel to perform work herein, it is incumbent on the contractor to monitor CAC reverification requirements and CAC expiration dates for all personnel. CACs are associated directly with this task order. It is the contractor’s responsibility to communicate with the PM/COR with adequate notice to complete reverification and re-issuance of each CAC to ensure personnel access as needed to perform the tasks required under this task order.

Government will furnish the following documents created for the RI-TAOCd for contractor reference and updates as needed:

· Database Entity Relationship Diagram (ERD)

· Design Document

· User Guides

· Any relational diagrams or documents General security requirements and guidance The security requirements described below apply to all…