NEST RFI_Market Survey.pdf

RFI/Market Survey | 1 October 2023

Request For Information (RFI)/Market Survey

I. CONTRACT OPPORTUNITY

+ Name: NISC Enterprise Support Tasking (NEST) (currently under Contract 693KA9-25-C-00020) + Notice ID: RFI ID: 693KA9-26-R-00003 + Related Notice: N/A + Department/Ind. Agency: TRANSPORTATION, DEPARTMENT OF + Sub-tier: 6920 FEDERAL AVIATION ADMINISTRATION + Office: AAQ-410

II. GENERAL INFORMATION

+ Contract Opportunity Type: (Original)/RFI/Market Survey + Original Response Date: December 16, 2025

III. CLASSIFICATION

+ Product Service Code: DA01 – IT & Telecom – Business Application/Application Development Support Services

+ NAICS Code: 541511 Custom Computer Programming Services + Place of Performance: FAA Site/Vendor Location

IV. DESCRIPTION

The Federal Aviation Administration (FAA) NAS Integration Support Contract (NISC) Program is issuing a Request for Information for “NISC Enterprise Support Tasking (NEST)” to the AJW-213, NISC Program Management Office (PMO). Please see attached documents for detailed instructions.

The acquisition strategy for the procurement has not been determined at this time; However, either an unrestricted competition or a set-aside will be chosen depending on the responses to this RFI Notice /Markey Survey.

a) This is not a Screening Information Request or Request for Proposals of any kind;

b) The FAA is not seeking or accepting unsolicited proposals;

c) The FAA will not pay for any information received or costs incurred in preparing the response to the market survey; and

d) Any costs associated with the market survey submittal are solely at the interested vendor’s expense.

The purpose of this RFI is to solicit statements of interest and capabilities statements from small businesses ((a) expressly certified by the Small Business Administration (SBA) for participation in SBA’s 8(a) program; (b) Service-disabled veteran-owned small business (SDVOSB); (c) Women-Owned Small Business (WOSB); (d) Historically Underutilized Business Zone (HUBZone) small business; and (e) Small business (SB)), capable of providing the services outlined in this document, in the timeframe stated in this document. The responses to this RFI will help determine the acquisition strategy and whether adequate competition exists to set aside the competition among small businesses. This notice is for informational and planning purposes only. This notice does not restrict the FAA to the ultimate acquisition approach it may take in connection with this requirement, nor does it restrict changes to the SOW.

RFI/Market Survey | 2 October 2023

Please see attachment 2 for specific information regarding the contents of the 1.

Cover Sheet; 2. Capabilities Statement & Market Information; 3. Background Experience.

Note 1: The FAR references cited in SAM.gov are not applicable to the Federal Aviation Administration (FAA) as the FAA has its own policies and guidance referenced in the Acquisition Management System (AMS).

V. ATTACHMENTS

Attachments

1. Draft Statement of Work (SOW)

2. NIMS Support Submission Instructions

3. NIMS Support Contractor Capabilities (20 elements)

693KA9-26-R-00003

Part I – The Schedule

Section C – Statement of Work

PART I - SECTION C

DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

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 using the NAS Integration Support Contract (NISC IV Contract) and Technical Support Services Contract (TSSC).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 potential for errors in funding task orders and tracking funds that have been committed, obligated, or expended, which warrants integration between the NISC IV systems (NIMS/CMIS) and Prism/Delphi. In addition, the NISC IV contract will be transitioned to NISC V contract during the award period, , which will require a new system to support the NISC V contract

This work requires a support contractor that will serve as an independent Subject Matter Expert (SME) capable of providing design, development, testing, deployment and documentation of the software. This includes, but is not limited to, making recommendations regarding the selection of software architecture and software development tools, 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 system design, development 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 and design and installation of new systems to support the NISC V contract, connectivity and installation support, relocation or consolidation of applications in the FAA’s cloud environment, , systematic tracking of hardware (H/W) and software (S/W) assets, inventory, H/W specifications, maintenance, , upgrading, S/W end-user license agreement (EULA) acquisition and management, S/W and H/W Maintenance Agreement, and asset reports; and

• Assist with the identification of business needs and scope, research and evaluate potential options and present recommendations with rationale for implementing a system to support the upcoming NISC V Contract

C.3.2 Task 2 – NIMS/CMIS Operations and Maintenance, User Training, Helpdesk and Security Management Support

The current application stack for NIMS/CMIS includes but is not limited to: Adobe ColdFusion, NetSuite, Fusion Charts, Java, Oracle, PHP, SAML. These applications are currently hosted in AWS Cloud Environment.

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 the system and interfaces, maintain and resolve helpdesk tickets and provide the required user training.

The Contractor is responsible for responding to all the data calls, performing requisite system changes and submitting compliant documents to ensure compliance with FAA’s Cyber Security organization, conduct and attend presentations, briefings and any other meetings 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, while adhering to FAA IT recommended frameworks encompassing but not limited to, Enterprise Risk Management (ERM) framework, Enterprise Architecture Framework, Data Governance (DG), Architecture Governance Board, IT Service Management (ITSM) and FAA Technology Roadmaps. This support broadly includes, without limitation, the following:

o Software architecture and design;

o Solution development and bug fixes;

o System enhancements and maintenance;

o Disaster recovery, archiving and backups;

o Assist with any system decommissioning requirements;

o Patching and updating applications, software upgrades;

o System/Platform administration support, including operating system and database upgrades;

o Cloud management support;

o Management of Plan of Action and Milestones (POAM) and security vulnerabilities remediation;

o Managing the CMIS/NIMS database, its interfaces, Application Programming Interface

(API), Microservices, and associated data access tools, including related software upgrades;

o Maintaining CMIS/NIMS related financial data access tools;

o Producing financial data reports and maintaining requisite database and access tools;

o Recommending and implementing AI solutions to meet reporting requirements for all users o Performing daily downloads of information from the FAA’s Delphi and PRISM financial systems into the CMIS/NIMS for both NISC and TSSC;

o Analyzing the downloaded information from Delphi and PRISM to identify and correct errors in the data and its placement in the tables o Running scripts and refreshing the KFDB database and adjusting KFDB reports if required to meet business requirements, o Coordinating and testing the financial interfaces to comply with any PRISM and

Delphi upgrades and making changes to ensure the interfaces provide requisite data o Enhancing System and reports to comply with policies as required;

o Responding to data calls from the security team in a timely manner;

o Coordinating yearly scanning of the systems with the cybersecurity personnel;

o Addressing and correcting application issues pertaining to scan results and ensuring compliance with FAA’s cybersecurity team;

o Coordinating with FAA IT personnel to resolve scan issues pertaining to the Windows and Database environments;

o Managing POAM in ATOM/SMART systems or any other FAA systems to ensure compliance;

o Procuring and installing SSL certs and licenses as required o Drafting and submitting documentation such as SCD, SSP, etc. and participating in meetings required to maintain CMIS/NIMS ATO status to comply with Cyber Security 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-213 Program Office and FAA IT. This support includes, but is not limited to:

Cloud security assessments;

Code auditing to comply with cybersecurity requirements;

Cyber security 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.

• 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 and provide remediation strategies and integration solutions to ensure compliance;

C.3.3 Task 3 –Systems Support for NISC Contract Transition

The vendor needs to provide system architecture, design, development and implementation support to meet the requirements of the NISC V contract. This support broadly includes, without limitation, the following:

• Assist with the evaluation and documentation of requirements for the new NISC V Contract

• Conduct and participate in Joint Applications Development (JAD) meetings to understand requirements

• Recommend system architecture and design to support the NISC V Contract to meet business requirement, including without limitation, the following:

o Develop draft and final software recommendations, system 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, while 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;

o Perform thorough requirements gathering, management and analysis to track and trace each requirement through development, 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, which also includes acquiring and commissioning the necessary account services with cloud-based service providers that are authorized and approved by FAA IT

• Facilitate development, set-up and deployment of new systems/applications to meet NISC V contract requirements,

• Facilitate setting up the integration between the new system and FAA’s backend systems (Prism/Delphi) for the NISC V contract

• Provide detailed 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;

• Facilitate setting up reporting mechanisms and dashboards to consolidate and analyze data from NISC IV and NISC V contracts

• Coordinate with FAA’s cyber security for compliance and ensure that the new systems are Authorized to Operate within FAA

C.3.4 Task 4 – Transition Plan Transition-IN Plan Contractor must provide a Transition Plan that describes in detail its approach, process, resourcing, any anticipated risks and responsive risk mitigation strategies, and schedule for providing a structured, thoughtful, effective, and orderly transition from the outgoing NEST contractor.

The transition plan at a minimum must address the following areas:

• Transition Plan Contractor Assumptions

• Contractor’s Proposed Team Structure

• Contractor’s understanding of the Transition Plan Scope

• Proposed approach to business process and technology knowledge transfer

• Proposed Transition Plan Schedule

• Proposed Risk Mitigation Strategies in support of Transition

• Proposed Transition Staffing and Resourcing

• Proposed Change Management

