ATTACHMENT 5 - SOW - MARKET DIRECT.pdf

CUI

Statement of Work (SOW) for COTS Software License

CUI | Source Selection Information – See FAR 2.101 & 3.104 1

1. Introduction

This Statement of Work is for the Enterprise Version 14.2 or higher of eProductivity Software (ePS) Market

Direct StoreFront (MDSF) COTS product, the Fulfillment Module (Print FF), and Technical Services required by DLA Document Services to both meet the needs of specific projects and continue to upgrade and utilize MDSF at the scale and security posture required by the Government.

1.1. Background

Defense Logistics Agency (DLA) J62KA Enterprise Data Solutions provides IT application support to DLA Document Services. Document Services provides print broker services that include document reproduction, digital warehousing, electronic output, document conversion, electronic access and other specialty products and services to the Department of Defense (DoD) and federal agencies throughout the world. The Document Services mission is to provide best value document automation and document management solutions worldwide in support of America’s Armed Forces and Federal

Agencies, encompassing the capture, management, access, distribution, and output of digital and hardcopy information.

Document Services uses a J62 support application, Document Services online (DSO) to support their mission. DSO consists of COTS web to print applications and custom integration extensions in support of government unique requirements. The commercial off the shelf (COTS) license is with eProductivity Software (ePSSW) Market Digital Store Front, MDSF. DSO is the bridge for DLA

Document Services as they make the transition from paper-based communication to digital based communication. The DSO platform has been the consolidating platform for streamlining solutions across all of DoD.

An additional module was purchased to manage the warehouse functions of printed forms, managed by the J67 Document Services Tinker Warehouse. This module requires separate line-item maintenance support and is called the Print Fulfillment Module.

2. Period of Performance

The period of performance shall be one (1) 12-month base period with four (4) 12-month option periods.

Base Year: December 21, 2025 to December 20, 2026

Option Year 1: December 21, 2026 to December 20, 2027

Option Year 2: December 21, 2027 to December 20, 2028

Option Year 3: December 21, 2028 to December 20, 2029

Option Year 4: December 21, 2029 to December 20, 2030

3. Scope

The software server licenses’ maintenance will allow the eProductivity Software (ePS) Market Digital Store

Front (MDSF), to maintain current active status as a licensed software, to receive vendor license updates as they are released and to also maintain the ability of multiple and simultaneous users to access the MDSF software. To permit the licensing of 3 different environments development, stage and production. Fulfillment of this requirement is essential to maintaining mission readiness for our customers’ daily usage of this software’s capabilities in support of their ongoing daily work processes and objectives. Licensing and enabling of new modules must use Print ePS’ eFlow integration features and allow for unlimited users and storefronts. This will be a Firm Fixed Price contract. The Government intends to award without discussion;

therefore, offerors will be instructed to submit proposals that contain their best terms.

CUI | Source Selection Information – See FAR 2.101 & 3.104 2

4. Requirements

4.1. Market Direct StoreFront (MDSF) License

This maintenance purchase will provide the DLA J62K with all the necessary access rights and privileges to use the licenses in accordance with their intended purpose. In addition, during the maintenance term, J62K personnel will have access to any vendor web-based support or knowledge database regarding this product and any software updates, patches or upgrades that the vendor issues for these licenses. Moreover, the vendor will provide telephone support and ability to submit trouble tickets or general inquiry questions to a support site. The vendor will provide a website for the government to submit troubleshooting tickets and change requests. Any cybersecurity finds will require a response within 36 hours. The vendor will participate in weekly meetings to coordinate support, project, and maintenance activities.

4.2. Print Fulfillment (Print FF) Module License

This maintenance purchase will provide the DLA J62K with all the necessary access rights and privileges to use the fulfilment module in conjunction with the base MDSF licenses. In addition, during the maintenance term, J62K personnel will have access to any vendor web-based support or knowledge database regarding this product and any software updates, patches or upgrades that the vendor issues for these licenses.

4.3. Technical Support Services

