Attachment 2 - Mission Enabling Services Contract (MESC) Draft SOW.pdf

C-1

SECTION C – DRAFT STATEMENT OF WORK

MISSION ENABLING SERVICES CONTRACT (MESC)

C-2

Table of Contents Introduction

1 Baseline A: NAMIS Services

1.1 Scope

1.2 General Requirements

1.2.1 Contract Management

1.2.2 Financial Management

1.2.3 Task Management

1.2.4 Task and Project Control

1.2.5 Planning and Execution

1.2.6 Change Management

1.2.7 Acceptance of Software

1.2.8 Briefings, Schedules, and Budgets

1.2.9 Requirements Analysis & Development Services

1.2.10 Process Analysis Services

1.2.11 Quality Assurance and Process Certifications

1.2.12 Technology Evaluations

1.2.13 Government Property

1.2.14 Non-Disclosure Agreements (NDAs)

1.2.15 Information Technology Security

1.2.16 Emergency Preparedness

1.2.17 Regulatory Impacts

1.2.18 Safety and Health

1.3 Infrastructure Services Requirements

1.3.1 Configuration Management and Control

1.3.2 System Testing and Quality Control

1.3.3 Implementation Services

1.3.4 System Integration Services

1.3.5 Infrastructure Support and Operations

1.3.6 Server and System Administration

1.3.7 Disaster Recovery and Continuity of Operations Plan (DRCOP)

1.4 End-User Support Services Requirements

1.4.1 User Support and Help Desk

C-3

1.4.2 User Training

1.5 Software Development, Maintenance, and Sustaining Engineering

1.5.1 Software Maintenance and Sustaining Engineering

1.5.2 Software Development and Modification Services

1.6 Technical Publications and Document Management

2 Baseline B: FOD Mission Enabling Services

2.1 Scope

2.2 General Requirements

2.2.1 Contract Management

2.2.2 Change Management

2.2.3 Technical Meeting Support

2.2.4 Technology Evaluations

2.2.5 Logistics

2.2.6 Government Property

2.2.7 Non-Disclosure Agreements (NDAs)

2.2.8 Information Technology Security

2.2.9 Emergency Preparedness

2.2.10 Safety and Health

2.3 Infrastructure Service Requirements

2.3.1 Configuration Management and Control

2.3.2 FOD IT (FIT) System Sustaining Engineering Support

2.3.3 FOD IT (FIT) System Operations Support

2.3.4 Collaboration and Web Services Support

2.4 End-User Support Requirements

2.4.1 Enhanced User Support Services

2.4.2 Standard User Support Services

2.5 Software Development, Maintenance, and Sustaining Engineering

2.5.1 Software Maintenance and Sustaining Engineering

2.5.2 Software Development and Modification Services

2.6 IT Resource Management (ITRM) Support

2.7 FOD Project Information System CM and Support

2.8 FOD Business Office CMDM Support

2.9 Facility Utilization and Optimization Support

C-4

2.10 Schedule Support

3 IDIQ

3.2 General Requirements

3.2.1 Contract Management

3.2.2 Financial Management

3.2.3 Change Management

3.2.4 Technology Evaluations

3.2.5 Government Property

3.2.6 Non-Disclosure Agreements (NDAs)

3.2.7 Information Technology Security

3.2.8 Emergency Preparedness

3.2.9 Safety and Health

3.3 High-Level Requirements and Work Characterization

3.3.1 Management and Mission Support Services

3.3.2 Advanced Research and Development Technology Support

Appendix A: Acronyms

C-5

Introduction

The purpose of the Mission Enabling Services Contract (MESC) is to provide development, sustainment, and maintenance of specialized and highly specialized mission-enabling applications and services to the JSC Flight Operations Directorate (FOD) and its affiliate organizations. The MESC requirement spans the flight support requirements of NASA/JSC for the benefit of its external customers and partners, including, but not limited to, other NASA centers, International Partners, other Government organizations, and affiliated commercial enterprise partners.

The MESC contracting vehicle consists of three parts: two single-award baselines and a multiple-award Indefinite Delivery/Indefinite Quantity (IDIQ) component. Under the terms of this solicitation, a "baseline" comprises activities that satisfy known, continuous US government requirements that exist independent of another baseline or any task order under the IDIQ vehicle.

The two single-award baselines are the following:

• Baseline A: NASA Aircraft Management Information System (NAMIS) Services

• Baseline B: FOD Mission Enabling Services

The multiple-award IDIQ component has the same Baseline B scope and may be used for new content not identified at the time of contract award at discretion of the government. Additionally, IDIQ covers advanced research and development technology support.

C-6

1 Baseline A: NAMIS Services

Baseline A provides the requirements for the comprehensive support for the NASA Aircraft Management Information System (NAMIS), an integrated, module-based, custom software suite that supports aircraft flight operations across NASA and other Government Agencies. NAMIS is an Agency-wide system in use by Ames Research Center (ARC), Armstrong Flight Research Center (AFRC), Glenn Research Center (GRC), NASA Headquarters, Johnson Space Center (JSC), Kennedy Space Center (KSC), Langley Research Center (LaRC), Marshall Space Flight Center (MSCF), Stennis Space Center (SSC), and Wallops Flight Facility (WFF). NAMIS is also used by other Government agencies and external organizations.

NAMIS operates under the authority of the Office of the NASA Chief Information Officer. NAMIS is hosted by the Aircraft Operations Division of FOD at JSC. For other agencies and organizations, NAMIS may be hosted at JSC or hosted locally by the user on user resources. NAMIS is managed by the NASA NAMIS Project Manager and the NASA NAMIS Technical Manager reporting to the NAMIS Steering Committee.

NASA operates an extensive variety of types, series, and models of aircraft. Many are special purpose or heavily-modified aircraft. Operations and maintenance of such a diverse fleet requires extensive technical documentation and publications support, much of which is incorporated into NAMIS and all of which is included in the scope of Baseline A. The documentation consists of technical publications, including maintenance manuals, operating manuals, Service Bulletins (SB), Airworthiness Directives (AD), and Time Compliance Technical Orders (TCTO). The technical documentation is generated by multiple sources, including the military, the Original Equipment Manufacturer (OEM) and the Federal Aviation Administration (FAA). NASA must receive, review, and integrate all of the documentation from all of the sources and generate appropriate NASA technical documentation.

Frequently, NASA aircraft missions require that NASA design, fabricate, test, and implement aircraft modifications and configuration changes. Most of these changes require NASA, or the operating organization, to generate technical documentation to support and provide continued instructions for airworthiness. Most of these modifications are unique to the Agency’s aircraft and require expertise in multiple aeronautical engineering disciplines. The exact nature of the aircraft modifications requiring generation of documentation cannot be determined in advance.

NAMIS users depend on multiple computer-based systems and tools for safety and mission-critical decision support; consequently, this effort is heavily focused on quality assurance and quality control of all the aircraft operations support system components.

C-7

1.1 Scope

The scope shall include all the life-cycle support elements for an enterprise-level, agency-wide project, including project management, requirements analysis, software development, testing, and verification. This includes the upgrading and integration of NAMIS and a range of data management systems to support all aspects of aviation and aircraft activities including maintenance, quality assurance, technical publications and documentation, engineering, and operations. This includes IT security management, Disaster Recovery and Continuity of Operations Plan (DRCOP) development and support, remote access support, sustaining support of deployed components, and execution of administration processes. Responsibilities also include supporting strategic and enterprise planning for the migration of data management systems into a cost-effective open systems architecture that provides users with accurate and timely information.

The scope shall include sustaining and modification of the NAMIS modules as necessary to adapt the system to provide support for other Agency activities, as required. NAMIS consists of seven modules:

a. Flight Scheduling Application

b. Flight Data Capture

c. Flight Records & Currency

d. Aircraft Logistics System

e. Work Card System

f. Aircraft Maintenance System

g. NASA Web Reporting Site

The scope shall include sustaining and modification of the following supplemental applications as well as those listed in Attachment J-XX, List of Government-Furnished Computer Software:

a. Engineering Work Order Application

b. ViPER (Virtual Publications Electronic Repository)

c. QMT (Quality Management Tool)

d. NAARS (NASA Aviation Anomaly Reporting System)

e. Application Deployment Utility

f. Attachments Web Service

g. Nametags

h. Purchase Order (1307)

i. AOD Web Reporting Site

j. Aircraft Operations Web Site

k. Qualification Requirements

l. Pack and Go

m. Document Integration Tool

n. Help Desk Application

o. Infrastructure Application

p. Engineering Work Order Application

C-8

The scope shall include all services relating to implementing the NAMIS system at or on behalf of other agencies, including data cleansing, data loading, agency-specific capabilities, system configuration, development of training programs and materials, training, and user support.

The scope shall include providing IT services related to implementing Center-based and Agency-wide systems, and includes all the usual and customary efforts implied by and associated with migrating legacy systems to automated processes, upgrading existing computer-based systems, and sustaining such systems.

The scope shall include adapting the NAMIS modules for tracking and management of newly identified air and ground vehicles and other assets approved by the Government.

The scope shall extends to the associated systems that share data, hardware, software, or human resources with the NAMIS system. Examples include: security systems, system service interfaces, system data exchange interfaces, etc.

The scope shall include providing subject matter expertise at the request of the Government in all phases and aspects of aircraft operations, aircraft engineering, aircraft and ground safety, and NASA, Occupational Safety and Health Administration (OSHA) and FAA regulatory requirements relating to safety and or flight operations.

The scope shall include system engineering, operations support and sustaining engineering, application development, system maintenance and operations, data management services, system integration services, infrastructure upgrades, security management, and prototyping.

The scope shall include development and maintenance of the full spectrum of services associated with aircraft documentation.

The scope shall include the full range of integration and implementation services for any Federal agency or external organization that enters into an agreement with NASA

1.2 General Requirements

This section of the Statement of Work (SOW) specifies the general requirements applicable to Baseline A.

1.2.1 Contract Management

The Contractor shall provide leadership, management oversight, direction, and problem resolution for all functions performed under Baseline A. The Contractor shall provide contract management to act as the primary interface to the Contracting Officer (CO), Contracting Officer Representative (COR), NASA NAMIS Project Manager, and the NASA NAMIS Technical Manager. The Contractor shall:

a. Provide a management interface who is authorized to direct day-to-day work, coordinate with NASA on contractual matters, respond to questions and action items from NASA, and resolve problems.

b. Prepare program performance metrics and report program performance.

c. Accept and utilize existing hardware, software, and documentation unless otherwise

C-9 agreed with NASA.

d. For activities performed under this contract, adhere to the JSC Quality Management

System (QMS) and appropriate FOD quality management documentation.

e. Comply with Attachment J-XX, List of Applicable Documents.

f. Integrate with and utilize, to the maximum extent practicable, the NASA-established contract management system that includes but is not limited to order processing, contract correspondence, and Data Requirements Document (DRD) delivery.

1.2.1.1 Project Management and Staffing

The Contractor shall organize and institute integrated processes and tools for managing the products and services specified in Baseline A, in accordance with the approved Contract Management and Staffing Plan (Attachment J-XX).

The Contractor shall perform activities at the request of the Government that support research, development, acquisition, and sustainment efforts across a broad spectrum of functional disciplines in order to effectively assist in the implementation of Government programs.

1.2.2 Financial Management

The Contractor shall provide project support in the area of financial management and includes, but is not limited to:

a. Conducting financial studies and research

b. Evaluating project funding plans and changes

c. Providing comments and recommendations for program guidance

d. Providing project budgeting and cost estimating

1.2.3 Task Management

For each task, the Contractor shall prepare a Task Management Plan describing the technical approach, organizational resources, management controls, and schedule to be employed to meet the cost, performance, and schedule requirements for authorized tasks. The Contractor shall provide a Work Breakdown Structure (WBS) that will allow project management and control to the subproject and task level. The Contractor shall provide monthly progress status which includes financial reports showing the cost-to-date and projected cost to completion by month for each project or major task under the SOW. Supporting or associated other direct charges (ODCs) shall be allocated to the appropriate task by the contractor. Status reports shall be provided to monitor progress to the CO, COR, NASA NAMIS Project Manager, and NASA NAMIS Technical Manager by the contractor.

1.2.4 Task and Project Control

Due to shifting budgets and mission priorities and because the Government desires the ability to capitalize on opportunities discovered during development and operations, project schedules and priorities can shift. Based upon the Government’s evaluation of priorities and available resources, the Government will make a determination of when to proceed on a major project and will issue written instructions that will include an Authority to Proceed (ATP) for the task or project. Upon receipt of an ATP, the contractor shall provide implementation plans and schedules using standard

C-10 project planning tools to the Government. Each major project will be independently tracked for technical and financial performance. The Task Management Plan shall be updated as appropriate to reflect each project or task as it is added to the on-going effort.

1.2.5 Planning and Execution

The Contractor shall assist in strategic planning and execution of projects. The Contractor shall support the development of technology roadmaps, risk management plans, and strategies to support acquisition and programmatic decisions relative to project and mission objectives.

1.2.6 Change Management

The Contractor shall implement changes to hardware and software components managed under Baseline A. These changes include corrections of issues, sustaining engineering change requests, and any other change authorized by the Government. The Contractor shall update all related documentation when changes are released.

The Contractor shall integrate with and utilize the NASA-established discrepancy reporting program and systems for the submittal, status, review, ranking, and reporting of discrepancies, including, but not limited to Incident Reports (IR), Anomaly Reports (AR), Issues, etc.

The Contractor shall track discrepancies against the released code base and the NASA requirements specifications, and track change requests against the user requirements.

The Contractor shall perform scheduled and emergency releases. Scheduled releases shall occur no less frequently than once per quarter and shall consist of corrections of discrepancies/issues as well as changes and enhancements to the existing code base. Emergency releases shall be made on an as-required basis upon approval of the NASA Technical Manager.

Routine changes to aircrew flight currency requirements shall be released by the contractor immediately upon completion of successful user acceptance testing.

The Contractor shall provide changes to the NAMIS components based on requirements as specified and approved by the NASA NAMIS Technical Manager and the NASA NAMIS Configuration Control Board (CCB). Corrections of issues shall be implemented as approved by the NAMIS CCB. Change Requests (CRs) shall be executed as approved by the NAMIS CCB.

The Contractor shall update all related documentation when changes are released.

1.2.7 Acceptance of Software

The task sub-task project plans will include detailed acceptance criteria and standards for specific software deliverables. The general acceptance criteria for all software deliverables developed or customized under this SOW is completed through acceptance testing by the users.

1.2.8 Briefings, Schedules, and Budgets

The Contractor shall assist in the development of briefings, schedules, and budgets. As required, the Contractor shall provide periodic status reports to the Government.

C-11

1.2.9 Requirements Analysis & Development Services

The Contractor shall provide services in support of requirements analysis and development. These analyses shall include business requirements, functional requirements, and user requirements as well as agency, center, program, project, system, and design requirements development. This shall include management and tracking of all forms of requirements from “cradle to grave” including business requirements, functional requirements and design requirements. Services in this task area are directed at the requirements relating to the tools and software that will be developed and supported under Baseline A.

1.2.10 Process Analysis Services

When requested, the Contractor shall support process-reengineering by performing independent analyses of Government processes. The Contractor shall provide written recommendations for process improvements to include justification and basis for recommended changes along with impacts of implementing, or failing to implement, the recommendations.

1.2.11 Quality Assurance and Process Certifications

The Contractor shall possess certification of its quality assurance quality control processes applicable to software development in accordance with the Software Engineering Institutes Capability Maturity Model (CMM) or Capability Maturity Model Integration (CMMI) Level 3. An independent certifying authority must provide this certification.

The Contractor shall employ procedures developed and certified in accordance with the CMMI Level 3 or greater unless specifically waived in writing by the NASA NAMIS Project Manager, NASA NAMIS Technical Manager, and COR. This requirement shall extend to all deliverables by subcontractors retained or employed by the Contractor for Baseline A work.

1.2.12 Technology Evaluations

When requested by the Government, the Contractor shall provide recommendations for commercial alternatives (hardware software tools, components or complete solutions) that shall include an evaluation of existing Commercial-Off-The-Shelf (COTS) products, as well as products available through Government-Off-The-Shelf (GOTS) solutions. The Contractor shall provide life-cycle cost benefit analyses of the recommended commercial alternatives.

1.2.13 Government Property

Physical equipment, as enumerated in Attachment J-XX, List of Installation-Accountable Government Property is classified as Government property. “Contractor-acquired property” means property acquired, fabricated, or otherwise provided by the Contractor as a direct contract charge to NASA for performing a contract and for which NASA has title.

Attachment J-XX, List of Installation-Accountable Government Property, identifies the on-site Government physical property made available on a no-charge basis for use in performance of MESC.

NASA will provide onsite contractors with standard NASA End User Services and Technologies (NEST) computer seats and phone seats as Agency Institutional IT. NASA is responsible for support

C-12 and asset management of Agency Institutional IT, including hardware and all standard software. Mobile phone seats will also be provided to Contractor personnel who are on-call for help-desk and customer assistance at the discretion of the Government.

The Contractor shall submit updates to the List of Installation-Accountable Government Property, in accordance with the schedule defined in Attachment J-XX.

The Contractor shall document and maintain MESC Government property management processes and procedures in accordance with DRD-XX, Government Property Management Plan (PMP).

The Contractor shall utilize the Government s property tracking system for MESC property identified in Attachment J-XX, List of Installation-Accountable Government Property. The Contractor shall provide custodians to input and manage data in the Governments property tracking system for property provided under this contract.

The Contractor shall be the delegated property administrator and shall designate a point-of-contact for MESC Government property administration and management.

1.2.14 Non-Disclosure Agreements (NDAs)

The Contractor shall provide a nondisclosure statement (per company policy), a signed individual nondisclosure statement for each person supporting specific tasks as identified by the Government, and a summary of the procedures for information control and protection that are applicable to all personnel supporting those tasks.

1.2.15 Information Technology Security

The Contractor shall provide support for the annual NASA JSC Security Plan requirements as set forth in NPR 2810.1 and shall ensure that the NAMIS system satisfies applicable certification and accreditation standards. This shall include ensuring the NAMIS components meet NASA and organizational security standards. Reference DRD-XX, Contractor Information Technology (IT) Security Management Plan and Reports.

1.2.16 Emergency Preparedness

The Contractor shall institute and implement processes and procedures to ensure emergency preparedness and disaster recovery, in accordance with DRD-XX, Emergency Preparedness Disaster Recovery Continuity of Operations Plan (DRCOP).

1.2.17 Regulatory Impacts

The Contractor shall provide appropriate business case and risk analysis of applicable federal regulations, federal laws, and directives, including impacts or constraints arising from applicability of these regulations, laws, and directives to the products and services supported under Baseline A.

Examples include, but are not limited to:

a. FAA Airworthiness Directives

C-13

1.2.18 Safety and Health

The contractor shall perform tasks to ensure the protection of personnel, property, equipment, and the environment in contractor products and activities generated in support of institutional and spaceflight program objectives. To ensure compliance with pertinent NASA policies, requirements, federal, state, and local regulations for safety, health, environmental protection, and fire protection, the contractor will develop and implement a safety and health program per a NASA-approved safety and health plan. The “JSC Safety and Health Requirements” document provides detailed requirements and instructions regarding safety and health procedures and policies at JSC and is incorporated by reference into all JSC contracts when performance is on site at a JSC facility. It can be viewed at http://jscHandbook.jsc.nasa.gov.”

1.3 Infrastructure Services Requirements

This section of the SOW specifies the services requirements for the IT infrastructure in Baseline A.

1.3.1 Configuration Management and Control

The Contractor shall provide configuration control of all requirements and specifications. The Contractor shall provide configuration management and tracking for all code. Configuration and management tracking shall include traceability of all requirements through all levels, i.e.

requirements through acceptance tests. Configuration management shall also extend to the hardware and full software load on each server supported under Baseline A.

1.3.2 System Testing and Quality Control

The Contractor shall provide testing and quality control services for all deliverables under Baseline A. This shall include documentation of appropriate measurements and metrics. Test and quality control procedures shall be tailored as appropriate and include the following:

a. Functional testing

b. Performance testing

c. Module testing

d. Integration testing

e. Reliability testing

f. User testing

g. Parallel testing

h. Performance testing

i. DRCOP testing

All implementations shall include test plans and processes that are designed to exercise the system capabilities. Tests shall exercise all software components.

1.3.3 Implementation Services

The Contractor shall provide implementation support to include:

a. Data extraction from legacy systems

b. Data cleansing http://jschandbook.jsc.nasa.gov/

C-14

c. Data loading

d. Data conversion services

e. Ad hoc reports and queries

f. Configuration, operation, and maintenance of the system

g. Security management for the system

h. DRCOP development

i. System sustaining engineering

j. System administration including system security management and operations

1.3.4 System Integration Services

The Contractor shall provide integration services to integrate products delivered under this baseline with appropriate legacy and external systems. This may include, but is not limited to, any or all of the following systems and any and all other related systems developed under or acquired by the Government:

a. The electronic catalog system of the Air Force (D043)

b. The military electronic invoicing system, known as MILSBILLS

c. Military Standard Requisitioning and Issue Procedures (MILSTRIP)

d. Other contractors systems conditioned on agreement between the contractors and the approval of the Government (Example: Deltek Time and Expense suite)

e. The NASA Integrated Enterprise Management (IEM) Program Core Finance

Systems System, Applications and Products (SAP)

1.3.5 Infrastructure Support and Operations

The Contractor shall provide data management services for the NAMIS IT infrastructure and its support systems. The data management services include database administration (DBA) support, web site administration and support, product administration support for the Database Management Systems (DBMSs), data transfer and conversion services, system security support, and disaster recovery plan development and support. The Contractor shall ensure the NAMIS system is operational and available for all users for all scheduled work periods except for scheduled down-periods for software upgrades and hardware maintenance. Usual and customary tasks associated with on-going operations and maintenance of the NAMIS infrastructure shall be performed. These tasks include planning for, implementation of, and upgrades to IT systems, facilities, and network components. Examples may include, but are not limited to:

a. Security monitoring and administration including network monitoring and management

b. DRCOP execution

c. Supporting and upgrading network interfaces, components and facilities infrastructure, to include administering web services

d. Hardware and software management including maintenance, upgrades, and equipment-replacement planning

e. Coordinating detached operations of NAMIS on transportable computers when deployed aircraft do not have wide area networking or internet access, and ensuring the data is properly merged upon return of the aircraft

C-15

1.3.6 Server and System Administration

The Contractor shall provide administrators for the NAMIS servers. The Contractor shall provide provisioning, credential management, access control, data and system backup services, and system monitoring.

Backup services performed by the contractor shall ensure that no more than one days file system changes are lost in the event of server failure. The Contractor shall ensure that no Structured Query Language (SQL) Server data is lost in the event of a server failure.

The Contractor shall ensure that all software modules are available during all scheduled and unscheduled work periods except for scheduled down-periods for software upgrades and hardware maintenance.

The Contractor shall maintain the software configuration of all NAMIS server components in a secure manner. Software updates, security patches, and other configuration changes shall be made to production systems in a timely fashion, but only after the changes have received appropriate verification in non-production environments. The Contractor shall provide the ability to roll back configuration changes to the last good configuration.

1.3.7 Disaster Recovery and Continuity of Operations Plan (DRCOP) The Contractor shall maintain a primary system and a disaster recovery system for NAMIS. Loss of the primary system shall be recovered by the contractor to a Disaster Recovery system within 8 hours of system loss. Localized component or system failures shall also be recovered by the contractor within 8 hours of component loss. In the event of a server failure, the Contractor shall ensure that the server hardware and operating system are recovered to a fully functional state within 8 hours of notification of the failure. The contractor shall return the database related applications to operability within 8 hours of the failure.

1.4 End-User Support Services Requirements

The Contractor shall provide user support services for the systems listed in Attachment J-XX, List of Installation-Accountable Government Property.

The Contractor’s support shall include end-user training, implementation support for the receiving organization, and sustaining support for the deployed components.

1.4.1 User Support and Help Desk

The Contractor shall provide end-user and Help Desk support for users of NAMIS and its associated data management systems, IT Systems, and infrastructure for all shifts at all locations where the NAMIS components are deployed. The contractor shall provide Help-Desk support via on-site and or

C-16 on-call services. The contractor’s support shall be focused on process analysis to determine root causes of user, process, and software issues for incorporation into remediation plans.

1.4.2 User Training

The Contractor shall develop training programs and materials for the NAMIS modules. The contractor shall focus training aides on user functions within each module. The Contractor shall provide updates to the NAMIS user-documentation and training to ensure the documentation is consistent with changes to the NAMIS components.

The Contractor shall provide training to new users and refresher training for current users of the systems.

1.5 Software Development, Maintenance, and Sustaining Engineering This section of the SOW specifies the software development, maintenance, and sustaining engineering requirements applicable to Baseline A.

1.5.1 Software Maintenance and Sustaining Engineering

The Contractor shall provide sustaining engineering for the products and services described in Baseline A. The Contractor shall provide initial implementation of only the required components of a system, then prioritize and schedule incremental maintenance upgrades and emergency releases to correct defects to the systems as agreed to by the Program/Technical Monitor of the contract.

NAMIS systems that will require software sustaining engineering services include those listed in Attachment J-XX, List of Government-Furnished Computer Software.

1.5.2 Software Development and Modification Services

The Contractor shall provide software development services for customized tools and specialized applications including requirements analysis, process engineering plans, and schedules.

Examples include but are not limited to

a. Modifications and upgrades of the NAMIS components for deployment to other agencies, either through NASA hosting of the servers, or local hosting by the receiving agency.

b. An Executive Information/Data Warehouse system to collect, integrate, analyze and report on financial, operational, logistical, trend analysis, and performance data relating to aircraft operations.

c. Add additional NAMIS reporting capabilities to support the NASA submission to the General Services Administration Federal Aircraft Interactive Reporting System

(FAIRS).

d. Productivity tool development.

e. Data Warehousing and Business Intelligence capabilities.

f. A basic data warehouse based on data contained within NAMIS for flight time

C-17 analysis for both aircrew and aircraft, logistics data, including number and costs receipts, repairs, and issues from stock, and for aircraft maintenance records.

g. Upgrades to the ViPER Application SharePoint-based system.

h. Upgrades to the Engineering Work Order Application SharePoint-based system.

i. Modify NAMIS to enhance its suitability for non-NASA customers that operate public aircraft, such as allowing easier installation and more user control over the software configuration and business process options.

NAMIS systems that may require software modification services include those listed in Attachment J-XX, List of Government-Furnished Computer Software.

1.6 Technical Publications and Document Management

The Contractor shall provide support for the technical documentation and publications functions associated with NAMIS that support all aspects of aviation and aircraft activities. This includes but is not limited to the technical data which must be referenced in NAMIS Maintenance Actions, or used by operators and Quality Assurance, and development and maintenance of Work Cards that are adopted into the NAMIS Maintenance Actions.

The Contractor shall provide services to incorporate changes to technical publications arising from organizational engineering, maintenance, or quality assurance instructions as well as changes to organizational documents necessitated by changes from the Original Equipment Manufacturer (OEM) and by the FAA through Airworthiness Directives and Instructions for Continued Airworthiness.

The Contractor shall provide support for all normal life-cycle support elements for organizational technical publications including subject matter research, document generation, tracking, publication, and maintenance.

Accuracy of the technical content is the responsibility of the originating organization but the Contractor shall be responsible for the form and technical completeness to ensure that all approved changes are properly included.

The Contractor shall track the status and location of all documents, technical orders, and changes that are under development or in the approval cycle and shall report regularly, at least monthly, on the status of the publications whether electronic, hardcopy, or both. Weekly reports shall provide statistics on quantities and locations, but the weekly status reports are not required to report the location status of every document.

The Contractor shall provide support for selection, development, implementation, integration, maintenance and operations, and sustaining engineering of a document management system. The Contractor shall assist the Government in continued development of user requirements for the electronic document management system to include enhancements to document routing and approval.

The Contractor shall support all technical publications and documentation development and maintenance which are associated with NAMIS and all aspects of aviation. The Contractor shall

C-18 provide document configuration and version control, release control, and electronic and hard-copy publication. The Contractor shall provide task management, technical writing and editing, draftsman skills, and graphic services.

Major subtasks include but are not limited to:

a. Electronic Documentation System - The Contractor shall support a system and processes to manage electronic and hardcopy documentation. This includes engineering drawing management and an electronic library.

b. Electronic Document Creation - The Contractor shall provide services to create electronic documents consisting of technical manuals, checklists, operations manuals, work instructions, presentations (including multi-media, graphics and digital images), and other electronic documents appropriate to support operational systems and systems performance analysis.

c. Hardcopy document creation and delivery - The Contractor shall deliver hardcopy end items such as checklists, in-flight guides, and other technical manuals used for support of aircraft operations.

d. Conversion of hardcopy to electronic format - The Contractor shall, when required, convert text and engineering documents from hardcopy to electronic format utilizing Government-furnished services, equipment, and or software. Recommendations on outsourcing versus in-house document conversion are required. The Government will make a selection based on the recommendation.

C-19

This page intentionally left blank

C-20

2 Baseline B: FOD Mission Enabling Services

The Flight Operations Directorate (FOD) and its supported affiliate organizations consists of approximately 2,500 individuals including, but not limited to, flight controllers, mission planners, trainers, domestic astronauts, International Partner (IP) astronauts, cosmonauts, management astronauts, flight directors, engineering support, directorate, and administrative staff (hereinafter referred to as “the customer”). The customer’s primary mission is to plan, train, and fly NASA space missions aboard the International Space Station (ISS) and any future NASA space endeavors as well as to support the development of human rated launch systems.

The customer is a highly mobile, demanding, time compressed group and is highly unpredictable in terms of location and schedule. Some communities within the customer base have working relationships and responsibilities at the highest levels of the United States and foreign governments.

The customer also depends on unique and specialized support and services to enable its primary mission to plan, train and fly. The customer requires support for these technical integration and administration functions, unique multimedia coordination and production, and technical planning efforts.

The customer depends on specialized and highly-specialized IT resources to accomplish its mission. The customer has very demanding support and availability requirements for their IT resources to ensure flight safety and success.

2.1 Scope

Baseline B scope provides the mission enabling services and support for FOD. The scope extends to the associated systems that share data, hardware, software, or human resources within

FOD.

The scope includes system administration, database administration, and a performance management functions associated with Space Flight Operations. This scope also includes project support, configuration management and data management of FOD’s mission enabling space flight activities. The scope includes the procurement and tracking of hardware and software systems and associated maintenance and license agreements including hardware and software asset-management and logistical support required to perform the work defined in this Baseline.

The scope includes unique FOD required end-user support above and beyond services provided by Center or Agency contracts to support the Astronaut Office (AO), and Flight Director (FD) Office.

2.2 General Requirements

This section of the SOW specifies the general requirements applicable to Baseline B.

2.2.1 Contract Management

The Contractor shall provide leadership, management oversight, direction, and problem resolution for all functions performed under Baseline B. The Contractor shall provide contract

C-21 management to act as the primary interface to the Contracting Officer (CO) and Contracting Officer Representative (COR). The Contractor shall:

a. Provide a management interface who is authorized to direct day-to-day work, coordinate with NASA on contractual matters, respond to questions and action items from NASA, and resolve problems.

b. Prepare program performance metrics and report program performance.

c. Accept and utilize existing hardware, software, and documentation unless otherwise agreed with NASA.

d. For activities performed under this contract, adhere to the JSC Quality Management

System (QMS) and appropriate FOD quality management documentation.

e. Comply with Attachment J-XX, List of Applicable Documents.

f. Integrate with and utilize, to the maximum extent practicable, the NASA-established contract management system that includes, but is not limited to, order processing, contract correspondence, and DRD delivery.

2.2.1.1 Project Management and Staffing

products and services specified in Baseline B, in accordance with DRD-XX, Contract Management and Staffing Plan.

The Contractor shall perform activities at the request of the Government that support research, development, acquisition, and sustainment efforts across a broad spectrum of functional disciplines in order to effectively assist in the implementation of Government programs.

2.2.1.2 Financial Management

The Contractor shall provide project support in the area of financial management which includes, but is not limited to:

a. Conducting financial studies and research

b. Evaluating project funding plans and changes

c. Providing comments and recommendations for program guidance

2.2.2 Change Management

the MESC contract. These changes include corrections of issues documented in deficiency reports, sustaining engineering change requests, and any other change authorized by the Government. The Contractor shall update all related documentation when changes are released.

The Contractor shall integrate with and utilize the NASA-established change and discrepancy reporting program and systems for the submittal, status, review, ranking, and reporting of changes and discrepancies, including, but not limited to, Change Requests (CR), Incident Reports (IR), and Problem Reports (PR).

2.2.3 Technical Meeting Support

The Contractor shall provide the necessary technical support to the appropriate FOD configuration control boards, and panels, including but not limited to, producing meeting agendas, recording meeting minutes, and recording final disposition.

C-22

2.2.4 Technology Evaluations

commercial alternatives (hardware/software tools, components or complete solutions) that includes an evaluation of existing Commercial-Off-The-Shelf (COTS) products, as well as products available through Government-Off-The-Shelf (GOTS) investments. The Contractor shall provide life-cycle cost/benefit analyses of the recommended commercial alternatives.

2.2.5 Logistics

The Contractor shall provide logistical support (e.g., sparing, check-in/check-out, shipping, courier services, equipment provision, and maintenance) to ensure sufficient planning, arrangements, and support for the activities comprising the technical, managerial, and administrative services specified for Baseline B.

The Contractor shall be responsible for transporting items from JSC central receiving to contractor on-site warehouses or on-site buildings as needed.

2.2.6 Government Property

Physical equipment, as enumerated in Attachment J-XX, List of Installation-Accountable Government Property is classified as Government property.

