FAST MOD PWS DRAFT 11.6.24.pdf

FAST Modernization Performance Work Statement Table of Contents

1. INTRODUCTION

1.1. Background

1.2. Scope

1.3. Performance Objectives

2. PERFORMANCE REQUIREMENTS

2.1. Task 1 – Project and Contract Management

2.2. Task 2 – Data Conversion and Data Migration

2.3. Task 3 – Development of Appian Low Code Application Platform

2.3.1. Content Management

2.3.2. Business Process Workflows

2.3.3. Clause Automation Module

2.3.4. Instant Publishing

2.3.5. Website Design

2.4. Task 4 - Testing Support

2.5. Task 5 – Training Support

2.6. Task 6 – Operations and Maintenance

2.7. Task 7 – Transition Support

3. DELIVERABLES

4. PERSONNEL

4.1 Key Personnel

4.1.1 Program/Project Manager

4.1.2 System Solution Architect

4.1.3 Software Developer

4.1.4 System Administrator

4.2. Personnel Security Requirements

5. GOVERNMENT FURNISHED PROPERTY

6. ACCEPTANCE CRITERIA

APPENDIX A: FAST Modernization Functional and Non-Functional Requirements

1. INTRODUCTION

1.1. Background

The Federal Aviation Administration (FAA) is modernizing the FAA Acquisition System Toolset (FAST) website (https://fast.faa.gov), which serves as the official repository of the Acquisition Management System (AMS) and other acquisition tools and resources (i.e. FAST content). FAST content is essential for program offices, governance organizations, and approval authorities such as the Acquisition Executive Board (AEB), Acquisition System Advisory Group (ASAG), and FAA Acquisition Executive (FAE). The AMS establishes policy and guidance for all aspects of lifecycle acquisition management for the FAA. It defines how the FAA manages its resources - money / people / assets - to fulfill its mission. The objectives of the AMS are to increase the quality, reduce the time, manage the risk, and minimize the cost of delivering safe and secure services to the aviation community and flying public. AMS fosters collaboration among service providers and customers to ensure FAA plans, programs, and budgets address priority aviation needs. Per section 348 of Public Law 104-50, (1996 DOT Appropriations Act), the FAA established an independent acquisition system. AMS supersedes acquisition policies and procedures of the Department of Transportation and all other acquisition and procurement statutes and regulations, including the Federal Acquisition Regulation.

1.2. Scope

The FAA aims to modernize the FAST website platform and its related content and change management processes by replacing the current, predominantly manual system. The FAA requires the conversion and migration of content and data into a FedRamp authorized, cloud based Appian Low Code Application Platform (LCAP).

The new LCAP will enhance the organization's web presence by introducing features such as instant content publishing and an integrated business process workflow management system. This effort includes converting all existing web content, documents, media, and metadata into formats compatible with the new platform while ensuring no data loss or corruption. The platform will enable content creators, editors, and administrators to collaborate efficiently while ensuring content is reviewed, approved, and published in a timely manner.

FAA intends for the Appian solution to leverage Robotic Process Automation (RPA), Artificial Intelligence (AI), and Machine Learning technology to enhance agency outcomes. This includes, but is not limited, to streamlining and eliminating repetitive and mechanical activities within the change management process to improve efficiency and effectiveness. The Appian solution must streamline internal business processes, from content submission to final approval, while maintaining near real-time content updates on the website. The platform will also integrate the Appian Clause Automation Module which will serve as the centralized source for AMS clauses and provisions and provide FAA Contracting Officers a more efficient way to include clauses in solicitation packages and award documents. Additionally, the project requires a structured Agile project management approach to ensure that timelines are met, risks are managed, and quality deliverables are produced.

1.3. Performance Objectives

This Performance Work Statement (PWS) establishes a framework for the planning, analysis, architecture, design, development, testing, implementation, and operation & maintenance of products or tools developed on the Appian LCAP platform.

The FAA is seeking a contractor to serve as an integrator to perform the following objectives:

A. Convert existing FAST website content data into DITA XML format.

B. Establish a functional web-based platform for developers to store and collaborate on the converted data.

C. Ensure that the converted DITA XML data can be integrated with Appian LCAP for efficient application development.

D. Ensure the platform facilitates collaboration among stakeholders for AMS changes and FAST website content, enabling seamless communication, information sharing, and the ability to make redline changes to documentation to support effective decision making.

E. Incorporate capabilities and workflow automation within the platform to streamline approval processes and reduce manual intervention.

F. Configure, implement, and provide training sessions tailored to defined user roles. Additionally, offer post-go-live platform support that incorporates the FAA’s core business functions required to implement changes to the AMS and FAST Website content.

G. Provide an automated AMS clause retrieval feature for Contracting Officers for efficient inclusion in solicitation packages and award documents.

H. Ensure that the new platform is architected to provide performance, high availability, scalability, compliance, security, ease of use, and cost effectiveness.

I. Ensure a seamless transition of Appian LCAP and clause automation operations and maintenance to government personnel.

2. PERFORMANCE REQUIREMENTS

2.1. Task 1 – Project and Contract Management

The Contractor’s methodology and solution implementation must comply with all FAA policies, procedures, and guidance as stated in this PWS. The Contractor must provide project management and contract management functions to establish the project requirements and effectively organize, plan, schedule, implement, control, analyze, maintain, and report on all project elements. This includes, but is not limited to, planning, and reporting project status against scheduled milestones, reporting, and deliverables.

The Contractor’s Project Management methodology must be based on the Agile Program Management Framework to ensure iterative delivery, transparency, and collaboration. This contract must be managed in a consistent and quality manner to accomplish the work described in this PWS. The Contractor must ensure all work is in full compliance with the documents listed in Section 3 (Deliverables).

The Contractor must perform the following objectives:

A. Develop a detailed resource loaded Project Management Plan, outlining tasks, milestones, deliverables, and a timeline for completion.

B. Conduct a project Kick Off Meeting with FAA stakeholders to review the PWS requirements and scope, deliverable schedule, and address any project questions.

C. Implement Agile project management practices, including sprint planning, daily stand up, and retrospectives.

D. Finalize detailed requirements with FAA stakeholders to include capturing user stories and significant use cases.

E. Develop and implement a Risk Management Plan to identify, assess, and mitigate risks throughout the development process.

F. Develop and implement a Quality Control Plan to ensure quality standards are met through testing and validation of performance objectives and acceptance criteria.

G. Conduct monthly Project Management Review (PMR) presentations with FAA stakeholders (i.e. CO, COR, Program Manager, etc.) that includes, but is not limited to, contract information, financial summary by CLIN, staffing summary by task, performance summary, accomplishments, and action item summary.

H. Provide Monthly Status Reports (MSRs) detailing the activities and progress of the previous month and identifying planned activities for the following month.

MSRs must include, at a minimum:

1) Detailed record of activities and accomplishments during the previous month, work in progress, and work planned for each task.

