Attachment S-7 SOO Artifacts Workbook.xlsx
XLSX spreadsheet 3 MB Posted
- Solicitation number
- 693KA9-22-R-00016
About this file
This document is a request for proposal (RFP) amendment for the System of Airports Reporting (SOAR) contract. The RFP amendment provides additional details on the required SOAR operations and maintenance, including configuration management, application change management, reporting and business intelligence, security compliance, and user support. It also outlines specific deliverables such as performance reports, status reports, release reports, and security briefings. The RFP amendment indicates that proposals are due by August 31, 2022 and the contract is expected to be awarded by January 2023, with an anticipated period of performance through January 2028. The Federal Aviation Administration Headquarters is the contracting agency.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| SIR_693KA9-22-R-00016_Section B thru M_FinalRev_Amend 3.pdf | ||
| Attachment S-3_Question and Comments - Government Response.pdf | ||
| 693KA9-22-R-00016 Section B Workbook.xlsx | XLSX spreadsheet | |
| SIR_693KA9-22-R-00016_Section B thru M_FinalRev.pdf | ||
| 693KA9-22-R-00016 Section B Workbook.xlsx | XLSX spreadsheet | |
| SIR_693KA9-22-R-00016_Section B thru M_Final.pdf | ||
| Attachment S-6 BusinessDeclarationForm.pdf | ||
| Attachment S-8 Industry QandC.xlsx | XLSX spreadsheet | |
| Attachment S-2 Example Quality Assurance Surveillance Plan.xlsx | XLSX spreadsheet | |
| Attachment S-1 Section C - SOAR Statement of Objectives.pdf | ||
| Attachment S-5_ PP Questionairre.docx | DOCX document | |
| Attachment S-3_Question and Comments Form.doc | DOC document | |
| Section A_SolOfferAwardSF33.pdf | ||
| Attachment S-4 CLIENT AUTHORIZATION LETTER.docx | DOCX document |
Show all 14
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
1a-Functional Requirements
| Grey header indicates transformation requirements are in production, although there may be backlog or new findings related to now O&M features and functions. | |||||||||||
| Neutral header indicates cross pilot functionality; however, depending on when functionality was adopted and rigor of developers there could be inconsistensies which should be captured in O&M backlog. | |||||||||||
| Light grey header or cell indicates feature is under development and is planned to be at least partially in production prior to contract transition. | |||||||||||
| Blue header or cell indicates feature is planned for transformation under this procurement award. | |||||||||||
| Pilot 1 | Finding & Ideas (User Interface Tools) | Pilot 2 | Data Driven Notifications (Custom Rule Management) | Pilots 3 & 11 | Dashboard (Widgets) | Pilot 4 | Worksite (Widget based, replace Legacy) | Pilot 5a | Carryover (Flowable workflow) | Pilot 5b | Transfers (Flowable workflow) |
| 1.1 | Add/edit/save a finding | 2.1 | List notification by logged in user | 3.1 | Display dashboard as landing page if permitted by user role | 4.1 | Navigate to worksite detail via a single LOCID or NPIAS # search | 5a.1 | List of Carryover requests and status information | 5b.1 | Allow ADO or RO users to create and submit transfer request enforcing applicable business rules |
| 1.2 | Assign Category to finding from drop down list | 2.2 | Hyperlink record to business object for which notification was generated | 3.2 | Toggle and save dashboard on/off where off goes to secondary default landing page based on user permissions | 4.2 | Allow users to create a worksite grid based on partial NPIAS, My Associated Worksites, or My Favorite Worksites, or search by State, City and County (or combination thereof) | 5a.2 | Submit carryover request details enforcing AIP business rules | 5b.2 | Allow ADO and ROs to specify and edit business rules to accommodate varying business practices by ADO or region |
| 1.3 | Assign Functional Area to finding from drop down list | 2.3 | Mark notice as read/unread individually | 3.3 | Display System Messages and Notifications Summary as uneditable and non-removable widgets a above configurable dashboard widgets | 4.3 | Hyperlink to a worksite (LOCID) from the results grid | 5a.3 | Reflect carryover transaction funds adjustments in checkbook based on request status (e.g., pending carryover requests in applicable checkbooks; adjustment to available to program) | 5b.3 | Allow multi-year transfer agreements |
| 1.4 | Add an attachment to a finding | 2.4 | Delete notices individually | 3.4 | Configure and save dashboard based on set of display options | 4.4 | Display the following widgets as default 12/6-6/12 structure for all new users from left to right: Basic Information; Service; FAA ADO/Regional Points of Contact; Runway Type/Categorization; NASR - Runway; HQ Hold; Plans/Certifications; NASR - Worksite; PFC; Proposed Worksite Information; Passenger Entitlement Eligibility; Worksite User Fields | 5a.4 | Allow ROs (approvers) to specify the workflow approvers and path within ADOs and RO within set number of approval steps and valid users. | 5b.4 | Notify users (pilot 2 functionality) when multi-year transfer agreements become current. |
| 1.5 | Provide guiding questions to complete finding information | 2.5 | Accommodate unlimited number of notification types | 3.5 | Select and save widgets to display based on a defined list of available widgets dependent on user permissions | 4.5 | Access, add and remove worksite specific widgets based on permissions, unless otherwise approved for all access by CCB or User Work Group. | 5a.5 | Generate, route and manage workflow after RO approval by create a carryover conversion request to 520 | 5b.5 | Context sensitive upload for sponsor transfer request documents upload (to ADMS Pilot 6) automatically filling metadata specific to the transfer |
| 1.6 | Comment on a finding | 2.6 | Generate notification based on prescribed business rules | 3.6 | Add and remove and save widgets without changing base widgets available for future use based on permissions. | 5a.6 | Allow 520 to enter conversion details for ABU action | 5b.6 | Allow RO to manage workflow process specific to their region | ||
| 1.7 | Hide submitted by for "anonymous" finding submission | 2.7 | Set individual notification preferences including (on/off); delivery method (in-system or email or both); notification title; message; audience; frequency, generation date, worksite exception list, inactivity period depending on business rules | 3.7 | Resize widgets within selected configuration | 5a.7 | Generate, route and manage workflow after 520 submission to ABU to carryover conversion to discretionary funds within the current fiscal year | 5b.7 | Generate, route and manage workflow through the RO specified process and HQ steps through the term of individual transfer agreements | ||
| 1.8 | Display user submitted findings at top of default list of all findings | 2.8 | Allow role-based management override of notice preferences to ensure all audience receives notifications | 3.8 | Change the dashboard title | 5a.8 | Allow ADO and RO users to create a carryover retraction request within the AIP and funds movement business rules | 5b.8 | Generate transfer agreement with PDF signature capability to reduce work on sponsor and provide consistency in documentation | ||
| 1.9 | Like a finding to indicate user concurrence | 2.9 | Show individual number of unread notices on entering SOAR | 3.9 | Restore default settings for dashboard | 5a.9 | Reflect carryover retraction funds adjustments in checkbook based on request status (e.g., pending carryover retraction in applicable checkbooks; adjustment to available to program) | 5b.9 | Submit "stop" or "cancel" request for a transfer request that has not been fully executed | ||
| 1.10 | Transfer findings to Jira to maintain work list | 2.10 | Provide Inactive Grant notification based on SOAR data for defined "inactive" rules | 3.10 | Display the following widgets as default 3-9(12-6/6) structure for new field office users from left to right: My Favorite Reports; CIP Projects; SOAR Stats & Tips; Grant Close Out; Amend Grant | ||||||
| 1.11 | Provide/view processing information (clarification, priority, severity, date required, action status and assigned to) | 2.11 | Provide PFC Expiring Application notification based on SOAR data for defined "expiring" rules | 3.11 | Access to all widgets based on module permissions, unless otherwise specified by CCB or user work group. For example: My Favorite Reports; CIP Projects; SOAR Stats & Tips; Grant Close Out; Amend Grant; Documents; Headquarters Grant Review; Risk Assessment Status; Worksite Summary (National Level View) | ||||||
| 1.12 | Notify submitter of change CCB actions and comments on finding | 2.12 | Provide Grant Activity notification for open grants based on a prescribed step in workflow | 3.12 | Display the following widgets as default 3-9(12-6/6) structure for new headquarters users from left to right: My Favorite Reports; CIP Projects; SOAR Stats & Tips; Grant Close Out; Amend Grant | ||||||
| 1.13 | Read/deleted notifications associated with user findings | 2.13 | Provide Unassigned Checkbook Funding notification for various fund types that have no current year projects | 3.13 | Select worksites from a favorite worksites list to filter results | ||||||
| 1.14 | Email helpdesk on submission so finding does not age before Jira pull | 3.14 | Undo changes made to widget configuration or selection | ||||||||
| 1.15 | Display number of unread notifications | ||||||||||
| 1.16 | Manage drop down list for finding categories | ||||||||||
| 1.17 | Manage finding guiding questions based on category | ||||||||||
| 1.18 | Hide closed findings on initial display | ||||||||||
| 1.19 | Reply to a comment entered by another user | ||||||||||
| 1.20 | Allow a user to delete comment they entered provided no reply has been submitted |
| Pilot 6 | Airports Document Management System (ADMS/Alfresco Interface) | Pilot 7 | e-Sign (Adobe eSign) | Pilot 8 | Risk Tool (JSON template approach) | Pilot 9 | Red Folders (Mobile) | Pilot 10 | Planning (replace legacy, now AIP) | Cross Pilot | Help Tray, Navigation, Workflow, Kendo Grid, Reports, Legacy Updates |
| 6.1 | Upload a document through SOAR to ADMS providing as much metadata as available at a give SOAR context. | 7.1 | Enter email information necessary to initiate an Adobe Sign process for grant agreements (e.g., Signatories, CC, Message, etc.), including any needed error-checking data validation | 8.1 | Allow HQ to define the frequency of assessments for each rating level (e.g. Nominal Risk every three years) | 9.1 | Reviewers can perform all functions associated review of grants/amendments on FAA mobile devices or computer/laptop provided they operate behind the FAA firewall using SOAR | 10.1 | Retrieve a list of Overall Development Objectives (ODOs) and/or Projects based on a limited set of selection criteria specified by the user | HT.1 | Create a help tray for screen or function specific user assistance |
| 6.2 | Ability to associate a specific worksite, category (AIP, PFC, Planning), and sub-category (options dependent on selected category), and SOAR Object Reference (e.g., grant number, PFC application number, sponsor, etc.) as metadata with a document, if not available in SOAR context | 7.2 | Once available, pull email information for Adobe Sign process based on sponsor contact information and allow user to verify or change email | 8.2 | Upload the last assessment for each sponsor via SOAR to ADMS | 9.2 | Reviewers utilizing SOAR access grants/amendments requiring their review through a Red Folder Dashboard widget | 10.2 | List ODOs and/or Projects in a way that reveals their relationship and includes capability to drill-down to further ODO/Project details from within a retrieved list | HT.2 | Provide text and graphic based screen or function specific help in Help Tray (Note: These have been implemented as either Quick Reference Guides (QRG)s or Step-by-Step Guides) |
| 6.3 | Upload a document through SOAR to ADMS under the context of a specific worksite, grant, PFC application, Sponsor Risk Assessment, etc. so that the worksite, category, and object reference metadata is automatically captured for the uploaded document (including Region, ADO, State, City, etc.) | 7.3 | Upload a grant agreement .PDF into SOAR for transmission to Adobe for signature | 8.3 | Allow past assessments for each sponsor to be uploaded into SOAR|ADMS | 9.3 | Reviewers can mark a grant/amendment as approved which will advance to the next step in workflow | 10.3 | Add a new or edit/delete existing ODO or Project, including ability to add ODOs, add projects and associate them to ODOs, edit ODOs, and edit projects (not including custom data fields) | HT.3 | Provide context sensitive Data Element Dictionary for all fields used in give page as part of Help Tray function |
| 6.4 | View a list of documents in SOAR of documents stored in ADMS that are associated with a specific worksite, including both documents uploaded through SOAR and documents uploaded directly to ADMS | 7.4 | Save grant agreement e-sign information into SOAR/ADMS prior to transmission to Adobe for the signature process | 8.4 | Identify/mark all sponsors that are expected to receive an assessment at the beginning of a fiscal year | 9.4 | Reviewers can record comments for each grant | 10.4 | Mark projects that are expected to be grouped and programmed under the same grant | HT.4 | Provide short, task specific, training videos context sensitive based on page or function in Help Tray |
| 6.5 | Download a document from the SOAR user interface to view, edit or otherwise manipulate) locally | 7.5 | Save newly entered email addresses as a new contact in SOAR for use in the future (see 7.2) | 8.5 | Provide information from SOAR to assist in completing the assessment checklist for a sponsor, such as: untimely closeouts, reimbursement requests without attachments, % of reimbursements requests over 30-days, and % of grants utilizing the full 15% amendment capability based on data for the past three fiscal years | 9.5 | Reviewers can decline grants back to APP-520 staff to be corrected or have additional information provided | 10.5 | Provide data analysis of planning checkbooks showing users how funds have been planned for a program "at large" including planned amounts from future years as well as what funds are expected to be available for planning in future years (e.g., Carryovers, Transfers, etc.). | HT.5 | Provide the ability for a user to display and/or search ALL help materials including Data Element Dictionary regardless of context (e.g., not Help Tray/page or function specific) |
| 6.6 | Delete (with appropriate ADMS permissions) documents uploaded via SOAR from ADMS | 7.6 | Transmit, file, and save grant document and audit e-sign documents from Adobe Sign to SOAR|ADMS when completed. | 8.6 | Select a sponsor to: review previously completed assessments, initiate a new assessment, or edit an assessment in progress | 9.6 | Reviewers can open a grant/amendment profile page to assist their review | 10.6 | Lay the foundation (backend) for the cross-system Custom Data fields concept allowing ARP to time bound an existing generic field for a program-specific purpose. Foundation allows SOAR team to change the name of the field, change the definition of the field, specify a start and end timeframe for the field via database (not code) | Intentionally blank | |
| 6.7 | Recognize and utilize ADMS folder structure | 7.7 | Allow users to associate additional reference information/metadata to the signed grant agreement before or after it is uploaded in SOAR|ADMS | 8.7 | Complete all categories and associated questions in the Grant Oversight Risk Model assessments they initiate. | 9.7 | APP-520 can Red Folder Review through the Grants Module only (e.g., not from dashboard or mobile) | 10.7 | Track planned ODO/Capital project funding to view of how planned project funding for future years is distributed as well as how currently programmed funding affects the project plan. Allow users to balance project funding needs against available funding while highlighting any surpluses or shortcomings in the office's funding plan. |
Assign planning funds to planning checkbooks, maintain a planning transactions table which includes checkbook adjustments like carryovers or transfers, update calculation used for creating and funding future year planning checkbooks.
| NAV.1 | Facilitate navigation from legacy to transformed SOAR seamlessly | |||||||||||
| 6.8 | Retrieve and view in SOAR a list of documents (stored in ADMS) based on criteria selected by the user. The document list should include both documents uploaded through SOAR and documents uploaded directly to ADMS | 7.8 | Show the status of a grant agreement that is currently in the Adobe Sign workflow process as part of the overarching grants workflow, including the transmission of metadata from Adobe to the workflow engine to allow users to progress the workflow without needing to input a grant signed date. | 8.8 | Once an assessment is completed and locked the assessment based on user name and prevent further modification without special approval | 9.8 | APP-520 staff can add review information in the form of comments or notes to assist reviewers | 10.8 | Analysis capability including summary overviews, data drill-down, detail views, etc. to explore the correlation of funds between PFC and AIP | NAV.2 | Create new browser tab when appropriate to work function and user need (i.e., Findings and Ideas, User Management, etc.) | |
| 6.9 | Provide context sensitive uploads and retrievals to include, but not necessarily limited to: Region, ADO, Worksite, Sponsor/Public Agency, Grant, Grant Amendment, ODO, Capital, grant justification, compliance issue, LOI, Transfer Request, Carryover Request, Retraction Request, PFC Application, PFC Amendment, PFC Project, PFC 43C, PFC Audit | 7.9 | Enable the user of notarization once that feature is support by eSign Adobe contract | 8.9 | Verify that all required questions have been answered before saving assessment as complete | 9.9 | APP-520 staff can attach electronic documents associated with individual grants/amendments as needed (e.g. email, word or pdf documents, …) | 10.9 | Capture ODO and Capital Project data defined by their office or organization using the custom data field management capability, updating the ODO and project data entry screens to capture and display the custom data, and any corresponding report adjustments | NAV.3 | Incrementally adopt target site map navigation based on Pilots | |
| 6.10 | Allow users to view documents in SOAR without having to download a file to their local machine | 8.10 | Update the SOAR sponsor "Risk Level" data field with the results from completed assessment | 9.10 | APP-520 staff can mark grants/amendments as "expedite" to indicate priority review | 10.10 | Customize search criteria, adding related criteria (e.g., ODO/project attributes, worksite attributes, etc.), smart search (if applicable), saved searches, etc. | NAV.4 | Restrict navigation (or menu/button selection) based on organization, role, and access permission. NOTE: Unless otherwise specified roles and access is across regional and ADO boundaries in transformed SOAR) | |||
| 6.11 | Select one or more documents from a document list in SOAR to retrieve or remove those documents with a single action | 8.11 | Allow user accessing sponsor information through the SOAR Sponsor page to view completed assessment information | 9.11 | APP-520 staff can mark grants/amendments that do not require a full review (e.g. do not require six reviewers to approve) | 10.11 | Update specified data (e.g. Grant Year) for a project and automatically update the corresponding data for all projects under the same ODO | Intentionally blank | ||||
| 6.12 | Select one or more SOAR items (e.g. capital projects) and associate them to a single uploaded document | 8.12 | Allow sponsors to enter performance data and upload reports through the SOAR AEP Module to comply with Quarterly Reporting requirements | 9.12 | After the review process has started, APP-520 can mark grants/amendments that do not require a full review and advanced them to OST Batching | 10.12 | Update the fiscal year and assigned funding information to develop the planned spending for the location over the next years | WF.1 | Provide a My Task list of pending tasks for users to easily access workflow action requirements | |||
| 6.13 | Enforce document naming conventions implemented by ADMS or ARP business rule | 8.13 | Transfer sponsored entered data and reports to SOAR at least nightly | 9.13 | Grants/amendments can be advanced to the next reviewer without approval | 10.13 | Indicate the priority of projects so that only projects that are expected to be funded under the current continuing resolution (if applicable) can be referenced in reports or other planning features | WF.2 | Provide a notification (Pilot 2) to inform users about carryover, retractions, and conversions related to their worksites or office | |||
| 6.14 | Ability to review and modify documents in SOAR with a version history from ADMS | 9.14 | Grants/amendments can have their priority changed while in the review process | 10.14 | Allow APP-520 ACIP users to create, distribute, and monitor the Regional planning ceilings and planning guidance for a particular planning year range | WF.3 | Show graphical workflow steps and status for individual items | |||||
| 6.15 | Allow mass import of documents into ADMS via SOAR. | 9.15 | The number of reviewers required for grants/amendments can be changed while in the review process (e.g. 4 reviewers to 6) | 10.15 | Allow Regional ACIP users to establish planning ceilings and guidance for their associated ADOs | Intentionally blank | ||||||
| 6.16 | Send an email to SOAR with a document attached and metadata identified in the subject line so that the attached document is automatically uploaded into ADMS with the correct metadata associated. | 9.16 | Grants/amendments can be Retracted back to APP-520 staff for additional preparation work or to be returned to the field | 10.16 | Generate and route ACIP Review workflow at both the ADO and Regional levels | KG.1 | Sort and filter grid based on column data | |||||
| 6.17 | Include document templates (e.g. grant offer letter, grant, project listing for ATO, etc.) which automatically pull in data stored in SOAR and upload to ADMS | 9.17 | Provide a Red Folders Dashboard Widget so users can determine grant status and priorities | 10.17 | Enable and enforce justification business rules on ACIP ODO/Project data to initiate corresponding workflow steps/tasks | KG.2 | Allow user to change the number of items on a page | |||||
| 6.18 | Create a template library where users can modify templates or choose standard SOAR templates to create a document utilizing current SOAR data | 9.18 | Grant review process can categorize grants/amendments level of review (2 to 6 reviewers) | 10.18 | Allows user with appropriate workflow management permissions to edit the workflow settings for the ACIP Approval within their office | KG.3 | Allow user to export grid to Excel | |||||
| 6.19 | Allow users to create their own templates (documents and forms) which utilize SOAR data and upload to ADMS | 9.19 | Users can see the status (workflow step) of grants/amendments in the Red Folder | 10.19 | Provide notifications based on data contained within ODOs/Projects and their associated ACIP Review workflows | KG.4 | Allow user to resize column | |||||
| 9.20 | Users can drilldown to evaluate the status of grants/amendments for a specific region or ADO | 10.20 | Allows APP-520 ACIP users to establish an NPR Threshold for a particular planning year range which will in turn determine the Projects that require justification | KG.5 | Allow bulk marking to permit users to mark multiple rows at the same time and take action either to the entire package (e.g., bulk delete) or successively on each record (e.g., select records for review and action (approve/decline) | |||||||
| 9.21 | Users search for specific grants/amendments to view where they are in the Red Folders process | 10.21 | Allow APP-520 ACIP users to create the one or more ACIP snapshots for a particular planning year range and then use that snapshot as part of the PCL/DCL creation. This feature also includes the generation of ACIP guidance based on the data from the PCL/DCL. | KG.6 | Default list by user or organization unless customized default list is permitted | |||||||
| 9.22 | Users can request notification for grants/amendments that remain in queue over a threshold amount of time | 10.22 | Generate ACIP guidance based on the data from the PCL/DCL. | KG.7 | Allow user to change number of rows (15/50/100) displayed and navigate pages on grid | |||||||
| 9.23 | System generated notification alert users when grants/amendments are in their queue at the start of a day | 10.23 | Provide widgets that surface ODO and Project data as it relates to the project planning process available on dashboard (Pilot 3) | KG.8 | Hyperlink unique record identifier to detail page based on context | |||||||
| 9.24 | Users can request notification for grants/amendments that are declined | 10.24 | Select a saved set of ODO/project search criteria to define the projects returned in the widget (Pilot 3). Allow users to edit projects from the widget in a similar manner as described in the "Develop ACIP - ACIP Project List Manipulation" feature. | KG.9 | Search on grid content by keyword or string | |||||||
| 10.25 | Display ODOs and Projects relationship between the planned and in-progress work at a worksite and how that relates to the development milestones (e.g. service volume, based aircraft, etc.) that have been set for that worksite in its master plan including the ability to capture the additional data elements which define these milestones on a per worksite basis | KG.10 | Allow user to resize or reorder columns and maintain for duration of session | |||||||||
| 10.26 | Add or edit environmental actions and to associate one or more projects to an environmental action. | KG.11 | Allow user to resize or reorder columns and save for later use | |||||||||
| 10.27 | Upload one or more documents for association with a particular environmental action (Pilot 6). | Intentionally blank | ||||||||||
| 10.28 | Initiate details for a new worksite in SOAR for approval by APP-400 so that the new worksite can be used to track the required initial projects for a new worksite (e.g. Site Study, etc.) | RPT.1 | Update existing reports to utilized new data including workflow information, as needed. No existing report at time of release of a new pilot should error because of the pilot. | |||||||||
| 10.29 | Accept new ODO or Project to SOAR for review and approval by SOAR ADO/Regional user | RPT.2 | Update data views/Data Explorer to make any new data including workflow information, available for ad hoc reporting. | |||||||||
| 10.30 | Generate and route External ODO/Project Approval workflow | Intentionally blank | ||||||||||
| LU.1 | Update any and all legacy functions, including but not limited to, backend processes, user permissions, security, navigation, etc., that require changes to function seamlessly with transformation release |
| Pilot 12 | Grants (replace legacy, now AIP) | Pilot 13 | Passenger Facility Charge (replace legacy, now PFC) | Pilot 14 | Data Explorer (Tableau replacement of Data Wizard) | Pilot 15 | Air Carrier (Air Carriers, Cargo + Scenarios; legacy ACAIS) | Pilot 16 | System Interfaces (APIs Using Anypoint) | Pilot 17 | Airports Capital Improvement Plan (ACIP) (replaces and enhances HQ MSAccess ACIP Review tool) | ||||
| 12.1 | Add a new grant to the system | 13.1 | Retrieve a list of Applications, Amendments, 43c and Projects based on a limited set of selection criteria specified by the user. Selection options include by: LOCID, Location, etc. | 14.1 | Single sign on from SOAR to Tableau | 15.1 | View a list of all available funding scenarios | 16.1 | Provide API to interface with Delphi SOA replacing manual entry of combined 107/1413 data by account staff (detailed requirements in progress) | 17.1 | Collect/"extract" data for ACIP checklist analysis based on NPIAS Capital Projects for flexible duration (e.g., next 3 years, next 5 years) and flag projects for approximately 30 check categories | ||||
| 12.2 | Edit grant data, including add or edit: general grant information, capital projects, grant funding, and talking points for both the grant and capital projects. | 13.2 | Add a new PFC Application or select existing PFC Application data to make updates, or delete the item entirely. | 14.2 | Three types of privileges based on Tableau licensing -- Creator, Explorer and Viewer | 15.2 | Select, run and open scenarios | 16.2 | Provide web services to interface with state systems for batch transmission and exchange of data from AEP/AIPE (pilot with FL system) | 17.2 | Provide review results for discretionary and entitlement funding checks including economic recovery leftover and funding plan review. Specific areas evaluated: Discretionary -- to be funded off-the-top, adjusted planning ceiling, total discretionary planned, and the differnce between the two; Entitlement -- planned or over planned | ||||
| 12.3 | Add or update milestone information associated with a grant, including Planned and Actual dates for Environmental Completion and Bid Opening Date | 13.3 | Add a new Excluded Classes to an Application or select existing Excluded Classes data to make updates, specify if they are approved or disapproved; or delete the item entirely. | 14.3 | Users have access to data sources made available by creators (initially this will be same as available in Data Wizard, but should be updated from SOAR to all data and include other sources outside SOAR eventually) | 15.3 | Customize the calculation criteria when running a scenario. | 16.3 | Provide web services to interact with Delphi SOAR to replace DTF nightly transfer | 17.3 | Provide review results for flag checks comprised of approximately 15 distinct data validations for various NOIS, MAP, Part 139, RSAT, Part 1542 flag existence, non-existence and consistency with other data | ||||
| 12.4 | Create a new grant from Planned grants associating of all planned grant information with the new grant created | 13.4 | Validate business rules related to PFC applications (e.g. Notice to Carrier dates, application received dates, etc.). | 14.4 | Each module has different views. Currently views are restricted by module but should be opened to at least Viewer access to all. | 15.4 | Run funding scenarios using existing calculations (i.e. passenger entitlements and cargo entitlements). | 16.4 | Improve SAM/Delphi/SOAR data reconciliation using APIs | 17.4 | Provide review results for discretionary and entitlement funding checks including economic recovery leftover and funding plan review. Specific areas evaluated: to be funded off-the-top, adjusted planning ceiling, total discretionary planned, and the difference between the two | ||||
| 12.5 | Retrieve a list of grants based on selection criteria specified by the user (e.g., LOCID, NPIAS#, Location, etc.) | 13.5 | Add a new PFC Project to the system or select existing PFC Project data to make updates or delete the item entirely. | 14.5 | Select from available fields in the views | 15.5 | Run funding scenarios using additional calculations (e.g. Protected Entitlements, Set Asides, APP-520 AIP Master Program, etc.). | 16.5 | Other possible API implementations include but may not be limited to: GNS interface; NASR interface; BTS and TAF data loads, replacing SOAR Internal/AEP data synch, PFC, Cargo and enplanement batch upload to AEP | 17.5 | Provide project check functionality for various conditions such as old project and projects below NPR threshold justification requirements | ||||
| 12.6 | View the Talking Points Report for individual grants to include grant and capital projects talking points | 13.6 | Associate one or more PFC Project(s) from one Impose Application with a different Use Application | 14.6 | Create operator based filters on fields (Viewer) | 15.6 | Allows for RO users to review new funding scenarios and provide feedback (comments) to APP-400 on the results | 17.6 | Provide project / work code check to ensure correct coding based on coding guidance | ||||||
| 12.7 | Retrieve a list of grants based on a grant's workflow status: INI, ROR, HQR, HQB, ARP, AGI, etc.. Multiple statuses appear in one list and user can drill down to the status grouping or grant they desire | 13.7 | Indicate review status for a PFC application under the regular approval process. The application available status updates include | ||||||||||||
| Pending, Approved, Partially Approved, Withdrawn and Disapproved. | 14.7 | Output list reports in Excel, PDF and HTML | 15.7 | Retrieve air carrier information based off their specific search criteria. | 17.7 | Provide flexibility to add, modify or remove review conditions and types or for different grant programs and checklist rules (e.g., AIP vs BIL) | |||||||||
| 12.8 | Modify, approve, and return grants to an earlier step via the grant workflow from initiation to obligation based on the workflow step and the user's role | 13.8 | Indicate review status for a PFC application using the streamline approval process. Status selections include | ||||||||||||
| Pending, Acknowledged, Partially Acknowledged, Withdrawn and Objected. | 14.8 | Save queries for reuse and add to the library of queries available for the team | 15.8 | Add new air carrier and aircraft information, also allow users to update existing air carrier information | 17.8 | Identify potential data errors or omissions based on checklist review results. | |||||||||
| 12.9 | Create a grant amendment after the grant is in open status | 13.9 | Indicate review status for a PFC project independently to the application or amendment with which they are linked. For the regular approval process the project status include Pending, Approved, Partially Approved, Withdrawn and Disapproved | 14.9 | Modify existing queries for differing need and save with different name | 15.9 | Validate air carrier information based on established criteria | 17.9 | Allow users to edit project data including comments and ACIP narrative with minimal navigation while conducting review. | ||||||
| 12.10 | Modify (e.g. increase/decrease grant amount, change description, etc. ), approve, return to an earlier step, or remove grant amendments based on the status of the amendment and the user's role | 13.10 | Functionality that allows users to approve PFC project independently of the an application or amendment they are assigned to. For the streamline approval process the project status include Pending, Approved, Partially Approved, Withdrawn and Disapproved | 14.10 | Creators have all functionality available based on licensing (and could have Tableau desktop install if additional capabilities are needed) | 15.10 | Allow internal users to add and update existing cargo data | 17.10 | Allow users to mark and track review status and comment on review criteria (e.g., project, ADO, checklist type) to aid followup and further review. | ||||||
| 12.11 | Close a grant | 13.11 | Link the PFC Project with the planning project and/or associated grant project. | 14.11 | Explores have all Tableau functionality available based on licensing | 15.11 | Validation that cargo data meets established criteria | 17.11 | Allow certain users (based on user ID, office and Tableau license type) to create and name ACIP snapshot and copy to/load Tableau | ||||||
| 12.12 | Modify, approve, and return to prior step a grant closeout workflow based on the status of the closeout and the user's role | 13.12 | Allows users to specify the types of funding (Pay-as-you-go, PFC Bond Capital, PFC Financing & Interest and PFC Funding, AIP or other funding) associated with the Project | 14.12 | Include logics/calculations to fields not part of raw data (e.g., total number of grants) | 15.12 | Allow internal users to add and update existing enplanement data | 17.12 | Allow users to delete snapshots based on organization, except national. | ||||||
| 12.13 | Reinstate a closed grant to open status | 13.13 | Add, modify, delete and approve PFC application amendments (e.g. change effective/expiration dates, increase/decrease funding amount, change PFC Level, etc. ) | 14.13 | Ability to save and edit new calculations without overwriting the existing baseline calculations | 15.13 | Validation that enplanement data meets established criteria | ||||||||
| 12.14 | Withdraw or delete a grant | 13.14 | Modify and approve PFC projects (e.g. change status, change effective/expiration dates, increase/decrease funding amount, change PFC Level, etc. ) | 14.14 | Ability to construct complex calculations and share with other users | 15.14 | Synchronize data entered internally to AEP at least nightly | ||||||||
| 12.15 | Reinstate previously withdrawn or deleted grants | 13.15 | Approve PFC amendments to applications. For the approval process the amendment status include Pending, Partially Approved, Approved, Disapproved and Retracting | 14.15 | Ability to create new outputs such as visualizations and image output | 15.15 | Allow APP-400 Admin to review externally submitted cargo data, identify errors with the data, make corrections, and approve before the data is committed into the SOAR transactional files | ||||||||
| 12.16 | Adjust the type and amount of funding associated with a grant, no net change to the total grant amount | 13.16 | Automatically generate Causal 43cs and cascade them to subsequent applications when an application's charge dates are modified via an amendment. | 15.16 | View past fiscal year data for cargo and enplanements (okay as reporting function) | ||||||||||
| 12.17 | Create groups of grants (packages) for red folders or OST (post red folders), to add or remove grants from a package, and provide required documentation. | 13.17 | Add a new 43c or to select existing 43c data to make updates or delete the item entirely. | 15.17 | Automatically file eSigned enplanement and cargo forms and their audit document via SOAR|ADMS API (with the correct metadata) to ADMS. | ||||||||||
| 12.18 | Permit HQ users to move OST packages through the OST process leading to the announcement of each grant attached. Includes retrieving, approving, declining and commenting on packages in ARP, AGI, and OST. | 13.18 | Approve PFC application 43c (e.g. change the effective/expiration date, etc. ) | 15.18 | Provide ability to retrieve ADMS files in SOAR | ||||||||||
| 12.19 | Allow HQ users to combine packages of grants to create "Super packages" | 13.19 | Auto generate Causal 43cs as part of the cascading process | 15.19 | Permit users with the correct permissions (i.e. APP-400) to unlock submitted data sets so they can edited by external users. | ||||||||||
| 12.20 | View or print the package or Super package as well as individual grants within a package | 13.20 | Maintain the data entered or updated in the internal system synchronized with the data entered in the external system and vice versa including Applications, Amendments, 43c, Projects, Revenue, Disbursements, Forecast, Collections, Sponsor, Worksite, Contacts, etc. | 15.20 | See AEP for external Air Carrier/Cargo functionality | ||||||||||
| 12.21 | Allow Headquarters' users to create, modify, or delete a Talking Point template and to associate Talking Points with specific grant criteria. | 13.21 | Retrieve Projects based on a limited set of selection criteria specified by the user. | ||||||||||||
| 12.22 | Search the Talking Point Templates, to include by work type code and Talking Point Template | 13.22 | Add a new disbursement associated with a Quarter and Project to the system. This feature would also allow users to select existing Project data to make updates to the Implementation date, the Physical Completion date and/or the Financial Completion date and their statuses | ||||||||||||
| 12.23 | Validate that a grant meets AIP minimum standards prior to being approved by ADO (e.g. grant is over 25K, all talking points are included, justifications provided as needed, grant and capital funding match) | 13.23 | Notify user that one or more of the Estimated Dates is past due and restrict updating disbursements until past due date is resolved. | ||||||||||||
| 12.24 | Generate and modify grant documents (grant offer letter, grant document, grant amendment based on grant type, funding or other criteria and including required tags for processing via eSign or eNotary (Pilot 7) | 13.24 | Retrieve revenue for an Airports for the specified year and month. | ||||||||||||
| 12.25 | Add a new sponsor to the system or to select existing sponsor data to make updates or delete a sponsor. It would include the ability for users to add or edit general sponsor information including sponsor contacts | 13.25 | Add a new revenue associated with a Year, a Month and a PFC Airport including adding entering Collections amount, Interest Amount as well as a Comment. (View only fields Total Revenue and Last Updated) | ||||||||||||
| 12.26 | Retrieve a list of sponsors based on a set of selection criteria specified by the user. Selection options include by: location, Sponsor ID, and LOCID or NPIAS_NUM of worksites owned by a sponsor | 13.26 | Show how the Projected Program Expiration Date is calculated as well as the projected months to collect | ||||||||||||
| 12.27 | View/print sponsor information to include: general information, sponsor contacts, sponsor risk status and history, checkbook report for passenger and worksite entitlements | 13.27 | Retrieve forecast for an Airports for the specified year | ||||||||||||
| 12.28 | Generate and manage funds allocation adhering to fund type business rules so that grants cannot exceed allotment amounts | 13.28 | Add a new Forecast associated with a Year and a PFC Airport to the system including Forecast amount | ||||||||||||
| 12.29 | Combine multiple grants | 13.29 | Display the impact of the forecast on the AIP | ||||||||||||
| 12.30 | Split a single grant into multiple grants | 13.30 | Automatically generate PFC Application documents based on the Application, Amendment and 43c Document templates and populate based on the data in SOAR | ||||||||||||
| 12.31 | Create, view and update a Letter of Intent | 13.31 | Upload Application, Amendments, 43c and Project Document to ADMS and associate it with the correct Application, Amendments, 43c or Project Document (Pilot 6) | ||||||||||||
| 12.32 | Route LOIs for approval | 13.32 | Display all PFC documents stored in SOAR (legacy) as well as those stored in ADMS using similar metadata until such time as all documents in SOAR have been transferred to ADMS | ||||||||||||
| 12.33 | Provide tools to manage LOI commitments, payment schedule, and audit reporting | 13.33 | Allow user sign all PFC Documents generated in SOAR electronically, using Adobe eSign if external signature required, or Adobe digital signature on PDF, if only internal signature requirement | ||||||||||||
| 12.34 | Automate eSigned grant and audit document to ADMS, and provide Accounting access via SOAR to replace KSN Accounting verification | 13.34 | Automatically send the PFC Documents to ADMS and associate it with the correct Application, Amendments, 43c or Project Document after it has been signed electronically. | ||||||||||||
| 12.35 | Manage recoveries and recovery ceiling | 13.35 | Functionality that allows users to view how future applications would be affected if the expiration date of an application is amended. Including when Causal 43cs would be generated. | ||||||||||||
| 12.36 | Facilitate limitation adjustment | 13.36 | View how future projects would be affected if the expiration date of a parent application is modified with the 43c. Including when Causal 43cs would be generated. | ||||||||||||
| 12.37 | Automate grant announcement including political contact management | 13.37 | View how different components are calculated. Such as: Calculated PFC Level, Calculated Expiration Date, Projected Program Expiration Date, Calculated Disbursements, Calculated Disbursements rate, Attributed Disbursements, Remaining Authority, Projected Months to Collect, Decision Due Date (for applications SML vs Non-Hub), Impose/Use totals (for applications/amendments), Impose/Use deltas (for amendments), revised impose and/or use deltas; Use Required date (for projects) and/or Required Start date (for projects) | ||||||||||||
| 12.38 | See AEP for external AIP functionality | 13.38 | Modify revenue for airports, bypassing some of the system rules. For example, the congressional year for which the revenue should be counted towards. This functionality also includes display how different calculations are achieved (Projected Program Expiration Date and Projected Months to Collect) | ||||||||||||
| 13.39 | Allow PFC Admin users to add, modify or delete existing Applications, Amendments, Projects and/or 43c while bypassing some of the system rules. | ||||||||||||||
| 13.40 | Check integrity of the PFC data and displays the relevant data to the user. For a preselected checks, allow users to the fix of this data. | ||||||||||||||
| 13.41 | Admin users can upload the most current version of the PFC Locations Report to compare against the report generated by the system. | ||||||||||||||
| 13.42 | Functionality that updates any new Tableau reports to enhance the PFC program management | ||||||||||||||
| 13.43 | Allows users to retrieve contact information for an Airports. | ||||||||||||||
| 13.44 | Add/edit/modify contact information for an Airports. This feature would include PFC Airport Program Contact, PFC Airport Financial Contact, Overall PFC FAA Point of Contact and Airport Contact | ||||||||||||||
| 13.45 | Automatically generate Notifications when the Quarterly Report is 30 days past due and when the Audit Report is due in the next 30 days, but allow user to turn the function on/off | ||||||||||||||
| 13.46 | Add a new Public Agency to the system or to select existing Public Agency data to make updates including add or edit general Public Agency information including Public Agency contacts. | ||||||||||||||
| 13.47 | Add or edit the Public Agency Year Month End value and the Next Audit Report Due date | ||||||||||||||
| 13.48 | Retrieve a list of public agencies based on a limited set of selection criteria specified by the user. Selection options include by: location, Public Agency CD, and LOCID worksites owned by a sponsor | ||||||||||||||
| 13.49 | Add or remove Public Agency associations with worksites including identifying if a Public Agency fills the role as the Primary Public Agency or a Alternate Public Agency | ||||||||||||||
| 13.50 | Retrieve contact information for an Public Agency | ||||||||||||||
| 13.51 | Add/update/delete contacts associations with Public Agency including PFC Program Contact and PFC Financial Contact for a Public Agency | ||||||||||||||
| 13.52 | View/print Public Agency information to include: general information, Public Agency contacts, Public Agency risk status and history | ||||||||||||||
| 13.53 | Retrieve Air Carrier information | ||||||||||||||
| 13.54 | Flag if an Air Carrier is currently under Bankruptcy or not. (View only Carrier Name, Carrier Country, Carrier City, Carrier State, Carrier Codes) | ||||||||||||||
| 13.55 | HQ users can flag and add data such a as the Bankruptcy Effective/Expiration Date, Average Monthly Amount and Average Amount Effective/Expiration Date. | ||||||||||||||
| 13.56 | HQ users can blend applications with future applications when these applications meet predefined criteria | ||||||||||||||
| 13.57 | See AEP for external PFC functionality |
| TBD | User Management (legacy AEP and SOAR Internal Account Management, User Profile, and Account Control) | 18 | Stakeholder Contacts, Sponsors, and Public Agencies (Internal and External) | TBD | NPIAS Process, Role Generator, Assets | TBD | Compliance/Environment | TBD | AEP (ACAIS, AIP, PFC. Note: Some Transformation may occur under other Pilots) | TBD | Database Refactoring, Reports Cleanup, Custom Fields, Other | |||
| UPB.1 | Display profile information and allow user to edit or delete profile data that does not impact organization, roles, or permissions | CNT.1 | Allow users to search for contacts based on applicable business rules (modules, organizations, or other) | RG.1 | Transfer Role Generator system to FAA domain under SOAR system boundary and subject to SLDC (current web based in Azure) | CMP.1 | Determine if functionality beyond compliance widget on Worksite is required; if not then address user requests below. | AC.1 | Download a formatted cargo data spreadsheet and then upload a completed spreadsheet to be parsed by the system for uploading the data. This feature also includes the validation needed on parsed files to ensure the proper format is used and that the data is accurate. | DB.1 | Minimize redundant data | |||
| UPB.2 | Automatically populate address info based on organizational selection, while allowing user to edit profile record without saving to master organizational record | CNT.2 | Display a list of contacts based on search criteria | RG.2 | Integrate all existing Role Generator functionality, either by linking from SOAR with single sign on or by adding functionality in SOAR (if the former, it may be an interim solution) | CMP.2 | Allow users to enter informal complaint for a worksite. The user should be able to selects the grant assurances or policy being questioned and eventually enter the outcome or resolution. Capturing the informal complaints would allow ARP to see how many exist for a State, ADO, Region, type of airport etc. and it would allow front-line staff to search for similar situations and resolution for new complaints. | AC.2 | Upload a completed cargo spreadsheet to be parsed and validated prior to saving data | DB.2 | Adopt agency and government naming conventions | |||
| UPB.3 | Allow user to set preference information applicable to account | CNT.3 | Define contact types (e.g., Sponsor, Public Agency, Air Carrier) | RG.3 | Provide efficient way for users to load or reload data sets needed, preferably without contractor assistance. Some of data sets already exist in SOAR and others are publically available. | CMP.3 | Clarify Mothers' Room check box on the Worksite page. See F&I 2543 | |||||||
| . | AC.3 | Permit Cargo users to acknowledge their submission of cargo data | DB.3 | Improve system performance (data retrieval and commit) | ||||||||||
| UPB.4 | Allow user to set account hold for extended leave more than 14 and up to 90 days without counting these days as "inactive". If the user does not log in within 60 days the account should be disabled | CNT.4 | Define contact subtypes (e.g., organizations or access levels) | RG.4 | Calculate and display distance between NPIAS airports. The results are one of the criteria used in determining roles. | CMP.4 | Add a date of latest approved ALP and Exhibit A. Then when a grant offer is generated the data is able to be pulled from the worksite information instead of user having to manually input exhibit a date into grant offer every time one is generated. | AC.4 | Present form that can be electronically signed to attest to the accuracy and integrity of submitted cargo data | Blank Intentionally | ||||
| UPB.5 | Automatically turn account to Active status at the end of the hold period (calculated inactive will start on the day after the user logs in to remove the hold) | CNT.5 | Define roles by types and subtypes (if applicable) | RG.5 | Allow user to see the date of the data sets used to generate an output file | Blank Intentionally | AC.5 | Allow Air Carrier users (airports) to enter, edit, and update existing cargo data, this would include previously "locked" data set opened for corrections by internal user | RPT.1 | Provide ability to easily identify report output without running a report | ||||
| UPB.6 | Provide email notification option for user and approvers | CNT.6 | Allow users based on permissions to add, edit or delete contact records | RG.6 | Allow user to select different data sets or different dates of the same data to determine impact on role | ENV.1 | Incorporate requisite planning and grant environmental data in SOAR including status information, NEPA type and NEPA decision date, for each grant application. Having this information within SOAR would permit identification of environmental status for each grant application for sorting and tracking purposes. | AC.6 | Validation cargo data according to existing business rules | RPT.2 | Allow users to access all reports unless specifically identified as restricted access for business reasons | |||
| UPB.7 | Provide workflow for organizational first line (Ext) or RO approver (Int) only for removing hold request | CNT.7 | Provide ability to relate contacts intra and inter organization | RG.7 | Allow user update to key criteria used in the calculation to determine role impact | AC.7 | Workflow to submit cargo landing data, have it reviewed/approved by APP-400, and coordinate on data updates if needed. | RPT.3 | Show report usage information (month and annual counts) | |||||
| UPB.8 | Allow user to request adding or removing access permissions | CNT.8 | Provide any data sharing required within the FAA organization (e.g., SharePoint Contact site, or EIM) | RG.8 | Allow user to quickly identify whenever there is a role change from a previous period | AC.8 |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .