Attachment 1 - EGSS PWS DRAFT 29 Nov 2023.docx

National Aeronautics and Space Administration Enterprise Geospatial Support Services

Performance Work Statement

Contents

1. INTRODUCTION

The National Aeronautics and Space Administration (NASA) Office of Strategic Infrastructure (OSI) has a requirement for Enterprise Geospatial Support Services (EGSS). The EGSS contract will deliver non-personal services under an Indefinite Delivery, Indefinite Quantity (IDIQ) contract to provide institutional geospatial support and services for NASA, with a primary focus on OSI functional areas including facilities engineering and asset management, real property management, management, logistics management, and space environments testing management as defined in NPD 1000.3E. Through the EGSS contract, OSI aims to standardize the institutional geospatial support and services provided at NASA Headquarters (HQ), Centers, and field sites by providing a centrally managed contract vehicle for use throughout the OSI functional communities.

The Contractor shall be responsible for the overall successful performance of the NASA EGSS contract and provide all necessary resources to meet contract requirements. The Contractor shall be responsible for all training and certifications required to accomplish contract requirements. All work completed under this contract shall comply with requirements contained in the applicable documents referenced in Contract Data Requirements List. The release of new revisions of applicable and reference documents during the performance of the contract will supersede those defined in the Contract Data Requirements List at the award of the contract.

1.1 BACKGROUND

NASA is currently undergoing a major initiative to transform how it will strategically procure mission support services to meet the Agency’s evolving needs in the decades to come. Critical elements of the initiative are to: (1) establish clearly defined enterprise requirements and deliverables; (2) streamline acquisition practices and business processes; and (3) reduce redundant and duplicative contracts and other instruments across the Agency. In support of these transformation efforts, OSI is pursuing an enterprise operating model that would standardize geospatial support services provided to its functional communities at NASA HQ, Centers, and field sites.

OSI’s mission is to operate, revitalize, and sustain NASA’s infrastructure, reduce risk, and optimize services by strategically managing environmental, facilities, and logistics programs. Organizationally, OSI is a NASA Mission Support function and consists of four divisions: Environmental Management, Facilities and Real Estate, Logistics Management, and Space Environments Testing. Geospatial support for OSI functions has historically been procured individually by NASA Centers and field sites. This support is currently embedded within a range of support contracts at Ames Research Center (ARC), Armstrong Flight Research Center (AFRC), Glenn Research Center (GRC), Goddard Space Flight Center (GSFC), Headquarters (HQ), Johnson Space Center (JSC), Kennedy Space Center (KSC), Langley Research Center (LaRC), Marshall Space Flight Center (MSFC), Stennis Space Center (SSC), Wallops Flight Facility (WFF), and White Sands Test Facility (WSTF). Current institutional geospatial capabilities vary by location and range from limited use to fully matured enterprise implementations. Additionally, geospatial policy and standards were developed and implemented separately with little to no strategic alignment. Across center implementations, geospatial data may be stored in a variety of formats including but not limited to Oracle Relational Database Management System (RDBMS), SQL Server, PostgresSQL, ArcGIS Data Store, personal/file geodatabases, and shapefiles. Methods of data maintenance vary from direct editing to regular imports from systems of record. Geospatial data and products may be delivered using diverse distribution methods such as Portal for ArcGIS, custom applications, file shares, and Microsoft products (Outlook, OneDrive, SharePoint, etc.). NASA provides task management software to manage internal work and customer requests.

In support of OSI enterprise geospatial strategy, LaRC and JSC have designed and implemented an initial enterprise architecture model that is designed for scalability and supporting unique center level requirements using Service-oriented architecture (SOA) methodology. This architecture is built on a foundation of Oracle RDBMS and Esri ArcGIS Enterprise technology in a virtual server environment provided and managed by NASA IT services. Automated data exchange processes provide integration with other NASA systems such as Computerized Maintenance Management Systems (CMMS) IBM Maximo, NASA Enterprise Directory (NED), SAP and AVEVA PI Systems. Multiple modular, dependency driven, scheduled geo-processing tasks perform a wide variety of data preparation, distribution and analysis functions including denormalization, generalization/anonymization, spatial containment, space utilization and facility planning, DXF/PDF/map book generation, geocoding, reporting, and base map generation. A wiki-based configuration management system and NASA’s Enterprise GitHub system manages revisions, approvals, auditing and deployment of the production software, applications, data schema, metadata, code, and process documents. Portal for ArcGIS through an enhanced front page application provides primary access to editing and read-only content to ensure fast, reliable services. Content is access controlled through appropriate control mechanisms such as the Identity Management and Access Management eXchange (IdMAX) system, NASA Access Management System (NAMS), portal groups and auto-provisioning workflows. Data editing occurs through desktop applications (e.g. ArcGIS Pro, ArcMap, etc.), web enabled services and mobile applications. The versioning capabilities of the enterprise geodatabase are leveraged to implement a quality control process that permits a review of pending edits before reaching production.

OSI is currently in the process of developing governance and data standards to implement an organizational enterprise geospatial capability. These efforts include creating an adaptation of the Department of Defense developed Spatial Data Standards for Infrastructure and Environment (SDSFIE) data model for OSI use, and development of data quality documents to guide creation and maintenance of geospatial data.

1.2 SCOPE

The Contractor shall implement solutions to consolidate and standardize geospatial data and products into a common resilient operating environment using Esri software products. The Contractor shall provide, manage, maintain, and evolve geospatial products and services that meet the requirements as defined in this Performance Work Statement (PWS) and subsequent Task Orders (TO). This support includes enterprise geospatial program technical and organizational support, geospatial data collection and maintenance, geospatial visualization and analysis, and geospatial systems and applications development and implementation. While the EGSS contract may be utilized to provide support to all NASA institutional customers, the principal stakeholders for the EGSS contract are the OSI functional communities at NASA HQ, Centers, and field sites.

Geospatial data collection referred to in this PWS and all subsequent task orders excludes professional surveying and mapping services of an architectural or engineering nature as described in FAR 36.601-4.

IT services subject to mandatory sourcing requirements are excluded from this contract and will be procured using the appropriate mandatory contract as described in NASA Federal Acquisition Regulation Supplement, Appendix A, Section A-102.2.

2. CONTRACT MANAGEMENT

The Contractor shall provide all personnel, equipment, supplies, vehicles, tools, materials, supervision, and other items and non-personal services necessary to deliver geospatial products and services as defined in this PWS and any subsequent TO except for those items specified as Government Furnished Property/Equipment (GFP/GFE).

2.1 Project Management Support

The Contractor shall provide all necessary management to ensure the successful performance of the requirements stated in the contract to include, but not limited to, technical and business functions to plan, implement, track, report, and deliver the required products and services described in the PWS and contract. The Contractor shall:

· Provide a primary point of contact who is responsible for program management of the EGSS contract and who will work with the Government Program Manager on all contract issues.

· When specified in a TO, the contractor shall provide a project manager to serve as the team lead and act as a liaison between the Government Program Manager, the Contractor’s Program Manager, and the team delivering results to the Government.

· In a timely manner notify the Contracting Officer (CO) and Contracting Officer’s Representative (COR) of any issues that could have an adverse impact on successful performance of the contract requirements.

· Provide financial data and other information to the CO and COR as requested in support of data calls and other requests for contract related information.

· Notify the CO and COR of any changes to the contract management structure including the roles and responsibilities of contract management and team leads and the lines of communication between contract management, any subcontractors, and the Government.

· The Contractor shall participate in meetings with the CO and COR when requested to address contract performance issues, process improvements, corrective actions, and other details of contract operations. The Contractor shall maintain frequent communications with the Government regarding technical challenges, accomplishments, findings, problems, risks, corrective actions, progress, and other details of contract operations.

· The Contractor shall schedule and attend general performance management reviews, at times mutually agreed upon with the CO and the COR. The CO, COR, and other Government personnel, as appropriate [e.g., Technical Point of Contact (TPOC)] will meet periodically with the Contractor to review performance. Performance management reviews will be held at least semi-annually; however, the Government reserves the right to conduct these reviews more frequently as needed. The Government and the Contractor will work together in advance of the review to develop the agenda which will include, but not limited to, status and feedback on performance standards, overall contract performance, and any significant events that occurred or are forecasted. Performance management reviews are intended to serve as an opportunity for open dialogue on the current status of the contract. The Contractor shall document the meeting and provide the minutes to the CO and COR.

· It is the Contractor’s responsibility to remain cognizant of and compliant with the most current version of applicable Federal, State, and local laws and regulations, NASA Policy Directives (NPD), NASA Procedural Requirements (NPR), NASA Center Policy Directives, Procedural Requirements, Work Instructions (WI), Permits, and all attachments of this PWS. When two or more directives or instructions apply, Contractor personnel shall comply with the more stringent of the directives or instructions.

2.2 Meeting Support

The Contractor shall support NASA conferences, working groups, and in person or virtual meetings as necessary. This shall include, but not be limited to, responding to data calls and providing input for presentations as well as participation in teleconferences and occasional conference or face to face meeting attendance.

2.3 Configuration Control

The Contractor shall develop, implement, and sustain configuration control for an enterprise data model, spatial and tabular data, metadata, applications, products, and field measurement hardware. The Contractor shall follow all NASA configuration control policies and procedures. Configuration control activities include, but are not limited to:

· Ensure all applicable applications are securely configured to meet or exceed NASA security configuration standards.

· Coordinate with NASA staff to document application configurations and ensure the documentation is updated whenever configurations change.

· Ensure that all IT software and hardware assets are managed and/or operated by the Contractor are configured in accordance with the applicable NASA Security Configuration Standards.

2.4 Property/Inventory Management

The Contractor shall manage all NASA geospatial hardware and software equipment/property, with which the Contractor has been furnished and/or has acquired on behalf of the Government.

The Contractor shall:

• Perform logistics management functions in accordance with NASA’s policies and processes

• Perform property management functions in accordance with NASA’s policies and processes

• Enter all acquired property into the NASA provided system, as directed by COR

• Prepare and maintain an asset management report

• Perform property custodian and user functions in accordance with NASA’s policies and processes

• Perform all requirements of the NASA’s supply chain risk management (SCRM) process before acquiring equipment

• Utilize NASA’s systems to screen for excess property needed in support of the contract and use resulting components in support of the infrastructure in a cost-effective manner

• Identify excess, obsolete, and end-of-life assets, and initiate disposal in accordance with NASA’s policies and processes

• Ensure all equipment removed from service have all data sanitized prior to excess in accordance with NASA policies and processes

• Utilize NASA property tags process for all existing and new assets

• Establish loan agreements for all Installation Accountable Government Property (IAGP) that will be utilized at off-site locations

• Conduct an annual physical inventory of all provided software/hardware provide results to the NASA COR

• Track all changes, such as locations, disposals, etc., monthly to the NASA COR in the NASA approved system

2.5 Staffing

The Contractor shall provide adequate staffing levels with the required training and development to maintain core competencies, enhance performance, and advance capabilities to meet contract requirements. The Contractor shall ensure applicable training is compliant with all sections of this PWS and subsequent task orders. The Contractor shall coordinate with the Government to cross-utilize the workforce to meet evolving requirements among individual organizations and across work locations, as required.

2.5.1 Work Schedule

Normal business hours are Monday-Friday 8:00 AM to 4:30 PM with core hours of 9:00 AM to 3:00 PM local time. The NASA workday encompasses a 6:00 AM to 6:00 PM flexible work schedule to allow for flexibility of shifts. The Contractor shall provide adequate staffing during these normal work hours and will be able to adjust shifts to meet programmatic milestones. Some positions will require occasional instances of performing services outside normal working hours, such as requirements for working an extended day, working late (working beyond the mutually agreed ending time for any day), or working on a weekend. The Contractor is responsible for managing employees’ work schedules and compensation accordingly, as needed, to provide services outside normal working hours.

2.6 Quality

2.6.1 Quality Control

The Contractor shall develop, implement, and maintain a comprehensive inspection system that assures compliance with all requirements of this contract and its associated TOs. The Contractor shall submit a Quality Control Plan that demonstrates how it will maintain an inspection system acceptable to the Government covering the services under this contract.

2.6.2 Quality Assurance Surveillance Plan

The Government shall evaluate the Contractor’s performance under each Task Order in accordance with a Quality Assurance Surveillance Plan (QASP). When the proper level of performance is not met, the CO will issue a written Corrective Action Request (CAR) to the contractor. CORs will follow the methods of surveillance specified in the Government’s QASP. Government personnel will record all surveillance observations. When an observation indicates defective performance, the COR will require the contractor TO manager or representative to acknowledge the observation on the CAR. The acknowledgement of the observation does not necessarily constitute concurrence with the observation, only acknowledgment that they have been made aware of the defective performance.

3. TASK REQUIREMENTS

3.1 Enterprise Program Support

The Contractor shall provide geospatial program support that includes drafting of plans, policies, guidance, and standards; establishing geospatial program requirements and reporting methods; development of geospatial strategic plans to enhance enterprise capabilities; and customer and helpdesk support.

3.1.1 Administrative Support

The Contractor shall provide technical support for drafting of policies, guidance, standards, strategies, and plans. Contractor developed plans shall include roles and responsibilities, milestones, standards, procedures, and measures to determine progress and completion. This support shall also include participation in and administration of functional working groups, communities of practice, and other meetings and forums.

3.1.2 Technical Requirements

The Contractor shall provide support for the identification of requirements and conversion to execution plans for establishing or enhancing geospatial capabilities. Support shall include technical evaluations of existing geospatial architecture, applications, system integrations, hardware, and commercial software products. The Contractor shall provide recommendations on enhancement of existing technologies and data sources, and requirements for development or customization of new solutions to improve the capability and capacity of geospatial data and services provided to agency stakeholders.

3.1.3 Strategic Support

The Contractor shall provide technical support in the development of geospatial strategies to guide advancement and optimization of the OSI enterprise geospatial capability. The contractor shall develop program advancement strategy documentation, to include but not limited to, plans, strategies, approaches, standard operating procedures, needs analyses, feasibility studies, business case analyses, cost/benefit analyses, performance measures, maturity models, governance models and charters, best practices, briefings.

3.1.4 Geospatial Standards

The Contractor shall provide technical support for the development of geospatial data and metadata standards. This support shall include but not be limited to developing and implementing logical and physical data models, drafting geospatial data quality standards documents and data migration plans, and coordinating review and updates to standards and plans. The Contractor shall ensure that the most current standards versions and industry standard procedures are utilized in support of OSI managed geospatial data and systems.

3.1.5 Enterprise Architecture

The Contractor shall provide Enterprise Architecture design and implementation support including but not limited to; evaluation of existing architecture framework to document current state, developing recommendations for optimization and enhancements to increase efficiency, and designing and implementing future state architectures. Architecture products shall be built in alignment with NASA IT policy and compatible with other NASA enterprise architectures including interoperability with commercial software packages used to create the architectures. The contractor shall coordinate with Office of Chief Information Officer (OCIO), OSI and Center IT strategic leads, data owners, and others as required to ensure alignment with NASA and organizational data and architecture strategies.

3.1.6 Customer Support

The Contractor shall provide customer support and helpdesk services to NASA stakeholders both on-site and remotely as needed. This support shall include but is not limited to: troubleshooting geospatial software and hardware issues, software license management, data requests, creation of geospatial products, consultation, and requests for changes or upgrades to existing capabilities. Customer support requests shall be recorded, tracked, and reported using professional tools, techniques, and procedures.

3.2. Outreach and Training

OSI is pursuing an enterprise geospatial capability which will serve as a comprehensive platform for innovation, analytics, location intelligence and insights. Raising awareness and increasing spatial literacy within the OSI workforce will improve long term competencies and drive adoption of geospatial technology. The contractor shall provide outreach and training as described in this PWS and any subsequent task orders.

3.2.1 Outreach

The Contractor shall support outreach plans and activities to ensure the widest adoption and use of geospatial applications, tools, and services. The Contractor shall develop and update materials such as capability and program presentations, storymaps, white papers, and fact sheets. The Contractor shall provide support in managing virtual and onsite workshops, meetings, or other outreach activities which will vary from small group settings to large audiences.

3.2.1 Training

The Contractor shall provide training support including development of training plans, creating training materials, and conducting geospatial technology training. The Contractor shall prepare technical training aids to include user guides, digital presentations, and exercises. Training delivery methods include formal webinars, training videos, tutorials, demonstrations, and virtual or on-site courses or workshops. Training topics include but are not limited to use of ArcGIS desktop software, use and customization of ArcGIS enterprise maps and web applications, geospatial data analysis, GNSS user training, and field collection methods. Training audience shall include NASA civil servants, contractors, tenants, and users as applicable to meet PWS requirements.

3.3 Geospatial Data Creation and Maintenance

The Contractor shall create, validate, manage, and maintain data to support OSI functional areas. This support shall include both spatial and non-spatial data as required to support integration and interoperability with NASA business systems and processes. Data support shall include but is not limited to development and implementation of data strategy, data migration, and utilization of best practices and procedures to properly create, maintain, store, distribute, and enhance the value of data throughout the complete data life cycle.

3.3.1 Data Acquisition

The Contractor shall provide support for data collection/creation and validation of vector and raster data necessary to support OSI functional areas. Support for creation and acquisition of data shall conform to Federal, NASA, and industry standards. Data acquisition methods shall include, but are not limited to data conversion, field data collection, feature digitization and extraction, and user generated content. Requirements for data formats, spatial coordinate systems, and spatial accuracy will be provided at the task order level.

3.3.1.1 Data Conversion

The Contractor shall develop and perform processes for data conversion including but not limited to; extract, transform, and load for conversion of existing spatial data; scanning, digitizing and georeferencing hardcopy or digital maps, drawings, or images; transformation of data from/to various raster or vector formats (e.g., CAD, BIM, Photoshop, Adobe); support for COTS software plugins (e.g. ArcGIS for AutoCAD).

3.3.1.2 Field Data Collection

The Contractor shall support field collection and validation of data using field collection methods including but not limited to; use of GNSS technologies (survey, resource, or mapping grade), surveying technologies (e.g., RTK, Total Station, digital level), remote sensing technologies (e.g., LIDAR, Thermal, UAS, GPR, range finders), and field collection devices and applications (e.g., mobile, Survey123, ArcGIS Field Maps). Field data collection shall include collection of spatial data and associated feature attributes, metadata, and stakeout and markup of spatial features/geometry (e.g., underground utilities).

3.3.1.3 Unmanned Aircraft Systems (UAS)

The contractor shall support operation of UAS for collection of geospatial data. The Contractor shall ensure UAS operators meet all NASA and FAA flight safety certification requirements and adhere to all requirements outlined in NPR 7900.3D and any additional NASA guidance, including designation as a NASA UAS Pilot and/or Ground Control Station Operator.

3.3.2 Metadata

The Contractor shall create and maintain current, relevant, and standardized metadata for all geospatial data layers which meet or exceed Federal Geographic Data Committee (FGDC) approved standards. The Contractor shall utilize applicable metadata tools and templates to develop, maintain, and publish metadata. The Contractor shall solicit metadata with all data requested from outside sources and shall provide metadata with all geospatial data transfers.

3.3.3 Data Migration

The contractor shall perform geospatial data migration support including pre-migration planning, schema mapping, data transformation, loading, and post migration data cleanup as needed to support alignment with established spatial data standards. The contractor shall coordinate migration plans with data stakeholders for awareness and develop strategies for mitigation of any potential disruption of service.

3.3.4 Data Quality

The Contractor shall provide geospatial data quality assurance and/or quality control support using industry standard methods. Data quality support shall include data quality control process design, development, documentation, implementation, coordination, and management. The Contractor shall ensure that geospatial data (including geometry, topology, attribution, and metadata) is compliant with Federal government and NASA guidance including accuracy and completeness standards. The Contractor shall design, develop, document, implement, configure, and manage automated scripts or processes used to perform data quality checks and reporting methods. Geospatial data quality and availability shall be continuously improved to support timely and informed decision support.

3.4 Geospatial Products and Services

3.4.1 Geospatial Products

The Contractor shall produce geospatial products as requested to meet OSI stakeholder requirements. Geospatial products include static or interactive visualizations for geographic analysis including but not limited to maps, dashboards, models, simulations, and animations and shall be delivered in digital, hardcopy, or web-based formats as applicable to meet mission requirements. The Contractor shall follow government provided or industry standard cartographic layout and portrayal specifications and standards.

3.4.2 Analysis

The Contractor shall provide geospatial analysis and modeling support for OSI functional mission areas utilizing innovative tools and methods. Analysis support shall include a multitude of techniques as needed to support requirements including, but not limited to, simulation and modeling, proximity, statistical, interpolation, regression analysis, network analysis, photogrammetry, temporal or image analysis. Geospatial data, models, reports, or other products that are generated as a result of analysis methods shall conform to provided guidance and industry standards.

3.4.3 Application Development/Configuration

The Contractor shall provide support in the development and/or configuration of geospatial applications, tools, and scripts to meet OSI functional area requirements. This support shall include but is not limited to assessment, planning, design, development, testing, integration, administration, maintenance, operational support, and documentation for new and existing applications and tools. The Contractor shall coordinate with OCIO, OSI, and other required stakeholders for approval as required for all application development activities. The Contractor shall ensure development activities are performed in compliance with all NASA and Federal policies. The Contractor shall use industry best practices for continuous integration and continuous development/deployment of applications.

image1.png