RFI Budget and Planning Application_ SOO 2024 (Final ).pdf

GENERAL SERVICES ADMINISTRATION (GSA)

OFFICE OF ADMINISTRATIVE SERVICES (OAS)

OFFICE OF CHIEF INFORMATION OFFICER

REQUEST FOR INFORMATION #: 47HAA025N0001

STATEMENT OF OBJECTIVES

GSA Budget and Planning Application (BAPA)

NAICS Code: 541519

Product and Service Code (PSC): DA01

Posting Date:

October 11, 2024

Closing Date:

October 28, 2024 @ 11 AM EST

Statement of Objectives (SOO)

Disclaimer

This Request for Information (RFI) is for planning purposes only and is not a Request for Quotes (RFQ), Request for Proposals (RFP) or an obligation on the part of the Government to acquire any services.

Responses to this RFI are not offers and cannot/will not be accepted by the Government to form a binding contract. The Government reserves the right to determine how it should proceed as a result of this notice. Furthermore, those who respond to this RFI should not anticipate feedback with regard to their submission. However, the government may engage vendors that respond to this notice by seeking further information about capabilities. The Government will not pay any cost incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the responding vendor expense. The information provided in this RFI is subject to change and is not binding on the Government.

1.0 INTRODUCTION

The General Service Administration (GSA) Office of the Chief Information Officer (OCIO) in coordination with the Office of the Chief Financial Officer (OCFO) will be using OneStream to help manage the Agency’s complex budgeting process. This Statement of Objectives (SOO) describes the goals that GSA expects to achieve with regard to development, modernization, and enhancement (DM&E).

2.0 BACKGROUND

GSA awarded a contract in September of 2021 to acquire OneStream licenses and integration services to configure a Budget and Planning Application (BAPA) that enables GSA users to complete complex planning activities. GSA completed the implementation in March of 2023 standing up OneStream as a cloud based solution with an Authority to Operate. OneStream now serves as GSA’s agency-wide Budget Formulation system of record used to collect budgetary data from programs, perform cost allocation processes, generate reports, and share data with other GSA systems. With the major modules completed, OneStream now moves into a primarily an O&M phase with some smaller enhancements still required.

3.0 CURRENT SYSTEM FUNCTIONALITY

As background, current system capabilities for this solution include the following:

1. Ability to manage a hierarchy that allows GSA to budget at the lowest level of its organization, while allowing users to view budget roll-ups at different levels of the hierarchy.

2. Ability to formulate budget requests and track execution across at least 15 different funds.

3. Assigns financial codes to each cost center to track budget execution by cost center in the GSA financial system (support at least 2,000 cost centers). Each cost center has its own Line of Accounting.

4. Allows Super Users to realign and rename cost centers within the budget hierarchy to support organizational realignments.

5. Allows Super Users to control access to cost centers to certain users.

6. Allows Administrators and Super Users to customize the input screens of individual cost centers (or groups of cost centers) to tailor them to unique needs of those center(s) [Ex:

showing complete object class table vs select object/sub-object classes that apply to an organization].

7. Supports at least seven years of budgets (current year, next fiscal year matching GSA’s Congressional Justification, two years out to develop the OMB Budget Request, and four out years).

8. Supports monthly plans for at least each of the first three years. At certain points of the year, GSA is managing three years: the current fiscal year, the next fiscal year (FY +1), and the year of the President's Budget is being developed (FY+2).

9. Allows user to develop non-Personnel compensation and benefits using a variety of methods, including the following:

a. Lump sum direct entry for the cost center;

b. Line item enter descriptions for items such as contracts, equipment, travel, etc.

i. Able to enter various items related to that line item, such as vendor, project codes, description of service, financial system document number, etc.

c. Budget based on some kind of factor (cost per trip, dollar amount for travel per employee, etc.).

10. Ability to budget according to OMB Object Classification structure and drill down to defined sub-object classes.

11. Develops GSA’s Budget Exhibits, including an Object Class Table that contains the GSA-wide total that includes the sum of all GSA funds by object class.

12. Ability to customize the cost categories used for each organization but will allow roll up to GSA’s sub-object class and OMB’s Object Classification system.

13. Allows GSA to develop different models for formulation that can be customized within the hierarchy by fund or a lower level of the hierarchy (ex: allows differentiation in the PC&B models, the view an end user sees, etc.); despite differentiation, everything will need to tie back to a consistent object class table.

14. Allows GSA to formulate budgets that account for both obligation and expense plans by cost centers.

15. Tracks obligations and expenses by cost centers (requires connection with GSA’s financial system or file upload).

16. Allows GSA to develop pro-forma income statements for different funds that roll up into business line, portfolio and fund-wide pro-forma income statements based on lower-level income statements, some of which are roll-ups themselves (ex: Federal Acquisition Service > General Supplies and Services > Retail Operations > etc.).

a. Allow GSA to assign cost centers to a specific line on the income statement (allocation methodology will determine which specific income statements get the costs, but those costs will show up on the same line of the income statement regardless of which income statement they show up on).

b. Different income statement formats by fund to account for unique needs.

17. Allows GSA to enter revenue and other non-budgetary expenses (ex: depreciation) to the system, which would flow to the pro-forma income statements.

a. Similar hierarchical structure as the pro-forma income statements that allows

GSA users to enter this information at the lowest level.

b. Enter revenue per one of the following methods: Direct Entry; Revenue = Cost of

Goods Sold + Markup factor; Business Volume to Revenue Conversion [ex:

Business Volume of $1,000,000 equals $7,500 in revenue (0.75% fee)].

18. Supports Working Capital Fund (WCF) Bill Generation, which involves the allocation from cost centers to services to customers using several general allocation methodologies such as laptop count, employee headcount, and obligations as well as a handful of allocation methodologies that are directly tied to usage.

19. Supports the Acquisition Services Fund cost allocation process, which involves more than 100 steps that take costs from cost centers and assigns them to cost pools, which are ultimately assigned to the various income statements within the Acquisition Services Fund; different allocation methods used in the ASF in its cost allocation methodologies include the following:

a. Relative Share (System Calculated) [ex: System adds up the total operating budget of all the various ASF organizations and assigns the overhead based on each income statement’s share of the total operating budget].

b. Relative Share (Table Driven) [ex: Super User enters the count of an allocation driver, which the system then uses to assign the proportionate level of cost to each income statement].

c. Relative Share of Relative Share [ex: System develops a relative share of various cost pools developed by a previous step’s relative share calculation and calculates the relative share of those cost pools to assign costs to the appropriate income statements].

d. Workload Entry - Lowest Level [ex: Users directly enter the percentage (or dollar amount) of their cost center’s budget to allocate to the income statements at the bottom of the income statement hierarchy].

e. Workload Entry - Summary Level [ex: Users directly enter the percentage (or dollar amount) of their cost center’s budget to allocate to income statements that are roll-ups of multiple lower level income statements and then a relative share calculation allocates them to the lower level income statements].

f. Direct Allocation - Cost center's budget is allocated 100% to a specific income statement.

g. Multiple Allocation Methodologies [ex: Allocates 50% of a cost center’s budget using one of the above allocation methodologies and the other 50% using another].

20. Allows GSA Administrators to manage the allocation process (adjust the steps, allocation methodology for cost centers, etc.).

21. Allows GSA to run reports from the budget system, containing the various information (budgets by cost center/roll-ups of cost centers), revenue projections, pro-forma income statements, WCF Bill/service.

22. Supports a workflow process that allows OCFO to control who has edit rights to a cost center/revenue center at certain points of time.

a. Ex: Programs enter budget requests and submit to the OCFO, at which point the OCFO has the ability to make changes. The program can view the cost center at this point but can’t edit the budget.

b. Ability to control access to certain years’ budgets within a cost center is preferable.

23. Allows GSA to save snapshots/iterations of the budget at various points in time so that the OCFO can go back and reference it later.

a. Ex: Snapshot of the program request level, OMB request level, CJ request, enacted budget, mid-year realignment, etc.

24. Allows GSA to develop various forecast scenarios and revert those forecasts back to the previous version of the budget.

25. Allows GSA to pull in actual financial information (via direct feed, etl, file upload) into the system so OCFO and program users can view plan vs. actual information.

a. Allow OCFO users to develop and save forecasts in the tool based on plan and year to date execution.

b. Allow GSA to run status of funds/Budget execution/plan vs. actual reports using the tool that can be run at various levels of the cost center/revenue hierarchies or even along another dimension such as region.

c. Able to bring non-financial information into the system/tool so the OCFO can develop and track financial metrics and evaluate program efficiency over time.

26. Allows GSA to develop and track its budget in a way that allows it to follow an organizational cost center structure while also supporting the Technology Business Management taxonomy.

a. Develop plan and actual reports that align with the TBM taxonomy

27. Allows Super Users to build and modify models used to formulate the budget and assign them to the appropriate cost centers as needed.

28. Allows for web-based data entry; no-reliance on Microsoft Excel.

a. Allow reports to be downloaded and viewed in Excel, Google Sheets, or another spreadsheet program.

b. User-friendly interface that allows users to enter data seamlessly without waiting long periods of time for the data to save.

29. Meets GSA IT ATO requirements for moderate risk.

30. If the system is a SaaS solution, it shall be FedRamp moderate certified (or in the process of obtaining FedRamp certification) – See Section 11.

31. Supports Multi-Factor Authentication or GSA's Single Sign-On Capability.

32. At the time of implementation, allow GSA to import initial data via Excel/CSV file uploads or other forms of data importation.

33. User management module to allow GSA system administrators to update, delete, and create user groups and accounts; allow system administrators to grant and remove access rights.

34. Ability to encrypt all data at rest.

35. Allow GSA flexibility to assign and reassign licenses as the number of users may fluctuate over the life of the resultant task order award.

4.0 OBJECTIVES

GSA has two primary objectives described in 4.1 and 4.2 below.

4.1 License Procurement Objectives

Allow GSA flexibility to assign and reassign licenses as the number of users may fluctuate over the life of the resultant task order award. The budgetary quotation should account for the following baseline: 250 mandatory users. The government requests that the vendor include the capability to scale up, with proposed increments ranging from 250 to 600 users.

4.2 Support Services Objectives

The General Services Administration (GSA) is se eking support to maintain and enhance GSA’s existing budgeting solution that enables current users to complete activities relating to cost center and project planning, labor planning, revenue planning, allocations, and analytics and reporting.

GSA is seeking support to configure the system capabilities and complete developer activities as described below.

Provide developer support for a minimum of 1,040 mandatory hours. The government requests that the vendor include the capability to scale up 1040 additional optional hours a year that provide support for the following activities laid out below (General O&M, Budget Planning Increments, People, Project/Thing Planning, etc).

This support would be treated as a general base pool for hours.

General O&M

● Work with OneStream’s Customer Service Portal to ensure the system remains available to users; except during scheduled downtime to be communicated 10 business days in advance.

● Troubleshoot errors and performance issues as they arise with responsiveness within 24 hours.

● Supports existing business rules by modifying and improving code to ensure that system functionality is maintained.

● Supports migrations to newer FedRamp compliant versions of OneStream as they become available.

● Supports GSA’s data integrity by uploading, clearing, and cleansing GSA’s data (e.g. duplicative data).

● Support existing cube views if modifications are required to the intersections, formatting, parameters.

● Build new dashboards and input forms to collect and visualize data as business processes dictate.

● Supports reorganizations in OneStream, maintaining accurate data from previous iterations of the budget.

Budget Planning Improvements

● Allows Administrators/Super Users to set global assumptions such as pay raises or increases.

○ Percent growth method where the user enters a growth factor/assumption and the system calculates this year’s figure based on prior year execution or value.

● Supports annual, multi-year and no-year periods of availability [currently the multiyear funds are managed on a more manual basis outside of OneStream].

People Planning

● Allows user to develop personnel compensation and benefits using a variety of models (that can be assigned to specific cost centers), including the following:

○ Average salary and benefit by employee in the cost center;

○ By lump sum salary and benefits budgets at the cost center.

Project and Detailed Level Planning

● Overhaul GSA Dimensionality to remove Project Code from the Cube and instead manage GSA’s project and other detailed object class data in a relational database through OneStream’s thing planning solution or another comparable solution.

● Design a quick and efficient module that allows users to easily add, delete, and modify rows of data.

● Identify, test, and troubleshoot any issues with implementation that impact reporting and other aspects of GSA's application.

● Update and maintain the relational database solution as other aspects of the application are modified.

Data Integration

● Build a new data exchange between OneStream and Amazon Web Services (e.g.

S3) so that data can be visualized in software such as Microstrategy.

● Supports GSA’s existing data export processes where reports are sent to GSA’s

SFTP server through the use of business rules, a data management job, and task scheduler to automate the processing of the data management job.

● Allows GSA to automate the ingestion of actual financial information (via direct feed, ETL, file upload) into the system so OCFO and program users can view plan

vs. actual information.

● Supports new API conventions allowing OneStream to exchange data with systems or data platforms such as mulesoft, sailpoint, or GSA's internal business systems.

Making Use of Actuals

● Allow OCFO users to develop and save forecasts in the tool based on plan and year to date execution.

● Allow GSA to run status of funds/Budget execution/plan vs. actual reports using the tool that can be run at various levels of the cost center/revenue hierarchies or even along another dimension such as region.

● Able to bring non-financial information into the system/tool so the OCFO can develop and track financial metrics and evaluate program efficiency over time.

● Using transformation rules or other reconciliation methods, support identification of data exceptions (where the actual budget execution data does not map to onestream’s valid data intersections), providing the ability to map these exceptions to valid intersections so that future actual data is aligned.

Training & Documentation

● Lead virtual on-demand and instructor-led training sessions on new functionalities or refresher training on how to use the existing functionalities.

● Provide new user training for new employees as needed and requested by GSA.

● Enhance OneStream knowledge among end users to increase user engagement and data entry accuracy.

● Develop and provide relevant training documentation such as user guides, how-to guides, reference guides to GSA within 30 business days of completion of enhancements.

● Assist with the development of any training materials specific to GSA OneStream processes.

● Guided training to include exercises, videos, or user guides to help users understand OneStream functionality.

● Update GSA’s system design documentation as necessary to capture major changes and enhancements as they are completed.

Potential Development Tasks

● Develop modules to intake, evaluate, approve or reject unfunded requests or changes to existing approved plans.

● Identify opportunities to incorporate OneStream’s modeling, forecasting, machine learning, and artificial intelligence features.

● Improve system accessibility and digital inclusivity by implementing section 508 compliant solutions.

User Experience Enhancements

● Identify performance issues such as lengthy load times and implement solutions to improve runtimes.

● Identify inconsistent design elements and implement a more consistent and professional design aesthetic.

● Enhances user experience by creating consistent, familiar, branded, dashboards and reports to improve usability and deliver a more cohesive and professional application.

Reporting Maintain GSA’s Budget Exhibits, including Object Class Tables that contain the GSA-wide total that includes the sum of all GSA funds by object class.

● Budget Reports - Generates reports of the status of plan/request information in the budget system for the previously mentioned modules at various levels of the cost center and revenue hierarchies.

● Execution Variance Reports - generates reports comparing actual execution with the plan information in the budget system for the previously mentioned modules. Tracks actual availability compared with projected availability.

● Budget Exhibit Reports - generate GSA’s tables/exhibits used for the OMB & Congressional Budget Exhibits based on the information in the previous models.

Examples include Object Class Tables, Explanation of Changes, and other fund specific tables. Track’s iterations of various exhibits on certain dates.

ATO Support

● Provide HelpDesk support during GSA business hours from 9 a.m. to 5 p.m. EST.

● Maintain availability through chat platforms such as Google Meet.

● Document significant system changes in a ticketing system such as Jira, Smartsheets, or other similar tools.

● Update required security documents to maintain GSA ATO.

● Support yearly ongoing security authorization to operate.

5.0 CONTRACT TYPE

This task order will be a Hybrid –consisting of Firm Fixed Price and Labor Hour CLINs. This order is a FIRM FIXED PRICE/LABOR RATE for technical services provided and FIRM FIXED PRICE for software or Other Direct Cost to be delivered as part of this order. The Government anticipates the Contractor to perform at a level of effort (LOE) that imposes a minimal amount of administrative burden upon either party and promotes a maximal amount of reducing waste and inefficient performance.

6.0 PLACE OF PERFORMANCE

The majority of work required by this task order will be performed remotely or at the contractor’s site. Upon customer request, the contractor may be required to come to GSA Headquarters, 1800 F Street, NW, Washington, DC 20405 for training sessions.

All work days referenced in this SOO are business days in which work is expected to be performed, excluding weekends and all federal holidays (see table below), unless otherwise specified. The Contractor will be expected to perform all work at the Government’s facility, or previously authorized location, within the hours of operation currently anticipated between the hours of 7:00 AM and 7:00 PM Eastern Time.

With written notice to the Contractor, GSA may extend, reduce hours, not exercise options, or terminate any TO resulting from this solicitation based on the Government’s need for the technical requirements.

6.1 Travel

Travel is not anticipated for this requirement. Travel at times may be at the Contractor location, or an alternate Government authorized telework location. Local travel may be required from the Government’s site to Virginia, Maryland or the District of Columbia. The Government will not pay for local travel within a 50 mile radius of the designated performance location; with consideration to frequency.

6.2 Federal Holidays

In accordance with the Office of Personnel Management set by law (5 U.S.C. §6103) that are followed by GSA, are identified in Table 1 below:

Table 1 GSA’s Observed Federal Holidays

Federal Holidays Designated Dates

New Year’s Day January 1

Martin Luther King’s Birthday Third Monday in January

President’s Day Third Monday in February

Memorial Day Last Monday in May

Juneteenth June 19 (Date observed varies)

Independence Day July 4

Labor Day First Monday in September

Columbus Day Second Monday in October

Veterans’ Day November 11

Thanksgiving Day Fourth Thursday in November

Christmas Day December 25

7.0 PERIOD OF PERFORMANCE

The period of performance shall be 12 months from the date of award with four option years.

Base Year: Date of Award plus 12 Months Option Year 1: End of Base Year plus 12 months Option Year 2: End of Option Year 1 plus 12 Months Option Year 3: End of Option Year 2 plus 12 Months Option Year 4: End of Option Year 3 plus 12 Months

8.0 KEY PERSONNEL

The contractor shall identify key personnel in the technical quotation regardless of the type of task. NOTE: Key personnel may not be removed from the task without express approval of the Contracting Officer.

8.1 Task 1 BAPA Project Support

The Contractor shall perform deployment, installation, development, configuration, requirements gathering & analysis, documentation, operations, and management activities in support of BAPA including:

8.1.1 Change Management

The Contractor will follow the GSA IT Change Management plans to cover all analysis, development, and implementation work for new/existing applications and their supporting processes’ changes throughout the project life cycle. The Change Management plan consists of but is not limited to the following:

1. Readiness assessments, migration plans, communication and collaboration, user training, and performance measures

2. Steps to obtain buy-in through user and management participation throughout system development and implementation

8.1.2 Testing

The Contractor shall support the Government and/or its other vendors on testing the budgeting solution or their components to ensure they operate as intended in the existing GSA IT environment. This will include:

1. Development, testing, and verification of application integration support for existing and future GSA business systems.

2. Production and Pre-Production Testing support for the developed budgeting solution.

3. Create and execute automated or manual test scripts for the budgeting solution.

4. Support GSA testers and QA to test the developed budgeting solution.

5. Document test results.

6. Repair defects found in testings.

8.1.3 Technical Requirements Development

The Contractor will support the development of technical requirements. The Contractor will review resulting deliverables, as tasked, on new projects and changes to existing projects including, but not limited to, GSA IT systems and platforms. The results of this task will be presented according to the Contractor’s proposed timelines and milestones.

Technical requirement deliverables will be in written form including briefings, electronic correspondences, and white papers as requested.

8.2 Task 2 Optional Supplemental Task Support

An Optional CLIN will be used for meeting the objectives of the OCFO Divisions. The Government may exercise an optional supplemental task support requirement, as needed, to request that additional Contractor personnel be assigned to perform a variety of tasks. The Contractor will have in place procedures to cope with increased demand that peak above proposed thresholds. OCFO will fund this CLIN as needed and based on BAPA requirements which will be determined on an annual basis.

9.0 PERSONNEL REQUIREMENTS

9.1 Developer

1. Subject Matter Expert with multiple budget solution implementations

2. Responsible for detailed design of application and modules and manages all technical delivery

3. Experience developing a budgeting system

4. Experience developing budgeting reports

5. Knowledge of systems integration and reporting

6. Experience testing packaged and custom developed financial and/or budgeting applications

7. Experience developing test plans, test scenarios/ cases and managing testing execution

8. Experience developing and executing training for packaged and custom developed financial and /or budgeting applications

10. ADDITIONAL INSTRUCTIONS TO INTERESTED PARTIES

Please provide detailed responses to the following questions, October 28, 2024, 11:00 AM

EST:

1. What increments do you offer for licenses?

GSA requests a quote that includes the ability to scale from 250 to 600 licenses.

2. What increments do you offer for labor hours?

GSA requests a quote that includes the ability to scale from 1,040 hours to 2,080 hours.

3. What experience do you have with OneStream data integration?

Additionally, do you have experience configuring OneStream Marketplace Solutions (e.g., Task Manager, People Planning Software, Thing Planning, etc.)? Please provide an example to illustrate your expertise.

RESPONSE INFORMATION:

Responses are due no later than October 28, 2024 by 11:00 AM EST. Submit your responses via email only in “.doc”, “.docx”, or “.pdf” file formats to Erica Pelham, Contracting Officer, at erica.pelham@gsa.gov & Bonnie Impastato, Acquisition Advisor, at bonnie.impastato@gsa.gov with the email subject header “RESPONSE - RFI 47HAA025N0001 – Budget and Planning Application (BAPA) - {your company name}”. All responses received after the due date will not be considered. The Government is not obligated to review responses to the RFI received after the deadline specified above. Please be advised that all submissions become Government property and will not be returned.

Interested respondents that can provide support services are requested to provide the following information:

● Name of Company mailto:erica.pelham@gsa.gov mailto:bonnie.impastato@gsa.gov

● Company Description

● Type of Business (large or small business type. i.e. Woman-Owned, Hubzone)

● UEI number,

● NAICS Code

● Point of contact (POC) name, phone number and email address

● A brief high-level description of existing capabilities to perform the support services referenced herein

The Government is not obligated to and will not pay for any information received from potential sources as a result of this RFI. It is requested that interested vendors submit to GSA’s Contracting Officer a brief capabilities statement package (single spaced, one sided, letter size, Times Roman, 12-point font minimum, with one (1) inch margins, in “.doc”, “.docx”, or “.pdf” file formats with a maximum of four (4) pages, including the cover page, demonstrating their ability to provide a solution and perform the requested services.

No Classified information will be included anywhere in your responses.

All proprietary information must be clearly marked in accordance with the instructions set forth below in “Marking Requirements.” Any information submitted in response to the RFI may be disclosed to GSA and other Government personnel. All information marked as proprietary information will be safeguarded by GSA to prevent unauthorized disclosures to non-government personnel and entities in accordance with applicable law and regulation. The GSA reserves the right to challenge proprietary information markings.

Marking Requirements: The header and footer of each page containing interested source proprietary information shall be marked with the legend “PROPRIETARY INFORMATION.”

Further, the particular paragraph(s) section(s), etc. containing the actual proprietary information shall be clearly high- lighted or otherwise marked by the Respondent.

This is an RFI. No solicitation exists; therefore, do not request a copy of the solicitation. The information provided in this RFI is subject to change and is not binding on the Government.

GSA has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned.

QUESTIONS

Questions regarding this RFI shall be submitted to the Erica Pelham, Contracting Officer, at erica.pelham@gsa.gov & Bonnie Impastato, Acquisition Advisor, at bonnie.impastato@gsa.gov with the email subject header “QUESTIONS - RFI mailto:erica.pelham@gsa.gov mailto:bonnie.impastato@gsa.gov

47HAA025N0001 – Budget and Planning Application (BAPA) - {your company name}”. by October 16, 2024 at 5:00 PM EST. Please use Attachment B Questions Template to submit all questions. No questions will be accepted after the specified time and due date to submit questions. Each question submitted must cite the RFI Section number/title/RFI question number for which the question pertains, unless the question is general in nature and not specific to a particular portion(s) of the RFI. (No questions will be accepted by telephone). Do not include the following in your response:

● Proposals or offers

● Requests to be considered for award or to be notified of a future solicitation

● Requests to be added to a mailing or distribution list

● Questions or comments not related to this RFI

● Classified information

This notice is for informational purposes only and does not constitute a solicitation or Request for Quote. This notice is not to be construed as a commitment by the Government to contract for services. Please be advised that the Government will not pay for any information provided as a result of this notice and will not recognize or reimburse any costs associated with any RFI submission.

The vendor should identify any proprietary information in their RFI response. Proprietary materials will neither be distributed nor discussed with any other vendor. The use of information submitted to the Government as a result of this RFI will be at the discretion of the Government. The Government will not provide comments to any vendor’s submission.

8.2 Task 2 Optional Supplemental Task Support