MODIFICATION
D -- Integrated, Automated Information System (IAIS)
- Notice Date
- 1/31/2003
- Notice Type
- Modification
- Contracting Office
- General Services Administration, Federal Technology Service (FTS), Center for IT Solutions (5TF), 230 South Dearborn Street - Room 3380, Chicago, IL, 60604-1696
- ZIP Code
- 60604-1696
- Solicitation Number
- 5TI1503034RFI
- Response Due
- 2/14/2003
- Archive Date
- 3/1/2003
- Point of Contact
- Irma Sauseda, Information Technology Manager, Phone (312)886-3825, Fax (312)886-3827,
- E-Mail Address
-
irma.sauseda@gsa.gov
- Description
- REQUEST FOR INFORMATION Alien Address Management System (AAM). This notice identifies the Department of Justice (DOJ), Immigration and Naturalization Services (INS) intent to acquire an integrated, Automated Information System (AIS) that will be known as the Alien Address Management (AAM) System. The INS is issuing this Request for Information (RFI) to solicit information from commercial entities capable of providing the services and products described herein. The system will have to comply with architectural, technical, security, business processes and legislative requirements. This RFI is not a Request for Proposal (RFP), but, rather, is an exploratory request to identify capabilities, obtain expressions of interest, determine the availability of commercial off-the-shelf (COTS) products, market information and contractor capabilities for Government planning purposes. The AAM team is seeking to identify and resolve concerns regarding the feasibility of the requirements, integration of the various technologies, and other industry concerns or questions related to this acquisition. BACKGROUND INS is required to maintain current address information for all aliens residing in the United States for longer than 30 days. Aliens who change their address are currently required to notify INS via a standard form within 10 days of the change. INS currently maintains 19 automated systems that contain alien and alien-related addresses. At present, these systems are not integrated to allow for a synchronized inventory of alien information. These systems do not interface with each other allowing the possibility that each system could indicate a different address for a single alien. In addition, failure by INS to note a properly submitted AAM in all relevant systems could result in negative legal consequences for the INS. Currently INS receives and processes between 6 and 9 million application each year. INS admits between 1.4 and 1.7 million people each year. Any address information received on initial contact would be entered into this system. In addition, each time an alien in the United States changes his or her address, this information would be recorded in the proposed system. INS currently has 22 million active files in its system. For the six months from August 2002 to January 2003, the INS has received over 850,000 change of address forms. The objective of the AAM system is to improve the process of collecting, updating, and maintaining address information related to aliens and associated entities. The goal is to ensure compliance with Federal regulations regarding AAM notification while providing a means to facilitate locating and contacting aliens. SOLUTION REQUIREMENTS The AAM solution must provide one source of alien address information containing information source and history, thereby requiring only one change notification from an alien to update address information Service-wide. There must be data-integrity and quality-assurance safeguards to ensure that accurate and uniform data is maintained and to provide reverse look-up functionality. All data collection input methods must provide the alien with a clear understanding of what information is required to comply with INS guidelines in order to receive benefits or services. User-generated reports must include historical and statistical outputs in addition to ad-hoc reports that do not require programming intervention. The solution should automatically generate correspondence to aliens notifying them of receipt of the notification by INS. Data-verification reports should provide validation of INS data by comparing it to commercial-address databases with the understanding that no commercially obtained address would populate an INS database automatically or overwrite alien-provided input. INS AAM system users must be able to mark an address as invalid with a reason until information can be corrected or validated. INS address systems must have the capability to send and receive address information electronically to and from INS legacy systems as well as designated Government agencies within INS rules and Memoranda of Understanding. All information sent and received by INS must comply with the Privacy Act, other legal mandates, and INS address regulations, as well as the INS Third Party Rule. Access to sensitive address information must be protected based upon user access roles and depending on alien status. The solution must be scaleable to meet evolving INS technology needs. Principal alien information should link to dependent address information. Information should also link between all individuals indicated as living at the same address. AAM must be able to maintain no fewer than three address categories for each alien record and have the capability to link a minimum of seven related address records (attorney, sponsor, etc.) to each alien record. The solution must be able to maintain all standard domestic and international address fields. In addition to address information, AAM must have the capability to maintain no fewer than 10 personal attribute information fields, including identification numbers (Social Security Number, Admission Number, etc.) as well as biographical information (Date of Birth, Country of Birth, etc.). The system must have a method to annotate a level of trust for each address record depending on address source and reliability. Address information input methods must include telephone, mail, in person, Internet, and E-mail and may be integrated with biometric-scan and smart-card capability. The system must be able to maintain an audit trail and include the following attributes regarding the physical entry of address information: date of receipt, date of entry into system, effective dates of information, source of information, and individual who entered the information. A chart reflecting systems and databases currently in use at INS is provided as attachment 1. PROCUREMENT STRATEGY Procurement and implementation may be sought at a later date through the issuance of a statement of work and RFP. It is anticipated that any such future solicitation could result in an award to multiple offerors. SUBMISSION OF INFORMATION Respondents are asked to provide information that outlines specific capabilities of products and services that may satisfy the broad Governmental requirements as noted herein. The Government is also interested in relevant experience and contractor qualifications to perform the work envisioned. This RFI is NOT to be construed as a commitment by the Government to issue an RFP or ultimately to award a contract. Responses provided by industry will not be considered as proposals nor will any award be made as a result of this RFI. Any costs incurred as a result of responding to this RFI shall be borne by the respondent and cannot be charged to the Government for reimbursement. The information in this RFI represents an overview of the anticipated project, is subject to change, and is in no way binding on the Government. The Government will not provide any direct feedback to industry in general. The Government may utilize any information submitted by interested parties to assist in the development of the statement of work for the contemplated RFP. Offerors are advised not to submit any proprietary information that they would not want to be used for this purpose. A potential offeror may have an idea that does not fit into the existing framework of the current business process, but it may inform the Government of a new and more effective way of doing business. Potential offerors are encouraged to suggest any and all ideas they have that can add value to the process. All information submitted in response to this RFI or requests to be informed of the status of an possible RFP resulting from effort shall be sent to: ____________________. Responses shall be limited to 30 pages in MS Word format and include the name and telephone number of a point of contact having authority and knowledge to discuss responses with Government representatives. Point of Contact : Charles Locke Title: Senior IT Project Manager(COTR), GSA Phone: 312-886-3818 Fax 312-886-3827 Second Point of Contact Name: Ellen Womack Title: Senior Contracting Officer, GSA Phone: (312)353-2667, Fax: (312)886-3827 ---------------------------------------------------------------------------------------------------------------------------------- ATTACHMENT 1 Types of Operating Systems and Databases currently in use at INS (Sampling) NAME DESCRIPTION RAPS - IDMS IBM Mainframe CLAIMS3 - DOS using B-Trieve Database APSS - IDMS IBM Mainframe DACS - IDMS IBM Mainframe EREM - Web-based with Oracle Backend, during FY03 PAMS - IDMS IBM Mainframe CLAIMS 4 - Client/Server using Visual Basic as Front end and Oracle Database as the backend. Hosted on a UNIX DEC Alpha RNACS - IDMS MFAS - IDMS IBM Mainframe COA - Web-based with an Oracle backend BMIS - Resides on IBM Mainframe EADS - Stand alone PC ENFORCE Case Management system. - EID is Unix/Oracle based GEMS - Unix/Oracle based NIIS - IDMS mainframe system ADIS - Web-based system with an Oracle backend. GES - Database not identified JAMS - Database not identified PCTS - Database not identified STSC - Resides on mainframe at Justice Dept SEVIS - Database not identified
- Place of Performance
- Address: U.S.A. Nation Wide
- Country: United States
- Country: United States
- Record
- SN00250681-W 20030202/030131213735 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |