Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
RequestforInformation(RFI)
VERSION HISTORY
Version Number 0.1 0.2 0.3 0.4 0.5 0.6 1.0 1.0 1.0 Implemented By J. Mattix J. Mattix J. Mattix J. Mattix B. Wenstrom J. Mattix J. Mattix J. Noneman M. Roth Revision Date 7/31/13 8/03/13 8/27/13 8/28/13 9/11/13 9/11/13 9/18/13 9/20/13 9/25/13 Approved By Approval Date Description of Changes First Draft Tech Comments by CTO Comments from IPT IPT meeting comments Review IPT meeting comments IPT 9/18/13 Release Version Added acquisition method question. Deleted duplicate word
Page 2 of 10
Purpose
This document and its attachments provide information for vendors to decide whether they are willing to participate in a more detailed selection process. Vendors do not need to prepare detailed proposals at this stage. Vendors should provide basic information regarding capabilities and an indication as to how they would approach working with the BLM to achieve this documents outlined objectives.
Page 4 of 10
The objective of the Minerals and Lands Reporting System (MLRS) project is the development of a modern system employing automated business flows, that will enable the storage and retrieval of public land and mineral records which document the rights and interest of the U.S. in the form of electronic documents and metadata to include geospatial references. Today most of the BLM and its customers, the American public rely upon the antiquated Legacy Re-host 2000 system (LR2000) and a similar system called the Alaska Land Information System (ALIS) for the storage, maintenance and reporting of its land records and management data. Once site data has been obtained, users routinely go to the GLO image repository to obtain image data related to the site.
Page 5 of 10
Functional Requirements
BLMs core requirements are contained in the enclosed documents: BLM Mineral and Land Records System: Requirements Definition and the BLM MLRS Requirements Traceability Matrix. To further aid in your understanding we have also included an Evaluation Report on LR2000, the system we intend to replace. Processes are subject to change in response to, among other things, changes in policies, laws, regulations, industry technology, and internal process improvements.
Please send any questions to Lamont Sawyers by 3 pm ET, December 4, 2013. Please answer the following questions to the best of your ability and return to the BLM by 3 pm ET, January 3, 2014.
What solution would you recommend to meet the BLM s MLRS requirements? You may attach up to twenty (20) pages maximum to explain your solution recommendation. Submission of additional general marketing materials, white papers, etc. are welcomed, but the materials may or may not be evaluated by the BLM. Please provide answers to all questions based on the customization required to meet the BLM specific requirements.
Response
Page 6 of 10
Technical Requirements
Current BLM Technical Environment 1. Microsoft Enterprise 2. File Server OS a. Windows 2008R2 3. Client OS a. XP b. Windows 7 c. Windows 8, RT
d. Android e. Apple IOS 4. Workflow Environments supported. a. Documentum xCP b. ESRI ArcServer v.10.2 Workflow c. SharePoint Workflow (SharePoint Designer and Workflow
Page 7 of 10
5. Current databases. a. SQL Server (2008? 2010?) b. Oracle (10/11g) 6. Must be able to address legacy databases: a. Sybase b. Informix 7. VDI Environments a. Citrix b. Microsoft RDP 8. Mobile Environment a. Laptops b. Smartphones c. Can your solution work effectively in our environment as described? If not, what additions would be required in support of your solution? Is this system compatible with our operating system environment? With what other OSs is it compatible? What language(s) is your solution written in? What server software is compatible /incompatible with your system? How well does this software work with software- and hardware-based security applications? What browsers are compatible with this solution? Are you aware of any incompatibilities that this solution might have with any specific hardware or software? Provide details. Does this solution support a pattern similar to the model-view-controller (MCV) architecture pattern? Describe how it may or may not
MLRS Request for Information Procurement Sensitive / Unclassified For Official Use Only Page 8 of 10
Tablets
Is your solution cloud ready, or is it a cloudbased offering? Does your solution take advantage of any open source software? Describe any proprietary dependencies, components or elements your solution may have. Are there certified resellers of your system or are you a certified reseller? What acquisition method was used for past acquisitions? What Geospatial software would your solution use and/or support? What is the amount of memory required by the workstation and/or server? What business performance metrics and associated measures are available for your solution? What telecommunication connectivity speeds are needed for ideal operation of this solution? Is your solution compatible with NIST security standards? Are there any NIST standards it is NOT compatible with? Does your solution support mobile end use devices? If so, what device classes and are there feature restrictions when using those devices? Total Cost of Ownership (TCO) Is your solution priced by the number of users, or number of workstations or some other method? For licensed portions of your solution can you provide government or commercial license terms and agreements? Please describe your licensing policies, e.g. one time buy or annual renewal. Do you offer volume purchasing agreements? Please provide information on your
MLRS Request for Information Procurement Sensitive / Unclassified For Official Use Only Page 9 of 10
Describe a typical timeline for development/customization and installation of your solution. Describe the range of costs we might expect to encounter in a similar typical installation. From the information you have been given would you describe BLMs needs as typical or atypical? In what way? What levels of Operations and Maintenance support are available? Define each level. How often are major software upgrades typically available? What level of training do you recommend? Is formal user training available? Are there any other costs we should be aware of that would contribute to the total cost of ownership of your solution? Please provide an estimate of the total cost for this project.
Page 10 of 10