RFP 842367147 - WMOS Japan Region and Replenishment Module Redcated.docx

HC108423R0013

Section SF 1449 - CONTINUATION SHEET

PWS

PERFORMANCE WORK STATEMENT (PWS)

1. Contracting Officer’s Representative (COR).

a. Primary COR. See Points of Contact in Contract Administration Data Name:

Phone Number:

E-Mail Address:

b. Alternate COR. See Points of Contact in Contract Administration Data

c. Property Administrator SEE COR information below:

Name:

Phone Number:

E-Mail Address:

2. Contract or Task Order Title. Defense Commissary Agency’s (DeCA) Central Distribution Centers (CDCs) Warehouse Management Open System (WMOS) for Japan Region and Purchasing Module for All DeCA CDCs

3. Background. DeCA manages commissary operations worldwide for the Department of Defense (DoD). These operations are supported with various systems using commercial-off-the-shelf (COTS). A crucial part of DeCA’s overseas and geographical separated commissaries Resale supply chain involves CDC’s and warehouse functionality. DeCA currently has fielded the WMOS COTS solution to DeCA’s CDCs in Europe, Guam and are planning deployment into Korea. In addition, to the current solution supporting warehouse management operations, DeCA requires the solution to also support the CDC item ordering and replenishments to fully support all operational requirements within a single standardize solution. As directed by Department of Defense Software Modernization Strategy (Feb 1, 2022), Cloud services and data are fundamental to software modernization. Software must smartly utilize cloud services and incorporate data best practices to ultimately deliver impactful capabilities. To achieve and comply with the strategy DeCA requires the solutions to be hosted within a FedRAMP Authorized environment.

The state-of-the-art Warehouse Management Operating System (WMOS) is a COTS package that provides warehousing functions within DeCA Central Distribution Centers (CDCs). It currently provides oversight, visibility, and functionality for warehouse supply chain management and product inventory at two OCONUS warehouse central distribution centers located at Kaiserslautern Cold Storage (KCS), Germersheim (GER), both in Germany. Vocollect hardware and software products have already been incorporated with the WMS system solution. currently in the two CDCs named and with this new procurement Vocollect will be implemented into other CDC’s. The hardware purchase of Vocollect products are necessary to continue to utilize the capabilities provided to the CDC’s locations in DeCA.

4. Objectives: The Defense Commissary Agency seeks to add a warehouse management operating system implemented within a Software as a Service (SaaS) FEDRAMP moderate environment. The WMOS solution will support’s all of DeCA’s Functional and Technical required capabilities to include CDC suggested Ordering (CDC Replenishment), seamless integration for Radio Frequency (RF), voice-picking devices and all required interfaces with other DeCA’s Business systems providing automated warehouse capabilities for all of CDCs and geographical separated areas. The deployment of this Solution currently supports DeCA’s Germany region, Guam and will be deployed to support Korea Region CDC’s during Q4 FY23. DeCA has a critical need to add the agency’s remaining Japan Region CDCs, into other DeCA operational areas where warehouse operations are required in support geographic separated commissary operations and procure a purchasing/replenishment capability within these defined warehouse operational areas. Currently, the CDC’s in the Germany region, Guam and Korea Region have either implemented or will have implemented the WMS 2020 Software as a Solution (SaaS) FedRAMP Authorized Solution by 29 September 2023.

The Vocollect hardware and software purchase and maintenance are required in support of WMS. The hardware purchase consists of new A720voice devices and its associated software and hardware support to configure, test, and provide training is essential.

5. Scope. The Contractor shall provide all personnel, supervision, management, and non-personal technical services required to deploy a warehouse management operating system implemented within a SaaS FEDRAMP environment which support all of DeCA’s Functional and Technical required capabilities to include seamless integration for RF and voice-picking devices and all required interfaces with other DeCA’s Business systems providing automated warehouse capabilities for DeCA’s CDCs.

6. Performance Requirements.

6.1 COTS Software Package

6.1.1 WMOS Functional Specifications – The contractor shall provide the same capability-based solution and lever of support and maintenance for all functional capabilities of the current fielded FedRAMP WMOS SaaS solution. Functional and technical requirements are outlined in the below areas

6.1.2 Supply Chain Intelligence - Equips warehouse managers and supervisors with analytic reporting tool in a set of pre-configured reports; the tool allows managers and supervisors to create their own reports and queries.

6.1.3 Technical Specifications – The contractor shall continue to provide and meet all technical capabilities of the currently deployed FedRAMP WMOS SaaS Solution. The contractor will provide and meet all technical capabilities for redundant tunnels from DeCA east and west coast data centers and provide failover capabilities using BGP routing

6.1.3.1.1 The contractor shall provide technical support for network configuration and routing

6.1.3.1.2 The contractor shall provide technical support and any required interface development with other DeCA Business systems

6.1.3.1.3 The contractor shall provide updated diagrams to reflect any changes to technical implementation.

6.1.3.1.4 The contractor shall provide technical assistance in supporting the Manhattan WMOS SaaS Solution.

6.1.3.1.5 The Contractor shall provide data conversion functionality to allow conversion of two production databases to the new solution

6.1.3.1.6 The contractor must ensure the RF-HHT functionality is supported on handheld devices specified by DeCA

6.1.3.1.7 The contractor will ensure Voice Picking functionality are supported on devices specified by DeCA

6.1.3.1.8 The contractor shall provide technical solutions support SCI report development

6.1.3.1.9 The contractor will ensure the solution is supportable on one or more of DeCA’s web browsers (Microsoft Edge, Google Chrome and Firefox)

6.1.3.1.10 The contractor shall provide technical consulting for issues involving the Warehouse Solution

6.1.4 The Contractor shall provide licenses and software support for the DeCA’s CDC sites and for 50 site specific concurrent users. The contractor shall provide an environment to allow for the testing and access of DeCA designated Subject Matter Experts (SMEs) for testing and training of the FedRAMP WMOS SaaS solution. The Contractor shall engage with DeCA SME(s) throughout the migration of the WMOS solution to a SaaS environment. The Contractor shall provide automated testing capabilities with the capability to provide and produce artifacts on test results.

6.1.5 The contractor shall provide licenses and software maintenance for Vocollect including product upgrades to include both major scheduled software releases and periodic incremental releases and patches to add minor functionality, resolve software bugs or security issues. The contractor shall provide test bed licenses to be used exclusively for application testing and evaluation. In addition to the installation of these licenses on the primary production servers, the vendor shall allow the installation of these licenses on secondary standby servers to support application failover and Continuity of Operations (COOP).

6.1.6 The contractor shall provide description of any upgrade, release or patch along with installation instructions and scripts needed for installation and verification the upgrade, release or patch was installed successfully. The contractor shall warrant all COTS software and modifications to COTS software developed under this contract. This warranty shall apply to software developed to maintain existing operational baselines as well as any software developed in support of new requirements.

6.1.7 The Contractor shall provide product support and upgrades to include both major scheduled software releases and periodic incremental releases to add minor functionality or resolve software bugs that do not operate per the required technical and functional specifications. All of the product support and upgrades outlined above will be included in the software support cost.

6.1.8 The Contractor shall provide a warranty for all COTS software and modifications to COTS software developed under past contracts with DeCA. This warranty shall apply to software developed to maintain existing operational baselines as well as any software developed in support of new requirements.

6.1.9 All materials provided by the contractor under this contract become the property of the Federal Government. All software/code purchased, provided, written, or developed under this contract for the use of Federal Government, becomes the property of the Federal Government. In the monthly status report, the contractor shall document the purchase, use, transfer, and destruction of all Government provided or Contractor-acquired property.

6.1.10 The Federal Government (DeCA) shall retain ownership of all operational data within the WMOS environments (Test and Production,). The Federal Government shall retain its data rights of all data produced, utilized, updated, populated and/or maintained under this contract.

6.2 Software Maintenance and Support Services

6.2.1 The Government will provide Level I support through the DeCA Enterprise Service Desk (DESD). Level I support consists of a 24 x 7 Service Desk, logging of problems within the Service Desk ticketing system (Remedy) and establishing priority, providing problem resolution for recurring/minor problems such as printer, PC, network, or RF-handheld malfunctions, and escalating problems to Level II support when required.

6.2.2 The Contractor shall provide Level II support for all software acquired through this contract. The contractor shall resolve problems that are of a complex nature with available troubleshooting tools and expert knowledge of the system. Typical problems resolved by Level II support include, but are not limited to, solving application problems or providing pre-approved workarounds to solve the problems, researching status on files, restaging and processing files, and resolving minor database problems.

6.2.3 The Contractor shall provide Level III support for systems identified within this PWS. The contractor shall resolve any problems reported on the system. The Contractor shall resolve and/or provide an approved and implemented successful workaround within 6 hours for all emergency problems and/or high priority or critical (P1) tickets.

6.2.4 The Contractor shall maintain a 24-hour, 7 days per week, 365 days per year call support center to provide operational support to users worldwide (CONUS and OCONUS).

6.2.5 The Contractor shall establish a continuous telephone service within the United States to provide DeCA the ability to report problems 24 hours per day.

6.2.6 The Contractor shall answer and provide a live response to all incoming calls within forty-five (45) seconds. All call center personnel responding to DeCA queries shall speak, write, and understand English.

6.2.7 The Contractor shall respond to system problems using a problem priority process. The internal DeCA Help Desk will establish a priority for each problem upon entry into the DeCA Remedy system. DeCA Program Management Office (PMO) has established the following priority classification and response times for mission essential systems:

P1 MISSION ESSENTIAL (CRITICAL)

· DC cannot process orders and/or Financial Accountability is at Risk

· Response Time: 15 minutes

· Resolution Time: 6 hours

P2 USER ESSENTIAL (HIGH)

· Individuals cannot perform their job responsibilities

· Response Time: 2 hours

· Resolution Time: 18 hours

