DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

PRIVACY IMPACT ASSESSMENT

Regulation and Certification Infrastructure for System Safety
(RCISS)

August 15, 2008


Table of Contents

Overview of the Federal Aviation Administration (FAA) RCISS Program
Overview of FAA Privacy Management Process for RCISS
Personally Identifiable Information (PII) and RCISS
Why RCISS Collects Information
How RCISS Uses Information
How RCISS Shares Information
How RCISS Provides Notice and Consent
How RCISS Ensures Data Accuracy
How RCISS Provides Redress
How Long RCISS Retains Information
System of Records

Overview of the Federal Aviation Administration (FAA) RCISS Program

The Federal Aviation Administration (FAA), within the Department of Transportation (DOT), has been given the responsibility to carry out safety programs.  The FAA is responsible for:

One of the programs that will help fulfill this mission is the Regulation and Certification Infrastructure for System Safety (RCISS) program.   RCISS will provide the Information Technology (IT) infrastructure to the FAA’s Office of Aviation Safety (AVS) safety workforce so it will have access to safety data at the time and location needed to assess safety factors in real-time.

An infrastructure is the fundamental structure of a system and its architecture determines how it functions and how flexible it is to meet future requirements.  The most familiar infrastructure is an urban infrastructure, which describes the utilities and facilities such as roads, bridges, sewers, and sewer plants, water lines, power lines, fire stations, and other sites and facilities necessary to the functioning of an urban area.  An IT infrastructure consists of the equipment, systems, software, and services used in common across an organization, regardless of mission, program, or project.  The IT infrastructure also serves as the foundation upon which mission, program, and project specific systems and capabilities are built.   The RCISS infrastructure includes mobile and portable devices, workstations and server hardware, operating systems, and database management systems (DBMS) and is the foundation for airmen and aircraft data required for safety applications.  The RCISS infrastructure is viewed as everything that supports the flow and processing of aviation safety information.

The current legacy IT infrastructure supporting AVS is not capable of meeting evolving requirements created by the changes in the aviation and IT industries.  RCISS will redesign the current infrastructure to support data storage, data access, data integration, connectivity, availability, and disaster recovery.  The RCISS Program will support the safety workforce responsible for promoting aviation safety through regulation and oversight of the civil aviation industry.

AVS is the FAA organization responsible for the certification, production approval, and continued airworthiness of aircraft; and certification of pilots, mechanics, and others in safety-related positions.   The two largest offices within AVS are the Aircraft Certification Service and the Flight Standards Service.  The Aircraft Certification Service of the FAA is the office responsible for:

The Flight Standards Service promotes safe air transportation by setting the standards for certification and oversight of airmen, air operators, air agencies, and designees.  The office is responsible for:

RCISS provides an infrastructure for the Aviation Safety Knowledge Management Environment (ASKME) program and the System Approach for Safety Oversight (SASO) applications.  The ASKME program provides Aircraft Certification Service aviation safety professionals with a repository of critical safety technical information and data, as well as with a set of knowledge management and analysis tools for knowledge collection, dissemination, and analysis. The ASKME environment includes a web-based knowledge management portal, collaboration, predictive safety data analysis, integrated data management and reporting, and Aircraft Certification Service process execution tools.  The SASO applications are changing the way Flight Standards Service and the aviation industry oversee and manage safety by realigning
25 independent FAA safety systems into a single System Safety-based enterprise architecture.  SASO applications will serve 4,800 FAA Aviation Safety employees, in eight regions, at more than 120 headquarters and field offices, and is capable of supporting more than 25,000 aviation industry professionals managing aviation safety throughout the United States and around the world.

Though still in the early implementation phase, RCISS will perform four high-level functions:

Overview of FAA Privacy Management Process for RCISS

The RCISS infrastructure will use a web interface for most functions.  This also supports the Paper Work Reduction and E-Government Act priorities, and may include public web sites for some appropriate activities.