Transition-OUT Plan Contractor must develop and execute a plan to transition system support to any potential future vendor without operational impact on the systems.

C.4. END RESULTS/DELIVERABLES

C.4.1 Acceptance and List of Deliverables by Task

The following table provides a list of the required deliverables by task. All deliverables under this contract will be subject to review and inspection by the CO or COR. Inspection, review or approval of deliverables or associated services prior to final acceptance must not be construed as assurance of acceptance of the finished product. Final inspection and acceptance of deliverables or services will be performed by the CO or COR.

Task Deliverable Due Date Acceptance Criteria

1 Reports As required Government Approval

1 Financial Reports and Analysis As required Government Approval

1 Program Management Reviews, Plans, Schedules

As required Government Approval

1,3 Test plans and associated documentation

As required Government Approval

1 Project Schedules As required Government Approval

1 Meeting notes As required Government Approval

2,3 Updated code As required Government Approval

2,3 Database Feeds for both NISC and TSSC Contracts

Each agency systems’ operational Workday, as required

Government Approval

1,2,3 NIMS/CMIS Upgrades As required Government Approval

NIMS/CMIS High Quality Plan for Transition this contract work scope to a potential new vendor

As required Government Approval

1 Monthly Status Report Monthly Government Approval

1,2,3

Updated System Design and Architecture documentation, Database Management documentation and Data Dictionary, Requirements Document, Test Plans, Operations manuals and any relevant transition related documents

Baseline documents within 90 days of contract award and periodic updates thereafter.

All final documents must be submitted before transition.

Government Approval

C.4.2 Transmittal/Delivery

The Contractor must provide electronic copies of files, reports, and deliverables. Acceptable electronic formats are: Microsoft Word, Microsoft Excel, Microsoft PowerPoint, Microsoft Project, and other formats agreed to by the FAA. Hard copies may be delivered if approved by the FAA. The Contractor, as needed, by the government must also follow the Knowledge Service Network (KSN) site protocol to deposit the electronic documents as part of deliverables.

C.5 PLACE OF PERFORMANCE

The principal place of performance will be at FAA’s or Contractor’s facilities. For requirements to be performed at the Contractor’s facility, the facility must be conveniently located to ensure timely access to FAA Headquarters, 800 Independence Avenue SW, Washington, DC 20591.

C.6 TRANSITION/CLOSEOUT PLAN – PRIOR TO CONTRACT END

In addition to the requirements of AMS Clause 3.8.2-11, approximately three months prior to this effort’s end date, the Contractor must provide the following:

• All documentation, as of the most recent revision;

• A transition status report to include a projection for the next 120 days of the program; and

• A close out meeting (to include all key personnel) with the FAA (details to be determined by the

FAA)

C.7 OTHER DIRECT COSTS (ODCs)

C.7.1 Travel

Travel will be required to the annual NISC off-site training.

C.7.2 Material Costs

Purchase of materials is authorized for this effort. When items are to be purchased, the material must be determined to be in direct support of administration or performance or accomplishment of tasks under the Contract by the COR in advance of purchase. Any items purchased under the Contract as a direct cost become the property of the government. Disposal of obsolete equipment must be in accordance with FAA procedures. The Contractor must keep a record of all the approved purchase requests.

C.8 OTHER REQUIREMENTS

C.8.1 Office Space

The Contractor must provide adequate space and communication tools necessary for its personnel to work effectively under this contract. The Contractor must maintain a modern office environment with amenities such as standard office furniture, telephone equipment, copying equipment, conference or workroom facilities, file storage facilities, and operating supplies.

C.8.2 Telework

Contractor employees may work remotely (Telework) with prior approval from the FAA management. The FAA may revoke this approval at any time; if it does, performance may no longer occur remotely. Telework costs (space, phones, internet, travel, etc.) will not be allowed as direct costs under this contract.

(End of Section C)

ATTACHMENT 2 – NEST SUPPORT SUBMISSION INSTRUCTIONS:

Page | 1

A. COVER SHEET – no more than 1 page

1. Vendor name, address, website, Unique Entity Identifier (UEI), and Commercial and

Government Entity (CAGE) Code.

2. Point of contact to include an e-mail address and telephone number.

3. Type of business, including socio-economic category (i.e., Large Business, Small, Socially and Economically Disadvantaged Business (SEDB) 8(a), Service-Disabled Veteran-Owned Small Business (SDVOSB), Historically Underutilized Business Zone (HUBZone) small businesses, Small Disadvantaged Businesses (SDB), Women-Owned Small Business (WOSB) firms, and/or Economically Disadvantaged Women-Owned Small Business (EDWOSB))

