SOLICITATION NOTICE
D -- FACILITIES GIS AND DATA INTEGRATION
- Notice Date
- 7/28/2006
- Notice Type
- Solicitation Notice
- NAICS
- 541511
— Custom Computer Programming Services
- Contracting Office
- NASA/George C. Marshall Space Flight Center, Procurement Office, Marshall Space Flight Center, AL 35812
- ZIP Code
- 35812
- Solicitation Number
- 4200163267
- Response Due
- 8/4/2006
- Archive Date
- 7/28/2007
- Description
- Facilities GIS and Data Integration Phase VI (Task Order 3) A. Objective The objective of this Statement-of-Work (SOW) is to expand the Functionality and Data Connectivity of the GIS (Geographic Information System) and Data Integration Application built for the Facilities Management Office at NASA?s Marshall Space Flight Center in Huntsville, AL. This web based Facilities GIS (FacGIS) application has been successfully developed and implemented on a secure web server at NASA-MSFC. The main component of this application is a map of the Center. Many sub-components are integral to the main component, and are utilized to explore information. The objectives of this expanded functionality and data connectivity are to provide a web interface to Facilities data, rapid data access, a visual portal to multiple data sets, and be integrated in such a way that facilitates information gathering and analysis. This application will be compliant with section 508 of the Rehabilitation Act, to provide accessibility to people with disabilities. B. Scope The tasks detailed within this scope of work are divided into three (3) segments. Segment 1 ? Maintenance Application Enhancements. This task involves the maintenance, functional enhancement, and continued data integration of the existing FacGIS and Interactive Floor Plan web applications. Segment 2 - Data Development and Migration. This task provides technical support for the collection, migration, database design, and integration of the Engineering Systems Drawings and the Utility Distribution Systems GIS. Segment 3 ? Handheld Applications. This task encompasses the development and implementation of Handheld applications and the integration of GIS (Geographical Information Systems) Maps and SVG (Scalable Vector Graphics) floor plan files generated in previous project phases. C. Reference Documents D. Tasks The following tasks shall be accomplished as part of this Statement of Work. 1.0 Maintenance and Application Enhancements. During the previous phases of this project, many maps, data sets, functions, reports, tools, etc. were integrated and developed. The result is a very robust application that brings numerous data reports, maps, drawings, floor plans, etc. to the user?s desktop. The entire application can be viewed as two sub-applications. The main application (or component) is a Map Viewer of the Center. From the Map Viewer, the user can query databases from a center wide and/or building perspective. 1.1 GIS and Facilities Web Application). The second component is the Interactive Floor Plan. From the Interactive Floor Plan web application, the user can query databases from a floor and room perspective. The Maintenance and Application Enhancements task involves maintenance of the existing application and all components, and technical support to enhance functionality, expand data connectivity, and improve reports and maps. Configuration Control Board (CCB) A Configuration Control Board (CCB) and a Task List database were established during previous phases. The CCB is comprised of NASA and contractor personnel and managed by the NASA Project Manager. It is the responsibility of the CCB to review and approve any suggested additions and/or modifications to the application. The Task List database and associated design diagrams has been a beneficial tool in the management of the development of this product. Other review processes have contributed to a continual expansion of functions and data sets that could be incorporated. These reviews consist of the web review process, hands-on workshops and training, project review meetings, design meetings, and individual user requests. All of these processes would be used to determine application enhancements to be recommended to the CCB. 1.1 GIS and Facilities Web Application. The GIS and Facilities web application is the main map viewing component. From this component the user can query databases from a center wide and/or building perspective. This task involves maintenance of the existing application and all components, and technical support to enhance functionality, expand data connectivity, and improve reports and maps. 1.1.1 Improve and Add Functionality. All additions and modifications to the Facilities GIS and Data Integration web application will first be reviewed and approved by the CCB before implementation. The NASA PM will set implementation priorities and authorize the final design and configuration. This task will include, but is not limited to, the following: add and/or modify functions, tools, menus, queries, reports, search tools, graphic display, etc. These tasks will be confined within the period of performance of this contract and allocated funds of this task. System requirements for additions and modifications shall be delivered as reports, system diagrams, punch lists, storyboards, etc. Recommendations shall be presented to the CCB. Development of necessary code will begin after final approval of the design. All required code, tools, applications, databases, processes, metadata, etc. to create and modify functions, as directed by the CCB, will be delivered and installed at NASA-MSFC. 1.1.2 Integrate Additional Data Sets. All additional Data Set Connections to the GIS and Facilities application will first be reviewed and approved by the CCB before implementation. The NASA PM will set implementation priorities and authorize the final design and configuration. 1.1.3 Maintenance and Training. Maintenance of the GIS and Facilities application previously delivered, will be conducted throughout the period of performance of this contract. Maintenance will be performed on a as-needed bases. 1.1.4 MSFC Compliance and Usability Board (CUB). This task involves all necessary activities to successfully comply with the requirements of MSFC?s Compliance and Usability Board (CUB) [f.k.a. Web Standards Board (WSB)] , and the Marshal Operations Readiness Review (MORR). 1.1.5 Software Development documentation. A Software Development Plan (SDP) will be written that describes the implementation process. 1.2 Interactive Floor Plan Web Application. The Interactive Floor Plan application is accessed via the main mapping page, and is used to drill-down to more information about a facility. From the Interactive Floor Plan web application the user can query databases from a floor and room perspective. 1.2.1 Improve and Add Functionality. All additions and modifications to the Interactive Floor Plan web application will first be reviewed and approved by the CCB before implementation. The NASA PM will set implementation priorities and authorize the final design and configuration. 1.2.2 Integrate Additional Data Sets All additional Data Set Connections to the Interactive Floor Plan application will first be reviewed and approved by the CCB before implementation. The NASA PM will set implementation priorities and authorize the final design and configuration. 1.2.3 Maintenance and Training. Maintenance of the Interactive Floor Plan application previously delivered, will be conducted throughout the period of performance of this contract. Maintenance will be performed on a as-needed bases. 1.2.4 MSFC Compliance and Usability Board (CUB). This task involves all necessary activities to successfully comply with the requirements of MSFC?s Compliance and Usability Board (CUB) [f.k.a. Web Standards Board (WSB)] , and the Marshal Operations Readiness Review (MORR). 1.2.5 Software Development Documentation. A Software Development Plan (SDP) will be written that describes the implementation process. This document will address project monitoring and management of each phase of the project (Plan, Define, Design, Develop, and Implement). A Software Development Guide (SDG) will be written that describes the application and architecture. This document will address system architecture, data architecture, and application design. A Version Description Document (VDD) will be written for each modified application release. 2.0 Data Development and Migration. 2.1 Engineering Systems Drawings. The Engineering Systems Drawings are currently being captured in MicroStation format. The objective of this task would be to support this collection process. Database design techniques, development of a system architecture, and the establishment of new data maintenance procedures, would make the integration of the Engineering Systems Drawings with the Interactive Floor Plan application possible. All database design and system development tasks would be conducted using a team approach. Current data managers will be consulted during all tasks. 2.1.1 Database Design and Development. This task consists of the design of graphics layering, naming conventions, symbology, attributes, etc. Note: If data collection is not conducted in a systematic and logical format, then the data cannot be integrated to other intelligent systems. 2.1.2 System Architecture Design and Development. The new data structure must be maintained and be integratable with CMMS, MicroStation, ArcSDE, FacGIS, and the Interactive Floor Plan application. A system architecture will be developed that insures integration, and facilitates data maintenance. The development of system workflows may also be conducted in this task. The system architecture will be developed, were possible, within the framework of the exiting hardware and software. Existing CADD, GIS, Enterprise Databases, and other products, and existing Servers and Networks will be incorporated within the design, in order to leverage off of the existing architecture and save costs. Interoperability will be incorporated into the design of the system architecture in order to share data between GIS and CADD applications. Conduct all necessary activities needed to establish an interoperable environment. 2.1.3 Support Collection Efforts. This task involves the technical support of the data collection efforts of the existing team. Data collection documents will be developed. Data collection tools may be developed if necessary. 2.1.4 Data Input and Cleaning - Pilot. Data collected will be cleaned, organized, and inputted into the newly developed Engineering Systems Drawing database. This phase of the data input process will be conducted as a pilot project. A sub-set of data will be input to ensure the database design integrity and the integration to other databases and applications. 2.1.5 Data Input and Cleaning ? Production. Technical support and direction will be provide to the existing staff during the remaining data input and cleaning process. Data cleaning tools may be developed if necessary. These tasks will be confined within the period of performance of this contract and allocated funds of this task. 2.1.5.1 Temporary Data Entry Personnel. Provide temporary data entry personnel and CADD operators to support existing staff with the remaining collection, clean-up, and data entry efforts. 2.1.6 Design and Establish Data Maintenance Procedures. The new database design, system architecture, and collected data will require a re-structuring of Data Maintenance Procedures in order to insure the accuracy and continued reliability of the data. Workflows and procedures for data entry, data maintenance, export and import procedures, and interoperability will be established. Data entry tools and other utilities may be developed as necessary. 2.1.7 Connect Data Set to Interactive Floor Plan. Once the Engineering Systems data is collected into an intelligent format, it can be connected to the Interactive Floor Plan web application. A design of additional web functions, to query and display Engineering Systems data, will consist of drawings, queries, reports, storyboards, and proposed functionality. This design shall be used to communicate with the development team and the customer. Development of the web code will begin after the customer?s final approval of the design. 2.1.8 Software Development Documentation. A Software Development Plan (SDP) will be written that describes the implementation process. This document will address project monitoring and management of each phase of the project (Plan, Define, Design, Develop, and Implement). A Software Development Guide (SDG) will be written that describes the application and architecture. This document will address system architecture, data architecture, and application design. A Version Description Document (VDD) will be written for each modified application release. This document will address functional information, technical information, and implementation schedule of each release of the application. 2.2 Utility Distribution Systems GIS. The current Utility Distribution Systems data exists in MicroStation design files. These CADD files have some logic incorporated in the structure. However, the current data structure is not conducive to many GIS type queries. Also, the current Utility System data is not drawn to any government sanctioned standard. It is recommended that the existing Utility Systems data be migrated into a standard GIS format. 2.2.1 Database Design and Development. This task consists of the design of map layering, naming conventions, symbology, attributes, etc. 2.2.2 Review, Clean, and Organize Existing Data. Prior to the migration of the Utility data into a GIS/Relational Database format, the data will be cleaned and organized in the existing CADD format. Much of the exiting utility data is contained on the same levels and annotation and line work is drawn sporadically. Organizing the CADD data prior to migration will reduce overall costs and errors. 2.2.3 System Architecture Design and Development. The new data structure must be maintained and be integratable with MicroStation, ArcSDE, and FacGIS. A system architecture will be developed that insures integration, and facilitates data maintenance. The development of system workflows may also be conducted in this task. The system architecture will be developed, were possible, within the framework of the exiting hardware and software. 2.2.4 Migrate Data - Pilot The existing cleaned and organized CADD data will be migrated into the newly developed Utilities GIS database. This phase of the data migration process will be conducted as a pilot project. A sub-set of data will be migrated to ensure database design integrity and the integration to other databases and applications. 2.2.5 Data Migration ? Production Technical support and direction will be provide to the existing staff during the remaining data cleaning and migration process. Data migration tools may be developed if necessary. These tasks will be confined within the period of performance of this contract and allocated funds of this task. 2.2.5.1 Temporary Data Entry Personnel. Provide temporary data entry personnel and CADD operators to support existing staff with the remaining data clean-up and migration efforts. 2.2.6 Design and Establish Data Maintenance Procedures. The new database design, system architecture, and migrated map data will require a re-structuring of Data Maintenance Procedures, in order to insure the accuracy and continued reliability of the data. Workflows and procedures for data entry, data maintenance, export and import procedures, GPS data, and interoperability will be established. Data entry tools and other utilities may be developed as necessary. 2.2.7 Connect Data Set to FacGIS Web Site. Once the Utility data is migrated into an intelligent GIS format, it can be connected to the FacGIS web site. A design of additional web functions, to query and display Utility data, will consist of drawings, queries, reports, storyboards, and proposed functionality. This design shall be used to communicate with the development team and the customer. Development of the web code will begin after the customer?s final approval of the design. 2.2.8 Software Development Documentation. A Software Development Plan (SDP)will be written that describes the implementation process. 3.0 Handheld Device Applications. A wireless network has been implemented at NASA-MSFC, and handheld applications have been deployed. The previous phases of the Facilities GIS and Data Integration project have produced robust Map Services and Floor Plan SVG (Scalable Vector Graphic) files and processes. The objective of these tasks would be to leverage the previous projects and the wireless network to create handheld applications that access Map and Floor Plan graphics and data. 3.1 CMMS Handheld Applications. The Mobile CMMS Maintenance Application is a PDA/Handheld application that has been previously developed and implemented by another contractor. The objective of this application would be to design and implement a Floor Plan Module, and other functions, into the existing Mobile CMMS application, that accesses the SVG Floor Plans that are stored on a file server and have been generated by an existing process(refer to Figure 6 for a conceptual design and architecture of this application). The scope of this application would be strictly for CMMS mobile users. 3.1.1 Develop Requirements with the NASA Team. Conduct detailed interviews with data managers, review applications, server configuration, databases, etc.. 3.1.2 System Architecture Design. There are many technologies, methods, and products available to develop handheld applications. 3.1.3 Design Application. Based on a combination of the requirements study and the System Architecture, a design of the proposed handheld application consisting of drawings, storyboards, navigation, queries, reports, and functions will be developed. 3.1.4 Develop Application. The customer approved system requirements and application design would be used as the basis for developing the handheld application. Connections to databases and graphic data sources would be included in this task. 3.1.5 Test and Deploy Application. Periodic reviews of functionality, graphics viewing, and data reports of the Handheld Application will be conducted to ensure quality control. Various user tests will be performed during the development process. Modifications and corrections will be accomplished as needed. The final Hand Held Application will be deployed after the customer?s approval. 3.1.6 Software Development Documentation. A Software Development Plan (SDP) will be written that describes the implementation process. This document will address project monitoring and management of each phase of the project (Plan, Define, Design, Develop, and Implement). A Software Development Guide (SDG) will be written that describes the application and architecture. This document will address system architecture, data architecture, and application design. A Version Description Document (VDD) will be written for each modified application release. This document will address functional information, technical information, and implementation schedule of each release of the application. 3.2 Facilities Center Handheld Applications. GIS Map Services, Floor Plan SVG files, Database Connections, Reporting Tools, and other data tools and functions have been developed and prepared in previous phases. Also, the FacGIS mapping application and the Interactive Floor Plan web application have been developed under other taskings. The objective of the Facilities Center Handheld Applications would be to develop and implement PDA/Handheld applications that access and report on Maps, Floor Plans, and Databases similar to those produced on the FacGIS and interactive Floor Plan web site. User navigation and tools would be reconfigured to accommodate the limited viewing and processing capabilities of handheld devices. These applications may be accessible to all users with MSFC accounts. 3.2.1 Develop Requirements with the NASA Team. Conduct detailed interviews with data managers, review applications, server configuration, databases, etc. 3.2.2 System Architecture Design. There are many technologies, methods, and products available to develop handheld applications. 3.2.3 Design Application. Based on a combination of the requirements study and the System Architecture, a design of the proposed handheld application consisting of drawings, storyboards, navigation, queries, reports, and functions will be developed. This design shall be used to communicate with the development team and the customer. User navigation and tools would be designed to accommodate the limited viewing and processing capabilities of handheld devices. Development of the application code will begin after the customer?s final approval of the design. 3.2.4 Develop Application. The customer approved system requirements and application design would be used as the basis for developing the handheld application. Connections to databases and graphic data sources would be included in this task. 3.2.5 Test and Deploy Application. Periodic reviews of functionality, graphics viewing, and data reports of the Handheld Application will be conducted to ensure quality control. Various user tests will be performed during the development process. Modifications and corrections will be accomplished as needed. The final Hand Held Application will be deployed after the customer?s approval. System documentation will be updated and code documentation will be included within the code and other formats. The application will be processed through the MSFC?s Compliance and Usability Board (CUB), and the Marshal Operations Readiness Review (MORR). 3.2.6 Software Development Documentation. A Software Development Plan (SDP) will be written that describes the implementation process. This document will address project monitoring and management of each phase of the project (Plan, Define, Design, Develop, and Implement). A Software Development Guide (SDG) will be written that describes the application and architecture. This document will address system architecture, data architecture, and application design. A Version Description Document (VDD) will be written for each modified application release. This document will address functional information, technical information, and implementation schedule of each release of the application. The Government intends to acquire a commercial item using FAR Part 12. See note 22. Interested organizations may submit their capabilities and qualifications to perform the effort in writing to the identified point of contact not later than 4:30 p.m. local time on August 9, 2006. Such capabilities/qualifications will be evaluated solely for the purpose of determining whether or not to conduct this procurement on a competitive basis. A determination by the Government not to compete this proposed effort on a full and open competition basis, based upon responses to this notice, is solely within the discretion of the government. Oral communications are not acceptable in response to this notice. All responsible sources may submit an offer which shall be considered by the agency. An Ombudsman has been appointed. See NASA Specific Note "B". Any referenced notes may be viewed at the following URLs linked below.
- Web Link
-
Click here for the latest information about this notice
(http://prod.nais.nasa.gov/cgi-bin/eps/bizops.cgi?gr=D&pin=62#121368)
- Record
- SN01100891-W 20060730/060728221503 (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 |