FEMA_IT_Industry_Day_Final_141205.pdf

Federal Emergency Management Agency

Information Technology Industry Day

December 5, 2014

Welcome & Opening Remarks

Mr. Bobby J. McCane Director, Acquisition Operations Division

Office of the Chief Procurement Officer Federal Emergency Management Agency

Department of Homeland Security

Time Topic Presenter

0800-0900 Check-In Registration

0900-0910 Welcome and Opening Remarks

Mr. Bobby J. McCane, FEMA Director of Acquisition Operations Division

0910-0915 Introduction Mr. Joseph Nimmich, FEMA Deputy Administrator

Mr. Bobby J. McCane, FEMA Director of Acquisition Operations Division

0915-0920 FEMA Leadership Intent Mr. Joseph L. Nimmich, FEMA Deputy Administrator

0920-1015 FEMA Information Technology Vision and Overarching Strategy

Mr. Adrian R. Gardner, FEMA Chief Information Officer

1015-1030 Acquisition Strategy and Guidelines Mr. David A. Grant, FEMA Chief Procurement Officer

1030-1500 Acquisition and Subject Matter Expert (SME) Breakout Sessions

FEMA SMEs and Contracting Officers

AGENDA

Important Information o Remarks today from Government Officials should not be considered a guarantee of the Government’s course of action for obtaining Information Technology (IT) services or products.

o The information provided to date is notional and reflects current Government intentions of how FEMA’s IT acquisitions should be carried out, and is subject to change based on a variety of circumstances, including input from industry.

o A solicitation is the only document that is relied upon in determining the Government’s requirements.

Notional and Subject to Change o All information that will be discussed or presented today, to include the documentation posted on Federal Business Opportunities, are notional and subject to change.

o Attending the FEMA Technology Industry Day does not guarantee a contract award.

o You may submit questions after this event to:

FEMA-Industry@fema.dhs.gov, listing your name, your company’s name, and identifying the relevant line of business.

mailto:FEMA-Industry@fema.dhs.gov o Be respectful of your peers as you visit each line of business.

o Be inquisitive and ask any questions necessary that will give you an understanding of FEMA’s requirements.

o Feel comfortable and engage with the Subject Matter Experts.

o Expect questions and answers to be posted for all to see.

o When asking a question during our breakout sessions, please provide your name, your company name, and limit your questions to two initially.

o Your engagement with FEMA personnel will not be confidential.

o If there is an emergency while in the Ronald Reagan building, the staff/security will make an announcement providing instructions on where, when, and how to respond appropriately to the situation.

Objectives for Today’s Event o Call to action for the delivery of “survivor-centric” technology solutions and capabilities that advance FEMA’s mission.

o Inform industry on FEMA’s vision and strategy for procuring Information Technology Services and Products.

o Promote networking among potential industry participants.

o Initiate and engage with FEMA’s industry partners.

FEMA Leadership Intent

Mr. Joseph L. Nimmich Deputy Administrator

FEMA’s Mission is to support our citizens and first responders to ensure that as a nation we work together to build, sustain, and improve our capability to prepare for, protect against, respond to, recover from, and mitigate all hazards Ethos to serve the Nation by helping its people and first responders, especially when they are most in need Core Values: Compassion, Fairness, Integrity, and Respect

Information Technology Vision and

Overarching Strategy

Mr. Adrian R. Gardner Chief Information Officer

Our goal is to reorient FEMA’s IT Ecosystems so they are “survivor-centric,” ensuring they support the delivery of services focused on easing the experience of survivors

Where are we?

FEMA’s Mission is to support our citizens and first responders to ensure that as a nation we work together to build, sustain, and improve our capability to prepare for, protect against, respond to, recover from, and mitigate all hazards Ethos to serve the Nation by helping its people and first responders, especially when they are most in need Core Values: Compassion, Fairness, Integrity, and Respect

2014-2018 FEMA Strategic Plan advances the Agency’s mission to support our citizens and first responders through 5 Strategic Priorities and 16 Outcomes

“FEMA, however, is just one part of the Nation’s emergency management team. We will be successful only if we build, sustain, and draw upon the capabilities of the whole community. I look forward to working with partners throughout Federal, state, and local governments; tribal governments; the private sector; faith-based and non-profit communities; and citizens across our country to bring about the outcomes set forth in this Plan."

