1. SOW Jira Confluence posting ver..docx

Statement of Work (SOW) - Atlassian Jira and Confluence Enterprise Renewal

1. Introduction and Background

1.1 Program Title

Renewal of Enterprise Licenses, Maintenance, and Technical Support for Atlassian Jira Software and Confluence.

1.2 Background

The National Institutes of Health (NIH) Clinical Center (CC), Department of Clinical Research Informatics (DCRI), utilizes Atlassian Jira Software and Confluence as core platforms for IT Governance, Quality Management, and critical system documentation. The continuity of these platforms is essential for regulatory compliance and system stability:

Jira Software: Serves as the official Change Management System for Master Control (Quality Manufacturing Compliance for items manufactured within the CC). Maintenance of this system is strictly required for FDA Compliance for manufacturing processes supporting clinical research protocols.

Confluence: Serves as the authoritative source for documentation and communication of changes related to CC Software development and the complex CRIS (Clinical Research Information System) Build and Configuration data. This documentation is required to maintain the compliance and integrity status of CRIS as a High-Valued Asset (HVA).

The overall purpose is to ensure all changes are communicated, documented with a high level of accuracy, and that high system availability is maintained in accordance with Federal regulatory requirements.

1.3 Objective

The primary objective of this SOW is to secure the necessary enterprise license renewal, maintenance, and expert technical support for the NIH CC’s deployed Atlassian Jira and Confluence environment for a specified Period of Performance (POP), guaranteeing no interruption to mission-critical regulatory compliance workflows.

2. Scope of Work (SOW) and Requirements The Contractor shall provide a seamless renewal of the existing Atlassian Jira and Confluence licenses, ensuring the continuous operation of all associated functionality, integrations, and user access for the designated NIH CC DCRI user base.

5 ATL-MP- Message field Data Center for Jira Software (Data

MSSGFIELD4JDC-100R

2.1 Licensing Renewal and Provisioning

The Contractor shall renew and provide all required licenses, including but not limited to:

A. Core Licenses: Renewal of Enterprise, Data Center, or equivalent licenses for Atlassian Jira Software and Atlassian Confluence for the specified user tier and instance count.

B. Add-On Licenses: Renewal of all necessary licenses for integrated Atlassian Marketplace applications (if applicable, e.g., security, reporting, or advanced workflow apps) that are essential for the NIH CC's operational workflows.

C. License Documentation: Provide complete and validated license key(s) or files and a detailed listing of all renewed products, user entitlements, and expiration dates.

2.2 Maintenance, Support, and Availability

The Contractor shall ensure highly reliable service and vendor support:

A. Technical Support: Provide Tier 3 (Vendor Direct) technical support for Severity 1 (system down/critical compliance failure) issues with a response and resolution pathway compliant with NIH CC's internal RTO standards.

B. Updates and Patches: Provide immediate access to all minor software updates, hotfixes, and security patches for the licensed products within fifteen (15) business days of public release to maintain optimal security posture.

C. Compliance and Regulatory Updates: Provide documentation and support guidance related to platform changes that may impact NIH CC’s Federal Information Security Management Act (FISMA) and System Security Plan (SSP) requirements.

2.3 Continuity of Mission-Critical Use Cases

The renewal and associated support must specifically ensure the continuity and regulatory fidelity of the following applications:

A. FDA-Compliant Change Control: The renewed Jira license must maintain full functionality for all established workflows, audit logs, and security controls supporting the Master Control change management process used for quality manufacturing compliance.

B. CRIS HVA Documentation: The renewed Confluence license must maintain read/write integrity, version history, and access controls for all documentation relating to the CRIS Build and Configuration, ensuring compliance required for CRIS as a High-Valued Asset.

C. Security Integration: Maintain compatibility with existing NIH security tools, vulnerability scanners, and network configurations used to monitor the Atlassian platforms.

3. Deliverables Deliverable ID

Description

Delivery Date

D-1

Confirmation of Full License Renewal (Jira and Confluence) and documentation of new subscription term/expiration date.

Within 5 calendar days of POP start date.

D-2

Access credentials and contact information for the Tier 3 Technical Support portal.

Within 5 calendar days of POP start date.

D-3

All released security and compliance patches (as they become available during the POP).

Within 15 business days of vendor release.

D-4

Documentation of any required major version upgrades and confirmation of deployment compatibility.

As required, upon vendor release.

4. Period of Performance (POP) and Place of Performance

4.1 Period of Performance

The base Period of Performance shall be twelve (12) months, with the potential for [Number] one-year option periods, exercisable at the discretion of the Government.

4.2 Place of Performance

The licensed software is utilized by NIH CC personnel primarily on NIH-owned and managed equipment located at the Clinical Center campus or via authorized remote access. The Contractor's services (licensing, support) are performed remotely.

5. Government-Furnished Items The NIH CC will provide the following to the Contractor for the purpose of fulfilling this SOW:

5.1 User/License Count: Current license usage reports and the exact number of users/seats required for the renewal.

5.2 COR/Technical Point of Contact: A dedicated Contracting Officer Representative (COR) and a DCRI Technical POC for communication and license coordination.

5.3 Instance Details: Configuration information, deployment model (e.g., Data Center or Cloud instance details), and version information necessary to execute the renewal.