Application_Development_Engineering_and_Sustainment_Draft_SOW.pdf

Applications Development, Engineering & Sustainment

STATEMENT OF WORK

OFFICE OF THE CHIEF INFROMATION

OFFICER

1 Cover Page

PROCUREMENT SENSITIVE TO NOT DISTRIBUTE

Contents 1 Cover Page ............................................................................................................................................. i

This Page Intentionally Left Blank ................................................................................................................. v

2 Introduction ...................................................................................................................................... - 1 -

2.1 Contract Model ......................................................................................................................... - 2 -

3 Scope and Purpose ............................................................................................................................ - 2 -

3.1 Scope ......................................................................................................................................... - 2 -

3.2 Architecture Engineering (AE) Support ..................................................................................... - 7 -

3.3 Database Engineering Support ................................................................................................. - 7 -

3.4 Information Technology Security Engineering and Support Services ....................................... - 9 -

3.5 Service Oriented Architecture (SOA) Engineering .................................................................. - 10 -

3.6 Site Services Systems Engineering .......................................................................................... - 11 -

3.7 Storage Area Network (SAN) Engineering............................................................................... - 11 -

3.8 Video Systems Engineering ..................................................................................................... - 12 -

3.9 Virtualization Engineering ....................................................................................................... - 13 -

3.10 Voice Systems Engineering ..................................................................................................... - 13 -

3.11 Wireless Domain Radio Engineering ....................................................................................... - 15 -

3.12 Wireless Domain Cellular Engineering .................................................................................... - 15 -

3.13 Wireless domain WiFi/WiMax/WLAN Engineering ................................................................. - 16 -

3.14 Satellite System Engineering ................................................................................................... - 17 -

3.15 Technical Writing and Editor Support Services ....................................................................... - 18 -

3.16 Purpose ................................................................................................................................... - 18 -

4 Requirements .................................................................................................................................. - 19 -

4.1 Global Requirements for Engineering, Applications Development, Integration and Sustainment Services ............................................................................................................................................... - 19 -

4.1.1 Application Portfolio ....................................................................................................... - 31 -

4.1.2 Application Platforms and Technical Environments ....................................................... - 32 -

4.2 Compliance with Appropriate Policies, Laws, and, Standards ................................................ - 34 -

4.3 Application Development Approaches ................................................................................... - 36 -

4.4 Architectural Control and Compliance .................................................................................... - 37 -

4.4.1 Enterprise Architecture ................................................................................................... - 37 -

4.4.2 Services Oriented Architecture (SOA) ............................................................................. - 38 -ii

4.4.3 Data Exchange Model ..................................................................................................... - 38 -

4.4.4 Industry Best Practices .................................................................................................... - 39 -

4.5 Innovation ............................................................................................................................... - 39 -

4.6 Information Systems security ................................................................................................. - 40 -

4.6.1 Security Review and Reporting ....................................................................................... - 40 -

4.6.2 System Certification and Accreditation .......................................................................... - 40 -

4.6.3 Information Security Policy Compliance ......................................................................... - 41 -

4.6.4 Interconnection Security agreements (ISAs) .................................................................. - 41 -

4.6.5 Security Requirements for Unclassified Information Technology Resources ................. - 41 -

5 Work Definitions ............................................................................................................................. - 43 -

5.1 Work packages ........................................................................................................................ - 43 -

5.2 Work orders ............................................................................................................................ - 43 -

5.2.1 Sustainment Support ...................................................................................................... - 44 -

5.2.2 Business Area Applications Development and integration ............................................. - 49 -

5.2.3 Exigency Applications Development, Engineering, and Integration ............................... - 50 -

5.2.4 Developmental Systems Engineering and Platform Services ......................................... - 51 -

5.3 Government Furnished Equipment / Facilities / Workspace .................................................. - 52 -

5.4 Place of Performance .............................................................................................................. - 52 -

6 Deliveries and Performance ............................................................................................................ - 54 -

6.1 EAGLE II Task Order ................................................................................................................. - 54 -

6.1.1 Task Order Term.............................................................................................................. - 54 -

6.1.2 Period of Performance .................................................................................................... - 54 -

6.1.3 Work Order Period of Performance ................................................................................ - 54 -

6.2 Fair Opportunity ...................................................................................................................... - 56 -

6.3 Order Process .......................................................................................................................... - 56 -