P3 GENERAL ISSUES (MEDIUM)

· Job responsibilities cannot be performed, but an alternative is available

· Response Time: 4 hours

· Resolution Time: 36 hours

P4 INQUIRIES, QUESTIONS, AD-HOC REPORTS (LOW)

· Non-Production System Support

· Response Time: 24 hours

· Resolution Time: 72 hours

6.3 Configuration Management Support

6.3.1 The Contractor shall provide documentation for all software installation and configuration change procedures.

6.3.2 The Contractor shall provide a Software Version Description Document detailing the content of all software releases to include any scripts, codes, applications and/or programs that change the software baseline.

6.3.3 The Contractor shall follow and support the DeCA IT Technical Review Process for Information Systems. The Contractor will work with the DeCA point of contact to ensure all system changes requests are submitted through this process with the appropriate documentation. The Contractor shall ensure that all systems change requests (CRs) have been developed and tested at the COTS provider’s site. The COTS provider shall document and produce findings on all testing and quality assurance (QA) performed. After successful testing and QA and a review conducted of evidence produced to substantiate successful testing and QA via screen prints or output from the application, the patch or modification will be installed on the production environment.

6.3.4 The Contractor shall maintain the current application baseline to match the DeCA production environment, which will be base-lined and documented upon completion of the migration. Once the WMOS SaaS migration are complete, the Contractor shall maintain the baseline within the WMOS SaaS environment(s) (Pre-Production and Production). All changes to the DeCA production environment, the vendor’s development environment and/or vendor’s SaaS environment shall be documented and tested.

6.3.5 The Contractor shall provide all programs, processes, menus, screens, loading and implementation instructions, user documentation, user guides and any other information pertinent to releasing the changes to the operational baselines (including patches and scripts that produce a configuration change).

6.3.6 The Government will provide a personal computer with VPN access to the DeCA network and any applicable servers required.

6.4 Technical, Functional and User Training

6.4.1 The contractor shall provide Functional training for up to ten users on the WMS SaaS Solution. The training shall be provided at DeCA Headquarters in Ft Gregg-Adams, Virginia or at an mutually agreed to location.

6.4.2 The contractor shall provide operational user manuals and support documentation.

6.5 Operational System Support

6.5.1 The contractor shall install, configure, and test the integration of the Vocollect hardware and software with the Warehouse Management System (WMS) without major errors.

6.5.1.1 The contractor shall install, configure, and test the Vocollect hardware devices.

6.5.1.2 The contractor shall install, configure, and test the Vocollect software on the Vocollect hardware.

6.5.1.3 The contractor shall verify Vocollect hardware and software is installed, configured and integrated with WMS without major errors.

6.5.2 The contractor shall provide product training and documentation on the Vocollect hardware and software.

6.5.3 The Contractor shall provide testing and verification support of the Vocollect hardware and software within test environment.

6.5.4 The contractor shall provide deployment support for the Vocollect hardware and software and verify new components are functioning properly in production

6.6 Operational System Support

6.6.1 The Contractor shall identify any new software, including any third-party software, needed to sustain the WMOS Solution.

6.6.2 The contractor shall provide support in tuning of the WMOS application to include but not limited to database instance(s), application settings/parameters, operating systems, server settings, client computing settings, and network tuning parameters to achieve optimum performance.

6.6.3 The contractor shall test operating system, Information Assurance Vulnerability Alerts (IAVAs), and database upgrades in their development environment and identify/mitigate issues prior to production environment upgrades. The contractor shall assist the PMO in maintaining Information Assurance Vulnerability Management (IAVM) compliance and documenting mitigation plans as required.

6.6.4 The Contractor shall provide remote system support for analysis and troubleshooting for maintaining a healthy system.

6.6.5 The Contractor shall utilize the Information System Contingency Plan (ISCP) template provided by DeCA that adheres to the NIST SP 800-53 policies and procedures to provide a NIST SP 800-53 plan that addresses failover, disaster recovery (DR), duration and timing for data and system restoration from a backup, and Continuity of Operations (COOP) integration and implementation for the WMOS SaaS environments. The Contractor shall support annual DR and COOP tests and/or exercises to ensure data retention, data restoration and continued operations of the WMOS solution.

6.6.6 The Contractor shall develop, implement and provide artifacts and/or technical documentation for its Backup and Recovery (BAR) processes and procedures to mitigate and avoid data loss, improve data recovery, performance redundancy and enhance storage capacity efficiency within the WMOS SaaS environment.

6.6.7 The Contractor shall provide and update software release documentation for all patches, upgrades, and versions delivered to the Government.

6.6.8 The Contractor shall assist the DeCA IA PMO in resolving any issues during the security testing and evaluation phase to ensure successful completion of the DoD Risk Management Framework (RMF).

6.6.9 The Contractor shall support testing and validation for all patch updates (including DoD mandated security patches) for operating systems, databases, third party, and embedded software for all certified releases of the WMOS products within 30 days of notification or by the DoD mandated response date whichever comes first. The DoD issues Information Assurance Vulnerability Alerts (IAVAs) for all systems.

