RFI - DRAFT PWS SAP Platform.pdf

DRAFT PERFORMANCE WORK STATEMENT

Defense Logistics Agency J6 System Application and Products (SAP) Platform Software

Implementation, Development Lifecycle, and Support Services

2.1 BACKGROUND

The Defense Logistics Agency (DLA) is a United States (U.S.) Department of Defense (DoD) agency that provides worldwide logistics support for the missions of the Military Departments and the

Unified Combatant Commands under conditions of peace and war.

The Defense Logistics Agency (DLA), Information Operations (J6), SAP Platform (J62X) services the Enterprise by providing both Commercial Off the Shelf (COTS) and Government proprietary

(GOTS) Automated Information Systems (AIS) lifecycle management. This Task Order outlines the requirements to acquire support services working in conjunction with Government resources for the

Enterprise Business System (EBS) Portfolio, the Distribution Standard System (DSS) and Warehouse

Management System (WMS) Portfolio, the Federal Logistics Information System (FLIS) Portfolio, and the technical divisions supporting those portfolios which include SAP and Non-SAP technical support and compliance support.

The EBS portfolio is responsible for DLA’s Enterprise Business System (EBS) which is a comprehensive, SAP-based enterprise resource planning (ERP) platform that serves as the backbone of DLA’s supply chain and financial operations. EBS supports a wide range of logistics, acquisition, inventory management, and financial functions essential to DLA’s mission of providing global, full-spectrum logistics support to the warfighter and other federal partners. As one of the largest and most complex ERP systems in the Department of Defense, EBS enables end-to-end visibility, integration, and accountability across DLA’s operations. It supports over 25,000 users and processes millions of transactions, facilitating everything from material planning and procurement to distribution, billing, and audit compliance.

The DSS/WMS Portfolio is responsible for the Warehouse Management System (WMS) including production support, software design, development, maintenance, deployment support, Tier II and III

Support, Customer Service, Audit Readiness Support, and other portfolio support operations. The portfolio focuses on modernizing DLA’s systems for warehousing and distribution and has a requirement to obtain application support services to modify, deploy modifications and sustain the existing SAP deployed Warehouse Management System, which is a configured and customized

Commercial Off-The Shelf (COTS) product.

The Logistics Cataloging and Data Solutions (LCDS) Portfolio is responsible for the Federal

Logistics Information System (FLIS). FLIS, a legacy COTS application, is currently a mainframe system in the process of modernizing into an SAP and ServiceNow environment. FLIS Program enables operation of the Federal Catalog System used to create, maintain, and disseminate item of supply information including archived historical information. FLIS provides a single source of truth for item identification and classification, aids parts standardization across the services, promotes standard item substitutions, facilitates intra/inter- departmental logistics support, and improves material management and military effectiveness by promoting efficiency in logistics operations.

Currently FLIS capabilities are delivered through forty (40) various applications, modules and tools including mainframe, mid-tier and web-based elements to achieve its mission.

The SAP Technical Support Portfolio is responsible for providing comprehensive, best practice

Information Technology (IT) support to the DLA Business Community resulting in high quality production support, environment management, application administration, and ongoing sustainment and operational support for its SAP Platform, existing Enterprise Business System (EBS), and associated SAP and Non-SAP applications.

The SAP Platform underpins critical logistics capabilities and requires continuous support to ensure sustained performance, security, and operational readiness following major transformational initiatives including DLA’s EBS Enterprise Resource Planning (ERP) system from SAP ERP Central

Component (ECC) to SAP S/4 HANA, Federal Logistics Information System (FLIS) Modernization, and Warehouse Management System (WMS) deployment as they transition into Full Operational

Capability (FOC). The support services will encompass continuous operational readiness, robust cybersecurity compliance, cloud infrastructure management, hardware lifecycle oversight, workforce training, comprehensive documentation, and strategic administrative coordination.

2.2 SCOPE

The applications that will utilize this Task Order are WMS, FLIS, and EBS/ERP applications. Individual

Task Orders will be issued utilizing selected tasks relative to an immediate defined need. DLA is currently modernizing legacy systems across several capabilities. This Task Order will support DLA in all software development lifecycle (SDLC) phases and program support for systems as they reach Full Operational

Capability (FOC) and transition to a sustainment posture.

The Contractor shall provide support services as set forth in this PWS. The Contractor shall provide the full range of IT services (as identified in Tasks 1-16) to include the entire SDLC as well as the project management over the SDLC and sustainment support services.

Following the award of the Task Order, the specific scope of each effort will be based on the tasks defined in individual task orders. All deliverables will be defined at the task order level.

This Task Order JETS 2.0 IDIQ SOW Task

TASK 1 – Program Management; (IUS-0004

Program Management)

TASK AREA 7: Program/Project Management

Support

TASK 2 – Technical Environment Support; (IUS-

0003 Operational Phase)

TASK AREA 9: Technical Support

TASK 3 – Application Security Support, Cybersecurity, Risk Management Framework

(RMF), Department of Defense Architectural

Framework (DODAF) & Audit Support (IUS-0003

Operational Phase)

TASK AREA 6: Cyber Security Support Services

TASK 4 – Planning (IUS-0001 Acquisition and

Preliminary Design)

TASK AREA 5: Lifecycle Program Support

Services

TASK 5 – Requirements Analysis (IUS-0001

Acquisition and Preliminary Design)

TASK AREA 2: Technology Services

TASK 6 – Design/Explore (IUS-0001 Acquisition and Preliminary Design) TASK AREA 4: Defense Business Systems (DBS)

Life Cycle Management: Acquisition, Development, Sustainment, Maintenance, and

Technical Support TASK 7 – Build/Configure/Realize (IUS-0002

Development) TASK AREA 4: Defense Business Systems (DBS)

Life Cycle Management: Acquisition, Development, Sustainment, Maintenance, and

Technical Support TASK 8 –Testing (IUS-0003 Operational Phase) TASK AREA 9: Technical Support TASK 9 – Production Prep (IUS-0003 Operational

Phase) TASK AREA 4: Defense Business Systems (DBS)

Life Cycle Management: Acquisition, Development, Sustainment, Maintenance, and

Technical Support TASK 10 – Deployment Prep and Support/Deploy

(IUS-0003 Operational Phase) TASK AREA 4: Defense Business Systems (DBS)

Life Cycle Management: Acquisition, Development, Sustainment, Maintenance, and

Technical Support TASK 11 – Hypercare (IUS-0003 Operational

Phase) TASK AREA 4: Defense Business Systems (DBS)

Life Cycle Management: Acquisition, Development, Sustainment, Maintenance, and

Technical Support TASK 12 – Production Support and

Sustainment/Run (IUS-0003 Operational Phase) TASK AREA 4: Defense Business Systems (DBS)

Life Cycle Management: Acquisition, Development, Sustainment, Maintenance, and

Technical Support TASK 13 – Knowledge Transfer (KT) and On the

Job (OJT) Training (IUS-0003 Operational Phase) TASK AREA 4: Defense Business Systems (DBS)

Life Cycle Management: Acquisition, Development, Sustainment, Maintenance, and

Technical Support TASK 14 – Transition Support (IUS-0003

Operational Phase) TASK AREA 7: Program/Project Management Support

TASK 15 – Hardware Lifecycle Management

(IUS-0003 Operational Phase) TASK AREA 2: Technology Services

TASK 16 – Cloud and Platform Integration/

Operations: (IUS-0003 Operational Phase) TASK AREA 10: Cloud Hosting Services

2.3 TASK REQUIREMENTS

The Contractor will be required to perform tasks such as the following:

2.3.1 TASK 1 – Program Management, IUS-0004 Program Management

The Contractor shall provide Program Management as defined below:

a) Coordinate and advise the Government of requested changes of customer, functional, and technical requirements.

b) Track progress of completing each requirement as it progresses through the SDLC.

c) Develop, prepare, and maintain appropriate reports, briefings, and implementation documentation, as required, and ensure communication is maintained during transitions in infrastructure, organizational responsibilities and products.

d) Provide Status Reports to include information such as, but not limited to, system health, risk management, resource forecasting, and audit-related activities as defined in the task order.

e) Ensure DLA project execution tools are used and that appropriate agile metrics are available to the government as defined in the task order. These may include, but are not limited to: sprint health, velocity, burndown, defect rates, mean time to resolve (MTTR), and resource capacity tracking.

f) Identify and track Test coverage metrics.

g) Develop and maintain a schedule, identify interdependencies between tasks, identify and track critical milestones.

h) Identify potential issues with critical path, project tracking and oversight, to include analysis, recommendation on changes, potential impact on project cost and schedule for each task order as required.

i) Provide complete updates of reports of each task order throughout the lifecycle of the task order as required.

j) Propose changes and modifications to overall and individual project schedules as necessary for

Government approval and acceptance.

k) Document all Government approved changes and modifications to overall and individual project schedules in accordance with DLA requirements methodology of tracking Change Requests and break/fixes for the enterprise.

l) Facilitate and participate in meetings in support of contract activities.

m) Contact, coordinate, and participate in discussions with external partners (Army, Navy, SAP, Microsoft, etc.) and Business/Customers/Stakeholders within DLA as needed.

n) Provide support and management of unforeseen risks for each task order as required, perform risk assessments and maintain a risk register.

o) Create a project management plan for each task order as required.

p) Consult, Recommend, and Develop standard processes, provide support for documentation of processes (for example, System Engineering Plan, Standard Operating Procedures, Desk

Guides, and SOP-related procedures) as required for each task order.

q) Identify risks for any customization activities through performance of gap analyses, provide recommendations for minimizing customizations across all products as required for each task order.

r) Provide status and health of project in writing or presentation as required for each task order;

the information shall include an overview of the completed work, the plan to complete the future work, any risks to the successful completion of the work, and any other information agreed upon by the Contractor and the Government.

s) Support Audit requirements as required for individual task orders.

