B08.03 Questions and Answers for W912HQ25R0007 - VTN Content and Maintenance.docx

1. Is there any incumbent/recompete or this is a brand-new project? If yes, could you please provide us with their award number or even if the customer bought similar services in the past.

This work has been performed by Web and Writing Solutions Company previously under contract W912HQ22P0117.

2. Could you please confirm whether the work will be performed on-site or remotely? Can work be done from remote location other than Contractor Physical site?

The work can be performed at the Contractor’s physical site or remotely.

3. Is there a Government estimate or budget range for this requirement that can be shared?

This information will not be provided. Price is being competed for this requirement.

4. Are there any set-aside considerations for this opportunity?

This 100% small business set aside

5. Can USACE provide more detailed objectives or success metrics for the content development and website modernization project?

For Task 1 (Support for the development and update of the contents of VTN Fast Facts), the contractor shall develop clear, contextually appropriate content and narratives based on data, information, and guidance provided by the USACE project team. They will also be responsible for managing and enhancing user interface elements, including the development and maintenance of links, related components, and developing downloadable PDFs (Fast Facts) and spreadsheets.

As for Task 2 (Support for VTN website analytics, maintenance, improvements, and modernization efforts), the contractor shall support the project team by providing website analytics, including traffic metrics and user engagement insights, to inform ongoing content and design decisions. They are also expected to perform routine website maintenance and implement modernization efforts as directed, ensuring accuracy of information, resolution of critical errors, and continuous improvement of user interface elements.

Success metrics include content alignment (quality and accuracy of content/narratives developed), UI functionality uptime (all links and interface components remain operational and error free), and timely delivery (i.e., content and UI updates are completed within 21 calendar days of receiving source data/guidance, as well as providing website analytics once per quarter, and UI improvement requests completed within 14 calendar days)

6. Is this project limited to a specific USACE division or region, or does it include support for multiple offices/agencies?

This project is supporting work for a specific USACE component (USACE Institute for Water Resources) and contents are at the national level. This work includes information across the entire USACE enterprise.

7. Which CMS platform is currently used for the existing USACE website(s)? Are there any existing plans, wireframes, or technologies already in use that the contractor needs to be aware of?

This is proprietary information relating to the technical approach of the incumbent. Offerors should choose a CMS that is appropriate to achieve the objectives outlined in the PWS.

8. Are there any preferred or required technologies or tools (e.g., analytics platforms, frameworks, content creation tools) that vendors must use?

No preference, as long as it is supported by and meets the requirements of USACE and IWR.

9. Will the contractor have administrative access to the backend of the current website, or will updates be submitted through an intermediary?

The contractor will have direct access to change the contents of the website.

10. Will the client provide all raw data for narrative content, or are vendors expected to conduct independent research and data interpretation?

The USACE VTN Project Team will provide all raw data, which the narratives will depend.

11. Will the awarded vendor be responsible for ADA compliance and Section 508 accessibility in all digital content and documents?

Yes. As stated in the PWS, the awarded contractor will be responsible for meeting digital government website requirements, including ADA and Section 508.

12. How often will USACE expect new content to be created, updated, or refreshed during the 15-month contract period?

During the 15-month POP, new content will be developed/updated once, major annual update, for each business line (7 business lines in total: Flood Risk Management; Hydropower; Water Supply; Recreation; and Navigation, which includes Great Lakes Navigation, Coastal Navigation, and Inland Navigation).

13. Are there specific guidelines for PDF formatting, version control, or metadata tagging to be followed?

There is a specific requirement for PDF formatting. There is an existing structure and format. As part of the modernization/improvement effort, this existing structure may change. However, for the most part, it will adhere to the existing structure/format. The awarded contractor may use the existing structure as template.

14. Will vendors be expected to support document version audits or maintain logs for historical file access?

Yes. The awarded contractor is expected to provide document audits to ensure accuracy of the data, content/narratives, and any content posted on the website. Additionally, the contractor is also expected to maintain and manage historical data, as they are also made available on the website.

15. What is the current web analytics setup (e.g., Google Analytics, Matomo), and will vendors receive access to historical performance data?

The awarded contractor will have access to historical performance data.

16. How frequently should performance reports and analysis dashboards be submitted to USACE (monthly, quarterly, etc.)?

As stated in the PWS, website analytics data is expected quarterly – once in December, March, June, and September, at the minimum. More frequent analysis would be helpful/welcome but not required.

17. Is there a defined Service Level Agreement (SLA) for response time, bug fixes, or content errors?

As stated clearly in the PWS, critical site errors must be resolved within 24 hours.

18. Are there any anticipated high-traffic periods or mission-critical events that vendors should prepare for?

No specific high-traffic periods. Website traffic is expected to be steady over the FY. Mission-critical events would be around JUNE through SEPTEMBER, as they are when the USACE project team will be providing the contractor with data for the massive annual update.

19. Are past performance references required to be federal clients, or are private-sector projects acceptable? Will commercial past performances be considered?

Both federal and private projects are acceptable. Relevancy will be considered in assessing past performance.

20. Is there a page or word limit for technical proposals, particularly for narrative content sections?

There is no limit.

21. Will there be an opportunity for oral presentations or proposal walkthroughs after submission?

No. There will not be an opportunity for oral presentations.

22. Is there any restriction for using subcontractors. Should subcontractors or teaming partners be listed in the proposal, and if so, what documentation is required?

Subject to FAR 52.219-14 “Limitations on Subcontracting” there is generally no restriction for using subcontractors. Subcontractors/teaming partners should be listed in the proposal. Any members who will be considered for supporting this project should be noted with their credentials to aid in the assessment.

23. Is there a preference for vendors to be GSA schedule holders or small/disadvantaged businesses?

This requirement was a total small business set-aside. There is no preference for GSA schedule holders or any socioeconomic category of small business.

24. What is the expected kickoff timeline after contract award?

We expect the kickoff meeting to take place within the first month of the contract award.

25. Will a dedicated USACE point of contact be assigned for day-to-day coordination and approvals?

Yes. A dedicated USACE POC will be assigned, likely the Program/Project Manager for the VTN Program.

26. The PWS indicates a 15-month base period with a 15-month option (30 total months), but FAR 52.217-9 states the total duration shall not exceed 24 months. Could the government clarify this discrepancy?

The PWS governs.

27. Are there any technical constraints, legacy system dependencies, or required integrations that are not mentioned in the PWS?

Nothing specific.

28. Are there specific security requirements (FISMA compliance levels, ATO requirements) for the website platform? Are there any security clearance requirements for contractor personnel, or is Public Trust sufficient?

Public Trust is sufficient for this work, as the contents will be made available to the public.

29. Can the government provide more specific details on the "additional information" that will be provided by the USACE Team for developing new Fast Facts and narratives?

The USACE Team will provide all data relevant for the update. The contractor shall develop and/or update content based on the data provided. The “additional information” mentioned in the PWS include information that the project team wants the contractor to include in the contents/narratives for the annual update cycle.

30. For "ad-hoc inquiries and requests related to improvement and modernization efforts," what is a typical volume or scope of these requests?

The “ad-hoc inquiries and requests related to improvement and modernization efforts” may include updating specific content/information on the website, uploading new graphs or tables (enhancing information delivery by transitioning from text heavy content into more visual representation), improving UI components. The volume of this is expected to be minimal to moderate (once per month) in varying complexity.

31. Approximately how many Fast Facts reports exist currently, and what is the typical page length/content volume for each report?

Each Fast Facts Report is one page. There is a Fast Facts Report (in downloadable PDF) for the national-level data, division-level data, and district-level data for each business line (7 business lines in total). Some business lines have state-level data, some have lake-level data, and some have project-level data. Each business line should have about 100 Fast Facts Reports.

32. For the 24-hour critical error resolution requirement - how is a "critical error" defined? (site down, broken links, incorrect data, etc.)

“Critical error” is defined any malfunction or failure that renders any part of the website partially or fully inaccessible, compromises data integrity, or prevents users from accessing essential contents or services. This includes, but not limited to, broken navigation links, missing or incorrect information, etc.

33. For the Excel spreadsheet requirement in Factor 1 - should this include estimated hours for the 15-month base period only, or for both base and option periods?

There should be information for each of the base period and the option period.