“Contractor-acquired property” means property acquired, fabricated, or otherwise provided by the Contractor as a direct contract charge to NASA for performing a contract and for which NASA has title.

Attachment XX, List of Installation-Accountable Government Property, identifies the on-site Government physical property made available on a no-charge basis for use in performance of

MESC.

NASA will provide the onsite contractors with standard NASA End User Services and Technologies (NEST) computer seats and phone seats as Agency Institutional IT. NASA is responsible for support and asset management of Agency Institutional IT, including hardware and all standard software. Mobile phone seats will also be provided to Contractor personnel who are on-call for help-desk and customer assistance at the discretion of the Government.

The Contractor shall submit updates to the List of Installation-Accountable Government Property, in accordance with the schedule defined in Attachment J-XX.

The Contractor shall document and maintain MESC Government property management processes and procedures in accordance with DRD-XX, Government Property Management Plan

(PMP).

The Contractor shall utilize the Government’s property tracking system for MESC property identified in Attachment J-XX, List of Installation-Accountable Government Property. The Contractor shall provide custodians to input and manage data in the Government’s property tracking system for property provided under this contract.

C-23

The Contractor shall be the delegated property administrator and shall designate a point-of-contact for MESC Government property administration and management.

2.2.7 Non-Disclosure Agreements (NDAs)

The Contractor shall provide a nondisclosure statement (per company policy), a signed individual nondisclosure statement for each person supporting specific tasks as identified by the Government, and a summary of the procedures for information control and protection that are applicable to all personnel supporting those tasks.

It is anticipated that the Contractor will have access to, be furnished with, or use the following types of recorded information:

a. Information pertaining to third parties, with limited rights or restricted rights, in the form of notices submitted via NASA or directly to the Contractor

b. Information pertaining to third parties, which NASA has agreed to handle under protective arrangement

c. Information of which NASA intends to control the use and dissemination

d. Information governed by the Privacy Act of 1974, 5 U.S.C. 552a

In order to provide appropriate management and control for protecting this information, the Contractor shall:

a. Use and disclose such information only to the extent necessary to perform the work required under this task, with particular emphasis on restricting the information to employees having a “need to know”

b. Establish the procedures and controls necessary to prevent disclosure of this information outside of the Contractor’s scope of work in this task, except in accordance with written instructions from the CO

2.2.8 Information Technology Security

The Contractor shall provide support for the annual NASA/JSC Security Plan requirements as set forth in NPR 2810.1 and shall ensure compliance with the applicable certification and accreditation standards. This includes ensuring the IT components meet NASA and

Security Management Plan and Reports.

2.2.9 Emergency Preparedness

preparedness and disaster recovery, in accordance with the DRD-XX, Emergency Preparedness & Disaster Recovery / Continuity of Operations Plan (DRCOP).

2.2.10 Safety and Health

The contractor shall perform tasks to ensure the protection of personnel, property, equipment, and the environment in contractor products and activities generated in support of institutional and spaceflight program objectives. To ensure compliance with pertinent NASA policies, requirements, federal, state, and local regulations for safety, health, environmental protection, and fire protection, the contractor will develop and implement a safety and health program per a NASA-approved safety and health plan. The “JSC Safety and Health Requirements” document

C-24 provides detailed requirements and instructions regarding safety and health procedures and policies at JSC and is incorporated by reference into all JSC contracts when performance is on site at a JSC facility. It can be viewed at http://jscHandbook.jsc.nasa.gov.

2.3 Infrastructure Service Requirements

The Contractor shall provide sustaining engineering support for all end items enumerated in Attachment J-XX, List of Installation-Accountable Government Property.

2.3.1 Configuration Management and Control

The Contractor shall provide configuration control of all requirements and specifications. The Contractor shall provide configuration management and tracking for all code. The contractor shall ensure configuration and management tracking include traceability of all requirements through all levels, i.e. requirements through acceptance tests. Configuration management shall also extend to the hardware and full software load on each server supported under Baseline B.

2.3.2 FOD IT (FIT) System Sustaining Engineering Support

The Contractor shall provide sustaining engineering support for the FIT System and its legacy predecessor components. In performing sustaining engineering support of the FIT System, and its legacy predecessor components, the Contractor shall, in accordance with the FOD IT Management plan:

a. Manage and maintain all servers, and the associated IT infrastructure, including warranty tracking, troubleshooting, and contacting the vendor for onsite repair, as required

b. Perform all upgrades to, and perform preventative maintenance on hardware and install new server hardware, and any associated IT infrastructure

c. Manage and maintain all access control groups (e.g. domain groups)

d. Manage and oversee all identity, credentialing, and access management (e.g.

ActiveDirectory)

e. Support hardware installations as required

f. Install new software and perform patch upgrades to comply with NASA IT standards

g. Install and maintain FOD-unique office applications

h. Remove hardware/software that is deemed no longer required by the Government

i. Manage access to data in accordance with NASA IT standards

j. Perform and verify backups and restores

k. Develop and maintain system documentation

l.…