6.6.10 The Contractor shall adhere to the DoD and DeCA Information Assurance Requirements Compliance and Support Procedures, and the Public Key Infrastructure policies for software implementation and support. http://www.dtic.mil/whs/directives/corres/pdf/852002p.pdf

6.6.11 The Contractor shall prepare impact analysis and detailed cost estimates associated with System Changes request (SCR) when requested by the COR within 10 business days of request.

6.6.12 The Contractor shall provide documentation for all metadata and data models. The documentation provided shall include detailed information such as all table names, relationships, columns and column attributes (including business names, definitions, data types, and sizes), logical and physical data models. The Contractor shall ensure that DeCA receives updates for metadata and data models as required throughout the lifecycle of the products.

6.6.13 The Contractor is solely responsible for connectivity to the DeCA network and its SaaS environment. The Contractor shall coordinate and ensure DeCA’s connectivity to its SaaS environment and address any connectivity issues impeding and/or prohibiting DeCA’s access

6.7 Program Management

6.7.1 The Contractor shall provide technical specifications for hardware and software, including any third-party software, needed to sustain the WMOS solution.

6.7.2 The contractor shall submit written monthly status reports on tasks performed during the contract’s period of performance. In addition, the status report shall include a summary of maintenance support activities and possible risks or issues.

6.7.3 Site Survey and Trip Reports - Trip reports for all employees travelling on behalf of the Government shall be delivered to the COR within 10 business days after trip is completed. The contractor shall determine the trip report format; however, the report should include at a minimum a brief summary of the trip and a description of the goals and accomplishments completed. Travel shall be authorized, in writing, by the Government prior to performance.

6.7.4 Program Management Review - The contractor shall perform a quarterly Program Management Review (PMR). The Contractor shall prepare and submit a Microsoft PowerPoint presentation that details schedule, cost, baseline, issues and risks to the COR and PM ten (10) business days prior to the scheduled PMR. The location of PMR meetings will be either at DeCA HQ Ft. Gregg-Adams, the contractor’s site, a third-party location, or conducted via Video Teleconference (VTC). The Contractor is responsible for taking the PMR meeting minutes.

6.7.5 The Contractor shall provide assistance to create the required documents and/or artifacts required to support DeCA Program Management Office (PMO) efforts to obtain and maintain FedRAMP certification of its WMOS solution and complete the required FedRAMP 3PAO assessment.

6.8 Test and Evaluation

6.8.1 System Testing. The Contractor shall perform WMOS testing and evaluation of the software and all upgrades and patches prior to delivery to the Government to support the Government’s internal testing and production release procedures and processes. The Contractor shall document all Test Cases in a Test Plan. The Contractor shall provide automated testing and the capability to generate ad hoc report and Test Reports from the system and/or application that will include Test Results prior to delivery to the Government.

6.9 Information Assurance

6.9.1 The WMOS FedRAMP certified SaaS Solution shall comply with DoD FedRAMP requirements. The Solution shall also comply with standards in applicable Defense Information Systems Agency (DISA) Security Technical Implementation Guidelines (STIG) and checklists and must be maintained within the same FedRAMP SaaS environment.

6.9.2 The contractor shall assist DeCA in the generation of all documentation to maintain all required FedRAMP accreditation and support under the RMF process.

6.9.3 The WMOS shall comply with the use of public key infrastructure technology for authentication in accordance with DoD guidelines. Web servers hosting data that is not approved for release outside of the Government shall use Secure Sockets Layer (SSL) for access and public key certificates to authenticate users. If WMOS relies on DeCA’s Active Directory to authenticate system users, then the systems shall be compatible with DeCA’s smart card logon solution.

6.9.4 Contractors with access to the DeCA network shall comply with smart card logon requirements. The contractor shall support DeCA in the secure distribution, management, and disposal of credentials or tokens used by remote contractors for access to the DeCA network.

6.9.5 Contractors with access to Government computer systems shall meet the requirements of DoD 5200.2-R as implemented by DeCA and receive a favorable background investigation commensurate with their level of system access. This includes designating each contractor to an IT position category (i.e. IT-I, IT-II, or IT-III) based on their level of access and in accordance with DeCA criteria. DoD 5200.2-R can be found on the World Wide Web at the following link: http://www.dtic.mil/whs/directives/corres/pub1.html.

6.9.6 The contractor shall review DoD and DeCA system security requirements and document all exceptions to the standard settings required for the WMOS. Exceptions are only allowed if they are approved by the DeCA Designated Accrediting Authority (DAA).

6.9.7 DeCA shall be allowed access to any offsite contractor-operated systems that process, transmit, or store DeCA information for the purposes of evaluating the security compliance. Activities will include, but are not limited to, scanning and interviews.

6.9.8 Contractor will comply with 8570.01-m, Workforce Improvement Program, as required (See 12.4).