2) Hours expended by task, labor category and personnel associated with each

Time and Materials (T&M) Contract Line-Item Number (CLIN), if applicable.

3) Provide level of effort for all System Change Request (SCR) packages and track and report expenditures to these estimates.

4) Status of quality verification process to ensure integrity of data is maintained.

5) Areas of concern, risk register, status of work completed, sprint schedule and releases, problem areas, and progression milestones.

6) Identification of risk areas with recommended mitigation strategies for managing risk.

7) Status of all outstanding risks identified in previous MSRs.

8) Status of individual deliverables planned submission dates, actual acceptance dates, location of where deliverable is stored (if applicable), and corrective actions being taken, if any, to address rejected deliverables associated with each CLIN.

9) Government Furnished Property (GFP) Listing.

10) Other information pertinent to administering performance of this effort or as requested by the COR.

11) Monthly Financial Status that includes CLINs used during month, Funded cost by CLIN, Expended cost CLIN, Remaining funds by CLIN, Other direct costs

(ODCs) estimated, used, and remaining by month, and payment schedule by month.

I. Ensure all tasks, deliverables, invoices, reports, and schedule are within the scope of the contract and are approved by the FAA.

J. Hold regular stakeholder meetings to provide updates, review progress, and address concerns. Document meetings by providing meeting minutes.

K. Conduct weekly project status meetings, and host or attend other meetings in support of this effort as required by the FAA.

L. Ensure that resources are allocated appropriately across all tasks and phases of the project.

M. Deliver a comprehensive deployment plan, including approach, activities, schedule, conditions, dependencies, contacts, and other details necessary to ensure a well-orchestrated, successful release.

N. Execute the deployment plan at the direction of the FAA that provides deployment support for transitioning the system into production, followed by operational support and fix any bugs or defects without impacting other scheduled tasks.

2.2. Task 2 – Data Conversion and Data Migration

The FAST website currently houses documentation and processes that require standardization for better management and usability. Converting this data to DITA

XML will enhance its reusability and integration with the Appian LCAP. The contractor will perform an analysis of the existing data on the FAST website and convert identified data to DITA XML format. The converted data will be stored in a web-based platform that facilitates developer collaboration and supports the population of the Appian LCAP.

The Contractor will oversee the content and data conversion process from the existing system to the new Appian LCAP. This includes performing a thorough analysis of the current content, executing data migration, ensuring the integrity of all migrated content, and configuring the new platform to support instant publishing and custom business process workflows. The project will ensure that all legacy content is fully accessible, searchable, and correctly formatted within the new system.

The Contractor will meet the following objectives:

A. Review the current FAST website content in collaboration with FAA stakeholders and develop a complete Content Inventory Report listing all content types available on the FAST website.

B. Assess the data quality to determine content structure, categorization, relevance, metadata, and conversion requirements and develop Content Assessment Report with recommendations for content to update, retain, or remove with support from FAA stakeholders.