When needed the government shall identify the need to use a portion of the Technical Support hours allocated each year in support of any required assistance. The vendor shall provide that acknowledge of the needed support within 24 hours via email and provide the support within 3 days. Assistance may include troubleshooting, configuration assistance, installation, and training on additional add-ons and modules offered to be bolted on to the basic MDSF application. Hours must be approved by the

DLA COR in advance of expending.

4.4. Technical Project Services: ICAM (New security requirement)

Identity, Credential, and Access Management (ICAM) is a requirement for the overall DSO application currently deployed and supported by J67 and utilized by DLA Document Services.

Support for ICAM will require changes to the COTS product MDSF and likely the extensions. The

Federal Government must be able to identify, credential, monitor, and manage subjects that access

Federal resources, including information, information systems, facilities, and secured areas across their respective enterprises. According to the Enabling Mission Delivery through Improved Identity, Credential, and Access Management memorandum issued May 21, 2019, by the Executive Office of the President.

ePS and MDSF have implemented “single-sign-on” solutions in the commercial space. The implementation of ICAM according to the requirements spelled out by the Federal Government will include unique requirements both due to the specific Government requirements and the scale of the

DSO deployment within DLA Document Services. These unique requirements will require expertise of all the technology components involved (MDSF, how single sign-on has been implemented in commercial settings, and then the unique requirements of DLA). ePS will provide the resources that are skilled in implementing single-sign-on with the required budgeted hours to learn and execute on the unique requirements of DLA Document Services.

CUI | Source Selection Information – See FAR 2.101 & 3.104 3

The implementation of ICAM will occur the Base Year of this contract, the annual maintenance in the follow-on Option Years will include annual maintenance for the continued evolution of ICAM with

DLA Document Services as it pertains to DSO.

ICAM DRAFT Project Plan Project Initiation

Define project scope & objectives

Identify stakeholders & assemble project team

Conduct project kickoff meeting

Requirements & Analysis

Access Provisioning (Obtain OKTA admin access and test accounts)

Define Attributes & Claims (Decide on user attributes (NameID, email, roles, etc.))

Define User Access Roles (Map roles/groups to OKTA for access control)

Gather detailed functional requirements (User Cleanup & Role Definitions)

Document non-functional requirements (performance, security, compliance)

Obtain formal requirements sign-off

Planning & Design

Create high-level solution/architecture design

Develop detailed technical design (data models, module diagrams)

Prepare project schedule & resource plan

Risk assessment & mitigation planning

Development (Implementation)

Set up development environment & branching strategy

Cleanup the existing data

Configure OKTA App (Create new app in OKTA dashboard, configure settings)

Configure MDSF Application (Configure SP side: metadata, URLs, keys)

Break work into iterations/sprints

Coding of core features

Conduct peer code reviews / pull-request approvals

Quality Assurance & Testing

Unit testing completed for all modules

Integration testing of combined components

System testing (end-to-end scenarios-Test SSO login, logout, attribute mapping)

User Acceptance Testing by business stakeholders (Test with real users across roles)

Error Handling & Logging (Ensure proper error messages and audit logs)

Defect triage & resolution cycle

Release Preparation

Build/release candidate packaged and deployed to staging

Perform performance/load testing

Security vulnerability scan & remediation

Final sign-off on release candidate

Deployment & Go-Live

Deploy to production environment

Smoke testing in production

Rollback plan verification

Official “go-live” announcement (Notify end users with instructions & support)

Post-Implementation & Closure

Monitor production for issues (first 24–72 hours) (Confirm usage, review error logs)

Transition to support/operations team

Conduct post-mortem / retrospective (lessons learned)

Formal project closure & documentation handover

Maintenance & Enhancements

Triage & fix production defects

Plan & deliver minor enhancements or patches

Regular system health checks & performance tuning

CUI | Source Selection Information – See FAR 2.101 & 3.104 4

4.5. Technical Project Services: AOE (New mission requirement)

Automated Order Entry (AOE) is a strategy of DLA Document Services to reduce labor, improve efficiencies and deliver print communication products to the war fighter in the most efficient manner possible.