6.9.9 Contractor shall comply with all United Stated Department of Defense Instructions and Directives unless directed otherwise by Contracting Officer. DOD Instructions and Directives can be found at the following link: http://www.dtic.mil/whs/directives/index.html

6.10 Operational Sustainment Support

6.10.1 The contractor shall provide for the cost required to perform software upgrades, any software and hardware fixes that are not covered under the software or hardware support.

6.11 Cloud based Software as a Services Solution

6.11.1 DeCA requires a FedRAMP Cloud based SaaS solution and services to support CDC capabilities in processing all incoming shipments, verifying order accuracy, managing warehouse operations, optimizes picking, and providing pallet size, weight, and cube routing information. Also included in the system are software license, software configuration, development, and delivery; system and data conversion; documentation; installation, and de-installation; testing; training; disaster preparedness and business continuity; hardware and software maintenance; system administration; 24x7 help desk (excluding Tier 1, performed through DeCA’s Enterprise Service Desk); consulting services; and program management. CDC operations in utilizing an automated warehouse solution directly affects every commissary that relies on a CDC to keep its shelves stocked. It incorporates grocery industry best practices in reading and processing European Article Numbers and Japanese Article Numbers and voice picking technology. DeCA requires the warehouse solution to perform at a minimum five primary business functions described below within the CDC:

(1) CDC Replenishment - CDC must have the capability to create suggested orders to replenish items for the CDC. The suggested ordering will need to take into consideration historical ordering data, Promotional, seasonal/holiday items, past bulk ordering for Sales.

i. The solution shall generate a suggested order and allow the user to modify ordering based on required projected needs.

ii. The solution shall have the capability to separate warehouse orders and promotional orders in due-in quantity.

iii. The solution shall have the capability to differentiate orders from warehouse due-ins such as promotions, cross dock, and stor special requests.

iv. The solution shall provide the capability to have adjustable lead times by CDC locations

v. The solution shall provide the capability to account for and provide consumption history

vi. The solution shall provide item level flagging:

1. Prioritize and review problematic items/swap, replacement item links/new items, and high interest items.

2. Flag items for ordering as case, layer, pallet, and source load. Recommended/pending order rounded to nearest

3. Shelf-life/salvage caution flags per item.

4. Order filtering: commodity, regular and special location assignments, flag items as regular order and do not order

vii. Build order lists options by sorting delivery frequency, commodity code, vendor, and warehouse items vs non-warehouse items

viii. The solution shall have the capability to import and export data to text or spreadsheet format

ix. The solution shall allow generation of reports

x. The solution shall provide capability to display status and history of orders and it shall be able to be sort

xi. The solution shall provide projected Balance on Hand (BOH) at the time of order arrival for current order build

xii. The solution shall provide projected pending order quantity sustainment in weeks or days at the time of arrival

xiii. The solution shall provide item by item product turnover ratio.

xiv. The solutions order UI shall display RSL code, DF code, warehouse location, Tie/Tier and Vendor

(2) Inbound Management

i. Receiving - CDC workers use radio frequency (RF) handhelds to inventory inbound shipments.

ii. Put away - CDC workers store palletized products, input product location, and manage the internal operations of the CDC, using RF handhelds.

(3) Inventory Management

i. Physical and Cyclic Inventory - CDC workers physically count all of the products in each warehouse location. Cyclic inventories are performed under normal warehouse operations without freezing locations. CDC workers cycle count inventory by checking product locations to identify and correct discrepancies between current inventory in the WMOS and actual physical inventory.

ii. Quality Control - CDC workers inspect merchandise being received or shipped to ensure that it is of adequate quality and that the LPN content specification is accurate.

(4) Task Management – Warehouse management solution generates warehouse worker tasks and enables management to prioritize the sequence of CDC activities in English, German, Japanese, or Korean to optimize workload efficiency.

(5) Outbound Distribution

i. Replenishment - CDC workers move item inventory from a reserve storage location to the primary picking location or to another mode of storage from which picking is performed.

ii. Picking & Shipping – Voice picking directs CDC workers in English, German, Japanese, or Korean to identify product locations in the warehouse, pick inventory against store orders, and ship the picked inventory to requesting stores.

6.11.2 VoCollect/Voice Picking – The contractor shall provide support deploying DeCA’s voice picking capabilities. The devices DeCA utilizes to provide these capabilities are included within this contract, as capabilities are tightly coupled between the software and the devices. During deployment into the CDC’s the contractor shall provide support to integrate and allow for the voice picking solution.

6.11.2.1 The contractor shall provide a VoCollect implementation plan.

6.11.2.1.1 Manhattan will support deployment of the voice solution. Support of the Honeywell Vocollect voice solution deployment and operation of the Voice Console server in the ManhGov Cloud environment is dependent on the acquisition of Vocollect hardware and software support through Manhattan Associates or one of our partners. If another vendor is chosen to procure and support the Vocollect solution, the ManhGov Cloud SaaS solution can continue to support voice picking capabilities. However, Vocollect device deployment, device configuration, hosting of the Voice Console servers, configuration of the Voice Console servers, associated software updates, and overall support would be a responsibility of the other vendor. The existing Honeywell Vocollect support contract is through Manhattan Associates. If this were to be changed to another vendor, a contract change would be required to remove hosting of the Voice Console servers and overall voice support from this contract