2.3.2 TASK 2 – Technical Environment Support, IUS-0003 Operational Phase

The contractor shall assist the Government in comprehensive Technical Environment Support and

Sustainment covering continuous operational sustainment and technical management of applications, infrastructures, and platforms as outlined in the Task Order. The Contractor shall:

a) Install, configure, test, and troubleshoot applications in production, staging, and test/development environments.

b) Document and adhere to DLA Change Control processes, capturing all application and infrastructure changes.

c) Document all software installs and application architecture/network configuration in accordance with DLA requirements.

d) Coordinate Maintenance Window (MW) activities, including emergency maintenance windows, with appropriate government resources.

e) Perform operational validation post-maintenance window activities.

f) Provide 24x7 support, on-call or scheduled shifts, for Test/Development and Production environments as defined within the task order.

g) Ensure accurate software installation, documentation, and maintain detailed architecture and network configurations.

h) Support design, implementation and sustainment of the application(s) in various environments

i) Provide expertise for inter-system communication between SAP and non-SAP applications across the DLA and DOD enterprise

j) Support integrated infrastructure comprising varied operating systems, utilities, middleware, and messaging software.

k) Maintain Internet-based and internal/external portals for integrated application management, including web interfaces and electronic commerce.

l) Provide oversight for middleware, bridging software components, and application integration tasks.

m) Provide strategic advice on FinOps principles, optimizing application and hosting infrastructures.

n) Maintain alignment with the DLA Digital Business Transformation initiative, ensuring system scalability and flexibility

o) Conduct performance evaluations, recommend improvements in application design and operational processes, enhancing operating efficiency, reducing operational costs, and streamlining platform and application management.

2.3.3 TASK 3 – Application Security Support, Cybersecurity, Risk Management Framework (RMF), Department of Defense Architectural Framework (DODAF) & Audit Support, IUS-0003

Operational Phase

The Contractor shall partner with the cognizant Program Office and DLA Cybersecurity to maintain and ensure compliance with DLA Cybersecurity, RMF and Audit requirements.

References:

• All applicable DoD Instructions

• All applicable NIST Publications

• DoDM 5200.01, et al.

• DoDD 8100.02, FIPS 140, Circular A-130, et al

• Government Accountability Office (GAO) Federal Information System Control Audit

Manual (FISCAM); a copy of the FISCAM manual can be found at:

http://www.gao.gov/products/GAO-09-232G

Cybersecurity & Access Control

The Contractor shall review, coordinate, and recommend cybersecurity standards and protocols in accordance with the Department of Defense’s (DoD) Defense in Depth (DID) strategies. The Contractor shall ensure compliance with Federal, DoD and DLA information technology and security requirements, policies, procedures, and standards as applicable. The contractor shall perform analyses to validate established security requirements and to recommend additional security requirements. The Contractor shall recommend corrective actions for detected vulnerabilities that could preclude accreditation for management, operational, or technical controls. This may include human procedures, software configuration parameters, system changes, or combinations thereof to mitigate the risk associated with the vulnerability. The Contractor shall adhere to all applicable Security Technical Implementation Guides

(STIGs) and provide documentation of compliance upon request. The Contractor shall participate in cybersecurity vulnerability scans, testing and evaluation. The contractor shall analyze and remediate vulnerability scans and Security Readiness Review (SRR) results, STIG compliance and deficiencies of all forms identified during internal and external cybersecurity reviews. Contractor shall participate in

Information Assurance (IA)/Authority to Operate (ATO) implementation planning and validation. The

Contractor shall attend all relevant cyber security related meetings and provide recommendations and guidance for mitigation/remediation.

The Contractor shall:

a) Develop role design procedures that adhere to DLA Enterprise Segregation of Duties (SoD) policy to include the following:

i. Identify risk within current role infrastructure

ii. Plan and execute risk remediation actions

iii. Implement remediation actions throughout the system landscape utilizing SDLC concepts

iv. Support role redesign efforts from the DLA Distribution business end users

b) Create and maintain role design documentation and reference material that clearly specifies hierarchy of composite roles to single roles to transactions and authorizations.

c) Develop, receive government concurrence, and implement a comprehensive application security change management process.

d) Create, receive government concurrence, and implement comprehensive processes and procedures to ensure the applications follow DLA Enterprise Access Control policy.

e) Provide Central User Administration expertise to Government for managing user base.

f) Provide expertise to Government in managing Java-stack user base.

g) Support audit activities and assist in ensuring that DLA systems are adhering to Enterprise Access

Control policy and procedure.

h) Leverage SAP Business Process Master List (BPML) to improve the Application Security mapping of security roles to defined business processes as described at the individual task order level.

i) Develop and administer the Role Based Access Control processes and documentation.

http://www.usfj.mil/Portals/80/Documents/Instructions/36-2611%20(USFJI).pdf

j) Provide on-call support for after-hours technical work, including but not limited to: upgrade activities, production or non-production issues, implementation or cutover actions.

k) Provide Governance Risk Compliance (GRC) support for alignment to DLA Enterprise Rule Sets to include the following:

a. Expertise with GRC integration and management

b. Establishment of temporary emergency access and authorizations (Firefighter roles)

c. Train government personnel on development and administration of temporary emergency access

l) Assist the Government in compliance with Cybercom/Security Vulnerabilities and Security Technical

Information Guides (STIGs) for the applications, Operating Systems and infrastructure.

m) Assist the Government with providing STIG/technical architecture/network documentation for the applications.

n) Assist the Government with creation/remediation of Plan of Action and Milestones (POAMS).

o) Assist the Government with completion of the STIG/Information Assurance (IA) checklists.

p) Update and provide the Government DLA Accreditation Boundary documents.

q) Provide Cyber Operational Readiness Assessment (CORA) compliance support and remediate any

Assured Compliance Assessment Solution (ACAS)/Web/Penetration scan findings.

Risk Management Framework (RMF)

The Contractor shall support compliance with DoDI 8510.01, Department of Defense Instruction Risk

Management Framework (RMF) for DoD Information Technology (IT).

Department of Defense Architectural Framework (DODAF)

The Contractor shall:

a) Provide services that assist DLA in complying with Department of Defense Architectural Framework

(DODAF).

b) Develop/assess/validate DoDAF artifacts.

c) Participate in DoDAF implementation planning and validation.

d) Maintain conformance with the current DoDAF Architecture Framework version and ensure all documentation is DoDAF compliant.

e) Conduct monthly Systems Viewpoint (SV-8) Systems Evolution Description review to identify software end of life dates to plan for and be in compliance with Risk Management Framework (RMF) and STIG requirements

Audit Support

The Contractor shall collaborate with Program Management Offices (PMO) outlined in the task order terms in response to Auditor (i.e., DoDIG, Financial Statement, Service Owned Items in DLA Custody (SOIDC), etc.) inquiries as related to system capabilities and functions.

2.3.4 TASK 4 – Planning, IUS-0001 Acquisition and Preliminary Design

The contractor shall:

a) Prepare project management documents as defined for each task order to include documents such as project management plan for each project, project charter, and scope definition, as well as other industry standard project management documents.

b) Provide complete updates of reports of each task order throughout the lifecycle of the task order as required.

c) Assist the Government in establishing project governance structure and documentation

d) Survey and Information Gathering Efforts

1. Draft and maintain survey documentation (i.e. questionnaires)

2. Participate in the coordination and dissemination of survey material

3. Evaluate information gathering responses

4. Coordinate and Facilitate Follow-on Engagements

e) Document continuous improvement opportunities as a result of survey processes

f) Expeditionary Efforts

1. Conduct on-site or remote evaluations such as terrain walks to assess:

i. Business Operations

ii. Physical Layout

iii. Network Infrastructures

iv. Other relevant focal points

2. Document findings in appropriate formats (i.e. trip reports, Situation Reports

SITREPs, briefings)

g) Scoping of Work

1. Participation in initial evaluations of proposed changes prior to formal submission

i. Conduct and present Gap Analysis against existing requirements documents and implemented capabilities and provide recommendations for implementation

2. Calculate Initial Complexity Scoring and provide to government for approval and funding

3. Determine Communities of Interest and Areas of Impact

h) Prioritization and Scheduling of Work

1. Participate in planning activities

2. Strategize workload sequencing and efficiencies

3. Advise on feasibility and alternatives per Gap Analysis Workshop and presentation to Government

4. Intermittently evaluate previous plans

i) Analyze the impact of new and changed requirements on current projects/resources and recommend resourcing options to the Government

j) Follow DLA Enterprise Change Management (CM) process

k) Add, revise, update, or close records in the DLA defined change management tools

l) Set up and maintain Project Team Logistics/Infrastructure and Document Repository as prescribed by the Government

m) Prepare Document templates as required using current DLA artifact templates per current

SOPs

n) Support DLA in researching requests to determine feasibility for future projects

o) Perform feasibility studies as defined by task orders

p) Support Audit requirements as required for individual task orders.

2.3.5 TASK 5 – Requirements Anlalysis, IUS-0001 Acquisition and Preliminary Design

The contractor shall work with stakeholders within DLA and other government partners to ensure requirements are complete, accurate, and testable. The contractor shall provide the following support:

a) Facilitate requirements meetings and other written and oral discussions around requirements.

b) Document business requirements, using DLA approved tools and processes, that are defined by business partners to include but not limited to:

1. Functional requirements in line with DLA policies and procedures

i. Successful path

ii. Unsuccessful path

2. Reporting requirements

3. Internal and external interface requirements

4. Information assurance impacts/requirements

5. Error handling requirements

6. System resource requirements

7. Security requirements

8. Audit requirements

9. Accessibility requirements

10. Identification of other business or technical areas that are impacted by the new or revised requirement

11. Special training requirements

c) Document technical requirements that are defined by technical resources to include but not limited to:

1. Technical requirements in line with DLA policies and procedures

2. Reporting requirements

3. Internal and external interface requirements

4. Information assurance impacts/requirements

5. Requirements for error handling where applicable

6. System resource requirements

7. Architecture requirements

i. Business Architecture

ii. Data Architecture

iii. Application Architecture

iv. Infrastructure/ Technology Architecture Audit requirements

8. Accessibility requirements

9. Identification of other business or technical areas that are impacted by the new or revised requirement

10. Special training requirements

11. Testing Requirements

d) Review business requirements documentation with stakeholders to receive confirmation of completeness and accuracy.

e) Provide documentation identifying impacts of the business requirements to technical requirements documents.

f) Review business requirements documentation with stakeholders to receive confirmation of completeness and accuracy.

g) Provide documentation identifying impacts of the business requirements to technical requirements documents.

h) Coordinate with stakeholders for review of the requirements documentation to confirm that both business and technical requirements are complete, testable, and accurately represent the needs of the business and technical stakeholders.

i) Create Requirements Traceability Matrix (RTM) documentation to track and ensure requirements traceability begins at the creation or receipt of requirements documentation.

j) Document risks that are identified and add to the risk register for tracking, reporting, mitigation, and resolution.

k) Provide information to DLA on any identified impacts to the schedule for the project or program based on requirements accepted for action and analysis.

l) Update records in Government identified systems to manage the scope of work for the project or program (currently utilizing ServiceNow (SNOW), JIRA, Solutions Manager

(SOLMAN), and SharePoint, among others. This list of systems is subject to change during the period of performance of the Task Order). Each Task Order will list Industry standard tools that may be subject to replacement by similar tools throughout the course of the task order. Where Government specific tools are utilized and known at time of award, the Government will enumerate those accordingly.

m) Recommend improvements to the process to include documentation requirements, and procedures.

1. Upon approval from DLA, the contractor shall update document templates.

n) Identify impacts of changes caused by requirements to any system documentation including software artifact deliverables (e.g. Reports, Interfaces, Conversions, Enhancements, Forms, and Workflows (RICEF-W), Print Products/Forms (PPF), internally generated desk guides, job aids, or SOPs).

o) Collaborate with the DLA J6 personnel and other partners to document the requirements for each capability that is necessary to meet full operating capacity (FOC).

1. Creation, Modifying and Executing Request for Change (RFC)

i. Document what exists currently, what can be changed, what cannot be changed, and options to support changes.

2. Updating and Maintaining IMS and artifacts defined by the task order

3. Finalize Requirements Documents

i. Details, options, changes per requirement

4. Creation of Draft Project RMF Checklist

p) Support Audit requirements as required for individual task orders.

2.3.6 TASK 6 – Design/Explore, IUS-0001 Acquisition and Preliminary Design

The contractor shall collaborate with the DLA J6 personnel and other partners to document the functional and technical designs as required by individual task orders. The contractor shall:

a) Update and maintain the project schedule in the approved DLA system as defined by individual task orders.

b) Create and maintain functional design documents or functional specifications as required by the individual task orders with input and approval from DLA, including requirements documentation, policies and procedures, audit requirements, and other documents.

c) Create and maintain technical design documents or technical specifications as required by the individual task orders with input and approval from DLA, including requirements documentation, policies and procedures, audit requirements, and other documents.

d) Provide updates to requirements traceability matrix to track the requirements through functional and technical design as required by individual task orders.

e) Update and Maintain documentation for Risk Management Framework (RMF) as required by individual task orders.

f) Present documentation at meetings and conferences as required by individual task orders.

g) Support Audit requirements as required for individual task orders.

2.3.7 TASK 7 – Build/Configure/Realize, IUS-0002 Development

a) Review Design Documents – For each software enhancement or modification to existing software code, including in-client or transportable configuration, the team will review the

Design documentation for understanding prior to beginning any coding.

b) Contractor Project Manager shall hold cross-functional discussions between impacted teams ensuring all parties understand cross-functional changes and resolve integration questions and problems that may arise.

c) Review the project schedule and Risk Register for an understanding of project timelines and any associated risks.

d) Review the activities required for successful execution of each project in each task order.

e) Propose necessary revisions/updates to the project schedule and tasks which would result in an efficient, successful solution for the documented requirements and/or problem statements of the project(s) assigned.

f) Create and maintain technical design documents for each change, including transportable and in-client configuration, as required by the individual task orders with input and approval from DLA.

g) Perform required development and/or configuration in accordance with the schedule for the project(s) as assigned.

h) Perform required development and/or configuration per approved design documentation.

This may include but is not limited to database table or field updates, additions, deletions, and creation of new database tables, as necessary and approved by the Government.

Applicable coding standards will be followed. Developers will perform dependency checks and validation between source objects and coordinate appropriately between other development teams, any adjustments in development time or substance will be made, as necessary.

i) Collaborate with the DLA J6 personnel and other partners to implement the changes documented in associated design documents.

j) Perform full unit testing of all system modifications completed as part of the build or development. Unit test shall be completed to confirm the system is operating as expected prior to modifications being moved to the Test system. Unit Test Script must be provided to the Government Testing team and sponsor no later than the time of Critical Design

Review (CDR) if applicable as indicated in individual task orders.

k) Conduct Peer Code Reviews and Code Inspections – Peer Code Reviews and Code

Inspections will be conducted on all objects changed or created. Results will be recorded, and updated as necessary, in the Technical Peer Review Documents and Code Review

Checklist. Applicable coding standards will be used as the measure for passing the Code

Inspection and Peer Code Review. Successful code inspection must be documented to include date and time of successful code inspection.

l) Perform Database Architect Review with the appointed government personnel – The Data

Architect reviews and approves the database changes that have been made in development to ensure the Data layer development matches the associated Design Documentation. The review and approval must be completed successfully before moving to the next step in this procedure.

m) Create Role Based Access Control (RBAC) – Contractor shall implement defined application security requirements in the development environment based on the Security

Requirements Document (SRD)Transactions and authorization objects that are developed will be aligned to the appropriate roles defined by DLA and in alignment with DLA’s current Identity, Credential, and Access Management (ICAM) solution.

n) Finalize draft documentation as required throughout the software development lifecycle defined by individual task orders.

o) Create and conduct Critical Design Review (CDR) as required by individual task orders.

p) Upon approval of CDR technical review, prepare and release transports to Configuration

Management (CM) and update Project schedule as required

q) Contract developers shall prepare the necessary software releases for all the objects, transports, and items not requiring transports in the Release and release them to the CM team. Contract developers shall update necessary records as complete for the Build process even if a transport is not required. Once all transports are completed, contract Project

Manager will notify all internal stakeholders and CM Teams that the Build process is completed.

r) Validate software releases were successfully posted to the target environment.

s) Create and conduct Test Readiness Review (TRR) upon Government approval of all software artifact deliverables and content.

t) Conduct Knowledge Transfer (KT) for Systems Testing (ST) Preparation – The Build and/or Design team(s) will prepare and present knowledge transfer information to familiarize the Government with how to test the changes made in preparation for ST. The government will provide the Build Team with specific needs at the task order level for each ST Knowledge Transfer. This must happen prior to TRR or testing phase as defined by task order to ensure the Testing Team is prepared with adequate information to conduct

ST.

u) Prepare data, metrics, and information to conduct the TRR/testing phase as defined by the task order. This must be completed prior to the start of ST.

1.1 TASK 8 – Build/Configure/Realize, IUS-0002 Development

a) Perform comprehensive unit, system, integration, performance, security, and regression testing.

b) Utilize automated testing to the fullest extent possible.

c) Generate automated test cases which can be executed autonomously on command and are repeatable for subsequent release(s) as prescribed by the task order.

d) Provide data preparation instructions for each automated test case if applicable.

e) Provide support in tracking test cases.

f) Maintain traceability of test cases against requirements, design elements, and other artifacts throughout the project lifecycle within the Requirements Traceability Matrix.

g) Provide Custom Integrations or Controls in the event the Automated Testing product is missing functionality.

h) Develop changes to the Automated Testing System (ATS) system. The contractor shall propose any customizations to the government and obtain approval prior to customizations being created.

i) Provide documentation as well as detailed assistance to review any workaround required to execute an automated test script.

j) Provide Administration Support in updating and patching software, ongoing software maintenance.

k) Provide Migration support to configure the system and perform migrations.

l) Provide documentation, support and instruction to government administrators for migration activities.

m) Provide test design workshops for automated test case creation as well as Automated

System configuration.

n) Provide Change Impact Analysis.

o) Review/update the government Automated Testing System Best Practices documentation tailored to the Government’s setup and customized SAP implementation.

p) Review and update Standard Operating Procedures for the Automated Testing System.

q) Create Analytics and Reporting, test coverage metrics, and requirements traceability to test scripts as prescribed by the task order.

r) Be assigned a percentage of test cases from the Test Plan created by the collaborative IPT.

Distribution, maintenance, and management of test cases is shared between Government and Contractor.

For each test case assigned to the contractor, the contractor shall:

1. Draft test case with government approved steps

2. Enter data in the government identified repository with required metadata to support metrics and Earned Value (EV) Reporting

3. Ensure data in the government identified repository is accurate within 24 hours of a status change to the test case

4. Enter data in the government identified defect data repository for every defect identified associated to the test case

5. Ensure data in the government identified defect data repository is accurate within

24 hours of a status change to the defect.

6. File Evidentiary Matter (EM) for completed test case when test case is marked as

Completed Successfully.

7. Remediate all defects associated with the project using DLA defect reporting procedures. Each defect associated with the project shall be remediated using time standards defined by its approved prioritization per defined DLA defect reporting and remediation procedures unless a new estimated completion date (ECD) is negotiated and approved by the government.

8. Renegotiate ECD with the government for defects with an elapsed or anticipated elapsed ECD. ECD renegotiation must occur within one business day of the elapsed ECD.

1.2 TASK 9 – Production Prep, IUS-0003 Operational Phase

The contractor shall collaborate with the DLA J6 personnel and other partners to configure the

Production Region as required by the individual task order. The Configuration of Production includes the following tasks. The contractor shall:

a) Provide a pre-deployment Subject Matter Expert (SME) assessment.

b) Extract data from source system and/or authoritative data source and transform/load data into destination environment.

c) Validate that loaded content is accurate and ready for use.

d) Identify a POC to work with identified government resource(s) to ensure the required system(s) is up to date with in-client configuration as necessary per the individual task order.

e) Create and provide End User training material if there are changes of a technical nature that must be conveyed to the Government for maintenance of the system in the future.

1.3 TASK 10 – Deployment Prep and Support/Deploy (IUS-0003 Operational Phase)

The contractor shall provide subject matter expertise to work alongside the Government-led deployment teams to perform the following activities. The contractor shall:

a) Be on site as required by individual task orders for activities leading up to and immediately following project deployments to ensure the highest level of communication and efficient resolution of emergent and/or emerging defects.

b) Extract staged data from the legacy system and transform/load Data into the Production environment

c) Validate all necessary interfaces are production ready and operational in the production environment.

d) Identify POC(s) to work with identified government resource(s) for each activity that must be completed at time of deployment. Identified contractor resource(s) shall work with the identified government resource(s) to complete all activities timely.

e) Provide a daily update on the Implementation/Configuration Activities for Production preparation and deployment.

1.4 TASK 11 – Hypercare, IUS IUS-0003 Operational Phase)

The contractor shall provide subject matter expertise to work alongside the Government-led deployment teams to perform the following activities. The contractor shall:

a) The contractor shall provide Subject Matter Experts (SME) to be on site for a designated period after “Go Live” as defined in the task order.

b) During the designated period, the contractor shall review and provide recommendations to the

Government for full resolution of known issues identified in production.

c) Incidents (break/fix) identified during Hypercare shall be of increased priority and shall be worked according to Government procedures defined in the individual task order.

d) The contractor shall remediate all hypercare incidents in accordance with the DLA Incident

Management SOP and/or any supplemental guidance as defined in the task order. Each incident associated with the project shall be remediated timely based on the approved prioritization per defined DLA incident reporting and remediation procedures unless a different ECD is negotiated and approved by the Government.

1.5 TASK 12 – Production Support and Sustainment/Run, IUS-0003 Operational Phase

a) Provide ongoing application support and maintenance including, but not limited to, incident management, problem management, change management, and performance monitoring. This includes both Tier 2 and Tier 3 support as defined in the task order.

b) Resolve ticket workload using the system identified in the task order and in accordance with the DLA Incident Management SOP and/or any supplemental guidance as defined in the task order.

c) Develop and maintain continuous integration/continuous delivery (CI/CD) pipelines.

d) Conduct root cause analysis for defects and perform defect remediation.

e) Provide post-production and warranty support including break-fix activities, issue coordination, and ongoing validation of deployed systems.

f) Incidents and tickets must be tracked to resolution by the Tier 2 analyst, or as defined by the task order.

g) Prior to elevating an incident or ticket to Tier 3, the contractor shall ensure Evidentiary

Matter (EM) confirming the problem statement is included (e.g. visuals/screenshots)

h) Adhere to response times, resolution times, and escalation procedures in accordance with

DLA service level agreements (SLAs) or other documentation as defined within the task order.

1.6 TASK 13 – Knowledge Transfer (KT) and On the Job (OJT) Training, IUS-0003

Operational Phase

a) Provide knowledge transfer to Government technical support team(s) identified in the task order for the applications, architecture and configuration.

b) Provide On-the-Job Training (OJT), and knowledge transfer for identified

Government employees, including the following:

1. General development and government staff mentorship during development.

Coordinate with government on the development and maintenance of the OJT plan to include updates as required.

2. Provide on the job training, and process configuration and development familiarization for identified program staff to include the following:

i. Provide OJT and KT with a “hands–on” emphasis on software modules and configuration, customization, test, and sustainment processes.

ii. Support the DLA creation of a user training schedule for integrating the software implementation and changes.

iii. Provide training, training materials (which are limited to any materials needed to facilitate Knowledge Transfer and On-The-Job training), and job aids as required.

iv. Provide the configuration path and process for each item that is configured and customized.

v. Provide on-site support to enable the government development team to fully participate in the development lifecycle.

3. Provide on-site support to enable the government testing team to fully participate in the development cycle. The contractor will advise and assist staff during the phases of the SDLC by walking them through the design/build/test of the selected capabilities. The contractor should work as a bridge and translator between the contractor’s own development teams and the Government’s team.

1.7 TASK 14 – Transition Support, IUS-0003 Operational Phase

In the event the incumbent Contractor is not awarded any future follow-on efforts or there is a need to transition during thetask order, transition support may be needed and will be defined at the task order level. Transition support will include knowledge transfer and training to any follow-on provider to include all of the necessary documentation, orientation, collaboration, and training to facilitate the comprehensive understanding and execution of tasks, processes, procedures, schedules and deliverables in a timely and orderly fashion. All transition activities shall be coordinated with and approved by the

COR. The contractor shall provide the following:

a) Provide transition services associated with the consolidation or divesture of DoD and/or

DLA workload or uninterrupted operations.

b) Assist DLA in planning, preparing, and implementing any transition or change services.

c) Provide DLA-approved changes to DLA equipment, software, processes, and overall environment to support such consolidation or relocation.

d) Take into account economies of scale and other synergies between the acquired operations of DLA.

e) Provide transition cost analysis, propose schedules and document risks associated with such transition

Deliverable: Transition Plan:

The contractor shall provide a Transition Plan NTE seven (7) pages within 120 days of task order award of the base period.

a) Provide a strategy to execute the transition out of all services to include knowledge transfer to personnel designated by the government.

b) Provide a full performance schedule for the transition out phases.

c) Provide transition services associated with the consolidation or divesture of DoD and/or DLA workload or uninterrupted operations.

d) Assist DLA in planning, preparing, and implementing any transition or change services.

e) Provide approved changes to DLA equipment, software, processes, and overall environment to support such consolidation or relocation.

f) Consider economies of scale and other synergies between the acquired operations of DLA.

g) Provide transition cost analysis, propose schedules and document risks associated with such transition.

1.8 TASK 15 – Transition Support, IUS-0003 Operational Phase

a) Conduct hardware sizing analysis and provide recommendations for adding or reducing hardware.

b) Complete and provide required documentation and service request forms to acquire additional hardware and software in accordance with existing procedures and proper approvals.

c) Complete and provide required documentation and service request forms to remove or decommission replaced/redundant and no longer needed hardware in accordance with existing procedures and proper approvals.

d) Provide break/fix maintenance services with defined response times based on criticality.

e) Install firmware/software updates and security patches as required to maintain hardware security.

f) Perform installation, configuration, and testing of new hardware to ensure proper integration with existing DLA systems.

g) Provide technical expertise and troubleshooting for hardware-related issues impacting warehouse operations.

h) Ensure all hardware meets DLA’s security and Trade Agreements Act (TAA) requirements and maintains compliance with DLA’s standards.

i) Conduct hardware inventory audits and provide status reports on operational equipment.

j) Provide training to DLA personnel on proper operation and maintenance of hardware devices.

1.9 TASK 16 – Cloud and Platform Integration/Operations: (IUS-0003 Operational Phase

a) Support cloud integration and delivery, middleware platform services, and managed cloud operations.

b) Provide environment lifecycle management including upgrades, patches, monitoring, and continuous optimization.

c) Support cloud platform operations, integration, and delivery services.

d) Assist migration and integration activities involving cloud technologies.

e) Conduct evaluations of platform enhancements to facilitate digital business transformations

1.10 TASK ORDER QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

In fulfillment of this effort, the Contractor shall provide the deliverables identified in this section. All deliverables shall be submitted to the Contracting Officer’s Representative (COR) and Program Point of

Contact for acceptance unless otherwise directed by the Government.

The COR has the responsibility to monitor the progress of the work of the Contractor personnel assigned to the tasks. Additionally, in the absence of other agreements negotiated with respect to time provided for government review, standards and actions shall be inspected and the contractor notified of the COR’s findings within 5 workdays of normally scheduled review.

Unless otherwise specified, the Government will review draft deliverables and provide comments back to the contractor or approve or disapprove the deliverable(s). The contractor will have a maximum of ten (10) working days from the day comments are received to incorporate all changes and submit the final deliverable to the Government. All days identified are intended to be workdays unless otherwise specified.

The format for the individual deliverables will be determined through consultation between the COR and the contractor with recommendations from the Government Program Management Office (PMO). The

QASP identifies the methods the government will use to measure performance of the service provider against the requirements and performance standards of the PWS. The QASP consists of guidelines for performance surveillance, evaluation, reporting, deficiency notification, and adjustments.

2.4.1 Performance Requirements Summary

The tasks the Contractor shall perform are defined in Section 2.3. All deliverables will be submitted to the

COR and Government PMO for review and the PMO will make recommendations to the COR for acceptance unless otherwise agreed upon and the COR will advise the Contracting Officer who will direct the Contractor unless delegated back to the COR.

The Government will make objective and subjective assessments of the contractor’s performance to determine whether contract performance is acceptable. The contractor is expected to perform all functions in a professional manner and prepare accurate and timely documentation. Progress will normally be tracked based on the milestone event when the contractor receives a specific task. Performance may vary with the complexity of the acquisition and/or technical document. It is expected that the documentation and procedures will comply with all major regulatory and process requirements and agency policies and procedures.

2.4.2 Method of Surveillance

The Government will ensure quality assurance and timeliness of all tasks via COR Inspections and

Customer Feedback that is consolidated and submitted by the PMO. The Government will inspect and evaluate performance of each completed task or deliverable required in the task order PWS. All work required by this task order is subject to surveillance.

2.4.2.1 Inspection and Acceptance Criteria

Final inspection and acceptance of all work performed, reports and other deliverables will be performed at the place of delivery by the COR based on PMO recommendations.