Inactive Total Small Business Set-Aside (FAR 19.5)

**PLEASE REFER TO SECTION L.8 OF SIR FOR INFORMATION ON LIVE DEMONSTRATION & QUESTION SUBMITTALS** ***THIS SOLICITATION IS SET-ASIDE FOR SMALL DISADVANTAGED BUSINESS (SDB) CONCERNS ONLY*** C.1 STATEME... **PLEASE REFER TO SECTION L.8 OF SIR FOR INFORMATION ON LIVE DEMONSTRATION & QUESTION SUBMITTALS** ***THIS SOLICITATION IS SET-ASIDE FOR SMALL DISADVANTAGED BUSINESS (SDB) CONCERNS ONLY*** C.1 STATEMENT OF WORK C.1.1 Background The AJW-2 Directorate, AJW-2131 Implementation Services Group, provides technical, engineering, financial, budget, and management support to Technical Operations programs through the use of the Technical Support Services Contract (TSSC) and NISC. These are task order contracts that present contract managers with the difficult task of managing the financial aspects of contracts when there is a constantly high volume of task orders. This is compounded by the fact that the FAA financial systems, PRISM and Delphi, are not integrated systems. This results in a high risk of errors in funding task orders and tracking funds that have been committed, obligated, or expended. This work requires a support contractor that will serve as an independent quality control Subject Matter Expert (SME) capable of providing oversight of the development, documentation, and testing of the software. This includes, but is not limited to, making recommendations regarding the selection of software architecture and software development applications, reviewing coding to ensure compliance with “best practices,” useable documentation, and developing and executing software testing plans. The support under this contract will provide independent quality assurance, quality control, operations, and maintenance as needed and directed by the Implementation Services Group. C.1.2 Scope of Work The Contractor must provide independent quality assurance and quality control of the currently operational NIMS/CMIS systems and its software rewrite efforts. This effort requires solution development, integration, database upgrading, and automation with other associated systems as stated within subsection C.1.3. Offeror will maintain NIMS/CMIS security certifications required to operate the software and its associated server hardware. In addition, the Contractor must provide transition support to any potential new vendor at the contract’s end. C.1.3 Objectives The objectives of the NEST’s Scope of Work are to provide the following support: Software Architecture development oversight for the NIMS/CMIS program software development, KITT Financial Database (KFDB) reporting database, and NISC Invoice Approval Tool (NIAT); Document NIMS/CMIS (including test, development, and mirror instances) code revisions, testing, software upgrades, and implementation activities; Operations support for NIMS/CMIS for both NISC and TSSC through the workday downloading of Delphi and PRISM data into NIMS/CMIS to be used by NISC and TSSC customers; Create integrated reports in a KFDB to include funding and other pertinent information from FAA Systems (PRISM/Delphi); Maintenance support for the NIMS/CMIS, i.e., troubleshooting, correcting data inaccuracies, responding to customer requests to make routine changes, and correct defects as they are identified; Maintain and update CMIS, which is dormant. CMIS needs to be available to users during contract closeout and as requested by Project Management Office (PMO), Contracting Officer Representative (COR), and Contracting Officer (CO); System upgrades include developing and integrating EVM financial dashboard (NED: NISC Enterprise Database) from the Contractor’s financial systems into NIMS. This includes, but is not limited to projecting Task Order EAC (Estimate at Completion), ETC (Estimate to Complete), and other financial metrics; Support and maintain the current level of security certification by interfacing with the FAA Cyber security organization and conducting the necessary security threat detection and the associated documentation such as System Characterization Document (SCD), System Security Plan (SSP), and Plan of Action & Milestones (POAM) fixes; Comply with FAA IT policies and guidelines to include PIV/My Access security authentication layer integrated into CMIS; Transition NIMS/CMIS support to a potential new vendor over three – six months; Training CMIS/NIMS users and developing/updating User Guides as requested by PMO C.2 TRANSITION PLAN – PRIOR TO CONTRACT START The Contractor must submit a Transition Plan for execution during the transition period. The Plan must not be materially altered without the Government’s consent. The transition period will begin upon execution of contract award unless a later date is specified. The Contractor must propose the length of the transition period but must not exceed 120 days. This transition period is intended to provide the Contractor time to perform due diligence functions associated with NIMS Capabilities, which includes the inventory of all systems/software and 3rd Party components that make up NIMS as well as the (systems/software that it interfaces/integrates with) – see Exhibit 2 NIMS Capabilities Document & Diagram. Contractor will be paid for transition costs in accordance with its pricing proposal. Transition costs are defined as all costs expended during the transition period that are necessary and reasonable to assume operation, maintenance, and responsibility for the system. The Contractor’s transition plan must permit sufficient time for a deliberate and orderly turnover of the NIMS system but must not exceed 120 days. The Contractor must participate in technical discussions with the outgoing contractor for the purpose of ensuring a smooth transfer. If the Contractor fails to begin its transition activities in accordance with its transition plan, any resultant additional transition costs incurred as a result its failure to meet its timeline will be absorbed by the Contractor. The Contractor will only be compensated by the Government when the failure is not attributable in any way to the acts or omissions of the incoming Contractor. C.3 ACTIVITIES The Contractor must conduct the following tasks as outlined here and within the following subsections in support of systems documented within subsection C.1.3: Independent quality assurance and quality control As needed operations and maintenance of the accepted NIMS/CMIS software Data collection and analytical support Implementation and integration of financial system tools; and Maintenance and automation support C.3.1 Task 1 – Task Management Task management involves the activities listed below which are in direct support of the Statement of Work. The program management functions associated with specific tasks will be found in subsections C.3.1 through C.3.3. The Contractor must provide support NIMS/CMIS as required below: Conduct and coordinate tasks assigned per the requirements provided by the PMO; As needed by the PMO, provide required briefings, reports, white papers, business process models, workflow diagrams, analyses, plans, schedules, and other required documents needed to support the functions of the NIMS/CMIS projects; Provide coordination and information exchange with stakeholders via meeting attendance and project status information; Provide support to the Project Manager in the development, coordination, and review of studies, plans, and documentation necessary for the development, integration, and implementation of NIMS/CMIS and its associated system applications. This includes staff studies, change proposals, implementation plans, documentation, analyses, and training plans, drafting notices/policies/directives for system operation, Investment and Business Case analysis, Solution assessment, and validation results as required; Develop and implement NIMS/CMIS Plans to include software development and/or upgrade as well as any necessary hardware upgrade or modification (currently anticipating dual NIMS/CMIS Systems and dual firewalled servers); Develop and execute a plan to transition NIMS/CMIS support from the current vendor to any potential future vendor over a three to six-month period without operational impact on the systems; Develop and maintain project schedules for implementation; Support the development of project management plans and other required documentation. This support includes project management consistent with expected Project Management Lifecycles (PMLC); Management/project plans across expected Software Development Lifecycles (SDLC) and methods (e.g. waterfall, agile, iterative development models); Support the NIMS/CMIS projects in the preparation for and participation in meetings. This support includes, without limitation, the following: Day to day activities related to office logistics, program, project, financial planning and execution, record keeping, and action item tracking; Support the NIMS/CMIS projects in consolidating project information to be reported in the Monthly Activity Report; and Adhere to proven and repeatable software development practices that are approved and recognized in the industry as well as recommended by FAA IT standards. This support also includes: facility support and asset management which involves the design and installation of NIMS/CMIS systems, connectivity and installation support, site surveys, relocation or consolidation, comprehensive installation planning of NIMS/CMIS systems, systematic tracking of hardware (H/W) and software (S/W) assets, inventory, H/W specifications, maintenance, tagging and tracking, upgrading, disposal; S/W end-user license agreement (EULA) acquisition and management, S/W and H/W Maintenance Agreement acquisition and management, preventive maintenance, and asset reports. C.3.2 Task 2 – Software Architecture, Design, Implementation Support Assist ATC Facilities staff in support of the currently operational NIMS/CMIS comprehensive operational software and the associated maintenance of accepted databases and web-enabled financial systems in support of the mission of the Implementation Services Group. The current application stack includes but is not limited to: Coldfusion, AWS, DBNetsuite, Fusion Charts, Java, Oracle, PhP, SaML. The Contractor must: Develop draft and final software architecture and design and implement the AJW-2131-approved architecture and design through software code. This support includes without limitation, the following: Initial Operational Capability (IOC) development and Full Operational Capability (FOC) completion; solution development; software code; Application Programming Interface (API); Microservices; user manuals and technical documentation; systems/software engineering; Test Driven Development (TDD); development, demonstration, and transition; web application design and development; enterprise architecture and application development and support for the hundreds of users across multiple FAA facilities/locations; debugging; Graphical User Interface (GUI) development and documentation; modeling and simulation; data protection and integrity procedures; multi-datacenter aware solutions; platform-based development; development of prediction, projection, probable resource(time/funds) run-out algorithms; Provide input for a recommended software architecture that supports the project’s goals and objectives and meets the customers’ requirements, including required software and hardware upgrades. This support includes, without limitation, the following: adhering to FAA IT recommended Enterprise Risk Management (ERM) Framework; Enterprise Architecture Framework; Data Governance (DG); Architecture Governance Board; IT Service Management (ITSM); Research support; Cloud Solution Strategy (including support for Cloud Architecture & Planning, Cloud Migration, Cloud infrastructure operations & service management); Technology standards; Solution standards; Product roadmaps; Technology roadmaps; Technology refresh and legacy systems modernization strategy; At the contract’s end. develop a plan to transition NIMS/CMIS support from the Contractor to a successor; Review and comment upon the software development contractor’s project management plans and compare them to the associated schedules that include the dates specified in the deliverables; Review and comment upon the Document Management and Change Management strategies in the software development contractor’s Project Management Plan; Review and comment on the software development contractor’s test and evaluation (T&E) plan to ensure that T&E activities are included in the Project Management Plan. This support as applicable includes, without limitation, the following: Requirement Traceability Matrix (RTM); Functional Testing (e.g., Beta/acceptance testing; Integration testing; Interface testing; Regression testing; Sanity testing; Smoke testing; System testing; Unit testing); Non-Functional Testing (e.g., Compatibility testing; Compliance testing; Install testing; Load testing; Localization testing; Performance testing; Recovery testing; Reliability testing; Security testing; Stress testing; Usability testing; Volume testing); Independent Verification & Validation (IV&V); Quality Control (QC); Quality Assurance (QA); Test automation; Testing strategy; Security testing; Support progress reporting through Status Reports, Action Items, and Meeting Minutes; Conduct and participate in Joint Applications Development (JAD) meetings; Review and provide comments on design diagrams and software code to ensure that they comply with the proposed design, best practices, and industry benchmarking standards; and Perform thorough requirements gathering, management and analysis to track and trace each requirement through implementation, test, and deployment cycles as well as mapping it back to the project mission statement and the organization’s goals and objectives. This support includes, without limitation, the following: Requirements/Scope Management; Enterprise analysis; Functional requirements; Specifications; Use case development; Agile requirements; Process models; Context diagrams; Functional decomposition; Security requirements; User requirements; User acceptance criteria; Non-functional requirements; Regulatory requirements; Service requirements; Process requirements; Product requirements; Usability requirements. Provide Acquisition and logistics support to procure/install/maintain all the necessary hardware, software and power/network cabling such as Cat-6 cables, C13/C14 power rack cables, zip ties, extension cords. The support includes, without limitation, transporting hardware to data centers and seating them in designated cage/racks, as well as follow protocols in decommissioning the end of the lifecycle hardware. The support also includes acquiring and commissioning the necessary account services with cloud-based service providers that are authorized and approved by FAA IT so that appropriate cloud virtual computing instances are available for NIMS/CMIS services to be available to end users in a seamless manner. C.3.3 Task 3 – NIMS/CMIS Operations and Maintenance, User Training, Helpdesk and Security Management Support NIMS/CMIS Operations and Maintenance consist of those activities required to download contract specific data from PRISM and Delphi and make it available to financial personnel managing the finances on participating contracts. The data must be presented in a format that is readable by the established user interfaces. The Contractor must undertake all activities required to manage and maintain helpdesk tickets and provide the required user training. The Contractor is responsible to respond to all the data calls and submit compliant documents, conduct and attend presentations, briefings that are required to obtain the Authority To Operate (ATO) status for the NIMS/CMIS systems as directed by the FAA IT and associated Cyber Security related policies and personnel in support of the AJW-2131 management. The Contractor must: Support the day-to-day operations of NIMS/CMIS with contract specific data that is accessible to only those personnel with authorized access. This support broadly includes, without limitation, the following: Multi-data center primary and disaster recovery support, connectivity and installation support, archiving and backups, configuration documentation, image creation, initial configuration, installation, integrating, optimization, patching and updating, recovery, relocation, scripting, system/software integration and migration, system administration, platform administration, troubleshooting, tuning, upgrading, (X)aaS implementation/integration/support (“(X)” meaning Software, Platform, Infrastructure, etc.), hardware support, Database Management Systems (DBMS) administration and support, data migration support, change management and reporting, configuration management and documentation updates, emergency services, continuity and disaster recovery, inspections and corrections, encryption and encryption key management, cloud computing, optimization evaluations, server rack energy usage assessments, utilization reporting, decommissioning, technology transition and data migration support with data management, Tier 2 and Tier 3 application support, incident management, helpdesk operations, training, existing application enhancement and sustainment Plan of Action and Milestones (POA&M), security vulnerabilities remediation, and application/infrastructure performance monitoring; Manage the NIMS/CMIS database, its interfaces, and associated data access tools, including as related to required software and hardware upgrades; Maintain NIMS/CMIS related financial data access tools; Produce and maintain financial data reports database and access tools; Perform routine and ad hoc maintenance on the back end of the NIMS/CMIS application to ensure its viability as a financial tool; Perform daily downloads of information from the FAA’s Delphi and PRISM financial systems into the NIMS/CMIS for both NISC and TSSC; Analyze the downloaded information from Delphi and PRISM to identify and correct errors in the data and its placement in the tables; Make updates and changes to user displays or the method of display as directed by the PMO; Provide 2nd level technical support to developers and Financial Analysts on all supported financial applications; Provide assessment of the impact of FAA Security Policies, design remediation strategies and integration solutions within 60 days; Draft documentation required to maintain NIMS/CMIS ATO status to include Cybersecurity Assessments and Accreditation that are required to be performed year-round and to reply to information requests from FAA Security Offices based on deadlines established by AJW-2131 Program Office and FAA IT. This support includes, without limitation, Cloud security assessments, code auditing; cybersecurity and information assurance, intrusion detection, event detection and monitoring virus detection, inspections and associated assessment corrections or remediations or justifications, security integrated with development (DevSecOps), FAA PIV security authentication integration, software auditing, and Continuous Diagnostics and Mitigation (CDM). C.3.4 Task 4 – NIMS and Associated Systems (NIAT, NED, KFDB) Modernization Emerging technologies and changes to mission may occur at any time, the Contractor is expected to demonstrate flexibility and problem-solving skills to adapt and provide for seamless and continuous operations. The Contractor must review and evaluate current processes, procedures, and systems for any potential inefficiencies, weaknesses, etc. and propose advancements and/or solutions to modernize NIMS and the associated systems to keep in line with technology and process upgrades over time, as requested by PMO. This task may involve, but is not limited to: Upgrade the Task Order Summary on the homepage to: Indicate the oldest funds year allocated to the task order Integration of Notices to Proceed (NTPs) to the Task Order Summary on the homepage to indicate if a Task Order is associated with an NTP in order to facilitate the Task Order Approval Process. Add rules to restrict Task Order revision to align with FAA financial funding policies. Upgrade processes related to the Performance Evaluation and reports as requested by PMO Modernize and update processes with the Financials module in NIMS: PR Coversheet process and integration with Delphi/PRISM data to validate the PR data from PRISM. Allocations tab for payment override (aka priority payment). Transfer funds module and process to integrate with payment of the monthly invoice Automate pop-up notification to users for overfunding task orders. Upgrade and change rules for monthly invoice payments to enable users to select the PR, Line #, and amount to be paid on each invoice prior to generation of payment. Add or update filters, criteria, and new reports as requested by PMO. Update Charts/Dashboard to integrate existing and new reports. As available and required by FAA Finance Group, update fund codes in the data tables to identify fund types Create new fund types as mandated by FAA policies As required automate process emails to users for NTP, Invoice, Task Order workflows **PLEASE REFER TO SECTION L.8 OF SIR FOR INFORMATION ON LIVE DEMONSTRATION & QUESTION SUBMITTALS** ***THIS SOLICITATION IS SET-ASIDE FOR SMALL DISADVANTAGED BUSINESS (SDB) CONCERNS ONLY***