Doc. No.: 28 TRS SRS 0089  1 Systems Requirements Document for Environmental Terminology Services Developed for Request for Comment/ Request for Information November 3, 2005 Revised November 8, 2005 U. S. Environmental Protection Agency Office of Environmental Information Office of Information Collection Collection Strategies Division Data Standards Branch Doc. No.: 28 TRS SRS 0089  2 Doc. No.: 28 TRS SRS 0089  3 TABLE OF CONTENTS 1.0 INTRODUCTION .................................................................................................. 4 1.1 Project Background........................................................................................... 4 2.0 SYSTEM DESCRIPTION...................................................................................... 4 2.1 Business Objectives.......................................................................................... 4 2.2 Anticipated Users/ Stakeholders ........................................................................ 5 2.3 Concept of Operations ...................................................................................... 5 3.0 SYSTEM ARCHITECTURE.................................................................................. 6 3.1 Business Process Model ................................................................................... 6 3.2 Use Scenarios................................................................................................... 7 3.2.1 Create A Terminology Resource for a New Project.................................... 7 3.2.2 Map Terminology for Interoperability.......................................................... 7 3.2.3 Supply Terminology for Content Management System.............................. 8 3.2.4 Conduct a Broad Based Search in Support of a Regulatory Investigation .9 3.2.5 Develop an XML Schema or DTD for a Dataset......................................... 9 3.2.6 Check a Document with an Environmental Spell Checker ....................... 10 3.2.7 Select a Definition from an Environmental Dictionary .............................. 10 3.2.8 Create an Environmental Glossary .......................................................... 10 4.0 Conceptual Data Model ...................................................................................... 10 4.1 Technical Environment.................................................................................... 13 5.0 SYSTEM REQUIREMENTS ............................................................................... 14 5.1 Content............................................................................................................ 15 5.2 Relationships................................................................................................... 16 5.3 Metadata for terms .......................................................................................... 16 5.4 Metadata for term sets .................................................................................... 17 5.5 Development and Maintenance....................................................................... 17 5.6 Searching the Repository ................................................................................ 17 5.7 Comparing Terms in the Repository................................................................ 18 5.8 Display and Print ............................................................................................. 18 5.9 Data Exchange................................................................................................ 19 5.10 User Interface.................................................................................................. 19 5.11 Validation and Error Prevention....................................................................... 19 5.12 Workflow ......................................................................................................... 19 5.13 System Interfaces............................................................................................ 21 5.14 Non Functional Requirements......................................................................... 22 5.14.1 Usability.................................................................................................... 22 5.14.2 Performance............................................................................................. 22 5.14.3 Availability ................................................................................................ 22 5.14.4 Standards................................................................................................. 22 5.14.5 Security .................................................................................................... 24 5.15 Support Requirements .................................................................................... 24 5.15.1 Training .................................................................................................... 24 5.15.2 Documentation......................................................................................... 24 5.15.3 System Acceptance/ Testing..................................................................... 24 5.15.4 Change Control ........................................................................................ 24 Doc. No.: 28 TRS SRS 0089  4 1.0 INTRODUCTION 1.1 Project Background The Terminology Reference System ( TRS) ( http:// www. epa. gov/ trs) is a part of the Environmental Protection Agency's System of Registries ( http:// www. epa. gov/ sor). The TRS was developed in 1997 and has not been updated or revised since. The TRS is a compilation of collections of terms from the Agency program offices and the states. These take all sorts of forms including dictionaries, glossaries, key word lists, taxonomies, data dictionaries, and thesauri. There is no consistency or common format. The entries have been captured in their original formats. Some of the TRS collections have definitions and relationships but many of the collections are simple lists of terms. The TRS also contains the General European Multilingual Environmental Thesaurus ( GEMET). GEMET contains 6,000 terms and definitions in 26 languages. GEMET is utilized as the terminology search tool for EIONET, the European Environment Agency's web site ( http:// www. eionet. eu. int). US EPA translated the GEMET terminology into American English with the intention of using some of its multilingual capability in retrieval of US EPA web documents. However, the multilingual retrieval capability has never been developed. The current TRS search capability and user interface is very basic permitting only alphabetical and resource searches. Other than the ability to search across all resources, there are no links between/ among terms or concepts in these resources. The TRS is not well known and scarcely used in the Agency.

Over the years there has been no modernization effort. And yet, the needs of the Agency for terminology are becoming more sophisticated. We are looking beyond dictionary capabilities. The Agency is moving in the direction of extending and enhancing web services and portal technologies. Both web services and portals are dependent on having robust terminology support so that like things called by different names can be integrated through meaning. Web services will enable programs providing simple services to interact with each other and deliver added value services. The portal will synchronize information around a role, process or project to improve decision making. Web services and portals are just the beginning of semantic management of content. The Agency must begin to put in place the type of terminology system able to feed these new semantic technologies. Only then can it use these new capabilities to improve its business processes and services.

2.0 SYSTEM DESCRIPTION 2.1 Business Objectives The Agency is seeking a commercial off the shelf ( COTS) and/ or Government off the shelf ( GOTS) software package( s) to match the user/ system requirements. The Agency will also consider customization of a COTS/ GOTS and the integration of several COTS/ GOTS products.

Part of EPA's vision is to see the TRS evolve from being just a terminology repository, into a suite of Environmental Terminology Services ( ETS). It will always remain a repository for environmental terminology and terminology structures ( taxonomies, thesauri, ontologies, dictionaries, etc.). However, the environmental terminology contained in the repository will be enriched. Through use and curation, the TRS will evolve from a term based system to a concept based system. The concepts the ETS contains, along with their terms and definitions, will have sufficient metadata to enable those concepts to be used as the building blocks for the creation of business driven Agency terminology structures ( taxonomies, thesauri, etc.) The repository will also contain an authoritative controlled vocabulary for the Agency which can serve in the creation of glossaries for web pages and documents, a common vocabulary for search engines, and in the development of rules and regulations.

In addition to being a repository, the ETS will offer services which will include 1) tools to assist users in the creation of business driven terminology structures, 2) the ability to serve up terminology machine to Doc. No.: 28 TRS SRS 0089  5 machine, 3) terminological dictionary interfaces that can be customized for a user's web page, and 4) the capability for ETS terminology stewards to input terminology and edit their terminology structures.

Ultimately, the ETS will support the implementation of semantic web technologies including software agents using ontologies developed by extending and enhancing the terms, relationships and rules surrounding the concepts relevant to a specific business process.

ETS will be much more marketable and many times more useful, once it is shaped to fit the actual needs of users. After the ETS is accepted as an enterprise solution, Agency costs will be lowered by centrally maintaining terminology and terminology metadata. In addition, the quality of the data will be improved as the currency of the data will automatically be maintained in a collaborative fashion by terminology stewards. The development of a robust ETS will also enable the Agency to take advantage of efficiency gained through semantic management technologies. Ultimately, the ETS will be the source of a standardized terminology for the Agency which will improve data quality in data integration and exchange.

2.2 Anticipated Users/ Stakeholders EPA anticipates a number of users. These include:

IT staff including IT specialists, managers, security specialists, system analysts, system architects and system planning specialists Decisions makers including Program Managers, Environmental Analysts, Research Scientist, Data Collection Managers, Lawyers, Emergency Response Staff, Policy Managers and Regulators Information professionals including Librarians, Terminology Experts, Records Managers, Data Standards Experts, Web Content Managers, and Information Specialists General users including Tribal Experts, State Environmental Agency staff, and the general public interested in environmental issues More specifically the ETS will be used by terminology stewards who have responsibility for maintaining certain term sets and by developers of taxonomies for EPA's content management and portal systems.

The use scenarios related to these stakeholder groups are provided under Use Scenarios ( Section 3.2) below.

Many of the users listed will use the ETS " behind the scenes", with the output from the ETS embedded or accessed by other systems, including EPA's Content Management System, EPA portals and desktop portlets, and search engines. Both humans and systems will use the content of the ETS. Therefore attention must be paid to both types of interfaces.

2.3 Concept of Operations The ETS will be web enabled. It will be accessible 24/ 7. There will be system administrator( s) and terminology stewards available to maintain the integrity of the content and software. To ensure that ETS is well maintained, the stakeholders will meet periodically to discuss new technology in the marketplace, advances in terminology practice and recommend changes to the system.

The modernization will include both the acquisition of modern software and redesign of the process for the management of the content. The software must be able to organize, advertise and manage Doc. No.: 28 TRS SRS 0089  6 concepts/ information. It must be able to generate a controlled word list, glossary, taxonomy, thesaurus, and ontology. It will have an internal capability to check for multiple definitions of a term depending on the context. It will be able to make comparisons of terms and definitions based on meanings. It will become the authoritative source for terms, and contain rigid security features for the protection of the system. The process for management will include a system of terminology stewards who, through a system of controlled access, will input and maintain definitions and terms to the database.

The EPA envisions that the ETS will provide the terminology for semantic management functions within the Agency. The design team will also be looking at the use of advanced linking and hyper linking capabilities to increase referencing abilities, multilingual options, and various methods of comparing terms and terms sets. This will enable EPA to collaborate more fully internally and with the health community, scientific community, environmental industry, and the international environmental community.