6.11.3 Supply Chain Intelligence - Equips warehouse managers and supervisors with analytic reporting tool in a set of pre-configured reports; the tool allows managers and supervisors to create their own reports and queries. The contractor shall create and provide up to 6 customized reports based on the operational requirements.

6.11.4 If delays to the approved deployment schedule agreed to by the contractor and DeCA are exceeded not directly related to the contractor’s performance, the contractor shall provide additional support are required by DeCA.

6.12 Deliverable/Delivery Schedule

6.12.1 Delivery of computer programs, specifications, technical reports, progress/status reports, and any other data shall be in accordance with the following table and outlined sections within the PWS. All deliverables under this contract shall become the property of the Government. The Government shall retain all rights to the data within the current WMOS solution and the upgraded FEDRAMP SaaS WMOS solution.

Deliverables

Survey Results

*Standard Distribution: 1 copy of the transmittal letter with the deliverable to the Primary and Alternate Task Managers at Jeffrey.Cook@deca.mil, and Johanna.Rowe@deca.mil. *Deliverable may be submitted in contractor format unless otherwise specified.

*Written documents should be in Microsoft Word 2013 (or later).

*Project schedule should be submitted in Microsoft Project 2013 (or later).

7. Performance Standards.

WMS and Replenishment Implementation Plan

Survey Results

Provide testing and verification support of the Vocollect hardware and software within test environment.

8. Incentives. Incentives are not part of this contract. Failure to perform work agreed that is within scope of the contract will result in payment being withheld.

9. Place of Performance.

Mission Location: The contractor shall perform work at the contractor’s site using remote access from Government provided workstations. The Contractor may be required to provide on-site support at DeCA Headquarters location.

Place of Performance: The contractor shall perform work at the contractor’s site using remote access from Government provided workstations. The Contractor may be required to provide on-site support at DeCA Headquarters location.

Local travel to and around the mission location or place of performance. Long distance travel within CONUS or OCONUS may be required to support the requirements of this PWS. Travel within CONUS and OCONUS must be pre-approved in writing by the COR prior to the Contractor incurring the cost in support of this contract.