4. If applicable, GSA contract number and schedule.

B. CAPABILITIES STATEMENT & MARKET INFORMATION – no more than 10 pages

1. Please describe your organization’s breadth of expertise/competency to respond to the content in the draft SOW. Please provide a response for each of the following:

• Ability and expertise in providing IT services to the federal government or private industry

• Ability to meet delivery requirements across multiple NIMS geographically dispersed users

• Ability to provide helpdesk activities for multiple tickets and users

• Ability to identify, offer, and provide additional services that enhance the FAA’s NIMS program

• Ability to recommend system architecture, tools, design, development and deployment support based on contract requirements

• Ability in providing referenced PMO support services in Attachment 3, please address all 20 elements.

2. Industry feedback is requested on the draft SOW for this requirement. Please list any challenges or potential performance roadblocks related to fulfilling the draft SOW requirements and any suggestions for improving the draft SOW language. Feedback is also requested regarding the proposed PSC and NAICS codes. Comments on PSC/NAICS and suggestions for alternative codes must include supporting rationale.

ATTACHMENT 2 – NEST SUPPORT SUBMISSION INSTRUCTIONS:

Page | 2

C. BACKGROUND/PAST EXPERIENCE- no more than 2 pages

Provide the following information on two (2) similar projects with respect to our draft SOW that was completed within the last three (3) to five (5) years for which you were the prime or a Sub- Contractor.

1. The name and value of each project;

2. The name, address, telephone, and e-mail address for point of contact;

3. A description of each project, including challenges and successes; and

4. Your company’s role and services provided for each project.

The point of contact for questions or clarifications pertaining to this RFI/Market Survey is below. No telephone inquiries will be accepted.

Submit responses to:

Jose Duran Contracting Officer E-mail: 9-AWA-AAQ410-Contracting-Team@faa.gov

Response Date: 10:00 AM Eastern Time on December 16, 2025 mailto:9-AWA-AAQ410-Contracting-Team@faa.gov

Attachment 3 – NEST Support Contractor Capabilities List

1. Leverage the Requirement Traceability Matrix (RTM) and other tools to provide Level-of-Effort estimates and help prioritize requirements.

2. Develop and maintain ~650,000 lines of code using ColdFusion, HTML, JavaScript, and CSS.

3. Create stored procedures, triggers, and SQL scripts.

4. Implement Version Controlling of the code in each test environment and scheduled testing on each environment.

5. Perform Unit, System, and Integration testing. Coordinate and assist with User

Acceptance Testing to validate changes and procure PMO sign-off.

6. Perform risk assessment and provide contingency plans to back-out deployed code (if required).

7. Perform build configuration, debugging and logging, extensions, and security features.

8. Provide strategic guidance on system optimization by monitoring code performance, recommending code optimization, and executing requisite performance tuning.

9. Document system requirements/functionality.

10. Demonstrate expert knowledge in the technical stack: Oracle, ColdFusion, HTML, JavaScript, CSS, PHP, Transact-SQL, DBNetSuite, Fusion Charts, CFC, JQuery, CFEclipse, SAML, Dream Weaver 11, Java, JSP, JSON XML, and Amazon Web Services under Windows and Linux operating systems.

11. Possess detailed functional database operation experience encompassing Task Order Processing, Purchase Requests, Financial Obligations/De-obligations, Fund Allocations and Transfers, Invoice Certifications, and Payment.

12. Possess detailed knowledge of Workflow life cycle management pertaining to task order administration processes. Demonstrate detailed understanding of workflows, with the ability to troubleshoot and fix workflow-related issues or enhance workflow rules to meet business objectives.

13. Evidence of detailed knowledge of data integration patterns with up-stream/down-stream systems like Delphi and PRISM. Demonstrate ability to troubleshoot, debug and fix integration-related issues.

14. Demonstrate a thorough understanding of data models and underlying data elements to support financial and non-financial reporting.

15. Exhibit ability to work closely with FAA’s Cybersecurity team to perform periodic code reviews and effect requisite code changes to ensure compliance.

16. Perform system performance monitoring, initiate and lead platform sizing efforts and assist with hardware/software upgrades.

17. Possess detailed knowledge of access control and security requirements to ensure system adheres to FAA’s policies and guidelines.

18. Provide helpdesk support to the PMO team as well as to the Key and End Users.

19. Maintain and restore CMIS (currently dormant) for audit and closeout activities as required and requested by PMO.

20. Provide system architecture and tools recommendations, design, development, testing and implementation support for a new system when transitioning from NISC IV to NISC V contract.