C. Develop a detailed strategy for converting documents, including mapping content elements to DITA structures (topic, maps, etc.).

D. Define and implement a strategy for mapping data from the legacy system to the new LCAP. This will ensure content compatibility and retention of all key metadata (e.g., Search Engine Optimization (SEO) tags, descriptions, and categories).

E. Determine and implement strategy for migrating and converting data that continues to be updated on existing FAST website to ensure latest content is incorporated into Appian LCAP prior to deployment.

F. Convert identified documents into DITA XML format, including mapping existing structures into DITA elements and ensure adherence to DITA standards.

G. Set up a web-based platform (e.g., GitHub, Bitbucket) to store, share, and collaborate on the converted code and migrate all converted data.

H. Ensure that the DITA XML data can be effectively utilized with Appian LCAP for application development and that all media (images, videos) are appropriately compressed and optimized for web delivery.

I. Migrate specified data from the current FAST website to the Appian website.

J. Conduct thorough testing and validation of the converted DITA XML files for accuracy and completeness.

K. Support a wide variety of content types, including text, multimedia, and downloadable resources.

L. Ensure that existing SEO attributes (e.g., URLs, meta descriptions, keywords) are preserved and/or improved in the new platform to maintain search rankings.

2.3. Task 3 – Development of Appian Low Code Application Platform The contractor will design, configure, test, deploy, and maintain an Appian-based LCAP with a business process workflow, clause automation module, and instant publishing capabilities. The platform must provide a user-friendly interface, robust content management tools, and integration with existing organizational systems. The primary objective is to enhance content creation, approval, and distribution processes while ensuring that website updates are efficiently published in real-time.

The LCAP must enable content management users the ability to develop, maintain, review, edit, collaborate, approve, and publish content through a role-based workflow system which restricts access based on content, user roles (both individual and group), permissions, or site ownership.

The LCAP will include, at a minimum, the following performance objectives:

A. Create design specifications for workflows, content management, clause automation and instant publishing.

B. Prioritize out of the box configuration over customer development.

C. Prioritize an intuitive design, ensuring that users with varying levels of technical expertise can easily navigate and utilize its features.

D. Ability to download selected content in multiple formats (i.e. Microsoft Office 365

Suite: Word, Excel and Adobe PDF etc.)

E. Interface or integrate with existing FAA platforms, specifically integration capabilities to email and third-party messaging (M365) providing the ability to send emails from within the system with replies routed into the user’s inbox.

F. Provide a robust search capability, based on roles and permissions, across all information sources, including databases, documents, web pages, attachments, forms, and activity logs. The search capability must also allow users to filter results based on specific content categories (i.e. policy, guidance, clauses, change requests) and to export search results in various formats (e.g. PDF, CSV, .DOC, .XLS).

G. Receive real-time notifications via email of reviews and approvals with intuitive quick links directly to the item requiring review.

H. Ability to assign roles and user permissions, automate approval process, and create customized approval workflows from FAA’s Global Address List.

I. Integrate with FAA Single Sign On (SSO).

J. Reporting and dashboard capabilities providing real-time metrics with a wide variety of standard reports and dashboards and the ability to create custom reports based on any field in the system out-of-the-box. Ad hoc reporting capability should include the ability to print and export to various formats including but not limited to .pdf, .doc, .html, .xls.

K. Integrate with web analytics tools for content performance tracking.

2.3.1. Content Management

The Contractor must develop the Appian LCAP to allow the following content management capabilities and functionality:

A. Enable quick and efficient bulk uploads and management of various web artifact formats, including but not limited to PDFs, images, podcasts, video, datasets, Microsoft Office 365 Suite: Word, Excel, etc.

B. Provide content versioning to allow tracking of changes and rollback functionality.

C. Allow side-by-side comparisons of current and prior versions of data, with changes red-lined or highlighted, and a history of revisions on the content management system.

D. Ability for multiple users to work on a specific area of content at any time, without interfering with other’s changes.

2.3.2. Business Process Workflows

The contractor will implement custom workflows to support the AMS content creation and management, review, approval, and publishing lifecycle. This includes:

A. Design and configure workflows to streamline content creation, editing, review, and approval processes with electronic signatures.

B. Allow intuitive review and approvals within the system, including in-document insertions, comments, suggestions, and highlights.

C. Workflows must provide a clean, uncluttered, user-friendly graphical interface that includes tooltips, inline help, or brief contextual instructions to guide the user in reviewing and approving changes within the system without requiring formal training.

D. Establish role-based permissions for users such as content creators, editors, reviewers, and administrators, allowing them to interact with the content at the appropriate stages of the workflow.

E. Set up automated notifications and reminders to alert users when tasks require their attention (e.g., content ready for review).

F. Create task assignment functionality to ensure that content moves through the process efficiently.

G. Workflow capabilities include the ability to automatically route, share information, automate tasks and processes, collaborate across departments, and distribute reports.

H. Implement version control features, allowing users to view previous versions and rollback to earlier states if necessary.

I. Ability to create/customize business rules for workflow as well as access controls.

J. Ability to assign roles and user permissions, automate approval process, and create customized approval workflows.

2.3.3. Clause Automation Module

The Contractor must provide an automated AMS clause and provision retrieval feature using Appian’s Clause Automation Module which will allow Contracting

Officers (CO) to efficiently include clauses and provisions in solicitation packages and award documents based on the acquisition’s characteristics and user provided information.

The clause module must be developed with the following objectives:

A. Ensure that clauses and provisions are updated automatically within the content management platform (Appian) from the authoritative DITA XML data source.

B. Ability to manage two distinct data sets for procurement and real property clause and provision sets.

C. Streamline the clause and provision selection through automation where clauses and provisions are assessed based on configurable business rules derived from clause and provision prescriptions.

D. Ensure that clause sets are automatically and accurately populated with recommended clauses and provisions based on user responses to questionnaires to ultimately minimize manual reviews.

E. Maintain an auditable clause and provision activity log for CO users that serves as a record of all clause and provision selection activities, including creation, modification, and deletion.

F. Allow for CO users to validate clause and provision sets to ensure completeness before final clauses and provisions are compiled for solicitations or award documents.

G. Ensure clauses and provisions are downloadable in multiple document formats (i.e. Word, Excel, Adobe PDF, etc.).

2.3.4. Instant Publishing

The LCAP will include, at a minimum, the following performance objectives:

A. Ensure content is published in real-time, appearing on the live website immediately upon approval (within 30 seconds).

B. Ensure content is mobile-friendly and accessible across various devices and browsers.

C. Provide content creators with the ability to preview their content before publishing, ensuring it displays correctly across various devices and browsers.

D. Enable scheduled or recurring publishing capabilities where necessary.

E. Allow users to schedule content to go live at a specific date and time, creating a queue for future posts.

F. Integrate with SEO tools to optimize published content for search engines, including features like meta tag editing, URL customization, and image alt text fields.

2.3.5. Website Design

The Contractor must design and organize the FAST web content to improve user experience and meet modern web design standards, including:

A. Optimize content layout and organization for a clean, user-friendly, intuitive design that enhances user navigation and accessibility without the need for formalized training.

B. Ensure that all content follows a mobile-first design approach, making it responsive and adaptable to various screen sizes.

C. Ensure that all web content conforms to FAA’s branding and design standards, including font use, color schemes, and image placement.

D. Optimize all content for SEO and user experience, ensuring content is easy to find, navigate, and consume.

E. Ensure that any configuration or development is done in accordance with 508 compliance standards. This requires collaboration with the FAA Section 508 Application Testing Team.

F. Ensure all websites meet FAA website standards in accordance with the Office of Communication’s guidelines.

G. Any webforms must use the FAA reCAPTCHA. This requires collaboration with the FAA Office of Communications team.

H. Ensure the website is set up to handle high traffic and rapid content updates with fast loading speeds.

I. Assess the best method to access current archived FAST content and display future archive content on website.

2.4. Task 4 - Testing Support

Effective testing is crucial to validate the functionality, performance, and user acceptance of the Appian LCAP applications and modules before deployment.

The Contractor must perform the following testing tasks:

A. Develop a comprehensive testing strategy that outlines testing objectives, methodologies, and timelines.

B. Identify tools and resources required for testing.

C. Create a detailed Test Plan that will specify test cases, acceptance criteria, and resource allocations for each component ensuring that the Appian LCAP application and modules meet all functional and non-functional requirements.

D. Conduct the following types of testing:

1) Unit Testing: Validate individual components for correctness.

2) Integration Testing: Ensure that different modules and processes work together as intended.

3) System Testing: Assess the complete application in a controlled environment to confirm all requirements are met.

4) User Acceptance Testing (UAT): Facilitate sessions with stakeholders to validate usability and functionality against business requirements.

E. Document and prioritize defects discovered during testing.

F. Collaborate with government stakeholders to ensure time resolution of identified issues.

G. Provide regular status updates and detailed reports on testing progress, findings, and outcomes.

H. Deliver a final Testing Report summarizing the testing efforts, defects found, and resolutions.

2.5. Task 5 – Training Support

The Contractor must develop training focused on the Appian LCAP, emphasizing simplicity for varying levels of users, particularly in managing content, business process workflows, and the clause automation module.

The training task must accomplish the following:

A. Design a comprehensive Training Plan addressing core functionalities of the

Appian LCAP and clause automation module tailored to the specific roles and responsibilities of each user group to ensure that they receive the knowledge and skills necessary to effectively utilize Appian and any associated modules.

B. Contractor must establish a Training Schedule that accommodates the availability of FAA personnel, with a focus on minimizing disruptions to daily operations while maximizing the effectiveness of the training.