Privacy management is an integral part of RCISS.  DOT and FAA have retained the services of privacy experts to help assess its privacy management program, utilizing proven technology, sound policies and procedures, and proven methodologies.  In addition, the RCISS planning team includes participation by FAA’s Privacy Officer.  This individual assists the RCISS program in considering all fair information practices and applicable laws when making decisions that may affect privacy.
The privacy management process is built upon a methodology that has been developed and implemented in leading companies around the country and globally.  The methodology is designed to help ensure that DOT and FAA will have the information, tools, and technology necessary to manage privacy effectively and employ the highest level of fair information practices while allowing FAA to achieve its mission of protecting and enhancing the U.S. transportation system.  The methodology is based upon the following:

Personally Identifiable Information (PII) and RCISS

The RCISS system contains both Personally Identifiable Information (PII) and non-personally identifiable information pertaining to designees, pilots, mechanics, registered aircraft owners, aircraft dealers, and others.  PII contained within RCISS may include:

RCISS may also contain information on manufacturers and other businesses or organizations involved in aviation.  In some cases, a business or organization (i.e., airlines; manufacturers of aircraft, rotorcraft, engines, propellers, and replacement parts) may submit an individual’s name and business contact information (e.g., business address and business telephone number) for inclusion in an RCISS database.  RCISS is not collecting new information, rather RCISS combines information (from SASO and ASKME applications) that the FAA was already authorized to collect  (Paperwork Reduction Act Office of Management and Budget control number 2120-0033).  This information is regulated by the Privacy Act of 1974, as stated in the Representatives of the Administrator System of Records DOT/FAA 830 and General Air Transportation Records on Individuals System of Records DOT/FAA 847.

Why RCISS Collects Information

RCISS collects PII to enable AVS staff to track certificates, monitor, and control designee activities; conduct safety investigations and inspections; and gain knowledge into flight surveillance measures.  AVS is responsible for regulation and oversight of civil aviation; therefore, AVS must review and take action on safety measures pertaining to individual certificate holders, i.e., pilots, navigators, mechanics, etc.  In addition, AVS uses designated aviation industry personnel known as “designees” in roles that include aviation medical examiners; designated airworthiness, engineering, and manufacturing inspection representatives; and designated pilot, mechanic, and parachute rigger examiners.  AVS must ensure that these individuals remain qualified and authorize their continued service in their respective roles.  RCISS receives all PII either directly through forms submitted by the individual, or through additional contact or interaction with the individual.

How RCISS Uses Information

RCISS is the “enabler” for ASKME and SASO applications, providing a communications infrastructure connecting individual members of the safety workforce to centralized databases and other resources.  RCISS is used by AVS, other parts of FAA, and other government agencies, e.g., NTSB, to analyze safety data; manage time-intensive processes such as airman certification, safety inspections, designee and equipment certificate activities; and share information with appropriate people and organizations.  These activities are described in Representatives of the Administrator System of Records DOT/FAA 830 and General Air Transportation Records on Individuals System of Records DOT/FAA 847 .

How RCISS Shares Information

The SASO and ASKME applications are primarily for the AVS safety workforce.  In some cases, AVS shares information in RCISS with other FAA organizations, or other government agencies, e.g., NTSB and federal, state, and local law enforcement agencies.  A description of how RCISS shares information is mentioned in the Aviation Records on Individuals System of Records Notice DOT/FAA 847 .  In addition, system connectivity will be authorized and monitored through Memorandums of Understanding that define the information to be transferred, protocols, recipients, security, authorized uses, and other protections.

How RCISS Provides Notice and Consent

The RCISS infrastructure will include several public web sites to facilitate online transactions.  RCISS will receive data directly through forms submitted by the individual.  The web sites that collect PII provide site-specific notice and consent information.  All web sites have a System Use Notification message to inform potential users that (a) they are accessing a United States Government information system; (b) system usage may be monitored, recorded, or subject to audit; (c) unauthorized use of the system is prohibited and subject to criminal and civil penalties; and (d) the use of the system indicates consent to monitoring and recording.  These web sites will also post an accurate privacy policy that contains all sections required by the E-Government Act of 2002.

How RCISS Ensures Data Accuracy

RCISS receives data either directly through forms submitted by the individual, or through additional contact or interaction with the individual.  The length of time a record remains within the RCISS system is governed by the National Achieves and Records Administration NARA retention schedule and, the FAA maintains a retention policy that addresses system data retention and destruction and applicable NARA-approved retention periods.

Under the Privacy Act, individuals may request searches of RCISS data to determine if any records pertain to them.  This is accomplished by any individual sending a request to:

Federal Aviation Administration
ATTN:  RCISS Program Manager, Room 738
800 Independence Avenue, SW
Washington, DC 20591

Individuals wanting to contest information about them that is contained in RCISS should make their requests in writing, detailing the reasons why the records should be corrected.  Requests should be submitted to the attention of the system owner at the above address.

How RCISS Provides Redress

As provided for by the Representatives of the Administrator System of Records Notice under the Privacy Act, individuals with questions about privacy and RCISS may contact the FAA directly at the below address.  If RCISS also includes a public website section, the posted privacy policy will provide additional contact information for FAA’s Privacy Officer.

Federal Aviation Administration
ATTN:  RCISS Program Manager, Room 738
800 Independence Avenue, SW
Washington, DC 20591

How RCISS Secures Information

RCISS will take appropriate security measures to safeguard PII and other sensitive data.  RCISS will apply DOT security standards, including but not limited to routine scans and monitoring, back-up activities, and background security checks of FAA employees and contractors.  RCISS will control access to information and limit the information collected and stored to the minimum necessary to accomplish the intended purpose.
The following matrix describes the levels of access and safeguards around the RCISS roles as they pertain to PII.

ROLE

ACCESS

SAFEGUARDS

User

  • Submit, access, change own profile information

 

  • User-set user name and password
  • Account set-up approved by Site Administrator 
  • Passwords expire after a set period
  • Minimum length of passwords is 8 characters
  • Passwords must be combination of alpha/numeric/special characters
  • Accounts are locked after a set number of incorrect attempts

Site Administrator

  • Search and view user names and profile information
  • Grant User accounts, reset account passwords, view access log information
  • Delete profiles
  • View, search, add, change, and delete all information in database
  • User-set user name and password
  • Account set-up approved by program management
  • Passwords expire after a set period
  • Minimum length of passwords is 8 characters
  • Passwords must be combination of alpha/numeric/special characters
  • Accounts are locked after a set number of incorrect attempts
  • Must access system from limited number of access points, each of which also has user name/password access control.

How Long RCISS Retains Information

RCISS retains and disposes of information in accordance with the approved records retention schedule as required by the National Archives and Records Administration (NARA).

System of Records

RCISS will contain information searched by name and other unique identifiers that is part of an existing system of records subject to the Privacy Act.  You can find applicable RCISS System of Records Notices at http://www.dot.gov/privacy/privacyactnotices/faa.htm; specifically DOT/FAA 830 and DOT/FAA 847.


See www.faa.gov/about/mission/activities for more information about FAA activities.

Within this document ‘RCISS,’ ‘RCISS system,’ and ‘RCISS infrastructure’ are used interchangeably.

Definition based on www.cio.gov/documents/CORE_Governance_Process_11_28_2005.doc.

See http://www.faa.gov/about/office_org/headquarters_offices/avs/ for more information about the AVS organization.

See http://www.faa.gov/about/office%5Forg/headquarters%5Foffices/avs/offices/air/ for more information about the Aircraft Certification Service office

See http://www.faa.gov/about/office%5Forg/headquarters%5Foffices/avs/offices/afs/ for more information about the Flight Standards Service office.

A Designee is a representative of the FAA Administrator authorized by law to examine, test, and make inspections necessary to issue airman or aircraft certificates. However, a designee is not considered an employee of the U.S. Government, and is not federally protected for the work performed or the decisions made as a designee.  See http://www.faa.gov/other_visit/aviation_industry/designees_delegations/designee_types/ for more information on FAA designees.

See System of Records Notices at http://www.dot.gov/privacy/privacyactnotices/faa.htm

See System of Records Notices at http://www.dot.gov/privacy/privacyactnotices/faa.htm

See System of Records Notices at http://www.dot.gov/privacy/privacyactnotices/faa.htm

See System of Records Notices at http://www.dot.gov/privacy/privacyactnotices/faa.htm