Mission_Needs.pdf

Question Answer

The Mission Needs and Requirements IDIQ requires a broad set of IT knowledge combined with requirements management, mission needs analysis, acquisition support, process improvement, etc. This fits well with a 541611 NAICS code, which has a $15M size standard.

There are a significant number of small businesses in this NAICS code performing similar work at FEMA today on EADIS and COMMIT. This approach would maximize competition and provide FEMA with a broad set of IT and management consulting skills.

Noted

Will the Government be using TABSS, Domain 1, Track 3 – 8a for the (Mission Needs) Requirements, Estimates, and Scope procurement?

TBD

The Mission Needs requirement is outlined to be met with a multiple award IDIQ. Is this anticipated to be a new FEMA IDIQ contract, or will FEMA make use of EAGLE II for this requirement area?

FEMA anticipates issuing its own contracts.

The Mission Needs requirement is outlined to be met with a multiple award IDIQ. How many awards in this area does FEMA anticipate?

TBD

What is the proper name of the Requirements contract: “Mission Needs & Requirements”, “Requirements, Estimates, and Scope (RES)”, or “Mission Needs (Requirements)”?

Mission Needs & Requirements

Which contract(s) define the format and ensure accuracy of the requirements that are delivered to the ADES contract?

All the contracts must work hand in hand to ensure a successful hand-off from beginning to successful roll-out. The format and governance controls will be with the PMO to the missions needs and PMO will maintain oversight.

What are the expectations for the format and accuracy of the requirements that are delivered to the ADES contract?

All the contracts must work hand in hand to ensure a successful hand-off from beginning to successful roll-out. The format and governance controls will be with the PMO to the missions needs and PMO will maintain oversight.

After “Mission Needs & Requirements” communicates baseline requirements to ADES, in what methods/channels can mission areas use to communicate changes in those requirements during development?

All the contracts must work hand in hand to ensure a successful hand-off from beginning to successful roll-out. The format and governance controls will be with the PMO to the missions needs and PMO will maintain oversight.

How are conflicts “Mission Needs & Requirements” and other contracts handled, particularly in terms of feasibility or realism of requirements?

This depends on the task. Feasibility will be worked through means of the SOO or PWS and other supporting documents that would include costs tools.

How are nonfunctional requirements gathered and assessed against the realism of the functional requirements?

The project office with the requirement will work with the MN&R team and PMO to develop both the technical functional requirements as well as the non-functional requirements and separate these where needed and within the operational scope and funding.

What are the different groups within FEMA that contribute toward the functional and nonfunctional requirements of systems and software?

The project office with the requirement will work with the MN&R team and PMO to develop both the technical functional requirements as well as the non-functional requirements and separate these where needed and within the operational scope and funding.

What are the expectations around the scope and definition of the Concept of Operations (as listed under “Mission Needs & Requirements”)?

The expectation is to clarify the customers' needs and generate output documents that allow a successful hand-off to the App Dev contractor.

How does the “Concept of Operations” affect the day-to-day execution of the ADES contract?

The CONOPS is the conceptual plan. Execution will depend on particular tasks under the contract.

How does the “Mission Needs & Requirements” contract interface with ADES and other contracts to analyze the cost and benefits of business cases?

All the contracts must work hand in hand to ensure a successful hand-off from beginning to successful roll-out. The format and governance controls will be with the PMO to the missions needs and PMO will maintain oversight.

Who determines whether a business case should be approved?

It is a collaborative effort among the customer with the requirement, OCIO, and other governance authorities.

How does the “Business Vision” affect the day-to-day execution of the ADES contract?

The day-to-day execution will depend on the requirement and the task order.

How is the “Business Vision” formed?

The program office generates the business vision relative to their project/program needs.

How is the “Business Vision” communicated to the other contracts?

It is communicated through the program owner, PMO and advance planning sessions.

What are the security standards upon which the “Mission Needs & Requirements” will develop

FEMA security requirements?

All security requirements must comply with DHS 4300 and all applicable FEMA subordinate processes.

Who participates in defining the Enterprise

Architecture?

FEMA OCIO, PMO & EA in alignment with DHS requirements.

What are the technical areas that are covered by the Enterprise Architecture?

HW, SW, SW development sustainment.

How often are Enterprise Architecture changes made?

Changes will be made as frequently as mandated changes occur and/or mandated at FEMA/DHS.

How is the Enterprise Architecture requirements incorporated and enforced within the contract areas?

The EA requirements of FEMA/DHS will be incorporated through direct cross team reviews of process, use of the TRM and all existing and to be defined EA policies.

The SOW refers to traditional waterfall method of development as well as agile methods. Does

FEMA, as an enterprise, have a preference about which methodology it would like to adopt for future development projects?

The use of different development types "agile, waterfall, spiral" will be determined at the task order level and will depend on the particular requirement.

The Requirements Estimates, Scope SOW indicates it will be under the EAGLE II contract, yet the Socioeconomic Disadvantage Concerns document, lists RES as a Small Business Set-a-Side.

Is it possible to provide clarification on competition type for this SOW?

TBD

Will FEMA consider Web-based applications to enable mobile apps across multiple platforms(ie:

explorer, safari, etc)

Yes, through reviews with the FEMA EA process in coordination with the DHS rules and mandates.

Prior to deployment of mobile hardware consider site surveys of high risk (hurricane areas) for best service provident?

Noted

Do you anticipate multiple pillars within MN&R?

For example, will you have pillars for the HR, one for Financial, one for Security offer?

TBD

For award as the prime, do you need to be on

MOBIS?

If the procurement is open market, then 'no';

however, if it is determined that BPA(s) will be established versus IDIQs, then the vendor would need to have a current GSA schedule although no determination has been made on which schedule.

Is it sufficient for a sub to meet the CMMI level 3 requirements instead of the prime? If not, it should be because FEMA will vastly reduce the number of eligible offerers from the small business award. Please clarify the OCI parameters for RES. Can you be a sub on one and a prime on another?

Requirements are still being defined.

Is there ever a need for staff augmentation?

There could be, but this will be determined by individual programs.

Can I be a sub with a prime on different contract awards?

This would depend on what mix of contracts are contemplated. FEMA will ensure it complies with organizational conflicts of interest regulations in accordance with the Federal Acquisition Regulation.

Can I be a prime on one contract and a sub on another?

This would depend on what mix of contracts are contemplated. FEMA will ensure it complies with organizational conflicts of interest regulations in accordance with the Federal Acquisition Regulation.

Mission Needs