C. Develop user-friendly instructional materials, including guides and visual aids tailored to content management and clause automation. Instructional Materials should be engaging, accessible, and designed for various learning styles.

D. Conduct interactive training sessions for defined user roles, utilizing both in-person and virtual formats that will include at a minimum:

1) Training on the Appian LCAP, business process workflows, and clause automation module for defined users, ensuring accessibility for novice, intermediate, and advanced users.

2) Overview of the Appian LCAP and the platform functionality for content management.

3) Steps to create and manage business process workflows.

4) Techniques for clause automation

5) Hands-on exercises for practical application

6) Empower users with practical skills to enhance productivity and efficiency within their roles.

E. Training must be delivered by trainers with proven expertise with the Appian

LCAP, business process automation, and clause automation module.

F. Conduct post-training assessments to evaluate participant knowledge and skill acquisition and create post-training evaluation report summarizing feedback and participant performance.

G. All training materials and formats must be 508 compliant.

2.6. Task 6 – Operations and Maintenance

The Contractor must provide operations and maintenance (O&M) support for the system. The Contractor will be responsible for providing comprehensive operations and maintenance services, including but not limited to:

A. System monitoring and performance tuning:

1) Regularly monitor system performance metrics and logs.

2) Optimize application performance based on user feedback analytics.

3) Conduct routine health checks and system audits.

B. Incident Management:

1) Availability. System must be accessible 24 x 7 x 365 with exception of scheduled maintenance windows.

2) Technical Support. Help Desk services must be established for user support and issue resolution and be available during normal business hours (8:00 AM to 8:00 PM ET) Monday-Friday (not including Federal Holidays) with on-call support after hours and weekends.

3) Monitor the supported environment and respond to user issues through escalation and resolution.

4) Lead coordination with other FAA technology teams such as the M365 Productivity Team associated with incident management.

5) Lead all testing activities associated with incident management.

C. Application updates and vendor releases:

1) Collaborate with COR and FAA Program Manager to identify and prioritize enhancement requests.

2) System Upgrades Coordination. The Contractor must coordinate software upgrades to the platform with the vendor and user community. Updates must be conducted without service disruption by the host vendor. New capabilities must be documented and briefed to the user community and implemented as deemed appropriate by FAA management. All approved system upgrades will be tested by vendor and user community prior to release. Changes or impacts to system configuration must be documented.

3) Provide technical training to user community prior to the features released during updates or enhancements.

4) Test new features and updates in a development environment for deployment.

D. Develop and provide an Incident Management, User Management, Change Management, and Release Management tracking mechanism using available applications within the FAA that is shared with the business customer.

E. The release management tracking system must include at a minimum what is in the release, rollback plan, customer approval for the release into production, date/time of the release, release failure or success and in the event of a failure, what went wrong, and how the issue was remediated.

F. The user management tracking must describe at a minimum the issue, document all troubleshooting steps and solutions, and will track the incident from discovery to completion.

G. User support:

1) Address user access issues including but not limited to managing and assigning licenses, managing permissions, and troubleshooting access issues.

2) Develop a process for users to submit incidents and service requests.

3) Manage and maintain all user manuals and training material affected by incident management modifications.

4) Provide recorded training sessions for new and existing users.

5) Create a knowledge base for common issues and solutions.

H. Security Management:

1) The contractor must support FAA security in the annual system security assessment and the process required for the system to be granted the authority to operate (ATO). The contractor must ensure the security of the database through access controls and compliance with FAA IT security protocols.

2) Manage the security aspects of the system and, in many cases, will be assigned responsibility for the day-to-day security operations of the system.

3) Ensure information system security requirements are addressed during all phases of an information system lifecycle.

4) Evaluate the efficiency, effectiveness, and compliance of operational processes for the information system in accordance with FAA, NIST 800-53 (as amended), federal government-wide laws, regulations, policies, procedures, and standards.

5) Establish audit trails, ensuring review, and making them available in accordance with FAA, NIST 800-53 (as amended), federal government-wide laws regulations, policies, procedures, and standards.

6) Participate and support in the Authorization to Operate (ATO). Attending meetings, providing system demonstrations and respond to action items.

7) Lead and support the creation and updating of security documentation such as but not limited to:

a. Review of the Executive Summary for the ATO

b. System Characterization Document (SCD)

c. Information System Contingency Plan (ISCP)

d. Incident Response Plan (IR)

e. Interconnection Document Agreement (ICA)

f. Data Sharing Agreements (SDA)

g. Configuration Management Plan (CMP)

h. System Security Plan (SSP)

i. Privacy Threshold Assessment (PTA)

j. Privacy Impact Assessment (PIA)

k. Privacy Continuous Monitoring (PCM)

l. Risk Assessments, Memorandums of Agreement/Understanding

m. Security Impact Analysis (SIA)

8) Ensure all hardware, software, and systems/applications meet and conform to the current version of FAA security standards and guidelines by working with FAA security team.

9) Respond to and remediate all Plan of Action and Milestones (POAMs), and audit findings.

10) POAM spreadsheet – Review and update the POAM spreadsheet provided by the FAA on a quarterly basis.

11) Document the system.

a. System architecture/technical design

b. Technical system configuration instruction

c. Technical system recovery instruction

d. Standard operating procedures (SOPs)

12) If applicable, request and respond to security scan findings and work with security teams to remediate findings above the operating system for all supported environments.

13) Comply with directed mandates to protect and defend information systems from recurring security threats or in response to real-time vulnerabilities.

14) Review and respond to system data calls.

15) Coordinate with product vendors, to provide and apply tactical application patching in defense of real-time vulnerabilities, if applicable.

16) Participate in FAA mandated Cybersecurity and Privacy Training and provide proof of completion.

17) Disaster recovery planning. Provide a disaster recovery plan with redundant capabilities, and an acceptable annual IT security audit. Ensure all systems are backed up and can be restored daily. After restoration of the production system or data due to an event, the Contractor must ensure that all components of the systems are operational and available.

I. Should the need arise for application-centric issues a subject matter expert (SME) may be needed. This encompasses all support needed to keep the application operational.

J. Hosting Support-The Contractor must assist the FAA in establishing a cloud environment with the platform vendor. The Contractor must make recommendations for storage and compute capacities as well as license type needed. This does not include the software licensing or storage fees-those will be provided through a separate contract.

K. The Contractor must also maintain issues, additional features, and new requirements backlogs which will be used to develop future requirements.

L. Onboarding of new users, including license management, creating accounts, assigning access and any other activity for the user to be functional in the system.

M. Support the creation of the following Appian environments: Development (if applicable), Test (UAT), and Production.

N. The migration of any changes into development, UAT, and production environments and any other environments that may have been created.

O. The Contractor is responsible for maintaining continuity between all environments specifically Test and Production. Best practices for refreshing the Test environment from the Production environment must be established. The Test environment should be refreshed from the Production environment two times annually as a minimum.

P. Operations and performance monitoring of the system across all environments (development, test, and production).

Q. Bug fixes and troubleshooting of each of the systems/environments (development, test, and production).

R. Testing. The Contractor must thoroughly test the system prior to conducting User Acceptance Testing (UAT) with comprehensive user group. All enhancements and modifications must be made in a non-production environment and receive FAA customer approval through testing prior to release to production.

S. Develop test plans/scripts and work with FAA's Information Technology staff to test configuration/code for all environments.

T. System must have a 90-day lockout for inactive accounts.

U. The Contractor must use FAA Enterprise tools including but not limited to: Jira, Confluence, Bitbucket, and the Microsoft 365 Office Suite for project management and administrative activities such as requirements gathering, backlogs, and incident management.

V. Migration of any changes from development to test, and finally production.

W. The Contractor will maintain a risk register that will be updated monthly.

X. Reporting - As required on an ad-hoc basis, no more than 12 times a year, the

Contractor will assist with reports for FOIA, Congressional requests, requests from other Lines of Business (LOBs) or Staff Offices (SOs), Agencies and other such requests.

Y. On a monthly basis the Contractor will review the system logs for suspicious or unusual behavior, and they will document that review in a manner sufficient to satisfy security requirements.

2.7. Task 7 – Transition Support

The Contractor must perform transition activities that will ensure a seamless transition of Appian LCAP and clause automation operations and maintenance to government personnel and/or successor contractor. The services under this contract are vital to the Government and MUST continue without interruption upon contract expiration. The transition activities must provide comprehensive knowledge transfer to government personnel and/or successor contractor regarding system operations, maintenance protocols, and best practices and establish a support framework for ongoing operations post-transition. The government and/or contract successor will be provided no more than a 30-day transition period.

If applicable, the Contractor must perform the following transition activities:

A. Develop a detailed 30-day Transition Plan that outlines key activities and timelines. The plan will also include details to minimize disruption and start up requirements while also considering recruiting, hiring, training, and security limitations, and must consider any other special consideration of the prospective provider.

The Transition Plan must also address at a minimum, the following:

1) Overall timelines outlining the 30-day phase-in process.

2) Mechanism(s) used to ramp up to required staffing levels, meeting specific qualifications, and education requirements.

3) Number and position title(s), including resumes, of all personnel known at the time proposal was submitted to the Government.

4) Steps that address and meet contractual roles and responsibilities.

5) Arrangements for any needed orientation or cross-training of respective staff to ensure quality of performance.

6) Ensure all equipment requirements are identified and in place to meet the conditions of the contract.

7) Have a designated person(s) to respond quickly and identify solutions based on unanticipated problems arising during the transition period.

8) Inventory government furnished equipment.

B. Identify and assess risks associated with the transition process and develop mitigation strategies.

C. The Contractor must provide comprehensive knowledge transfer to government personnel and/or successor contractor, including training sessions and documentation, to enable continuation of operations and maintaining of FAST website, Appian LCAP, and associated Appian modules (i.e. clause automation).

D. Develop Transition Documentation, including but not limited to:

1) System architecture diagrams.

2) Maintenance procedures and troubleshooting guides.

3) User manuals for the LCAP inclusive of business process workflow management, clause automation features, and FAST website.

E. Ensure that all data generated and maintained as part of the FAST Modernization effort is adequately backed up and securely transferred to government’s designated storage.

F. Schedule Transition Meetings to align parties on objectives, deliverables, and expectations. The meetings should cover the following:

1) Overview of Appian LCAP functionalities and architecture.

2) Operational procedures for managing the platform and clause automation.

3) Best practices for maintaining and troubleshooting system performance.

G. Facilitate the transfer of all operational responsibilities to government personnel and/or successor contractor, including:

1) Access control and user management.

2) Monitoring system performance and reporting metrics.

3) Incident management and response protocols.

H. Ensure government personnel and/or successor contractor is equipped with necessary tools and access to support resources.

I. Provide a defined period of post-transition support, including:

1) Availability for answering questions and resolving issues.

2) Follow-up sessions to address any challenges encountered during the transition phase.

3. DELIVERABLES

Task 1 – Project and Contract Management

Deliverable Description Delivery Delivery Date

Kick Off Meeting Project kickoff meeting agenda and meeting minutes

Status Meetings Meeting agenda Meeting minutes Updated action items list

Agile Project Management Plan

Outline of the specific strategies, practices, and activities that will be employed to manage the software development process

Project Management Plan

The plan will serve as the operational bases for the project

Master Schedule Includes all tasks (both Contractor and government), deliverables, and milestones necessary to complete the implementation of the FAST solution.

Reflects task begin and end dates, interdependencies, and resource requirements. Must be approved by COR and Program Manager.

Quality Control Plan

Plan to ensure that the performance standards identified in the PWS are met

Risk Management Plan

Plan addresses risks, their potential impact to a program

Monthly Status Report

Detailed listing of the monthly activities

Project Management Review

Monthly presentation of the current state of the project

Invoices

Task 2 – Data Conversion and Migration

Deliverable Description Delivery Delivery Date

Content Inventory Report

Content Assessment Report

DITA XML Files

Populated web-based storage platform with DITA XML files

Task 3 – Development of Appian LCAP Application

Deliverable Description Delivery Delivery Date

Workflow Requirements Document

A detailed document outlining the gathered requirements for the business process workflows.

Developed Workflows

Functional business process workflows implemented in the Appian LCAP

Task 4 – Testing Support

Testing Plan

Test Report A report summarizing testing results, including any issues identified and their resolutions.

Task 5 – Training Support

Deliverable Description Delivery Delivery Date

Training Plan Complete plan with strategy for developing and implementing effective training sessions aimed at enhancing participant skills and knowledge

Training Schedule Detailed schedule with dates, training delivery topics, and target audience

Instructional Materials

Complete training materials, including presentations and exercise documents

Training Schedule and conduct training sessions

Post Training Evaluation Report

Post-training evaluation report summarizing feedback and participant performance

Task 6 – Operations and Maintenance

Status Meetings Meeting agenda Meeting minutes Updated action items list

Security Documentation

POAM responses as required

Task 7 – Transition Support

Transition Plan Outline of the specific strategies, practices, and activities that will be employed to manage the transition process

Transition Documentation

System architecture diagrams, Maintenance procedures and troubleshooting guides.

User manuals, etc.

Transition Meeting Transition Meeting Agenda and Meeting minutes

4. PERSONNEL

4.1 Key Personnel

A. The personnel and/or facilities as specified below are considered essential to the work being performed hereunder and may, with the consent of the contracting parties, be changed from time to time during the contract.

B. Prior to removing, replacing, or diverting any of the specified personnel and/or facilities, the Contractor must notify in writing, and receive consent from, the Contracting Officer reasonably in advance of the action and must submit justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on this contract.

C. No diversion will be made by the Contractor without the written consent of the Contracting Officer

D. The key personnel under this contract are:

Labor Category:

4.1.1 Program/Project Manager

4.1.2 System Solution Architect

4.1.3 Software Developer

4.1.4 System Administrator

4.1.1 Program/Project Manager

The personnel proposed for the Project Manager (PM) role will serve as the Government’s point of contact (POC) and provide supervision and guidance for all contractor personnel assigned to this contract. The PM is ultimately responsible for the quality and efficiency of contract performance to support the requirements. The PM must manage the overall contract and coordinate tasking to contractor personnel, supervise on-going technical efforts, and manage overall contract performance. The PM will serve as the contractor’s authorized interface with the Government CO, COR, Project Manager, and Technical POC for the contract. The PM must have the following qualifications/certifications: An active PMI Project Management Professional (PMP®), PMI Program Management Professional (PgMP®), or a PMI Agile Certified Practitioner (PMI-ACP®) Certification at the time of proposal submission.

