Federal Aviation Administration
Office of the Assistant Administrator for Information Services
and Chief Information Officer
Office of the Chief Technology Officer (CTO)
Enterprise Architecture Program
Task Order #1- Enterprise Architecture
Advanced Concepts Exploration and Planning (ACEP)
Task Order #1
Office of the Assistant Administrator for Information Services and Chief Information Officer Formatted: Left
Office of the Chief Technology Officer (CTO) Formatted: Font: 10 pt, Not Bold
Enterprise Architecture Program
FOB 10-B Formatted: Font: 10 pt, Not Bold
800 Independence Avenue, SW Formatted: Font: 10 pt, Not Bold
ARD-1 Formatted: Justified, Indent: Left: 0"
Washington, DC 20591
The Office of the Chief Technology Officer (CTO) conducts information technology and information security Formatted: Font: (Default) Arial
related Research and Development (R&D), enhances and maintains the Enterprise Architecture (EA) for the non- Formatted: Indent: Left: 0"
real-time information technology (IT) systems within the Federal Aviation Administration (FAA), and works to
improve the processes used by the FAA to conduct its mission. This office will require support in program Formatted: Font: (Default) Arial
management and planning, enterprise architecture, process engineering, security engineering and research and
development activities to conduct the tasks described in this Statement of Work for the Advanced Concepts
Exploration and Planning (ACEP) program. This Task Order #1 under the ACEP contract s that the CTO’s Office Formatted: Font: (Default) Arial
has the resources necessary to support the Enterprise Architecture program.
The Office of the Chief Technology Officer or ARD-1 was established in 2005 with the objective of providing
cross-divisional technical resources to the Office of the Chief Information Officer (CIO) and to the FAA. Its
mission is to improve the FAA’s capability to perform its mission by identifying and recommending secure, robust,
technologies, and other solutions, and best practices in response to the user community. ARD-1’s mission is
complex, but its strategy is straightforward:
Provide leadership in introducing new technologies and ideas throughout the FAA
Experiment with technology in operational settings, rolling out effective new technology
Engage with other agencies and organizations in pursuing common solutions to government problems
Engage with industry assisting them to identify and champion products and technologies that satisfy
FAA’s emerging requirements
Achieve an adaptive culture and organization internally, while reinforcing positive shifts within the
Enhance customer focus and support
Focus on enterprise-wide solutions
Stay focused on AIO’s core missions and competencies
Acquire, develop, and keep talent – first-rate people make first-rate things happen
ARD-1 has established a 500-day plan to describe the activities its staff plans to perform over the next 500 days.
The Office of the CTO lies with the Office of the Assistant Administrator for Information Services and Chief
Information Officer (AIO). In addition to enterprise architecture, AIO provides these primary services:
Serves as the principal advisor to the Administrator, Deputy Administrator, and FAA offices on
information management and technology across the agency. As the agency's senior
management official, serves as the spokesperson on information technology matters before
Congress, other agencies, and the public.
Leads and directs agency-wide strategic planning for information technology.
Oversees Information Technology (IT) investments to ensure optimization across all agency
groups and the full range of cost tradeoffs.
Creates and maintains an IT strategy to guide research, development, maintenance, and
sharing of information systems, applications, data, and other resources across the lines of
business and throughout the agency.
Leads the establishment of world-class software and information systems engineering
methodologies, including Capability Maturity Models (CMM), and applies them to agency
systems, operations, and processes to provide continuous improvement of IT performance.
Leads and directs agency-wide efforts on information systems security, ensuring that standards
and policies are in place to provide security for the critical information architecture of the
Indefinite Delivery-Indefinite Quantities
This Enterprise Architecture SOW places a task order against the Delivery Order No. __________ IDIQ
contract entitled “Advanced Concepts Exploration and Planning” awarded on date______________. The
anticipated period of performance will include one base year and 4 option years.
This Statement of Work (SOW) describes the effort required for ongoing support and further development of
the FAA Enterprise Architecture (EA). The FAA Flight Plan provides the strategic direction for the FAA and
lists the initiatives and measures that determine FAA performance success. The Flight Plan contains the
following 2007 EA initiative: “All major NAS* and non-NAS IT investments are formally evaluated for
compliance with the FAA EA standards.” Inclusion in the Flight Plan indicates FAA agency commitment to EA
as a strategic initiative. In addition, the FAA’s Information Technology Planning Team has identified the EA
effort as having potential for targeted benefits for the agency.
The FAA conducts EA initiatives in order to better plan, develop, and manage its administrative information
systems and information technology infrastructure. A key aim is to attain improved administrative systems
capabilities through increased interoperability across systems, more directed targeting of IT resources for
enhancing administrative systems, enterprise-wide configuration management, and data
sharing/standardization. There is a need for information to interoperate between administrative systems such
as financial, human resource, and other systems both for enterprise-wide functions as well as in support of
lines of business (LOBs) specific functions. The latter entails the ability to move information from LOBs to
enterprise level functions and back to the LOBs.
The current FAA EA is composed of two segments, the National Airspace System (NAS) Operations
Architecture and the NAS Support Architecture that is represented by the EA Repository. As mandated by the
Clinger-Cohen Act, the CIO has responsibility for formulating and maintaining the overall EA. The Chief
Operating Officer of the Air Traffic Organization (ATO) is delegated responsibility to develop and implement
the NAS Operations Architecture.
The NAS architecture is accessible to the public and can be reviewed at http://www.nas-architecture.faa.gov.
FAA intranet access to the EA Repository is available through the Department of Transportation (DOT)
architecture portal found at http://ea.faa.gov. Further information about the NAS and NAS Support
architectures is found in Section 2.1 of this SOW. Further information about the EA Repository will be
provided through the FAA contracting officer upon request.
The FAA EA Repository was originally developed using the Federal Enterprise Architecture Framework
(FEAF). The FAA EA V1.1 that was published in September, 2002, provided a baseline as-is and draft to-be
FAA architecture that integrated the existing FAA data architecture. The FAA EA Version 2.0 was published in
September 2003 and contained baseline to-be administrative and mission support architectural information
that integrated the existing Information Systems Security (ISS) architecture to support the requirement that the
EA contain the information necessary to address security needs. Recent EA work has emphasized
collaboration with FAA business units to provide the support necessary to complete the FAA administrative
segment to by working with the FAA LOBs to complete individual business unit architectures and integrate the
information into the FAA EA Repository. The current version of the FAA EA Repository employs the
categorization framework provided by the Federal Enterprise Architecture (FEA). The FEA can be viewed at
http://www.whitehouse.gov/omb/egov/a-1-fea.html. The FAA EA now contains strategy, business process,
organizational, data, applications, and technology information and contains mappings to the FEA Business
Reference Model (BRM), FEA Service Component Reference Model (SRM), and FEA Technology Reference
Model (TRM). The FAA also contains extensive data information (application entity types and data models)
that can be leveraged to facilitate data sharing and/or exchange as intended by the FEA Data Reference
Model (DRM) strategy and newly formed communities of practice.
2. Project Background and Objectives
In the FAA today, there is agreement that the quality, availability, functionality, architecture, interoperability,
and security of current and planned IT systems could be improved to better meet the agency’s business
needs. For example, today FAA LOB’s may independently acquire administrative systems creating
interoperability problems, as well as gaps and overlaps in functionality. Ensuring data quality, accessibility,
availability, and security among independent systems is difficult. Return on investment may be reduced
accordingly. In the past, deployment of enterprise-wide systems has been severely hampered by the lack of
an enterprise-wide view of these systems. Deployment of enterprise-wide decision support systems is
severely hampered by the lack of an enterprise-wide view of these systems. The EA will provide a road map
for how to improve upon the interoperability, integration, and security for administrative systems. This road
map will prove invaluable as FAA IT governance matures to effectively support agency-wide IT portfolio
management throughout the investment life cycle.
A stated goal of the FAA EA practice is to serve as a best practice example to the rest of the agency through
early adoption of a robust SDLC methodology. Many LOB system development programs have their own
configuration control processes. Those processes are expected to continue. Any enterprise level
configuration control needs to be done in coordination with system-by-system configuration control to ensure
that any enterprise-wide effort complements existing legacy CM systems and processes and utilizes best
practice systems development life cycle (SDLC) methodologies.
Today, the FAA manages enormous quantities of information ranging from payroll to aircraft inspection records
to current aircraft position. Although FISMA reporting is now handled separately, the status of key NAS
support application security certification and accreditation milestones is currently reflected in the security
information recorded about each item in the EA Repository. Yet, that information is not identified in such a
way that managing it to those different requirements is easily accomplished.
FAA currently categorizes all information into separate domains, and subsequently manages that information
consistent with the unique characteristics of that domain. These two domains are:
1. National Airspace System (NAS) Operations – Time-sensitive safety critical information used to
provide safe separation of aircraft; e.g., the position of aircraft in the sky and communications between
pilots and controllers.
2. National Airspace System (NAS) Support - Relatively static information used to support NAS
Operations or provide other FAA unique services; e.g., the condition and position of navigational aides
and copies of aircraft inspection reports. In addition this includes administrative information such as
that needed to perform the general business functions of the FAA such as acquisition, payroll, human
resources, and accounting.
Formatted: Bullets and Numbering
The FAA NAS support enterprise architecture currently emphasizes the Federal Enterprise Architecture
Framework (FEAF) that was developed by the Federal CIO Council to coordinate and standardize enterprise
architecture efforts across the Federal Government. The FEAF provides a guideline and model for
communicating enterprise architectures through organizational entities, architectural components, and their
relationships. To increase consistency with the NAS Operations architecture and enhance the utility of the
NAS support EA information, the FAA NAS support architecture began adding selected DOD Architectural
Framework (DODAF) views of new investments during FY 2007.
This project will be led by AIO with full participation by LOB and staff office representatives through available
FAA boards, working groups, and regularly held technical exchange meetings. EA Task Order expected
targeted benefits are:
Ready availability of reliable EA information
Establishment of FAA EA standards
Provide for the continuing maintenance of the FAA EA and for future development of all EA
Support the formal evaluation of all major NAS and non-NAS (e.g. NAS support) investments for
compliance with the FAA EA standards
Reduce the cost of delivering IT services without reducing quality
Establish a clearly articulated EA strategy that is reflected in the agency IT strategy and governance
Provide the EA information necessary to optimize IT decisions and resources across the agency
Exploit technology opportunities
Solve targeted critical business problems arising from inadequate administrative systems
interoperability and capabilities
Reduce redundancy and overlap of applications and systems
Serve as an agency example of effective application of a SDLC methodology
Associate measures with architectural goals
Provide for independent validation and verification of the FAA EA
Increase system integration and interoperability
Increase correlation to business processes
Optimize data collection and management
Guide, promote, and coordinate IT investment in NAS support systems
Leverage economies of scale to increase return on investment
Increase flexibility to adopt new technologies
Support for further integration of EA into FAA SDLC’s and the budget formulation and execution
Support for data calls (DOT, OMB, GAO, etc) as requested
Support for modernization planning (Agency-wide or Line of Business specific)
Support for all activities related to Service Oriented Architectures and/or component architectures
Comply with the Clinger-Cohen Act and Office of Management and Budget (OMB) Circular A-130
3. Technical Services Required
3.1. Task Description
The Contractor shall develop the EA for the FAA that is consistent with the Clinger-Cohen Act, OMB Circular
A-130, and the FEAF as well as selected DODAF views. The contractor shall employ best practices placing all
project artifacts under configuration management and shall employ an agreed-upon SDLC process. In
addition the EA shall be developed with the targeted benefits identified above. These benefits shall be derived
from the work and deliverables specified in the sections that follow.
3.2. Scope of Work
The scope of the enterprise architecture developed under this SOW will be limited to the NAS support systems
information domain described above.
3.3. Statement of Work
The following tasks are the expected areas of work required to complete the objectives of this statement of
Formatted: Font: Bold
3.3.1 Required Tasks Formatted: Bullets and Numbering
Formatted: Indent: Left: 0.38"
The contractor is required to complete the following tasks:
For each task, the Contractor shall:
Task 1 Program Management
The contractor shall Develop develop & maintain Program/Project Plans for each task to support the
planning and monitoring of activities. Communicate status to the FAA that includes progress, updates
and revisions to the key activities, milestones, deliverables, risks and issues. Provide quality assurance
to all deliverables.
This task requires contractor to provide systems and business analysis services to FAA ATO Acquisition
and Business Services Information Technology Directorate in conjunction with the continued
development, enhancement and maintenance of an enterprise architecture (EA). Provide technical
support services for the EA ranging from analysing various components of EA, efficacy of future IT
purchases, developing project plans to develop the As Is and To Be model of EA. The contractor shall
develop the FAA EA developed shall beto be consistent with direction from the Office of Management and
Budget, the FAA AIO and other EA efforts within US DOT.
Task 2 Non-NAS Shared Infrastructure Development
Many of the non-NAS systems reside on common hosting and connectivity infrastructure. This The task
contractor shall provide will include modelingmodels of the non-NAS shared computing environment such
as Wide Area Networks (WANs), Metropolitan Area Networks (MANs), Local Area Networks (LANs),
Internet access points (IAPs), hosting centers, etc. that support the applications identified in the FAA non-
NAS application architecture. This task includes As-Is, Transitional, and To-Be states as well as projects
for migration. The outcome of this task will be the addition of shared infrastructure to the EA baseline.
Task 3 EA Content Reviews and Data Update (EA Maintenance)
The contractor shall Rreview of all elements of the existing FAA EA process areas/segments including
Business Reference Model (BRM), Data Reference Model (DRM), Service Reference Model (SRM),
Technical Reference Model (TRM), Shared Infrastructure, Migration Plan, and projects. The contractor
shall Update update of old or incorrect elements of the existing EA as identified by this the contractor’s
review. The contractor shall Update update the EA Repository and EA content to reflect changes to
OMB’s FEA reference models. including the addition of newer reference model information such as the
Performance Referance Model (PRM). The outcome deliverable of this task will be an updated EA
repository. The contractor shall provide monthly updates of incoming new investment and other EA
content information. The contractor shall that is constantly constantly maintained.maintain the EA
Repository providing at least monthly updates.
The contractor shall review the status of the ATO EA activities conducted to date and provide an analysis
and recommendation for enhancing the products in light of the need to create repeatable and auditable
EA products and processes. The review shall include an assessment of the maturity of the ATO EA using
the Enterprise Architecture Capability Maturity Model checklist.
Task 4 EA Baseline Transfer
The objective is tocontractor shall identify technology dependencies in support of requirements of LOB
business activities and provide current infrastructure baseline data for the FAA’s Target Architecture
Insofar as possible, provide supplemental support to the ATO Service Area Consolidation by sharing
analysis and data modeling information.
The contractor shall Provide provide analysis and data modeling services that supplement development
of the FAA NAS Support Target Architecture, by reviewing the current infrastructure baseline (“As Is”) and
determining an evolution strategy that will meet the technology support requirements of the FAA business
activities. Legacy systems/obsolete technologies should also be identified. Gap Analysis, data modeling,
and related activities will identify technology dependencies associated with achieving the Target
The contractor shall pProvide analysis and data modeling services, to include but not limited to the
supporting the transfer control of the EA content to the Lines of Business (LOBs). This includes
identification and training of EA Content Administrators, user guide and online help, data dictionary, and
support of the deployed data collection tool. An additional outcome of this task will be to enable LOBs to
control their content published in the DOT EA Repository.
Task 5 EA Governance
Provide documentation of processes and recommended organizations for the management, validation
and update of EA information consistent with General Accounting Office’s Enterprise Architecture
Management Maturity Framework (EAMMP) and how EA will support the Information Technology
executive Board (ITEB). The outcome of this task will be a functioning set of governance bodies and
The contractor shall develop effective EA communication mechanisms for the FAA, utilizing the future
Architecture Review Board (ARB), CCB and other such steering groups which could play significant role
in the overall ATO EA. Provide summary EA information to governance board members and EA
stakeholders that draws upon information in the FAA EA Repository and the AVS and ATO Metis
supplemental information repositories as well as any readily available information held in the Rational
Task 6 5 EA Governance Configuration Management Support
The contractor shall Establish establish and maintain the EA baseline under configuration management
control in conjunction with the EA governance processes and organizations. The outcome of this task will
be providing the ability to manage and control changes to the EA baseline.
Task 6 IT Asset Baseline Formatted: Font: Arial, Bold
Formatted: Font: Arial, Bold
The contractor shall support the FAA IT Asset Baseline activity to include IT asset management,
enterprise-wide strategy development, and integration with other FAA IT processes and repositories such
as the EA Repository. The contractor shall scan all non-NAS network-attached devices including
workstations and servers. The contractor shall compile scan data analyses and reports showing the
number and type of devices. The contractor shall compile a list of the software executables on these
devices and map the executable names against products. The contractor shall develop, maintain and
enhance the IT Asset Baseline reporting database. The contractor shall support improvement of existing
IT asset lifecycle management including governance.
Formatted: Font: Arial
Formatted: Font: Arial, Not Strikethrough
Task 8 7 FAA TRM and Standards
The contractor shall recommendRecommend aEnsure that FAA standards are developed and included in
thefor inclusion in the FAA TRM. The contractor shall Analyze analyze the LOB roadmaps, the ITAM
study reports, earlier DOT and FAA TRM reports, and existing EA repository information as necessary to
ensure that the FAA TRM and the other FAA target architectural models (BRM, SRM, DRM) are updated
and included to in the FAA EA Repository. The contractor shall place initial emphasis on recommending
those Initial standards and technologies/products that arerecommended will emphasize those considered
“cross-cutting” across the FAA. The contractor must also identify LOB specific standards will that will
supplement the cross-cutting items and be incorporated into the TRM accordingly. The long-term To-Be
TRM will not be in scope as it is too far out in terms of time to be useful. The outcome of this task will be
a single place of reference for FAA standards. The contractor must Utilize utilize the TRM information to
categorize existing and new FAA investments and identify those requiring transition. The contractor must
Identify and integrate TRM technology families with applicable solution architectures. Provide support for
solution architecture development u
pon direction from the CO.
Task 9 Solution Architecture Patterns & TRM Technology Families<<Need Review>>
Identify solution architecture patterns in use at FAA as well as in the Federal Government and compile
into the EA portal; using EA repository data, develop and integrate TRM technology families with solution
architecture patterns. Develop “wizard” capability to generate straw-man solution architecture and
provide solution architects ability to query EA repository for technology families. The outcome of this task
will be to provide solution architects the ability to quickly obtain straw-man solution architectures to assist
them in developing architectures already compliant with the EA.
Task 10 Develop SRM
Meeting meetingmaterialsin a contractor-provided facility that shall include computers for up to 18 people
if requested. Provide a collaboration support mechanism for meetings as requested 6sduring the base
task yearTask 8 EA Communications
The contractor shall establish and maintain EA communications tools and collaboration vehicles such as
a a KSN site or Lotus QuickPlace site. The contractor must make these vehicles available to any FAA
EA related activities or groups such as the ARB. The contractor must update sites not less than once per
month and must provide documentation of last update on the site. The contractor must provide training
support to EA Repository users to include data collection tool training.
Task 11 9 Software Development Life Cycle (SDLC) Integration
The contractor shall Survey survey and examine SDLC usage within the FAA. The contractor must
Record record similarities and must provide a high level LOB SDLC framework that is acceptable to all
SDLC stakeholders in initial draft and iteratively refined formats until final and accepted by the Chief
Enterprise Architect.. The contractor must Review review Program/Project Management (P/PM)
processes to identify the control points where analytical and decisional inputs/outputs should connect.
The contractor must Provide provide a list of recommended control points within the SDLC framework.
The contractor must Evaluate evaluate opportunities to support the SDLC with tools such as the Rational
Suite for creation of SDLC artifacts. The contract must Produce produce artifacts related to this SDLC
integration task as a best practice SDLC example. The contractor must Ensure include EA and other
Federal requirement integration into P/PM management processes. Activities related to this task may
require, but are not limited to, Business Process Modeling and also research, integration, and deployment
of EA and P/PM enabling tools. The contractor must ensure that the SDLC framework developed meets
Federal, FAA-wide, and individual business unit requirements. The Chief Enterprise Architect will serve
as the POC who will review draft and final deliverables within 5 work days of receipt to determine whether
Federal, FAA-wide, and individual business requirements are met.
Task 10 Portfolio Review
The contractor shall support AIO in its efforts to identify and implement processes that fully support the
EA requirements of the AMS policy. The contractor must support portfolio management through
identifying opportunities to leverage the information in the EA repository within the review process. The
Portfolio Review is the basis for migration planning; it includes combining the portfolios from LOBs and
synthesizing an enterprise wide view and providing analysis to identify efficiencies, conflicts, opportunities
to share infrastructure, etc. The deliverable for this task will be an analysis of the review process with
associated recommendations. The outcome of this task will be to assist in managing FAA’s non-ATO IT
Task 11 Annual EA Migration Planning
The contractor shall provide migration planning support. Migration planning support includes 1) analysis
of FAA’s Strategic Plan, IT Strategic Plan and other available business vision documentation for impact
on the strategic direction of FAA's IT environment/systems; 2) examination of existing project portfolio and
augment based upon gap analysis recommendations; 3) examination of the minutes and specific
technology decisions made by current or planned FAA boards or OMB or Congress to identify mandated
migration dates; 4) and sequencing funded projects into a migration plan taking into account mandated
deadlines. The deliverable for this task is a baseline migration plan that provides a diagram for budget
Task 12 ISSA Integration
The contractor shall update the EA Security Profile to integrate and incorporate the FAA’s Information
Systems Security Architecture (ISSA). The contractor shall modify EA repository and portal and models
accordingly. The outcome of this task will provide the FAA with an enterprise security view aligned to
business strategy. The ISSA integration activity will support an increased level of security information
within the EA Repository. The deliverable for this task is an updated security profile.
The contractor shall provide a plan for the addition of Security Certification and Authorization Package
(SCAP) documentation to the EA Repository that provides for the increased security necessary for
Sensitive Security Information (SSI) controlled under 49 CFR parts 15 and 1520. The deliverable
associated with this part of the ISSA integration task is the SCAPs addition plan.
Task 13 EA Segment Development
The contractor shall identify and group related FAA business process areas, and shall develop all of the
enterprise architecture components (as are related to the FEA models) for these process areas. The
deliverable for this task is a detailed non-NAS segment report and updated EA Repository segment
information for all LOB segments. The outcome of this task increases the scope of the non-NAS EA.
Task 14 LOB EA Support
The contractor shall provide EA development and maintenance support for LOB EA efforts; includes
identification and grouping of several related LOB business process areas, and development of all of the
enterprise architecture components (as are related to the FEA models) for these process areas. This task
differs from Task 17 in that the contractor works on a specific segment(s) providing support directly to an
individual FAA LOB. The deliverable for this task is an LOB EA model integrated with the FAA EA. The
outcome of this task increases the scope of the EA.
Task 15 Repository Study
The contractor shall conduct a study to update the current FAA EA Repository requirements to update
existing requirements and identify any new requirements. The contractor shall provide an outline or WBS
of the steps to be taken to complete the study as an initial deliverable. The contractor shall include a
structured method for gathering requirements in the WBS. For example, the contractor may choose to
contact LOB EA representatives and/or CIOs from each LOB using a repeatable process (structured
interview etc) to gather their requirements. Use of a feedback form on the entry level EA Repository
page to gather input from current repository users is one of several mechanisms that might be
considered for gathering information as is contacting other stakeholders including AIO staff, Employment
of use cases is desirable as is acquisition of a market survey. The deliverables for this part of the task
are the WBS and updated requirements with use cases.
The contractor shall conduct a market survey and provide a study report detailing results and
recommendations as a deliverable. The scope of the market survey must be broader than EA tool sets to
address the capabilities of related tools such as Flashline. An example of a new requirement might be
better integration with Metis or other FAA or DOT EA repository tools. The contractor study report shall
address enhancements already discussed such as 1) replacement of the existing Data Collection Tool
(DCT) to provide web-based access, context-sensitive help, and robust error-checking; and 2)
strengthened ad-hoc query capability to provide a Google-like search. The contractor must include a
discussion of integration with other tools such as Flashline and Metis in the deliverable study report.
Task 16 DOT/FAA EA Data Harmonization
The contractor shall take all steps necessary to ensure that the EA repository content and updates remain
in harmony with the DOT EA Repository after DOT implements Metis, their selected EA toolset. The
contractor must coordinate FAA EA repository metadata content with DOT. The Government will review
metadata content as provided by the contractor and provide feedback as to any changes necessary for
harmonization with DOT.
Task 17 Service Oriented Architecture Support
The contractor shall provide FAA non-NAS SOA readiness analysis support. The contractor shall
conduct an FAA non-NAS SOA readiness assessment and provide recommended steps to prepare for
FAA SOA governance and SOA implementation in the readiness analysis report.
Task 18 FAA EA or SDLC Related Training Classes
The contractor shall provide support for up to three FAA oriented EA or SDLC related training classes.
The training classes shall be provided to a maximum of 12 students and shall take a maximum of eight
hours classroom time for each class. The contractor shall prepare lesson plans and class
announcements, provide draft courseware and/or class presentation materials for COTR approval. Make
any requested modifications and prepare final courseware and/or class presentation materials to be used
during conduct of the class. Conduct the classes using a contractor-provided facility equipped with
computers. Training should be geared to the audience specified by the FAA, for example managers or
solution developers. Provide training rating forms to the students at the end of the class to be returned to
Task 19 Data Architecture Support
The contractor shall support FAA efforts to create an agency-wide Conceptual entity relationship diagram
(ERD), organized by subject area, that describes at a high level the major data elements stored and
transacted by all systems within the agency. The contractor shall develop fully attributed logical entity
relationship diagram that describes all the data elements and their relationships within the agency and an
Interaction Matrix of Data used by each Function/Process. The contractor shall develop the FAA Data
Reference Model (DRM) that fully integrates the FAA Data Architecture. The deliverables for this task are
a conceptual ERD version update and ongoing DRM support. The outcome of this task will be to provide
a line-of-sight from unstructured business data exchanges between processes down to data elements for
use in portfolio and change impact analysis, interface design and standardization, and solution
3.3.2 Optional Tasks
The Contractor may be required to complete the following tasks at the option of the Government: Formatted: Font color: Red
Task 20 Meeting Support
Upon request of the Government, the contractor shall provide meeting support services to include
development of procedures, briefings, communication materials such as meeting calendars, decision
support documentation, meeting minutes, etc. The contractor shall facilitate meetings in a contractor-
provided facility that shall include computers for up to 18 people if requested. The contractor must
provide a collaboration support mechanism for meetings and must provide an official record of decisions
and action items for up to 6 meetings to occur during the base task year.
Task 12 21 Exhibit 300/53 Support and EA Extracts
Upon request of the Government, the contractor shall support AIO in meeting DOT and Federal
compliance and audit requirements including development and EA evaluation of Exhibit 300’s and the
Exhibit 53. The scope of the effort required will be according to the EA requirements delineated in the
latest version of OMB Circular A-11. Upon request of the Government, the contractor shall Update
update the EA Repository whenever 300 / 53 data is more up-to-date than existing data. Upon request of
the Government, the contractor shall Facilitate facilitate export of EA Repository data to other tools in use
within FAA or by DOT. Upon request of the Government, the contractor shall Facilitate facilitate import of
EA data into the EA Repository if requested to do so. . Upon request of the Government, the contractor
shall Support support the creation of extracts of EA repository data such as LOB specific information.
Create Upon request of the Government, the contractor shall create customized EA repository reports
upon request reports..
Task 13 Portfolio Review
The Portfolio Review is the basis for migration planning; it includes combining the portfolios from LOBs
and synthesizing an enterprise wide view and providing analysis to identify efficiencies, conflicts,
opportunities to share infrastructure, etc. The outcome of this task will be to assist in managing FAA’s
non-ATO IT investments.
Task 14 Annual EA Migration Planning
Migration planning includes 1) analysis of FAA’s Strategic Plan, IT Strategic Plan and other available
business vision documentation for impact on the strategic direction of FAA's IT environment/systems; 2)
examination of existing project portfolio and augment based upon gap analysis recommendations; 3) and
sequencing funded projects into a migration plan. The outcome of this task will be a migration plan and
diagram for budget planning purposes.
Task 15 Data Architecture Support <<Need Review>>
Support of FAA efforts to create an agency-wide Conceptual entity relationship diagram (ERD), organized
by subject area, that describes at a high level the major data elements stored and transacted by all
systems within the agency. Develop fully attributed logical entity relationship diagram that describes all
the data elements and their relationships within the agency. Interaction Matrix of Data used by each
Function/Process. Develop the FAA Data Reference Model (DRM) that fully integrates the FAA Data
Architecture. The outcome of this task will be to provide a line-of-sight from unstructured business data
exchanges between processes down to data elements for use in portfolio and change impact analysis,
interface design and standardization, and solution architecture.
Task 16 ISSA Integration
Develop the EA Security Profile to integrate and incorporate the FAA’s Information Systems Security
Architecture (ISSA). Modify EA repository and portal and models accordingly. The outcome of this task
will provide the FAA with an enterprise security view aligned to business strategy.
Task 17 EA Segment Development
Identification and grouping of several related FAA business process areas, and development of all of the
enterprise architecture components (as are related to the FEA models) for these process areas. The
outcome of this task increases the scope of the EA.
Task 18 LOB EA Support
Provide EA development and maintenance support for LOB EA efforts; includes identification and
grouping of several related LOB business process areas, and development of all of the enterprise
architecture components (as are related to the FEA models) for these process areas. The outcome of
this task increases the scope of the EA.
Task 19 EA Research
Provide analysis and recommendations on how to incorporate concepts such as Ontology, Web Services,
and Real-Time Architecture. The outcome of this task will be points-of-view on how to proceed in
expanding the ability of EA to provide value to the FAA.
Task 20 22 Repository Enhancements & maintenance
Upon request of the Government, the contractor shall Continue continue to develop the DOT EA
Repository to support FAA and meet DOT-wide requirements for the sharing of EA information. . Near-
term minor enhancements include updates identified via the existing change request (CR) process.
These enhancements are generally small in scope and can be implemented by a single FTE with one
week or less effort.
completing the Transitional architecture state and related views and models; ad-hoc query capabilityG for
business processes and projects; inclusion of security profiles and account management; and general
improvements such as float-over text content. Future enhancements include integration with FEA models
through an explorer function that links FAA architecture elements to the appropriate SRM, TRM and PRM
components and improvements to the data collection tool (interview format). Note: these updates are
additional to those incorporated in other tasks.
Task 22 DOT/FAA EA Data Harmonization
Ensure that the EA repository content and updates remain in harmony with the DOT EA Repository after
they have implemented Metis, their selected EA toolset. Coordinate FAA EA repository metadata content
with DOT and ensure harmonization.
Task 23 Service Oriented Architecture Support
If requested under this task order, provide SOA readiness analysis support or other SOA support services
Task 24 FAA EA or SDLC Related Training Classes
If requested under this task order, provide support for FAA oriented EA or SDLC related training classes.
Prepare lesson plans and class announcements, provide draft courseware and/or class presentation
materials for COTR approval. Make any requested modifications and prepare final courseware and/or
class presentation materials to be used during conduct of the class. Conduct the classes as requested.
Topic and number of hours of instruction will be included in any request for training support. Training
should be geared to the audience specified by the FAA, for example managers or solution developers.
Provide training rating forms to the students at the end of the class to be returned to the COTR.
Task 21 DOT/FAA EA Data Harmonization
Provide data analysis and update support to harmonize the DOT EA content with the FAA content.
Provide recommendations to DOT on how to improve DOT EA metadata.
Task 22 IT Strategy Visioning
Review business and IT strategic plans for FAA, staff offices, and LOBs and conduct strategic envisioning
sessions that will drive revisions to the FAA IT strategic plans. Provide administrative and related
logistical support and detailed technical expertise and advice in support of preparation and management
of the annual IT Strategic Plan.
Task 25 23 Travel Expenses Shall be paid in accordance with Clause 4531/
Reimbursement of Travel Costs
Travel Expenses (Site Visits, Local Travel including parking and cab fare, etc.)
and Miscellaneous Expenses (Publications, Conferences, etc.) shall be paid according to the ACEP
contract specifications. Travel estimates are based on individual trips of 3 days duration.
6 individual trips Washington, DC to TBD
FAA Tech Center 6 Individual trips Washington, DC to Atlantic City, NJ
FAA Area Center 6 individual trips Washington, DC to Oklahoma City, OK
188.8.131.52. Itemized List and Due Dates
Draft and Final dates for deliverables are expressed in calendar days measured from day of task order award. In
addition to the applicable ACEP contract requirements, the Contractor shall provide the following deliverables and
reports. Note that all data and results achieved are subject to FAA approval and are owned by the FAA. The
technical approval authority is the Chief Enterprise Architect who is the EA Task Order COTR for all deliverables
in this list.
Required Tasks End Result / Deliverable Tool Due Date
1. Program EA Project Plan with MS Office Suite * Overall Program
Management WBS to 3 levels of detail MS Project Management Plan - 10 Days
updated monthly after start of task
Weekly Status Reports (supplements the ACEP IMS).
3 Month Resource
2. Non-ATO Preliminary Baseline: Enterprise 180 days after start of task
Shared Infrastructure wiring Architecture
Infrastructure diagrams Repository /
Development Infrastructure details Metis; other
pages tools TBD
3. EA Content Updated diagrams and Enterprise Updated repository -120 days
Reviews and database and Architecture after start of task; monthly
Data Update Refreshed EA repository Repository / updates of incoming new Formatted: Bulleted + Level: 1 + Aligned at:
(EA content for all EA LOB Metis investment information 0.02" + Tab after: 0.27" + Indent at: 0.27"
Maintenance) and SO segments
Refreshed EA repository
home page information
4. EA Baseline User guide & online help Enterprise 45 days after start of task
Transfer Metadata model Architecture
Data collection tool Repository /
Training material Metis
5. EA Current EA baseline and Enterprise 60 days after start of task and Formatted: Bullets and Numbering
Configuration updated CM reports and Architecture at the end of each month
Management CM reports & statistics Repository / thereafter
Support Metis/ Rational
76. IT Asset Completed analysis of Enterprise 30 days after completion Formatted: Bullets and Numbering
Baseline twice yearly scans Architecture of scan or start of task, Formatted: Bullets and Numbering
Repository / whichever is later
Updated IT Asset Metis/ other 30 days after completion Formatted: Bullets and Numbering
Baseline database tools TBD of scan
Report due 90 days after
IT Asset Management start of each scan Formatted: Bullets and Numbering
Required Tasks End Result / Deliverable Tool Due Date
7.FAA TRM Add FAA standards to Enterprise 75 days after start of task Formatted: Bullets and Numbering
Standards and the FAA EA Repository Architecture or receipt of TRM To-Be
TRM Technology Analysis of ITAM Repository / Information, whichever is Formatted: Bullets and Numbering
Families reports, LOB IT Metis/other later
roadmaps, and other EA tools TBD 150 days after start of
Repository information task
for use in updating 300 days after start of
standards and transition task
plan information Upon request with
Set of updated target deliverable due 40 work
architectures (BRM, days after request320
SRM, DRM, TRM) with days after start of task
and inter-relationships to
include an updated
Identification of solution
architecture patterns and
TRM technology families
Support for up to 6 TBD 7 work days after request Formatted: Bullets and Numbering
9. Meeting meetings per year for up Formatted: Bullets and Numbering
Support to 18 people to include
facilitation and minutes
LOB EA Support LOB EA models integrated Enterprise Ongoing beginning 30 Formatted: Bullets and Numbering
and Integration with EA Repository Architecture days after start of task; Formatted: Bullets and Numbering
Minor agreed upon LOB EA Repository / weekly reports thereafter
tasks as requested— Metis Upon request with
larger tasks must use deliverable due 5 work
change request process days after request
108. EA Establish new Enterprise 20 work days30 days after Formatted: Bullets and Numbering
Communications collaboration site or Architecture requeststart of task
update existing site Repository / 3 to 20 days after request
Presentations, web Metis / MS with depending upon Formatted: Bullets and Numbering
pages, printed fact Office Suite, scope of item
sheets, posters or other Cold Fusion requested120 days after
communication materials graphics and/or start of task
upon request desktop
119. Software LOB Framework Enterprise First draft 90 days after
Development Recommended controls Architecture start of task
Life Cycle Artifacts Repository / Second draft 180 days after
Integration Metis/ Rational start of task
Suite Final – two weeks14 days
before close of task year
Required Tasks End Result / Deliverable Tool Due Date
12. Exhibit Provide Enterprise Upon request with Formatted: Bullets and Numbering
300/53 Support Extract for FAA LOBs, DOT Architecture deliverable due work Formatted: Bullets and Numbering
and EA Extracts or e-CPIC Repository / Upon request with
Metis deliverable due work after
1310. Portfolio Analyis of review process Microsoft Office Upon request with Formatted: Bullets and Numbering
Review with recommendations Suite deliverable due 30 work
days after start of task
1411. Annual EA Baseline Migration Plan Enterprise Upon request with
Migration Architecture deliverable due 90 days
Planning Repository / after start of task
15. Data Conceptual ERD version Enterprise Upon request with deliverable Formatted: Bullets and Numbering
Architecture update Architecture due
Support Ongoing Data dictionary Repository /
Formatted: Normal, Bulleted + Level: 1 +
1612. ISSA Updated security profile Enterprise Upon request with Aligned at: 0" + Tab after: 0.25" + Indent at:
Integration SCAPs addition plan Architecture deliverable due 270 days
Repository / after start of task Formatted: Bullets and Numbering
Metis Upon request with360
days after start of task
deliverable due 60 days
1713. EA Detailed Segment Report and Enterprise Upon request with
Segment Updated EA Repository Architecture deliverable due 210 days
Development Repository / after start of task
18. LOB EA LOB EA models Enterprise Formatted: Bullets and Numbering
Support Architecture Formatted: Bullets and Numbering
Metis Formatted: Normal
14, LOB EA LOB EA models Enterprise Ongoing beginning 30 Formatted: Bullets and Numbering
Support integrated with EA Architecture days after start of task; Formatted: Bullets and Numbering
Repository Repository / weekly reports thereafter
Minor agreed upon LOB Metis Upon request with
EA tasks as requested— deliverable due 5 work
larger tasks must use days after request
change request process
19. EA Research EA-related t MS Office Upon request with Formatted: Bullets and Numbering
deliverable due work
20. Repository Minor or new Enterprise Upon request with Formatted: Bullets and Numbering
Enhancementnh Architecture deliverablework unless a Formatted: Bullets and Numbering
ancements Repository / later date is agreed upon
Metis/ Excel by the COTR
21. DOT/FAA EA EA repository/content Enterprise Upon request with Formatted: Bullets and Numbering
Data updates Architecture deliverable10 work Formatted: Bullets and Numbering
Harmonization DOT EA metadata Repository / unless a later date is
Metis agreed upon by the COTR
2215. Repository Updated requirements MS Office 45 work days after start of Formatted: Bullets and Numbering
Study with use cases task Formatted: Bullets and Numbering
Study report including 100 work days after start
market survey results and of task
Required Tasks End Result / Deliverable Tool Due Date
16. DOT/FAA EA EA repository/content Enterprise 90 days after start of task Formatted: Bullets and Numbering
Data updates and harmonized Architecture Formatted: Bullets and Numbering
Harmonization metadata Repository /
2317. Service SOA readiness analysis MS Office Draft 45120 work days
Oriented Report after requeststart of task
Architecture Other SOA support as Final 60 180 work days
Support requested after requeststart of task
2418. FAA EA or Lesson Plan and Class TBD Upon request with lesson
SDLC related Announcement plan due 10 days after
training classes Draft Courseware or request120 days after
Class Presentation start of task
Materials Upon request with draft
Final Courseware or deliverable due 25 work
Class Presentation days after request140
Materials days after start of task
Conduct Class Upon request with final
Training Rating Form deliverable due 25 work
days after request150
days after start of task
19. Data Conceptual ERD version Enterprise 210 days after start of Formatted: Bullets and Numbering
Architecture 6 update Architecture task Formatted: Bullets and Numbering
Support Ongoing DRM Support Repository / Ongoing DRM support
Metis Formatted: Bulleted + Level: 1 + Aligned at:
with activities reported at
0" + Tab after: 0.25" + Indent at: 0.25"
EA project meetings
25. Travel Individual contractor travel TBD Initiated by request of the Formatted: Bullets and Numbering
expense report COTR Formatted: Bullets and Numbering
Optional Tasks End Result / Deliverable Tool Due Date
Formatted: Font: Bold
Support for up to 6 TBD Upon request of the Government – Formatted: Font: Bold
20. Meeting meetings per year for up to due 7 work days after request Formatted: Font: Bold
Support 18 people to include Formatted: Font: Bold
equipped with computers,
printed material, meeting
facilitation and minutes
21. Exhibit Provide EA compliance Enterprise Upon request of the Government- Formatted: Bullets and Numbering
300/53 Support extracts upon request Architecture deliverable due 5 work days after Formatted: Bullets and Numbering
and EA Extracts Extract for FAA LOBs, DOT Repository / request
or e-CPIC Metis Upon request of the Government
with deliverable due 5 work days
22. Repository Minor repository Enterprise Upon request of the Government
Enhancement enhancements to be Architecture with deliverable due 7 work days
requested via existing or Repository / after request unless a later date is
new change request Metis/ Excel agreed upon by the COTR
23. Travel Individual contractor travel TBD Initiated by request of the COTR
*The Contractor shall maintain a single project schedule, using MS Project 2000 or compatible software,
from which various project reports shall be produced. The electronic project file and the following reports
shall be provided as required:
Project Gantt chart showing major tasks and milestones
Detailed Work Breakdown Structure (WBS) to at least 3 levels of detail
Inspection and Acceptance. In the absence of other agreements negotiated with respect to time provided for
government review, final deliverables will be inspected and the contractor notified of the COTR’s findings within 5
work days of normally scheduled review. If the deliverables are not acceptable, the COTR will notify the CO
4. Government Furnished Resources
4.1. Facilities, Supplies and Services
1. The FAA shall provide a primary point of contact (COTR) and secondary point of contact (alternate
COTR) with the authority to make technical decisions. The COTR and alternate will be designated as
the FAA Project Manager and alternate.
2. FAA will purchase the required software licenses for COTS software (if any) required for the use of
3. The FAA has a long term licensing agreement with Oracle.
5.4. The FAA will task the current EA contractor to transfer documentation specific to the currently used Formatted: Bullets and Numbering
FAA enterprise architecture and data management tools (e.g., EA Repository, FAA Data Registry and
FAA Metadata Repository).
5. Remote access will be provided to the contractor to the following hardware
and software owned by FAA that is currently housed in Oklahoma City,
Oklahoma. Current hardware includes one Dell 2850 Server. This server is
loaded with VMWare 2.52 which is a software package that allows the setup
of multiple servers one piece of the overall server resources.. There are
currently two virtual servers supporting the FAA EA Repository. One is
production and the other is test. Both are running Windows 2003 Web
Edition service pack 1 and Oracle 9.2 client that connects to an Oracle 9i
database that is on a Tru64 Unix Alpha Class ES40 server. All other
hardware and software to be utilized in the support of this contract is the
responsibility of the successful bidder
4.2. Information Sources
FAA Government Furnished Information (GFI) shall include the following:
Access to the FAA EA Repository (developmental and production) on the FAA intranet at http:// ea.faa.gov.
Access to the FAA EA NAS Support KSN web site.
Access to the ATO Metadata Repository information systems inventory on the FAA Intranet at
FAA Order 1375.1C, Data Management.
FAA Order 1370.82, Information Systems Security Program.
FAA Order 1600.1D, Personnel Security Program
FAA Data Management Strategy, Federal Aviation Administration, Office of Information Services and Chief
Information Officer, Version 1.0, dated 21 September 1999.
FAA Information Technology Strategy, Office of Information Services and Chief Information Officer, Version
1.0, dated 22 September 1999.
FAA Data Architecture, version 1.1, dated 15 November 2001.
Draft ATO Information Technology Architecture Vision and Principals.
FAA Flight Plan, latest version.
AIO Business Plan (2007).
FAA Performance Plan with Agency performance measures and targets.
FAA Directory of Plans website at http://www.apo.data.faa.gov/dirplans/.
Publicly accessible FAA information on the internet at http://www.faa.gov.
FAA Information Systems Security Architecture, Version 2.0.
The following specifications, handbooks, orders, forms, and standards are listed for informational purposes
Presidential Decision Directive 63, Critical Infrastructure Protection (May 1998)
Metamodel for the Management of Shareable Data, American National Standards Institute, ANSI X3.285,
Framework for the Specification and Standardization of Data Elements, International Organization for
Standardization and International Electrotechnical Commission (ISO/IEC), International Standard
ISO/IEC 11179, 1998.
FAA Acquisition Management System as documented by the FAA Acquisition System Toolset
Copies of FAA documents may be obtained from the Federal Aviation Administration, Headquarters Public
Inquiry Center APA-230, 800 Independence Avenue SW, Washington, DC 20591, 202-267-3484. Requests
should fully identify material desired and cite the solicitation or contract number.
Requests for copies of documents not covered in the preceding paragraphs should be addressed to the
Contracting Officer. Requests should fully identify material desired and cite the solicitation or contract number.
5. Contractor Furnished Resources
5.1. Facilities, Supplies and Services
The Contractor shall provide all management, administrative, clerical, and supervisory functions required for the
effective and efficient performance of this task order. The Contractor shall provide appropriate office space and
equipment for the performance of this EA task order as stipulated under the ACEP contract. At a minimum, the
Contractor is to furnish the following items:
Off-site office space, phone, LAN and Internet access, IT equipment, and office supplies. Permanent FAA office
space will not be provided. Interim FAA Office space may be available in FOB 10B when supporting specific
project activities but is not guaranteed.
Task Order Specific Material (TOSM) necessary for task performance shall be identified and approved in writing
by the Contracting Officer or the appropriate government technical representative prior to being procured.
6. Administrative Considerations
6.1. Government Contacts
Con Kenney (COTR)
U.S. Department of Transportation / FAA
FAA Chief Enterprise Architect
800 Independence Avenue, SW
Washington, DC 20591
Telephone: 202 385-8050
Karen Kaye (Alternate COTR)
U.S. Department of Transportation / FAA
FAA Chief Enterprise Architect
800 Independence Avenue, SW
Washington, DC 20591
Telephone: 202 385-8180
6.2. Place of Performance/Work Location
The primary place of performance for the activities covered under the SOW tasks, shall be the contractor’s
facility. If space is available, the FAA may allow contractor staff to sit at the FAA Headquarters, or the
Contractor may complete significant portions of the work in its own facilities.
6.3. Hours of Work
The hours of work will be during normal business hours (see contract Clause G.8) and will follow the federal
6.4. Period of Performance
The period of performance for this Task Order shall be:
Base Year Date of Award through 12 months thereafter
Option Year 1 13 months after date of award through 24 months thereafter
Option Year 2 25 months after date of award through 36 months thereafter
Option Year 3 37 months after date of award through 48 months thereafter
Option Year 4 49 months after date of award through 60 months thereafter