The file's text, extracted by GovTribe without its formatting.
Functional Requirements
| | | | Functional Requirements | VENDOR Response | |
| ID | Category | Functional Area | Requirement Description | Identify the requirement meets as | Comments |
| | | | | Product Feature (C ) or Non-Compliant | |
| | | | | (NC) | |
| R-001 | Mandatory | Application Process | Provide capability for the applicant to electronically submit badge applications, including Disqualifying Crimes and all other TSA required certifications and the airports Badge holder rules to their Authorized Signatory. | | |
| R-002 | Mandatory | Application Process | The IDMS shall have capability to clearly identify the type of application such as new badge application, renewal badge application, badge change (for adding or removing privileges e.g. escort, driving privilege), replacement badge application (name change or lost, stolen or mutilated). | | |
| R-003 | Mandatory | Application Process | The IDMS shall allow the Trusted Agent to review and modify as necessary all the information submitted by the Authorized Signatory or the applicant. | | |
| R-004 | Mandatory | Application Process | The IDMS shall alert the Trusted Agent if the new badge applicant already exists and allow the Trusted Agent to review the duplicate record and merge or process individually. | | |
| R-005 | Mandatory | AS Portal | Authorized Signatory Portal must be accessible via the most commonly used Web Browsers to include Chrome, Edge, Bing and Safari. | | |
| R-006 | Mandatory | Audit | The IDMS Audit capability will meet all the TSA regulatory requirements per the National Amendments. | | |
| R-007 | Mandatory | Audit | Audit should allow selection of records for Audit based on company, specific individuals and badge type. | | |
| R-008 | Mandatory | Audit | When completing the badge or key audits the Authorized Signatory must not be able to select all records in one transaction. | | |
| R-009 | Mandatory | Audit | IDMS shall add false names to company audits that will be randomly added and different in each company. The number or percentage of names added to an audit should be set/administered each audit by the Security Access and Badging Office, | | |
| R-010 | Mandatory | Authorized Signatory | IDMS must automatically deactivate an Authorized Signatory from the AS Portal if the Authorized Signatory fails to maintain up to date Authorized Signatory training, an active badge and maintains all required security clearances (STA/CHRC/Rap Back when applicable). | | |
| R-011 | Mandatory | Authorized Signatory | IDMS must assign each Authorized Signer a unique user account and password upon completion of the approval process, required training and badge issuance. This user account will be used for submission of employee badge applications and all other business activities performed using the Authorized Signatory Portal. | | |
| R-012 | Mandatory | Authorized Signatory | IDMS shall provide and describe mechanisms to incorporate multi-factor authentication for the Authorizing Signatory Portal. The IDMS shall have the capability to implement OTP / authentication codes via text or email. | | |
| R-013 | Mandatory | Authorized Signatory | SMF Trusted Agent shall be the first Authorized Signatory for each new company being onboarded. | | |
| R-014 | Mandatory | Authorized Signatory | Must allow the Authorized Signatories to submit applications for new and renew badges, request badge type change (Sterile/SIDA) submit request for adding/removing badge privilege (e.g. escort and driving) and the ability to indicate that a badge is lost/stolen or the employee is terminated. | | |
| R-015 | Mandatory | Authorized Signatory | Will allow an Authorized Signatory to renew badges 60 days before the badge expires. | | |
| R-016 | Mandatory | Authorized Signatory | Ensure Authorized Signatories cannot see notes that the Trusted Agent's entered. | | |
| R-017 | Mandatory | Authorized Signatory | The IDMS shall allow Authorized Signatories to modify certain employee information while restricting changes to Date of Birth (DOB), SSN, Birth Country and other fields deemed to be critical to the STA process or SMF. | | |
| R-018 | Mandatory | Authorized Signatory | The Authorized Signatories will see only those companies and badge holders, they are responsible for. | | |
| R-019 | Mandatory | Authorized | | | |
| Signatory | Require password reset at initial log-in to Authorized Signatory Portal. | | | | | |
| R-020 | Mandatory | Badge Payments | Allow payment methods to be defined at individual company levels (Billing, credit card or no billing). | | |
| R-021 | Mandatory | Badge Payments | Provide the capability to manage and track the fees associated with badges, keys, violations and other items issued in the Security Access Control and badge Office. SMF must be able to update/change badge fees without needing Contractor’s support team assistance. | | |
| R-022 | Mandatory | Badge Production | IDMS shall permit system administrators to change the layout and design of Airport ID Badge templates. | | |
| R-023 | Mandatory | Badge Production | Automatically calculate and default the maximum expiration date for each new, renewed or reprinted badge based on the airport’s requirements. | | |
| R-024 | Mandatory | Badge Production | The IDMS shall clearly indicate on the UI if the badge was returned, badge returned date, badge printed date, badge printed date, badge pick-up date. | | |
| R-025 | Mandatory | Badge Production | When the current date passes the expiration date on a badge, automatically update the badge status and deactivate the badge in the PACS. | | |
| R-026 | Mandatory | Badge Production | Prevent printing a badge if any of the requirements such as background checks, training or documents are not completed in the IDMS. | | |
| R-027 | Mandatory | Badge Production | IDMS must support SEOS prox, ISO/IEC 7816, ISO/IEC 14443, ISO/IEC 15693 and ISO/IEC 7501 smart-card technologies and must also support the Federal Information Processing Standard 201 (FIPS-201). | | |
| R-028 | Mandatory | Badge Production | Allow creation of new badges as replacements for unaccounted (e.g. lost, stolen) badges by copying previous badge details, badge expiration date and establishing a new badge number. | | |
| R-029 | Mandatory | Badge Production | SMF requires that the previous badge number be used for renewal badges (unless reported lost/stolen or is unaccounted for). | | |
| R-030 | Mandatory | Badge Production | Print a receipt and send notification to the badge holder and / or Authorized Signatory as proof the badge was returned. | | |
| R-031 | Mandatory | Badge Receipts | Issue Receipt upon Badge Return and provide ability to email the receipt to the Authorized Signatory or any other email address entered manually. | | |
| R-032 | Mandatory | Company | IDMS shall provide ability to capture company names such as business legal names, doing business as, abbreviated name to be printed on the badge. | | |
| R-033 | Mandatory | Company | IDMS shall provide capability to configure at company and division level the ID requirements (certain government employees can provide one Form I-9 document), access levels/clearance codes, payments (monthly billing, pay-as-you-go, fee waived), s (badge fees, other fees), badge limits, designation limits, security check exemptions (CHRC, Rap Back and /or STA). | | |
| R-034 | Mandatory | Company | IDMS shall provide the capability to scan and upload documents related to company enrollment. For example, company authorization letters and contract or sponsorship documents. | | |
| R-035 | Mandatory | Company | The IDMS shall allow suspension of a company, but existing active badges will not be automatically de-activated. However, when a company is suspended no new badges can be issued/printed until the company is active again. | | |
| R-036 | Mandatory | Company | Provide capability to set maximum number of active badges (percentage of numeric) for specific badge type or badge privilege for a company. (e.g. 25% concessionaire rule or limiting escort privileges.). Restrict badge printing if the limit is reached. | | |
| R-037 | Mandatory | Company | Provide capability for SMF to configure or modify default access levels / clearance codes for an approved company. | | |
| R-038 | Mandatory | Company | The IDMS should provide capability for SMF to perform bulk / volume tasks such as de-activation of badges, change access levels/clearance codes by badge type or company or divisions. | | |
| R-039 | Mandatory | Company | The IDMS shall provide functionality to allow mergers of companies (e.g. legal name changes and badge printed names) including providing report of all badge holders impacted. | | |
| R-040 | Mandatory | Dashboard | The IDMS shall provide immediate notification to the system administrator, Security Access Control and badge Office Manager if the connection to the DACS is lost. | | |
| R-041 | Mandatory | Dashboard | Provide on dashboard or custom queue STA and CHRC results that are pending. | | |
| R-042 | Mandatory | Data Migration - Data Analysis, Reconciliation and Migrations | A data mapping exercise must be conducted to map existing fields in PACS and determine fields must be maintained in the IDMS. | | |
| R-043 | Mandatory | Data Migration - Data Analysis, Reconciliation and Migrations | Data cleansing must be conducted prior to implementation for remediation of data issues. A review of existing badges must be completed for badge color | | |
and access consistency, data accuracy, missing data fields, and compliance. Manual and system automated cleansing may be used.
R-044 Mandatory Data Migration - Data Analysis, Reconciliation and Migrations The contractor shall perform data analysis and provide reconciliation reports across all data sources integrated in the IDMS including but not limited to PACS, DAC and Finance system.
R-045 Mandatory Data Migration - Data Analysis, Reconciliation and Migrations The contractor shall provide reconciliation reports clearly identifying the data mismatches, duplicates records, missing and inconsistent data fields (DOB, SSN, etc.) and action plan for normalizing the data. The recommendations can include automated scripts to fix the data by the contractor, manual clean up missing information by Airport or other 3rd party system updates.
| R-046 | Mandatory | Data Migration - Data Analysis, Reconciliation and Migrations | The new Unique Person ID number field must be generated for all existing employees during the data import to IDMS. |
| R-047 | Mandatory | Data Migration - Data Analysis, Reconciliation and Migrations | The Unique Personal Identifier must be assigned to each existing badge |
holder during migration in IDMS and similarly provide plan to update other systems PACS, DAC etc.
| R-048 | Mandatory | Data Migration - Data Analysis, Reconciliation and Migrations | The contractor shall perform data analysis and provide reconciliation reports in progressively and iterative method. |
| R-049 | Mandatory | Data Migration - Data Analysis, Reconciliation and Migrations | Identify all data to be migrated into the IDMS in a transition plan, which shall include a data migration validation. The contract shall perform data |
migrations during every system acceptance testing iteration.
| R-050 | Mandatory | Data Migration - Data Analysis, Reconciliation and Migrations | Proposer shall include a Roll back plan for all data and processes in the event the go-live event does not execute as planned |
| R-052 | Mandatory | Document Management | IDMS must accommodate for all identification types shown on the Form I-9 Acceptable Documents List (List A, B & C) and ensure that the applicant’s scanned documents are the correct combination. |
| R-053 | Mandatory | Document Management | IDMS will allow for SMF identified organizations to only provide one identity document (for example TSA and LEO’s) |
| R-054 | Mandatory | Document Management | Provide ability to restrict viewing of scan and stored documents (e.g. Rap sheets) and mark private based on user roles and permission levels. |
| R-055 | Mandatory | Document Management | Provide ability to scan, validate, and store Identification documents provided by applicants. Data retrieved from the documents should have the ability to auto-populate fields, reducing keying errors and saving time. |
| R-056 | Mandatory | Document Management | When documents are scanned the IDMS shall have the ability to alert the operator of mismatched data elements (e.g. name on document does not match demographic data previously captured for the applicant). |
| R-057 | Mandatory | Document Management | Provide the ability to archive badge records automatically on preset schedule following SMF data retention policies. |
| R-058 | Mandatory | e-Badge | IDMS will support the automation of e-Badge and provide a CBP User Role which will allow CBP to approve Seals in IDMS. |
| R-059 | Mandatory | Email Notifications | IDMS shall allow system administrators to add / modify wording in the email templates. |
| R-060 | Mandatory | Email Notifications | Provide capability to send various notifications with reminders and escalations to the Authorized Signatory. |
| R-061 | Mandatory | Email notifications | The IDMS shall have the capability to send email notifications to the Authorized Signatories for various activities as defined by SMF. |
| R-062 | Mandatory | General | The IDMS must meet the badging procedures and regulatory requirements as outlined in the Code of Federal Regulations (CFR) Title 49 Part 1542, the SMF ASP requirements and all other security regulations (including National Amendments and Security Directives). |
| R-063 | Mandatory | General | List the 3rd party licenses provided by the vendor, unit price, quantities, and licenses that the Airport needs to provide for IDMS. |
| R-064 | Mandatory | General | Provide the capability to mask all or specific Personal Identifiable Information (PII) (e.g. SSN) and non-PII (e.g. PIN) data fields for display after initial input. The masking will be based on business rules and allow the airport to modify PII fields. The UI will clearly indicate if the data is entered or not entered or missing. |
| R-065 | Mandatory | General | Provide invalid or non-conforming entries (E.g. red color) on the screen and prevent invalid or incomplete submissions. |
| R-066 | Mandatory | General | Provide ability to make comments private/ secured based on user roles |
| R-067 | Mandatory | General | Allow Trusted Agents or other airport users to create “Hot Notes” that immediately display when the person record is queried. Allow modification or deletion of the “Hot Note” by the person who created it or a supervisor. |
| R-068 | Mandatory | General | User roles should be configurable by the SMF System Administrator and not require users to have multiple log ins/ user roles to be able to complete all their job duties. |
| R-069 | Mandatory | Hardware/ Software Integrations | Physical Access Control System - Velocity-(existing system) |
| R-070 | Mandatory | Hardware/ Software Integrations | Livescan Fingerprint system (Cross Match) |
| R-071 | Mandatory | Hardware/ Software Integrations | TELOS DAC - for execution of STAs, CHRCs, Rap Back and e-Badge; bi-directional, real time with demographic data |
| R-072 | Mandatory | Hardware/ Software Integrations | Computer based training (CBT) platform (SSI) |
| R-073 | Mandatory | Hardware/ Software Integrations | Customs and Border Protection (eBadge Program) |
| R-074 | Mandatory | Hardware/ Software Integrations | DL/Passport credential verification system- to import information extracted from ID documents |
| R-075 | Mandatory | Hardware/ Software Integrations | Watch List and Stop List issuance and distribution |
| R-076 | Mandatory | Hardware/ Software Integrations | Badge Printing using existing badge printers’ system or vendor suggested printer use |
| R-077 | Mandatory | Hardware/ Software Integrations | Touchscreen (if needed with IDMS product) |
| R-078 | Mandatory | Hardware/ Software Integrations | Multi-page high speed document scanner |
| R-079 | Mandatory | Hardware/ Software Integrations | External badge# reader and transmit badge number to IDMS |
| R-080 | Mandatory | Hardware/ Software Integrations | Airport Email system (Outlook, Office 365, etc.) |
| R-081 | Mandatory | Hardware/ Software Integrations | Airport's Active Directory for single sign-on for Airport's internal users (non-AS and non-Applicants) |
| R-082 | Mandatory | Integration DACS | The IDMS shall have capability to provide an automated method to submit the CHRC/Rap Back and STA requests via Telos. Rap Back updates and cancelations must be automated following TSA regulations and completed within the required timelines. STA results should not be able to be modified by the SMF team (only TSA). |
| R-083 | Mandatory | Integration DACS | The IDMS shall have capability to integrate with Telos and submit the data for STA, CHRC and Rap Back. |
| R-084 | Mandatory | Integration DACS | Automatically retrieve results from the DAC and update / populate matched STA results to the existing badge holder or applicant database. |
| R-085 | Mandatory | Integration DACS | The IDMS shall have the capability to provide an automated method to enroll badge holders in the Rap Back program upon submission of fingerprint to DACS and not wait for badge issuance. |
| R-086 | Mandatory | Integration DACS | The IDMS shall provide capability to electronically submit the identity documents to the DAC for both new and renewal badge applications. |
| R-087 | Mandatory | Integration DACS | Provide the functionality to limit the review of background check results to authorized personnel. |
| R-088 | Mandatory | Integration Fingerprint | Livescan Fingerprint system (existing system -Cross Match) |
| R-089 | Mandatory | Integration PACS | When a badge is marked as lost or stolen, the badge must immediately be deactivated in IDMS and the PACS. |
| R-090 | Mandatory | Integration PACS | Provide ability to display doors / gates access that is associated with specific Clearance Codes. |
| R-091 | Mandatory | Integration PACS | IDMS will provide a means to define and create templates or other methods of setting default clearance code / groups for employees of a company based on variables such as company name, company type, badge type, privileges, job title, department/division. |
| R-092 | Mandatory | Integration PACS | Provide capability to auto assign clearance codes at a minimum based on job title, company name, company type, badge type. Allow manual override of the clearance codes (adding or deleting) by the Trusted Agent. |
| R-093 | Mandatory | Integration PACS | Physical Access Control System -Hirsch Velocity |
| R-094 | Mandatory | Integrations Other | Airport's Active Directory for single sign-on for Airport's internal users (non-AS and non-Applicants) |
| R-095 | Mandatory | Record Management | When an Authorized Signatory or badge holder reports a badge as lost or stolen, the badge must immediately be deactivated in the PACS. |
| R-096 | Mandatory | Reports | Generate reports that can be exported in multiple formats (at a minimum |
.csv, .pdf and .xlsx formats).
| R-097 | Mandatory | Reports | Provide SMF pre-defined reports, allowing the user to select or specify the grouping and / or sorting criteria. |
| R-098 | Mandatory | Security Requirements | Integration between IDMS on secure Airport network and systems connected |
via web services to external network (Authorized Signatory Portal, Applicant Portal, CBT, DAC, etc.) must be via secured protocol.
| R-099 | Mandatory | Security Requirements | Have the ability to encrypt sensitive and personally identifiable information at rest and in transit for internal as well as external users (AS and Applicant). |
| R-100 | Mandatory | Security Requirements | The data should be encrypted using Transparent Data Encryption (TDE), when the selected Proposer's application database contains Personal |
| R-101 | Mandatory | Security Requirements | Provide the capability to mask all or specific Personal Identifiable Information (PII) (e.g. SSN) and non-PII (e.g. PIN) data fields for display after initial input. The masking will be based on business rules and allow the Airport to |
modify PII fields. The UI will clearly indicate if the data is missing.
| R-102 | Mandatory | Security Requirements | Interface to manage all secure user logins Trusted Agents, Authorized Signatories. |
| R-103 | Mandatory | Security Requirements | Shall have capability to enforce password policy at a minimum follow the NIST Special Publication 800-63-3: Digital Authentication Guidelines: |
Disallow use of vendor supplied password defaults for system passwords Prevent passwords that are derivatives of the username Enforce password requirements of > = 8 characters and contains characters from 4 of the following 4 categories: Uppercase alphabetic (i.e., A- Z), Lowercase alphabetic (i.e., a-z), - Numeric (i.e., 0-9), Special characters (e.g.,. ! %@*#^ () _+|~) Require user to change password after first login Require user to reset password after a set period (90 days or Airport configurable)
| R-104 | Mandatory | Security Requirements | System provides automated means for user password resets with authentication |
| R-105 | Mandatory | Security Requirements | Times out IDMS web or client sessions according system administrator- configured period of idle time no longer than 15 minutes. The re-login should open the same screen/ page where auto logout triggered. IDMS mist saves |
work prior to auto time-out.
| R-106 | Mandatory | Security Requirements | Limit browser-based modules to accept only HTTPS connections for authentication purposes |
| R-107 | Mandatory | Security Requirements | Undo/rollback feature that reverts badge back to the prior state and logs it. For example, a badge is accidentally terminated, and the user can revert back to the prior state. Feature is controlled by user access and all rollbacks are |
logged R-108 Mandatory Security Requirements Provide system security that is role-based allowing for update or read-only access to specific functions and obfuscation of defined data elements (i.e. SSN not visible or redacted on the screen for all users assigned to a specific role).
| R-109 | Mandatory | Security Requirements | Provide method(s) for the System Administrator to view and maintain user profiles such as: add new users, modify and delete user profiles. |
| R-110 | Mandatory | Security Requirements | Provide details for cyber security based on NIS 800-171 and cyber security |
framework, including not limited to penetration testing, proprietary or 3rd- party, conducted by the vendor
| R-111 | Mandatory | Security Requirements | Provide details of a data breach Recovery Plan, including liability matrix |
| R-112 | Nice to Have | System Audit | Automatic audit trail logging and generate report of all data sent to integrated systems (PACS, DAC, CBT etc.), web calls, acknowledgement received from |
the integrated systems, status of messages - success/ fail, error coding of failure.
| R-113 | Mandatory | System Audit | IDMS shall provide system integration audit report with error codes and actionable information to fix error. |
| R-114 | Mandatory | System Audit | The system should have capability to log and generate report for data updated by any user - table, field, old value, new value, user ID, date/time |
| R-115 | Mandatory | System Audit | Automatic audit trail logging and generate report for all queries and reports run - query/report name or SQL code, date/time, user |
| R-116 | Mandatory | Training | IDMS shall have capability to integrate with the SSI computer-based training system to provision applicant records, training required based on the badge types and privileges requested, retrieve results (pass / fail) and record expiration dates. |
| R-117 | Mandatory | Training | The IDMS shall have the capability to restrict certain training courses. (e.g. Movement Area training is dependent on completing non-movement training.) and automatically assign renewal trainings as required by SMF. |
| R-118 | Mandatory | Violations | Allow an unlimited number of violation types to be added. |
| R-119 | Mandatory | Violations | Record and track airport policy infractions in each identity profile (e.g. safety and security violations). |
| R-120 | Mandatory | Violations | Allow SMF to determine if a badge should be suspended when a violation occurs, the IDMS should not automatically deactivate the badge. |
| R-121 | Mandatory | Violations | Track fulfillment of any necessary corrective actions (e.g. fines, suspension, training). |
| R-122 | Mandatory | Violations | Provide ability to search existing or historical records (entered and migrated in IDMS) of infractions by multiple fields such as name, company, badge number, or violation type. |
| R-123 | Mandatory | Violations | Send violation notices out via email automatically to the Authorized Signatory. |
Dylan sheet
| Functional Capabilities | | | Contractor Response | |
| ID | Functional Area | Capabilities Description | Meets | Comments |
| | | Capabilities (C) | |
| | | Doesn't Meet | |
| | | Capabilities (NC) | |
| FC-001 | Application | Provide capability for the applicant to electronically submit information related to Disqualifying crimes badge holder responsibilities, other airport specific legal language currently available in the badge application. | | |
| Process | | | |
| FC-002 | Application | The applicant portal shall be mobile friendly such that the web portal aligns to various mobile screen sizes without limiting functionality. | | |
| Process | | | |
| FC-003 | Application | The IDMS shall have capability for a website link or APP where the applicant can enter name, DOB, SSN and I9 document, with image upload capability for identity verification. | | |
| Process | | | |
| FC-004 | Application | The IDMS shall have the capability to list all complete applications submitted by the AS. If the applicant portion of the application is not complete the badge application cannot be processed by the badging office. | | |
| Process | | | |
| FC-005 | Application | The IDMS shall have capability to clearly identify the type to application such as new badge application, renewal badge application, badge change (for adding or removing privilege - escort, driving privilege), replacement badge application (name change or lost, stolen or mutilated). | | |
| Process | | | |
| FC-006 | Application | The IDMS shall allow the Trusted Agent to review and modify as necessary all the information submitted by the AS and the applicant. The Trusted agent can Accept or Reject or Cancel the badge application review step. IDMS shall send notification to AS if application is rejected or accepted. | | |
| Process | | | |
| FC-007 | Application | Once the applications are rejected, they will no longer appear in the application list for processing. | | |
| Process | | | |
| FC-008 | Application | The IDMS shall alert the Trusted agent if the new badge applicant already exists and allow the Trusted Agent to review the duplicate record and merge or process individually. | | |
| Process | | | |
| FC-009 | Audit | Audit should allow selection of records for Audit based on company, specific individuals, and badge type. | | |
| FC-010 | Authorized Signatory | The IDMS shall always check and enforce the AS to maintain an active badge, valid security checks, valid AS trainings, in order to keep the AS active and maintain access to the AS portal. | | |
| Functional Capabilities | | | Contractor Response | |
| ID | Functional Area | Capabilities Description | Meets | Comments |
| | | Capabilities (C) | |
| | | Doesn't Meet | |
| | | Capabilities (NC) | |
| FC-011 | Authorized Signatory | IDMS must assign each Authorized Signer a unique user account and password upon completion of the approval process and required training. This user account will be used for submission of employee badge applications and all other business activities performed using the web interface. | | |
| FC-012 | Authorized Signatory | IDMS shall provide and describe mechanisms to incorporate multi-factor authentication for the Authorizing Signatory Portal. The IDMS shall have the capability to implement OTP / authentication codes via text or email. | | |
| FC-013 | Authorized Signatory | The IDMS shall provide capability for the AS to perform at a minimum via the AS web portal, the following functions: enroll new applicants, authorize renewal of badges, submit badge replacement applications for lost, stolen, mutilated, name changes or privilege modification changes, respond to audits, upload supporting documentation for I-9, CBP forms, driving permits, key request form, and other documentation as necessary for the airport operations. | | |
| FC-014 | Authorized Signatory | The IDMS shall have capability to capture all the STA required fields during the badge application process. | | |
| FC-015 | Authorized Signatory | Provide the ability to send via email to a new badge applicant (mandatory field for all applicants), an expiring link to enter applicant regulatory information and acknowledgements application information and attest to a disqualifying felony statement. | | |
| FC-016 | Authorized Signatory | The IDMS shall allow the badge application entered by the AS to be saved prior to submission. The application will be saved for 30 days or user defined timeframe prior to permanently deleting the application from IDMS. | | |
| FC-017 | Authorized Signatory | The IDMS shall permit the Authorized Signer to select the badge type (escort or no escort), AOA privileges, access level / clearance and need for Videx key requests for a new badge application or for existing badges. | | |
| FC-018 | Authorized Signatory | The IDMS shall allow AS to authorize renewal if the employee badge is due to expire within the 30 days of badge expiration. | | |
| FC-019 | Authorized Signatory | At a minimum, the following should be displayed on the dashboard: The AS will see only those companies and badge holders, he / she is responsible for. The AS should see the list of applications submitted, pending, applicant acknowledgements submitted or pending, upcoming badge expirations and badge renewals, unaccounted badges. | | |
| Functional Capabilities | | | Contractor Response | |
| ID | Functional Area | Capabilities Description | Meets | Comments |
| | | Capabilities (C) | |
| | | Doesn't Meet | |
| | | Capabilities (NC) | |
| FC-020 | Authorized Signatory | The IDMS shall allow at a minimum the following badge statuses with capability for the system administrators to add / modify statuses and reason for de-activation: Active, Inactive, Suspended, Terminated, Revoked, Returned, Lost, Stolen, Damaged, The IDMS shall also provide drop down list for "Reason for De-activation" | | |
| FC-021 | Badge Production | Automatically calculate and default the maximum expiration date for each new or reissued badge based on current airport policy. | | |
| | The airport’s typical badging cycle is 24 months however badge expiration dates are tied to a person’s birth month. Other factors that come into play include people with Work Authorization Documents, Visa’s, Permanent Resident Cards, and companies who are on probation due to an excessive percentage of unaccounted for badges. Those badges may be set for a 1-year period or a 6-month period. | | |
| FC-022 | Badge Production | The IDMS shall clearly indicate on the UI if the badge was returned, badge returned date, badge printed date, badge pick-up date. | | |
| FC-023 | Badge Production | When the current date passes an assigned expiration date on a badge, automatically update the badge status to revoked with reason of expired and deactivate the badge in the DAC. | | |
| FC-024 | Badge Production | Allow creation of new badges as replacements for unaccounted (e.g. lost, stolen) badges by copying previous badge details, badge expiration date and establishing a new badge number. | | |
| FC-025 | Badge Production | Print a receipt and send notification to the badge holder and / or Authorized Signatory as proof the badge was issued or surrendered. | | |
| FC-026 | Badge holder Record | IDMS shall permit the Badging Office staff or Trusted Agents to indicate the status of a badge as returned, badge not returned, or lost or stolen. | | |
| Management | | | |
| FC-027 | Badge holder Record | When an AS or badge holder reports their badge as terminated, lost or stolen, the badge must immediately be deactivated in IDMS and the PACS. | | |
| Management | | | |
| FC-028 | Badge holder Record | Provide ability to issue single active badges to one individual working for multiple separate companies. (Up to 3 companies on the badge) | | |
| Management | | | |
| FC-029 | Violations | Allow users with appropriate permissions to add new types (security and safety) of violations. | | |
| FC-030 | Violations | Allow an unlimited number of violation types to be added. | | |
| FC-031 | Violations | Manage a central record of employee’s violations at the Airport. | | |
| FC-032 | Violations | Record and track airport policy infractions in each identity profile (e.g. safety and security violations, no insurance). | | |
| FC-033 | Violations | Record and track repeated infractions, which may warrant re-training of the employee. | | |
| FC-034 | Violations | Track the number of violations in each identity profile. | | |
| FC-035 | Violations | Track penalties relating to a suspension. | | |
| Functional Capabilities | | | Contractor Response | |
| ID | Functional Area | Capabilities Description | Meets | Comments |
| | | Capabilities (C) | |
| | | Doesn't Meet | |
| | | Capabilities (NC)) | |
| FC-036 | Violations | Track fulfillment of any necessary corrective actions (e.g. penalties, suspension, training). | | |
| FC-037 | Violations | Send violation notices out via email automatically to the Authorized Signatory. | | |
| FC-038 | Company | IDMS shall provide capability for the Badging Office staff to enroll a new company and provide at a minimum the following information including but not limited to company name, company start and end dates, company type (For Example: Airline, Local or Federal Government, Contract, Tenants, Vendors, Concessionaires, others) company status, clearance codes/access level assignment configurations, contract information, contract start and end dates, sponsor contractor information. | | |
| FC-039 | Company | IDMS shall provide ability to capture company names as - Business Legal name, doing business as, abbreviated name to be printed on the badge. | | |
| FC-040 | Company | IDMS shall provide the ability to store multiple company addresses, phone numbers and multiple company contacts information including name, email, job title. | | |
| FC-041 | Company | IDMS shall provide capability to configure at company and division level the ID requirements (certain government employees can provide one I9 document), access levels/clearance codes, financials (monthly billing, fee waived), payments (badge fees, other fees), security check exemptions (CHRC, STA, others). | | |
| FC-042 | Company | IDMS shall provide capability for the Badging Office to scan and / or upload documents related to company enrollment. For example, company authorization letter, contract documents, insurance certificate, nominate first Authorized Signatory for the company, and others as required by the Airport. The documents will be saved in the IDMS and be available and the archived/ deleted as per the airport data retention policy. | | |
| FC-043 | Company | The IDMS shall allow tracking of the Company statuses. At a minimum the following should be available Active, Inactive, Suspended, Terminated, and others as per the Airport business requirements. | | |
| FC-044 | Company | The IDMS shall have capability to add Reason for de-activation or add notes to company profile when the company status has changed from active to another status. | | |
| Functional Capabilities | | | Contractor Response | |
| ID | Functional Area | Capabilities Description | Meets | Comments |
| | | Capabilities (C) | |
| | | Doesn't Meet | |
| | | Capabilities (NC) | |
| FC-045 | Company | The IDMS shall allow suspension of a company such that existing active badges will not be automatically de-activated when the status has changed, however will enforce any future processing of the company employees for badge printing or badge renewals. (Example case: company has financial payments due/ defaulted) | | |
| FC-046 | Company | The IDMS shall enforce that a Company in Active status should have at least one (1) active Authorized Signatory. There is no limit on the number of Authorized signatories that a company can designate. Use of global AS or badging office manager for 1st AS enrollment is acceptable. A notification within the IDMS needs to be made to the Badging Office staff. | | |
| FC-047 | Company | The IDMS shall have capability to allow the badging office to set an authorized signatory as Active or Inactive. | | |
| FC-048 | Company | Provide capability for Badging Office to configure default access levels / clearance codes for an approved company. The default access levels / clearance codes will be visible in the company profile. | | |
| FC-049 | Company | Provide capability for the Badging Office or system administrator to modify the default access levels / clearance codes per company business requirements. | | |
| FC-050 | Company | The IDMS should provide capability for badging office manager to perform bulk / volume tasks such as de-activation of badges, badge printing, change access levels/clearance codes by badge type or company or divisions. | | |
| FC-051 | Company | The IDMS shall provide functionality to change company names (e.g. legal name changes and badge printed names) including providing report of all badge holders impacted. Allow corporate name changes while retaining relation to the former corporate name. | | |
| FC-052 | Company | The IDMS shall provide functionality to allow merger of companies (e.g. legal name changes and badge printed names) including providing report of all badge holders impacted. | | |
| FC-053 | Dashboard | The IDMS shall provide immediate notification on dashboard and email notification to the system administrators, badging office and ASC if the connection to any DACS is lost. | | |
| Functional Capabilities | | | Contractor Response | |
| ID | Functional Area | Capabilities Description | Meets | Comments |
| | | Capabilities (C) | |
| | | Doesn't Meet | |
| | | Capabilities (NC) | |
| FC-054 | Dashboard | The IDMS can provide a dashboard for Badging Office staff and the AS. The dashboard should be configurable for each user group and user. | | |
| FC-055 | Dashboard | Provide on dashboard those STA and CHRC results that have not been returned in 10 business days. | | |
| FC-056 | Document | IDMS will enable association of scanned documents with badge applications. IDMS must accommodate for all identification types shown on the Acceptable Documents List (List A, B & C). | | |
| Management | | | |
| FC-057 | Document | Provide ability to restrict viewing of scan and stored documents (e.g. Rap sheets) and mark private based on user roles by permission levels. | | |
| Management | | | |
| FC-058 | Document | Provide Badging Office staff an input form for capturing identification document data with appropriate fields displayed based on the type of identification provided. | | |
| Management | | | |
| FC-059 | Document | Be able to rotate and zoom in to review scanned documents. The upload document formats will be pdf or image files. Use of Adobe acrobat to rotate or zoom is acceptable for pdf files | | |
| Management | | | |
| FC-060 | Document | Provide ability to compare the data retrieved from the documents against the data entered by the AS or Applicant including ability to select data fields to merge or ignore. | | |
| Management | | | |
| FC-061 | Document | Provide the ability to archive electronic documents and badge records automatically on preset schedule following airport data retention policies. | | |
| Management | | | |
| FC-062 | Email Notifications | IDMS shall support the use of templates for emails to the Security Badging Office staff, companies, and Authorized Signers. | | |
| FC-063 | Email Notifications | Provide notification to the Authorized Signatory when a badge status changes within the Authorized Signatory’s company. | | |
| FC-064 | Email Notifications | IDMS shall allow system administrators to add / modify wording within and database references for field values in the email templates. | | |
| FC-065 | Email Notifications | Provide ability to notify Badging Office, AS, and applicant when a specified document in a record expires (e.g. driver’s license, passport, authorization to work). | | |
| FC-066 | Email Notifications | Provide capability to send various notifications with reminders and escalations to the Authorized Signatory, Airport Badging, ASC. | | |
| Functional Capabilities | | | Contractor Response | |
| ID | Functional Area | Capabilities Description | Meets | Comments |
| | | Capabilities (C) | |
| | | Doesn't Meet | |
| | | Capabilities (NC) | |
| FC-067 | Email Notifications | Notifications to AS, applicant and Badging Office for various statuses during badge application process (e.g. pre-enrollment, fingerprinting, security checks complete, training complete (pass/fail), badge issued, violations issued); scheduling appointments (e.g. fingerprinting, document submissions, badge pickup, renewals, key and training, badge applicant -No show to appointments, applicant failed to pick up badge within 30 days from the security checks completed). | | |
| FC-068 | Email Notifications | Notifications to AS, Applicant and Badging Office - Expirations: badge, training, documents, and audit responses. | | |
| FC-069 | Email Notifications | Provide notification if the connection to PACS is lost. | | |
| FC-070 | Financial | Allow payment methods to be defined at individual company levels. (e.g. while one company might be authorized to receive a single invoice at the end of the month for all services rendered by the Security Badging Office, another company may be required to pay for each badge or credential or service with a check or credit card at the time the service is rendered or at the time the appointment is booked.) | | |
| FC-071 | Financial | Provide the capability to manage and track the fees / charges associated with badges, background investigations, and other items issued in the Security Badging Office (e.g. keys, permits, card holders). | | |
| FC-072 | Financial | IDMS shall be capable to generate and export reports that show (itemized or grouped) all the financial transactions by badge holder (name, badge #, date, amount, payment method, payment type, etc.) grouped by company over any period of time (a day, a week, a month, year-to-date, or since system inception). | | |
| FC-073 | Financial | Support user-defined badge billing rate classes by company and badge type, considering CHRC exemptions, external adjudication, and federal employee allowances. | | |
| FC-074 | General | The IDMS shall follow the badging procedures and regulatory requirements as outlined in the Code of Federal Regulations (CFR) Title 49 Chapter XII Part 1542, active aviation security policy enforcement, ASP amendments, National amendments issued and Security Directives (SD) 1542-04-08 or subsequent updates. | | |
| FC-075 | General | IDMS shall assign a Unique ID number for each person employed at the airport regardless of the number of companies they work for and cannot be related to the person's name, SSN, or any other PII data. This ID will be used across all systems and will remain constant for that person. | | |
| FC-076 | General | Allow capability to search the database using multiple fields and combinations of those fields as search criteria. | | |
| Functional Capabilities | | | Contractor Response | |
| ID | Functional Area | Capabilities Description | Meets | Comments |
| | | Capabilities (C) | |
| | | Doesn't Meet | |
| | | Capabilities (NC) | |
| FC-077 | General | IDMS shall be intuitive and easy to follow requiring minimum training. The UI shall drive the user to completing relevant tasks and clearly display next step and missing mandatory information. | | |
| FC-078 | General | The IDMS shall clearly display on the badge holder record the stage / status the person is in at any given time. E.g. Pending security checks, incomplete training, etc. | | |
| FC-079 | General | Ensure standard drop-down lists/master data values are sorted alphabetically (e.g. US states, Country names, Ethnicity,). Ensure commonly used drop down/ master data values are on the top (e.g. United states country when entering Passport or DL) | | |
| FC-080 | General | The IDMS shall have field formatting and validations. For example: age minimum limit configurable, height cannot be in inches only and cannot be 10' or cannot accept alpha characters for age, height, weight. Ensure the UI enforces data type, field length, and formatting limitations as per all the dependent subsystems (i.e. PACS, fingerprinting etc.). | | |
| FC-081 | General | Provide the capability to mask all or specific Personal Identifiable Information (PII) (e.g. SSN) and non-PII (e.g. PIN) data fields for display after initial input. The masking will be based on business rules and allow the airport to modify PII fields. The UI will clearly indicate if the data is entered or not entered or missing. | | |
| FC-082 | General | Provide the capability that the masked data fields are viewable to certain user groups like Airport Security Manager, ASC or designees as determined by the Airport. | | |
| FC-083 | General | Provide ability in the UI to override business rules (supervisor override) on a case-by- case basis to certain user groups (ASC, Security Manager). E.g.: applicant from Law enforcement agencies may not be always exempt from CHRC and STA, allows ASC or designee to override the global rule form the UI for the applicant) | | |
| FC-084 | General | Allow field validations for name fields, date fields, zip codes, phone #s, SSN, DL#, Passports and ARN# etc. Allow selection of country, state where applicable. | | |
| FC-085 | General | Provide invalid or non-conforming entries (E.g. red color) on the screen and prevent invalid or incomplete submissions. | | |
| FC-086 | General | Support entering unlimited notes / comments associated with persons, company, security checks, training, badges, access levels, keys, each of which is automatically user/date/time stamped. | | |
| Functional Capabilities | | | Contractor Response | |
| ID | Functional Area | Capabilities Description | Meets | Comments |
| | | Capabilities (C) | |
| | | Doesn't Meet | |
| | | Capabilities (NC) | |
| FC-087 | General | Restrict Trusted Agent ability to change/delete comments they entered. Allow Security Manager or ASC or other designated Trusted agents to make modification to the comments entered by the Trusted agents. | | |
| FC-088 | General | Provide ability to make comments private/ secured based on user roles | | |
| FC-089 | General | Allow operators to flag a note/comment so that the note/comment will be immediately displayed when any user subsequently accesses the record until the user that made the comment, or a supervisor change or deletes the note/comment. For example: SOC users, LEO or CBP marks a record for suspension or revocation the Trusted Agent should get notification immediately. | | |
| FC-090 | Integration DACS | The IDMS shall have capability to provide automated method to enroll badge holder in Rap back program upon submission of fingerprint to DACS and not wait for badge issuance. Standard Rap Back subscription, cancel and uncanceled rules applicable. | | |
| FC-091 | Integration DACS | The IDMS shall have capability to integrate with DAC and submit the data for STA, CHRC and Rap-back. | | |
| FC-092 | Integration DACS | The IDMS shall have the capability to send notifications to the AS (via email to the AS) if the applicant has failed one or both (STA and CHRC) security checks. The IDMS shall track date when the security checks status was changed. The IDMS shall allow the Badging Office to set the background checks status to Appeals if the Applicant has appealed the CHRC results within 30 days. The IDMS shall limit further processing of training, or badge issuance for the applicant if the background check is in appeals process. | | |
| FC-093 | Integration DACS | The IDMS shall obtain change in status information from the DAC for CHRC and notify the Badging Office when the results are available on the FBI FPRD. | | |
| FC-094 | Integration DACS | Automatically retrieve results from the DAC and update / populate matched STA results to the existing badge holder database. | | |
| FC-095 | Integration DACS | The IDMS shall send notifications to AS and Applicant when security checks are complete, with instructions for next steps. | | |
| FC-096 | Integration DACS | The IDMS shall provide capability to electronically submit the supporting documents to the DAC. | | |
| FC-097 | Integration DACS | Provide the functionality to limit the review of background check results to authorized personnel. | | |
| FC-098 | Integration Fingerprint | Livescan Fingerprint system (existing system – Fulcrum Biometrics software, Green-bit Scanner, or compatible vendor software.) | | |
| Functional Capabilities | | | Contractor Response | |
| ID | Functional Area | Capabilities Description | Meets | Comments |
| | | Capabilities (C) | |
| | | Doesn't Meet | |
| | | Capabilities (NC) | |
| FC-099 | Integration PACS | Update PACS with badge holder, badge, and clearance codes data immediately (within operational acceptable timeframe). Update requests shall be queued for processing without delay. | | |
| FC-100 | Integration PACS | When an employee reports their badge as lost or stolen, the badge must immediately be deactivated in IDMS and the PACS. | | |
| FC-101 | Integration PACS | Provide ability to manage higher level of grouping / mapping of clearance codes based on job titles, privileges (e.g. movement area driving would allow assignment of vehicle gate clearance and emergency privilege mapping to all access). | | |
| FC-102 | Integration PACS | IDMS will provide a means to define and create templates or other methods of setting default clearance code / groups for employees of a company based on variables such as company name, company type, badge type, privileges, job title, department/division. | | |
| FC-103 | Integration PACS | Provide capability to auto assign clearance codes at a minimum based on job title, company name, company type, badge type. Allow manual override of the clearance codes (adding or deleting) by the Trusted Agent. | | |
| FC-104 | Integration PACS | Support an unlimited number of access levels per badge or credential type. | | |
| FC-105 | Integration PACS | Bulk access levels assignments and removals from badge holders | | |
| FC-106 | Reports | All reports be capable of being exported into multiple formats (at a minimum .csv, .pdf and .xlsx formats). | | |
| FC-107 | Reports | The IDMS can provide reports for reconciling badge holder records between DAC and IDMS. | | |
| FC-108 | Reports | The IDMS can provide reports for financial reconciliation of fingerprinting, STA, CHRC and Rap-back fees against the DAC financial reports. | | |
| FC-109 | Reports | Provide ability to list all open, closed, pending violations. | | |
| FC-110 | Reports | Generate reports based on the status of matches (e.g. cleared, under investigation, actual match). | | |
ID#AAABOGwVy1I Jamie Hansen (2024-06-07 23:07:37) @dylan@airbadge.us @nathan@airbadge.us have compared this against the PDF copy submitted and there was a line deleted from the Excel file they gave us. I added the line from the PDF to this file - I'm assuming they still want us to respond to it.
| _Assigned to dylan@airbadge.us_ | FC-111 | Reports | Provide pre-defined reports, in a variety of formats that allow the user to select or specify the grouping and / or sorting criteria. |
| FC-112 | Reports | Easily generate ad-hoc reports or queries without specialized skills (most easily via filtering, sorting, grouping). |
| Functional Capabilities | | | Contractor Response | |
| ID | Functional Area | Capabilities Description | Meets | Comments |
| | | Capabilities (C) | |
| | | Doesn't Meet | |
| | | Capabilities (NC)) | |
| FC-113 | Reports | Provide ability for a system user to create new reports as well as modify existing reports. | | |
| FC-114 | Reports | Daily and monthly reports will be created, stored, and managed within IDMS. Standard reporting tools, such as SQL Server Reporting Services or Crystal Reports must be supported. | | |
This is the start of the file's text. The full file is on GovTribe.