The ETS will support the implementation of the Federal Enterprise Architecture ( FEA) ( http:// cio. gov ) to enhance interoperability across business lines within the federal government, for example with other science and regulatory agencies.

3.0 SYSTEM ARCHITECTURE 3.1 Business Process Model While there are a number of informal processes in place at this time for the development of terminologies and vocabularies, EPA does not have a formal business process model for the development and governance of terminology. Work is currently underway on an EPA wide taxonomy for content management and information architecture on the web, but the process for ongoing maintenance of such a taxonomy and the integration of that work with the ETS has not yet been determined.

Prior to implementing the ETS and in conjunction with stakeholders and developers working on the other systems, one or more processes will be put into place. However, the business process for the ETS will change over time. The processes may be real time or in batch. Some processes may require more human intervention and review while others will require the ETS to respond machine to machine. A key requirement is for a system that will allow a number of business process models to be used depending on the requirements and the system and group with which the ETS is to be interfaced.

A major part of the development of the ETS will be the development of a process and governance for stewardship and curation of term sets and eventually concepts and ontologies across the enterprise. The governance structure is likely to involve a number of layers, and therefore, a number of roles, which may change over time as the ETS functionality and content mature.

Given the enterprise wide nature of the ETS, the fact that it is a redesign of an existing system, and that it will act as an authoritative repository for terminology that will be used by other systems, the following business process models are likely.

New terminology will be suggested by a user of any of these systems, including the ETS itself, and perhaps automatically by one of the systems. This new terminology will be staged for review by the stewards of a particular system or by the coordinators of the ETS. Once the term or concept has been approved, it will be connected to one of the term sets in the ETS and a minimal record will be created.

New terminology may also enter into the system by virtue of updates to the existing term sets from external sources. For example, as the GEMET Thesaurus is maintained, new versions will be ingested into the ETS. The GEMET Thesaurus will include new terminology or changes to the terminology, definitions, etc. that existed in the previous version. Doc. No.: 28 TRS SRS 0089  7 3.2 Use Scenarios The following use scenarios were developed based on interviews or discussion with key stakeholder groups. It is EPA's intent to have vendors address these use cases in the formal response and in any best and final presentations.

3.2.1 Create A Terminology Resource for a New Project The information manager for a recently funded project/ program within the EPA needs to create a taxonomy to organize digital materials and paper files. She accesses the ETS to look for existing terms that can be used. Since the program is related to Air Quality and Health, she accesses the two topic trees. At first she browses the individual resources that have been categorized as applicable to Air Quality and Health. She selects these two resources and then browses them ( using a visualization tool) to get an overview of the kinds of topics that are included. Based on this she finds some hierarchies of terms ( trees) and individual terms that may be useful. She selects the trees and terms and downloads them into a tool that allows her to create a specialized resource based on this input.

In addition to selecting terms based on browsing, she accesses the ETS with a text search on key terms. The results provide exact and near matches ( including truncated and stemmed terms). She can review the entire record, including the source of the term, the level of authority, and the definition. Individual terms may be selected with or without their hierarchy ( if applicable) or other parts of the record such as the scope note ( definition).

The tool allows the terms and hierarchies to be imported, displayed and manipulated. The tool tracks changes or additions to relationships and scope notes ( definitions) and other key metadata. She can also add new terms. These " new terms" may be completely new or they may have been in the ETS, in some form, but were not identified by the information manager.

Upon completion of the new resource, the information manager submits the resource back to the ETS. A series of validation checks are performed to ensure the quality of the information that is submitted to the ETS. The information manager assigns a curator, which may be the information manager or someone else, who has been trained to perform this function. A report of the upload is provided not only to the curator but to the ETS coordinator. The changes and new terms are made available in a candidate status within the ETS until they have been approved by the ETS coordinator.

3.2.2 Map Terminology for Interoperability As part of an international project agreement, the U. S. and Europe must develop joint reporting mechanisms based on environmental indicators. However, the U. S. and Europe have different definitions for key terms used in the development of the indicators. In addition, the Europeans must support the official languages of the European Union.

The information managers collect their respective indicators and definitions. The ETS is populated with these resources. The information managers work collaboratively to map the terms used by the U. S. and the various multilingual terms used in Europe in order to support the terms of reference documents, the agreements and the reporting mechanism. The terminology mapping is then used with the respective metadata registries in order to identify the appropriate datasets and to determine transforms that can be used to make the data more interoperable.

3.2.3 Develop and Register a Consensus Glossary The EPA and State and Tribal partners are undertaking a new project. During the discussions it becomes apparent that there is no consensus on the terms and the definitions of the terms in this Doc. No.: 28 TRS SRS 0089  8 particular area. While in the meeting, the partners access the ETS. They search for relevant terms and any definitions that are available. In some cases they agree on the terms and their definitions, while in other cases new consensus definitions are needed in order to develop appropriate terms of reference for this project. In still other cases, the terms do not exist in the ETS. In these cases, the terms are registered as candidate terms. Over the course of many meetings, they are able to create a consensus glossary ( with definitions) that allow the work on the project to move forward with common terms of reference.

3.2.4 Supply Terminology for the Content Management System The Content Management System is intended to organize and provide search support for documents, web sites and other information created by EPA. Part of the CMS is the development of a taxonomy for presentation and navigation of such information. The key to the CMS is the assignment of metadata for each piece of content.

A web content manager has recently authored content related to EPA's latest success in brown fields cleanup. She provides the content to the CMS so that it can be used by others in press releases, articles, on the web site and provided for records management. As part of the assignment of metadata for the CMS, she accesses terms provided to the CMS from the ETS. In addition she adds any terms that are not found. These new terms are extracted from the CMS and provided to the ETS curator for incorporation into the ETS.

<IP_ADDRESS> Add a Node to the Enterprise wide Taxonomy from within the CMS An EPA Web Content Manager needs to classify a new document according to an enterprise taxonomy of topics. The content refers to a topic that does not yet exist in the enterprise wide taxonomy. Through the CMS interface, she adds the node in what she believes is the appropriate place. However, she does not have authorization to make changes to an enterprise wide taxonomy; therefore, her submission sets off a workflow for review by an enterprise reference librarian. The new term appears in the CMS only after it has been approved. When it is approved, it kicks off an e mail to the Web Content Manager, who classifies the document with the new category.

<IP_ADDRESS> Add a Node to the CMS specific Taxonomy from within the CMS An EPA Web Content Manager uses a web specific list of audience types to tag content according to target EPA audiences. As a Senior Web Manager, she is authorized to revise this list, which is stored in the central ETS. Within the CMS she adds a new audience type to the list. It appears immediately within the CMS and she and her co workers may use the term when tagging content for audience going forward.

<IP_ADDRESS> Apply Categories and Terms from the ETS within the CMS An EPA Content Contributor adds new content, and ( depending on the content type he selects and perhaps other implicit metadata) is prompted within the author flow to supply explicit metadata. Values come from the central ETS  either real time or as a nightly cache  but are displayed differently according to structures and rules. For example, topic values are represented as navigable trees, with multiple facets. The Content Contributor can apply multiple categories from within and across trees. Other controlled terms are flatter; for example, Audience is represented as check boxes or multi selects in a select box. To the extent " Office" cannot be inferred from the Contributor's log in, he must select Office from a radio button listing. Doc. No.: 28 TRS SRS 0089  9 <IP_ADDRESS> Autosuggest Categories and Terms When the content contributor goes to tag new content, the CMS scans the text and suggests categories and keyword terms based on its " reading" of the text. All terminology is supplied to the CMS from the ETS. Assume that the auto classification subsystem has been at least minimally " trained" in advance. The Content Contributor reviews these suggestions manually and revises them as necessary.

<IP_ADDRESS> Revise or Add Metadata upon Transition to the Web CMS Repository An official EPA document is finalized within a document management repository. It has been fully tagged according to print and retrieval needs to that point. Upon finalization, the business rules within the system dictate that the document is converted to HTML and PDF and those renditions inserted into the Web CMS repository. Using an ETS based thesaurus, the Web CMS applies additional metadata  such as audience and additional access terms  to those renditions, based on existing metadata associated with the document.

<IP_ADDRESS> Invoke Retention Rules Based on Metadata A Content Manager adds a new document to the CMS. Based on a combination of implicit and explicit metadata, the CMS auto declares the document a record. At that point, it applies retention specific metadata from the ETS. As necessary, a " hold" is placed on the Web version and it is managed as an official record in situ or the authoritative document is transferred to a records repository.

<IP_ADDRESS> Generate Pages and Page Elements Based on Metadata The CMS, either in real time or on scheduled intervals, reads categories out of the ETS or a local cache to generate metadata based navigation elements, directory structures, and custom index pages.

3.2.5 Conduct a Broad Based Search in Support of a Regulatory Investigation A member of the EPA legal department must conduct a broad based search across federal, state and publicly available information regarding the regulation of a particular industry. The terminology related to this subject varies greatly. The lawyer accesses the ETS to determine all the terms related to the process being researched.

The ETS provides the term as it appears in all the ETS resources. The lawyer can choose to narrower the list by resource, language, approval status, source, etc. The lawyer can choose to display broader terms, narrower terms, or any related terms ( those that have more specific RT relationships are automatically included in this category, but more precise relationships are also identified in the display to provide more precision).

The lawyer selects terms. The terms are presented with the appropriate Boolean logic. The lawyer provides the query to both internal and external search engines.

3.2.6 Develop an XML Schema or DTD for a Dataset A database administrator is developing a database to house a new dataset for monitoring asthma and various particulates. The agency policy is that, whenever possible, data elements and corresponding XML tags should be selected from the XML Registry and the EDR, in order to promote interoperability Doc. No.: 28 TRS SRS 0089  10 and integration of data. The database administrator first searches these two registries in the SOR, but finds no previously developed element. He then searches the ETS for a concept that can be used to name and define the new data element.

He searches the ETS by term. The ETS responds with uses from all sources. He then limits the results to those terms that are approved for EPA official use. It turns out that the term he queried is not the official term, but there is an official term which is a synonym for it. The database administrator selects this term for use in his application.

The term usage is updated in the ETS to reflect the fact that it is proposed for use with this system/ dataset. However, this is only a temporary status. When the system/ dataset moves from development to production, the element's status is also changed to reflect its approved usage.

3.2.7 Check a Document with an Environmental Spell Checker An EPA researcher is working on a journal article. The authoring process is supported by a spell checker for environmental protection. The content of the ETS that meets certain criteria ( authority status, source, approval status, audience, etc.) is extracted and provided as a spell checker. This spell checker can be loaded as an add in to existing spell check dictionaries, including those used for word processing and email applications. The extracted terms from the ETS are enhanced with special routines to handle morphological variants, such as adverbs, singular versus plural, etc.

3.2.8 Select a Definition from an Environmental Dictionary A Congressional staffer is working on draft legislation for regulating a chemical that has been determined to be detrimental to human health. In order to ensure continuity between this draft legislation and previous related legislation, the staffer accesses the appropriate dictionary while in the word processing software.

The content of the ETS that meets certain criteria ( authority status, source, approval status, audience, etc.) is extracted and provided in an alphabetical list with one or more scope notes ( definitions) as a dictionary. This dictionary is made available, in various forms, to the public, decision makers, Congressional staffers, or researchers.

He searches the dictionary for the process that is being regulated. The ETS provides a scope note ( definition) that has been used before. It also provides a link to the related chemicals in the Chemical Registry and to the regulation/ legislation that previously defined or used the process term. Having looked up the process, the Congressional staffer copies the definition from the ETS into the document that he is creating.

3.2.9 Create an Environmental Glossary A publications manager wants to create a specialized glossary for a report on brown field technologies. Based on the audience/ office metadata elements and the terms related to the term " brown field", he selects terms and their definitions. The ETS provides the capability to display the terms in alphabetical order followed by the appropriate definition for the context. He has the option to include all the terms or to process it against the terms that actually appear in the report.

4.0 CONCEPTUAL DATA MODEL Doc. No.: 28 TRS SRS 0089  11 The Conceptual Data Model is based on ISO 1087 1. A graphical representation of 1087 1 is provided below. The terms used in the model are defined in the ISO standards listed in Section 5.14.4. Doc. No.: 28 TRS SRS 0089  12 Object Property Concept Characteristic Concept System Representation Designation Definition Term Name Concept Relation Hierarchical Associative Spatial Causal Temporal Generic Partitive Concept Type Superordinate Subordinate Co ordinate Generic Comprehensive [ has]* / is of is abstraction of /[ maps with]* is of / has represented by / represents contained in / contains contains / contained in types concepts in / has type concepts of Specific Partitive Subject Field Concept Field has / is of has / is of has / is of Special Language 1087 1 Summary Type of Characteristic is categorized by / categorizes used as criterion to establish / established using Doc. No.: 28 TRS SRS 0089  13 The initial content in the ETS will be focused on terms and term sets. However, over time, some of the content will be enhanced into a concept based system as reflected in the Conceptual Data Model. The ETS must serve current needs and also evolve into a richer environment; the system must support partial implementation of this conceptual model. For example, term sets that are in the current ETS must be migrated to the ETS without losing current information or demanding the completion of information that is not available at the time of migration. Some sets will be sets of terms, without connections to concepts, definitions or relationships. The ETS must allow these simpler structures to be imported and maintained, while allowing additional information, such as relationships, designations and definitions to be added over time. For example, special projects or routine curation of the ETS may over time connect separate terms around a single concept, assign " approved or preferred" attributes, or specify relationships or more granular relationships than those that exist upon original import into the ETS.

4.1 Technical Environment The EPA technical environment is changing as are many of its systems. The anticipated environment is centered on the use of Oracle for database management, NorthernLights for unstructured search, Oracle Portal for portal development, and Documentum for enterprise wide content management of documents as well as web content. However, EPA is seeking an ETS environment that is open enough to allow this technical environment to change over time, allowing for the interchange of components without major impacts on the ETS. As the ETS becomes an environmental tool, State, international and public users of the ETS may want to interface a variety of their own systems with the ETS, so an open environment based on standards, XML and web services is desirable.

The Agency, through the work of the Exchange Network and its Central Data Exchange ( CDX) ( http:// www. exchangenetwork. net/ ), is moving in the direction of extending and enhancing Web service capabilities. These services permit the aggregation of large quantities of information across different software applications, running on a variety of platforms and/ or frameworks. Web services are dependent on having robust terminology support so that like things that are called by different names can be integrated through meaning and so that programs providing simple services can interact with each other in order to deliver sophisticated added value services.

The Agency is piloting portal technology as a collaborative decision management solution within the enterprise. It is envisioned that the portal will support a convergence of collaboration, knowledge management, and business intelligence. The portal accesses content from disparate data sources; synchronizes information around a role, process or project; allows users to collaborate with subject matter experts throughout the decision network for insight and experience. Key to the success of the Portal Project will be the development and use of terminology to bring information together around meaning.

The Terminology Reference System is and will continue to be a part of a suite of registries ( EPA's System of Registries) based on ISO 11179 ( http:// metadata standards. org/ 11179/). The anticipated interaction among the registries is shown in the following diagram. Doc. No.: 28 TRS SRS 0089  14 20 System of Registries Semantic Vision System of Registries Semantic Vision Registry of EPA Applications and Databases ( READ)

Data Element Concepts, Value Meanings Environmental Data Registry ( EDR) Data Dictionaries Thesauri Classification Schemes ( Taxonomies) Terminology Reference System ( TRS) System Ontologies Data Models Permissible Value Lists Business Area Ontologies Data Element Names and Definitions Controlled Vocabularies Data Standards Terms System Inventory Black   Current Capability Red   Future Capability and Relationships 5.0 SYSTEM REQUIREMENTS The following requirements have been gathered from a variety of stakeholder groups. Priorities are provided. N= Necessary. D= Desirable. F= Future. Doc. No.: 28 TRS SRS 0089  15 5.1 Content <IP_ADDRESS> The system shall have the capability to build and maintain a variety of term set structures, including simple term lists ( pick lists), taxonomies, thesauri, glossaries, gazetteers, etc. ( N)

<IP_ADDRESS> The system shall have the capability to build and maintain ontologies. ( D)

<IP_ADDRESS> The system shall maintain concepts, associated terms, relationships between concepts, term definitions, meanings, synonyms, abbreviations, acronyms, context, and note fields. ( N)

<IP_ADDRESS> The system shall support the migration and storage of terms from the existing TRS. The resources currently available in the TRS are listed at http:// iaspub. epa. gov/ trs/ SEARCH$. STARTUP# 2 ( browse down to Information Resource search, keep the keyword field blank, keep " All" in the Resource Type field, and press Begin Search). ( N)

<IP_ADDRESS> The system shall have the capability to associate multiple terms with a concept. ( N)

<IP_ADDRESS> The system shall have the capability to maintain an approved ( or preferred) term attribute by context, if necessary. ( N)

<IP_ADDRESS> The system shall have the capability to maintain an authoritative definition attribute. ( N)

<IP_ADDRESS> The system shall have the capability to maintain an authoritative form or representation attribute. ( N)

<IP_ADDRESS> The system shall have the capability to store terms in upper, lower and mixed case. ( N) Doc. No.: 28 TRS SRS 0089  16 <IP_ADDRESS> The system shall support foreign language terms. ( N)

<IP_ADDRESS> The system shall handle non roman alphabets ( Unicode UTF 8). ( N)

<IP_ADDRESS> The system shall store common misspellings of terms to support aliases from the misspellings to the correct spellings in search systems. ( D)

<IP_ADDRESS> The system shall associate terms with a type of audience or other context. ( N)

<IP_ADDRESS> The system shall cite references for key elements such as term definitions and to hyperlink to reference materials in digital form. ( D)

<IP_ADDRESS> The system shall maintain scientific notation. ( D)

5.2 Relationships <IP_ADDRESS> The system shall have the capability to assign and manage relationships between concepts. ( N)

<IP_ADDRESS> The standard relationships Broader Term, Narrower Term, and Related ( Associative) Term shall be available. ( N)

<IP_ADDRESS> Hierarchical relationships shall be further specified through standard relationships such as partitive and generic. ( N)

<IP_ADDRESS> Hierarchical and Associative relationships shall be further specified through user defined relationships, both uni and bi directional. ( N)

<IP_ADDRESS> The system shall have the capability to label terms as abbreviations or acronyms and to cross reference them to the full versions of terms. ( N)

<IP_ADDRESS> The system shall have the capability to relate taxonomies created from the ETS to their parent collections. ( D)

5.3 Metadata for terms <IP_ADDRESS> The system shall have the capability to record the date of entry, date of modification, language, encoding scheme ( such as the transliteration scheme used), responsible individual or group, for terms and specific components of the concept record, such as definitions. ( N)

<IP_ADDRESS> The system shall assign unique identifiers to each concept and term within the system. Minimally this should be a URL, but a URI or a Handle that allows for global uniqueness on when the information is put on the web is important. ( N) Doc. No.: 28 TRS SRS 0089  17 <IP_ADDRESS> The system shall have the capability to record notes concerning the use, history and provenance of the concepts, terms and relationships. ( N)

<IP_ADDRESS> The system shall be able to record the applications where a term is used. ( D)

<IP_ADDRESS> The system shall have the capability to add other metadata elements as needed. ( D)

5.4 Metadata for term sets <IP_ADDRESS> The system shall have the capability to maintain metadata for term sets. Minimally, the Dublin Core element set shall be available for describing term sets. ( N)

<IP_ADDRESS> The system shall have the capability to associate terms and definitions with specific EPA program office or system that owns the terminology. ( N)

<IP_ADDRESS> The system shall have the capability to store contact information for terminology stewards. ( N)

5.5 Development and Maintenance <IP_ADDRESS> The system shall have the capability to add information to a record over time, including new definitions, new relationships, etc. ( N)

<IP_ADDRESS> The system shall have a collaborative maintenance facility to maintain content. ( D)

<IP_ADDRESS> The system shall have the capability to control term and term set versioning. ( N)

5.6 Searching the Repository <IP_ADDRESS> The system shall have the capability to search a concept and retrieve all or part of the record for that concept including terms linked to that concept, related concepts and their relationships, etc. ( N)

<IP_ADDRESS> The system shall have the capability to perform a Boolean search and phrase searching. ( N)

<IP_ADDRESS> The system shall have the capability to perform case sensitive and case insensitive searches based on user preference at the time of the search. ( N) Doc. No.: 28 TRS SRS 0089  18 <IP_ADDRESS> The system shall have the capability to search for EPA approved terms and term sets separate from other terms and term sets. ( N)

<IP_ADDRESS> The system shall maintain records of all transactions, including searching. ( N)

<IP_ADDRESS> The system shall have the capability to recover search failures by offering partial or alternative word choices. ( N)

<IP_ADDRESS> The system shall have the capability to search on partial or truncated terms, both left and right truncation and masking of characters. ( N)

<IP_ADDRESS> The system shall have a memory capability to record each user's past sessions. ( F)

<IP_ADDRESS> The system shall have the capability to provide prompts for new session queries based on a record of the user's past sessions. ( F)

<IP_ADDRESS> The system shall have the capability to store browser navigation information. ( D)

<IP_ADDRESS> The system shall have the capability to restrict a search to a single term set selected by the user or application. ( N)

<IP_ADDRESS> The system shall have the capability to restrict a search to a group of term sets selected by the user or application. ( N)

5.7 Comparing Terms in the Repository <IP_ADDRESS> The system shall have the capability to compare and contrast terms within and across term sets. ( N)

<IP_ADDRESS> The system shall have the capability to compare and contrast definitions within and across term sets. ( N)

<IP_ADDRESS> The system shall have the capability to use meanings to compare terms and term sets. ( N)

5.8 Display and Print <IP_ADDRESS> The system shall have default displays to support the display and printing of terms and types of term sets. ( N)

<IP_ADDRESS> The system shall display terms from hierarchies in a variety of standard formats including a flat alphabetical list, a display of the term within the hierarchy, etc. ( N)

<IP_ADDRESS> The system shall display the placement of a term within an ontology. ( D)

<IP_ADDRESS> The system shall provide printer friendly formats. ( N)

<IP_ADDRESS> The system shall have the capability to hide or expose archived terms and term set versions. ( N) Doc. No.: 28 TRS SRS 0089  19 5.9 Data Exchange <IP_ADDRESS> The system shall have the capability to use well structured and documented XML for the exchange of terminology with other systems. ( N)

<IP_ADDRESS> The system shall have the capability to export and import terminologies in SKOS/ RDF as defined by the W3C Deployment and Best Practices Working Group. ( F)

<IP_ADDRESS> The system shall have the capability to extract and export a term, terms or an entire term set, along with selected fields/ relationships, such as a terms and all its synonyms, a term and its related terms, a term and its definitions, etc. ( N)

5.10 User Interface <IP_ADDRESS> The system shall allow the system administrator to customize the interface including the display fields, order of the fields and whether the field is read only. ( N)

<IP_ADDRESS> The system shall record user feedback/ comments. ( N)

<IP_ADDRESS> The system shall be 508 compliant. ( N)

<IP_ADDRESS> The system shall have the capability to support browsers back one previous version on both MACS and PCs. ( N)

<IP_ADDRESS> The system shall support internationalized or localized interfaces, for example in Spanish or Korean. ( D)

5.11 Validation and Error Prevention <IP_ADDRESS> The system shall have the capability to alert the user or administrator to the entry of duplicate information both on individual and batch loads to support proper version control. ( N)

<IP_ADDRESS> The system shall have the capability to spell check terms. ( N)

<IP_ADDRESS> The system shall have the capability to alert the user to potential format errors when adding individual terms and terms in batch. ( N)

<IP_ADDRESS> The system shall have an undo function. ( N)

5.12 Workflow Doc. No.: 28 TRS SRS 0089  20 <IP_ADDRESS> The system shall have the capability to assign roles and limit access and functionality based on those roles. One such role shall involve the stewards of the term sets. ( N)

<IP_ADDRESS> The system shall have the capability to establish a workflow for terms which includes the input of candidate terms and term sets from across the agency, a review by one or more coordinators, and " publication" of those terms via the ETS, and the ability to deprecate terms and archive them. ( N)

<IP_ADDRESS> The system shall have the capability to change archived terminology to active status. ( N) Doc. No.: 28 TRS SRS 0089  21 5.13 System Interfaces <IP_ADDRESS> The system shall have an open environment, allowing interfaces via APIs or web services to support integration with a variety of other EPA systems. ( N)

<IP_ADDRESS> The system shall have the capability to interface with other tools for building a variety of knowledge organization systems including tools for building taxonomies, pick lists, thesauri, etc. ( N)

<IP_ADDRESS> The system shall have the capability to interface with other tools for building a variety of knowledge organization systems including tools for building taxonomies, pick lists, thesauri, etc. ( N)

<IP_ADDRESS> The system shall have the capability to interface with other ontology building tools. ( D)

<IP_ADDRESS> The system shall have the capability to support the tagging of web pages from the authoritative terminology. ( N)

<IP_ADDRESS> The system shall have the capability for users to link geospatial data to nongeospatial terms for tagging and retrieval. ( D)

<IP_ADDRESS> The system shall have the capability to interface with other terminology collections inside and outside the EPA. ( D)

<IP_ADDRESS> The system shall have the capability to exchange terminology with other webbased systems. ( N)

<IP_ADDRESS> The system shall have the capability to support full text searches from EPA websites. ( N)

<IP_ADDRESS> The system shall have the capability to mine terminology from other sources. ( F)

<IP_ADDRESS> The system shall have the capability to exchange terminology from machine to machine. ( N)

<IP_ADDRESS> The system shall have the capability to export selected terminology into a desktop portlet. ( N)

<IP_ADDRESS> The system shall have the capability to exchange data with the EPA Portal tool. ( N)

<IP_ADDRESS> The system shall have the capability to exchange terminology with the EPA's Enterprise Content Management System. ( N)

<IP_ADDRESS> The system shall have the capability to interface with the taxonomy tool XML registry. ( N) Doc. No.: 28 TRS SRS 0089  22 5.14 Non Functional Requirements 5.14.1 Usability <IP_ADDRESS> The system shall have the capability to maintain an on line, context sensitive Help Feature including " Frequently Asked Questions". ( N)

5.14.2 Performance <IP_ADDRESS> The system shall respond to requests within an average of 2 to 5 seconds. ( N)

<IP_ADDRESS> The system shall have the capability to respond to a minimum of 50 identical requests simultaneously. ( N)

5.14.3 Availability <IP_ADDRESS> The system shall be operational within the EPA network and accessible from the Internet 24/ 7. ( N)

<IP_ADDRESS> The system shall have documented recovery procedures. ( N)

5.14.4 Standards The system shall consider the following standards.

o Section 508 of the Rehabilitation Act o EPA System Development and Security Standards o EPA User Interface Standards o ISO 704: 2000   Terminology work   Principles and Methods o ISO/ CD 704 [ 2005]   Terminology work   Principles and Methods o ISO 860: 1996   Terminology work   Harmonization of concepts and terms o ISO/ CD 860 [ 2005]   Terminology work   Vocabulary   Harmonization of concepts and terms o ISO1087 1: 2000   Terminology work   Vocabulary   Part 1: Theory and applications o ISO 1087 2: 2000   Terminology work   Vocabulary   Part 2: Computer applications o ISO/ DIS 1951 [ 2005]   Presentation/ representation of entries in dictionaries o ISO 2788: 1986   Documentation   Guidelines for the establishment and development of monolingual thesauri o ISO 5964: 1985 Documentation   Guidelines for the establishment and development of multilingual thesauri o ISO/ IEC 11179 3: 2003  Information technology  Data Management and Interchange  Metadata Registries ( MDR)  Part 3, Registry Meta model and Basic Attributes Doc. No.: 28 TRS SRS 0089  23 o ISO 12200: 1999  Computer applications in terminology   Machine readable terminology interchange format ( MARTIF)   Negotiated interchange o ISO 12620: 1999  Computer applications in Terminology   Data categories o ISO/ CD 12620 [ 2005]  Computer applications in Terminology   Data categories o ISO 15188: 2001   Project management guidelines for terminology standardization o ISO/ CD 16503 [ 2005]  Computer applications in terminology   Representations of terminological data   MARTIF compatible format with specified constraints ( MSC)

o ISO 16642: 2003   Computer applications in terminology   Terminological markup framework o ISO/ WD 24156 [ 2005]   Guidelines for applying concept modeling in terminology work o ANSI/ NISO Z39.19   2003  Guidelines for the Construction, Format, and Management of Monolingual Thesauri Doc. No.: 28 TRS SRS 0089  24 5.14.5 Security <IP_ADDRESS> The system shall be in compliance with all National Computing Center ( NCC) security directives, Technology Information Security Staff ( TISS) policies, procedures and directives and with National Institute for Standards and Technology ( NIST) security guidance. ( N)

<IP_ADDRESS> The system shall have the capability to set different access levels for users. ( N)

<IP_ADDRESS> The system shall require a log on for users who are maintaining content, but not for agency or public users who are only searching and viewing the content. ( N)

5.15 Support Requirements 5.15.1 Training <IP_ADDRESS> The system shall include an on line user's guide. ( N)

<IP_ADDRESS> The system shall include an on line tutorial. ( N)

5.15.2 Documentation <IP_ADDRESS> The system shall have a documented procedure for updates, maintenance migration, and documented methods for applying user customization when upgrades and patches are applied. ( N)

<IP_ADDRESS> The system shall be documented as if the development environment is certified at and operating at the Software Engineering Institute ( SEI) Capability Maturity Model for Software ( CMM) Level 3   " The Defined Level." ( D)

5.15.3 System Acceptance/ Testing <IP_ADDRESS> The system shall be usability tested according to standard Office of Environmental Information ( OEI) protocols. ( N)

5.15.4 Change Control <IP_ADDRESS> The system shall have a formal change control process that will be tested and delivered when the system is operational. ( N) Doc. No.: 28 TRS SRS 0089  25


[Federal Register Volume 88, Number 166 (Tuesday, August 29, 2023)]
[Proposed Rules]
[Pages 59476-59480]
[FR Doc No: 2023-18567]

-----------------------------------------------------------------------

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 39

[Docket No. FAA-2023-1721; Project Identifier MCAI-2023-00676-T]
RIN 2120-AA64

Airworthiness Directives; Dassault Aviation Airplanes

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Notice of proposed rulemaking (NPRM).

-----------------------------------------------------------------------

SUMMARY: The FAA proposes to supersede Airworthiness Directive (AD)
2023-04-13, which applies to certain Dassault Aviation Model FALCON
2000EX airplanes. AD 2023-04-13 requires revising the existing
maintenance or inspection program, as applicable, to incorporate new or
more restrictive airworthiness limitations. Since the FAA issued AD
2023-04-13, the FAA has determined that new or more restrictive
airworthiness limitations are necessary. This proposed AD would
continue to require the actions in AD 2023-04-13 and would require
revising the existing maintenance or inspection program, as applicable,
to incorporate new or more restrictive airworthiness limitations, as
specified in a European Union Aviation Safety Agency (EASA) AD, which
is proposed for incorporation by reference (IBR). The FAA is proposing
this AD to address the unsafe condition on these products.

DATES: The FAA must receive comments on this proposed AD by October 13,
2023.

ADDRESSES: You may send comments, using the procedures found in 14 CFR
11.43 and 11.45, by any of the following methods:
     Federal eRulemaking Portal: Go to regulations.gov. Follow
the instructions for submitting comments.
     Fax:<PHONE_NUMBER>.
     Mail: U.S. Department of Transportation, Docket
Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New
Jersey Avenue SE, Washington, DC 20590.
     Hand Delivery: Deliver to Mail address above between 9
a.m. and 5 p.m., Monday through Friday, except Federal holidays.
    AD Docket: You may examine the AD docket at regulations.gov under
Docket No. FAA-2023-1721; or in person at Docket Operations between 9
a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD
docket

contains this NPRM, the mandatory continuing airworthiness information
(MCAI), any comments received, and other information. The street
address for Docket Operations is listed above.
    Material Incorporated by Reference:
     For material that is proposed for IBR in this NPRM,
contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; telephone
+49 221 8999 000; email: [email protected]; website: easa.europa.eu.
You may find this material on the EASA website: ad.easa.europa.eu. It
is also available at regulations.gov under Docket No. FAA-2023-1721.
     You may view this service information at the FAA,
Airworthiness Products Section, Operational Safety Branch, 2200 South
216th Street, Des Moines, WA. For information on the availability of
this material at the FAA, call<PHONE_NUMBER>.

FOR FURTHER INFORMATION CONTACT: Tom Rodriguez, Aviation Safety
Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590;
telephone<PHONE_NUMBER>; email [email protected].

SUPPLEMENTARY INFORMATION:

Comments Invited

    The FAA invites you to send any written relevant data, views, or
arguments about this proposal. Send your comments to an address listed
under ADDRESSES. Include ``Docket No. FAA-2023-1721; Project Identifier
MCAI-2023-00676-T'' at the beginning of your comments. The most helpful
comments reference a specific portion of the proposal, explain the
reason for any recommended change, and include supporting data. The FAA
will consider all comments received by the closing date and may amend
this proposal because of those comments.
    Except for Confidential Business Information (CBI) as described in
the following paragraph, and other information as described in 14 CFR
11.35, the FAA will post all comments received, without change, to
regulations.gov, including any personal information you provide. The
agency will also post a report summarizing each substantive verbal
contact received about this NPRM.

Confidential Business Information

    CBI is commercial or financial information that is both customarily
and actually treated as private by its owner. Under the Freedom of
Information Act (FOIA) (5 U.S.C. 552), CBI is exempt from public
disclosure. If your comments responsive to this NPRM contain commercial
or financial information that is customarily treated as private, that
you actually treat as private, and that is relevant or responsive to
this NPRM, it is important that you clearly designate the submitted
comments as CBI. Please mark each page of your submission containing
CBI as ``PROPIN.'' The FAA will treat such marked submissions as
confidential under the FOIA, and they will not be placed in the public
docket of this NPRM. Submissions containing CBI should be sent to Tom
Rodriguez, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite
410, Westbury, NY 11590; telephone<PHONE_NUMBER>; email
[email protected]. Any commentary that the FAA receives that is not
specifically designated as CBI will be placed in the public docket for
this rulemaking.

Background

    The FAA issued AD 2023-04-13, Amendment 39-22360 (88 FR 20741,
April 7, 2023) (AD 2023-04-13), for certain Dassault Aviation Model
FALCON 2000EX airplanes. AD 2023-04-13 was prompted by an MCAI
originated by EASA, which is the Technical Agent for the Member States
of the European Union. EASA issued AD 2022-0136, dated July 6, 2022
(EASA 2022-0136) (which corresponds to FAA AD 2023-04-13), to correct
an unsafe condition.
    AD 2023-04-13 requires revising the existing maintenance or
inspection program, as applicable, to incorporate new or more
restrictive airworthiness limitations. The FAA issued AD 2023-04-13 to
address reduced structural integrity of the airplane. AD 2023-04-13
specifies that accomplishing the revision required by paragraph (g) or
(j) of that AD terminates the requirements of paragraph (g)(1) of AD
2010-26-05, Amendment 39-16544 (75 FR 79952, December 21, 2010), for
Dassault Aviation Model FALCON 2000EX airplanes. This proposed AD
would, therefore, continue to allow that terminating action.

Actions Since AD 2023-04-13 Was Issued

    Since the FAA issued AD 2023-04-13, EASA superseded AD 2022-0136
and issued EASA AD 2023-0100, dated May 11, 2023 (EASA AD 2023-0100)
(also referred to after this as the MCAI), for all Dassault Aviation
Model FALCON 2000EX airplanes. The MCAI states that new or more
restrictive airworthiness limitations have been developed.
    Airplanes with an original airworthiness certificate or original
export certificate of airworthiness issued after January 15, 2023, must
comply with the airworthiness limitations specified as part of the
approved type design and referenced on the type certificate data sheet
for those airplanes; this AD therefore does not include these airplanes
in the applicability.
    The FAA is proposing this AD to address reduced structural
integrity of the airplane. You may examine the MCAI in the AD docket at
regulations.gov under Docket No. FAA-2023-1721.

Related Service Information Under 1 CFR Part 51

    The FAA reviewed EASA AD 2023-0100. This service information
specifies new or more restrictive airworthiness limitations for
airplane structures and safe life limits.
    This proposed AD would also require EASA AD 2022-0136, which the
Director of the Federal Register approved for incorporation by
reference as of May 12, 2023 (88 FR 20741, April 7, 2023).
    This material is reasonably available because the interested
parties have access to it through their normal course of business or by
the means identified in ADDRESSES section.

FAA's Determination

    This product has been approved by the aviation authority of another
country and is approved for operation in the United States. Pursuant to
the FAA's bilateral agreement with the State of Design Authority, it
has notified the FAA of the unsafe condition described in the MCAI
described above. The FAA is issuing this NPRM after determining that
the unsafe condition described previously is likely to exist or develop
in other products of the same type design.

Proposed AD Requirements in This NPRM

    This proposed AD would retain the requirements of AD 2023-04-13.
This proposed AD would also require revising the existing maintenance
or inspection program, as applicable, to incorporate additional new or
more restrictive airworthiness limitations, which are specified in EASA
AD 2023-0100 already described, as proposed for incorporation by
reference. Any differences with EASA AD 2023-0100 are identified as
exceptions in the regulatory text of this AD.
    This proposed AD would require revisions to certain operator
maintenance documents to include new actions (e.g., inspections).
Compliance with these actions is required by 14 CFR

91.403(c). For airplanes that have been previously modified, altered,
or repaired in the areas addressed by this proposed AD, the operator
may not be able to accomplish the actions described in the revisions.
In this situation, to comply with 14 CFR 91.403(c), the operator must
request approval for an alternative method of compliance (AMOC)
according to paragraph (n)(1) of this proposed AD.

Explanation of Required Compliance Information

    In the FAA's ongoing efforts to improve the efficiency of the AD
process, the FAA developed a process to use some civil aviation
authority (CAA) ADs as the primary source of information for compliance
with requirements for corresponding FAA ADs. The FAA has been
coordinating this process with manufacturers and CAAs. As a result, the
FAA proposes to retain the IBR of EASA AD 2022-0136 and incorporate
EASA AD 2023-0100 by reference in the FAA final rule. This proposed AD
would, therefore, require compliance with EASA AD 2023-0100 and EASA AD
2022-0136 through that incorporation, except for any differences
identified as exceptions in the regulatory text of this proposed AD.
Using common terms that are the same as the heading of a particular
section in EASA AD 2022-0136 or EASA AD 2023-0100 does not mean that
operators need comply only with that section. For example, where the AD
requirement refers to ``all required actions and compliance times,''
compliance with this AD requirement is not limited to the section
titled ``Required Action(s) and Compliance Time(s)'' in EASA AD 2022-
0136 or EASA AD 2023-0100. Service information required by EASA AD
2022-0136 and EASA AD 2023-0100 for compliance will be available at
regulations.gov by searching for and locating Docket No. FAA-2023-1721
after the FAA final rule is published.

Airworthiness Limitation ADs Using the New Process

    The FAA's process of incorporating by reference MCAI ADs as the
primary source of information for compliance with corresponding FAA ADs
has been limited to certain MCAI ADs (primarily those with service
bulletins as the primary source of information for accomplishing the
actions required by the FAA AD). However, the FAA is now expanding the
process to include MCAI ADs that require a change to airworthiness
limitation documents, such as airworthiness limitation sections.
    For these ADs that incorporate by reference an MCAI AD that changes
airworthiness limitations, the FAA requirements are unchanged.
Operators must revise the existing maintenance or inspection program,
as applicable, to incorporate the information specified in the new
airworthiness limitation document. The airworthiness limitations must
be followed according to 14 CFR 91.403(c) and 91.409(e).
    The previous format of the airworthiness limitation ADs included a
paragraph that specified that no alternative actions (e.g.,
inspections) or intervals may be used unless the actions and intervals
are approved as an AMOC in accordance with the procedures specified in
the AMOCs paragraph under ``Additional AD Provisions.'' This new format
includes a ``New Provisions for Alternative Actions and Intervals''
paragraph that does not specifically refer to AMOCs, but operators may
still request an AMOC to use an alternative action or interval.

Costs of Compliance

    The FAA estimates that this proposed AD affects 245 airplanes of
U.S. registry. The FAA estimates the following costs to comply with
this proposed AD:
    The FAA estimates the total cost per operator for the retained
actions from AD 2023-04-13 to be $7,650 (90 work-hours x $85 per work-
hour).
    The FAA has determined that revising the existing maintenance or
inspection program takes an average of 90 work-hours per operator,
although the agency recognizes that this number may vary from operator
to operator. In the past, the agency has estimated that this action
takes 1 work-hour per airplane. Since operators incorporate maintenance
or inspection program changes for their affected fleet(s), the FAA has
determined that a per-operator estimate is more accurate than a per-
airplane estimate.
    The FAA estimates the total cost per operator for the new proposed
actions to be $7,650 (90 work-hours x $85 per work-hour).

Authority for This Rulemaking

    Title 49 of the United States Code specifies the FAA's authority to
issue rules on aviation safety. Subtitle I, section 106, describes the
authority of the FAA Administrator. Subtitle VII: Aviation Programs,
describes in more detail the scope of the Agency's authority.
    The FAA is issuing this rulemaking under the authority described in
Subtitle VII, Part A, Subpart III, Section 44701: General requirements.
Under that section, Congress charges the FAA with promoting safe flight
of civil aircraft in air commerce by prescribing regulations for
practices, methods, and procedures the Administrator finds necessary
for safety in air commerce. This regulation is within the scope of that
authority because it addresses an unsafe condition that is likely to
exist or develop on products identified in this rulemaking action.

Regulatory Findings

    The FAA determined that this proposed AD would not have federalism
implications under Executive Order 13132. This proposed AD would not
have a substantial direct effect on the States, on the relationship
between the national Government and the States, or on the distribution
of power and responsibilities among the various levels of government.
    For the reasons discussed above, I certify this proposed
regulation:
    (1) Is not a ``significant regulatory action'' under Executive
Order 12866,
    (2) Would not affect intrastate aviation in Alaska, and
    (3) Would not have a significant economic impact, positive or
negative, on a substantial number of small entities under the criteria
of the Regulatory Flexibility Act.

List of Subjects in 14 CFR Part 39

    Air transportation, Aircraft, Aviation safety, Incorporation by
reference, Safety.

The Proposed Amendment

    Accordingly, under the authority delegated to me by the
Administrator, the FAA proposes to amend 14 CFR part 39 as follows:

PART 39--AIRWORTHINESS DIRECTIVES

0
1. The authority citation for part 39 continues to read as follows:

    Authority:  49 U.S.C. 106(g), 40113, 44701.

Sec.  39.13  [Amended]

0
2. The FAA amends Sec.  39.13 by:
0
a. Removing Airworthiness Directive 2023-04-13, Amendment 39-22360 (88
FR 20741, April 7, 2023); and
0
b. Adding the following new Airworthiness Directive:

Dassault Aviation: Docket No. FAA-2023-1721; Project Identifier
MCAI-2023-00676-T.

(a) Comments Due Date

    The FAA must receive comments on this airworthiness directive
(AD) by October 13, 2023.

(b) Affected ADs

    (1) This AD replaces AD 2023-04-13, Amendment 39-22360 (88 FR
20741, April 7, 2023) (AD 2023-04-13).
    (2) This AD affects AD 2010-26-05, Amendment 39-16544 (75 FR
79952, December 21, 2010) (AD 2010-26-05).

(c) Applicability

    This AD applies to Dassault Aviation Model FALCON 2000EX
airplanes, certificated in any category, with an original
airworthiness certificate or original export certificate of
airworthiness issued on or before January 15, 2023.

(d) Subject

    Air Transport Association (ATA) of America Code: 05, Time
Limits/Maintenance Checks.

(e) Unsafe Condition

    This AD was prompted by a determination that new or more
restrictive airworthiness limitations are necessary. The FAA is
issuing this AD to address reduced structural integrity of the
airplane.

(f) Compliance

    Comply with this AD within the compliance times specified,
unless already done.

(g) Retained Maintenance or Inspection Program Revision, With No
Changes

    This paragraph restates the requirements of paragraph (j) of AD
2023-04-13, with no changes. For airplanes with an original
airworthiness certificate or original export certificate of
airworthiness issued on or before January 15, 2022, except as
specified in paragraph (h) of this AD: Comply with all required
actions and compliance times specified in, and in accordance with,
European Union Aviation Safety Agency (EASA) AD 2022-0136, dated
July 6, 2022 (EASA AD 2022-0136). Accomplishing the revision of the
existing maintenance or inspection program required by paragraph (j)
of this AD terminates the requirements of this paragraph.

(h) Retained Exceptions to EASA AD 2022-0136, With No Changes

    This paragraph restates the exceptions specified in paragraph
(k) of AD 2023-04-13, with no changes.
    (1) The requirements specified in paragraphs (1) and (2) of EASA
AD 2022-0136 do not apply to this AD.
    (2) Paragraph (3) of EASA AD 2022-0136 specifies revising ``the
approved AMP'' within 12 months after its effective date, but this
AD requires revising the existing maintenance or inspection program,
as applicable within 90 days after May 12, 2023 (the effective date
of AD 2023-04-13).
    (3) The initial compliance time for doing the tasks specified in
paragraph (3) of EASA AD 2022-0136 is at the applicable
``limitation'' and ``associated thresholds'' as incorporated by the
requirements of paragraph (3) of EASA AD 2022-0136, or within 90
days after the May 12, 2023 (the effective date of AD 2023-04-13),
whichever occurs later.
    (4) The provisions specified in paragraphs (4) and (5) of EASA
AD 2022-0136 do not apply to this AD.
    (5) The ``Remarks'' section of EASA AD 2022-0136 does not apply
to this AD.

(i) Retained Provisions for Alternative Actions or Intervals, With a
New Exception

    This paragraph restates the requirements of paragraph (l) of AD
2023-04-13, with a new exception. Except as required by paragraph
(j) of this AD, after the existing maintenance or inspection program
has been revised as required by paragraph (g) of this AD, no
alternative actions (e.g., inspections) or intervals may be used
unless they are approved as specified in the provisions of the
``Ref. Publications'' section of EASA AD 2022-0136.

(j) New Maintenance or Inspection Program Revision

    Except as specified in paragraph (k) of this AD: Comply with all
required actions and compliance times specified in, and in
accordance with, EASA AD 2023-0100, dated May 11, 2023 (EASA AD
2023-0100). Accomplishing the revision of the existing maintenance
or inspection program required by this paragraph terminates the
requirements of paragraph (g) of this AD.

(k) Exceptions to EASA AD 2023-0100

    (1) This AD does not adopt the requirements specified in
paragraphs (1) and (2) of EASA AD 2023-0100.
    (2) Paragraph (3) of EASA AD 2023-0100 specifies revising ``the
approved AMP'' within 12 months after its effective date, but this
AD requires revising the existing maintenance or inspection program,
as applicable, within 90 days after the effective date of this AD.
    (3) The initial compliance time for doing the tasks specified in
paragraph (3) of EASA AD 2023-0100 is at the applicable
``limitations'' and ``associated thresholds'' as incorporated by the
requirements of paragraph (3) of EASA AD 2023-0100, or within 90
days after the effective date of this AD, whichever occurs later.
    (4) This AD does not adopt the provisions specified in
paragraphs (4) and (5) of EASA AD 2023-0100.
    (5) This AD does not adopt the ``Remarks'' section of EASA AD
2023-0100.

(l) New Provisions for Alternative Actions and Intervals

    After the maintenance or inspection program has been revised as
required by paragraph (j) of this AD, no alternative actions (e.g.,
inspections), and intervals are allowed unless they are approved as
specified in the provisions of the ``Ref. Publications'' section of
EASA AD 2023-0100.

(m) Terminating Action for Certain Actions in AD 2010-26-05

    Accomplishing the actions required by paragraph (g) or (j) of
this AD terminates the requirements of paragraph (g)(1) of AD 2010-
26-05, for Dassault Aviation Model FALCON 2000EX airplanes only.

(n) Additional AD Provisions

    The following provisions also apply to this AD:
    (1) Alternative Methods of Compliance (AMOCs): The Manager,
International Validation Branch, FAA, has the authority to approve
AMOCs for this AD, if requested using the procedures found in 14 CFR
39.19. In accordance with 14 CFR 39.19, send your request to your
principal inspector or responsible Flight Standards Office, as
appropriate. If sending information directly to the International
Validation Branch, send it to the attention of the person identified
in paragraph (o) of this AD. Information may be emailed to: [email protected]. Before using any approved AMOC, notify your
appropriate principal inspector, or lacking a principal inspector,
the manager of the responsible Flight Standards Office.
    (2) Contacting the Manufacturer: For any requirement in this AD
to obtain instructions from a manufacturer, the instructions must be
accomplished using a method approved by the Manager, International
Validation Branch, FAA; or EASA; or Dassault Aviation's EASA Design
Organization Approval (DOA). If approved by the DOA, the approval
must include the DOA-authorized signature.

(o) Additional Information

    For more information about this AD, contact Tom Rodriguez,
Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410,
Westbury, NY 11590; telephone<PHONE_NUMBER>; email
[email protected].

(p) Material Incorporated by Reference

    (1) The Director of the Federal Register approved the
incorporation by reference (IBR) of the service information listed
in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.
    (2) You must use this service information as applicable to do
the actions required by this AD, unless this AD specifies otherwise.
    (3) The following service information was approved for IBR on
[DATE 35 DAYS AFTER PUBLICATION OF THE FINAL RULE].
    (i) European Union Aviation Safety Agency (EASA) AD 2023-0100,
dated May 11, 2023.
    (ii) [Reserved]
    (4) The following service information was approved for IBR on
May 12, 2023 (88 FR 20741, April 7, 2023).
    (i) European Union Aviation Safety Agency (EASA) AD 2022-0136,
dated July 6, 2022.
    (ii) [Reserved]
    (5) For EASA ADs 2022-0136 and 2023-0100, contact EASA, Konrad-
Adenauer-Ufer 3, 50668 Cologne, Germany; telephone +49 221 8999 000;
email: [email protected]; website: easa.europa.eu. You may find
these EASA ADs on the EASA website: ad.easa.europa.eu.
    (6) You may view this service information at the FAA,
Airworthiness Products Section, Operational Safety Branch, 2200
South 216th Street, Des Moines, WA. For information on the
availability of this material at the FAA, call<PHONE_NUMBER>.
    (7) You may view this service information that is incorporated
by reference at the National Archives and Records Administration
(NARA). For information on

the availability of this material at NARA, email
[email protected], or go to: www.archives.gov/federal-register/cfr/ibr-locations.html.

    Issued on August 23, 2023.
Victor Wicklund,
Deputy Director, Compliance & Airworthiness Division, Aircraft
Certification Service.
[FR Doc. 2023-18567 Filed 8-28-23; 8:45 am]
BILLING CODE 4910-13-P