ADSS_DRAFT (SOW).docx

Statement of Work (SOW) Application Development and Support Services (ADSS)

FMCS

1.0 BACKGROUND

The Federal Mediation and Conciliation Service (FMCS) is an independent federal agency established under the Labor Management Relations Act of 1947 (Taft-Hartley). FMCS provides mediation, conflict resolution, and training services nationwide and internationally.

FMCS operates a cloud-based digital environment built primarily on Microsoft 365 (M365), including SharePoint Online, Microsoft Teams & Integrations, Power Platform components, and integrated third-party systems such as Collabware Collabspace for Electronic Records Management (ERM) and LMS365 for learning management. The environment supports enterprise-wide collaboration, records management, training systems, and operational applications FMCS requires contractor support to provide Application Development and Support Services (ADSS) across its enterprise Microsoft 365 environment and all related systems. The Contractor shall deliver comprehensive, full lifecycle IT services, to include application development, modernization, system integration, operations and maintenance (O&M), system assessments, cloud migration support, and security and compliance services. These services will ensure FMCS systems remain secure, reliable, scalable, and aligned with agency mission needs.

1.1 PURPOSE

To obtain comprehensive Application Development and Support Services (ADSS) to support FMCS’s enterprise application ecosystem, cloud platforms, and digital services.

1.2 OBJECTIVE

To provide full lifecycle support for application development, modernization, integration, and operations and maintenance (O&M) across FMCS’s Microsoft 365 environment and all related systems.

1.3 CONTRACT OVERSIGHT

All work shall be performed under the direction of the FMCS Chief Information Officer (CIO) and the Contracting Officer Representative (COR). The contractor’s program management activities shall also provide support for change management, risk management, and performance management in alignment with the CIO’s strategic goals.

1.4 MONTHLY STATUS REPORT (MSR)

The Contractor shall provide a Monthly Status Report (MSR) summarizing project activities, progress, risks, and performance. The MSR shall be submitted no later than the 5th of each month via email to the COR and CIO.

1.4.1 Contents

· Executive Summary

· Status of all current projects, including:

. Risks and issues . Planned and actual completion dates . Current phase . Disposition (red/yellow/green)

· Key milestones

· Upcoming activities

· Staffing updates

· Operations Performance Matrix

1.4.2 Format

· One-page coversheet

· No more than 3 pages per project

· Moderate margins

· 12-point Times New Roman

1.4.3 Final MSR

A final MSR shall be submitted on the last business day of the final period of performance.

1.4.4 Monthly Financial Dashboard

Delivered monthly to the COR, including:

· Planned

· Actuals

· Variance

2.0 SCOPE OF WORK

The Contractor shall provide full lifecycle Application Development and System Support (ADSS) services across FMCS’s Microsoft 365 ecosystem and associated application environments. The Contractor shall deliver secure, compliant, and modernized solutions that support FMCS mission needs, ensure operational continuity, and enable ongoing modernization.

2.1 Required Services

The Contractor shall provide, at a minimum, the following services:

• Application Development, Modernization, Enhancement, and Integration

· Design, develop, enhance, and integrate applications across FMCS environments.

· Modernize legacy applications and support cloud‑ready architectures.

• Microsoft 365 Platform Support

· Provide support for SharePoint Online, Microsoft Teams, Power Apps, Power Pages, and Power Automate.

· Maintain and enhance workflows, forms, portals, and collaboration solutions.

• Enterprise Systems Support

· Provide operational and enhancement support for FMCS’s Enterprise Records Management (ERM) and Learning Management System (LMS) platforms.

• Operations and Maintenance (O&M)

· Deliver ongoing O&M and support for all supported systems, including troubleshooting, patching, monitoring, and performance optimization.

· Maintain system documentation, run books, and configuration records.

• System Assessments and Modernization Recommendations

· Conduct assessments of existing systems and provide modernization roadmaps aligned with industry standards and best practices.

• Security and Compliance

· Ensure compliance with FISMA, NIST, and OMB A‑130 requirements.

· Ensure Section 508 accessibility compliance for applicable ICT.

· Support governance, data management, and security documentation.

• Cloud Migration and Legacy Modernization

· Provide planning, analysis, and execution support for cloud migration initiatives.

· Modernize legacy systems to align with FMCS’s cloud strategy.

• Enhancement of Systems and Processes

· Improve systems, applications, and business processes to align with industry best practices and evolving FMCS needs.

2.2 Contract Line-Item Numbers (CLINs)

CLIN 1 – Operations & Maintenance (O&M), Minor Enhancements, and Support Activities The Contractor shall:

· Provide O&M & support for all Microsoft 365 systems, CCMS, Arbitration systems, and FMCS web.

· Perform minor development or enhancement tasks requiring less than 40 hours per issue or task.

· Provide security compliance support (Agency/Federal) and transition completed work into O&M.

· Provide planning, coordination, and support for new initiatives.

· Maintain system documentation, run books, and technical artifacts.

CLIN 2 – Major Enhancements and New Initiatives The Contractor shall:

· Perform major enhancements requiring greater than 40 hours per issue or task.

· Support development activities for new initiatives.

· Provide security compliance support (Agency/Federal) and transition completed work into O&M.

· Develop and maintain documentation, run books, and technical artifacts.

3.0 CONTRACTOR REQUIREMENTS

3.1 Technical Qualifications

The Contractor shall possess:

· Demonstrated expertise in Microsoft 365 development and administration

· Experience with Power Platform (Power Apps, Power Automate, Power Pages, Power BI), Microsoft Teams Integrations, Azure Services

· Experience supporting enterprise content management and LMS systems

· Familiarity with federal IT security, compliance, and governance requirements

· Experience ensuring achieving ATO and establishing continuous monitoring for compliance with FISMA (High and Moderate), NIST 800‑53, OMB A‑130, FMCS IT security policies, and Section 508 accessibility requirements for all applicable Information and Communication Technology (ICT).

· Experience with cloud migration planning and modern application architecture

· Expertise in modern, OpenSource platform capabilities, including application development, data modeling, integration, and migration planning

· Ability to document and analyze legacy systems (Dynamics, Power Apps, Dataverse, C#, .NET, SQL Server)

· CMMI Level 3 Dev and services

· Experience with relational Databases: SQLServer, Postgres, Oracle

· Experience design and implement enterprise reports and dashboards

· Experience implementing forms and workflows

· Experience with regulatory agencies, and distributed userbase across the country and the world.

· Experience with environments in Azure cloud

3.2 Experience

· Minimum five (5) years providing ADSS in cloud environments

· Experience supporting small to medium federal agencies and sub agencies

· Experience supporting modernization or migration initiatives

· Minimum ten (10) years implementing, modernizing and maintaining enterprise, mission-critical systems

3.3 Personnel Security

· Tier 2 (Moderate Risk) background investigation with favorable adjudication

4.0 TASKS

4.1 INVESTIGATION PHASE – 3 Months

The Contractor shall conduct a comprehensive investigation of the FMCS Microsoft 365 environment during the initial three-month period. This phase runs concurrently with the O&M Phase.

4.1.1 Investigation Activities

A. Kickoff meeting within one (1) week of award.

B. Evaluate the current M365 environment (SharePoint, Teams, Power Apps, Power Pages, Power BI, LMS365, Collabspace, Dataverse, SQL, Azure Services).

C. Evaluate incomplete tasks from previous vendor.

D. Conduct interviews and review processes to identify issues and errors.

E. Collect requirements for new features and applications.

F. Submit documentation and present findings.

G. Provide modernization and mitigation recommendations, including data storage recommendations (SharePoint lists, Dataverse, SQL).

4.2 OPERATIONS AND MAINTENANCE PHASE – 12 Months (Concurrent)

4.2.1 O&M Activities

A. Redevelop under-functioning Power Apps.

B. Develop new sites, Power Apps, and Power Pages.

C. Update recordkeeping strategies to meet NARA/OMB requirements.

D. Implement new LMS365 features and support separation of LMS and Intranet home sites.

E. Conduct ongoing O&M for SharePoint, Collabspace, LMS365, Power Apps, Power Pages, and Dataverse.

F. Provide collaboration and training for FMCS IT staff and the eLearning Training Specialist.

G. Procure and manage licensing for Collabspace, LMS365, and approved add-ons.

H. Provide full documentation and training for applications and customizations.

I. Continuously evaluate FMCS systems against industry standards and recommend enhancements to improve performance, usability, accessibility, maintainability, and security.

4.2.2 Active Applications Currently Maintained Under This Contract

4.3 OPTION PERIODS – Two (2) Option Years, 12 Months Each

A. Development and modernization B. Operations and maintenance C. Continued licensing of Collabspace and Collabmail

4.4 COMPLIANCE, GOVERNANCE, AND RECORD MANAGEMENT

The Contractor shall:

· Support NARA/OMB compliance

· Maintain ERM tools and processes

· Ensure adherence to FMCS governance, accessibility, and data-management standards

· Ensure all systems comply with FISMA, NIST 800‑53, OMB A‑130, FMCS IT security policies, and Section 508 accessibility requirements, including conformance with the Revised 508 Standards and WCAG 2.0 Level AA for all applicable Information and Communication Technology (ICT).

· Support ATO documentation, POA&Ms, and continuous monitoring

· Implement secure development practices

· Ensure enhancements align with industry standards for security, accessibility, data governance, and digital service delivery

4.5 LICENSING AND PLATFORM SUPPORT

· Assist with license management

· Provide optimization recommendations

4.6 OPTIONAL TASK – Legacy Systems, Web, and Cloud Migration Roadmaps All optional task deliverables shall include:

· Cost estimates for recommended modernization activities

· Cost-benefit analysis

· Industry-standards alignment analysis

· Security modernization recommendations

· Future-state architecture

· Implementation prerequisites and sequencing

4.6.1 CCMS Documentation, Modernization Assessment, Migration Roadmap & Migration Implementation Current System Overview

· Platform: Microsoft Dynamics / Power Apps

· Hosting: Azure GCC Medium

· Criticality: Medium

· Known Issues: Aging architecture, limited extensibility A. CCMS Documentation Document architecture, data model, workflows, integrations, security roles, hosting configuration, and compliance posture.

B. CCMS Modernization Assessment Identify modernization opportunities, technical debt, data strategy improvements, and alignment with industry standards.

C. Migration Roadmap (Planning Only) Includes feasibility analysis, migration approach, data mapping, integration requirements, security requirements, cost estimates, cost-benefit analysis, future-state architecture, and sequencing.

D. CCMS Migration Implementation (Optional Execution Task) If exercised, includes configuration, development, data migration, integration, testing, deployment, training, and post-migration support.

E. Deliverables

· CCMS Documentation Package

· Modernization Findings Report

· Migration Roadmap

· Optional: Migration Implementation Plan

· Optional: Completed Migration

4.6.2 Arbitration System Documentation, Modernization Assessment, Migration Roadmap & Migration Implementation Current System Overview

· Tech Stack: Custom .NET application on Azure VMs with SQL Server backend

· Users: Public-facing; ~661 arbitrators; 12,000+ external users

· Criticality: High/Medium

· Known Issues: Legacy architecture, security vulnerabilities A. Arbitration System Documentation Document architecture, SQL schema, workflows, integrations, hosting configuration, and compliance posture.

B. Modernization Assessment Identify modernization opportunities, data strategy improvements, and alignment with industry standards.

C. Migration Roadmap (Planning Only) Includes feasibility analysis, SQL mapping, integration requirements, security requirements, cost estimates, cost-benefit analysis, future-state architecture, and sequencing.

D. Arbitration Migration Implementation (Optional Execution Task) If exercised, includes configuration, development, data migration, integration, testing, deployment, training, and post-migration support.

E. Deliverables

· Arbitration Documentation Package

· Modernization Findings Report

· Migration Roadmap

· Optional: Migration Implementation Plan

· Optional: Completed Migration

4.6.3 FMCS Web Environment Documentation

Current System Overview

· Tech Stack: WordPress, Apache, AWS

· Users: 118,000+ annually

· Criticality: High

· Known Issues: OMB compliance risks, accessibility issues Document WordPress configuration, Apache and AWS architecture, DNS/DNSSEC, integrations, security posture, modernization opportunities, and cost estimates.

4.6.4 AWS to Azure Migration Roadmap & Migration Implementation A. AWS Environment Assessment The Contractor shall assess the current AWS hosting environment, including workloads, architecture, DNS/DNSSEC, integrations, performance, and security posture.

B. Azure Migration Roadmap (Planning Only) The Contractor shall develop a detailed migration roadmap including:

· Migration strategy

· Future-state Azure architecture

· Data and application migration plan

· Security and compliance mapping

· DNS/DNSSEC transition plan

· Cost estimates for migration, hosting, re-architecture, and decommissioning

· Implementation sequencing and dependencies C. AWS to Azure Migration Implementation (Optional Execution Task) If exercised, the Contractor shall:

· Prepare Azure environment

· Migrate applications, data, and services

· Re-platform or re-architect components as required

· Transition DNS/DNSSEC

· Conduct testing and deployment

· Provide post-migration stabilization

· Decommission AWS resources D. Deliverables

· AWS Environment Assessment Report

· Azure Migration Roadmap

· Optional: Migration Implementation Plan

· Optional: Completed AWS→Azure Migration

· Optional: AWS Decommissioning Report

5.0 DELIVERABLES

5.1 Project Plan for Investigation Phase

5.2 Investigation schedule and stakeholder list

5.3 Investigation report

5.4 Monthly Status Reports (MSR)

5.5 Monthly Financial Dashboard

5.6 Cohesive working sites and applications

5.7 Bi-weekly project team meetings

6.0 Government-Furnished Property and Equipment (GFP/GFE)

The Government will provide Government-Furnished Property and Equipment (GFP/GFE) to support performance of work under this contract. Government-furnished items may include, but are not limited to:

All contractor personnel shall perform Government work exclusively using Government-furnished devices in accordance with FMCS security, IT, and acceptable use policies.

The Government will coordinate the provision of GFP/GFE and system access as required. The Contractor is responsible for complying with all applicable Government security requirements and for notifying the Government of any issues related to access, availability, or use of Government-furnished property or equipment.

7.0 Period of Performance

The period of performance consists of:

Each option year may be exercised at the discretion of the Government.

8.0 Place of Performance

The place of performance for this contract is anticipated to be hybrid. Contractor personnel may perform work remotely and may be required to perform work on site at FMCS facilities as directed by the Government. Specific on-site reporting requirements, including frequency and workspace availability, will be coordinated by the Government.

9.0 FMCS Information Custodial Requirements

9.1 Use of FMCS Information

Information made available to the Contractor by FMCS for the performance or administration of this contract, or information developed by the Contractor in performance or administration of the contract, shall be used only for those purposes and shall not be used in any other way without the prior written agreement of the Contracting Officer.

9.2 Data Segregation and Inspection Rights

FMCS information shall not be co‑mingled with any other data on the Contractor’s or subcontractor’s information systems or media storage systems to ensure FMCS requirements related to data protection and media sanitization can be met. FMCS reserves the right to conduct IT resource inspections to verify data separation and to conduct on‑site inspections of information destruction, media sanitization, or disposal procedures to ensure compliance with FMCS policy requirements.

9.3 Data Destruction Restrictions

Prior to termination or completion of this contract, the Contractor shall not destroy information received from FMCS or gathered or created by the Contractor while performing this contract without prior written approval from the FMCS Contracting Officer. Any data destruction performed on behalf of FMCS must comply with National Archives and Records Administration (NARA) requirements.

9.4 Information Handling Requirements

The Contractor shall receive, gather, store, back up, maintain, use, disclose, and dispose of FMCS information only in compliance with the terms of this contract and applicable Federal and FMCS information confidentiality and security laws, regulations, and policies. Applicable Federal information security regulations include all Federal Information Processing Standards (FIPS) and Special Publications (SP) issued by the National Institute of Standards and Technology (NIST). If additional Federal or FMCS information confidentiality and security laws, regulations, or policies become applicable after contract execution, the parties agree to negotiate in good faith to incorporate those requirements into the contract.

9.5 Restrictions on Copying

The Contractor shall not make copies of FMCS information except as necessary to perform the terms of the agreement or to preserve electronic information stored on Contractor electronic storage media for restoration purposes should any electronic equipment or data used by the Contractor require restoration to an operational state.

9.6 Violations and Remedies

If FMCS determines that the Contractor has violated any of the information confidentiality, privacy, or security provisions of this contract, such violation shall be sufficient grounds for FMCS to terminate the contract for default or terminate for cause under Federal Acquisition Regulation Part 12.

10.0 Personal Conflicts of Interest

Contractor personnel shall avoid personal conflicts of interest and may not participate in matters affecting their own financial interests or those of close associates. Impartiality must be maintained at all times.