DLA Document Services, as the as the single source of print broker services to the Armed Forces and federal agencies and the primary pathway for billing and funding of print orders into EBS needs a programmatic pathway for entering orders into DSO.

In the past this automated pathway was attempted to be solved using RPA/BOTs. It has been determined that the complexity of the ordering process of print (a custom manufacturing process where the customer provides a key manufacturing component at the time of purchase) and the constant changes occurring on the DSO platform configuration and infrastructure make the use of

BOTS not optimal.

The AOE project is to solve the challenge of automated order entry (programmatically creating orders in DSO so that they are accurately manufactured for the war fighter and accurately billed against proper funding in EBS) using API’s (application programming interfaces) instead of BOTS.

The path to this solution will require an extensive collaboration between DLA Document Services operation, J67 Program Management, and Web2Print Experts, Inc. (the builders of EBS integration and the makers of the Billing Module extension to DSO.

The proposed solution will include require the extension of the existing MDSF API to include DSO specific job specification and funding requirements. This will assure that programmatic order entry meets and matches the requirements of manual order entry by qualified DLA Document Services operations staff.

Presently there are two use cases for the need of automated order entry, Air Force and Navy

Technical Manual print orders. The solution will meet the requirements of these two use cases as well as not limited the solution to ONLY solve for those use cases. Automated order entry will become a tool in the toolbox of DLA Document Services to continue to improve efficiencies, reduce labor costs, and automate their services to the war fighter.

The implementation of AOE will occur the Base Year of this contract, the annual maintenance in the follow-on Option Years will include annual maintenance for the continued evolution of AOE with

DLA Document Services as it pertains to DSO.

AOE DRAFT Project Plan

Project Initiation

Define project scope & objectives

Identify stakeholders & assemble project team

Conduct project kickoff meeting

Requirements & Analysis

Review all documentation

Define and publish desired results / definition of done

Gather detailed functional requirements

Document non-functional requirements (performance, security, compliance)

Obtain formal requirements sign-off

Planning & Design

Create high-level solution/architecture design

Develop detailed technical design (data models, module diagrams)

Prepare project schedule & resource plan

CUI | Source Selection Information – See FAR 2.101 & 3.104 5

Risk assessment & mitigation planning

Development (Implementation)

Set up development environment & branching strategy

Cleanup the existing data

Break work into iterations/sprints

Coding of core features

Conduct peer code reviews / pull-request approvals

Quality Assurance & Testing

Unit testing completed for all modules

Integration testing of combined components

User Acceptance Testing (UAT) by business stakeholders

Error Handling & Logging (Ensure proper error messages and audit logs)

Defect triage & resolution cycle

Release Preparation

Build/release candidate packaged and deployed to staging

Perform performance/load testing

Security vulnerability scan & remediation

Final sign-off on release candidate

Deployment & Go-Live

Deploy to production environment

Smoke testing in production

Rollback plan verification

Official “go-live” announcement

Post-Implementation & Closure

Monitor production for issues (first 24–72 hours) (Confirm usage, review error logs)

Transition to support/operations team

Conduct post-mortem / retrospective (lessons learned)

Formal project closure & documentation handover

Maintenance & Enhancements

Triage & fix production defects

Plan & deliver minor enhancements or patches

Regular system health checks & performance tuning

5. Shipment

All software releases and patches shall be available from the vendors secure ftp/web site for download by the government POC. With each patch and or release shall include release notes and updated documentation.

Documentation shall be available in PDF format.

6. Point of Contacts

Defense Logistics Agency (DLA) J62KAB

6090 Strathmore Rd, Richmond VA 23237-5002

POC: Lionel Henderson

Telephone: (804) 387-5434

E-mail: lionel.henderson@dla.mil

Contracting Activity:

DLA Contracting Services Office – Philadelphia

700 Robbins Avenue, Philadelphia, PA 19111

POC: TBD

Telephone: (000) 000-000

Email: TBD@dla.mil mailto:lionel.henderson@dla.mil mailto:TBD@dla.mil