DRAFT
Section C
Statement of Work
For
Financial Support Services
PART I - SECTION C
STATEMENT OF WORK
C.1 Introduction
C.1.2 Purpose
The purpose of this procurement is to acquire support services for information technology financial
management services support of the FAA/ABA’s mission, vision, goals and objectives. The awarded contract
must provide the Office of Financial Services (ABA) and other FAA/ABA financial stakeholder organizations
support services for FAA/ABA’s financial information technology business needs and requirements. The
Office of Financial Services (ABA) provides IT financial management support services for many organizations
within the FAA. The financial management systems that ABA supports are listed in Section J Appendix 1 of
the SIR.
C.1.4 Period of Performance
The period of performance will consist of a base period starting at time of award for a period 12 months, with 6
one-year option periods.
C.2 Scope
The scope of the awarded contract is one that provides best in class IT financial management support services in
the following areas:
1. Program Management
2. Enterprise Architecture
3. Project Management Office (PMO)
4. Change and Configuration Management
5. Application Development
6. Business Intelligence and Reporting
7. Infrastructure and Operations
8. Information Security
9. Quality Assurance
10. Independent Validation and Verification (IV&V)
11. Business Process Reengineering
12. Special Projects; Other IT related requirements necessary to support the financial
business processes of the FAA.
The detailed requirements of these categories are described in Section C.3 below. The scope includes all
technology related work necessary to support the FAA/ABA financial business requirements.
The anticipated contract must also provide information technology financial management support services for
the financial system requirements of other FAA organizations such as Air Traffic Organization (ATO) and
Region and Center Operations (ARC) and other FAA Lines of Business.
In all areas of the requirements described below, the contractor must provide support services defined in
specific task orders and deliverables as required. In no circumstances will the supplier have the final
determination of any policy, process, rule or other inherently governmental activity. Final determination and
acceptance of these types of deliverables and work products are exclusively reserved for the FAA/ABA.
2
C.3.0 REQUIREMENTS
C.3.1 Program Management
The contractor must provide overall program management support, analyses and planning in order to operate
efficiently. Program management support will include analyses and recommendations pertaining to the overall
organizational effectiveness of ABA; assistance with the integration of the horizontal and vertical functions of
the ABA; and participation in meetings, conferences and forums to promote stakeholder and other external
relations. The primary goals for information technology governance are to (1) assure that the investments in IT
generate business value, and (2) mitigate the risks that are associated with IT. The Contractor must assist ABA
to implement organizational structure changes recommended in a FY10 Control Objectives for Information and
related Technology (COBIT) Assessment. The COBIT assessment provides a framework for effective
governance of IT to assist ABA Managers to understand and fulfill their legal, regulatory, and ethical
obligations in respect of their organizations’ use of IT.
C.3.2 Enterprise Architecture
The contractor must provide services support, maintain and update the ABA Enterprise Architecture program
and the FAA Financial Segment Architecture. This includes the business, information, systems and technology
architectures as well as individual systems technical architecture designs. Assist the FAA/ABA to update
architecture components for administrative business process, applications, and technology to the ―As-Is‖ state.
Assist the FAA/ABA to update, revise and maintain the ABA EA governance plan, formulate EA standards and
perform necessary reviews on IT projects for compliance to standards. Data governance is an emerging
discipline with an evolving definition. The discipline embodies a convergence of data quality, data
management, data policies, business process management, and risk management surrounding the handling of
data in an organization. Through data governance, organizations are looking to exercise positive control over
the processes and methods used by their data stewards and data custodians to handle data.
The Contractor must also assist ABA to develop a data governance process that ensures that important FAA
financial data assets are formally managed throughout the FAA. The contractor must assist ABA to develop a
process that ensures data can be trusted and that people can be made accountable for any adverse event that
happens because of low data quality. The contractor must recommend technology to help aid in he
implementation of the new data governance process. The Office of Financial Services is required to adhere to
OMB A-127 and its requirement for a Five Year Financial Management Systems plan. In support of this
requirement the contractor must:
- Support development of 5 Year IT Strategic and Systems Plan, work with the necessary stakeholders in
developing the project portfolio to support the business plan and IT strategic plan.
- Support development of performance metrics framework.
- Evaluate and recommend new technologies for use in project solution design and implementation
- Review and recommend solutions to improve operational performance of financial systems
- Measure and analyze metrics to evaluate progress against strategic and operational goals
C.3.3 Project Management Office
Contractor must support the FAA Office of Financial Services, Project Management Office (PMO). The PMO
is responsible for formulating and publishing PMO policies and processes, managing and implementing process
improvement initiatives, providing training on PMO policies, tools and processes. The PMO provides support
in project management, preparing, maintaining and tracking project schedules for financial systems and related
projects using the FAA/ABA provided Project planning and Portfolio Management (PPM) tool. The PMO
3
conducts necessary reviews on projects for compliance and quality, collects and maintains quality metrics and
briefs senior executives on a scheduled basis on the status of projects, PMO initiatives and metrics. In addition
to supporting the above activities, the contractor must maintain a consolidated master project schedule using the
FAA PPM tool from which various projects reports must be produced.
The contractor must provide all of the necessary technical engineering, operations research, and business and
administrative support such as: organizing, coordinating, and tracking required to perform all of the activities
successfully as required in accordance with ABA project management guidance.
C.3.4 Change and Configuration Management
The Change Management
Contractor must provide support for improvement and streamlining of existing change management procedures
for FAA/ABA. Ensure communication and documentation of change management policies and procedures
across the organization. Develop, define, and enforce change management policies and procedures. Ensure that
all policies and procedures are in line with ITIL Framework. Provide second level support for change
management and utilization of the Remedy application. Develop and communicate, and publish via FAA/ABA
intranet all policies and procedures as they relate to change management. Perform training as required.
Develop change control board (CCB) processes and facilitate CCB meetings as required. Develop, implement,
and facilitate regularly scheduled Change Control Meetings for discussion of ALL upcoming change activity
across FAA/ABA application portfolio using a forward schedule of change (FSC). Provide seamless support
with configuration management processes. Provide seamless support of Incident Management processes as they
relate to Change Management. Develop, implement, and automate reporting metrics for management updates
as required by FAA/ABA to illustrate adherence to Change Management policies and procedures. Provide
recommendations for continuous improvement of Change Management functions to FAA/ABA managers as
becomes necessary. Provide ITIL Training to staff as required for complete understanding of ITIL Framework
(Version 3). Provide Remedy training for staff as required.
The Configuration Management
Contractor must develop and implement a Configuration Management action plan to document and store any/all
updates to Configuration Items for hardware AND software assets as defined in a Configuration Management
Database (CMDB). Provide documentation of activities surrounding migrating of any/all assets (hardware,
software, code, database) to production operating systems using the Change Management process. Ensure that
these processes are in line with ITIL Framework. Assist in development of standardized naming conventions for
configuration items within the configuration management library. Develop, implement, and automate
supporting metrics as defined by FAA/ABA to document adherence to defined configuration management
procedures and policies. Develop and implement version control policies across the FAA/ABA software
catalog. Develop processes to keep stakeholders informed of updates to configuration items that occur via
change control or other means outside of FAA/ABA procedures (changes to production configuration items
without using change control process). Provide seamless support of change management processes. Provide
recommendations for continuous improvement of Configuration Management functions to FAA/ABA managers
as becomes necessary. Provide ITIL Training to staff as required for complete understanding of ITIL
Framework (Version 3). Provide Remedy training for staff as required.
4
C3.5 Application Development
C3.5.1 Requirements:
The contract must provide requirements management services. Requirements management will
assure the organization documents, verifies and meets the needs and expectations of its customers
and internal or external stakeholders. Requirements management will begin with the analysis and
elicitation of the objectives and constraints of the organization and further includes supporting
planning for requirements, integrating requirements and the organization for working with them
(attributes for requirements), as well as relationships with other information delivering against
requirements, and changes for these.
The traceability must be established to manage requirements to report back fulfillment of company
and stakeholder interests, in terms of compliance, completeness, coverage and consistency.
Traceability also support change management as part of requirements management in
understanding the impacts of changes through requirements or other related elements (e.g.,
functional impacts through relations to functional architecture), and facilitating introducing these
changes.
Requirements management will involve communication between the project team members and
stakeholders, and adjustment to requirements changes throughout the course of the project. To
prevent one class of requirements from overriding another, constant communication among
members of the development team is critical.
The contractor must:
Define Business Needs. Assist the FAA project managers and business unit staff in
defining FAA financial management project’s business requirements. Business
requirements include a statement of the organization’s business objectives and the ultimate
vision of what the system will be and do.
Identify Project Stakeholders and User Classes. Assist the FAA project managers by
identifying important project stakeholders. Work with the FAA business managers to select
appropriate representatives for stakeholder and enlist their participation and negotiate their
responsibilities. Assist the FAA project managers with the documenting of the
contributions from stakeholders and agree on an appropriate level of participation and
commitment from each one.
Conduct Requirements gathering interviews. Assist FAA users in articulating the
desired system capabilities needed to meet their business objectives.
Analyze Requirements. Assist the FAA by drafting requirements documents that are a
logical consequence of the customers’ requests, as well as identify implicit requirements
that are expected and verbalized. Identify vague, weak words that cause ambiguity and
confusion. Identify conflicting requirements and areas that need more detail. Specify the
functional requirements at a suitable level of detail for project success.
Write Specifications. Write draft and after FAA review and approval, write final well-
organized requirements specifications that clearly express the shared understanding.
Model the Requirements. Create represent requirements with non-textual media,
including graphical analysis models, tables, mathematical equations, storyboards and
5
prototypes. To maximize communication and clarity, draw analysis models according to
the conventions of a standard such as the Unified Modeling Language.
Assist FAA in Requirements Validation. Assist the FAA to ensure that the documented
requirements satisfy customer needs by reviewing designs, program code and test cases
based on the requirements specifications. Recommend changes to the requirements
document based on the review. In the validating process the review must recommend that
the requirements are clear, complete, correct, feasible, necessary, traceable, unambiguous,
and verifiable against the specifications provided.
Facilitate Prioritization. Assist FAA project managers by brokering collaboration and
negotiation among the various users’ stakeholders to ensure sensible decisions are made.
Manage Requirements. Assist FAA Project managers to establish the requirements
baseline; manage the requirements and verify FAA stakeholder satisfaction. Store the
requirements in the FAA designated tool designed which will be provided by the FAA
using the contractor’s recommendation. Track the status of individual functional
requirements as they progress from inception to verification in the integrated product.
Collect traceability information from FAA team members to connect individual
requirements to system elements.
C3.5.2 Application Development:
The contractor must provide support services for application development in a federal financial
environment. The requirement consists of providing the required contractor resources to support
the design, development, implementation and on-going support of the FAA/ABA financial systems
(See Section J, Appendix 1 for a list of systems).
All ABA financial applications will require the adherence to the FAA/ABA software development
lifecycle per the FAA ABA System Development Lifecycle (SDLC) process. (See Section J,
Appendix 3 for schematic of the process) Applications, Commercial off the Shelf Package (COTS)
configurations and web development services required by FAA/ABA include, but are not limited
to the following deliverables;
Preliminary Design Reviews
Critical Design and reviews
Development and unit test
System Integration testing
Configuration/change Management
Production migration
6
Documentation
Tier 3 support for the application
On-going enhancements
Several application development tools are utilized in supporting the FAA ABA SDLC processes.
These tools and applications are listed in Section J, Appendix 4. The contractor is expected to be
proficient in those tool sets.
The contractor must be proficient in the following languages and technologies to support
development and support ABA’s financial systems.
Java and JavaScript
SQL/XML
PL/SQL
.NET
XML DB
XSLT
WS-PBEL
WSDL / UDDI
PHP
HTML 4 and XHTML
People soft People code
PeopleSoft Application Designer
CSS – Cascading Style Sheets
VBScript
Visual Basic.NET
7
Perl
ActiveX Controls
ASP and ASP.NET
All application design and development must adhere to the following:
Federal, FAA, ABA standards and policies
Security Standards and policy
Web site/pages FAA branding standards
Industry standards or best practices if not addressed in standards
Conform to FAA and ABA Enterprise Architecture where applicable
The contractor will have to support the operations and configuration of COTS software packages.
This requires expert level knowledge in the following software packages:
Oracle Financials version 11 and 12,
SAP Business Objects
Oracle PeopleSoft
CompuSearch PRISM
Oracle Prism OCI
EMC Documentum
Oracle Goverence Risk and Compliance (GRC)
Oracle Service Oriented Architecture (SOA)
QlickView
In addition to development of deliverables the contractor must perform/create production
migrations, system documentation, document Standard Operating Procedures (SOPs), hand off
production operation to the Operations team and perform life cycle maintenance of all our
financial applications. It’s expected that the contractor keep ABA current with new technologies.
8
The contactor should apply the knowledge of new technologies and industry standards/best
practices to application enhancements and new solutions.
Contractor must establish and maintain knowledge base for all software and support activities
using FAA/ABA’s Knowledge Services Network (KSN) (FAA’s Sharepoint) and network share
drives.
C3.5.3 Testing:
Contractor must develop test plans and conduct structured testing in the following areas:
regression, unit, system and customer tests. The contractor will prepare and submit a test analysis
report and correct all discrepancies found during the testing period prior to system
acceptance/accreditation or as agreed with the FAA/ABA. The contractor must assist with the
development of automated test scripts in the FAA/ABA provided automation test tool to assist
with regression testing of FAA/ABA systems and provide technical support around usage of the
automated test tool. This task requires Expert knowledge of Quality Center.
Some of the deliverables/activities for the test team include:
Planning and developing test cases – writing test plans and documentation,
prioritizing the testing based on assessing the risks, setting up test data,
organizing test teams.
Setting up the test environment – an application will be tested using multiple
combinations of hardware and software and under different conditions. Also,
setting up the prerequisites for the test cases themselves.
Writing test harnesses and scripts – developing test applications to call the API
directly in order to automate the test cases. Writing scripts to simulate user
interactions.
Planning, writing and running load tests – non-functional tests to monitor an
application's scalability and performance. Looking at how an application behaves
under the stress of a large number of users.
Writing bug reports – communicating the exact steps required to reproduce
unexpected behavior on a particular configuration. Reporting to development team
with test results.
C3.5.4 Technical/Business Subject Matter Experts:
Contractor must provide resources that are mix of technical and business subject matter experts. In
the systems listed below we are requesting resources who understand government processes,
regulations and systems’ technology to assist and support system enhancements and new designs.
The FAA systems that we would require SMEs are;
Oracle Financials version 11 and 12 (FAA Accounting System – Delphi)
Oracle PeopleSoft version 8.9 or up (FAA Cost Accounting System – CAS)
Oracle Governance, Risks and Compliance version 8 and up –GRC
9
Compusearch Prism version 6.5 and up (FAA Procurement system)
EMC Documentum
Each of the SMEs should be experts in each of the systems listed in Section J. They should
understand business processes, how the processes integrate into the system, how the system is
configured. In addition these resources should be experts in data analysis to understand problems
and issues and recommend appropriate designs for enhancements and/or new implementations
and/or trouble shoot problems.
C3.6 Financial Data Warehouse, Business Intelligence and Reporting
The FAA/ABA currently has a financial data warehouse. The contractor will be responsible for the
enhancement and operations of the warehouse. Services that will be provided by the contractor include the
following:
Modeling the Business - Modeling the business processes and intersection of the data.
Defining requirements and measurements Metrics – Define and document the business performance
metrics and Critical Success Factors and model this into the warehouse and reporting.
Sourcing data – Documenting where the source data will come from, how will it be presented, will data
element need to be derived and to what detail.
Identification of data warehouse tool set – Recommendation of using the existing tool sets and/or
recommendation of new tool sets to meet the new and/or existing requirements.
Warehouse modeling and defining of Data Marts – Based on requirements and industry standards model
the data in the warehouse. Documenting the de-normalized structures to support efficient retrieval of the
data. Creating data marts and underlying data structures to support appropriate grouping of data. This
would include aggregates or OLAP (online analytical processor) and processes where appropriate.
Copy, building and loading the warehouse – This is the electronic transformation and load of the data
into the warehouse. Defining and building the ELT code to acquire, load and store the data in the ware
house.
Building Business intelligence, reporting and dash boards - Based on requirement building the method
the users will access and report/analyze/mine the data.
Training - Training of the end users.
The contract must support current operations of the existing warehouse and business intelligence tool sets. The
ABA warehouse is constructed with Oracle 11i, Business Objects, Oracle Discover and Qlickview. The
contractor must be knowledgeable in industry best practices, new technologies so that they can recommend the
most cost effective and efficient design. This would include review of existing data marts and tools sets to
ensure we stay current with industry standards.
The contractor will maintain and update the automated reporting capability tools for the Property and Cost
Analysis Division, and the Financial Statements and Reporting Division. The contractor must provide all of the
necessary technical engineering, operations research, and business support such as: planning, organizing,
managing, coordinating, and tracking (e.g., report management, cost/schedule/performance measurement, risk
management, component procurement management, system engineering management) required to develop and
maintain an enterprise-wide financial reporting system using existing Business Objects and/or recommending
must effective tools set or design possible.
10
Contract must be proficient in the following areas:
Documenting business processes and intersection of the data
Data Sourcing and acquisition
Building and maintaining the data dictionary
Warehouse design
ETL development
Reporting
Business Intelligence and data mining
Dashboards
C3.7 Infrastructure and Operations
C3.7.1 Infrastructure Requirements:
The contractor must provide technical support for the Infrastructure in use in support of ABA systems. This
includes ongoing maintenance and support tasks associated with the server platforms, operating systems,
storage arrays, switches, cabling, and other peripherals listed in Appendix X. The contractor must provide
ongoing maintenance of server operating systems such as service packs, fixes, and security patching. Hardware
support will also be required with tasks such as troubleshooting and repair and/or replacement. The contractor
will be responsible for planning, testing, and implementing any required operating system and hardware
upgrades. These tasks will encompass all environments in support of the FAA/ABA to include development,
test, and production.
The contractor will be responsible for developing and implementing an IT Technology and Acquisition plan, to
include lifecycle replacement, in support of FAA and ABA standards. This will include a strategy for
increased consolidation and standardization. Emerging technologies will be evaluated as part of the process in
order to ensure optimum efficiency and performance, while creating a flexible and expandable infrastructure.
As directed, contractor must evaluate hardware, firmware, peripherals, software packages for potential use by
FAA/ABA, and provide recommendations for their integration into the environment.
The contractor will be responsible for developing reports on performance, availability, and other infrastructure
and operations related activities. These reports will be developed based on requirements provided by ABA-20.
The contractor will be required to evaluate technologies to improve the reporting capabilities.
The contractor will be responsible for developing and maintaining a continuity of operations plan for ABA
systems. The FAA/ABA will provide the requirements for return to service and return to operations timelines.
C3.7.2 Operations Requirements:
The contractor must perform implementation, documentation of deployment and operating procedures,
operations and life cycle maintenance of all aspects of systems and technology implementations including web
page development, database development, enterprise solutions, financial systems modernization, data
warehousing, etc. and coordination with agency groups, and COTS vendors.
The contractor must provide performance monitoring, optimization and System Maintenance for existing and
newly developed FAA/ABA systems and applications. Contractor must conduct periodic performance
measurement and evaluation activities that may lead to re-engineering and/or optimization of existing
11
applications to improve productivity, system performance, network throughput, changing functional and
technical requirements or any other constraints identified by the Government personnel.
The contractor must maintain a help desk to provide end-user support for all national, local and specialized
ABA Financial system applications. Areas of support will include telephone assistance, problem tracking, initial
triage and problem resolution, call escalation, and limited training. The contractor must also provide,
troubleshooting and technical support to the end user of the applications. Software application support services
center must provide Level I, Level II and Level III support as necessary for the financial applications. The
Contractor must have experience and knowledge utilizing the FAA’s standard Service Desk Management Tool,
BMC’s Remedy.
The contractor must establish and maintain knowledge base for all software and support activities using
FAA/ABA’s Knowledge Services Network (KSN), the FAA/ABA’s Microsoft Sharepoint Server 2007 Network
and other established FAA Service Desk Management Tools such as BMC’s Remedy.
The contractor must provide database administration support services for FAA/ABA financial information
systems. The FAA/ABA’s business requirement is to support the databases of financial and mixed financial
systems. The database administrator (DBA) is responsible for the performance, integrity and security of a
database of all ABA supported or owned information system. Areas of support include database planning,
development, monitoring and troubleshooting.
The contractor must provide the database development and maintenance support for all the software
development related activities. The database development activities should include, but not limited to, database
requirements collection, database requirements analysis, database design and modeling, database scripting,
creating data marts and data warehouses, database backup and recovery, database performance and tuning,
database upgrades and updates, database consolidations etc. The work may be pure maintenance or it may also
involve specializing in database development.
The Contractor must provide support for Oracle Application Server in development, test and production
environments. This task includes the installation and patching of the application, account maintenance and
Oracle Forms migration.
The Contractor must install, configure and maintain all software components pertaining to the PRISM
procurement application in both development and production environments. They must provide technical
support for the interfaces to PRISM using approved APIs, Secure FTP, Oracle Database links, and UNIX data
files. They must provide technical support for the JAVA components of the application.
The Contractor must provide operational support, research, troubleshooting, and problem resolution and
business support of the PRISM web server. The Contractor must also perform application upgrades, identify
proposed technical solutions, provide technical support for Oracle Reports and Discoverer, provide
configuration management support and cross train to the FAA/ABA designated COTR as it pertains to the
PRISM web server.
The contractor must have experience supporting application software listed in Section J, Appendix 2 of this
SIR.
The Contractor must assist ABA Project managers to conduct weekly meetings with ABA Operations Lead to
review operational issues, risks, performance metrics, and improvement initiatives.
The Contractor must assist ABA by drafting and upon FAA/ABA approval finalizing operational processes and
assist to ensure that the operational processes are followed and improved upon, including proper Change
Management processes and approvals for all types of releases.
12
The Contractor must recommend best practices for ABA technical and/or business operations.
The Contractor must assist ABA Project managers to document standard operational processes. This entails
developing draft standards and upon FAA/ABA approval, finalizing such drafts.
The Contractor must provide assistance to ABA Operations Lead as part of the financial systems Change
Control Board (CCB).
The Contractor must assist ABA by acting as a central point of communication for FAA/ABA customers and
system teams by coordinating FAA/ABA provided status information on problem resolution and impact of
problems on service delivery, other projects, and contractor resource availability.
The Contractor must assist ABA by organizing problem resolution workflow efforts to follow the documented
problem resolution process. This includes ensuring proper approval gates from ABA; documentation of
changes, and status tracking of problem. The contractor must also recommend problem resolution process
improvements where necessary.
The Contractor must assist ABA to develop or update service level agreements with ABA customers and
agreements with other entities that ABA relies on for service. Contractor must also assist ABA to track, report
against, and generate corrective measures, recommendation, when there is a breach of a service level.
The Contractor must assist ABA by providing standard reporting for production and development infrastructure
such as system availability, responsiveness, etc. across environments and recurring operations checking an
interface, running processes, numbers of operational issues and other types of production and development
infrastructure or recurring operational reports as requested.
C3.8 Information Security
ABA-20 is required to maintain a proactive position regarding the protection of FAA/ABA financial systems
and sensitive data. The business requirement for information security includes contractor support for security
analysis, Program management support, Audit tracking and remediation for audit findings, system certification
and accreditation, risk mitigation support for ABA’s financial systems in accordance with ABA and NIST
security guidelines and policies.
C3.9 Quality Assurance
The contractor must perform independent activities to assure the quality of all software and documentation
produced under this SOW and to ensure compliance with all requirements of this contract.
The contractor must develop, implement, and maintain a Software Quality Plan (SQP) to include resources
required, schedules, tasks to be performed, procedures and tools to be used, records to be provided, the
methodology of identifying and implementing process improvements in the software development processes
and related management areas, and the contractor's software quality organization and interfaces. The Software
Quality Plan will describe how the contractor's overall software quality program will be applied.
The contractor must perform detailed reviews, walkthroughs, requirement traceability analyses, and defined
verification and validation processes which occur during the course of software development to ensure that
requirements are traceable, consistent, complete, and testable. The contractor must ensure the software
correctly reflects the documented requirements. The contractor must prepare for, conduct, report on, and/or
participate in formal reviews, informal reviews, inspections, peer reviews, tests, and evaluations for the purpose
of determining whether advancement to the next phase is warranted.
13
The contractor must ensure that quality assurance requirements are enforced for all aspects of software
development and/or revision.
The contractor must collect and analyze software quality metrics which include traceability, completeness,
consistency, accuracy, simplicity, and modularity. The metrics are directly related to the non-functional
requirements specified for the software.
C3.10 Independent Validation and Verification (IV&V)
The Contractor must provide Independent Verification and Validation during the entire life of this contract to
monitor the development of any deliverable in the SDLC. The Contractor must develop an Independent
Verification and Validation Plan to address, at a minimum, communication protocol, methods of access, joint
operating procedures, specific tasks, schedules, organization, reporting, and responsibilities, and close out
procedures.
The Contractor must provide IV&V for all major SDLC reviews, audits, inspections, walkthroughs, and
tests, and must review and provide comments on all documentation. The contractor must also conduct
independent evaluations, reviews, and tests for any SDLC deliverable both processes and products.
The contractor must submit status reports and attend weekly meetings to discuss potential solutions and
resulting action items from IV&V inspections.
C.3.11 Business Process Engineering
Contractor must provide the capability to codify and map FAA Financial and Technical processes. The
contractor team may be required to gather information through a series of desk side information gathering
sessions. The contractor team must upon request develop a model of a current Financial and Technical
processes using federal information-processing standard modeling software. The contractor team must rely on
government representatives to provide definitions and descriptions of the FAA process to be re-engineered. The
contractor will incorporate improvement opportunities and develop a to-be model of the FAA financial and
technical business processes.
C.3.12 Special Projects; Other IT related requirements
Contractor must support other specific tasks, which may occur less regularly, include: provide assistance in
planning and performing data conversions to internet technologies; develop data conversion and/or validation
routines; develop special applications as needed or required; develop and maintain a continuous quality
improvement and assurance program; document requirements of existing or legacy applications currently in-
use; develop and manage a configuration management program for all supported applications; and collect
statistics to size applications and improve performance.
C.4 Contract Management
The contractor must efficiently and effectively manage the performance under this contract, to include all the
necessary technical, business, and administrative planning; organizing; managing; coordinating; tracking (e.g.,
cost, schedule, deliverables); performance management; risk management; resource management; data
management; and subcontract management required to perform all the activities successfully as required by the
contract and resulting delivery orders. The awarded offer or must ensure that all new projects (task orders that
are not operations and sustaining work in nature) are approved by the ABA Project Review Board prior to
14
approval of funding and the start of work. Contractor will report staff utilization across projects and operations
to help track earned value metrics and costs for projects and system operations.
The contractor’s key personnel identified must be the primary point of contact for work to be performed under
the resultant contract. The key personnel must keep both contracting officer and contracting officer’s technical
representative informed of any potential problems and make recommendations for solutions.
The contractor must ensure that assignments are completed in a thorough and timely manner and prepare
written documentation of accomplishments. The FAA/ABA requirements in performing this contract demand
that the contractor's accounting, technical, analytical, and administrative support and the level of expertise,
experience, and demonstrated performance of contractor personnel providing the services must be at the highest
level of providing quality support.
The contractor must provide sufficient personnel, both in number and qualification to perform work described
herein.
The contractor must provide an organizational chart that described the relationship between the contractor’s
proposed support organizations and contractor’s executive level management and must identify the executive
level sponsor within the awarded suppliers’ organization and its counterpart organizations in the FAA/ABA
(business units, COTR, Contracting Officer, etc). An escalation path for initial service level resolution must be
identified.
This organizational chart must identify any and all sub-contractors that may conduct work under this contract
and the escalation path for issue resolution. The supplier must update this chart and notify the FAA/ABA
when any significant change is made that is relevant to this award. This chart may be an attachment or
appendix to Volume 1 of the Technical proposal
All task order engagements must require a narrative and price proposal from the awarded supplier. The
FAA/ABA must provide a statement of work, objective or requirements in order to initiate any task order under
the awarded contract.
Awarded supplier must adhere to the ABA systems’ development lifecycle methodology or present an
acceptable alternative methodology to the Manager of ABA-20.
C.4.1. Project Kickoff
Within 15 calendar days of award, the supplier must host and sponsor a Contract Engagement / Kick-Off
meeting with the FAA/ABA contract and business stakeholders. This kick-off meeting will cover, at a
minimum:
Transition Plan
Project Management Plan
The supplier must provide a Program Management Plan (PMP) to guide the transition and implementation of
the new contract. The PMP must have at a minimum the following information:
Key Personnel – Roles and Responsibilities
Staffing
Responsibilities
Organizational chart
Escalation Plan
15
Quality Assurance Plan
C.4.2. Cost and Schedule Performance
Suppliers must maintain a project plan with tasks, milestones, resorting, and critical path for each delivery
order.
C.4.3. Project Schedule
The supplier must provide a project schedule that identifies project activities, aligned to the work break down
structure, project phases; start-and-finish dates; durations; and milestones for the transition. The project plan
must be delivered at the project kick-off meeting. Each task order must also require a project schedule unless
specifically exempted by the COTR.
C.4.4. Cost and Schedule Baseline Performance Reporting
Identify the Government's requirement for contractor reporting on adherence to cost and schedule baselines
(type and frequency of report).
C.4.5. Cost and Schedule Performance (Earned Value Management-EVM)
Any individual delivery order in excess of $10 million may be required to employ and report on the project
progress used earned value measurement techniques and tools. The supplier must be able to support the
implementation of reporting of EVM required task orders as required by the FAA/ABA.
C.4.6. Project Status Reports
Each delivery order under the base contract must identify the types of reports and frequency necessary to the
success of that delivery order.
If no reports are identified and unless otherwise specified, the suppliers must provide on a weekly basis task
accomplishments and planned tasks progress against plan; risks, and issues. The supplier must track burn rate
on all delivery orders and notify the COTR when the allocated funds are within 80% of total delivery order
funding. The supplier must not work or continue working without authorized funding.
C.5. Deliverables Quality and Acceptance Criteria
Deliverable acceptance criteria for each task order are, at a minimum, as described below:
– Accuracy: Deliverables are accurate in technical content and adhere to accepted elements of style.
– Clarity: Deliverables are clear and concise; engineering or software development terms are used as
appropriate; diagrams are easy to understand and relevant to the supporting narrative.
– Specification Validity: All deliverables satisfy the Government's requirements specified herein, including
performance metrics, where applicable.
– Completeness: Deliverables are submitted with all the required information. For software development, all
artifacts are complete as specified in the relevant software development framework document.
16
Appendix 1—Inventory of FAA/ABA ABA Financial systems
Cost Accounting System (CAS)
FAA Financial Warehouse
Labor Distribution and Reporting (LDR)
Payroll Analysis tool
Advanced Reporting System (ARS)
SAVES
FABS
Project Activity Dictionary (PAD)
PRISM (FAA Acquisition System)
Oracle® governance risk and compliance solution (GRC)
Capitalization Documentation System (PDL) Documentum
Other ABA systems currently under development
Appendix 2—FAA ABA Infrastructure - hardware and software
HP–UX 11i, HP Tru64 and Windows 2003
Documentum
Oracle Governance Risk and Control application.
Oracle Database 9i and 10g
Oracle Application Server 10g
Business Objects Enterprise XIr2
PeopleSoft Financials 8.9
Compusearch PRISM- release 6.5 and above
Foglight, Oracle Enterprise Manger and HP Systems Insight Manager
Other software may be required per future development
These software packages are run on a combination of Hewlett-Packard Itanium and HP Alpha server’s
environments as well as Dell blades servers and Sun Microsystems hardware running SPARC IV+ chips and
Solaris 10. These reporting systems all use a common software environment that consists of primarily the
following: Oracle 10g database software, HP-UX operating system, Solaris 10, Windows 2003, Linux,
Business Objects software and other software as required by ABA.
17
DRAFT
Appendix 3—IT Tools and Applications used to support the FAA ABA SDLC process
CA Clarity PPM Solution
Blueprint Requirements Center 2010
BMC Remedy
HP Quality Center and Quick Test Professional
Microsoft Sharepoint Server 2007
SQL Developer
Toad
CA Erwin
Subversion
Oracle Discoverer
HP Quality Center