NISC Enterprise Support Tasking (NEST)

ent and deployment of new systems to support the NISC V contract. The Contractor must also 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 encompassing planning, design, and development for the NIMS/CMIS systems, KITT Financial Database (KFDB) reporting database, and NISC Invoice Approval Tool (NIAT) and future systems to support NISC V contract; Document NIMS/CMIS (including test, development, production and mirror instances) code revisions, testing, software upgrades, and implementation activities; Operations support for NIMS/CMIS for both NISC and TSSC by extracting and downloading Delphi and PRISM data into NIMS/CMIS for use by NISC and TSSC customers; Create integrated reports in KFDB to include funding and other pertinent information from FAA Systems (PRISM/Delphi); Maintenance support for the NIMS/CMIS application, i.e., troubleshooting, correcting data inaccuracies, responding to customer requests to make routine changes, and correcting 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 financial dashboard (NED: NISC Enterprise Database) from the Contractor�s financial systems into NIMS based on requirements provided by the PMO to provide financial metrics such as Task Order EAC (Estimate At Completion), ETC (Estimate to Complete), Earned Value Measurement (EVM), 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 system scans, resolution of cyber security issues and the associated updates to documentation such as System Characterization Document (SCD), System Security Plan (SSP), and Plan of Action & Milestones (POAM) fixes, and any other documents required by FAA�s cybersecurity team; Comply with FAA IT policies and guidelines to include PIV/My Access security authentication layer integrated into NIMS/CMIS; Transition-out NIMS/CMIS support to a potential new vendor over three � six months upon contract termination; Training NIMS/CMIS users and developing/updating User Guides as requested by PMO; Support implementing systems for future NISC V contract, while complying with all requirements from FAA Cyber Security organization. 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. The transition period is intended to provide the Contractor with time to perform due diligence functions associated with NIMS Capabilities. This includes the inventory of all systems, software, and third-party components that make up NIMS, as well as those systems and software that interface or integrate with it. 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 does not initiate and comply in accordance with transition activities as outlined in its transition plan, any extra costs arising from the delay in meeting the timeline will be the Contractor's responsibility. 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 Recommend and Implement systems for supporting the upcoming NISC V contract. 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.4. The Contractor must provide program/project management support for NIMS/CMIS as required below upon direction from PMO: Conduct and coordinate tasks assigned to manage the project; Provide required briefings, reports, business process models, workflow diagrams, analyses, plans, schedules, and other required documents needed to support the functions of the NIMS/CMIS projects; Provide work breakdown structures for managing the project and scope; Provide coordination and information exchange with stakeholders via meeting attendance and project status information; Provide support to the FAA�s Project Manager in the development, coordination, and review of plans and documentation necessary for the development, integration, and implementation of NIMS/CMIS and its associated system applications. This includes staffing plans, change proposals, implementation plans, documentation, analyses, and training plans, drafting notices/policies/directives for system operation, 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; Develop and maintain project schedules for implementation; Provide ability to track costs, budget and provide requisite financial control reports and variance reporting to the PMO; 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); Ensure requisite standards and metrics are applied for quality product delivery Develop and maintain a detailed plan to manage risks Provide details on the methodology and purpose of tools that will be used to manage the project; Support the NIMS/CMIS projects by participating in meetings as required and providing requisite action item tracking and consolidated monthly activity reports. 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: asset management which involves the management of current NIMS/CMIS systems