W. Craig Fugate FEMA Administrator

FEMA CIO Intent FY2015-FY2020:

• We realize that data, information, and IT are foundational to advancing FEMA’s all hazard mission.

• To advance FEMA’s mission, it is paramount that we securely, effectively, and efficiently manage our data and information resources.

• We anticipate that we will encounter several technological, policy, workforce, and economic challenges that will impact our ability to support survivors and first responders. We will embrace these challenges through a “unity of effort” mindset and improve our capability to deliver information solutions by understanding survivor and first responder needs, preferences, and behaviors.

• We will ensure the availability of and access to information that enables survivors and first responders to make timely and informed decisions by strengthening corporate data and information management approaches.

• The CIO will serve as the Technical Authority for information technology. Working with all FEMA components, the CIO will provide the architectures, requirements, interfaces, technical standards, tools, and systems engineering and integration processes that are in conformance with applicable and relevant laws, requirements, and policies and will drive effectiveness and efficiency into our IT development and acquisition processes across

FEMA.

17 Notional and Subject to Change

FEMA CIO Vision:

Reorient FEMA’s IT Ecosystems so that they are “survivor-centric,” ensuring they support the delivery of services focused on easing the experience of survivors

FEMA CIO Mission:

Deliver a secure and agile information ecosystem that emphasizes speed, agility, data driven decision-making, and the capability to responded effectively to meet the needs of survivors and first responders in their greatest time of need

Target Outcome – Multiple Awards

i. To award contracts that shall be used to:

Manage FEMA’S portfolio of IT projects

Capture Customer Systems Requirements

Develop and Engineer Solutions based on sound requirements

Provide Independent Validation & Verification (IV&V)

Provide Operations Maintenance (O&M) and Support Services

Provide Cyber Security Services

Hardware Blanket Purchase Agreements (BPAs)

ii. Create a formal management structure that includes financial oversight, a formal program and project management structure that governs all contracted support activities and services.

iii. Define a set of clear and distinct characteristics for each contract.

Program Management Oversight (PMO)

In-Scope Exploit economies of scale and to reduce coordination costs and risks. The individual project manager's job is to ensure that their project succeeds. The program manager’s job is to focus on the aggregate result or end-state.

Can use this oversight to support project-level activity to ensure the overall program goals are likely to be met

Providing a decision-making capacity that cannot be achieved at project level or by providing the Project Manager with a program perspective when required

Identify and manage cross-project dependencies

Out-of-Scope The activities performed by individual Project Managers.

In-Scope Requirements gathering for all Systems (Mission and Business) development projects based on industry standard methodologies Ensure that system requirements meet the existing and future IT architecture Create a baseline of testable requirements that match the customer needs and are suitable for the design of the current FEMA infrastructure Development of traceability matrices Ensure that the requirements conform to federal standards such as NIST, FISMA, DHS SELC, and other FEMA Directives Logical Follow On

Out-of-Scope Applications Development and Engineering (No Coding) Implementation of MS BackOffice Applications, Network Testing, &

Monitoring Tools All Operations and Maintenance (O&M) Activities

MISSION NEEDS AND REQUIREMENTS

All Systems/Applications Development Engineering, Integration, and Sustainment activities.

Implementation of Commercial Off-the-Shelf (COTS) solutions.

Systems Integration Testing (SIT).

Project Management Activities Out-of-Scope Operations and Maintenance (O&M) activities Independent Validation & Verification (IV&V) activities.

Applications Development, Engineering & Sustainment

• Functional Qualification Testing, User Acceptance Testing

• Quality Assurance Policy and Governance support

• IV & V Process Development

• Project IV&V support

• Enterprise and Project Configuration Management support

• System Engineering Life Cycle support

• IV&V of the work products produced by the developer based on the documented customer requirements.

Out-of-Scope

• Application Development

• Developer specific IV&V/QA functions

Quality Assurance, Independent Verification and Validation (IV&V)

Network Operations (LAN, MAN, WAN) Configuration, Components, Monitoring & Access Control Internet\Intranet Access & Support Desktop Applications Management and Delivery Communications Security (COMSEC) Continuity of Operations (COOP) Planning IT Operations Disaster Management Operations & Maintenance and End User Support Telecommunications Services Out-of-Scope Systems\Application Development, Systems\Application Engineering

Production Management Operations and Maintenance (O&M)

Assessment and Authorization Services All Cyber Security Services and Support Certifying Authority Support Control Assessor – Travel Audit and Assurance Services

Information System Security Officer (ISSO) Contractor Support Security Operations Center (SOC) 24x7 Monitoring Day-to-Day Operations Response Threat Management System and Application Vulnerability and Penetration Testing Support

Emerging Technology & Modernization Support Security Engineering Tools & Research (Lab)

Information Technology Security

Hardware BPAs

• The Government is seeking a one-stop shopping vehicle, which offers a wide array of computer hardware and software products to include computer hardware, software and licenses, and maintenance that is found under Schedule 70 – General Purpose Commercial Information Technology Equipment, Software, and Services. A specific list of equipment models will be provided at a later date/solicitation. The Government anticipates the establishment of one or more BPAs resulting from a Request for Quotations (RFQ) that will provide for the FEMA Federal Emergency Management Agency continuing IT needs.

Acquisition Strategy and Guidelines

Mr. David A. Grant Chief Procurement Officer

Notional Soliciting Approach In Priority Order o Intended RFP Posting in Fiscal Year 2015 o Information Technology Security o Mission Needs & Requirements o Application Development, Engineering & Sustainment o Intended RFP Posting in Fiscal Year 2016 o Software/Hardware (Blanket Purchase Agreements) o Program Management Oversight o Production Management (Operations & Maintenance) o Intended RFP Posting in Fiscal Year 2017 o Quality Assurance/ Independent Verification and

Validation (IV&V)

Requirement

Multiple/

Single Award

Competition Type

1. Program Management Oversight

Multiple IDIQ Socioeconomic Set-a-Side

2. Mission Needs & Requirements

Multiple IDIQ Socioeconomic Set-a-Side

3. Application Development, Engineering & Sustainment

Single IDIQ Full and Open

4. Quality Assurance, IV&V

Multiple IDIQ Government intends to exercise remaining options

Socioeconomic Set-a-Side

5. Production Management (O&M)

Single IDIQ Full and Open

6. Information Technology Security

a. Security Operations Center

Single IDIQ Socioeconomic Set-a-Side

b. Assessment and Authorization

Single IDIQ Socioeconomic Set-a-Side

c. Emerging Technology

Single IDIQ Socioeconomic Set-a-Side

d. Information System Security Officer

Single IDIQ Socioeconomic Set-a-Side

7. Hardware (BPAs) Multiple IDIQ Socioeconomic Set-a-Side

Notional Acquisition Approach

Organizational Conflicts of Interest oProgram Management Oversight: Standalone contract. Offerors can only receive contract award for this and no others.

oMission Needs & Requirements: Offerors can also receive contract award for the Quality Assurance, IV&V but no others. (Government intends to exercise remaining options) oApplication Development, Engineering & Sustainment: Standalone contract. Offerors can only receive contract award for this and no others.

Organizational Conflicts of Interest (con’t.)

oQuality Assurance, IV&V: Offerors can also receive contract award for Mission Needs only.

(Government intends to exercise remaining options) oProduction Management (O&M): Standalone contract. Offerors can only receive contract award for this and no others.

Organizational Conflicts of Interest (con’t.)

o Information Technology Security:

o Assessment and Authorization: Standalone contract.

Offerors can receive contract award for this and no others within Information Technology Security.

o Emerging Technology: Offerors can also receive contract award for Information System Security Operations only within Information Technology Security.

o Information System Security Operations: Offerors can also receive contract award for Emerging Technology only within Information Technology Security.

o Security Operations Center: Standalone contract. Offerors can only receive contract award for this and no others within Information Technology Security.

THANK YOU!

FEMA-Industry@fema.dhs.gov

(202)-646-1895

“We are at the beginning, not the end of this process!”

mailto:FEMA-Industry@fema.dhs.gov mailto:FEMA-Industry@fema.dhs.gov mailto:FEMA-Industry@fema.dhs.gov