34. For Past Performance evaluation, what constitutes "recent/relevant" experience? (timeframe and specific types of projects)?

Recency is defined as within the previous 3 years from the date the solicitation was posted.

Relevancy is determined by considering the similarity of service/support provided, complexity, dollar value, contract type, and degree of subcontracting/teaming.

These two items in addition to quality of past performance will be considered collective to assess confidence as detailed in the Combined Synopsis-Solicitation.

35. Can you provide examples of the types of "visualizations" and "modernization efforts" the Government is most interested in implementing?

Modernization efforts include enhancing information delivery by transitioning the currently text-heavy content into visually structure formats, including graphs, tables, and other data visualizations. Additionally, this may also include improved UI and website navigation.

36. Are there any planned major website redesigns or platform migrations during the performance period?

No major redesigns and/or platform migrations are planned during this POP. Consideration for future major overhaul may be discussed and/or strategized.

37. Is there a specific format or template the government would prefer for the price proposal? Should pricing be broken down by the CLINs provided?

Prices must be provided per the CLIN structure provided. Other price data must also be provided which includes the proposed hourly rates, and the proposed level of effort proposed per labor category/person per each task in the PWS.

38. How are the required IT standards, branding, style, and digital/website evaluated, and how is compliance determined?

Compliance is determined by adherence to the applicable standards and guidance outlined on Digital.gov, including those related to accessibility, usability, and federal web performance. Style and branding shall adhere to and follow other USACE-IWR webpages.

39. Is there an automated process, or a person or team who is responsible and who will give feedback? And if so, how long does the review process generally take?

The USACE Project Team will provide feedback to any of the updated content and information made by the awarded contractor. The contractor can expect about a week in review by the Government.

40. The PRS mentions the acceptable quality levels but wasn't clear on the process to determine the quality level.

The PWS provides the acceptable quality levels for 6 performance standards. The quality level (high quality vs. low quality) will be determined by the Program/Project Manager, or a designated USACE project team member, and will focus on accuracy (alignment with source data, correct interpretation, and error-free), timeliness (delivered within agreed-upon timeframe), and clarity/structure (information is presented in a clear, sound manner meeting the guidelines provided by the project team).

41. Will contractor/developers have access to a dev sandbox site for pre-deployment to production and have the ability to sign off on requested changes?

It is possible but not guaranteed a dev sandbox site can be provided.

42. IRT Support v Development (new elements) what are the baseline plans to determine price variance?

Prices are proposed by the offeror. It is understood price largely correlates to the proposed level of effort per each labor category per each task in the PWS. The price to be analyzed is the total price inclusive of the base and all options.

43. Can the government provide any guidance regarding the level of effort required in terms of labor category hours? Full-time equivalents?

Offerors shall propose the level of effort in terms of hours per labor category. See Factor 1 “Offerors must include an Excel spreadsheet separate from their price proposal that details the labor categories, mix of labor and quantity of labor hours per task in the PWS”. This is an evaluated factor, thus reflective of the Offeror’s unique understanding and approach to fulfilling the requirement.

44. What is the approval process to get new content posted to the website (within IWR and USACE)?

The Contractor shall get new content reviewed by the USACE Project Team prior to posting anything on the website.

45. Can the government provide sample or representative source materials (data and additional information) from which a Capital Stock or Fast Facts narrative and analysis would be generated?

https://www.iwr.usace.army.mil/Missions/Value-to-the-Nation/Fast-Facts/

46. Who are the target audiences for the VTN website?

The target audience includes the public, USACE leadership, and congressional staff.

47. What are the USACE Team’s immediate- and long-term goals (or top priorities) for improving and modernizing the VTN website?

Immediate goals include enhancing information delivery by transitioning from text-heavy content into visually structured formats, including graphs, tables, and other data visualizations. Additionally, immediate to mid-term goals include improving the UI and navigability of the website, in general, to enhance ease of use and ease of information accessibility.

48. What is the government’s current or preferred tool for tracking website analytics?

