SOURCES SOUGHT
R -- NETC Admissions System
- Notice Date
- 11/16/2007
- Notice Type
- Sources Sought
- NAICS
- 541512
— Computer Systems Design Services
- Contracting Office
- Department of Homeland Security, Federal Emergency Management Agency, NETC Acquisition Section, 16825 South Seton Avenue, Emmitsburg, MD, 21727, UNITED STATES
- ZIP Code
- 00000
- Solicitation Number
- HSFEEM08ADMISSIONS
- Response Due
- 12/14/2007
- Archive Date
- 12/29/2007
- Point of Contact
- David Orris, Contract Specialist, Phone (301)447-1830, Fax (301)447-1092, - Cynthia Adams, Contract Specialist, Phone (301) 447-1221, Fax (301) 447-1092
- E-Mail Address
-
david.orris@dhs.gov, cindy.adams@dhs.gov
- Description
- THIS IS A REQUEST FOR INFORMATION (RFI) FOR PURPOSES OF CONDUCTING MARKET RESEARCH TO IDENITFY TYPES OF SOFTWARE SYSTEMS AVAILABLE FOR THE NATIONAL EMERGENCY TRAINING CENTER (NETC) ADMISSIONS ACTIVITIES AS DESCRIBED HEREIN. THERE IS NO SOLICITATION AVAILABLE AT THIS TIME. The NETC Admissions activities are similar to most academic environments and are centered on the receipt and processing of application forms; the assignment of applicants to classes; the processing of lodging requests; the management of travel arrangements; and extensive back-end reporting and analysis. The primary needs of NETC Admissions are to automate any and all possible data ingestion activities and then automate the tasks performed on that ingested data to provide Admissions services to the student and data visibility to the Federal user community. Many of the tasks internal to the NETC Admissions business have been partially automated by an existing system. However, that existing system does not provide sufficient architectural flexibility to allow for quick feature modifications; intuitive user configuration; effective data exchange with other systems; or use of current technologies to support Internet use. PRIMARY ASSUMPTIONS FOR THE NETC ADMISSIONS SYSTEM INCLUDE: (1) The NETC Admissions System will exploit the most current version of Oracle available to FEMA. All data shall be managed within a secured and maintained relational database system. The database shall be designed to ensure referential integrity and allow for concurrent use by multiple users. (2) Hardware and software used to deliver on the requirements will meet the standards of the current Homeland Security Enterprise Architecture, as well as, FEMA product approval. (3) NETC employs a business model that utilizes an overall Operations and Maintenance team for all systems within the NETC IT infrastructure. The skills required to support the NETC Admissions System will be fully documented to support staffing decisions. (4) It is expected that system content and the associated support requirements contain no esoteric attributes that would inject significant cost into the NETC business. (5) All Application Programming Interfaces (APIs) will be published and made available to FEMA, as approved by the system owner. (6) Any algorithms created specifically to facilitate NETC Admissions business processes will be documented and published for FEMA such that they can be supported by Operations and Maintenance staff. (7) Interfaces (human and machine) will be based on industry best practice and standards found in higher education models. (8) Solution design will support industry best practice in object-oriented technology and graphical presentation. (9) Correspondence is critical to the conduct of NETC Admissions business. It is assumed that hot-link capabilities will be provided for all outgoing electronic correspondence to allow recipients to easily navigate from said correspondence to related points of interaction with the NETC Admissions System. (10) The NETC Admissions System will support the principles of leveraging existing software applications within FEMA and use of common tools across FEMA and DHS to promote information sharing, decrease cost and mitigate risks associated with Operations and Maintenance. (11) Configuration capabilities must be present to adapt the system to changes in NETC Admissions business rules and processes. (12) Attributes and functionality contained in the NETC Admissions System will be intuitive to the users and supported through robust help functions such that timelines for learning, configuration and use are minimized. (13) Secure interactions with the system must be provided through local interfaces and over the Internet. (14) Environmental conditions will be similar to those outlined in DHS 4300A, Sensitive Systems Hand book. (15) Web components must use secure socket layer (SSL) encryption technologies. (16) The NETC Admissions System houses sensitive privacy information. All interactions with the system must be appropriately constrained (security and encryption) to prevent unwanted exposure. Guidelines put forth by The Privacy Act of 1974, Public Law 93-579, as amended will be met. (17) Human interfaces will comply with the standards put forth in the 1998 Amendments to Section 508 of the Rehabilitation Act (29 U.S.C 794d). (18) The NETC Admissions System must be supported through a complete documentation set that includes, but is not limited to: Business Rules; System Specifications; Software Specifications; Design Specifications; Database Specifications and Schema; Installation Specifications; Application Programming Interface Specifications; User Guides; System Administration Guides; Technical Support Manuals; and Training Manuals. (19) Unified Modeling Language (UML) will be used to develop use cases that refine the business requirements and to define and capture the system design. All other design and development aspects are constrained only by the generic standards deemed acceptable by FEMA and the artifacts prescribed by the System Development Life Cycle (SDLC) governance. RESPONSES SHALL INCLUDE THE FOLLOWING: (1) Propose a solution/product, i.e., commercial off-the-shelf (COTS), government off-the-shelf (GOTS), existing system w/minor modifications, full development effort, etc. that will meet many or all of the NETC Admission System requirements. Address each item above (#1 through #19) to describe how the proposed solution/product meets the primary assumptions for the Admissions System. Provide a full description of the system, functions, diagrams, identify if it is proprietary, etc. (2) Identify and describe relevant experience using the proposed solution/product. This RFI is not a Request for Proposal (RFP), but rather, is an exploratory request to determine the availability of COTS, GOTS, existing software system w/minor modifications or full development products and identify vendors who can provide a solution/product that will satisfy the requirements specified above. The Government will review the information received to determine the acquisition strategy and assist with the development of the Statement of Objectives for this requirement. The Government will not reimburse any concern for any information that is submitted in response to this RFI. Responses should indicate whether they are large business or small business. Small Business Concerns should indicate if they are small, small disadvantaged, 8(a), HUB Zone, or woman owned and identify a NAICS code for this requirement, if applicable. All interested business concerns are required to respond to this RFI via email by December 14, 2007. Responses shall not exceed 20 pages with a file size of 3 MB or less and must include company point of contact, email address, telephone number and fax number. All concerns shall respond to Cindy Adams via email at cindy.adams@dhs.gov For additional information, Ms. Adams may be contacted at 301-447-1221.
- Place of Performance
- Address: DHS/FEMA/National Emergency Training Center, 16825 South Seton Avenue, Emmitsburg, MD
- Zip Code: 21727
- Country: UNITED STATES
- Zip Code: 21727
- Record
- SN01453728-W 20071118/071116223426 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |