FMCS_IT_Applications_DocumentationRoadmap_PWS.docx
DOCX document 19 KB Posted
- Attached to
- FMCS Documentation Strategy Sources Sought
- Solicitation number
- 93310026Q1002
About this file
This is a Performance Work Statement (PWS) for enterprise technical documentation, modernization strategy, and roadmap development services issued by the Federal Mediation and Conciliation Service (FMCS). The FMCS operates a cloud-based enterprise environment centered on Microsoft 365 services, integrated commercial and custom applications including SharePoint Online, Microsoft Teams, Power Platform, Dataverse, SQL Server, Collabspace, LMS365, Azure cloud services, .NET C# applications, and AWS-hosted WordPress systems. The contractor must deliver comprehensive system documentation packages, modernization assessments, and future-state architecture blueprints that align with federal IT, cybersecurity, and records management requirements including FISMA, NIST 800-53, OMB A-130, Section 508 (WCAG 2.0 AA), and NARA standards.
The scope encompasses enterprise technical documentation with architecture diagrams, data models, workflow documentation, and compliance posture mapping; modernization assessments including technical debt evaluation and security posture review; and future-state architecture and strategy development covering a 1-3 year modernization roadmap. System-specific deliverables are required for the Microsoft 365 ecosystem, CCMS (Dynamics/Power Apps on Azure GCC), Arbitration System (.NET/SQL/Azure), and WordPress environments. The initial 90-day investigation phase must produce an investigation project plan, stakeholder interview summaries, system inventory, baseline architecture report, technical debt register, and modernization opportunity matrix. The base period is four months with rolling deliveries scheduled through day 120, including monthly status reports tracking documentation progress, risks, and financial dashboards. Performance metrics include 90 percent documentation accuracy, 100 percent compliance coverage, and 90 percent on-time delivery, with final acceptance contingent upon complete and accurate documentation, sequenced roadmaps with cost models, and executive stakeholder approval.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| FMCS Documentation Strategy Sources Sought FINAL.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PERFORMANCE WORK STATEMENT (PWS)
Enterprise Technical Documentation, Modernization Strategy, and Roadmap Development Services.
1.0 BACKGROUND
The Federal Mediation and Conciliation Service (FMCS) operates a cloud‑based enterprise digital environment centered on Microsoft 365 (M365) services and integrated commercial and custom applications. The current ecosystem includes SharePoint Online, Microsoft Teams, Power Platform components, Dataverse, SQL Server, Collabspace (ERM), LMS365, Azure cloud services, a .NET C# application, an AWS‑hosted WordPress public website, and multiple legacy custom-developed systems.
FMCS requires performance‑based contractor support to develop authoritative enterprise technical documentation, including system overviews, architecture descriptions, and functional designs that define how FMCS business processes, user interactions, data flows, and system capabilities will operate within the future‑state enterprise environment. The Contractor shall also develop modernization strategies, migration roadmaps, and future‑state architecture recommendations. All services must align with federal IT, cybersecurity, and records management requirements and support the Agency’s long‑term goals for modernization, interoperability, and operational resilience.
2.0 PURPOSE
To obtain performance-based services for enterprise technical documentation, modernization strategy development, and future-state roadmap generation across the Agency’s digital ecosystem.
3.0 OBJECTIVE
The Contractor shall deliver comprehensive system documentation packages, modernization assessments, cloud migration roadmaps, Migration feasibility studies and analysis of alternatives (Salesforce, Power Platform, Opensource, others), enterprise future-state architecture blueprints, governance and compliance alignment frameworks, and technology strategy plans supporting executive decision-making and digital transformation.
4.0 PERFORMANCE-BASED SCOPE
The Contractor shall perform work based on measurable outcomes including documentation completeness, modernization recommendations, compliance traceability, and roadmap sequencing.
4.1 ENTERPRISE TECHNICAL DOCUMENTATION
Deliver complete documentation packages including architecture diagrams, data models, workflow documentation, integration maps, security models, hosting configurations, compliance posture mapping (FISMA, NIST 800-53, OMB A-130, Section 508), dependency mapping, risk identification, and licensing inventories.
4.2 MODERNIZATION ASSESSMENTS
Provide structured modernization analysis including technical debt assessment, security posture evaluation, accessibility review, governance assessment, scalability analysis, prioritized recommendations, and modernization sequencing.
4.3 FUTURE-STATE ARCHITECTURE & STRATEGY
Develop a 1–3 year enterprise modernization strategy including future-state architecture, application rationalization, cloud optimization roadmap, data strategy, governance enhancements, security modernization plan, DevSecOps framework, reporting and analytics strategy, and budgetary planning framework.
4.4 SYSTEM-SPECIFIC DOCUMENTATION & ROADMAPS
Produce documentation and strategy deliverables for:
• Microsoft 365 ecosystem
• CCMS (Dynamics / Power Apps – Azure GCC)
• Arbitration System (.NET / SQL / Azure)
• WordPress Public Web Environment (AWS)
• WordPress AWS to Azure Migration Each shall include current-state documentation, modernization assessment, cost-benefit analysis, future-state architecture, and migration sequencing plan.
4.5 COMPLIANCE & GOVERNANCE ALIGNMENT
All deliverables shall align with FISMA , NIST 800-53, OMB A-130, Section 508 (WCAG
2.0 AA), NARA requirements, secure development practices, ATO documentation, POA&M tracking, and continuous monitoring frameworks.
4.6 INVESTIGATION PHASE (FIRST 90 DAYS)
Deliver Investigation Project Plan, stakeholder interview summaries, system inventory, architecture baseline report, technical debt register, risk register, and modernization opportunity matrix within 90 days of award.
4.7 REPORTING REQUIREMENTS
Provide Monthly Status Reports including executive summary, documentation progress, roadmap development status, risks/issues, milestones, and financial dashboard (planned vs actual vs variance).
5.0 DELIVERABLE SCHEDULE
• Investigation Project Plan – 20 Days; Day 20
• Baseline Documentation – 45 Days; Day 45
• System Documentation Packages – Rolling Delivery
• Modernization Reports – Within 45 Days after Baseline; Day 90
• Enterprise Strategy Report – 60 Days; Day 60
• Migration Roadmaps – 90 Days; Day 90
• Final Consolidated Strategy & Roadmap – 120 Days; Day 120
6.0 PERFORMANCE METRICS
• Documentation Accuracy ≥90%
• Cost Estimate Reliability ±20%
• Compliance Coverage 100%
• On-Time Delivery ≥90%
7.0 PERIOD OF PERFORMANCE
Base Period: 4 months
8.0 ACCEPTANCE CRITERIA
Deliverables will be accepted when documentation is complete and accurate, roadmaps include sequencing and cost models, compliance traceability is validated, and executive stakeholders approve.
File details come from the government source that posted it. Updated .