Section_C.docx

Section C – Statement of Work

Contents of Section C: JOIST Statement of Work

Introduction

The purpose of the Joint Operations and Integrated System Technology (JOIST) contract is to provide for development, sustainment, and maintenance of specialized and highly-specialized information technology (IT) software, systems, and support to the Johnson Space Center (JSC) Flight Operations Directorate (FOD) and its affiliate organizations. JOIST spans the mission support requirements of NASA and 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 JOIST 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 and any related contracts, 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. Baseline A and Baseline B content includes statically-defined, Full Lifecycle IT management and execution. Full Lifecycle IT management and execution spans the “cradle to grave” IT processes, including development (a dynamic phase), sustaining, and disposal of IT hardware, software, and associated services as defined in the Statement of Work.

The two single-award baselines are the following:

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

· Baseline B: FOD IT and Planning, Integration, and Control (PIC) Services The multiple-award IDIQ component consists of requirements for specialized, highly-specialized, and advanced research and development IT not covered under the baselines. The IDIQ scope is inclusive of Baseline A and Baseline B scope in the event that Baseline A or B options are not exercised, thereby allowing for the competition of that baseline scope as a task order or task orders amongst the JOIST multiple-award IDIQ awardees or other competitive environment.

This page intentionally left blank

Baseline A: NAMIS Services

Baseline A provides the requirements for the IT and related support for NAMIS, an integrated, module-based, custom software suite that supports aircraft flight operations across NASA. NAMIS is an Agency-wide system in use by Ames Research Center (ARC), Armstrong Flight Research Center (AFRC), Glenn Research Center (GRC), NASA Headquarters/Aircraft Management Division, Johnson Space Center (JSC), Kennedy Space Center (KSC), Langley Research Center (LaRC), and Wallops Flight Facility (WFF). NAMIS may also be 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.

Scope The scope includes all the life-cycle support elements for an enterprise-level, agency-wide IT 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 development of 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 IT and data management systems into a cost-effective open systems architecture that provides users with accurate and timely information.

The scope includes 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 includes sustaining and modification of the following supplemental applications as well as those listed in Attachment J-04, List of Government-Furnished Computer Software:

a. Change Request (CR)/Discrepancy Report (DR) Tracking System

b. Personnel Application (NAMIS Users)

c. Engineering Work Order Application

d. ViPER (Virtual Publications Electronic Repository)

e. QMT (Quality Management Tool)

f. NAARS (NASA Aviation Anomaly Reporting System)

g. Application Deployment Utility

h. Attachments Web Service

i. Nametags

The scope includes 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 includes 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 includes adapting the NAMIS modules for tracking and management of newly identified air and ground vehicles and other assets approved by the Government.

The scope 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 includes 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, OSHA and FAA regulatory requirements relating to safety and/or flight operations.

The scope includes 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 includes development and maintenance of the full spectrum of services associated with aircraft documentation.

In the event that NASA enters into an agreement with another Federal agency or external organization to implement the NAMIS modules at that external organization, the scope includes the full range of integration and implementation services for that organization.

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

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 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-07, 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.

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 DRD-03, 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.

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 (Reference DRD-17, Monthly Cost Reporting (533 and Supplemental Requirements)

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. Status reports shall be provided to monitor progress to the CO, COR, NASA NAMIS Project Manager, and NASA NAMIS Technical Manager.

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, implementation plans and schedules using standard project planning tools will be provided to the Government. Each major project will be independently tracked for technical and financial performance. The Task Management Plan will be updated as appropriate to reflect each project or task as it is added to the on-going effort.

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.

Change Management The Contractor shall implement changes to hardware and software components managed under Baseline A. These changes include corrections of issues documented in Deficiency Reports (DRs), 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), DRs, 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 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 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 documented in DRs 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.

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 completion of acceptance testing by the users.

The Contractor shall include the items in the following list for any software, hardware, or system-deliverable designated by the Government as mission essential, mission critical, or safety critical for which the Government determines there is no readily available commercial substitute that performs substantially the same functions at substantially the same cost to the Government:

a. Documented, uncompiled source code accompanied by a license for an appropriate software compiler as a part of the deliverable and a written acknowledgement that the software end item, excluding the compiler, does not include any protected intellectual property from any Contractor or subcontractor who provides or contributes to the software; or

b. If the software product does include the vendor’s, Contractor’s, or sub-Contractor’s protected intellectual property, an escrow agreement signed by the holder of the intellectual property rights and approved by the NASA NAMIS Project Manager, NASA NAMIS Technical Manager, COR, and the CO and accompanied by delivery of documented, uncompiled source code to a NASA-designated escrow agent; or

c. A written waiver of these requirements signed by the NASA NAMIS Project Manager, NASA NAMIS Technical Manager, and COR.

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.

Requirements Analysis & Development Services The Contractor shall provide services in support of requirements analysis and development. These analyses include business requirements, functional requirements, and user requirements as well as agency, center, program, project, system, and design requirements development. This will 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.

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.

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 Institute’s 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.

Technology Evaluations When requested by the Government, the Contractor shall provide recommendations for 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) solutions. The Contractor shall provide life-cycle cost/benefit analyses of the recommended commercial alternatives.