It is required that the PM has the following qualifications as a contract/task order

PM:

A. 5 years in IT Project Management and Application Development with Appian project management experience.

B. 3 years working with Appian.

C. Appian certification (Appian Certified Analyst or above).

D. Bachelor’s degree.

E. Formal training or certification in Agile software development methods at the time of proposal submission.

F. Demonstrated experience in using an Agile development framework to gather requirements, estimate tasks, distill business requirements into incremental features, and demonstrate new functionality to product owners.

G. Demonstrated ability to orchestrate and communicate the management of technology scope and risks.

H. Demonstrated experience utilizing an Agile project management tool such as Jira to plan, execute, and measure projects.

I. Demonstrated experience ensuring that the technical expectations of deliverables are met thru Agile processes; additionally, support the continuous improvement of those processes.

J. Demonstrated experience with management, adequate staff utilization, and supervision of employees (including subcontractors) of various labor categories and skills. Specifically, managing teams that will coordinate with the Government and work with other contractors to support an Agile environment with small teams of developers, managing the transformation and consolidation of systems in support of improving efficiency, data quality, and service delivery.

K. Demonstrated written and verbal communication skills, including experience in presenting matier to senior Government officials.

L. Managerial and leadership experience skills.

4.1.2 System Solution Architect

The proposed contractor personnel supporting the FAST Modernization project must have a broad range of technical knowledge and solution strategy expertise in order to advise on the best technical solution for stakeholder requirements.

Contract personnel supporting the operating environment must possess general knowledge of other cloud technologies, platforms, and tools in order to determine when Appian is the best option for satisfying a business requirement.

Additionally, the contractor personnel will be coordinating with the DevOps and continuous integration teams on the implementation of the architecture and will provide technical leadership.

It is required that the proposed staff has the following qualifications while working as a System Solution Architect:

A. Minimum 5 years’ experience working with Appian.

B. Appian certification (Appian Certified Lead Developer preferred) with multiple

Appian implementations/staff positions in the Solution Architect role.

C. Experience creating and delivering Appian solutions using SAIL or "Self

Assembling Interface Layer."

D. Possess strong knowledge of Appian functionality and configuration capabilities, able to lead Appian solution design efforts.

E. Support an Appian environment with 2000 + users.

F. Demonstrated experience, in the context of an Agile continuous integration/deliver model, with the offerors proposed architecture design and solution components.

G. Has training/certification in Agile methods.

H. Demonstrated experience, in the context of an Agile continuous integration/delivery model, designing platform architectures for a Cloud environment.

I. Strong written and oral communication skills required.

4.1.3 Software Developer

The proposed contractor personnel developing in the operating environments must have a broad range of technical knowledge and solution strategy expertise in order to advise on the best technical solution for stakeholder requirements.

Contract personnel is responsible for design, development, testing and deployment of software. Contract personnel supporting the operating environment must possess knowledge of other cloud technologies, platforms and tools in order to determine when Appian is the best option for satisfying a business requirement.

A. Minimum 5 years’ experience working with Appian.

B. Appian certification (Appian Certified Senior Developer).

C. Demonstrated comprehensive aspects of systems and software development from analysis.

D. Demonstrated feasibility analysis, problem definition, requirements development, and solution development.

E. Demonstrated solutions by developing documentation, flowcharts, layouts, diagrams, charts, code comments and clear code.

F. Prepare and install solutions by determining and designing system specifications, standards, and programming.

G. Develop software solutions by studying information needs, conferring with users, studying system flows, data usage and work process.

H. Develop and configure applications.

I. Provide support in developing the defined architectural utilizing development processes and methods.

J. Provide subject matter expert to implement interfaces between applications and data stores.

K. Technical understanding and experience associated with implementing and maintaining applications.

4.1.4 System Administrator

The personnel proposed as the System Administrator must have significant knowledge and experience in conducting routine Appian system administration tasks.

Systems Administrators are responsible for maintaining system efficiency:

A. Must have experience in maintaining troubleshooting of a wide variety of systems and networks including Appian.

B. Appian certification (Appian Certified Analyst or above).

C. Must have knowledge on several debugging protocols and processes.

D. Must be able to troubleshoot problems and issues identified by customers and implement corrective actions within the agreed timeframe.

E. Optimize system operation and resource utilization and perform analysis and planning to resolve incidents.

F. Manage user accounts and permissions sets.

G. Provide assistance to users in accessing and using the systems and application components.

H. Manage configurations as necessary while following configuration and change management best practices.

I. Responsible for ensuring the timely process through which problems are controlled. Includes problem recognition, research, isolation, resolution, and follow-up steps

Must have the following:

A. Bachelor’s degree B. 3 Years of experience with Appian administration

4.2. Personnel Security Requirements

A. Security Clearances/Approved Personnel. All Contractor employees working on this contract may be subject to a…