Currently, the USACE project team is interested in knowing traffic data (# of visitors, pageviews, bounce rate, session duration, pages per session… etc.). The team welcomes any other metrics.

49. What are the government’s goals or key performance indicators (KPIs) for the VTN website (traffic, user behavior, user journeys, downloads, etc.)?

Key performance indicators (website analytics) include traffic data (# of visitors, pageviews, bounce rate, session duration, page per session… etc.). # of downloads would also be valuable.

50. Under Task 2, can the government confirm that support for “maintenance, improvement, and modernization efforts” are limited to website content and do not include development support for the website infrastructure, architecture, content management system, or other code?

Task 2 (Support for VTN website analytics, maintenance, improvements, and modernization efforts) is primarily focused on ongoing maintenance to ensure operation of the website (making sure all contents are live and links operational without critical errors), as well as improvements and enhancements to content delivery (transitioning from text-heavy content to include more data visualization) and UI (creating links and/or additional pages and removing possibly redundant pages).

51. The government requires the Contractor to possess knowledge of its intranet. What are the expectations for the Contractor relevant to the IWR intranet?

The Contractor is expected to be familiar with the IWR intranet and/or become familiar with it upon award.

52. Does the PWS include direct management of content on the VTN website (i.e., working within the VTN content management system to upload/post PDFs, update page copy, manage the information architecture/navigation, etc.)?

The Contractor is expected to manage the contents on the VTN website directly. The contractor is also expected to develop the PDFs (and then upload them to the VTN website) based on the data provided to them by the USACE project team.

53. Does the government have a preferred approach or cadence for progress reporting under the PWS?

Given the responsive nature of the work, progress will be tracked through a request-and-approval workflow. The Contractor will submit proposed updates in response to USACE project team inquiries/requests and/or data submission, and upon approval, implement the changes. This should provide a clear and traceable record of progress.

54. Can the Government provide information on the current team size and labor roles supporting the VTN content and website?

Details regarding the current project team size and labor roles are internal to the Government and not relevant to Contractor responsibilities under this requirement.

55. Are offerors allowed to propose Key Personnel or support staff who are on valid U.S. work visas (e.g., H-1B, L-1, etc.)?

Contractor personnel must be US citizens.

56. Are there any page limits or formatting requirements for the technical and business/price volumes?

There are no page limits or formatting requirements. Times New Roman is a preferred font.

57. Any specific formatting guidelines for pricing, or may Offerors use a format of their choosing?

Offerors may use the format of their choosing. Price information as detailed in the Combined Synopsis Solicitation must be provided.

58. Is there possibility of just one option year or more?

One option year.

59. Additional support USACE will be firm fixed price or T&M or Labor hour?

This question cannot be answered. The Government does not know what is being asked.

60. Please clarify whether the Government intends to provide transition support, documentation, or training to enable the Contractor to obtain this required knowledge, or if the Contractor is expected to have this knowledge fully in place at contract award?

The Contractor should have sufficient knowledge at the time of award to ensure immediate and effective performance. The Government cannot guarantee it will provide transition support, documentation, and guidance to facilitate knowledge transfer and onboarding.

61. Will the Contractor be required to create new data visualizations or only update existing ones, and are there preferred visualization tools or frameworks? PWS 3.3, 5.1

No specific visualization tool or framework in mind. The contractor is expected to create new data visualization and update existing ones, based on the data submitted to them by the USACE project team and reflecting the project team’s intended narrative and presentation preferences, which will be determined at a later time, ensuring that the data is conveyed clearly, accurately, and in a manner that supports effective storytelling.

62. Can the Government confirm the current CMS or content management architecture used for the VTN site, and whether it is custom-developed or based on a commercial platform? PWS 3.3

The CMS being used by the incumbent is proprietary information as to their technical approach. The offeror can use a CMS of their choosing that is appropriate to achieve the objectives in the PWS.

63. Are there existing APIs or automated data feeds from USACE systems to the VTN site, and will the Contractor be responsible for maintaining or enhancing these integrations? PWS 3.3

The Contractor will be responsible for maintaining the VTN site and the content and data on the site. The contractor can utilize APIs as appropriate. No existing APIs are currently being utilized.

64. Does the Government require formal independent third-party testing or certification (e.g., Section 508 compliance audits, security reviews) for any deliverables, or is Contractor-led verification sufficient for acceptance? PWS 4.4

Contractor-led verification should be sufficient.