Government Property Physical equipment, as enumerated in Attachment J-05, 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-05, 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 JOIST.

NASA will provide onsite contractors with standard NASA Agency Consolidated End-User Services (ACES) 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 Attachment J-05, List of Installation-Accountable Government Property, not later than 30 days after the beginning of each fiscal year.

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

The Contractor shall utilize the Government’s property tracking system for JOIST property identified in Attachment J-05, 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.

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

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.

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 includes ensuring the NAMIS components meet NASA and organizational security standards. Reference DRD-06, Contractor Information Technology (IT) Security Management Plan and Reports.

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

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

b. OSHA directives

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

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.

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.

Implementation Services The Contractor shall provide implementation support to include:

a. Data extraction from legacy systems

b. Data cleansing

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

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 System’s System, Applications and Products (SAP)

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 are to 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

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 shall ensure that no more than one day’s 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.

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 to a Disaster Recovery system within 8 hours of system loss. Localized component or system failures shall also be recovered 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. Database related applications shall be returned to operability within 8 hours of the failure.

End-User Support Services Requirements The Contractor shall provide user support services for the systems listed in Attachment J-05, List of Installation-Accountable Government Property.

Support shall include end-user training, implementation support for the receiving organization, and sustaining support for the deployed components.

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. Help-Desk support may be provided via on-site and/or on-call services. This support shall be focused on process analysis to determine root causes of user, process, and software issues for incorporation into remediation plans.

User Training The Contractor shall develop training programs and materials for the NAMIS modules. Training aides shall be focused 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.

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

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 upgrades to the systems. The expected requirement is for two “point-level” releases each year. A point release is described as an enhancement in capabilities to the existing system that require significant but not major modifications to the underlying data structure or existing code base. “Maintenance releases” in which only defects are corrected shall not be considered “point releases” or upgrades to the products.

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

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:

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 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 Document Management System SharePoint-based system.

h. Upgrades to the Engineering Drawing Configuration Management System 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-04, List of Government-Furnished Computer Software.

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 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 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:

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.

Baseline B: FOD IT and PIC 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 IT resources to accomplish its mission. The customer requires support at all times to ensure the availability of their IT resources, including the associated all-encompassing back-end IT infrastructure and software.

Scope The scope includes all services and support relating to implementing the FOD Information Technology (FIT) System, and its predecessor legacy components, including system design, development, procurement, installation, sustaining engineering, configuration management, system and security administration, training, and user support. The scope shall extend to the associated systems that share data, hardware, software, or human resources with the FIT System, such as security systems, system service interfaces, and system data exchange interfaces.

The scope includes system administration, database administration, and a performance management function that will be used to improve FOD’s ability to troubleshoot and identify sources or performance issues or problems in their IT systems.

The scope includes the procurement and tracking of hardware and software systems and associated maintenance and license agreements for Baseline B. It also includes hardware and software asset-management and logistical support (e.g., sparing, shipping, receiving, and maintenance) as required to perform the work defined in this Baseline.

The scope includes FOD end-user support not covered by the Center or Agency contracts. End-user support shall include two support-level tiers: Enhanced User services for the Astronaut Office (AO), FOD Directorate Suite, and Flight Director (FD) Office, and Standard User services for all other FOD civil service and Contractor employees and the Commercial Crew Program Office (CCPO).

The scope includes IT Resource Management (ITRM) inclusive of IT planning, and IT investment management and reporting.

The scope includes responsibility for providing the following administrative and technical services:

a. Project support and Configuration Management (CM) of FOD Project Information Systems

b. Configuration Management and Data Management (CMDM) of all Business Planning and Control Office project management processes, documentation, and FOD Control Board (CB) activities

c. Facility utilization and optimization

d. Integrated Master Scheduling

e. Technical Integration Services

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

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 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-07, 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.

Project Management and Staffing The Contractor shall organize and institute integrated processes and tools for managing the products and services specified in Baseline B, in accordance with DRD-03, 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.

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 (Reference DRD-17, Monthly Cost Reporting (533 and Supplemental Requirements))

Change Management The Contractor shall implement changes to hardware and software components managed under the JOIST 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 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), Discrepancy Report (DR).

Technical Meeting Support The Contractor shall provide the necessary technical support to the appropriate NASA configuration control boards, panels, and working groups in all matters of disposing changes including, but not limited to, producing meeting agendas, recording meeting minutes, and recording final disposition.

Technology Evaluations When requested by the Government, the Contractor shall provide recommendations for 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.

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 JOIST on-site warehouses or on-site buildings as needed.

Government Property Physical equipment, as enumerated in Attachment J-05, 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-05, 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 JOIST.

NASA will provide the onsite contractors with standard NASA Agency Consolidated End-User Services (ACES) 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 Attachment J-05, List of Installation-Accountable Government Property, not later than 30 days after the beginning of each fiscal year.

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

The Contractor shall utilize the Government’s property tracking system for JOIST property identified in Attachment J-05, 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.

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

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:

1. 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”

2. 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

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 organizational security standards. Reference DRD-06, Contractor Information Technology (IT) Security Management Plan and Reports.

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

Infrastruct…