6.3.1 Issuing Work orders ........................................................................................................ - 56 -

6.3.2 Deliverables ..................................................................................................................... - 56 -

6.3.3 Contract Type of Work Orders ........................................................................................ - 56 -

6.3.4 Work Order Contents ...................................................................................................... - 57 -

6.4 Advertising of Award............................................................................................................... - 57 -

6.5 Avoidance of Personal Services .............................................................................................. - 57 -

6.5.1 Prohibition on Personal Services .................................................................................... - 57 -iii

6.5.2 Performance of Inherently Governmental Functions ..................................................... - 58 -

6.5.3 Government Rights ......................................................................................................... - 58 -

6.6 Release of Information............................................................................................................ - 58 -

6.7 Key Personnel.......................................................................................................................... - 58 -

6.7.1 Substitution of Key Personnel ......................................................................................... - 59 -

6.8 Interrelationship of Associate Contractors ............................................................................. - 60 -

7 Systems Inventory ........................................................................................................................... - 60 -

8 Invoicing (Based on Objective, CLIN) .............................................................................................. - 64 -

9 ADDITIONAL PROVISIONS/TERMS AND CONDITIONS .................................................................... - 64 -

3052.204-71 CONTRACTOR EMPLOYEE ACCESS (JUN 2006) ALTERNATE I (JUN 2006) ...................... - 68 -

3052.209-72 ORGANIZATIONAL CONFLICT OF INTEREST (JUN 2006) ................................................ - 71 -

3052.237-70 QUALIFICATIONS OF CONTRACTOR EMPLOYEES (DEC 2003) ........................................ - 74 -

3052.237-72 CONTRACTOR PERSONNEL SCREENING FOR UNCLASSIFIED INFORMATION TECHNOLOGY ACCESS (DEC 2003) ............................................................................................................................. - 75 -

3052.242-72 CONTRACTING OFFICER'S TECHNICAL REPRESENTATIVE (DEC 2003) ........................... - 77 -iv

This Page Intentionally Left Blank v

2 Introduction

The Federal Emergency Management Agency (FEMA) Office of the Chief Information Office embarked on a mission to enhance and maintain information technology infrastructure;

develop and enhance key systems to support operating programs; and increase efficiencies and cooperation across FEMAs divisional and regional lines. They did this by establishing the

Enterprise Applications Development Integration and Sustainment (EADIS) Task Order under the Department of Homeland Security’s Enterprise Acquisition Gateway for Leading Edge

Solutions (EAGLE) contract. In addition to accomplishing the mission the EADIS team, a combination of OCIO federal employees and the IBM contractors, established a baseline support model and developed the future Information Technology Service Oriented Architecture

(SOA) modernization roadmap.

The OCIO Roadmap serves as a guide for FEMA’s modernization initiatives that increase agility, remove silos and duplicative functionality, implement best practices, and implement reference architecture for future application development. It is segmented by major functional domains, seeking to re-engineer aging legacy systems to modern designs, eliminate outdated technology, extract and expose functionality through services, and reduce co-dependency among systems.

At the same time, a cross-domain thread exists to eliminate silos of function, leverage Service

Oriented Architecture, break apart data structures that create co-dependency, and build a future state architecture that is agile.

The current FEMA information technology environment is a combination virtualized and standalone servers. There is an aggressive effort to virtualize all of the enterprise servers to include the various flavors of UNIX and Windows operating system. FEMA endeavors to continue to convert legacy code (old Power Builder) to more supportable languages and collapse the server footprint to a more manageable virtual model.

These systems represent a broad spectrum of highly effective to ineffective alignment to the

DHS/FEMA mission and technology goals and objectives. Some systems meet the mission as

- 1 -prescribed, others are in critical need of replacement due to the limits of the technology, others are implemented with newer technology but do not meet the mission at an enterprise level, and some organizational processes are not yet fully automated. This task order must continue to provide enterprise level solutions, solutions to support a particular business need and solutions that are necessary to support the immediate needs in support of the emergency management and disaster operations of FEMA.

Section 3 of this document defines the full scope of this Task Order.

2.1 Contract Model

FEMA intends to conduct a full and open competition to award a single Indefinite

Delivery/Indefinite Quantity (IDIQ) type contract.

3 Scope and Purpose

3.1 Scope

The scope of this effort includes all aspects of Enterprise Engineering, Applications

Development, Integration, Sustainment Services, and associated infrastructure support to include documentation by a single integrator. The migration to the target architecture shall continue under this effort unless formally changed by a contract modification. The OCIO mission includes supporting the Clinger-Cohen requirements and to provide applications development and support for all of FEMA’s unclassified systems and centralized platform services. Therefore, the scope of this effort encompasses the full range of Engineering, Applications Development, Integration, Sustainment Services and associated development infrastructure services. Specifically, this effort includes, but is not limited to, use of various development approaches for mission need determination; requirements analysis; and application design, development, engineering, testing, and implementation; support of non-production environments; application development organizational consulting and related business process reengineering; configuration management and release management; and related project management as well as COTS and GOTS implementation, systems integration,

- 2 -performance and availability analysis and improvement, implementing contingency planning and execution capabilities.

The offeror receiving the award will be expected to maintain a Government Owned Contractor

Operated (GOCO) development\engineering environment to supporting any developmental effort authorized in Work Packages within this task order to include support within a classified environment. The GOCO development environment includes license and maintenance of all tools and services.

This task orders shall include:

1. Enterprise Engineering, Applications Development, Integration, Sustainment Services, with associated infrastructure support to include documentation – these services are consolidated under a single integrator to ensure consistency and uniformity in applying the DHS Systems Development Life Cycle (SDLC) and applicable federal standards.

2. The contractor shall provide highly specialized Systems Engineering, Application

Development, and Project Management expertise to support the FEMA mission that includes, but is not limited to geographically separate locations and DHS approved Data

Centers. This support may include, but is not limited to, the following:

o Expertise and support for planning, analysis, design, development, testing, integration, and installation activities o Development and review of operational and technical systems specifications and requirements o Design of infrastructure, applications and configurations in a multi-tier network environment including high availability (HA), disaster recovery (DR) and high volume (HV) environments o Development and maintenance of system architecture models o Conduct studies and analyses o Analyze engineering plans o Prepare technical documentation on engineering issues

- 3 -o Review system and technical specifications o Provide well-founded technical opinions on current or proposed engineering issues o Conduct operational planning for engineering activities o Review engineering practices, standards, and processes o Provide firewall design recommendations in a HA and HV database architecture with Oracle RAC clusters and Microsoft SQL Clusters o Support rapid prototyping o Provide engineering support to demonstrate, assess, and implement new system and technologies o Additional types of architecture engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances

3. Due to the criticality and wide variety of IT projects, the contractor shall possess the ability to provide knowledgeable and experienced technical resources to support multiple concurrent projects.

4. The contractor shall provide services in the form of engineering advice and direct technical assistance essential to the research, design, development, integration, implementation, evaluation, and testing of IT solutions necessary to ensure the effective operation and maintenance of complex IT networks and systems for FEMA organizations and mission activities. Services generally include information technology consulting services, such as: infrastructure engineering support, architecture design, and database engineering and management. Systems engineering includes a combination determining requirements and specifications, performing planning, conducting analysis, developing designs, conducting testing, integration, and installation and technical services include technical program management support, development of requirements and work statements, technical strategy development, supporting strategy and governance activities and resolving technical controversies.

- 4 -

5. The contractor shall provide classified and unclassified information technology systems engineering and technical assistance support services to FEMA. Additionally, the Contractor shall assure that engineering and technical assistance support activities are collaboratively integrated with other FEMA IT contracts as defined in the individual Task Orders.

6. Independent Technical Assistance and Program Enterprise Services (ITAPES) – to identify gaps in services across the agency programs and examine alternative solutions for implementing resolution of those gaps; to provide high quality systems engineering and technical assistance expertise; to support government managers in the management oversight and direction of services provided to our customers; and to support the integration of services across programs. Contractors participating in this area will be prohibited from participation in other areas due to obvious conflicts of interest.

7. Sustainment – to provide a reliable, stable, and secure operating environment that is aligned with the DHS enterprise infrastructure and supported by service level agreements with supported customers; this includes the support of operating environments and providing oversight and direction for managed services support.

8. Policy Support – to provide direct support to the Office of the CIO in setting, and monitoring, and enforcing agency IT policies; assists in management of budgeting and planning functions; addressing CIO reporting requirements; and to support the enterprise architecture. Contractors participating in this area will be prohibited from participation in other areas.