Secondary Place of Performance – Contingency Only. As determined by the Contracting Officer’s Representative (COR), contractor employees may be required to work at a secondary place of performance (e.g., home, the contractor's facility, or another approved activity within the local travel area) in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, government closure due to inclement weather). Additionally, the contractor may be required to account for the physical location of their personnel should this information be requested by the COR. Non-emergency/non-essential contractors should not report to a closed government facility. Contractor shall prepare all deliverables and other contract documentation utilizing contractor resources. To the extent possible, the contractor shall use best efforts to provide the same level of support as stated in the PWS. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer or the contractor may request an equitable adjustment pursuant to the Changes clause of the contract.

10. Period of Performance.

The base period of performance (POP) will be for a period of 12 months beginning at contract award, with four 1-year options as follows:

· Base Year:

CLIN 0001: Warehouse Management Operating Solution (WMOS), Design, Build and Deploy Phases - Japan Sites Deployments

· PoP: 30 September 2023 – 29 September 2024 CLIN 0002: WMOS – Travel

· PoP: 30 September 2023 – 29 September 2024 CLIN 0003: WMOS Replenishment Module Design Validation and Customization

· PoP: 30 September 2023 – 29 September 2024 CLIN 0004: WMOS Replenishment Module Testing

· PoP: 30 September 2023 – 29 September 2024 CLIN 0005 WMOS Replenishment Module Training

· PoP: 30 September 2023 – 29 September 2024 CLIN 0006 Replenishment Module - Implementation

· PoP: 30 September 2023 – 29 September 2024 CLIN 0007: Replenishment Travel - Design/Test

· PoP: 30 September 2023 – 29 September 2024 CLIN 0008: Replenishment Travel - Implementation

· PoP: 30 September 2023 – 29 September 2024 CLIN 0009: WMOS and Replenishment Module - SaaS Subscription

· PoP: 30 September 2023 – 29 September 2024 CLIN 0010 (OPTIONAL): WMOS - Functional Training Class - Fort Gregg-Adams, Virginia - 10 Super-users for 5 days (Japan)

· PoP: 30 September 2023 – 29 September 2024 CLIN 0011 (OPTIONAL): WMOS - Functional Training Class - Fort Gregg-Adams, Virginia - 10 Super-users for 5 days (Geographic Separated Sites)

· PoP: 30 September 2023 – 29 September 2024 CLIN 0012 (OPTIONAL): WMOS - Site Specific Configuration - Japan Region

· PoP: 30 September 2023 – 29 September 2024 CLIN 0013 (OPTIONAL): WMOS - Site Specific Configuration - Geographic Separated Sites

· PoP: 30 September 2023 – 29 September 2024 CLIN 0014 (OPTIONAL): WMOS - SCI Report Development

· PoP: 30 September 2023 – 29 September 2024 CLIN 0015 (OPTIONAL): WMOS - Additional Monthly Support - Minimal Support

· PoP: 30 September 2023 – 29 September 2024 CLIN 0016 (OPTIONAL): WMOS - Additional Monthly Support - Full Support

· PoP: 30 September 2023 – 29 September 2024 CLIN 0017 (OPTIONAL): Upgrade Deployment and Change Management Assistance

· PoP: 30 September 2023 – 29 September 2024 CLIN 0018 (OPTIONAL): Software Extension and Customization

· PoP: 30 September 2023 – 29 September 2024 CLIN 0019: VoCollect - DeCA HQ - Hardware

· PoP: 30 September 2023 – 29 September 2024 CLIN 0020: VoCollect - DeCA HQ - Software

· PoP: 30 September 2023 – 29 September 2024 CLIN 0021: VoCollect - DeCA HQ - Shipping

· PoP: 30 September 2023 – 29 September 2024 CLIN 0022: VoCollect - KCS CDC- Hardware

· PoP: 30 September 2023 – 29 September 2024 CLIN 0023: VoCollect - KCS CDC- Software

· PoP: 30 September 2023 – 29 September 2024 CLIN 0024: VoCollect - KCS CDC- Shipping

· PoP: 30 September 2023 – 29 September 2024 CLIN 0025: VoCollect - GERM CDC - Hardware

· PoP: 30 September 2023 – 29 September 2024 CLIN 0026: VoCollect - GERM CDC - Software

· PoP: 30 September 2023 – 29 September 2024 CLIN 0027: VoCollect - GERM CDC - Shipping

· PoP: 30 September 2023 – 29 September 2024 CLIN 0028: VoCollect - Guam CDC- Hardware

· PoP: 30 September 2023 – 29 September 2024 CLIN 0029: VoCollect - Guam CDC - Software

· PoP: 30 September 2023 – 29 September 2024 CLIN 0030: VoCollect - Guam CDC - Shipping

· PoP: 30 September 2023 – 29 September 2024 CLIN 0031: VoCollect - Korea Region CDCs - Hardware

· PoP: 30 September 2023 – 29 September 2024 CLIN 0032: VoCollect - Korea Region CDCs- Software

· PoP: 30 September 2023 – 29 September 2024 CLIN 0033: VoCollect - Korea Region CDCs- Shipping

· PoP: 30 September 2023 – 29 September 2024 CLIN 0034: VoCollect – Manhattan - Hardware

· PoP: 30 September 2023 – 29 September 2024 CLIN 0035: VoCollect – Manhattan - Shipping

· PoP: 30 September 2023 – 29 September 2024 CLIN 0036: VoCollect - Japan Region CDCs - Hardware

· PoP: 30 September 2023 – 29 September 2024 CLIN 0037: VoCollect - Japan Region CDCs - Software

· PoP: 30 September 2023 – 29 September 2024 CLIN 0038: VoCollect - Japan Region CDCs - Shipping

· PoP: 30 September 2023 – 29 September 2024 CLIN 0039: VoCollect On-Site Support and Translation

· PoP: 30 September 2023 – 29 September 2024 CLIN 0040 (OPTIONAL): Design, Build and Deploy Phases - Geographic Separated Sites Deployments

· PoP: 30 September 2023 – 29 September 2024 CLIN 0041 (OPTIONAL): WMOS - Geographic Separated Sites - Travel

· PoP: 30 September 2023 – 29 September 2024

· Option Year 1:

CLIN 1001: WMOS - SaaS Subscription (including all annual upgrades) - Germany Region, Guam and Korea Region

· PoP: 30 September 2024 – 29 September 2025 CLIN 1002: WMOS - SaaS Subscription (including all annual upgrades) - Japan Region

· PoP: 30 September 2024 – 29 September 2025 CLIN 1003: WMOS - SaaS Subscription (including all annual upgrades) - Geographic Separated Sites (2 Sites

· PoP: 30 September 2024 – 29 September 2025 CLIN 1004: Design, Build and Deploy Phases - Geographic Separated Sites Deployments

· PoP: 30 September 2024 – 29 September 2025 CLIN 1005: WMOS - Travel

· PoP: 30 September 2024 – 29 September 2025 CLIN 1006: WMOS - Functional Training Class - Fort Lee, Virginia - 10 Super-users for 5 days (Geographic Separated Sites)

· PoP: 30 September 2024 – 29 September 2025 CLIN 1007: WMOS - SCI Report Development

· PoP: 30 September 2024 – 29 September 2025 CLIN 1008: WMOS - Additional Monthly Support - Minimal Support

· PoP: 30 September 2024 – 29 September 2025 CLIN 1009: WMOS - Additional Monthly Support - Full Support

· PoP: 30 September 2024 – 29 September 2025 CLIN 1010: Replenishment Module - SaaS Subscription (including all annual upgrades)

· PoP: 30 September 2024 – 29 September 2025 CLIN 1011: Annual Maintenance

· PoP: 30 September 2024 – 29 September 2025 CLIN 1012: Misc. Accessories and Consumables (Earpads, Mic Caps, etc)

· PoP: 30 September 2024 – 29 September 2025 CLIN 1013: Travel

· PoP: 30 September 2024 – 29 September 2025

· Option Year 2:

CLIN 2001: WMOS - SaaS Subscription (including all annual upgrades) - Germany Region, Guam and Korea Region

· PoP: 30 September 2025 – 29 September 2026 CLIN 2002: WMOS - SaaS Subscription (including all annual upgrades) - Japan Region

· PoP: 30 September 2025 – 29 September 2026 CLIN 2003: WMOS - SaaS Subscription (including all annual upgrades) - Geographic Separated Sites (up to 5 Sites)

· PoP: 30 September 2025 – 29 September 2026 CLIN 2004: Replenishment Module - SaaS Subscription (including all annual upgrades)

· PoP: 30 September 2025 – 29 September 2026 CLIN 2005: Annual Maintenance

· PoP: 30 September 2025 – 29 September 2026 CLIN 2006: Misc. Accessories and Consumables (Earpads, Mic Caps, etc)

· PoP: 30 September 2025 – 29 September 2026 CLIN 2007: Travel

· PoP: 30 September 2025 – 29 September 2026

· Option Year 3:

CLIN 3001: WMOS - SaaS Subscription (including all annual upgrades) - Germany Region, Guam and Korea Region

· PoP: 30 September 2026 – 29 September 2027 CLIN 3002: WMOS - SaaS Subscription (including all annual upgrades) - Japan Region

· PoP: 30 September 2026 – 29 September 2027 CLIN 3003: WMOS - SaaS Subscription (including all annual upgrades) - Geographic Separated Sites (up to 5 Sites)

· PoP: 30 September 2026 – 29 September 2027 CLIN 3004: Replenishment Module - SaaS Subscription (including all annual upgrades)

· PoP: 30 September 2026 – 29 September 2027 CLIN 3005: Annual Maintenance

· PoP: 30 September 2026 – 29 September 2027 CLIN 3006: Misc. Accessories and Consumables (Earpads, Mic Caps, etc)

· PoP: 30 September 2026 – 29 September 2027 CLIN 3007: Travel

· PoP: 30 September 2026 – 29 September 2027

· Option Year 4:

CLIN 4001: WMOS - SaaS Subscription (including all annual upgrades) - Germany Region, Guam and Korea Region

· PoP: 30 September 2027 – 29 September 2028 CLIN 4002: WMOS - SaaS Subscription (including all annual upgrades) - Japan Region

· PoP: 30 September 2027 – 29 September 2028 CLIN 4003: WMOS - SaaS Subscription (including all annual upgrades) - Geographic Separated Sites (up to 5 Sites)

· PoP: 30 September 2027 – 29 September 2028 CLIN 3004: Replenishment Module - SaaS Subscription (including all annual upgrades)

· PoP: 30 September 2027 – 29 September 2028 CLIN 4005: Annual Maintenance

· PoP: 30 September 2027 – 29 September 2028 CLIN 4006: Misc. Accessories and Consumables (Earpads, Mic Caps, etc)

· PoP: 30 September 2027 – 29 September 2028 CLIN 4007: Travel

· PoP: 30 September 2027 – 29 September 2028

11. Security Requirements. The contractor shall coordinate site visits with site POCs at least 72 hours prior to requiring any site access. Contractor personnel without security clearances performing any task under this PWS must be escorted by Government personnel who are cleared.

This section shall be considered a supplement to Block 13 of the Government provided DD Form 254, DoD Contract Security Classification Specification. The following security requirements shall apply to this effort.

References:

a. DISA End User Access Agreement, 11 February 2021

b. DISA Policy Letter, Unauthorized Connections to Network Devices, 11 September 2013

c. DISA Instruction 240-110-8, Information Security

d. DISA Instruction 240-110-36, Personnel Security

e. DISA Instruction 240-110-38, Industrial Security

f. DISA Instruction 240-110-43, Insider Threat Program

g. DISA Instruction 630-230-19, Cybersecurity

h. DoD Manual 5200.01, Vol 1-3 Information Security Program, 24 February 2012

i. DoD Manual 5200.02, Procedures for the DoD Personnel Security Program, 3 April 2017

j. DoD Instruction 5200.48, Controlled Unclassified Information (CUI), 6 March 2020

k. DoD 5220.22-M, National Industrial Security Program Operating Manual, February 2006 Incorporating Change 18 May 2016

l. 32 CFR Part 117, “National Industrial Security Program Operating Manual (NISPOM”, 24 February 2021

11.1 Facility Security Clearance. The work to be performed under this contract/order is at the sensitive but unclassified level. All Contractors’ employees while working at a Government facility, shall conspicuously display on their person a badge, which shall include the full name of the employee, and the legal name under which the Contractor is doing business.