9. Quality Assurance – to provide an independent capability to ensure compliance with program requirements; ensures the delivery of quality products through effective testing and validation; to ensure compliance with Certification and Accreditation requirements; to provide Cyber Security and FISMA; and to manage the agency’s

Configuration Management and Release Management process.

10. Documentation – to provide complete systems documentation, to include updates based on Change Requests (CR), new development, and break fixes.

Pursuant to this modernization, the CIO’s vision, and the Agency’s mission, this task order is intended provide a single developer and applications integrator for all applications developed in

- 5 -response to FEMA missions. A primary goal of this overarching effort is to support both the support the development and integration of new and modernized applications while supporting the sustainment of existing technology, services and applications. This modernization is also occurring within the scope of the larger modernization efforts of the Department of Homeland

Security.

FEMA’s goal is to continue to create, through innovation, a transformed organization where IT services are delivered through state-of-the-art, service-enabled applications to:

• Stabilize and integrate Information Technology assess across the Agency

• Provide “cradle to grave” emergency management support including but not limited to preparedness, training, mitigation, response, and recovery

• Protect the emergency management infrastructure and information assets against loss or compromise

• Enhance the Homeland Security information infrastructure through sharing mission-critical information where and when it is needed, regardless of organizational boundary

• Effectively leverage existing information assets to address emerging mission requirements quickly

• Propel FEMA Software Application development, integration, implementation, and operations forward to Capability Maturity Model Level 3 and/or Capability Maturity

Model Integrated Level 3 as defined by the Software Engineering Institute.

• Support the effective analysis, assessment and selection of appropriate solutions, products and technologies to support the enterprise

• Optimize return on all IT applications expenditures

• Implement proper project management practices and reporting procedures in adherence to established best practices (e.g., Project Management Body of

Knowledge (PMBOK ))

- 6 -

The Government’s desired outcome is to transform the FEMA organization so that resources are optimized and the mission is more efficiently and effectively accomplished.

3.2 Architecture Engineering (AE) Support

The Contractor shall provide architectural engineering to technically evolving environments that include, but are not limited to geographically separate locations and DHS Data Centers.

This support may include, but is not limited to, the following:

• Expertise and support for planning, analysis, design, development, testing, integration, and installation activities

• Development and review of operational and technical systems specifications and requirements

• Design of infrastructure, applications and configurations in a multi-tier network environment including high availability (HA), disaster recovery (DR) and high volume (HV) environments

• Development and maintenance of system architecture models

• Conduct studies and analyses

• Analyze engineering plans

• Prepare technical documentation on engineering issues

• Review system and technical specifications

• Provide well-founded technical opinions on current or proposed engineering issues

• Conduct operational planning for engineering activities

• Review engineering practices, standards, and processes

• Provide firewall design recommendations in a HA and HV database architecture with

Oracle RAC clusters and Microsoft SQL Clusters

• Support rapid prototyping

• Provide engineering support to demonstrate, assess, and implement new system and technologies.

• Additional types of architecture engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances.

3.3 Database Engineering Support

The Contractor shall provide database engineering and database administration support to a large and complex enterprise class and application level database environments. This support may include, but is not limited to, the following:

• Evaluation of database software and hardware solutions

- 7 -

• Technical configuration of database software

• Database planning and modeling

• Design and tuning of Online Transaction Processing (OLTP) and On-Line Analytical

Processing (OLAP), and Extract, Transform and Load (ETL) environments and solutions

• Data warehouse and data mart design and engineering

• Design and implementation of database backup and recovery strategies

• Design and implementation of data access controls and security configurations

• Database design (logical and physical)

• Database tuning

• Database systems maintenance (patches, performance, memory management, and configuration parameters management)

• Support for engineering upgrades of database software

• Testing support deployments

• Performing performance and data use analysis

• Evaluation and testing of new system features.

• FEMA ITD engineering and operations currently uses various database tools such as Data

Pump or Query Analyzer, monitoring of the database and underling file systems, deployment and maintenance of Oracle Streams, as well as third party replication applications that run in the database environment such as Quest SharePlex data replication tools, advanced replication maintenance, unit testing, load testing, user acceptance testing, maintaining the security of the database, and ensuring that the database conforms to DHS security guidelines.

• The current FEMA database environment includes both Microsoft SQL Server and Oracle database environments. Various versions of each of these platforms are currently in use.

These environments are currently hosted are various geographically separate locations.

In the near future, systems will also be hosted at DHS Data Centers. Additional types of database engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances.

- 8 -

3.4 Information Technology Security Engineering and Support Services The Contractor shall provide IT security engineering advice and direct technical assistance in support of the FEMA enterprise environments. This support may include, but is not limited to, the following:

• Technical analysis and engineering support for security systems and network design

• Functional requirement gathering, analysis, and documentation

• Support for IT security system & network design

• Support for IT security system implementation and integration

• Performance of security system acceptance testing

• Research and analysis of emerging IT security technology

• Development of migration plans to aid incorporation of new technologies

• Development of standards and creation of concepts to meet future standards

• Engineering design and implementation of network security technologies, including but not limited to:

o Network and personal firewalls o Virtual Private Networks (VPN) o Intrusion Detection Systems (IDS) o Anomaly detection systems o Network Admission Control (NAC) o Routing protocols o Endpoint security technologies o Wireless security o IP telephony security o IPv6 security o System and network monitoring o Management of embedded devices o Digital certificates and PKI

The Contractor shall provide expertise for Tier 3 level (engineering level) support of security and security support systems in the FEMA Enterprise.

The Contractor shall support IT Security Certification Agents, Standards, Test, and Evaluations (ST&E); IT Security Validation Testing; Encryption and PKI Certificates; Contingency Planning;

Policy Development; Product Evaluation; Risk Management Services; Security Architecture Services; Testing; Training; Surge Support; and Transition Activities.

- 9 -

Additional types of security engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances.

3.5 Service Oriented Architecture (SOA) Engineering

The Contractor shall provide SOA engineering advice and direct technical assistance in support of the FEMA enterprise environments. This support may include, but is not limited to, the following:

• Technical analysis and engineering support for SOA systems design

• Expertise to support the review and development of operational and technical systems specifications / requirements

• Development and maintenance of system architecture models

• Studies and analyses

• Analysis of engineering plans

• Preparation of technical documentation on engineering issues

• Review of specifications

• Development of technical opinions on current and / or proposed engineering efforts

• Operational planning for engineering activities:

o Review of engineering practices, standards, and processes

• Engineering and technical assistance in the implementation of SOA standards and technology, including but not limited to:

o Business Process Execution Language (BPEL) o Simple Object Access Protocol (SOAP) o Enterprise Service Bus (ESB) o Interface Control Documents (ICDs) o Web Services Inspection Language (WSIL) o Web Service Definition Language (WSDL) o Oracle Web Services Manager (OWSM) o Oracle Internet Directory (OID) o Service Registry o Metadata Repository o Support for system & network design engineering (utilizing Computer Aided

Design), network topological design tools, and operating design tools o Support rapid prototyping and provide engineering support to demonstrate, assess, and implement new system and SOA technologies o The Contractor shall provide expertise for Tier 3 level (engineering level) support of SOA and SOA support systems in the FEMA Enterprise.

- 10 -o Additional types of SOA engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances.

3.6 Site Services Systems Engineering

The Contractor shall provide site services systems engineering advice and direct technical assistance in support of the FEMA enterprise environments. This support may include, but is not limited to, the following:

• Technical analysis and engineering support for site support systems

• Functional requirement gathering, analysis, and documentation

• Support for cable infrastructure system & transport network design

• Site services system implementation and integration

• System acceptance testing

• System maintenance and technical support

• Research of emerging site services technology trends

• Development of migration plans to aid incorporation of emerging technology

• Development of standards and creation of concepts to meet future standards

• Engineering and support to all areas of FEMA’s enterprise voice, video, and data networks.

The Contractor shall provide expertise for Tier 3 level (engineering level) support of site and site support systems in the FEMA Enterprise.

Additional types of site systems engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances.

3.7 Storage Area Network (SAN) Engineering

The Contractor shall provide SAN engineering advice and direct technical assistance in support of the FEMA enterprise environments. This support may include, but is not limited to, the following:

• Technical analysis and engineering support for SAN systems design

• Engineering, design, deployment and management duties for the switched fabrics

• Support for the creation of Logical Devices (LDEVs) and meta devices

• Support for the mapping of LDEVs and meta devices to the appropriate Fiber

Attachments (FAs)

• Support for the masking devices to the appropriate World Wide Names (WWNs)

• Development of weekly reports detailing SAN utilization and performance

- 11 -

• Development of periodic reports regarding LDEV utilization and performance

• Migration of legacy SANs to FEMA standard SANs

• Diagnosis and resolution of performance issues

• Capacity planning and capacity expansion

• Engineering support for the addition of new servers and clusters to the fabric

• Evaluation and support to ensure interoperability

• Creation of support cases with SAN vendors to resolve issues, questions, and hardware failures.

The Contractor shall provide expertise for Tier 3 level (engineering level) support of SAN and SAN support systems in the FEMA Enterprise.

Additional types of SAN systems engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances.

3.8 Video Systems Engineering

The Contractor shall provide video system engineering advice and direct technical assistance in support of the FEMA enterprise environments. This support may include, but is not limited to, the following:

• Engineering advice and direct technical assistance necessary to ensure the effective design, operation, and maintenance of FEMA audio, visual and video teleconference systems

• Support all facets of planning, analysis, design, development, testing, integration, and installation associated with large-scale video teleconferencing systems, conference rooms, emergency operations centers and web delivery video systems.

• Technical assistance and expertise to support functional requirement gathering, analysis, and documentation; video system & network design; video system implementation and integration

• Support of system acceptance testing

• Research of emerging video technology trends

• Development of migration plans to aid incorporation of emerging technology

• Development of standards and creation of concepts to meet future standards

• Analysis of hardware and software interoperability (including protocols, network management and multimedia applications) across conventional networks, hybrid fiber-coaxial transmission networks, IP video, other next generation internet-based networks, and unified communications technologies and approaches.

- 12 -

• Engineering support services to all areas of FEMA’s audio, visual and video teleconference systems and networks, analog and digital streaming motion imagery, standards-based video teleconference systems

• Support in the diagnosis of video signals and the throughput signatures of video streams; technical video support

• Support for security implementation, telephone conferencing systems, video controllers, audio/video switching systems and complex wall display systems.

The Contractor shall provide expertise for Tier 3 level (engineering level) support of video and video support systems in the FEMA Enterprise.

Additional types of video systems engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances.

3.9 Virtualization Engineering

The Contractor shall provide virtualization engineering advice and direct technical assistance in support of the FEMA enterprise environments. This support may include, but is not limited to, the following:

• Engineering support all facets of planning, analysis, design, development, testing and integration of system and application virtualization

• Support for the design, installation, configuration, patching, support and management of the physical hosts operating system daemons and virtualization software, virtualization management center, and licensing server, configuration and management of virtual machines, templates and clones, host environment backups, virtual network administration, and load testing of virtual machines.

The Contractor shall provide expertise for Tier 3 level (engineering level) support of virtualization and virtualization support systems in the FEMA Enterprise.

Additional types of virtualization systems engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances.

3.10 Voice Systems Engineering

The Contractor shall provide expertise and engineering assistance to FEMA voice system and enterprise network environment. This support may include, but is not limited to, the following:

- 13 -

• Voice systems planning, analysis, design, development, testing, integration, and installation associated with a nationwide voice network

• Voice system & network design engineering using engineering Computer Aided Design;

hardware development

• Network control / communications center operations

• Simulation and modeling in support of voice systems design and analysis

• Voice network capacity planning

• Development of specifications and standards

• Evaluation of new technologies and device interoperability evaluation

• Support for the engineering and implementation of fiber optic network technologies

• Analysis of hardware and software interoperability (including protocols, network management and multimedia applications)

• Engineering and support across conventional networks, hybrid fiber-coaxial transmission networks, Integrated Services Digital Networks (ISDN), Asynchronous Transfer Mode (ATM), current (IPv4/IPv6), VoIP/IP telephony; IP video, other next generation internet-based networks and unified communications technologies and approaches.

• Review and development of operational and technical systems specifications / requirements

• Development and maintenance of system architecture models

• Analysis of engineering plans

• Preparation of technical documentation on engineering issues

The Contractor shall possess the knowledge and skill to provide engineering support services to all areas of FEMA’s voice systems and networks including: voice mail technologies; Automatic Call Distribution (ACD); Interactive Voice Response (IVR); Intelligent Call Management (ICM);

network level routing; Private Branch Exchange (PBX) implementation, integrations, and administration; out-bound dialing systems; interpretation and adherence to standards and specifications related to voice/data telecommunications systems including physical, electrical, procedural, performance communications protocols such as ISDN, Digital Telephony, and Voice over (VoIP), H323, SIP, 802.3/802.3F, 802.5 standards; and high availability and redundancy of critical system resources including recovery activities in the event of component failure, machine failure or larger disaster situations.

The Contractor shall provide expertise for Tier 3 level (engineering level) support of all voice systems in the FEMA Enterprise.

Additional types of voice engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances.

- 14 -

3.11 Wireless Domain Radio Engineering

The Contractor shall provide expertise and engineering assistance to FEMA IT Wireless Domain.

This support may include, but is not limited to, the following:

• Provide radio system engineering advice and technical assistance in support of the FEMA Enterprise Radio Network and disaster radio network environments

• Engineering and technical assistance in the implementation of radio systems solutions, including but not limited to:

• Land mobile radio systems (LMR) and components

• Radio cross banding

• Repeater networks

• Radio over IP (ROIP) technology

• Frequency propagation and management

• Ad hoc radio networks

• RF products (amplifiers, filters, duplexers, phase shifters, repeaters, feed line, surge protection, and antennas)

• Radio test equipment (spectrum analyzers, noise figure meters, etc.).

• Support of functional requirement gathering, analysis, and documentation

• Engineering of radio systems & networking design

• Radio system implementation and integration

• Support of radio system acceptance testing

• Support of radio system maintenance and technical support

• Research of emerging radio technology trends

• Development of migration plans to aid incorporation of emerging technology

• Development of standards and creation of concepts to meet future standards

The Contractor shall provide expertise for Tier 3 level (engineering level) support of all radio systems in the FEMA Enterprise.

Additional types of radio engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances.

3.12 Wireless Domain Cellular Engineering

The Contractor shall provide expertise and engineering assistance to FEMA IT Wireless Domain.

This support may include, but is not limited to, the following:

• Provide cellular engineering advice and direct technical assistance in support of the FEMA Enterprise cellular network environments

- 15 -

• Engineering and technical assistance in the implementation of wireless cellular solutions including but not limited to:

• Point-to-point microwave

• Wireless cellular networks

• Indoor cellular amplifier technologies

• RF products (amplifiers, filters, repeaters, feed line, surge protection, and antennas)

• Wireless test equipment (spectrum analyzers, noise figure meters, etc.).

• Support of functional requirement gathering, analysis, and documentation

• Engineering of cellular system solutions & networking design

• Support of system acceptance testing

• Support of system maintenance and technical support

• Development of migration plans to aid incorporation of emerging technology

• Development of standards and creation of concepts to meet future standards

The Contractor shall provide expertise for Tier 3 level (engineering level) support of all cellular solutions in the FEMA Enterprise.

Additional types of cellular engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances.

3.13 Wireless domain WiFi/WiMax/WLAN Engineering

The Contractor shall provide expertise and engineering assistance to FEMA IT Wireless Domain. This support may include, but is not limited to, the following:

• Provide wireless system engineering advice and technical assistance in support of the FEMA Enterprise and disaster response network environments

• Engineering and technical assistance in the implementation of wireless systems solutions, including but not limited to:

o Access Points, controllers and wireless LAN (WLAN) security systems o Ad hoc wireless Local Area Network (LAN) networks o WiFi technology and trends o Mesh and point-to-point networks o Wireless bridge technologies o Wireless security technologies o Wireless local area radio networks (ROIP) o RF products (amplifiers, POE, Ethernet cable standards, feed line, surge protection, and antennas)

- 16 -o Wireless test equipment (spectrum analyzers, TDR, Ethernet testers, etc.).

• Engineering of wireless LAN system solutions and network designs

• Support of functional requirement gathering, analysis, and documentation

• Engineering of wireless systems & networking design

• Wireless system implementation and integration

• Support of wireless system acceptance testing

• Support of wireless system maintenance and technical support

• Research of emerging wireless technology trends

• Development of migration plans to aid incorporation of emerging technology

• Development of standards and creation of concepts to meet future standards

The Contractor shall provide expertise for Tier 3 level (engineering level) support of all wireless systems in the FEMA Enterprise.

Additional types of wireless engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances.

3.14 Satellite System Engineering

The Contractor shall provide expertise and engineering assistance to FEMA IT Wireless Domain.

This support may include, but is not limited to, the following:

• Provide system engineering advice and direct technical assistance in support of the FEMA Enterprise Network and satellite network environments

• Engineering and technical assistance in the implementation of wireless and satellite solutions, including but not limited to:

o GAN, BGAN, M4, AMSAT satellite systems and components o Fixed Inmarsat satellite earth stations o Fixed, deployable and mobile Inmarsat satellite systems o Globlestar and Iridium satellite phones o Ku and Ka satellite system components o Satellite teleports o Fixed and deployable satellite systems o Low-earth-orbit (LEO) and geostationary satellite systems o TDMA and SCPC technologies o Very small aperture terminals (VSAT) o Wireless LAN interface solutions o Ad hoc satellite system networks o Point-to-point and mesh satellite networks

- 17 -o RF products (amplifiers, filters, duplexers, phase shifters, repeaters, feed line, surge protection, and antennas) o Wireless test equipment (spectrum analyzers, noise figure meters, etc.).

o Inmarsat

• Support of functional requirement gathering, analysis, and documentation

• Engineering of satellite system & network design

• Satellite system implementation and integration

• Support of system acceptance testing

• Support of system maintenance and technical support

• Research of emerging satellite technology trends

• Development of migration plans to aid incorporation of emerging technology

• Development of standards and creation of concepts to meet future standards

The Contractor shall provide expertise for Tier 3 level (engineering level) support of all satellite systems in the FEMA Enterprise.

Additional types of satellite engineering and support activities may be defined and required in the future to support changes to the Agency mission, implementation of technology improvements and other circumstances.

3.15 Technical Writing and Editor Support Services

The Contractor shall provide technical writing and editing support to produce, review, and edit highly complex written, graphical technical materials and web content, including system configuration, documentation, studies, reports and other presentation graphics.

The Contractor shall ensure compliance with DHS and FEMA standards, styles and formats, proper usage of English syntax, and overall structure and organization of material. Contractor must be proficient with Microsoft Office suite of applications and Microsoft Project software.

3.16 Purpose

The purpose of this acquisition is to procure Engineering, Applications Development, Integration, Sustainment Services, and associated infrastructure support to include documentation (code, configuration, deployment instructions, and manuals). The desired and necessary outcome is to identify a highly qualified and capable Contractor team who:

• Understands a variety of application development approaches as described herein.

• Can apply those various approaches to different scenarios, as described by a unique set of work packages, each containing unique requirements, desired behaviors, required labor categories, and relevant skill sets.

- 18 -

• Demonstrates understanding, knowledge, willingness, and ability to accomplish the evolution of applications pursuant to the FEMA CIO’s vision and efforts to create an agile enterprise that is responsive to the dynamic mission requirements facing FEMA.

• Demonstrates that they can embrace a series of diverse architectures within which work is currently accomplished, and help drive toward those strategic capabilities that FEMA must create.

• Can accelerate the forward motion to build and employ an effective, practical, and usable service-oriented architecture.

• Can smoothly migrate the legacy applications to a modernized architecture while effectively servicing our current customers who depend upon legacy applications that must continue to exist, and be reliable and responsive until migrated to the evolving web-based service-oriented architecture environment.

4 Requirements

4.1 Global Requirements for Engineering, Applications Development, Integration and Sustainment Services

FEMA’s requirements for Enterprise Engineering, Applications Development, Integration, Sustainment Services, and associated infrastructure support span a wide range of development, engineering, and support requirements and cut across the entire FEMA organization and its partners in emergency management at the federal, state, and local levels.

Figure 1 defines the collective “superset” of all known functional requirements that will be used to create future Work Packages. EEADIS services will be organized by FEMA business areas with

Information Technology integration across business areas to meet the spirit and intent of the

Clinger-Cohen Act, OMB Circular A130, and the other mandates identified in Attachment 3. The sponsors include the FEMA Directorates, FEMA Offices, FEMA Divisions, Regional Offices, Joint

Field Offices, Territorial Recovery Offices, and FEMA Partners in Emergency management, including those non-government entities who work closely with FEMA in emergency, response, preparedness, and mitigation situations. The stakeholders and users include state and local

- 19 -government, non-government entities engaged in emergency management and the general public that access FEMA information technology to apply for assistance, request services, and obtain emergency management information.

The services provided by this task order are provided to the organizational business areas and serviced by the OCIO under service agreements with the various FEMA Program Offices. Some

Program Offices may utilize the EEADIS services directly via Work Packages on the EEADIS Task

Order coordinated through the OCIO.

OCIO maintains a significant set of enterprise applications and…